Service providers that submit mobile broadband availability data in the BDC system must submit the following Supporting Data as well:
- Mobile Propagation Model Details (file upload)
- Mobile Propagation Model Conditions Explanation (web form)
- Mobile Clutter Category Data (file upload)
- Mobile Propagation Model and Link Budget Association (file upload)
- Mobile Link Budget Parameters (file upload)
- Mobile Link Budget Parameters Rationale (file upload)
- Mobile Link Budget Description (web form)
Mobile Propagation Model Details
This file contains records of each propagation model used to model mobile broadband coverage. The file must be in Comma Separated Value (CSV) format and match the specifications in the table below. All values are required unless otherwise indicated.
| Field | Header | Data Type | Example | Description / Notes |
|---|---|---|---|---|
| Model ID | model_id | Text | ITM-1A |
Unique identifier, assigned by the filer, for the propagation model used to generate the coverage data. Value length must be less than 256 characters. |
| Modeling Tool Name | tool_name | Text | Atoll | Name of the planning tool used to generate the coverage data. |
| Modeling Tool Version | tool_version | Text | 3.4.0 | Version number of the planning tool used to generate the coverage data. |
| Modeling Tool Developer | tool_developer | Text | Forsk | Name of the developer of the planning tool used to generate the coverage data. |
| Model Resolution | model_resolution | Integer | 10 |
Resolution of the model used to generate the coverage data, in meters. Value may be approximate for models measured in arcseconds (e.g., 1 arcsecond ≈ 30 meters). Value must be greater than 0 and less than or equal to 100. |
| Receiver Height | receiver_height | Decimal | 1.5 |
Height of the receiver used in modeling, in meters. Value must be greater than or equal to 1.5. |
| Terrain Data Source | terrain_source | Text | USGS | Name of the creator, developer, or supplier of the terrain dataset |
| Terrain Data Vintage | terrain_vintage | Date | 2021-10-18 |
Vintage date of terrain dataset, with at least the year of the dataset entered. Value must match valid ISO-8601 date format, YYYY-MM-DD. If only the year is entered, then YYYY. |
| Terrain Resolution | terrain_resolution | Integer | 30 |
Resolution or granularity of terrain data, in meters. Value may be approximate for datasets measured in arcseconds (e.g., 1 arcsecond ≈ 30 meters). Value must be greater than 0 and less than or equal to 100. |
| Clutter Data Source | clutter_source | Text | ESA Worldcover | Name of the creator, developer, or supplier of the clutter dataset |
| Clutter Data Vintage | clutter_vintage | Date | 2020 |
Vintage date of clutter dataset, with at least the year of the dataset entered. Value must match valid ISO-8601 date format, YYYY-MM-DD. If only the year is entered, then YYYY. |
| Clutter Data Resolution | clutter_resolution | Integer | 10 |
Resolution or granularity of clutter data, in meters. Value may be approximate for datasets measured in arcseconds (e.g., 1 arcsecond ≈ 30 meters). Value must be greater than 0 and less than or equal to 100. |
| Model Validation | calibration_flag | Boolean Integer {1} | 1 | Affirmation that the model has been validated and calibrated at least one time using on-the-ground and/or other real-world measurements taken by the provider or its vendor.
Value must be:
|
| Model Calibration Date | calibration_date | Date | 2021-09-05 |
Most recent date that the model was calibrated. Value must match valid ISO-8601 date format including, at a minimum, the year and month, e.g.: YYYY-MM[-DD] |
| Model Calibration Process | calibration_process | Text | Brief narrative summary of the process used to calibrate the model. |
Mobile Propagation Model Conditions Explanation
If a provider uses more than one propagation model to generate mobile broadband coverage, it must provide a description of the circumstances under which each model is deployed and why. This description must be entered in a web form in the BDC system. Filers that use only one propagation model do not need to enter this form.
| Field | Description / Notes |
|---|---|
| Description |
Explanation of the conditions or circumstances under which each model was applied to the base stations, as used in the modeling tool (identified in the Mobile Propagation Model Details file). Value may be null if only a single model is used. |
Mobile Clutter Category Data
This file must contain records for each clutter category used in the link budget. The file must be in Comma Separated Value (CSV) format and match the specifications in the table below. All values are required unless otherwise indicated.
| Field | Header | Data Type | Example | Description / Notes |
|---|---|---|---|---|
| Clutter Category Number | category_number | Integer | 11 |
Numerical identifier, assigned by the filer, corresponding to each distinct clutter category. Value must be greater than or equal to 0. |
| Clutter Category Name | category_description | Text | Evergreen Forest |
Name or short description of the clutter category. Value length must be less than 256 characters. |
| Constant Signal Loss | constant_signal_loss | Decimal | 3 |
Constant signal loss used in propagation modeling for the clutter category, in dB, with up to 1 one decimal place. Value may be null if the variable_signal_loss value is not null. If entered, value must be greater than or equal to 0. |
| Variable Signal Loss | variable_signal_loss | Decimal | 3 |
Variable signal loss as a function of distance used in propagation modeling for the clutter category, in dB/meter, with up to one decimal place. Value may be null if the constant_signal_loss value is not null. If entered, value must be greater than or equal to 0. |
| Model ID | model_id | Text | ITM-1A |
Unique identifier for the propagation model that has a list of clutter categories. Value should correspond to a model_id value in the Mobile Propagation Model Details file. |
Mobile Propagation Model and Link Budget Association
This file must contain records of the propagation model IDs and their association with link budget IDs, noting that there can be a many-to-many relationship between link budgets and propagation models.
| Field | Header | Data Type | Example | Description / Notes |
|---|---|---|---|---|
| Model ID | model_id | Text | ITM-1A |
Unique identifier of a propagation model used to generate the mobile coverage data and associated with at least one link budget. Value length must be less than 256 characters. Value should correspond to a model_id value in the Mobile Propagation Model Details file. |
| Link Budget ID | link_budget_id | Text | VA1238DL |
Unique identifier of a link budget used to generate the mobile coverage data and associated with at least one propagation model. Value length must be less than 256 characters. Value should correspond to a link_budget_id value in the Mobile Link Budget Parameters file. |
Mobile Link Budget Parameters
This file must contain the fields listed below for each mobile link budget, including separate records for each downlink link budget and each uplink link budget. If a service provider uses different link budget parameters for different technologies or spectrum bands, this file must contain records for each set of distinct downlink / uplink link budget parameters.
| Field | Header | Data Type | Uplink Example | Downlink Example | Description / Notes |
|---|---|---|---|---|---|
| Link Budget ID | link_budget_id | Text | VA1238UL | VA1238DL |
Unique identifier to identify the link budget. Value length must be less than 256 characters. |
| Link Direction | link_direction | Enumerated Text {1} | U | D | Direction of the link budget described in this record.
Value must be one of the following codes:
|
| Technology Code | technology | Enumerated Integer | 501 | 501 | Integer code, taken from the list below, indicating the technology standard used by the channel/carrier described in this record.
Value must be one of the following codes:
|
| Duplex Scheme | duplex_scheme | Enumerated Text {1} | F | F | Duplex scheme used in the link budget from one of two possible values representing either Frequency Division Duplexing or Time Division Duplexing (including CSMA/CA).
Value must be one of the following codes:
|
| Allocation Ratio | allocation_ratio | Text | 2:1 | 2:1 |
Downlink to uplink time allocation ratio. Value may be null. If entered, value must match the format "<numeric>:<numeric>", and each numeric value must be an integer greater than 0. |
| Morphology | morphology | Enumerated Integer {1} | 2 | 2 | Code, taken from the list below, indicating the morphology of the area used in the link budget.
Value must be one of the following codes:
|
| Propagation Conditions | propagation_conditions | Enumerated Integer {1} | 0 | 0 | Integer code, taken from the two options below, indicating the propagation conditions used in the link budget.
Value must be one of the following codes:
|
| Target Speed | target_speed | Decimal | 3.0 | 35.0 |
Target user speeds of the link budget in Mbps. Value must be 0.2 for downlink records and must be 0.05 for uplink records when technology is 3G. Value must be 5 for downlink records and must be 1 for uplink records when technology is 4G LTE. Value must be either 35 or 7 for downlink records and must be either 3 or 1 for uplink records when technology is 5G-NR. |
| Modulation Scheme | modulation_scheme | Text |
16-QAM 2/3 |
16-QAM 2/3 |
The modulation and the coding rate used to deliver the target user speed of the link budget. Filers should enter the modulation followed by a space and then a fraction (<numeric>/<numeric>). Value must be in the format "<string> <numeric>/<numeric>", and each numeric value must be an integer greater than 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Antenna Configuration | antenna_configuration | Text | 1x2 | 2x2 |
Typical deployed antenna configuration. Value must be in the format "<numeric>x<numeric>", and each numeric value must be an integer greater than 0. For 3G or non-FDM/OFDMA technologies, we recommend entering 1x1. |
| Operational Frequency | operational_frequency | Decimal | 1860.0 | 1940.0 |
Center frequency of the operational carrier, in MHz (with three decimal places). Value must be greater than 0. |
| Channel Bandwidth | channel_bandwidth | Decimal | 10.0 | 10.0 |
Total bandwidth of the operating channel, in MHz (with up to two decimal places). Value must be greater than or equal to 0 and less than or equal to 1000. |
| Subcarriers | total_subcarriers | Integer | 600 | 600 |
Total number of subcarriers for the channel (i.e., resource element) if the provider uses OFDM/OFDMA technology. Value may be null if provider does not use OFDM/OFDMA technology. If entered, value must be greater than 0. |
| Subcarrier Spacing | subcarrier_spacing | Decimal | 15.0 | 15.0 |
Subcarrier (or resource element) spacing / bandwidth, in KHz, if the provider uses OFDM/OFDMA technology (with up to two decimal places). Value may be null if provider does not use OFDM/OFDMA technology. If entered, value must be greater than or equal to 15 and less than or equal to 240. |
| Cell Loading Factor | cell_load | Decimal | 0.5 | 0.5 |
Average cell loading factor (both own cell and neighboring cells). Report as a percentage (with up to two decimal places). Value must be greater than or equal to 0.5 and less than or equal to 1. |
| Required Subcarriers | required_subcarriers | Integer | 72 | 200 |
Number of subcarriers required to deliver the target user speeds. Value must be greater than 0. For 3G or non-FDM/OFDMA technologies, we recommend entering 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Required SINR | required_sinr | Decimal | 0.00 | 4.00 |
Required signal to interference and noise ratio (SINR) to deliver the target speeds, in dB (with up to two decimal places). Value must be greater than or equal to -20 and less than or equal to 50. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Spectral Efficiency | spectral_efficiency | Decimal | 1.00 | 1.70 |
Required spectral efficiency to deliver the user speeds at the cell edge, in bps / Hz (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Total Transmitter Power | total_tx_power | Decimal | 23.00 | 30.00 |
Total transmitter power for the cell, including multiple transmitters, in dBm (with up to two decimal places). Value must be greater than or equal to 0. |
| Total Losses in Transmitting Path | total_tx_losses | Decimal | 0.00 | 2.00 |
Total losses in the transmitting path from the amplifier to the antenna, in dB (with up to two decimal places). Value must be greater than or equal to 0 and less than or equal to 10. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Transmitting Antenna Gain | tx_antenna_gain | Decimal | -1.00 | 16.00 |
Transmitting antenna gain, in dBi (with up to two decimal places). Value must be greater than or equal to -20 and less than or equal to 40. |
| EIRP | total_eirp | Decimal | 22.00 | 60.00 |
Total maximum effective isotropic radiated power (EIRP), in dBm, including multiple transmitting antennas, (with up to two decimal places). Value must be greater than or equal to 0 and less than or equal to 80. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| EIRP per Subcarrier | eirp_per_subcarrier | Decimal | 3.43 | 32.22 |
Maximum effective isotropic radiated power (including multiple transmitting antennas) per subcarrier, in dBm (with up to two decimal places). Value must be less than or equal to (<total_eirp> - 10log(<total_num_of_subcarriers>)) +3) for downlink link budgets. Value must be less than or equal to the lesser of <total_eirp> and (<total_eirp> -(10*log(<required_subcarriers>)) +3) for uplink link budgets Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Receiving Antenna Gain | rx_antenna_gain | Decimal | 16.00 | 0.00 |
Receiving antenna gain, in dBi (with up to two decimal places). Value must be greater than or equal to -20 and less than or equal to 40. |
| Total Losses in Receiving Path | total_rx_losses | Decimal | 2.00 | 0.00 |
Total losses in the receiving path from the antenna to the receiver, in dB (with up to two decimal places). Value must be greater than or equal to 0 and less than or equal to 10. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Receiver System Noise Figure | rx_noise_figure | Decimal | 2.00 | 10.00 |
Noise figure of the receiver system - which could consist of an antenna (circuits), a transmission line, and a receiver - in dB (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Receiver Sensitivity | rx_sensitivity | Decimal | -130.21 | -118.21 |
Receiver sensitivity per subcarrier, in dBm (with up to two decimal places). Value must be less than 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Thermal Noise Power | thermal_noise_power | Decimal | -173.98 | -173.98 |
Thermal noise power, in dBm per Hz (with up to two decimal places). Value must be less than 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Thermal Noise Power per Subcarrier | thermal_noise_power_per_subcarrier | Decimal | -132.21 | -132.21 |
Thermal noise power, in dBm, per subcarrier (with up to two decimal places). Value must be less than 0. |
| Total Noise Power per Subcarrier | total_noise_power_per_subcarrier | Decimal | -130.21 | -122.21 |
Total noise power (thermal and receiver), in dBm, per subcarrier (with up to two decimal places). Value must be less than 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Fading Standard Deviation | fading_std_deviation | Decimal | 8.00 | 8.00 |
Standard deviation of the log-normal signal slow fading, in dB (with up to two decimal places). Value must be less than 0. |
| Cell Edge Probability | cell_edge_probability | Decimal | 0.9 | 0.9 |
Desired probability of receiving the signal at or above the receiver sensitivity at the cell coverage boundary. Report as a percentage with up to two decimal places. Value must be greater than or equal to 0.9 and less than or equal to 1. |
| Fade Margin | fade_margin | Decimal | 10.25 | 10.25 |
Signal slow fading margin required to deliver the desired cell edge reliability, in dB (with up to two decimal places). Value must be greater than 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Head and Body Loss | head_body_loss | Decimal | 0.00 | 2.00 |
Typical signal loss at the operating frequency, in dB, due to head and/or body obstruction (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Interference Margin | interference_margin | Decimal | 3.00 | 5.00 |
Additional signal loss, in dB, due to interference from adjacent cells due to cell loading (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Penetration Margin | penetration_margin | Decimal | 0.00 | 0.00 |
Additional signal loss due to surrounding obstructions when the receiver is inside a vehicle, in dB (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Other Losses | other_losses | Decimal | 0.00 | 0.00 |
Any other unaccounted signal losses, in dB (with up to two decimal places). Value may be null. If entered, value must be greater than or equal to 0. If entered, value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Frequency Selection Gain | freq_selection_gain | Decimal | 0.00 | 0.00 |
Dynamic frequency selection gain, in dB (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Multi-Cell Switching Gain | multi_cell_diversity_gain | Decimal | 2.00 | 2.00 |
Multi-cell switching or macro-diversity gain, in dB (with up to two decimal places). Value must be greater than or equal to 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Other Gains | other_gains | Decimal | 0.00 | 0.00 |
Other unaccounted gains, in dB (with up to two decimal places). Value may be null. If entered, value must be greater than or equal to 0. If entered, value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
| Total Margins | total_margins | Decimal | 11.25 | 15.25 |
Total net margins, in dB (with up to two decimal places). Value must be greater than or equal to 0. |
| Maximum Allowable Path Loss | mapl | Decimal | 136.39 | 139.18 |
Maximum allowable path loss of the link, in dB (with up to two decimal places). Value must be greater than 0. |
| Minimum Signal Strength | minimum_signal_strength | Decimal | -132.96 | -106.96 |
Minimum required signal strength at the receiver to deliver the specified performance targets (e.g., RSRP for 4G LTE), in dBm, per subcarrier (with up to two decimal places). Value must be less than 0. Value for this field must have a corresponding explanation / rationale in the Mobile Link Budget Parameters Rationale file for each link budget. |
Mobile Link Budget Parameters Rationale
This file must contain an explanation / rationale for the particular values reported in the provider's Mobile Link Budget Parameters file. Unless the reported link budget parameter is null, filers must include, for each separate link budget, an explanation / rationale for the reported value for the following link budget parameters:
- Modulation Scheme (modulation_scheme)
- Required subcarriers (required_subcarriers)
- Required SINR (required_sinr)
- Spectral Efficiency (spectral_efficiency)
- Total Losses in Transmitting Path (total_tx_losses)
- EIRP (total_eirp)
- EIRP per Subcarrier (eirp_per_subcarrier)
- Total Losses in Receiving Path (total_rx_losses)
- Receiver System Noise Figure (rx_noise_figure)
- Receiver Sensitivity (rx_sensitivity)
- Thermal Noise Power (thermal_noise_power)
- Total Noise Power per Subcarrier (total_noise_power_per_subcarrier)
- Fade Margin (fade_margin)
- Head and Body Loss (head_body_loss)
- Interference Margin (interference_margin)
- Penetration Margin (penetration_margin)
- Other Losses (other_losses)
- Frequency Selection Gain (freq_selection_gain)
- Multi-Cell Switching Gain (multi_cell_diversity_gain)
- Other Gains (other_gains)
- Minimum Signal Strength (minimum_signal_strength)
| Field | Header | Data Type | Example | Description / Notes |
|---|---|---|---|---|
| Link Budget ID | link_budget_id | Text | VA1238DL |
Unique identifier of a link budget used to generate the mobile coverage data and associated with at least one propagation model. Value length must be less than 256 characters. Value should correspond to a link_budget_id value in the Mobile Link Budget Parameters file. |
| Parameter | parameter | Enumerated Text | fade_margin |
Field name header identifying the parameter. Value should correspond to one of the required field names from the Mobile Link Budget Parameters file. Enter the specified header for the field. |
| Rationale | rationale | Text | The value of 10.3 dB corresponds to 90% cell edge coverage probability with 8 dB fade margin standard deviation. 8 dB fade margin standard deviation is reasonable based on previous studies [enter citation]. | Short narrative explaining why a particular value was chosen in the link budget with citations where possible. |
Mobile Link Budget Description
In this web form, filers must provide a description of how the link budgets were created for each link budget that was used to generate the mobile broadband availability data.
| Field | Description / Notes |
|---|---|
| Description | Narrative description of how the link budgets (identified in the Mobile Link Budget Parameters file) were created. |