Opened the wrong way — this page has no styling and no images.
Image and stylesheet paths are resolved from the site root (/assets/…), so opening the file directly resolves them to C:\assets\… and nothing loads.
To see it properly: unzip 2_双击进后台改字_仅Windows.zip and double-click 启动后台.bat — the browser then shows the full site with styling, images and the ZH/EN switch.
(This zip is a plain static preview: opened directly it shows one page at a time, without styles, images or the language switch.)
Once uploaded it works normally: live traffic arrives over http, not by double-clicking a file.
This notice only appears when the file is opened locally; online visitors never see it.
ProductsWireless access & coverageSwitching & data centerOptical access & transportOptics & cabling
ServicesManaged NOCImplementation & deliverySpare parts & maintenanceAdvisory & architecture
SolutionsManaged network operations & NOCCampus & wireless coverageCloud-network branchesSecurity & compliance
Case studiesScale · managed operationsSpeed · bulk migrationContinuity · legacy retrofitTechnical notes
About usCompany profileCertificationsOffices & contactTechnical notes
Resources & contactTechnical notesFAQDelivery processPricingPrivacy & termsContact usOffice address
Solutions / Cloud-networked branches

Multi-site branch networking: 800+ sites, delivered to a standard

Banks, retail chains, government service halls — many sites, scattered, and trading cannot stop. We turn the branch into a standardized product managed from the cloud, so one site at a time becomes a production line.

30 days
Province-wide rollout
800+
Sites covered
1.5 hours
Per-site install
15+
Parallel crews

Three bottlenecks in multi-site work

Building one site is easy. Copying it eight hundred times without errors, without closing the doors, and in a way that can be signed off — that is the work.

01

Boxes stacked, configs drifting

A traditional branch needs five boxes — router, firewall, switch, APs, PBX — each configured on its own. The more sites, the worse the configuration drift.

02

Ageing voice systems

Legacy PBX lines are worn, mostly analogue handsets, they cannot reach the head-office directory or the contact center, and they are expensive to keep.

03

Invisible and unmanageable

Hundreds of scattered sites with no single view. Faults arrive by phone and diagnosis means driving there.

The common answer: move the complexity off each site and into the cloud.

Architecture: a lean site, controlled centrally

At the site

One gateway, four jobs

A converged gateway combines routing, next-generation firewall, PoE switching and IPSec VPN, with APs and IP phones behind it. Five boxes become two.

In the cloud

Control moves to the cloud

A cloud controller manages every AP in the province, pushing configuration in seconds and upgrading firmware in bulk; cloud IP PBX makes inter-site calls free and ties into head-office systems; the audit and authentication platform meets log-retention and real-name requirements.

Interconnect

All traffic backhauled encrypted

Audit and authentication data return to the cloud over IPSec VPN tunnels, end-to-end encrypted, meeting financial-sector data requirements.

Management

One view of the province

Device state, signal quality, throughput and alarms for every site in one place, filterable by district or batch.

Delivery: a standard process

01

Stock ahead of time

Sourcing starts the day the contract is won: material is packed per site by AP count and labeled with the site name, so a crew installs the moment it arrives.

02

Pre-loaded templates

Every gateway and AP ships with a base template; on site you only cable and power up, and the device pulls its own configuration from the cloud.

03

Nights, in parallel by district

Work runs from 20:00 to 06:00, with fifteen crews moving district by district in parallel. The doors open as usual.

04

Digital acceptance

No paper spot checks. The platform generates a heat map and a device health report per site, so acceptance happens at completion and passes on the spot.

The result: 30 days, 800+ sites

A branch refresh for a leading bank across Guangdong. The estate was old, voice was analogue and nothing was centrally managed; the requirement was no interruption to business, no site left overnight.

30 days
Province-wide delivery
800+
Sites live
1.5 hours
Per site (was 4 hours)

Acceptance produced 800 individual heat maps and device health reports; management can see the live state of any branch from their desks.

Read the full post-mortem →

Where it fits: and where it does not

FitsDoes not fit
Twenty sites or more, all much the same shapeA handful of sites, each with a completely different network
Head office needs one view of every store and siteEach site has its own IT team and will not hand over control
Fixed trading hours that allow night work24/7 operation with no window for downtime at all
Voice over IP or multi-site networking is neededYou only want to buy equipment, not manage it centrally
Clear audit requirements (finance, government, healthcare)The budget covers hardware only, not installation or operations

Stating the boundary is more useful than claiming everything. If the right-hand column applies, we say so up front instead of taking the work and improvising.

How we start

STEP 1

Three representative sites as a pilot

The cheapest way to prove the architecture, the build process and the acceptance criteria — then the volume conversation runs on measured data.

STEP 2

Templates and batches

Equipment list, configuration templates, packing rules, working hours and district sequence become a work instruction anyone can repeat.

STEP 3

Batch by batch, accepted batch by batch

Delivered by district; each batch ends with an acceptance report and a review, and the fixes land before the next batch.

Pilot three sites first, and let the measurements speak.

Talk to us about multi-site delivery →