Both of the scenarios above require the configuration for vehicle-mounted and trackside APs. The differences between the configurations are listed in Table 1.
Vehicle-mounted APs support the configuration for scenario 2 from V200R009.
Task |
Description |
Configuration Difference Between Scenarios 1 and 2 |
|---|---|---|
Configure vehicle-mounted APs. |
||
| Configuring Mesh Radio Parameters | Configure the same channel and bandwidth for both the vehicle-mounted and trackside APs. |
In scenario 1, configure only one working channel for radios on a vehicle-mounted AP. In scenario 2, configure different working channels for radios on a vehicle-mounted AP, which map working channels of trackside APs on different lines. |
| Configuring a Security Profile | Configure a security profile and a security policy to improve Mesh security. |
In scenario 1, configure only one security profile for a vehicle-mounted AP. In scenario 2, configure multiple security profiles for a vehicle-mounted AP to map the Mesh networks where trackside APs on different lines reside. |
| (Optional) Configuring a Mesh Whitelist | Add trackside APs to a Mesh whitelist so that the vehicle-mounted AP can set up Mesh links only with the trackside APs in the whitelist. If the Mesh whitelist is not configured, vehicle-mounted APs can set up Mesh links with all trackside APs. |
The Mesh whitelist is not recommended in scenarios 1 and 2. If a Mesh whitelist is configured:
|
| Configuring Train-Ground Communication (For Vehicle-Mounted APs in V200R007 or Later) | Configure the vehicle-ground communication mode based on site requirements. |
No difference |
| Configuring a Mesh Profile | Configure Mesh profile parameters to generate a Mesh VAP for setting up links with trackside APs. |
In scenario 1, configure only one Mesh profile for a vehicle-mounted AP, set the Mesh ID, and bind the Mesh profile to the security profile. In scenario 2, configure multiple Mesh profiles for a vehicle-mounted AP, set different Mesh IDs, and bind the Mesh profiles to the security profiles. |
| Configuring Proxied Ground Devices | Configure proxied ground devices. When a train turns around, data streams sent to the ground network are routed to the vehicle-mounted AP at the front, ensuring normal data transmission. |
No difference |
| Configuring Proxied Vehicle-Mounted Devices | Configure proxied vehicle-mounted devices. When a vehicle-mounted AP connects to a new trackside AP, devices on the ground network can forward data to the vehicle-mounted AP through the new trackside AP. |
No difference |
| Enabling IGMP Snooping on a Vehicle-Mounted AP | Configure uninterrupted multicast services. |
No difference |
Configure trackside APs. |
||
| Adding APs | Add trackside APs to the AC for management. |
No difference |
| Configuring Mesh Radio Parameters | Configure radio parameters for trackside APs. |
No difference |
| Configuring Parameters for an AP's Wired Interface | Configure the wired port of trackside APs to work in root mode, and add the ports to VLANs. |
No difference |
| Configuring a Security Profile | Configure a security profile and a security policy to improve Mesh security. |
No difference |
| Configuring a Mesh Whitelist | Add vehicle-mounted APs to a Mesh whitelist so that the APs can communicate with trackside APs. |
In scenario 1, add vehicle-mounted APs only on a train traveling on the current line to the Mesh whitelist for the current line. In scenario 2, add vehicle-mounted APs on trains traveling on multiple lines to the Mesh whitelist for the current line. |
| Configuring a Mesh Handover Profile | Bind a Mesh profile to a Mesh handover profile to provide the fast link handover function. |
No difference |
| Configuring a Mesh Role and Mesh Profile | Configure trackside APs as MPPs and a vehicle-mounted AP as MPs, and set Mesh profile parameters. |
No difference |
| Guaranteeing Multicast Data Transmission | Configure uninterrupted multicast services. |
No difference |