Broadband Data Collection Data Specifications for Mobile Speed Test ...

[Pages:24]Broadband Data Collection

Data Specifications for Mobile Speed Test Data

March 9, 2022

Table of Contents

1 Overview......................................................................................................................... 1 2 Crowdsourced Data.......................................................................................................... 2

2.1 Mobile Crowdsourced Data........................................................................................ 2 2.1.1 Mobile Consumer Crowdsourced Speed Test Data............................................... 3 2.1.2 Mobile Entity Crowdsourced Speed Test Data ..................................................... 4

3 Challenge Process Data .................................................................................................... 4 3.1 Mobile Challenge Data ............................................................................................... 4 3.1.1 Mobile Consumer Challenge Speed Test Data...................................................... 5 3.1.2 Mobile Entity Challenge Speed Test Data............................................................. 6

4 Provider Response Data ................................................................................................... 6 4.1 Mobile Provider Response Data ................................................................................. 6 4.1.1 Mobile Provider Response Speed Test Data......................................................... 7

5 Common Data Formats .................................................................................................... 7 5.1 Common Mobile Speed Test Data .............................................................................. 7 5.1.1 Contact Object.................................................................................................... 8 5.1.2 Submission Object .............................................................................................. 8 5.1.3 Test Object........................................................................................................12 5.1.4 Download Test Object........................................................................................13 5.1.5 Upload Test Object ............................................................................................14 5.1.6 Latency Test Object ...........................................................................................16 5.1.7 Location Objects ................................................................................................17 5.1.8 Cell Objects .......................................................................................................18

1 Overview

As part of the Federal Communication Commission's (FCC or the Commission) Broadband Data Collection (BDC), individuals and entities can take on-the-ground speed tests of mobile network coverage and submit the results of those tests to the FCC.

The speed test results for the BDC may be collected and submitted to the FCC via different mechanisms depending on who takes the speed test and the purpose of the test. Specifically, mobile speed test data fall into five categories:

1. Consumer Crowdsource: speed tests that are (a) conducted by members of the general public using the FCC Speed Test app or an approved third-party mobile app, and (b) are not intended to formally dispute a mobile service provider's claimed coverage. These test results are not considered valid challenge data and will be used by the Commission to inform its understanding of mobile coverage data.

2. Consumer Challenge: speed tests conducted by members of the general public using the FCC Speed Test app or an approved third-party app that are submitted to formally dispute a mobile service provider's claimed coverage.

3. Entity Crowdsource: speed tests that are (a) conducted by service providers, state, local, or Tribal governments, or other entities using their own hardware or software, and (b) are not submitted to formally dispute a mobile service provider's claimed coverage. These test results are not considered valid challenge data and will be used by the Commission to inform its understanding of mobile coverage data.

4. Entity Challenge: speed tests conducted by service providers, state, local, or Tribal governments, or other third-parties using their own hardware or software that are submitted to formally dispute a mobile service provider's claimed coverage.

5. Provider Response: speed tests that are conducted by service providers using their own hardware or software, and are submitted to provide on-the-ground measurements in response to a challenge or a Commission verification inquiry.

Consumers or members of the general public interested in submitting mobile speed tests as crowdsourced data or as part of the challenge process may use the FCC Speed Test app or other third-party apps approved by the Office of Engineering and Technology (OET) on iOS or Android devices to conduct and automatically submit data. All consumer speed test data must be transmitted to the FCC's BDC system by the third-party app developer from its servers via an Application Programming Interface (API), and such data must conform to the specifications detailed below.

Entities ? including service providers, state, local, and Tribal governments, as well as other third-parties (e.g., consumer groups, non-governmental groups, etc.) ? interested in submitting mobile speed tests as crowdsourced data or as part of the mobile challenge process may use their own hardware or software to conduct bulk collections of mobile speed tests. Such bulk speed test data must be submitted in the BDC system either via file upload or through use of the BDC filer API, and such data must conform to the specifications detailed below. An entity interested in submitting such data must first be authenticated in the BDC system.

