SIP Push Session Setup Using Device Identity Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing push session setup methods, multiple clients bound to a public user ID receive push messages unnecessarily, wasting network resources and leading to poor user experience, as all clients are required to set up connections with the server to receive the same message.
Innovation Solution
The method involves obtaining device identity information for each client and adding it to a Session Initiation Request (SIR) message, allowing only the intended client to set up a push session connection with the server based on Session Initiation Protocol (SIP), thereby routing the SIR message specifically to the client that needs to receive the push message.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a public user ID is used to identify the client in the SIR message, then all clients bound to the user ID can receive push messages, but network resources are wasted and user experience deteriorates due to unnecessary message delivery to multiple clients
Solution Approach 1:
The patent segments the client identification from the public user ID level down to the individual device level. Instead of using a single public user ID that binds multiple clients, the system introduces device identity information (such as device ID or international mobile equipment identity) to uniquely identify each client device. This segmentation allows the SIR message to be targeted at a specific device rather than being broadcast to all devices associated with a user account, thereby eliminating unnecessary network resource consumption while maintaining the ability to deliver push messages to the intended client.
2Reliability
If the SIR message is sent to all clients corresponding to a public user ID, then connection setup is ensured for all clients, but the quantity of message reception increases unnecessarily
Solution Approach 1:
The patent extracts the device-specific identity information from the broader public user ID context and uses it as the primary routing key for SIR messages. By taking out the device level identification (device ID, international mobile equipment identity) from the user account level identification, the system enables precise targeting of the SIR message to only the intended device. This extraction ensures reliable connection setup for the specific client that needs to receive the push message while preventing unnecessary message reception by other clients bound to the same user ID.
3Loss of energy
If device identity information is added to the SIR message, then only the intended client receives the push message, but the device complexity increases
Solution Approach 1:
The patent leverages the existing device identity information (such as device ID or international mobile equipment identity) that is already universally present in mobile communication devices. Rather than introducing a completely new identification mechanism, the system repurposes these existing device-level identifiers for the specific function of push message routing. This multi-functional use of existing device identity information allows precise message targeting without significantly increasing device complexity, as the same identity data serves both general device identification and specific push session routing purposes.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A method, a push system, and relevant devices for setting up a push session are provided. The method for setting up a push session includes: obtaining device identity information of a client; adding the device identity information of the client to a Session Initiation Request (SIR) message; and sending the SIR message to the client according to the device identity information of the client, and requesting the client to set up a push session connection based on a Session Initiation Protocol (SIP) with a server according to the SIR message. The push system includes a server and a client. The server includes an information obtaining unit, a message adding unit, and a request sending unit. The client includes a request receiving unit and a judging and connecting unit. Hence, the setting up of push sessions based on the SIP is implemented.