Electronic Software Delivery System Customer-Specific Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current digital distribution systems are unable to efficiently limit the distribution of software product updates, such as emergency bug fixes and patches, to specific customers without compromising security or requiring extensive system configuration and IT resource involvement.

Innovation Solution

A method and apparatus within an electronic software delivery and management system that allows manufacturers to store and restrict access to data objects or files, enabling selective customer access by inputting restriction parameters and storing customer-specific information in a database, allowing only authorized customers to download specific data objects or files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If direct server access is used to deliver bug fixes and patches, then delivery efficiency is improved, but system security is compromised due to exposure to external users

Engineering Contradiction:
Improvedelivery efficiencyVSAvoidsecurity risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary mechanism between the manufacturer and customer servers. Instead of direct access, the system uses a controlled interface where the manufacturer can initiate updates and the system automatically manages the delivery process. This intermediary layer maintains security by preventing direct exposure of customer systems while still enabling efficient update delivery.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If FTP server with password protection is used, then access security is improved, but system complexity increases requiring IT administrator intervention for account management

Engineering Contradiction:
Improveaccess securityVSAvoidaccount management complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The system implements self-service functionality where customer-specific data objects are automatically delivered to entitled customers without requiring manual account creation or configuration. The system automatically manages access rights, delivers appropriate files, and handles updates without IT administrator intervention, eliminating the complexity of traditional FTP account management while maintaining security.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If anonymous FTP is used for file distribution, then ease of access is improved, but file availability control is lost to target customers

Engineering Contradiction:
Improveaccess easeVSAvoidfile availability control
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments the file distribution system into customer-specific delivery streams. Instead of a single anonymous FTP access point, the system divides file availability into distinct, customer-specific channels. Each customer receives only their entitled files through automated delivery, maintaining both ease of access (automatic delivery) and file availability control (customer-specific restrictions).

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8271387B2Method and apparatus for providing limited access to data objects or files within an electronic software delivery and management system
Publication Date: 2012.09.18 FLEXERA SOFTWARE LLC
  • US8271387B2 patent drawing
  • US8271387B2 patent drawing
  • US8271387B2 patent drawing

AI summary

A method and apparatus for providing limited access to data objects or files within an electronic software delivery and management system are described. A data object is transmitted to the system for storage in a library. Input of one or more restriction parameters is further requested for the stored data object. A user interface is displayed in a display window for facilitating input of the restriction parameters. At least one customer is selected, such as, for example, one or more users authorized to receive the stored data object. The stored data object is further designated as restricted data object for the selected users. Finally, the user restriction information is stored in appropriate tables within a database.