UE Relationship Entity Management for Group Service Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunications networks struggle to recognize and manage ad-hoc systems formed by multiple user equipment (UE) operating together as a distinct entity, limiting the ability to provide services tailored to the relationship entity's tasks and understand network usage effectively.
Innovation Solution
A relationship entity management system that assigns a unique relationship ID to groups of UE operating together, tracks their activities using a blockchain-based ledger, and authorizes network services based on UE identifiers and attestation data, enabling better resource utilization and service provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional individual UE management is used, then network infrastructure complexity is low, but the ability to recognize and manage relationship entities is insufficient
Solution Approach 1:
The network management function is segmented into individual UE management and relationship entity management. The relationship entity manager is introduced as a separate functional component that specifically handles group-based operations, while the core network maintains its traditional individual UE management capabilities. This segmentation allows the network to manage both individual devices and relationship entities without overwhelming complexity.
Solution Approach 2:
The relationship entity manager acts as an intermediary between individual UEs and the core network. It receives registration requests from UEs, processes relationship entity formation, generates relationship IDs, and manages the relationship history ledger. This intermediary layer shields the core network from the complexity of relationship entity management while enabling advanced group-based services.
2Measurement precision
If relationship entity tracking is implemented, then service provisioning accuracy is improved, but network function complexity increases
Solution Approach 1:
The relationship entity manager performs multiple functions within a single network function: it registers relationship entities, generates relationship IDs, manages the relationship history ledger, and authorizes network services. This multi-functionality improves service provisioning accuracy by consolidating relationship entity management capabilities while avoiding the complexity of multiple separate specialized functions.
Solution Approach 2:
The system creates a simplified representation of relationship entities through relationship IDs that reference the relationship history ledger. Instead of managing complex relationship data structures throughout the network, the system uses lightweight relationship ID copies that can be efficiently processed by network functions, improving accuracy without proportionally increasing complexity.
3Reliability
If blockchain-based ledger is used for relationship history, then data integrity is improved, but processing overhead increases
Solution Approach 1:
The relationship history ledger is extracted as a separate data storage component from the relationship entity manager. The ledger stores relationship entity data immutably using blockchain technology, while the relationship entity manager handles processing operations. This extraction allows data integrity to be maintained through blockchain's inherent properties while minimizing processing overhead by keeping the ledger as a reference store rather than an active processing component.
4Adaptability or versatility
If relationship ID generation incorporating task information is implemented, then service customization is improved, but identification complexity increases
Solution Approach 1:
The relationship ID generation incorporates task-specific information locally at the point of relationship entity formation. The relationship entity manager extracts relevant task information from the registration request and embeds it in the relationship ID generation process. This local quality approach allows service customization based on task type without requiring complex identification logic throughout the entire network infrastructure.
Data Source
AI summary
Relationship entity management systems and methods for telecommunications network user equipment are disclosed. In some embodiments, two or more UEs may form relationship entity in which they operate together to provide a service using a telecommunications network. A UE acting on behalf of the relationship entity may communicate a registration request message to a network function of the operator core network that includes which the network function may use to assign a relationship ID to the relationship entity. Records of relationship entity actives and/or resources used may be recorded to a relationship history ledger under the relationship ID, such as a block-chain technology ledger for example. In some embodiments, a UE while operating on the operator core network as part of the relationship entity may be authorized to access network services otherwise not available to the UE when they are not part of the relationship entity.