Secure Software Download via Multi-Server Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software component download methods are insecure and require a Google account, making them unsuitable for secure deployment within company networks and incompatible with certain use cases.
Innovation Solution
A method involving multiple distribution servers with varying security levels, where the first application connects securely to a second distribution server with authentication and cryptographic protection, and the second application connects securely to a third distribution server for software component download, ensuring high-security authentication and data protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a public server or Google Play system is used for downloading software components, then the download process is simple and accessible, but the security is compromised and communication can be corrupted
Solution Approach 1:
The system segments the download process into multiple phases: initial application download from public server, then secure connection establishment to dedicated server, followed by authenticated software component download. This segmentation allows the system to benefit from both public server accessibility and dedicated server security without requiring the entire process to use one approach.
Solution Approach 2:
The first application acts as an intermediary between the user device and the dedicated server. It establishes the secure connection and authentication mechanism, enabling subsequent secure downloads without requiring the user to directly interact with complex security protocols. The intermediary handles the security-sensitive operations while maintaining ease of use.
2Ease of manufacture
If a Google account is required for downloading the first application, then the download process is standardized, but compatibility with company computer park deployments is lost
Solution Approach 1:
The system dynamically adapts the authentication mechanism based on the deployment context. In public scenarios, Google account authentication is used for standardization. In company computer park scenarios, the system can switch to alternative authentication methods or pre-configured credentials, allowing the same download infrastructure to serve multiple deployment models without requiring Google accounts.
Solution Approach 2:
The authentication parameters are made configurable rather than fixed. The system can change authentication credentials, server endpoints, and security protocols based on deployment requirements. This parameter flexibility allows the same software distribution infrastructure to accommodate both consumer Google Play deployments and enterprise computer park deployments with different security and authentication requirements.
3Reliability
If multiple distribution servers with varying security levels are used, then security is enhanced through multiple authentication layers, but the system complexity increases
Solution Approach 1:
The distribution system is segmented into multiple servers with different security levels, each handling specific functions. The first server handles initial application distribution with lower security requirements, while the second server handles authenticated software component downloads with higher security. This functional segmentation allows complexity to be distributed and managed separately rather than concentrated in a single system.
Solution Approach 2:
The system performs preliminary authentication and connection establishment through the first application before accessing the secure second server. This preliminary action creates a trusted context that simplifies subsequent secure communications. The authentication framework is established in advance, so that when software components need to be downloaded from the second server, the security infrastructure is already in place and operational.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention relates to a method for downloading at least one software component onto a computing device, such as a mobile telephone, said method being implemented by the computing device comprising an information processing unit comprising a memory. The downloading method comprises downloading (205) a first application (L1) onto the memory from a first distribution means (S1), and connection (220), via the first application (L1), to a second distribution means (S2). The connection (220) to the second distribution means (S2) is carried out securely by means of an authentication code (D2), and the downloading method also comprises: downloading (235) a second application (L2) onto the memory from the second distribution means (S2); connection (255, 275), via the second application (L2) and in a secure manner, to a third distribution means (S3); and downloading (265, 285) the or each software component onto the memory from the third distribution means (S3).