Common Language Information Services

Common Language Information Services encompasses several products that are in general use by the global telecommunications industry through license agreements. Common Language products combine numerics and mnemonics to establish naming conventions that telecommunication companies use to exchange critical information via Operations Support Systems and other interface mechanisms.

Common Language codes help communications companies name, locate, inventory and manage all aspects of their networks.[1] They identify items as large as a building, as small as a single board in a digital switching machine and as complex as a customer circuit.[2] Telcordia manages the registry for all Common Language codes on behalf of the telecommunication service providers industry.

Common Language code sets are recognized by industry standards bodies and organizations, including ATIS,[3] ANSI,[4] IETF,[5] and ETSI.[6]

Common Language Codes

Following are Common Language codes used by the telecommunications industry.

CLEI Codes

Common Language Equipment Identifier or CLEI code is an industry standard, globally unique identifier[7] for telecommunications equipment with a uniform feature-oriented classification. CLEI codes must be acquired by telecommunications equipment manufacturers and assigned to devices before they are sold to a licensed service provider.[8]

CLLI Codes

A Common Language Location Identification or CLLI code identifies buildings that contain telephony equipment, network facilities housed in those buildings and non-building sites such as poles and manholes.[9][10] By labeling the equipment functionality, office number, city, and state in a CLLI code, a telecommunication company’s central office can keep this information on and immediately reference any particular item when necessary. This information can be used for making repairs, replacing old equipment, ordering phone service, recovering call detail records, and assisting in tracing calls.[11]

CLCI S/S

Special Service Circuit or CLCI S/S codes provide a coded designation for a service that is dedicated and billed to a particular customer.[12]

CLCI MSG

Message Trunk Circuit or CLCI MSG codes provide a naming scheme for message trunk circuits.[13] These codes identify individual trunks and trunk groups by number, office class, traffic use, trunk type modifier, signaling, and the originating and terminating office locations.

CLFI

Common Language Facility Identification or CLFI Codes provide a standard, mnemonic naming scheme to uniquely identify cable and transmission facilities between two standardized locations (identified via CLLI codes) within a network. It comprises facility designation, facility type, channel/pair/time slot, location of facility terminal A and location of facility terminal Z.

NC/NCI

Network Channel/Network Channel Interface or NC/NCI codes are used to communicate technical attributes of services, facilities[14] and their associated interfaces to support interconnections between telecommunications service providers through the use of the Access Service Request (ASR) process.

Service Order Process

The service order process utilizes the USOC, USO and Field Identifiers (FIDs), to provision, bill and maintain services and equipment.[15] Universal Service Order or USO Codes are used by telecommunications service providers to collect and structure all the information needed for service activation, including ordering, provisioning, service assurance and billing. USOC codes, also known as rate elements, are used by telecommunications service providers to identify each billable element of a customer’s service.[16] Field Identifiers or FIDs are used by telecommunications service providers to identify a billing preference or attribute of a customer’s account.[17] FIDs define the technical parameters required to provision and bill a customer’s service beyond those described in USOCs.

General Codes

General Codes provide a naming scheme that applies across the industry to identify company names, equipment frames, service centers, design routes, signaling types, circuit switch originating equipment, distributing frame cross-connect points and standard abbreviations.

See also

References

  1. "A common language". Connected Planet. Retrieved 2012-06-08.
  2. "A common language". Connected Planet. Retrieved 2012-06-08.
  3. "Intercompany Responsibilities in the Telecommunications Industry" (PDF). ATIS Standard. Retrieved 2012-06-08.
  4. "A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code". Network Working Group. Retrieved 2012-06-08.
  5. "A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code". Network Working Group. Retrieved 2012-06-08.
  6. "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Equipment Information in the Management Information Base (MIB)" (PDF). ETSI TS 102 359 V1.2.1. Retrieved 2012-06-08.
  7. "A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code". Network Working Group. Retrieved 2012-06-08.
  8. "CLEI Codes". PowerSource Online. Retrieved 2012-06-08.
  9. "A common language". Connected Planet. Retrieved 2012-06-08.
  10. "Intercompany Responsibilities Within The Telecommunications Industry" (PDF). ATIS/NIIF 0015 Issue 1.0. Retrieved 2012-06-08.
  11. "CLLI Codes". Tech-FAQ. Retrieved 2012-06-08.
  12. "Bellcore to license Common Language codes to Telmex". Company Press Release. Retrieved 2012-06-08.
  13. "Bellcore to license Common Language Message Trunk Circute Codes: CLCI MSG Codes". Common Language Website. Retrieved 2012-06-08.
  14. "Common Language NC/NCI Information Services" (PDF). Common Language Website. Retrieved 2012-06-08.
  15. "Telecom Glossary". Telapprise Website. Retrieved 2012-06-08.
  16. "Telcordia Automates USOC Searches". Billing & OSS World. Retrieved 2012-06-08.
  17. "AT&T Billing Guide" (PDF). AT&T Company Website. Retrieved 2012-06-08.
This article is issued from Wikipedia - version of the Saturday, April 18, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.