Discovery Server Architecture for Context-Aware Network Service Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing machine type communication architectures, such as 3GPP, lack flexibility in service discovery and do not support context-aware and policy-based mechanisms for MTC entities, leading to inefficient service provisioning and network load balancing.
Innovation Solution
Implement a Discovery Server within the 3GPP network to facilitate service-based discovery, allowing MTC entities to query and discover services based on situational context and policy information, enabling dynamic load balancing and service selection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a Discovery Server is implemented to enable context-aware and policy-based service discovery, then service discovery flexibility and efficiency are improved, but network architecture complexity increases
Solution Approach 1:
A Discovery Server is introduced as an intermediary component between MTC entities and services. The server receives discovery requests from MTC entities, queries the service repository for matching services based on context information and policies, and returns appropriate service information. This mediator approach enables flexible, context-aware service discovery without requiring complex peer-to-peer negotiation mechanisms among MTC entities, thus improving adaptability while managing architecture complexity through a centralized coordination point.
2Productivity
If MTC entities dynamically select services based on situational context, then service provisioning efficiency is improved, but information processing requirements increase
Solution Approach 1:
Context information and service criteria are pre-configured and stored in the Discovery Server before actual service discovery operations. The server maintains a service repository with pre-processed service descriptions, capability profiles, and policy rules. When an MTC entity submits a discovery request, the server performs efficient matching against pre-prepared data structures rather than processing raw information in real-time, thus improving service provisioning efficiency while minimizing information processing requirements during operational phases.
3Productivity
If the Discovery Server controls entity discovery based on policies, then network load balancing is improved, but control mechanism complexity increases
Solution Approach 1:
The Discovery Server implements policy-based control by evaluating and filtering discovery requests against predefined policy parameters such as entity types, service categories, geographic locations, and network conditions. The server dynamically adjusts discovery outcomes based on these parameters, enabling network load balancing by directing entities to appropriate services and preventing overload on specific network components. This parameter-driven approach provides effective load balancing through simple comparison operations rather than complex real-time optimization algorithms.
Data Source
AI summary
Systems, methods, and instrumentalities may implement service-based discovery in a network, such as a 3GPP or 3GPP2 network. A Discovery Server may be used to query and find services offered by the network or by entities that interface with the network. Situational context information or policy information, or both, may be communicated to the discovery server so that the Discovery Server can provide context-aware and policy-based discovery services. The Discovery Server may be used to control which of the entities that interface with the network can discover one another. The Discovery Server may support queries based on, for example, the type of MTC entity, the type of services hosted on the entity, the availability times of the entity, types of protocols supported, levels of Quality of Service (QoS) supported, and MTC-IWF services.