1

Service providers that submit on-the-ground measurements in response to a challenge or a Commission verification inquiry may use their own hardware or software to conduct mobile speed tests. All provider response speed test data must be submitted in the BDC system either via file upload or through use of the BDC filer API, and such data must conform to the specifications detailed below. A service provider submitting such data must first be authenticated in the BDC system. Section 5 of this document provides the data structure used for all mobile speed test data collected as part of the BDC. The data must be submitted in a JavaScript Object Notation (JSON) file format and match the specifications below. Sections 2 through 4 explain which attributes detailed in the common data structure are optional and which values may be null, depending on the type of entity submitting the data, the purpose of the data, the device operating system, and other factors.

Instructions for governmental entities, other entities, and mobile providers on how to use the API to submit data into the BDC system will be provided at a later date.

The requirements in this document do not constitute binding FCC rules; rather, this document provides guidance on the requirements governing the binding FCC data collection rules and explains how to make the required filings in the system. The rules governing the Broadband Data Collection (formerly known as the Digital Opportunity Data Collection) can be found in 47 CFR ? 1.7004 et seq.

The FCC's Office of Economics and Analytics may publish updates to this document prior to the initial BDC filing window and in advance of subsequent BDC filing windows. In addition, formal instructions for biannual BDC submissions, a User Guide for the BDC System, and other materials will be made available, prior to the initial BDC filing window, on the Broadband Data Collection Resources page of the FCC's website at .

2 Crowdsourced Data

2.1 Mobile Crowdsourced Data

