Attachment A Format of Data All data should be submitted in a .csv (comma-delimited) format. The sheets in the workbook provide a template for how the tables should be designed. The required format for the entries in each column/field is indicated in the instructions for each sheet. All entries in Text fields must be in quotation marks (e.g. "T-Mobile", "Sprint"). Column entries in bold red indicate that the party shall enter only one of the possible entries listed for that column. No other entries shall be entered. Data for all of the tables shall be submitted on a periodic basis as specified in the instructions in individual tables. In a separate written response, explain in detail the applicable methodology and assumptions used to derive all projections in response to this data request. "Site Data" Table For each year beginning December 2015 and extending through December 2024, provide, at the level of site ID, the following site and projected site data. Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Column A: Date Description: The month for which the data is being collected as of the second week of the month. Format of Field: Text - YYYY_MM Possible Entries: 2015_12 2016_12 2017_12 2018_12 2019_12 2020_12 2021_12 2022_12 2023_12 2024_12 Column B: Operator Description: The operator of the site to which this data record applies. In cases where a Sprint site and T-Mobile site share the same tower or other supporting structure, each site shall be entered separately. Format of Field: Text Possible Entries: "Sprint" "T-Mobile" "New T-Mobile" Column C: Site ID Description: A unique site ID for the site to which this data record applies. Format of Field: Text Example Entries: "AL0001", "VA0128", etc. Column D: Number of Sectors Description: This field provides an integer representing the number of sectors this site utilizes. Format of Field: Number - Integer Example Entries: 1, 2, 3, etc. Column E: Latitude Description: This field is the latitude of the site in decimal form to at least seven significant digits. Coordinates must be in the WGS84 geographic coordinate system. Format of Field: Number - At least 6 decimal places Example Entries: 40.7127837, etc. Column F: Longitude Description: This field is the longitude of the site in decimal form to at least seven significant digits. Coordinates must be in the WGS84 geographic coordinate system. Format of Field: Number - At least 6 decimal places Example Entries: -74.0059413, etc. "Site Data" Table For each year beginning December 2015 and extending through December 2024, provide, at the level of site ID, the following site and projected site data. Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Column G: County FIPS Description: This field is the 2010 five-digit FIPS code of the county in which the site is located. Please provide data for counties and county-equivalents in the United States and Commonwealth of Puerto Rico. Format of Field: Text Example Entries: "01001", "51059", etc. Column H: CMA Description: This field represents the standard market number of the CMA in which the site is located. Please provide data for CMAs in the United States and Commonwealth of Puerto Rico. Format of Field: Number - Integer Possible Entries: Integers 1 - 729 Column I: Site Type Description: This field indicates the type of site to which the record applies using one of the possible entries listed below. Format of Field: Text Possible Entries: "Macro_Tower" An outdoor macrocell mounted on a monopole, guyed tower, or free standing tower "Macro_Building" An outdoor macrocell mounted on a building "Macro_Other" An outdoor macrocell that does not fit the previous categories (silo, water tower, etc.) "Microcell" An outdoor cell classified by the vendor as a microcell (much smaller coverage footprint than a macrocell) "Picocell" A cell classified by the vendor as a picocell (smaller coverage footprint than a microcell) "Outdoor DAS" An outdoor Distributed Antenna System "Indoor DAS" An indoor Distributed Antenna System "Repeater" A cell that repeats/boosts the signal of another cell "Other" A cell that does not meet any of the above descriptions Site Clutter Column J: Classification Description: This field indicates the morphology of the area that the site serves using one of the possible entries listed below. Please provide a description of the methodology used to determine these classifications in a separate attachment. Format of Field: Text Possible Entries: "Urban" "Suburban" "Rural" "Site Data" Table For each year beginning December 2015 and extending through December 2024, provide, at the level of site ID, the following site and projected site data. Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Antenna Height - Column K: (Feet - AGL) Description: This field indicates the antenna height above ground level in feet. Enter 9999 if not applicable. Format of Field: Number Example Entries: 100 Site Height (Feet - Column L: ASL) Description: This field indicates the antenna height above sea level in feet. Format of Field: Number Example Entries: 467 Column M: Backhaul Medium Description: The type of technology used for backhaul at this site using one of the possible entries listed below. Format of Field: Text Example Entries: "Fiber" "Copper" "Hybrid Fiber Coax (HFC)" "Fixed Wireless" "Satellite" Column N: Backhaul Capacity - Incoming (Gbps) Description: Provisioned Capacity: One-way provisioned capacity of backhaul link in Gbps given capabilities of existing HW - incoming to the base station Format of Field: Number Column O: Backhaul Capacity - Outgoing (Gbps) Description: Provisioned Capacity: One-way provisioned capacity of backhaul link in Gbps given capabilities of exisiting HW - outgoing from the base station Format of Field: Number Column P: Latency (ms.) Description: Service Level Agreement Latency in miliseconds (round-trip) Format of Field: Number Example Entries: 10 ms. "Site Data" Table For each year beginning December 2015 and extending through December 2024, provide, at the level of site ID, the following site and projected site data. Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Max. Upgradable Column Q: Backhaul Capacity - Incoming (Gbps) Description: Max. Upgradable Capacity: One-way maximum capacity of backhaul link in Gbps given capabilities of upgradable HW - incoming to the base station Format of Field: Number Max. Upgradable Column R: Backhaul Capacity - Outgoing (Gbps) Description: Max. Upgradable Capacity: One-way maximum capacity of backhaul link in Gbps given capabilities of upgradable HW - outgoing from the base station Format of Field: Number BBH DL Speed Column S: (Mbps) Description: Average user dowload speed (Mbps) during the bouncing busy hour (BBH) for the site The BBH traffic should be the five-day (weekday) average. Format of Field: Number Example Entries: 10 Mbps BBH UL Speed Column T: (Mbps) Description: Average user upload speed (Mbps) during the bouncing busy hour (BBH) for the site The BBH traffic should be the five-day (weekday) average. Format of Field: Number Example Entries: 2 Mbps "Site Data" Table For each year beginning December 2015 and extending through December 2024, provide, at the level of site ID, the following site and projected site data. Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Retained Site for Column U: New T-Mobile Description: Will this site be retained for the New T-Mobile network? Format of Field: Text Possible Entries: "Y" "N" Remaining Lease Column V: Time (months) Description: How many remaining months before this site current lease expires If this site is owned by the applicants, enter 9999 Format of Field: Number Example Entries: 60 Months Applicants Column W: Colocated Description: Are applicants colocated on the same site? Format of Field: Text Possible Entries: "Y" "N" 600 MHz Available Column X: (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 700 MHz Available Column Y: (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 800 MHz Available Column Z: (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 PCS Available Column AA (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 "Site Data" Table For each year beginning December 2015 and extending through December 2024, provide, at the level of site ID, the following site and projected site data. Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. AWS Available Column AB (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 BRS Available Column AC (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 EBS Available Column AD (MHz) Description: The total amount of spectrum (MHz) available for this band (Downlink + Uplink) Format of Field: Number Example Entries: 10 mmWave Available Column AE (MHz) Description: The total amount of spectrum (MHz) available for the 24, 28, 39, and 47 GHz bands (Downlink + Uplink) Format of Field: Number Example Entries: 100 Number of Site Clutter Antenna Height - Date Operator Site ID Sectors Latitude Longitude County FIPS CMA Site Type Classification (Feet - AGL) Max. Max. Upgradable Upgradable Backhaul Backhaul Backhaul Backhaul Retained Remaining Capacity - Capacity - Capacity - Capacity - Site for Lease Site Height Backhaul Incoming Outgoing Latency Incoming Outgoing BBH DL Speed BBH UL Speed New T- Time (Feet - ASL) Medium (Gbps) (Gbps) (ms.) (Gbps) (Gbps) (Mbps) (Mbps) Mobile (months) 600 MHz 700 MHz 800 MHz PCS AWS BRS EBS mmWave Applicants Available Available Available Available Available Available Available Available Colocated (MHz) (MHz) (MHz) (MHz) (MHz) (MHz) (MHz) (MHz) "Deployed Carriers" Table For each year beginning December 2015 and extending through December 2024, provide at the level of carrier the following deployed or projected carriers da Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The term "carrier" refers to channels or portions of spectrum used in the network rather than operators or service providers. In general, this table should contain one row for each carrier/channel deployed or projected at each sector. Because sites and sectors can include multiple carriers/channels, the same site/sector ID may appear in multiple rows. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Column A: Date Description: The month for which the data is being collected as of the second week of the month. Format of Field: Text - YYYY_MM Possible Entries: 2015_12 2016_12 2017_12 2018_12 2019_12 2020_12 2021_12 2022_12 2023_12 2024_12 Column B: Operator Description: The operator of the site to which this data record applies. In cases where a Sprint site and T-Mobile site share the same tower or other supporting structure, each site shall be entered separately. Format of Field: Text Possible Entries: "Sprint" "T-Mobile" "New T-Mobile" "Deployed Carriers" Table For each year beginning December 2015 and extending through December 2024, provide at the level of carrier the following deployed or projected carriers da Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The term "carrier" refers to channels or portions of spectrum used in the network rather than operators or service providers. In general, this table should contain one row for each carrier/channel deployed or projected at each sector. Because sites and sectors can include multiple carriers/channels, the same site/sector ID may appear in multiple rows. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Column C: Site ID Description: The unique site ID from the "Site Data" table for the site to which this data record applies. Format of Field: Text Example Entries: "AL0001", "VA0128", etc. Column D: Sector ID Description: A unique sector ID for the sector to which this data record applies, created by adding a suffix to the site ID. Format of Field: Text Example Entries: Suffix examples include "A","B","C" or "1","2","3" Deployed Column E: Technology Description: This field indicates the technology standard used by the channel/carrier described in this record. Format of Field: Text Possible Entries: "1X" A carrier/channel that supports 1X CDMA "EVDO" A carrier/channel that supports EVDO "GSM" A carrier/channel that supports GSM "HSPA" A carrier/channel that supports HSPA or HSPA+ "LTE-R8" A LTE carrier conforming to 3GPP Release 8 "LTE-R10" A LTE carrier conforming to 3GPP Release 10 "LTE-R12" A LTE carrier conforming to 3GPP Release 12 "LTE-R13" A LTE carrier conforming to 3GPP Release 13 "LTE-LAA" A LTE Licensed Assisted Access supplemental downlink carrier "5G-R15" A 5G-NR carrier conforming to 3GPP Release 15 "5G-R16" A 5G-NR carrier conforming to 3GPP Release 16 "5G-R17" A 5G-NR carrier conforming to 3GPP Release 17 "Fixed-Wireless" A carrier used for fixed wireless deployment "NB-IoT" Narrowband IoT "List Other" Specify a technology that does not conform to one of the technologies listed above "Deployed Carriers" Table For each year beginning December 2015 and extending through December 2024, provide at the level of carrier the following deployed or projected carriers da Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The term "carrier" refers to channels or portions of spectrum used in the network rather than operators or service providers. In general, this table should contain one row for each carrier/channel deployed or projected at each sector. Because sites and sectors can include multiple carriers/channels, the same site/sector ID may appear in multiple rows. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Deployed Spectrum Column F: Band Description: The frequency band in which the channel/carrier in this data record operates. Format of Field: Text Possible Entries: "600 MHz" The 600 MHz band "700 MHz" The 700 MHz band "800 MHz" The 800 MHz band "PCS" The PCS band "AWS" The AWS band "BRS" The BRS band "EBS" The EBS band "mmWave" The 24, 28, 39, and 47 GHz mmWave bands DL RF Carrier Center Column G: Freq. (MHz) Description: This field contains the unrounded center frequency in MHz of the downlink carrier described in this record. If the carrier is TDD, then enter the center frequency of the TDD carrier Format of Field: Number Example Entries: 1937.5, 2142.625, etc. DL RF Carrier Column H: Bandwidth (MHz) Description: This field contains the bandwidth in MHz of the downlink RF carrier described in this record If carrier aggregation is used, each component carrier is an entry with the traffic distributed accordingly If the carrier is TDD, then enter the entire bandwidth of the TDD carrier Format of Field: Number Example Entries: 1.25 Carrier = 1X 1.25 Carrier = EVDO 0.2 Carrier = GSM 5 Carrier = HSPA 5 Carrier = LTE 10 Carrier = LTE 15 Carrier = LTE 20 Carrier = LTE 60 Carrier = 5G Carrier = Other "Deployed Carriers" Table For each year beginning December 2015 and extending through December 2024, provide at the level of carrier the following deployed or projected carriers da Projected data shall include as separate entries plans for the standalone Applicants and those for New T-Mobile. The term "carrier" refers to channels or portions of spectrum used in the network rather than operators or service providers. In general, this table should contain one row for each carrier/channel deployed or projected at each sector. Because sites and sectors can include multiple carriers/channels, the same site/sector ID may appear in multiple rows. The site IDs in this table shall correspond to the site IDs entered in the other requested tables. Column I: Sector Az Description: Azimuth of the antenna sector orientation in degrees Format of Field: Number Example Entries: 0 120 Column J: Carrier Active Description: This field is used to indicate whether a carrier is actively carrying customer traffic. Format of Field: Text Possible Entries: "Y" Indicates that the carrier is carrying commercial traffic generated by paying customers "N" Indicates that the carrier is not yet deployed, used for test or trial purposes, or turned off BBH DL Carried Column K: Traffic (Gbytes/Hr) Description: Base to mobile carried traffic (data+voice) in Gbytes during the bouncing busy hour (BBH) for the deployed RF carrier The BBH traffic should be the five-day (weekday) average. For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 75 Gbytes/Hr BBH UL Carried Column L: Traffic (Gbytes/Hr) Description: Mobile to Base carried traffic (data+voice) in Gbytes during the bouncing busy hour (BBH) for the deployed RF carrier The BBH traffic should be the five-day (weekday) average. For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 20 Gbytes/Hr Deployed DL RF Carrier DL RF Carrier BBH DL Carried BBH UL Carried Deployed Spectrum Center Freq. Bandwidth Sector Az Carrier Traffic Traffic Date Operator Site ID Sector ID Technology Band (MHz) (MHz) (deg.) Active (Gbytes/Hr) (Gbytes/hr) Deployed Carriers Template "Offered Capacity" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide at the level of technology/spectrum band the following offered capacity data at the county level, and for the United States, including the Commonwealth of Puerto Rico. Projected data shall include as separate entries capacity projections for the standalone Applicants and those for New T-Mobile. Column A: Date Description: The month for which the offered capacity data is being collected or projected. as of the second week of the month. Format of Field: Text - YYYY_MM Possible Entries: 2015_03 2018_12 2015_06 2019_12 2015_09 2020_12 2015_12 2021_12 2016_03 2022_12 2016_06 2023_12 2016_09 2024_12 2016_12 2021_12 2017_03 2022_12 2017_06 2023_12 2017_09 2024_12 2017_12 2018_03 2018_06 Column B: Operator Description: The operator of the site to which this data record applies. In cases where a Sprint site and a T-Mobile site share the same tower or other supporting structure, each site shall be entered separately. Format of Field: Text Possible Entries: "Sprint" "T-Mobile" "New T-Mobile" Column C: County FIPS Description: This field is the 2010 five-digit FIPS code of the county in which the site is located. Please provide data for counties and county-equivalents in the United States and Commonwealth of Puerto Rico. Format of Field: Text Example Entries: "01001", "51059", etc. Column D: CMA Description: This field represents the standard market number of the CMA in which the site is located. Please provide data for CMAs in the United States and Commonwealth of Puerto Rico. Format of Field: Number - Integer Possible Entries: Integers 1 - 729 "Offered Capacity" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide at the level of technology/spectrum band the following offered capacity data at the county level, and for the United States, including the Commonwealth of Puerto Rico. Projected data shall include as separate entries capacity projections for the standalone Applicants and those for New T-Mobile. Column E: Technology Description: This field indicates the technology standard used by the channel/carrier described in this record. Format of Field: Text Possible Entries: "1X" A carrier/channel that supports 1X CDMA "EVDO" A carrier/channel that supports EVDO "GSM" A carrier/channel that supports GSM "HSPA" A carrier/channel that supports HSPA or HSPA+ "LTE-R8" A LTE carrier conforming to 3GPP Release 8 "LTE-R10" A LTE carrier conforming to 3GPP Release 10 "LTE-R12" A LTE carrier conforming to 3GPP Release 12 "LTE-R13" A LTE carrier conforming to 3GPP Release 13 "LTE-LAA" A LTE Licensed Assisted Access supplemental downlink carrier "5G-R15" A 5G-NR carrier conforming to 3GPP Release 15 "5G-R16" A 5G-NR carrier conforming to 3GPP Release 16 "5G-R17" A 5G-NR carrier conforming to 3GPP Release 17 "Fixed-Wireless" A carrier used for fixed wireless deployment "NB-IoT" Narrowband IoT "List Other" Specify a technology that does not conform to one of the technologies listed above Column F: Spectrum Band Description: The frequency band in which the channel/carrier in this data record operates. Format of Field: Text Possible Entries: "600 MHz" The 600 MHz band "700 MHz" The 700 MHz band "800 MHz" The 800 MHz band "PCS" The PCS band "AWS" The AWS band "BRS" The BRS band "EBS" The EBS band "mmWave" The 24, 28, 39, and 47 GHz mmWave bands "Offered Capacity" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide at the level of technology/spectrum band the following offered capacity data at the county level, and for the United States, including the Commonwealth of Puerto Rico. Projected data shall include as separate entries capacity projections for the standalone Applicants and those for New T-Mobile. DL+UL Bandwidth Column G: (MHz) Description: This field contains the downlink and uplink combined bandwidth (MHz) in operation for the spectrum band Format of Field: Number Example Entries: 10 Carrier = LTE 20 Carrier = LTE BBH DL Offered Column H: Capacity (Gbytes/Hr) Description: Collected or projected base station to mobile offered traffic (data+voice) in Gbytes during the bouncing busy hour (BBH) for the combine The BBH traffic should be the five-day (weekday) average. For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 75 Gbytes/Hr BBH UL Offered Column I: Capacity (Gbytes/Hr) Description: Collected or projected mobile to base station offered traffic (data+voice) in Gbytes during the bouncing busy hour (BBH) for the combine The BBH traffic should be the five-day (weekday) average. For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 20 Gbytes/Hr Column J: Latency (ms.) Description: Collected or projected network latency (round-trip) in miliseconds Format of Field: Number Example Entries: 70 ms. BBH DL Offered BBH UL Offered DL+UL Capacity Capacity Date Operator County CMA Technology Spectrum Band Bandwidth (MHz) (Gbytes/Hr) (Gbytes/Hr) Latency (ms.) Page 19 Offered Capacity Template "Traffic Demand" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide for each county in the United States and the Commonwealth of Puerto Rico and each technology the following traffic data. Projected data shall include as separate entries traffic projections for the standalone Applicants and those for New T-Mobile. Column A: Date Description: The month for which the traffic demand or carried traffic is being projected. as of the second week of the month. Format of Field: Text - YYYY_MM Possible Entries: 2015_03 2018_12 2015_06 2019_12 2015_09 2020_12 2015_12 2021_12 2016_03 2022_12 2016_06 2023_12 2016_09 2024_12 2016_12 2021_12 2017_03 2022_12 2017_06 2023_12 2017_09 2024_12 2017_12 2018_03 2018_06 Column B: Operator Description: The operator of the site to which this data record applies. In cases where an Sprint site and T-Mobile site share the same tower or other supporting structure, each site shall be entered separately. Format of Field: Text Possible Entries: "Sprint" "T-Mobile" "New T-Mobile" Column C: County FIPS Description: This field is the 2010 five-digit FIPS code of the county in which the site is located. Please provide data for counties and county-equivalents in the United States and Commonwealth of Puerto Rico. Format of Field: Text Example Entries: "01001", "51059", etc. "Traffic Demand" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide for each county in the United States and the Commonwealth of Puerto Rico and each technology the following traffic data. Projected data shall include as separate entries traffic projections for the standalone Applicants and those for New T-Mobile. Column D: CMA Description: This field represents the standard market number of the CMA in which the site is located. Please provide data for CMAs in the United States and Commonwealth of Puerto Rico. Format of Field: Number - Integer Possible Entries: Integers 1 - 729 Column E: Technology Description: This field indicates the technology standard of this record. Format of Field: Text Possible Entries: "1X" A carrier/channel that supports 1X CDMA "EVDO" A carrier/channel that supports EVDO "GSM" A carrier/channel that supports GSM "HSPA" A carrier/channel that supports HSPA or HSPA+ "LTE-R8" A LTE carrier conforming to 3GPP Release 8 "LTE-R10" A LTE carrier conforming to 3GPP Release 10 "LTE-R12" A LTE carrier conforming to 3GPP Release 12 "LTE-R13" A LTE carrier conforming to 3GPP Release 13 "LTE-LAA" A LTE Licensed Assisted Access supplemental downlink carrier "5G-R15" A 5G-NR carrier conforming to 3GPP Release 15 "5G-R16" A 5G-NR carrier conforming to 3GPP Release 16 "5G-R17" A 5G-NR carrier conforming to 3GPP Release 17 "Fixed-Wireless" A carrier used for fixed wireless deployment "NB-IoT" Narrowband IoT "List Other" Specify a technology that does not conform to one of the technologies listed above Column F: Subscribers Description: The number of subscribers with the technology standard in the county Format of Field: Number Example Entries: 22,000 BBH DL Traffic Column G: Demand (Gbytes/Hr) Description: Collected or projected base station to mobile traffic (data+voice) demand in Gbytes/Hr during the bouncing busy hour (BBH) for the county and tech The BBH traffic should be the five-day (weekday) average. For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 15,000 Gbytes/Hr BBH UL Traffic Column H: Demand (Gbytes/Hr) Description: Collected or projected mobile to base station traffic (data+voice) demand in Gbytes/Hr during the bouncing busy hour (BBH) for the county and techn The BBH traffic should be the five-day (weekday) average. For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 3,000 Gbytes/Hr "Traffic Demand" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide for each county in the United States and the Commonwealth of Puerto Rico and each technology the following traffic data. Projected data shall include as separate entries traffic projections for the standalone Applicants and those for New T-Mobile. BBH DL Speed Column I: (Mbps) Description: Average user dowload speed (Mbps) during the bouncing busy hour (BBH) for the county and technology The BBH traffic should be the five-day (weekday) average. Format of Field: Number Example Entries: 5 Mbps BBH UL Speed Column J: (Mbps) Description: Average user upload speed (Mbps) during the bouncing busy hour (BBH) for the county and technology The BBH traffic should be the five-day (weekday) average. Format of Field: Number Example Entries: 1 Mbps Column K: BBH Latency (Ms) Description: Average latency (round-trip) in milliseconds during the bouncing busy hour (BBH) for the county and technology The BBH traffic should be the five-day (weekday) average. Format of Field: Number Example Entries: 80 ms. Avg DL Traffic Column L: Demand (Gbytes/Hr) Description: Collected or projected average base station to mobile traffic (data+voice) demand in Gbytes/Hr over the course of a 24-hour day, as a montly average, including weekends, for the county and technology For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 5,000 Gbytes/Hr Avg UL Traffic Column M: Demand (Gbytes/Hr) Description: Collected or projected average mobile to base station traffic (data+voice) demand in Gbytes/Hr over the course of a 24-hour day, as a montly average, including weekends, for the county and technology For predominantly voice technologies such as GSM and 1X CDMA, the traffic unit shall be in Erlangs Format of Field: Number Example Entries: 1,000 Gbytes/Hr "Traffic Demand" Table For each quarter beginning 2015_Q1 and extending through 2018_Q2, and for each year thereafter extending to 2024, please provide for each county in the United States and the Commonwealth of Puerto Rico and each technology the following traffic data. Projected data shall include as separate entries traffic projections for the standalone Applicants and those for New T-Mobile. Avg DL Speed Column N: (Mbps) Description: Average user dowload speed (Mbps) over the course of a 24-hour day as a montly average, including weekends, for the county and technology Format of Field: Number Example Entries: 22 Mbps Avg UL Speed Column O: (Mbps) Description: Average user upload speed (Mbps) over the course of a 24-hour day as a montly average, including weekends, for the county and technology Format of Field: Number Example Entries: 6 Mbps Column P: Avg Latency (Ms) Description: Average user latency (round-trip) in milliseconds over the course of a 24-hour day as a montly average, including weekends, for the county and techn Format of Field: Number Example Entries: 70 ms. Data Blocking Column Q: Rate (%) Description: The percentage of data requests that were blocked or failed to connect as a montly average, including weekends, for the county and technology Format of Field: Number - at least 4 decimal points Example Entries: 0.0179 Dropped Calls Rate Column R: (%) Description: The percentage of calls that were dropped as a montly average, including weekends, for the county and technology Format of Field: Number - at least 4 decimal points Example Entries: 0.0024 Blocked Call Rate Column S: (%) Description: The percentage of call requests that were blocked or failed to connect as a montly average, including weekends, for the county and technology Format of Field: Number - at least 4 decimal points Example Entries: 0.0024 BBH UL Traffic BBH DL BBH DL Traffic Demand Speed Date Operator County CMA Technology Subscribers Demand (Gbytes/Hr) (Gbytes/Hr) (Mbps) Avg DL Avg UL BBH UL BBH Traffic Traffic Avg DL Avg Data Dropped Blocked Speed Latency Demand Demand Speed Avg UL Latency Blocking Calls Call Rate (Mbps) (Ms) (Gbytes/Hr) (Gbytes/Hr) (Mbps) Speed (Mbps) (Ms) Rate (%) Rate (%) (%)