Cross-Domain Cookie Personalization for SIP and HTTP Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication networks lack efficient methods for personalizing multiple communication services, such as SIP and HTTP services, which limits user experience and service customization.
Innovation Solution
A method and system that utilize a cross-domain cookie (CD cookie) mechanism to store and insert personalization information across different communication services, allowing for seamless personalization of SIP and HTTP services by storing and retrieving personalization elements in a communication network database and inserting them into relevant messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate personalization mechanisms (HTTP cookies for HTTP services, SIP cookies for SIP services) are used for different communication services, then each service can be personalized independently, but the user experience is fragmented and personalization does not carry across different services
Solution Approach 1:
The patent introduces a universal personalization mechanism that works across multiple communication services (HTTP, SIP, and other IP-based services). Instead of service-specific personalization, a common personalization data structure and transmission mechanism is implemented that can be universally applied to different service types, allowing personalization information to be shared and recognized across service boundaries
Solution Approach 2:
The patent introduces intermediary components (personalization server, personalization data storage, and message modification mechanisms) that act as mediators between the user and different communication services. These intermediaries capture, store, and inject personalization information into service messages, enabling seamless personalization across services without requiring each service to implement its own personalization logic
2Ease of operation
If service-specific personalization cookies are used, then personalization can be implemented within each service domain, but personalization information is lost when switching between services or using different devices
Solution Approach 1:
The personalization mechanism is designed to be service-agnostic and device-agnostic, using universal message formats and transmission protocols that work across HTTP, SIP, and other IP-based communication services. The personalization data structure and injection mechanism are universally applicable, enabling consistent personalization experience regardless of service type or accessing device
Solution Approach 2:
The system performs preliminary actions by capturing and storing personalization information during initial service interactions, and then proactively injecting this stored personalization data into subsequent service messages before the user actually needs it. This preliminary storage and proactive injection ensures personalization is available across services and devices without requiring the user to re-input preferences
3Reliability
If independent traffic streams are used for different communication services, then each service can operate autonomously, but there is no functional relation or coordinated personalization between services
Solution Approach 1:
The patent introduces intermediary personalization components that operate independently for each service traffic stream while maintaining coordinated personalization across services. These intermediaries capture service-specific message characteristics, apply appropriate personalization data, and inject modified messages back into the respective service flows, preserving service independence while enabling correlated personalization through the intermediary layer
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A message (203) of a first communication service is received from a service provider. On the basis of the received message (203) of the first communication service, an information element for personalizing communication services is stored. The received message (203) of the first communication service is then forwarded towards a subscriber (10). Further, a message (205) of a second communication service is received from the subscriber. The stored information element is inserted into the received message (205) of the second communication service. The received message (205) of the second communication service with the inserted information element is then forwarded towards the service provider. The service provider may then personalize the second communication service based on the information element.