↑ arvau

Wikipedia / Local Access and Transport Area

Local Access And Transport Area (LATA) is a term defined in United States telecommunications regulation. A LATA is a geographical area of the United States under the terms of the Modification of Final Judgment (MFJ) entered by the United States District Court for the District of Columbia in Civil Action number 82-0192 or any other geographic area designated as a LATA in the National Exchange Carrier Association, Inc., Tariff FCC No. 4, that precipitated the breakup of the original AT&T into the "Baby Bells" or created since that time for wireline regulation.

Generally, a LATA represents an area within which a divested Regional Bell Operating Company (RBOC) is permitted to offer exchange telecommunications and exchange access services. Under the terms of the MFJ, the RBOCs are generally prohibited from providing services that originate in one LATA and terminate in another.

LATA boundaries tend to be drawn around markets, and not necessarily along existing state or area code borders. Some LATAs cross over state boundaries, such as those for the New York metropolitan area and Greenwich, Connecticut; Chicago, Illinois; Portland, Oregon; and areas between Maryland, Virginia, and West Virginia. Area codes and LATAs do not necessarily share boundaries; many LATAs exist in multiple area codes, and many area codes exist in multiple LATAs.

Originally, the LATAs were grouped into regions within which one particular RBOC was allowed to provide services. The LATAs in each of these regions are numbered beginning with the same digit. Generally, the LATAs were associated with carrierss or other indications in the following manner:In addition to this list, two local carriers were made independent: Cincinnati Bell in the Cincinnati area, and SNET (a former unit of AT&T, sold to Frontier) in Connecticut. These were assigned LATAs in the 9xx range.

Since the breakup of the Bell System in 1984, however, some amount of deregulation, as well as a number of phone company mergerss, have blurred the significance of these regions. A number of new LATAs have been formed within these regions since their inception, most beginning with the digit 9.

LATAs contribute to an often confusing aspect of long-distance telephone service. Due to the various and overlapping regulatory limitations and inter-business arrangements, phone companies typically provide differing types of “long distance” service, each with potentially different rates:

  • within same LATA, within same state

  • within same LATA, between different states

  • between different LATAs, within same state

  • between different LATAs, between different states

Given the complexity of the legal and financial issues involved in each distinction, many long-distance companies tend to not explain the details of these different rates, which can lead to billing questions from surprised customers.

Local carriers have various alternative terms for LATAs such as “Service Area” by Pacific Bell in California, or “Regional Calling Area” by Verizon in Maryland.

To facilitate the sharing of Telcordia telephone routing databases between countries, LATAs were later defined for the provinces of Canada, the other countries and territories of the North American Numbering Plan, and Mexico. Aside from U.S. territories, LATAs have no regulatory purpose in these areas. In 2000, the Canadian Radio-television and Telecommunications Commission eliminated all Canadian provincial LATAs in favor of a single LATA for Canada (888).

No LATAs exist with a second digit of 0 or 1, which distinguished them from traditional area codes.

List of LATAs

US state LATAs

The city or place name given with some LATAs is the name given to identify the LATA, not the limit of its boundary. Generally this is the most significant metropolitan area in the LATA. In some cases, a LATA is named after the largest phone exchange in the LATA that was historically served by an RBOC. For example, the largest city in the Pahrump LATA in Nevada is Las Vegas. Since Las Vegas was not historically served by an RBOC, the LATA is named after the smaller town of Pahrump, which was historically served by Nevada Bell (now AT&T Inc.). Also, listing under a state does not necessarily limit the LATA's territory to that state; there may be overlaps as well as enclaves. Areas that include notable portions of other states are explained, but not all LATA state overlaps may be detailed.

LATA boundaries are not always solidly defined. Inter-carrier agreements, change proposals to the Federal Communications Commission (FCC), and new wiring developments into rural areas can and do often alter the effective borders between LATAs. Many sources on LATA boundary information conflict with each other at detailed levels. Telcordia data may provide the most up-to-date details of LATA inclusions.

Alabama

478 Montgomery

480 Mobile

Alaska

  • 832

Arizona

666 Phoenix

668 Tucson

980 Navajo Nation (Arizona portion)

Arkansas

526 Fort Smith

528 Little Rock

530 Pine Bluff

California

730 Los Angeles

Colorado

Connecticut

  • 920

Washington, D.C.

236

Florida

448 Pensacola

450 Panama City

Georgia

438 Atlanta

440 Savannah

442 Augusta

Hawaii

  • 834

Idaho

652 Southern Idaho

960 Coeur d'Alene

Illinois

358 Chicago

360 Rockford

