HTTP Proxy XCAP Routing via SIP Query
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for routing XCAP requests in communication networks with multiple XDMS nodes are inefficient, leading to excessive signaling and requiring a 'trial and error' approach, which is not compatible with Auto-Provisioning and results in significant message exchange before finding the correct XDMS node.
Innovation Solution
An HTTP proxy creates a SIP request with user information and sends it to a SIP proxy, which retrieves the address of the allocated XDM server from a subscriber database, allowing the HTTP proxy to route the XCAP request efficiently, reducing the need for extensive signaling and enabling compatibility with Auto-Provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the trial and error method is used to find the correct XDMS node, then the user can be allocated to an XDMS node, but excessive signaling messages are exchanged and time is consumed
Solution Approach 1:
The patent applies preliminary action by having the AP check local storage before forwarding XCAP requests, and by using SIP proxy to query subscriber database in advance to obtain the correct XDMS node address. This prevents the need for trial-and-error routing by preparing routing information beforehand through storage checks and proactive database queries.
2Reliability
If the trial and error method is used to find the correct XDMS node, then the user can be allocated to an XDMS node, but a large number of signaling messages are exchanged
Solution Approach 1:
The patent introduces a SIP proxy as an intermediary between the AP and the subscriber database. The SIP proxy mediates the routing process by querying the database for the correct XDMS node address and returning it to the AP, thereby eliminating the need for multiple trial-and-error signaling messages between the AP and XDMS nodes.
3Ease of operation
If the AP restarts, then the local storage is cleared, but the trial and error procedure must be repeated from the beginning
Solution Approach 1:
The patent implements feedback by having the AP continuously check local storage for user information before forwarding XCAP requests. After a restart, the AP can quickly determine the correct XDMS node by checking if user information exists in local storage, providing feedback-based routing without requiring complete trial-and-error procedures.
4Reliability
If user provisioning into an XDMS node is required, then the user can be allocated to an XDMS node, but compatibility with Auto-Provisioning is lost
Solution Approach 1:
The patent applies universality by making the routing mechanism independent of pre-provisioning requirements. The SIP proxy queries the subscriber database to obtain XDMS node addresses dynamically, allowing the system to work with both traditional provisioning and Auto-Provisioning methods, thereby achieving multi-functionality in terms of provisioning compatibility.
Data Source
AI summary
The present invention relates to methods and apparatuses for finding out which XDM server a specific user is allocated to in a network with several XDM servers. An HTTP proxy (120) receives an XCAP request (610) from an XDM client (100), including information related to a user associated with the XDM client. The HTTP proxy checks if the user exists in its storage (330), based on the received user information, and if not, the HTTP proxy creates a SIP request (630) including the user information, and passes it over to a SIP Proxy (130, 230). The SIP Proxy finds out which XDM server the user is allocated to by enquiring a subscriber database (140), and then the SIP proxy passes the XDM server address information back to the HTTP Proxy (640), which is then able to route the XCAP request (650) to the correct XDM server (150, 250).