User Determined User Busy

Description

User Determined User Busy (UDUB) is a telecommunications supplementary service defined within the 3GPP standards that empowers the called party to deliberately signal a 'busy' status to the network for incoming calls. Unlike a network-determined busy condition (which occurs when the user is already engaged in a call or has network-verified unavailability), UDUB is explicitly invoked by the user, often through a specific action on the mobile handset, such as pressing a 'busy' button or selecting a 'reject with busy' option during an incoming call alert. When activated, the service causes the user's terminal to respond to the network's call setup attempt with a specific indication that the user is busy by choice. The network, typically the serving MSC or call session control function, then processes this as a busy condition and applies the appropriate call handling procedures, which usually involve terminating the call attempt and returning a busy tone or announcement to the calling party.

The architectural implementation of UDUB involves coordination between the user equipment (UE), the serving network node (e.g., MSC in circuit-switched domains or CSCF in IMS), and potentially the home subscriber server (HSS) where service subscription data is stored. When an incoming call arrives, the network sends a setup message (like SETUP in CS or INVITE in IMS) to the called UE. If the user decides to invoke UDUB, the UE does not answer the call but instead sends a specific rejection message back to the network. In circuit-switched networks, this might be a DISCONNECT or RELEASE COMPLETE message with a cause value indicating 'user busy' (cause #17). In IMS, the UE would send a 486 Busy Here response to the INVITE. The network node interprets this response, ensures the user is subscribed to the UDUB service (by checking subscriber data if required), and then handles the call release towards the caller, providing busy indication.

Key components in the UDUB service include the service logic within the network switch or session controller, the signaling protocols between UE and network (like DTAP in CS or SIP in IMS), and the subscriber profile that may control whether the service is active. The role of UDUB in the network is to provide users with a direct and unambiguous mechanism to control incoming communications, enhancing privacy and call management. It differs from simply not answering a call (which might lead to ring-no-answer and eventual forwarding) or using call forwarding on busy, as UDUB is an immediate, user-initiated busy signal that typically results in a faster call termination and a clear busy indication to the caller. This service is particularly valuable in scenarios where users wish to avoid interruptions without resorting to turning off the device or enabling unconditional forwarding, offering a middle ground for active call screening.

Purpose & Motivation

The UDUB supplementary service was created to address the need for enhanced user control over incoming call handling in digital mobile networks. Prior to such features, users had limited options when receiving an unwanted call: they could answer and then hang up, let it ring until forwarding on no-answer (if configured), or power off the phone—all of which were either socially awkward, delayed, or overly drastic. There was a gap in providing a polite, immediate, and network-assisted method to reject a call while clearly signaling unavailability to the caller. UDUB fills this gap by allowing the user to manually trigger a 'busy' state, giving the caller a clear busy tone or announcement, which is a socially accepted indication that the callee is unavailable, without revealing whether the busy condition is genuine or intentional.

The motivation for standardizing UDUB within 3GPP stemmed from the evolution of supplementary services in GSM and their continuation into UMTS and IMS. As networks offered more advanced call features (like call waiting, call forwarding, and explicit call transfer), providing users with fine-grained control over call acceptance became a key differentiator for service quality. UDUB solves the problem of passive call rejection by making it an active, service-based decision. It also interoperates with other supplementary services; for example, if call forwarding on busy is active, a UDUB invocation might trigger forwarding to voicemail, depending on subscription settings. This creates a cohesive user experience for call management.

Historically, UDUB was introduced in 3GPP Rel-4, aligning with the development of the GSM Phase 2+ and UMTS core network enhancements. Its creation was driven by operator and user demand for better call control features, especially with the proliferation of mobile phones and the desire to manage increasing call volumes. By standardizing UDUB, 3GPP ensured interoperability across networks and devices, allowing users to rely on consistent behavior regardless of their location or handset model. The service addressed limitations of earlier systems where busy conditions were solely network-determined, giving users an empowered role in managing their communication availability.

Key Features

• User-initiated busy condition for incoming calls
• Provides clear busy indication (tone/announcement) to calling party
• Typically invoked via handset UI during call alert
• Works in both circuit-switched and IMS-based call sessions
• Interoperates with other supplementary services like call forwarding
• Enhances user privacy and call management control

Evolution Across Releases

Defining Specifications