CCN CROSS-BORDER BANDWIDTH

Compare Direct and routed ACK paths.

Compare a Public Internet Direct baseline with a configured Guangzhou ingress → Guangzhou ↔ Silicon Valley CCN → Silicon Valley private-origin Command-to-ACK path.

CNChina Mainland
Client

01Guangzhou
Ingress

02CCN Cross-Border
Bandwidth

03Silicon Valley
Private Origin

USSame US
Origin

What this demo proves: the operating model and a fair test method — not a performance claim.

ARCHITECTURE WALKTHROUGH

No live Direct endpoint is configured. This page is currently an architecture walkthrough.

Choose the path to inspect.

Both paths must reach the same US origin. The difference is the cross-border path being evaluated.

LIVE PATH WALKTHROUGH

Current: CCN Cross-Border Bandwidth Path

CCN PATH

A designed logical path: China Mainland ingress, CCN Cross-Border Bandwidth, and US egress to the Same US Origin. All states for this path are simulated in this deliverable.

Client

China Mainland

Guangzhou

Ingress EIP + CVM

CCN Bandwidth

Guangzhou ↔ Silicon Valley

Silicon Valley

Private-origin VPC

Same US Origin

ACK target

SIMULATEDPath ready: send a game command to display the simulated Command-to-ACK return state.

COMMAND-TO-ACK TEST

Send a test command.

01/ 10

SOURCE-LABELED ACK LIFECYCLE

Path ready

Send a command through the selected path. A real sample is recorded only when the configured endpoint returns a matching ACK.

POC SUCCESS METHOD

Keep the comparison fair.

Same clientSame US originSame payloadTwo endpointsCompare raw ACK records