Automated API Generation for Mobile-Enterprise Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise systems are not easily integrated with mobile applications, requiring significant time and resources to develop software and APIs for mobile devices to access and interact with mainframe or enterprise systems, leading to unsustainable one-off solutions.
Innovation Solution
A method and system that automatically generates APIs, connections, and code for mobile applications to interface with mainframe/enterprise systems using preconstructed computer code sets and domain models, enabling effortless and secure connectivity between mobile devices and legacy systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual software development is used to integrate mobile applications with enterprise systems, then integration functionality can be achieved, but development time and resources increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-defining integration patterns, data models, and connection templates for common enterprise systems before actual mobile app development begins. These pre-configured elements can be automatically instantiated and customized, eliminating the need to build integration logic from scratch for each new mobile application.
Solution Approach 2:
The patent introduces an intermediary integration layer that sits between mobile applications and enterprise systems. This mediator handles the complexity of system-specific protocols, data formats, and authentication mechanisms, allowing mobile developers to work with simplified, standardized interfaces while the intermediary manages the actual integration complexity.
2Adaptability or versatility
If custom software development is performed for each mobile application, then specific functionality can be implemented, but resource investment and costs increase
Solution Approach 1:
The patent implements universality by creating a platform that provides common integration capabilities, authentication mechanisms, and data access patterns that can be reused across multiple mobile applications. Instead of building separate integration solutions for each app, the platform offers standardized interfaces and pre-configured connectors that serve multiple applications simultaneously.
Solution Approach 2:
The patent applies segmentation by separating the integration logic into modular, reusable components that can be independently configured and assembled. The integration platform divides complex enterprise system connections into discrete, manageable units such as data connectors, authentication modules, and API wrappers, which can be selectively applied to different mobile applications based on their specific needs.
3Manufacturing precision
If extensive manual analysis and configuration is performed, then integration accuracy and security can be ensured, but development complexity and time increase
Solution Approach 1:
The patent applies self-service by enabling automated configuration and validation of integration settings. The platform includes self-documenting interfaces that automatically generate API specifications, data models, and connection configurations based on the selected enterprise system and mobile app requirements. Security policies and authentication methods are automatically configured and validated, reducing manual analysis while maintaining accuracy.
Solution Approach 2:
The patent implements feedback mechanisms that automatically validate integration configurations, data mappings, and security settings during the setup process. The system provides real-time feedback on configuration correctness, potential security issues, and compatibility problems, allowing developers to correct errors immediately rather than discovering them during testing or production.
Data Source
AI summary
The present invention provides a system and method for constructing a complete definition of a backend requirements model that can be automatically accessed and interpreted, and generated into a mobile consumable API for creation of, and use with, mobile applications. The mobile consumable API can be provided and made available to mobile app developers on a separate, stand-alone platform, and may act as an intermediary between the mobile app and the primary mainframe/enterprise/back end system. The method may include identification and definition of one or more of information providers, integration providers, and system behaviors, and creating a domain model. The domain model may be automatically codified into an API based solution as the app/mainframe interface, and stored on a development and operational platform for use.