Invitation to Participate

GR-1188-CORE and GR-3103-CORE
LSSGR: CLASS^SM Feature: Calling Name Delivery Generic Requirements (FSD 01-02-1070), Issue 3; and Lightweight Directory Access Protocol (LDAP) Interface Specification for Line Information Database (LIDB), Issue 4

Contact:

GR-1188 contains switching and signaling generic requirements for Calling Name Delivery (CNAM) for residential and small business customers, as well as for Basic Business Group (BBG) and Multiswitch Business Group (MBG) customers. The current scope of the features described in this document is limited to conventional lines. Name database application generic requirements could be provided in future documentation. The purpose of the proposed update is to enhance CNAM to make it more accessible and useful to a larger IP population.

This effort, while mainly focused on GR-1188, will include clarifications to one or more of the following GRs:

• GR-1158, OSSGR Section 22.3: Line Information Database
• GR-446, Generic Requirements for the Line Information Database (LIDB) Administrative System (AS)-LIDB Interface
• GR-2838, Generic Requirements for GetData
• GR-3697, Volumes I & II, Data Screening Generic Requirements
• GR-1149, OSSGR Section 10: System Interfaces.

The Key Generic Value of Call Name Delivery (CNAM) Enhancement

• Longer than 15-character Calling Name – Calling Name is one of the most popular services for LIDB owner companies. As the industry evolves to newer technologies, LIDB customers, especially the non-traditional, IP customers, would find it valuable to retrieve and display untruncated, full names for their CNAM subscribers. GR-1188 would need to be updated with "objectives" and/or a separate section containing "Name-database application-specific requirements" to store/return more than 15-character names. The goal is to allow new Query Originators / Clients / Hub providers to access the database and retrieve Names regardless of the length (i.e., without a maximum limitation of 15 characters). This adds value to the CNAM product offering to non-traditional customers such as Cable/VoIP providers. This capability would enable CNAM providers to attract additional customers.
  Audience: The majority of non-traditional LIDB customers are Cable companies and facilities-based CLECs interfacing with VoIP providers; therefore, the general audience would be new CNAM/ wireless CNAP, query originators, IP-based Cable/VoIP providers, Hub providers, LIDB owners, and Suppliers.

GR-3103, Lightweight Directory Access Protocol (LDAP) Interface Specification for Line Information Database (LIDB), contains the Lightweight Directory Access Protocol (LDAP) Interface Specification for Line Information Database (LIDB). With its current data on the majority of the working telephone lines, LIDB is a valuable database and resource for a number of diverse industries.

This GR allows an LDAP Client to understand the available/supported capabilities in a LIDB for LDAP requests. It is the initial version of such an interface; therefore, not all of the standard LDAP functionalities (listed in RFC 2251) are supported within.

This effort, while mainly focused on GR-3103, will include clarifications to the following GR:

• GR-3697, Volume II, Data Screening Generic Requirements for LDAP.

The Key Generic Value of LIDB-LDAP Enhancement

• Add LDAP Compare Functionality in LIDB – The LIDB-LDAP interface enables IP-based service providers and/or business/enterprise clients to supplement their service offerings with broader customer profiles stored in the LIDBs. These clients or LIDB customers demand additional capabilities such as to match/mismatch data in addition to plain interrogation or data retrieval capability that LIDB supports today. This work effort would add the capability to support LDAP compareRequest and compareResponse messages via the LDAP-LIDB interface. The results of this effort would enhance LIDB's capability to meet today's market needs by supporting the capability to send, for example, a Name match/mismatch or an Address match/mismatch in the response. This capability, if supported, would help LIDB stay competitive in today's marketplace.
  Audience: Non-traditional LIDB customers such as data aggregators, verification data companies, LIDB owners, and Suppliers.

Pursuant to provisions of the Telecommunications Act of 1996, related to the development of industry-wide generic requirements, Telcordia invites all interested parties to participate in this GR project. If your company is interested in participating in this activity, please contact Telcordia. The resulting document(s) will only be available through the purchase of an Enterprise License. Such a license is included in the participation fee for this GR project.

To proceed with this LIDB-related GR project, it is expected that Telcordia will need at least two industry participants. While the project can proceed with fewer participants, deliverables may change as a result. The participating industry members will be apprised regularly of project status and any changes in deliverables.