Static Reference Handle for XDM Service Information Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing system for managing XDM service information in OMA services faces issues with signaling overhead, compatibility degradation, and resource waste due to changes in reference handles, particularly when updating reference relationships between shared URI lists and other OMA services.
Innovation Solution
A system and method that utilize a static reference handle, such as a random value, for the shared URI list, which remains unchanged after creation and is used consistently across OMA services, eliminating the need for additional signaling updates and maintaining stable reference relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a dynamic reference handle (such as URI or list name) is used for shared URI list, then the reference can be updated to reflect changes in service information, but additional signaling overhead is generated and system resources are wasted when updates occur
Solution Approach 1:
The reference handle is segmented into two parts: a static identifier (ID) that remains unchanged and a dynamic descriptor (URI/list name) that can be updated. This segmentation allows the system to maintain stable references while enabling necessary updates without generating excessive signaling overhead.
Solution Approach 2:
A static ID is assigned to the shared URI list at creation time as a preliminary action. This pre-established identifier serves as a stable reference point that eliminates the need for continuous update signaling, while still allowing the dynamic descriptors to be modified when service information changes.
2Adaptability or versatility
If a dynamic reference handle is used for shared URI list, then the reference can adapt to service information changes, but compatibility degradation occurs due to frequent updates
Solution Approach 1:
The reference handle is segmented into a static ID component and a dynamic descriptor component. The static ID ensures compatibility by remaining unchanged across updates, while the dynamic descriptor allows adaptability to service information changes. This segmentation resolves the contradiction between maintaining compatibility and enabling updates.
Solution Approach 2:
Different parts of the reference handle have different qualities: the ID portion is static and immutable to ensure compatibility, while the URI/list name portion is dynamic and mutable to ensure adaptability. This local differentiation of properties allows the system to simultaneously achieve both compatibility and adaptability.
3Loss of energy
If a static reference handle is used for shared URI list, then signaling overhead is reduced and system resources are conserved, but the reference cannot be updated when service information changes
Solution Approach 1:
The reference handle is divided into a static ID that reduces signaling overhead and a dynamic descriptor that maintains adaptability. This segmentation allows the system to achieve both low signaling overhead and reference update capability by utilizing different components for different purposes.
Solution Approach 2:
A static ID is assigned in advance to serve as the primary reference handle, which reduces signaling overhead. Meanwhile, the system maintains the ability to update dynamic descriptors when service information changes, thus preserving adaptability while minimizing resource consumption.
4Adaptability or versatility
If dynamic reference handles are used for shared URI list, then service information can be updated, but device complexity increases due to management of reference relationships
Solution Approach 1:
The reference handle is segmented into a simple static ID and a dynamic descriptor. This segmentation simplifies reference relationship management by providing a stable anchor point (the ID) that reduces the complexity of tracking changes, while still allowing service information updates through the dynamic descriptor portion.
Solution Approach 2:
The static ID is assigned in advance as a preliminary action, establishing a stable reference framework before service information changes occur. This pre-established structure simplifies subsequent update operations by providing a consistent reference point, thereby reducing the overall device complexity of managing reference relationships.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed is a system and method for managing XDM (XML Document Management) service information to improve management efficiency for OMA (Open Mobile Alliance) service information. The apparatus includes a controller for creating a shared User Resource Identifier (URI), and using a value created by the controller as a static value to be used as a newly-created reference handle for shared service information referred to by service information. The newly-created value is set as an unchanged value (i.e., it remains static until a corresponding element vanishes), thereby preventing signaling overhead, compatibility degradation, and resource waste due to modification of the shared service information.