Method and apparatus for providing default media content to a calling party

Patent No. US7702083 (titled "Method and apparatus for providing default media content to a calling party") on Feb 28, 2005. The application was issued on Apr 20, 2010.

What is this patent about?

’083 is related to the field of multimedia communication systems, specifically within the context of contact centers and interactive voice response environments. It addresses the technical challenge of maintaining a consistent user experience when a communication session involves multiple media types, such as audio and video, but one of the endpoints lacks the capability to support all active streams. This often occurs during call transfers, queuing, or when a call is routed to a legacy terminal that only supports voice, leading to a fragmented or broken user interface.

The underlying idea behind ’083 is to implement a failover media mechanism that detects a mismatch between the media capabilities of an originating device and a destination endpoint. Rather than allowing a specific media channel to go dead—such as a video screen turning black when a caller is transferred to a voice-only agent—the system dynamically injects a default content stream to fill the void. This ensures that the high-bandwidth or rich-media capabilities of the caller's device are continuously utilized even when the primary respondent cannot provide the necessary data.

The claims of ’083 focus on a method and apparatus for monitoring the status of media streams between endpoints and triggering a default media injection when a specific media type is missing. The independent claims cover the logic of determining that a destination is not providing a stream of a first media type (e.g., video) that the originating endpoint expects, and subsequently initiating the transmission of substitute content. This logic is designed to function regardless of whether the determination is made via signaling analysis, database lookups, or direct observation of the data packets.

In practice, the invention works by employing a controller or observer that audits the communication session in real-time. If a caller who was previously receiving video from an automated system is transferred to a human agent who only has a telephone, the system identifies this capability gap. It then commands a default media server to stream pre-recorded content, such as advertisements, status updates, or branding, to the caller’s video display while the audio conversation continues with the agent. This process can be handled by the network carrier, a central call center server, or even the client software on the user's device.

This approach differs from prior solutions by moving beyond simple session negotiation to active stream continuity management. Traditional systems would simply drop the unsupported media component or fail to establish it entirely if one party lacked the hardware. By contrast, this invention treats the absence of a media stream as a trigger for a secondary content delivery service. It effectively decouples the media experience from the specific limitations of the destination hardware, ensuring that the multimedia session state remains intact throughout the duration of the interaction.

How does this patent fit in bigger picture?

Technical Landscape

In the mid-2000s when ’083 was filed, multimedia communication in contact centers was at a time when interactive voice response systems were typically implemented using audio-only scripts or VoiceXML pages. While the integration of video and data into telephony was beginning to emerge, systems commonly relied on separate, siloed media streams rather than unified session management that could dynamically adapt to varying endpoint capabilities. Hardware and software constraints made the seamless transition between different media types non-trivial, as call routing and transfer protocols were primarily designed for voice-centric architectures where a lack of media from a destination node resulted in a total loss of signal for that specific channel.

Prosecution Position

The disclosed invention addresses the technical problem of media discontinuity, such as a 'dark screen' effect, occurring when a multimedia call is transferred to a destination endpoint that lacks the capability to support all media types initiated by the caller. The architectural solution involves a monitoring and substitution mechanism that detects the absence of a specific media type—either through capability database lookups, signaling analysis, or direct stream observation—and automatically triggers the transmission of default media from a secondary source. This integration achieves the technical effect of maintaining a continuous, multi-channel user experience during transitional states like call setup, queuing, or transfer, effectively overcoming the constraint of heterogeneous endpoint capabilities within a unified communication session.

Claims

This patent contains a total of 26 claims, with claims 1, 14, and 26 serving as the independent claims. These independent claims focus on a method, an apparatus, and a machine-readable medium designed to detect when a destination endpoint fails to provide a specific type of media stream to an originating endpoint and subsequently trigger the transmission of default media to that originating endpoint. The dependent claims serve to specify the technical components performing the detection, such as application controllers, signaling observers, or stream observers, while also defining the location of the default media server and the specific network entities responsible for executing the process.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Default media
(Claim 1, Claim 14, Claim 26)
Default media services are provided to endpoints when a media stream of the specified type is not available and during transitional periods, such as times of call setup, transfer or hold. A default media source can be directed to provide an appropriate media stream of the given media type.Substitute content provided to an endpoint when the expected media stream of a specific type is unavailable, preventing a 'dark screen' or loss of information.
Destination endpoint
(Claim 1, Claim 14, Claim 26)
Each destination node may not support all of the media types supported by the caller. Examples include operator consoles that do not have video capabilities or nodes that are unidentified during transitional periods like call setup, transfer, or hold.A node, device, or operator console to which a call is transferred or connected, which may or may not support all media types requested by the caller.
Initiating transmission
(Claim 1, Claim 14, Claim 26)
The server handling the routing may deliver or designate another server to deliver a default media stream until a connection with the destination endpoint is completed. This can be implemented by a server-side device, by client-side device, or by a device associated with a carrier, such as an Internet Service Provider.The act of triggering the delivery of substitute content, which can be performed by a server-side device, a client-side device, or a carrier-associated device.
Media stream of a first media type
(Claim 1, Claim 14, Claim 26)
Multimedia communications allow a call center to efficiently exchange information with a user using a number of different media. Examples of media types include images, video, audio or text, such as a video portion used to present a graphical menu.A specific category of multimedia content, such as video, audio, images, or text, transmitted during a communication session.
Originating endpoint
(Claim 1, Claim 14, Claim 26)
An originating device supports a video connection and receives a default video stream until the call is connected to a destination endpoint that delivers video content. The originating endpoint may be associated with a client-side device that determines if a media stream is being provided.A communication device that initiates a call or connection and supports specific media types, such as video, which expects to receive corresponding media streams.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
7:25-cv-00483Oct 22, 2025Arlington Technologies LLC v. NVIDIA Corporation

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US7702083

Application Number
US11068096A
Filing Date
Feb 28, 2005
Publication Date
Apr 20, 2010
External Links
Slate, USPTO , Google Patents