GR 2970 CORE : ISSUE 1

1. Introduction
   1.1 Purpose and Scope
   1.2 Limitations
   1.3 Target Audience
   1.4 End User Perspective
   1.5 Review/Concurrence Information
   1.6 Structure and Use of This Document
   1.7 Requirements Terminology
   1.8 Requirement Labelling Conventions
2. Overview
   2.1 Overview of LSPI
   2.2 Drivers for LSPI Capability
   2.3 Definitions
   2.4 Assumptions
   2.5 Format of LSPI
   2.6 LSPI Call Model
   2.7 Sample Call Scenarios
3. LSPI Provisioning Requirements
   3.1 LSPI Provisioning Overview
   3.2 Per Switch LSPI Network Capability Control
       Requirements
   3.3 Per Switch LSPI Recording Options
   3.4 Per-LSPI Value Screening and Recording Options
   3.5 Associating Directory Numbers With LSPI
   3.6 Associating a Trunk Group with a LSPI
   3.7 LSPI Query and Reporting Capabilities
4. Common Channel Signalling
   4.1 ISDNUP Requirements for Service Provider
       Identification
   4.2 Generic Requirements
   4.3 Local Service Provider Identification
5. Usage Measurements
   5.1 Working Assumptions for AMA
   5.2 General AMA Recording Options
   5.3 Office-Wide AMA Recording Requirements
   5.4 LSPI-specific AMA Recording Options
   5.5 AMA Requirements for the Originating Switch
   5.6 Generating New LSPI Intraswitch Originating AMA
   5.7 Originating Interswitch Calls
   5.8 Generating BAF Structure Code 0001
   5.9 AMA Requirements for the Intermediate Switch
   5.10 Population Rules for New AMA at an Intermediate
        Switch
   5.11 AMA Recording Options for the Terminating Switch
Appendix A: Operator Services, LIDB, AIN and CLASS
            Interactions
            A.1 Operator Services
            A.2 LIDB
            A.3 AIN
            A.4 CLASS
            A.5 800/888 "Toll-Free" Service
            A.6 Queries to obtain LSPI-XX
Appendix B: LSPI Codeset Considerations
            B.1 Purpose of Local Service Provider
                Identification (LSPI)
            B.2 Identification of Service Providers
                - Current Methods
            B.3 Existing Databases/Processes
            B.4 Candidates for LSPI
            B.5 Using the Bellcore OCN/NECA Company Code
            B.6 OCN/NECA Code Assignments as LSPI
Appendix C: Acronyms
References
Requirement-Object Index
Requirement-Object List
List of Figures
2-1. Samples of Trunk group Types from an
     LSPI Perspective
2-2. LSPI Call Model
2-3. Originating Call from a Resold DN
2-4. Identification of a Resold Line from a
     Non-LSPI-Capable Switch
2-5. Identification of a Non-LSPI-Capable Switch Owner
2-6. Passing LSPI Information through an Intermediate
     Network
3-1. General LSPI Switch Options
4-1. Trunk Setup and Backward Signalling Diagram
4-2. Identification of Trunk Groups and Signalling Links
     in Figure 4-1
4-3. Local Service Provider Identification Parameter
     (Parameter name code: (XXXX XXXX))
4-4. Encoding Scheme
4-5. LSPI Type
4-6. Context Identification
5-1. Decision Tree for Populating BAF Module 338 for
     ODNAO and ODNSO at the Originating Switch
5-2. Decision Tree for Populating Module 338 for TDNAO
     and TDNSO at
     (1) an Originating Switch for Intraswitch Calls and
     (2) at a Terminating Switch
5-3. Decision Tree for Populating Module 104 - Table 244
5-4. Decision Tree for Populating Module 338 for TDNAO and
     TDNSO for Interswitch Calls - Originating and
     Intermediate Switches
5-5. Decision Tree for populating Party Identifier for
     Incoming Trunk Group Account Owner
5-6. Decision Tree for Populating Module 338 for ODNAO and
     ODNSO at Intermediate and Terminating Switches
A-1. Potential LSPI Information Available at an OSS During
     an Operator Services Call

Defines Telcordia's view of the switching and signalling generic requirements for Local Service Provider Identification (LSPI) which identifies the entity providing local service to a Directory Number (DN) or to a trunk group transport facility. It is intended to improve the capabilities of all telecommunication networks to offer and bill services supplied by multiple companies in an environment where the line or trunk group can be owned on a native, resold, or unbundled basis.