Priority-Based LDAP Service Publication Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing directory services, such as LDAP, do not effectively direct clients to a preferred service instance based on proximity, leading to potential overload of service instances and inefficient service location.

Innovation Solution

A method and system that query a directory for all service instances, storing domain and priority data in the service binding attribute, allowing clients to select a preferred instance by comparing domain names and priorities, ensuring clients connect to a service instance close to them while preventing overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If clients connect to service instances without priority-based selection, then service location is simple, but service instances may become overloaded and efficiency decreases

Engineering Contradiction:
Improveservice location efficiencyVSAvoiddirectory service structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-assigning priority values and domain information to each service instance before clients need to connect. The directory service is pre-configured with multiple service instances, each having assigned priorities and associated domains, allowing clients to efficiently select the most appropriate instance without complex runtime decisions about load distribution

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements local quality by allowing different service instances to have different priority levels and domain associations tailored to their specific characteristics and locations. Each service instance can be optimized for its local domain, with priorities assigned based on proximity, capacity, and other local factors, rather than treating all instances uniformly

Inventive Principle:
Principle #3Local quality

2Reliability

If multiple service instances are provided without priority assignment, then service availability increases, but client selection becomes inefficient and overload occurs

Engineering Contradiction:
Improveservice availabilityVSAvoidclient connection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies parameter changes by introducing priority values as a new parameter for service instances. This numerical parameter allows clients to quickly compare and select service instances based on predefined criteria, transforming the selection process from an unguided search to a parameter-driven decision that reduces connection time while maintaining multiple instances for availability

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If service instances are distributed across multiple domains, then network coverage improves, but determining the preferred instance becomes more complex

Engineering Contradiction:
Improvenetwork coverageVSAvoidservice instance selection
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent uses the directory service as an intermediary that centralizes the management of service instance information across multiple domains. Clients query the directory which returns pre-organized service instance data with priorities and domain information, simplifying the selection process despite the distributed nature of the service instances across multiple domains

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7496566B2Priority based LDAP service publication mechanism
Publication Date: 2009.02.24 MAPLEBEAR INC
  • US7496566B2 patent drawing
  • US7496566B2 patent drawing
  • US7496566B2 patent drawing

AI summary

A method and system are provided for directing a client to a preferred service instance. At creation of a service instance, the service binding attribute of the created instance is extended to include assigned domains and associated priorities. There are then two phases to directing a client to the preferred service instance. The first phase is compilation of a list of domains and priorities for the service in response to a query. Upon completion of the first phase, a second phase is executed to determine a preferred service for the client by comparing fully qualified domain name entries and assigned priority entries.