Network Access Request Control via Multi-Layer Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network access request control methods for large e-commerce websites are inefficient due to lack of uniformity in traffic control across subsystems, leading to reliability issues and conflicts, especially during high traffic bursts, as they fail to differentiate between types of access requests and apply non-directed, coarse-grained control measures.
Innovation Solution
A system that identifies and categorizes network access requests as user, crawler, or invalid requests, applying specific traffic flow control schemes across different layers of a distributed system, including DNS, web server, and application layers, dynamically adjusting throttling policies to ensure stability and reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If overall traffic is limited at entry to manage burst traffic, then system stability is improved, but control granularity becomes too coarse and cannot be directed to specific services
Solution Approach 1:
The patent segments traffic control into multiple layers (entry layer, service layer, and subsystem layer) and divides control authority among different components. The entry application is segmented into multiple service modules, each with independent control capabilities. This allows fine-grained control at the service level while maintaining overall system stability through coordinated multi-layer control.
Solution Approach 2:
The patent introduces a new dimension of control by implementing vertical multi-layer control architecture. Instead of single-dimensional entry-level control, it adds service layer and subsystem layer control dimensions, enabling three-dimensional traffic management that simultaneously achieves coarse-grained stability control and fine-grained service-level directionality.
2Reliability
If different subsystems apply their own respective methods to control access, then each subsystem's reliability is improved, but conflicts arise between protective measures and uniformity is lost
Solution Approach 1:
The patent implements a unified multi-functional control framework that serves multiple subsystems simultaneously. The control system provides universal access control, authentication, and traffic management functions across all subsystems through standardized interfaces and protocols, ensuring consistent behavior while allowing each subsystem to maintain its reliability characteristics.
Solution Approach 2:
The patent introduces an intermediary control layer between individual subsystems and the entry point. This intermediary coordination mechanism mediates between different subsystem protective measures, resolves conflicts, and ensures uniform system-wide control policies are applied while preserving individual subsystem reliability.
3Adaptability or versatility
If entry application provides many services simultaneously, then service versatility is improved, but traffic control becomes non-uniform and difficult to direct
Solution Approach 1:
The patent segments the entry application into distinct service modules, each handling specific traffic types or functions. This segmentation allows independent control policies for each service module, simplifying traffic control complexity while maintaining the ability to provide multiple services simultaneously. Each module can be configured with specific control parameters appropriate to its function.
Data Source
AI summary
Embodiments of the present application provide a method and system for network access request control. During operation, the system may identify a network access request received by a website. The system may determine a type of the network access request, and control the network access request according to the type of the network access request. The type of the network access request can be one of a user access request, a crawler access request, or an invalid access request. Based on the type of the network access request and/or the access requests overall compared to a cluster stability threshold, the system may take measures to throttle the access requests or otherwise adjust a throttling policy. The system may take measures such as demoting a service to a lower priority, rejecting execution of an access request, redirecting an access request to another service cluster, and expanding a physical layer of a service cluster.