Hardware and Software Requirements for Collecting Bulk Mobile Speed Tests

Updated December 06, 2022 12:53

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 crowdsource data or as part of the mobile challenge process may use their own hardware or software to collect mobile speed test data. Such bulk speed test data must be submitted in the BDC system by uploading a file that conforms to the specifications detailed below. An entity submitting such data must first log in and register in the BDC system.

Entities must provide certain information when using their own hardware or software to collect on-the-ground data and must submit on-the-ground speed test data that meets the same metrics and parameters as that submitted by consumers using the FCC Speed Test App and any other apps approved by the FCC, which may be found in the Data Specifications for Mobile Speed Test Data. They must submit a complete description of their data collection methodology and have their information certified by a qualified engineer or official.

Entities must also provide a narrative overview of the testing solution including, if available, a description of the test methodology and a URL link to the test solution product. They should also include, if available, product images, sample reports from test campaigns conducted using this product, and any other information that is useful in determining the product test and measurement capabilities.

In addition to a narrative overview, entities must also submit the specific information, described in the table below, about their test methodologies using a web form in the BDC system.

Entity Mobile Testing Methodology Data

Filers are required to enter a description of the testing methodology that was used to collect the Entity Mobile Crowdsource/Challenge Information.

Field	Data Type	Example	Description / Notes
Methodology ID	String	Acme Wireless Drive Test – Team B	Unique name identifying the testing methodology used to collect the mobile speed test data
Narrative	File Upload		Narrative explanation of the methodology used to conduct the mobile speed tests. -File must be a valid Word Document (.DOC/.DOCX), OpenDocument (.ODF), Portable Document Format (.PDF), or plain text (.TXT) file.
Category	Enumerated	App-based	Category of testing methodology. -Value must be one of the following: App-based Software-based Hardware-based
Supported Technologies	Enumerated	4G LTE 5G-NR NSA 5G-NR SA	List of radio access technologies supported by the device(s) used for testing. -Value(s) must be one or more of the following: 3G 4G LTE 5G-NR NSA 5G-NR SA
Testing Environment	Enumerated	In-vehicle	Testing environment used for the test setup. -Value must be one of the following: In-vehicle Outdoors
Antenna Type	Enumerated	External	Type of antenna used for the test setup. -Value must be one of the following: External Internal
External Antenna Height	Decimal	0.5	Height of external antenna in meters. -Value must be ≥ 0 if the Antenna Type value is “External”. -Value must be null if the Antenna Type value is “Internal”.
Data Plan Type	Enumerated	Unlimited (Not Subject to any Data Usage Management)	Type of data plan used by the devices. -Value must be one of the following: Unlimited (Subject to Typical Consumer Data Usage Management) Unlimited (Not Subject to any Data Usage Management) Other
Data Plan Description	String		Description of data plan used by the device(s) in the test setup. -Value may be null unless the Data Plan Type value is “Other”.

Entity Mobile Test Servers Data

Filers are required to enter a description of the test servers corresponding to the methodology used to collect the Entity Mobile Crowdsource/Challenge Information.

Field	Data Type	Example	Description / Notes
Server ID	String	Acme Wireless Stackpath Cloud	Unique name identifying the test server record.
Server Count	Integer	15	Minimum count of test servers available for transmitting data for a speed test.
Server Type	Enumerated	Geographically-distributed / Nationwide Test Servers with Common Configuration	Type of test server(s) for which the test record applies. -Value must be one of the following: Geographically-distributed / Nationwide Test Servers with Common Configuration Non-distributed / Region-specific Test Server(s)
Server Location – State	Enumerated		State or territory in which the test servers are located. -Value must be null if the Server Type value is “Geographically-distributed / Nationwide Test Servers with Common Configuration”. -Value must be a valid state or territory from the latest U.S. Census Bureau data if not null.
Server Location – County	Enumerated		County or other subdivision within the state or territory in which the test servers are located. -Value must be null if the Server Type value is “Geographically-distributed / Nationwide Test Servers with Common Configuration”. -Value must be a valid county or county-level subdivision for the selected state from the latest U.S. Census Bureau data if not null.
Server Capacity – Incoming	Decimal	100.0	Minimum one-way provisioned capacity of test server link in Gbps given capabilities of existing hardware – incoming to the test server. -Value must be > 0.
Server Capacity – Outgoing	Decimal	100.0	Minimum one-way provisioned capacity of test server link in Gbps given capabilities of existing hardware – outgoing from the test server. -Value must be > 0.
Server Client – Type	Enumerated	iPerf	Type of client software running on the test server(s). -Value must be one of the following: iPerf Ookla Other
Server Client – Description	String		Description of the client type used by the test server(s). -Value may be null unless the Server Client Type value is “Other”.
Server Client – Protocol	Enumerated	TCP	Transport layer network protocol used by the client software running on the test server(s). -Value must be one of the following: TCP UDP SCTP Other
Server Client – Port	Integer		Network port used by the client software running on the test server(s). -Value may be null.
Server Client – Buffer Length	Integer		Buffer length used by the client software running on the test server(s). -Value may be null.
Server Client – Max Connections	Integer		Maximum number of simultaneous connections allowed by the client software running on the test server(s). -Value may be null.
Server Client – Configuration Description	String		Description of any other configuration of the client software running on the test server(s). -Value may be null.

Articles in this section