BELLEVUE, WASH.—Shortly after the Federal Communications Commission approved the first use of unlicensed LTE in the 5 GHz band, T-Mobile announced it would launch LTE-U over its network by this spring. On Tuesday, the FCC approved of the first use of unlicensed LTE in the 5 GHz band with equipment modification grants for Ericsson and Nokia, both equipment partners of the carrier.
Referring to itself as the “un-carrier,” T-Mobile said it is “now deploying LTE-U technology in its LTE network, following today’s FCC certification of equipment from strategic partners Ericsson and Nokia. This move paves the way for the Un-carrier to introduce new network capabilities and devices for consumers this spring.”
T-Mobile, the third largest cell-service provider in the United States behind Verizon and AT&T, said it started field trials of LTE-U last December. LTE-U devices are said to be able to share spectrum with Wi-Fi without disruption to that service.
“LTE-U devices and equipment intelligently tap into and share underutilized unlicensed spectrum without affecting other users on the same band, including those using conventional Wi-Fi. LTE-U constantly seeks the least utilized channels to maximize efficiency and performance for everyone. As demand on the Wi-Fi network increases, LTE-U backs off, and as Wi-Fi demand wanes, customers can tap into that unused capacity for LTE,” T-Mobile said.
Feb. 23, 2017
“Verizon Aims to Deploy 5G Pilot Programs in 11 Markets by Mid-2017”
Verizon intends to launch “pre-commercial” 5G in Ann Arbor, Mich.; Atlanta, Bernardsville, N.J.; Brockton, Mass.; Dallas, Denver, Houston, Miami, Sacramento, Seattle and Washington, D.C.
Feb. 22, 2017
“FCC OK’s First Unlicensed LTE in 5 GHz”
There was no specific public notice on the action, but rather a couple of equipment modification grants for Ericsson and Nokia.
Future US's leading brands bring the most important, up-to-date information right to your inbox
Thank you for signing up to TV Technology. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.