Natural Language Identity Management Rule to Markup Script

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The development of markup-language (ML) scripts for identity management (IM) policies is tedious and prone to errors, especially when done directly, and using integrated development environments (IDEs) with graphical user interfaces (GUIs) can be unintuitive and time-consuming.

Innovation Solution

A natural language (NL)-based rule script is used to define IM rules, which are then converted into an intermediate object tree (IOT) and subsequently into an ML script, allowing for more intuitive and efficient generation of ML scripts with minimal syntactical constraints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If ML scripts are developed directly or using IDEs with GUIs, then the scripts can be created with proper syntax, but the process becomes tedious and time-consuming

Engineering Contradiction:

Improvescript development speedVSAvoidscript development complexity

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary natural language processing layer between the user and the ML script generation. Users interact through natural language descriptions of IM rules, which are then automatically translated into properly formatted ML scripts, eliminating the need for users to directly write complex markup language while maintaining script correctness

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical process of manually writing and configuring ML scripts through GUIs with an automated natural language processing system. This substitution eliminates tedious manual operations while preserving the ability to generate syntactically correct scripts

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If ML scripts are developed directly, then the scripts can be generated, but errors are more likely to occur

Engineering Contradiction:

Improvescript generation efficiencyVSAvoidscript accuracy

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The natural language processing intermediary automatically translates user intent into syntactically correct ML scripts, eliminating manual syntax errors. The system handles the complex transformation logic, ensuring that generated scripts meet all required formatting and syntax standards without user intervention

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs self-validation and self-correction during the natural language to ML script translation process. The automated generation process inherently ensures syntax correctness and logical consistency, reducing the need for manual error checking and correction

Inventive Principle:

Principle #25Self-service

3Ease of operation

If IDEs with GUIs are used for script development, then the interface provides structure, but the process becomes unintuitive and time-consuming

Engineering Contradiction:

Improveinterface structureVSAvoidscript development time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The patent replaces the multi-step GUI interaction process with a direct natural language processing approach. Users simply describe the IM rule in natural language, and the system automatically generates the complete ML script, eliminating the time-consuming navigation through GUI elements while maintaining operational simplicity

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11321525B2Generation of markup-language script representing identity management rule from natural language-based rule script defining identity management rule

Publication Date: 2022.05.03 MICRO FOCUS LLC

AI summary

A natural language (NL)-based rule script defines an identity management (IM) rule that governs how a driver performs data transformation among sub-systems of an IM system to coordinate user identity and data access across the sub-systems. An intermediate object tree (IOT) for the IM rule defined within the NL-based rule script is generated by parsing conditions and actions of the IM rule specified in the NL-based rule script. A markup-language (ML) script is generated from the IOT of the IM rule. The driver uses the ML script when performing the data transformation among the sub-systems of the IM system to coordinate user identity and data access across the sub-systems.