Enterprise Application Identifier Tag Files for Software Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional software discovery techniques fail to identify software based on enterprise-specific information, leading to inefficient discovery processes and resource utilization, as they rely on vendor-specific hashcodes or application fingerprints that do not include enterprise details.

Innovation Solution

The creation and deployment of enterprise-specific application identifier tag files, which include unique enterprise information, allow for the discovery of applications by associating these tags with application files, enabling identification of server locations and maintenance entities within the enterprise environment, even across different vendors and operating systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If vendor-specific discovery tools are used, then software can be discovered using proprietary identifiers, but enterprise-specific information cannot be identified

Engineering Contradiction:
Improvesoftware identification accuracyVSAvoidenterprise-specific information
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent introduces an intermediary component - the enterprise information file - that mediates between the vendor-specific application identifier and the enterprise-specific deployment information. This file contains enterprise-specific identifiers and mappings that enable discovery tools to connect vendor identifiers with enterprise context, thereby resolving the contradiction between using proprietary identifiers and accessing enterprise-specific information

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The solution segments the identification system into multiple independent components: vendor-specific identifiers, enterprise-specific identifiers, and mapping relationships stored in the enterprise information file. This segmentation allows each component to maintain its own specificity while enabling cross-referencing, thus preserving both vendor identification accuracy and enterprise information accessibility

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple vendor-specific identifiers are used, then software from different vendors can be identified, but a unified enterprise-wide discovery mechanism is lacking

Engineering Contradiction:
Improvemulti-vendor compatibilityVSAvoiddiscovery system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The enterprise information file serves as a universal interface that works with identifiers from multiple vendors. It provides a standardized structure for storing enterprise-specific information that can map to various vendor identifier formats, enabling a single discovery mechanism to handle multiple vendors without requiring separate tools for each vendor

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

Solution Approach 2:

The enterprise information file acts as a mediator layer between diverse vendor-specific identifier systems and the enterprise's unified discovery requirements. By storing mapping relationships and enterprise context in this intermediate file, the system achieves multi-vendor compatibility while maintaining a consistent discovery approach across the enterprise

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10572449B2Systems, devices, and methods for software discovery using application ID tags
Publication Date: 2020.02.25 WALMART APOLLO LLC
  • US10572449B2 patent drawing
  • US10572449B2 patent drawing
  • US10572449B2 patent drawing

AI summary

Provided herein are methodologies, systems, and devices for facilitating software discovery within a server environment using an enterprise-specific application identifier tag file. Such enterprise-specific application identifier tag files can be created for applications from various vendors and can include enterprise-specific information not known to an application vendor. Once created, the enterprise-specific application identifier tag file is deployed within the server environment, and may be saved on a database associated with the server environment. The application identifier tag files can include a link to their corresponding application files and can facilitate in application/software discovery by allowing a user to determine application information by performing an enterprise-specific application identifier tag file query.