Enterprise Software Store Architecture for Centralized Licensing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current online software distribution platforms face challenges such as overwhelming customers with numerous software options, lack of enterprise-focused solutions, unregulated software purchases, complex approval processes, and revenue losses due to piracy, particularly in the enterprise market where bulk purchases and productivity applications are prioritized.
Innovation Solution
A software distribution architecture that receives requests from enterprise-associated users, determines their identity, and selects software options based on pre-approved, context-specific, or policy-compliant choices, facilitating centralized billing, licensing, and approval processes to ensure compliance with enterprise rules and reduce piracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a customer accesses an online store, then the customer can browse software applications, but the customer can be overwhelmed by the number of software applications available for purchase
Solution Approach 1:
The patent segments the software catalog into enterprise-specific categories and pre-approved selections. Instead of presenting all available software to every user, the system divides the catalog into relevant subsets based on enterprise identity, department, and user role, making the selection process manageable while maintaining access to diverse software options.
Solution Approach 2:
The system performs preliminary actions by pre-approving and pre-configuring software selections for different enterprises before users access the store. Enterprise administrators can pre-approve software in advance, and the system automatically presents only pre-approved options to users, eliminating the need for users to navigate through all possible software applications.
2Adaptability or versatility
If multiple customers from an enterprise buy applications, then the enterprise can access needed software, but a very large number of accounts are created for differing members of a single enterprise
Solution Approach 1:
The patent implements a universal enterprise account structure where a single enterprise account can be shared by multiple members. The system distinguishes between enterprise-level accounts and individual user credentials, allowing multiple users to access software through one centralized enterprise account while maintaining individual user profiles for tracking and management purposes.
Solution Approach 2:
The system introduces an intermediary enterprise account layer between individual users and the software catalog. This intermediary account manages software licenses and permissions centrally, allowing multiple users to access software without each user needing a separate purchasing account. The enterprise account acts as a mediator that handles billing, licensing, and approval workflows.
3Adaptability or versatility
If any application can be purchased and downloaded by a requesting enterprise customer, then software availability is maximized, but purchases are made without regard to the rules of the enterprise
Solution Approach 1:
The system performs preliminary approval actions where enterprise administrators pre-approve specific software applications before they can be purchased by enterprise members. The pre-approval process ensures that only software compliant with enterprise policies, security requirements, and budget constraints is made available in the store, while still allowing broad software selection within those constraints.
Solution Approach 2:
The system implements feedback loops where software purchases are monitored and validated against enterprise rules. When a user attempts to purchase software, the system checks enterprise policies, licensing agreements, and approval status, providing feedback to either allow or block the transaction. This ensures policy compliance while maintaining software availability through automated enforcement.
4Productivity
If the enterprise focuses on productivity enhancing applications, then business value is maximized, but the consumer-market model with discretionary funds is inappropriate
Solution Approach 1:
The patent implements local quality by providing different purchase models and software catalogs for different enterprise contexts. Instead of a single consumer-market model, the system tailors the software store experience to each enterprise's specific needs, priorities, and purchasing patterns. Enterprise-focused applications receive priority visibility and streamlined approval processes, while discretionary consumer applications are secondary.
Solution Approach 2:
The system changes key parameters of the purchase model based on enterprise identity. For enterprise customers, the system enables bulk purchasing, centralized billing, and productivity-focused software prioritization. For individual consumers, the system maintains the traditional discretionary purchase model. This parameter changing allows the same platform to serve both enterprise and consumer markets with appropriate models for each.
5Reliability
If a complex application approval process is used, then software security is improved, but the approval process is not policy-based or centrally coordinated
Solution Approach 1:
The patent introduces a centralized approval intermediary system that manages software purchase approvals. Instead of ad-hoc complex approval processes, the system implements a policy-based approval workflow where pre-defined rules and enterprise policies automatically guide the approval process. The intermediary system coordinates approvals across different enterprise departments and maintains centralized control while streamlining the process through automation.
Solution Approach 2:
The system changes the approval process from a complex manual workflow to a policy-based automated system. By transforming approval criteria into enforceable policy parameters, the system maintains security and control while reducing complexity. The automated policy enforcement replaces manual coordination steps, making the approval process both secure and manageable.
Data Source
AI summary
The present invention is directed to a software distribution architecture in which a software vendor provides a software store that is coordinated with the unique requirements of a software purchasing enterprise. Examples of the requirements include the enterprise infrastructure, information technology requirements and/or approval, account billing, and other attributes.