Mobile crowdsourced data is submitted by authenticated entities in the BDC system using either a file upload process (in the system's challenge process module) or a filer API. In addition, authorized mobile speed test app providers can submit consumer crowdsourced speed test results to the BDC system via an API. All mobile crowdsourced data must be submitted as tabular data file in a standardized format specified below.

Crowdsourced data may contain less information than required for mobile challenges, but otherwise will use the same data specifications and API specifications. Consumers and entities submitting crowdsourced data must provide identifying information and certify to the accuracy of the data.

2

Data Name Mobile Consumer Crowdsourced Data

Mobile Entity Crowdsourced Data

Parties Consumers

Service Providers Governmental Entities Other Entities

Description / Notes

Records of mobile speedtests or other mobile measurements (e.g., latency, signal strength, etc.) in tabular format.

- Note: providers will be notified when mobile consumer crowdsourced data have been submitted but such data do not, on their own, initiate the mobile challenge process or otherwise obligate a provider to respond.

Records of mobile speedtests or other mobile measurements (e.g., latency, signal strength, etc.) in tabular format.

- Note: providers will be notified when mobile entity crowdsourced data have been submitted but such data do not, on their own, initiate the mobile challenge process or otherwise obligate a provider to respond.

2.1.1 Mobile Consumer Crowdsourced Speed Test Data

This file must contain records of each mobile speed test. The file must be in JavaScript Object Notation (JSON) format and match the specifications provided in Section 5.

For crowdsourced data, the following Test Object attributes are optional if the test includes at least one type of test:

download upload latency

To account for limitations on the iOS platform, the following attributes are optional or have values that may be null when submitting crowdsourced data for devices running iOS:

Submission Object o device_tac o net_mobile_country_code o net_mobile_network_code o sim_mobile_country_code o sim_mobile_network_code

Download Test Object o carrier_aggregation_flag o network_connected_flag o network_available_flag o network_roaming_flag

Upload Test Object o carrier_aggregation_flag o network_connected_flag o network_available_flag o network_roaming_flag

3

 Latency Test Object o carrier_aggregation_flag o network_connected_flag o network_available_flag o network_roaming_flag

Cell Object o physical_cell_id o cell_connection o signal_strength o rssi o rsrp o rsrq o sinr o csi_rsrp o csi_rsrq o csi_sinr o cqi o spectrum_band o spectrum_bandwidth o arfcn

2.1.2 Mobile Entity Crowdsourced Speed Test Data

This file contains records of each mobile speed test in JavaScript Object Notation (JSON) format matching the specifications provided in Section 5.1. All attributes and values are required (unless the attribute is nullable and the value is null).

For crowdsourced data, the following Test Object attributes are optional so long as the test includes at least one type of test:

download upload latency

3 Challenge Process Data

3.1 Mobile Challenge Data

Speed test data for the BDC mobile challenge process can be submitted by authenticated entities in the BDC system using either a file upload process or a filer API. In addition, authorized mobile speed test app providers can submit mobile challenge speed test results from consumers into the BDC system via an API. All mobile crowdsourced data must be submitted as tabular data file in a standardized format specified below.

4

Challenge data submitted by consumers may be taken on iOS devices and therefore contain less information than is required for challenge data submitted by governmental or other entities, but in both cases challenge data must contain more information than required for crowdsourced data. Otherwise, the data will use the same data specifications and API specifications. Consumers submitting challenge data via mobile app must provide identifying information and certify to the accuracy of the data.

Data Name

Parties

Description / Notes

Mobile Consumer Challenge Consumers Speed Test Data

Records of mobile speedtests, including download, upload, and latency test metrics, challenging a provider's coverage data.

- Note: certain technical measurements are unavailable on iOS devices and thus are optional for consumer challenge data.

- Note: providers will be notified when mobile challenge data have been submitted and a challenge created. Once an area is challenged, providers have 60 days to respond.

Mobile Entity Challenge Speed Test Data

Service Providers

Governmental Entities

Other Entities

Records of mobile speed tests, including download, upload, and latency test metrics, challenging a provider's coverage data.

- Note: all technical measurements are required for entity challenge data, and thus entities cannot use iOS devices to submit such data.

- Note: providers will be notified when mobile challenge data have been submitted and a challenge created. Once an area is challenged, providers have 60 days to respond.

3.1.1 Mobile Consumer Challenge Speed Test Data

This file must contain records of each mobile speed test. The file must be in JavaScript Object Notation (JSON) format and match the specifications provided in Section 5.

To account for limitations on the iOS platform, the following attributes are optional or have values that may be null when submitting challenge data for devices running iOS:

Submission Object o device_tac o net_mobile_country_code o net_mobile_network_code o sim_mobile_country_code o sim_mobile_network_code

Download Test Object o carrier_aggregation_flag o network_connected_flag o network_available_flag o network_roaming_flag

5

 Upload Test Object o carrier_aggregation_flag o network_connected_flag o network_available_flag o network_roaming_flag

Latency Test Object o carrier_aggregation_flag o network_connected_flag o network_available_flag o network_roaming_flag

Cell Object o physical_cell_id o cell_connection o signal_strength o rssi o rsrp o rsrq o sinr o csi_rsrp o csi_rsrq o csi_sinr o cqi o spectrum_band o spectrum_bandwidth o arfcn

3.1.2 Mobile Entity Challenge Speed Test Data

This file must contain records of each mobile speed test. The file must be in JavaScript Object Notation (JSON) format and match the specifications provided in Section 5. All attributes and values are required (unless the attribute is nullable and the value is null).

4 Provider Response Data

4.1 Mobile Provider Response Data

Mobile service providers whose coverage data have been challenged may optionally submit either the results of mobile speed tests or infrastructure information as response data, along with other data relevant to rebut the challenge, or else concede the challenge. Mobile service providers that are the subject of an inquiry as part of the Commission's verification process must submit either the results of mobile speed tests or infrastructure information. Regardless of the type of data submitted in response to a challenge or verification inquiry, the Commission may subsequently require the mobile service provider to submit additional information if

6

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download