Self-Service Device Integration for NAC Servers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network access control (NAC) server integration of network devices is complex and labor-intensive, requiring skilled engineers for manual device mapping and configuration, which is time-consuming and unmanageable in larger environments, often necessitating physical engineer presence for proof of concept and new installations.

Innovation Solution

A self-service device integration system for NAC servers that maintains a device database with mappings of system object identifiers to implementation details, allowing users to select candidate devices and map implementation details for access, reducing the need for manual property file modifications and skilled engineer assistance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual device mapping and configuration is performed by skilled engineers, then device integration accuracy is improved, but integration time and labor cost increase significantly

Engineering Contradiction:
Improvedevice integration accuracyVSAvoidintegration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system enables non-engineer users to perform device integration themselves through an automated workflow. The NAC server automatically discovers devices, retrieves their system object identifiers, queries the device database for mappings, and guides users through selection and verification processes without requiring manual property file modifications or deep technical expertise.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The device database is pre-populated with mappings between system object identifiers and implementation details before integration is needed. This preliminary preparation allows the system to quickly match discovered devices with appropriate configurations, eliminating the need for engineers to create mappings during the integration process.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If manual device mapping is performed, then device-specific configuration accuracy is improved, but complexity of the integration process increases

Engineering Contradiction:
Improvedevice configuration accuracyVSAvoidintegration process complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The device database acts as an intermediary layer between the NAC server and diverse network devices. It stores pre-configured mappings that translate between generic system object identifiers and device-specific implementation details, allowing the NAC server to manage devices without directly handling device-specific complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system copies proven device mappings from the database for similar device types. When a device is discovered, the system retrieves an existing mapping template that can be applied to the new device, ensuring consistent configuration accuracy while simplifying the integration process through reuse of established patterns.

Inventive Principle:
Principle #26Copying

3Reliability

If skilled engineers are required for device integration, then integration reliability is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveintegration reliabilityVSAvoidease of device integration
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system empowers end-users to perform device integration independently through automated discovery and guided selection processes. The NAC server handles technical complexities automatically, including device discovery, identifier retrieval, database querying, and mapping application, while users only need to follow simple interface prompts.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides feedback mechanisms during the integration process, including displaying discovered device information, showing available mappings from the database, and allowing users to verify selections before finalization. This feedback loop ensures integration reliability by confirming each step while maintaining ease of operation through clear user guidance.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If comprehensive device mappings are maintained in a database, then adaptability to different devices is improved, but system complexity increases

Engineering Contradiction:
Improvedevice compatibilityVSAvoiddatabase management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The device database serves multiple functions: storing system object identifier mappings, providing device discovery support, guiding user selection, and enabling automated configuration. This universal approach allows a single database structure to handle diverse device types while maintaining adaptability without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11470083B2Device integration for a network access control server based on device mappings and testing verification
Publication Date: 2022.10.11 FORTINET INC
  • US11470083B2 patent drawing
  • US11470083B2 patent drawing
  • US11470083B2 patent drawing

AI summary

Systems and methods for facilitating self-service device integration for a NAC server is provided. According to one embodiment, a database is maintained by a NAC server. The database includes mappings of system object identifiers to corresponding implementation details of associated devices. A system object identifier of a device that is to be modeled within the NAC server based on implementation details of another device is received. A list of candidate devices is retrieved from the database based on the system object identifier. A user of the NAC server is prompted to select a candidate device from the list. Responsive to receipt of the selected candidate device, implementation details of the selected candidate device are mapped against the system object identifier and access to the network device is facilitated based on the implementation details of the selected candidate device by storing the mapping as an entry in the device database.