Push Server HTML File Delivery During Voice Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 2G/3G networks, the limited bandwidth restricts the ability to push rich media content during voice calls, and existing OTT technologies do not support real-time data communication, limiting the provision of multimedia content to subscribers during voice processes.
Innovation Solution
A method and device utilizing the MSRP protocol to push HTML files to subscribers during voice calls, establishing MSRP-TCP connections to transmit HTML files between terminals, enabling the provision of rich media content by adding HTML file information to SIP call request messages and media request messages, and using RTP bearers for ringback tones.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If ringback tone audio occupies the bandwidth exclusively in 2G/3G networks, then audio quality is maintained, but other data cannot be pushed
Solution Approach 1:
The patent segments the bandwidth by introducing separate bearers: one dedicated to ringback tone audio (maintaining quality) and another for data transmission (enabling HTML file pushing). This is achieved through the SCSCF forwarding SIP messages with HTML file information to the push server, which then establishes separate MSRP connections for data transfer while audio continues on the original bearer.
Solution Approach 2:
The push server acts as an intermediary that receives SIP call request messages from the SCSCF, extracts HTML file information, establishes MSRP-TCP connections separately from the audio bearer, and transfers HTML files to the called terminal. This intermediary enables data pushing without interfering with the dedicated audio bandwidth.
2Duration of action of moving object
If existing OTT technology downloads content locally after data connection is enabled, then content can be stored, but real-time delivery during voice calls is not supported
Solution Approach 1:
The patent implements preliminary action by pushing the HTML file to the called terminal during the voice call setup phase (via SIP INVITE message), before the actual voice conversation begins. The SCSCF forwards the SIP message containing HTML file information to the push server, which establishes the MSRP connection and transfers the file in advance, so content is ready immediately when needed rather than downloading during the call.
3Reliability
If data connection is disabled during call process in existing terminals, then call quality is maintained, but real-time data communication cannot occur
Solution Approach 1:
The patent segments communication channels by using separate bearers: the original audio bearer for voice call quality and a new MSRP-TCP bearer for real-time data communication. The push server establishes this separate data connection independently of the voice call setup, allowing HTML files and other data to be transmitted in real-time during the call without affecting voice quality.
Solution Approach 2:
The patent makes the communication system multi-functional by enabling the MSRP-TCP connection to handle both data pushing during call setup and real-time data communication during the call. The same MSRP infrastructure supports both preliminary content delivery and ongoing data exchange, eliminating the need to disable data connections during calls.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Embodiments of the present invention relate to the communications field, and provide a method for implementing a push service and a device, so that an HTML file can be pushed to a subscriber in a process of a voice call, and rich media content can be provided to the subscriber. The method includes: receiving, by a push server, an SIP call request message sent by a calling terminal, and adding first HTML file information set by a calling party to the SIP call request message; sending the SIP call request message to an SCSCF of a called domain, so that the SCSCF of the called domain forwards, to a called terminal, the SIP call request message carrying the first HTML file information; establishing an MSRP-TCP connection to the called terminal according to the MSRP; receiving a first HTML file obtaining request sent by the called terminal; and sending a first HTML file to the called terminal by using the MSRP-TCP connection to the called terminal.