Baidu AI Cloud Public Sector China Translated from Chinese

Guiyang Public Security Traffic Management Bureau (贵阳市公安交通管理局)

Real-time Analytics

Guiyang needed a more systematic way to reduce congestion in a mountainous city where road geometry, rapid growth, and fragmented traffic-management methods made it hard to optimize signal timing and respond to changing traffic conditions.

Average vehicle delay at target intersections fell 15%.
Citywide indicators are monitored at 5-minute granularity.
The deployment covers 31 key intersections.

Reported impact

Business outcome

Guiyang improved traffic-flow visibility, reduced intersection delay, and gained a reusable operating pattern for AI-assisted congestion control in a road network with severe physical constraints.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

Baidu AI Cloud and Guiyang's traffic-management bureau deployed an AI traffic-signal optimization system for thirty-one key intersections in the city's Guanshanhu core district. The solution combines roadside radar-and-vision integrated sensing devices with Baidu Maps traffic indicators to create a continuous picture of road-network conditions, congestion events, flow levels, and intersection performance. Those inputs feed an AI signal-control large model that generates signal-timing plans for peak, off-peak, and night conditions and updates them dynamically as traffic changes. The system also exposes a monitoring screen that shows macro congestion indicators, citywide five-minute traffic trends, and micro-level alerts for specific intersections or corridors. In practice, the deployment links sensing, diagnosis, timing-plan generation, and operational monitoring in one workflow so traffic managers can move from reactive adjustments to data-driven optimization and earlier intervention.

Data flow

Roadside radar-vision devices and Baidu Maps traffic indicators feed real-time data into the congestion-analysis layer, which diagnoses flow, incidents, and road-network conditions. The traffic-control large model then generates timing schemes for each period and state, and the resulting plans are monitored and refined through dashboards that expose macro, corridor, and single-intersection performance.

Solution architecture

4 components · 3 layers
  1. Ingest
    • Radar-Vision Integrated Sensor Captures real-time roadside flow data that is fused with map indicators to diagnose congestion causes.
  2. Compute
    • Qianfan Model Development Platform Supports the development and optimization of the traffic-signal large model used in Guiyang's congestion program.
    • AI Traffic Signal Control Large Model Generates signal-timing plans for different traffic states and adjusts them dynamically based on congestion conditions.
  3. Serving
    • Qianfan Application Development Platform Packages the operational application used to monitor conditions and distribute optimized signal plans.

Architecture clues

  • The operational dashboard spans macro city metrics, corridor analysis, and micro intersection alerts.
  • The system fuses roadside sensing with map-derived traffic indicators instead of relying on one data source.
  • Timing plans are generated for multiple periods such as peak, off-peak, and night conditions.

Evidence from the source

Average vehicle delay at intersections was reduced by 15% (original: 路口车均延误下降15%).
Roadside radar-vision sensing is fused with Baidu Maps traffic indicators to analyze traffic conditions comprehensively (original: 通过外场雷视一体机感知获取实时车流量数据,融合百度地图交通指标数据,全面分析31个路口的交通通行情况).
The large model generates timing plans for different periods and conditions so signal timing can be tuned automatically (original: 基于交通信控大模型智能匹配生成不同时段,不同状态的信号灯配时方案,实现信号配时的自动调优).
The project used an AI signal-control large model and radar-vision integrated sensing to optimize signals at 31 key intersections in Guanshanhu District (original: 基于AI信控大模型和雷视融合感知技术,在观山湖区31个重点路口实现信号灯智能调优).
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Baidu AI Cloud

    Guiyang Public Security Traffic Management Bureau (贵阳市公安交通管理局) customer story

    First-party
    https://cloud.baidu.com/customer/case/guiyangjiaotong.html
    Source type
    Vendor-published customer story
    Published
    Oct 12, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Oct 12, 2025 · Baidu AI Cloud · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.