370 Champaign

Indiana

336 Indianapolis

937 Richmond

938 Terre Haute

Iowa

630 Sioux City

632 Des Moines

634 Davenport

Kansas

Kentucky

462 Louisville

Louisiana

Maine

  • 120

Maryland

  • 236 see Washington, D.C.; most of this LATA is actually in Maryland

  • 238 Baltimore

240 Hagerstown

Massachusetts

  • 126 Western Massachusetts

  • 128 Eastern Massachusetts

Michigan

342 Upper Peninsula of Michigan

Minnesota

Mississippi

482 Jackson

Missouri

520 St. Louis

  • Includes part of south-central Illinois southwest of Springfield.

  • 521 Westphalia (per locallingguide.com, includes Columbia MO)

  • 522 Springfield

524 Kansas City

  • Includes eastern portion of Kansas as far out as U.S. 73 and U.S. 59 and south as far as U.S. 54

  • 521 Central Missouri: Columbia and surrounding areas

Montana

963 Kalispell (historical)

  • note: LATA 963 appears on many LATA lists, and at least one map, but is no longer a separate LATA-equivalent area. It is now part of LATA 648.

Nebraska

Nevada

720 Reno

New Hampshire

122

New Jersey

New Mexico

  • 664

New York

132 New York City and surrounding metropolitan area

  • Includes Greenwich, Connecticut

133 Poughkeepsie

  • Includes Milford, Pennsylvania and surrounding area

134 Albany

138 Binghamton

  • Includes Sayre, Pennsylvania and surrounding area

140 Buffalo

North Carolina

422 Charlotte

North Dakota

638 Bismarck

Ohio

922 Cincinnati

Oklahoma

Oregon

672 Portland

Pennsylvania

Rhode Island

  • 130 Rhode Island

South Carolina

430 Greenville

South Dakota

  • 640

Tennessee

468 Memphis

472 Chattanooga

956 Bristol-Kingsport-Johnson City

Texas

546 Amarillo

554 Longview, Kilgore

Utah

660 Utah

Vermont

124 Vermont

Virginia

Washington

676 Spokane

West Virginia

  • 254 Charleston

  • 256 Clarksburg

  • 240 Martinsburg

  • 932 (overlap with VA)

Wisconsin

350 Northeast Wisconsin

  • Includes the southern corner of Michigan's Upper Peninsula

  • 352 Northwest Wisconsin

  • 354 Southwest Wisconsin

  • 356 Southeast Wisconsin

Wyoming

  • 654 Wyoming

U.S. territory LATAs

Non-U.S. LATAs (non-regulatory)

Canada

As LATAs exist for US regulatory purposes, where they serve as a demarcation between intra-LATA calls (handled by regional Bell operating companies) and inter-LATA calls (handled by interstate long-distance carriers such as AT&T), they have no legal significance in Canada.

As of 2000, all of Canada (except for non-geographic numbers) is identified as LATA 888.

The use of this LATA set to identify individual provinces is therefore deprecated:

Local interconnection region

Canada does define local interconnection regions (LIR's), which determine where points of interconnection (POI) must be provided by competing local exchange and mobile carriers to provide local number portability. A Canadian LIR is geographically smaller than a US LATA, typically comparable in size to a small city's flat-rate local calling area or to an entire large regional municipality. In areas where a small-city Digital Multiplex System controls a group of remote switching centres, one for each surrounding village, the local interconnect region normally includes each exchange in the city plus all downstream remotes of those exchanges. In a Toronto-sized city, the LIR will include only the city itself.

While the LIRs resemble local calling areas in geographic size, there are some key differences:

  • LIR's normally do not include incumbent local independent telephone company exchanges in locations not opened to competition, where the independent numbers are currently not portable.

  • LIR's do not cross provincial boundaries. Lloydminster has an LIR for each province, as does Ottawa-Hull.

  • LIR's closely follow network topology, which often does not match a local flat-rate calling area as local calling is defined by arbitrary regulatory constructs.

Example: The tiny unincorporated village of Beebe Plain, divided by the Quebec-Vermont border, is served by +1-819-876 Rock Island, Quebec, Canada (a remote station controlled from Magog) and +1-802-873 Derby Line, Vermont, USA (a remote station controlled from St. Johnsbury). Magog and St. Johnsbury are both a long-distance call from anywhere in Beebe Plain, even though Canadian subscribers can place local calls to Sherbrooke, US subscribers can locally call Newport and an international call within the village is local. An LIR assignment which follows network topology places the Canadian remote station in Magog's LIR, not Sherbrooke's LIR.

See also

Notes