Application Traffic Scheduling via Pre-deployed Area Mapping

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current traffic scheduling methods for applications are inadequate when user account data and service data are attributed to different areas, leading to inefficient scheduling and potential misrouting of service traffic, especially when the default domain name and service area do not match.

Innovation Solution

Implementing a traffic scheduling method within an application that determines the correct server by mapping registration areas to domain names, allowing for accurate scheduling of service traffic to the appropriate server without relying on network requests, by using a pre-deployed mapping relationship between registration areas and domain names.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the default domain name is used for traffic scheduling, then the scheduling process is simple, but the service traffic may be routed to the wrong server when the default domain name and service area do not match

Engineering Contradiction:

Improvescheduling process simplicityVSAvoidtraffic routing accuracy

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent pre-deploys a mapping relationship between registration areas and domain names within the application before the application runs. When the application needs to schedule traffic, it directly uses this pre-established mapping to determine the correct domain name based on the service's registration area, eliminating the need for runtime network requests and ensuring accurate routing from the outset.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that sits between the service's registration area and the domain name resolution process. This mapping relationship acts as a mediator that translates the service's registration area into the correct domain name, ensuring that traffic is routed to the appropriate server even when the default domain name would be incorrect.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If network requests are used to determine the correct server, then the routing accuracy can be improved, but the scheduling efficiency and response time deteriorate

Engineering Contradiction:

Improverouting accuracyVSAvoidscheduling efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent performs the domain name mapping determination in advance by pre-deploying the mapping relationship within the application. When traffic scheduling is needed, the application directly queries the pre-existing mapping based on the service's registration area, eliminating the need for runtime network requests and achieving both high accuracy and high efficiency.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The application becomes self-sufficient by having the mapping relationship deployed within it. The application can independently determine the correct domain name using its internal mapping data without needing to external network requests, thereby improving both routing accuracy and scheduling efficiency.

Inventive Principle:

Principle #25Self-service

3Device complexity

If the registration area tag is used to schedule user traffic, then the implementation is simple, but the scheduling is inaccurate when user account data and service data are in different areas

Engineering Contradiction:

Improveimplementation complexityVSAvoidscheduling accuracy

Core Design Contradiction:

Device complexityVSMeasurement precision

Solution Approach 1:

The patent pre-deploys a comprehensive mapping relationship within the application that accounts for the relationship between user account registration areas and service registration areas. This advance preparation enables the application to accurately determine the correct domain name based on the service's registration area without requiring complex runtime calculations or network requests.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that resolves the discrepancy between user account registration areas and service registration areas. This mapping acts as a mediator that translates the service's registration area into the correct domain name, ensuring accurate routing even when the user's account area and the service's area differ.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250007876A1Traffic scheduling method of application and apparatus, device and storage medium

Publication Date: 2025.01.02 BEIJING YOUZHUJU NETWORK TECH CO LTD

AI summary

The present disclosure relates to the field of computer technology, and discloses a traffic scheduling method and apparatus of an application, a device and a storage medium. The method comprises: obtaining a first registration area of a target service of the application and a second registration area where an account of a target object is located; detecting whether the first registration area is the same as the second registration area; when the first registration area is not the same as the second registration area, determining a target domain name corresponding to the first registration area based on a mapping relationship between the first registration area and a domain name, the mapping relationship being deployed in the application; and scheduling service traffic generated by the target service to a target server corresponding to the target domain name information.