How can we help?
-
zWAN
-
-
-
-
- Firewall & Layer 7 Application Filtering
- VPN Site-to-Site Tunnel Setup & Connectivity (z40 to Cloud vGR)
- Intrusion Prevention System (IPS) / Intrusion Detection System (IDS) Testing
- DNS Filtering
- DDoS Protection & Logging
- MAC Address Filtering & Geo-fencing
- Application Control & Protocol Blocking
- Authentication & Access Control (zID)
-
- WAN Link Failover & Load Balancing (ACI Mode)
- Dynamic Path Selection & Application-Aware Routing
- SaaS & Internet Breakout Validation
- QoS for Microsoft Teams (Datacenter vGR + Branch z40)
- Tunnel Failover (z40 ↔ vGR) — WAN00 (wired) primary, WAN03 (4G) & WAN04 (5G) backups
- IP Routing & Static Route Steering (z40 Branch)
- VLAN & Layer-2 Bridging
-
-
-
-
-
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- IPsec Tunnel not Establishing
- SSL-VPN Tunnel not Establishing
- Mobile Network Issues
- Management Tunnel does not Establish
- DNS not Resolving from Local Network Appliance
- DNS Resolution Issues in Tunnel Configuration
- DHCP Server not Leasing IP to LAN PC
- Debugging EC Events - Unknown Status Issue
- Trusted-MAC Geofencing Issues
- DNS Issues from DC LAN PC
- Troubleshooting LAN Connectivity to Internet via WAN, Remote Branch LAN, or Local Branch LAN
- NetBalancer gateways displaying Faulty/Inactive
- Packet Drop Issues
-
-
zTC
-
-
-
-
-
- Citrix HDX + USB Headset (Call-Center Baseline)
- VMware Horizon + Smart Card / CAC Login
- Microsoft AVD/RDP + Teams Optimized Video
- Multi-Monitor & 4K Performance
- USB Device Management - Block Storage
- Printing to Local USB & Network Printers
- Barcode Scanner (HID) with Line-of-Business App
- Kiosk / Assigned-Access Auto-Launch
- Wi-Fi Roaming & Link Change Mid-Session
- Power Management and Session State
- OS/Firmware Update & Rollback
-
-
StorTrends
-
zAccess
-
zGuardian
You are here:
Print
Band Locking
0 out Of 5 Stars
| 5 Stars | 0% | |
| 4 Stars | 0% | |
| 3 Stars | 0% | |
| 2 Stars | 0% | |
| 1 Stars | 0% |
Functional Requirements Document (FRD) – Band Locking
Feature: Band Locking Management in zWAN SDWAN CPE
Version: 0.9
1. Objective
To enable control over the modem’s frequency band selection by allowing users to lock the modem to specific bands (LTE/NR/UMTS/GSM) for diagnostic, performance tuning, or compliance reasons.
Band locking improves stability, avoids poor-performing bands, and can aid in testing and carrier certification.
2. Functional Requirements
FR1: Band Listing
- The system must be able to query and list all bands supported by the modem and its current radio technology (e.g., NR5G, LTE, UMTS).
- The supported bands list must include:
- Band number
- Band name (e.g., LTE B3, NR n78)
- Radio Access Technology (RAT)
FR2: Band Lock Configuration
- The system must support user-defined locking to one or more bands for a given RAT.
- Configurable options:
- RAT type (e.g., NR5G, LTE, WCDMA)
- Band numbers to lock (single or multiple)
- Example: Lock to LTE Band 3 and Band 20 only.
- Single band lock (e.g., only Band 3)
- Multiple band lock (e.g., Band 3 + Band 5 + n78)
- Band configuration must persist across reboot.
- Notify user if band locking is unsupported on current hardware/firmware.
FR3: Locking/Unlocking Operation
- The user must be able to:
- Enable band locking with a list of specified bands
- Disable band locking (return to automatic selection)
- Changes must take effect without requiring system reboot, though modem restart may be required.
FR4: Validation & Status
- The system must:
- Validate that specified bands are supported by the modem hardware
- Provide API to query current band lock status
- Report active bands used in current connection (e.g., via
AT+QENG,AT+QNWINFO)
- It must not interfere with normal modem operation when band lock is not active.
FR5: Persistence
- Band locking settings must be stored in a persistent configuration in the database.
- After system or modem reboot, the previous band lock state and settings must be restored.
FR6: Status Display
- The system must provide a status report showing:
- Currently active RAT
- Active band(s)
- Locked bands (if any)
FR7: Event Logging
- All band lock operations (apply, clear, fail) must be logged with timestamps.
- Logs must include success/failure and any modem responses.
3. Out of Scope
- Dynamic band switching based on signal quality (requires advanced modem coordination and policy engine)
- Signal metrics per band
- Auto-scan feature to detect optimal band based on signal quality
- Automatic band locking based on MCC/MNC (operator-specific band policies)
Was this article helpful?
0 out Of 5 Stars
| 5 Stars | 0% | |
| 4 Stars | 0% | |
| 3 Stars | 0% | |
| 2 Stars | 0% | |
| 1 Stars | 0% |
5
Table of Contents