Docstoc

---------------------------------- Forwarded

Document Sample
---------------------------------- Forwarded Powered By Docstoc
					---------------------------------- Forwarded ---------------------------------From: walt.subora@ameritech.com ICC LNP testing meeting - Chicago 10/18/96 Attendees: Bill Belshaw MCI Metro Barry Bishop Ameritech Ralph Brown AT&T Any Chalk Sprint Joe Clark Bellcore Mack Dobkins US West Mitch Fuchs AT&T John Good Ameritech Ed Hendrix BellSouth OC Jackson AT&T Jim Marshall US West Robin Meier Ameritech Brent Struthers ICC Walt Subora Ameritech Meetings: Next two meetings for Nov 21 and Dec 11. Rooms to be provided by Barry Bishop. Conference call on Nov 4. 09:00 CST, 312-814-8097. Notes: 1. This committee owes a test schedule to the Operations Committee by 12/1. This will be major discussion at next meeting. 2. Barry Bishop's web site is www.ported.com. These notes will be posted there in Word6 format. Open question whether the draft test plan can reside there. Meeting Notes: I. Test Plan layout and test formats: A. AT&T put together proposal on how to think about the test plans. (in MSWord to make review easier. o Ralph: Since a lot of people not on this committee will have to execute tests, can those other people run the tests without a lot of explanations? B. O. C. Jackson, AT&T - review of script format. 1. Defined eight types of tests, up to 15 different scenarios or service combinations. 2. 8 tests for inter-LATA presub, 8 for dial-around, etc. - Request to add confirmation of AMA being acceptable to the service provider who gets the AMA record. C. Discussion: o question: how do inter-LATA calls fit in? They don't necessarily in the

Illinois test next year, but would in later tests. Might run some as part of the Illinois plan. o present structure is exhaustive, would have to do a thin sample to get a practical test. o Walt: An objective for this meeting: determine if the test script structure would be usable to a tester who has not been in on the planning. o Walt: since the objective is to prove the operational ability to provide service, rather than to prove exhaustive characteristics of the technology, we should use a very collapsed version of the tests as official tests for reporting. - e.g. Combinations like NP to NP for portable NXXs at both ends will be covered by setup, and shouldn't appear as separate test cases. - Each set of tests could apply to multiple network conditions. - (side note: how to do default routing in a live network? A couple of possibilities exist without killing links; will have to work it out.) o Only a fraction of the whole universe of tests will apply during any one test sequence at a particular location. Because each tester would run a fraction of all the tests, each company will have to do work to write compact procedures for their own testers. o Test plan for Illinois vs. generic test plan: We must define tests to satisfy MSA-1 for all participants. But this will be a small subset of any generic test plan. o One view: Generic plan to be defined by 12/1, then cut down to MSA-1-specific plan later. We want the specific plan to make it easy to produce reports for ICC and FCC. Very important for the plan to avoid the need for massive rework of the results at reporting time. Must keep in mind that schedule due to ICC Operations Committee by 12/01/96. o AT&T advocates proceeding with generic plan first. AT&T offers to draft the functional test sections in this way, with each generic test represented by about a half-page, as shown in the examples provided today. o Walt emphasizes that his primary focus is to get a proper MSA-1 test plan, and he supports a generic test plan to the extent that it helps to produce the MSA-1 plan. He opposes any generic plan work that stands in the way of the MSA-1 plan. - e.g. test cases involving IXC calls in the MSA-1 test plan should show all results for LSP, not just for IXC. - e.g. inter-LATA calls will be viewed as "ported to ported" being distinct from "non-ported to ported" in the generic plan. In the MSA-1 plan, there is no distinction if the originating LATA is distant. i.e. There is only one case called "IXC to ported".

o Exposed a difficulty in writing the test plan to meet everybody's interests. Should we continue to organize tests as LSP tests vs. inter-LATA carrier tests? Or should we organize tests as LSP-only tests vs. IXC-call tests, but with all LSP and IXC considerations included? - Discussion item - combinations of IXC switch, local switch and trunks: either switch can be LNP capable or not, and the trunks can be MF or SS7. Which combinations apply? - Obviously, "capable IXC to capable LSP via SS7", "capable IXC to non-capable LSP via MF", "non-capable IXC to capable LSP via MF". Are any others important? Is SS7 trunking to/from non-capable switches worth considering? Is it out of the question to have MF trunks between two capable switches? Etc. o Will discuss on the conference call. repeat: Assumption is that each service provider has taken care of the capability of its own network elements. This test is only proving operational abilities. Action Item 1: AT&T will provide drafts of IXC and LSP sections under 4.5 by 10/28 to allow review time before 11/4 conference call. It will be somewhat compacted in relation to the plan reviewed today. Action Item 2: Walt requests draft test plan contributions in Word 6.0 format on floppy disk, direct to Bill and direct to Walt. Working ASSUMPTION FOR THE REST OF TODAY: Use the AT&T format for test cases in each section. (PM session) Review of test script order with ownership indicated where appropriate. 4.1 Pre-test 4.2 Call-Through tests - rename to "Setup" Include the non-ported to non-ported cases here, not in 4.5. NPAC/SMS test plans to come from NPAC committee. 4.3 Provider to provider operations interfaces (using every-day interfaces) Operations team will provide. 4.4 Porting OA&M Everybody ports out, everybody ports in, but not every combination of port-from and port-to LSPs. Telephone numbers will be in section 2. 4.5 Service (functional) tests (old section 7) Embed cases for most CLASS features (e.g. Calling Name/Number delivery, Calling ID delivery blocking, Calling ID on Call Waiting?, CLASS Distinctive ringing screening list, customer originated trace?) in the straightforward tests. CLASS

Repeat-Call and Return-Call features will require separate tests. 4.6 Unique situations Bridged answering services - DROP. Tones & announcements - No special implications, any failure scenarios identified later will be added to 4.9. ISDN cases? some disagreement. US West offers to write up the proposed cases for ISDN. Voice mail: ported sub with voice mail on donor switch is the high-runner. Need to check bureau change of MWI for interoffice case. Ameritech will write Voice mail tests. Calling Card Validation goes to "Operator & Coin Services" section. 4.7 Cellular and PCS interconnection treat as non-capable, simple scenarios like incoming MF or incoming SS7 non-capable. No outgoing tests. Assume PCS same as cellular? Walt will talk to Operations Committee via Barry Bishop. 4.8 Operator & Coin (call it "Operator, Calling Card, and Coin") Port coin phones?? (probably not.) Mitch Fuchs will provide an answer. LIDB important because of global title distinction for originating line and LRN dip for destination line at OSS. Ed Hendrix will provide LIDB test cases, with input from Ralph Brown No pure DA 411/555-1212 impact. Complete-after-411 service is probably not different than pure operator call. Ed Hendricks or O.C. Jackson will provide cases if needed. They will work out how. O. C. Jackson will provide operator-assisted calls test cases. 4.9 (discussion of failure cases postponed for now) 4.10 Billing verification Put in a section with reference to AMA-related steps and validation of data from tests in 4.5 Specific AMA tests not envisioned. 4.11 Other EO and Tandem Non-capable EO and tandem will be covered under section 4.5. CAMA end offices probably needed. Andy Chalk will provide cases to include in 4.5 DID tests not provided - still needed? 4.12 NPA Splits Probably should be deferred: LNP platform may not be ready No NPA split scheduled in MSA-1. Ameritech will draft paragraphs to say why not included, unless work flows come through. 4.13 Code Gapping LRN ACG is a special case. Might not be in switches. Should

include in test plan anyway. LRN ACG works on dialed DN, pre-query, for 10-digit queries. Can set up to do default routing after LRN call gap. Switch-based (Netwk Mgmt) Code Controls: on dialed digits, pre-query, for 10-digit queries. on DN/LRN digits, post-query, for 6-digit queries. Walt Subora will provide test cases. 4.14 Choke Networks "891" choke network number won't be portable, but other LSPs can route their own choke codes to Ameritech tandem. Appears no test cases required for LNP. If any are, Barry Bishop will provide. Attached is Bill Belshaw's layout of each sub section, with numbering. Walt will use this for dissemination of the test plan updates when he sends out the disks for the 11/5/96 call.

Walt My notes as promised. Bill Test Script Order SECTION 4 4.1 Pre-test Pre LNP Test (from Section 1) (LNP Translations not used) 4.1.1 Switch 4.1.2 Station 4.2 Set-Up Call through tests with LNP translations in place (LNP Translations in switch, but numbers not ported) 4.2.1 SSP Tests (from Section 2) 4.2.1.1 SSP Functions 4.2.1.2 Translations 4.2.1.3 Trunk Testing 4.2.1.4 Industry Requirements 4.2.2 STP Tests (from Section 3) 4.2.2.1 STP Functions 4.2.2.2 Translations 4.2.2.3 Industry Requirements 4.2.3 Network Interconnections (from Section 5) 4.2.3.1 Equipment Capabilities 4.2.3.2 Network Configurations 4.2.4 NPAC, SMS & SCP (from Section 4) (Lockheed to furnish) 4.2.4.1 NPAC 4.2.4.2 SMS 4.2.4.3 LNP SCP 4.2.4.4 LNP Database (SCP) 4.3 Provider to Provider Interface (to be developed from OPs flows) (Inter-company communications channels) 4.3.1 Electronic Interface 4.3.2 Provisioning 4.3.3 Repair (from Section 12.5) 4.3.4 Conflict (from Section 12.6) 4.4 Porting and Operational Interfaces (Inter-company porting processes) 4.4.1 Porting Sequence (from Section 12.1) 4.4.2 Cancellation of Service order (from Section 12.2) 4.4.3 Disconnecting Ported Number (from Section 12.3) 4.4.4 Un-porting , return to donor (from Section 12.4) 4.4.5 Administrative Situations (from Section 13) 4.5 Service Tests (from Section 7) (Ralph Brown & Mitch Fuchs - ATT) (LNP translations in switches, test with ported numbers) 4.5.1 Basic Message Interaction 4.5.2 Features 4.5.3 CLASS Features

4.5.4 Special Number Interactions 800/888 4.5.5 900 - 500 Numbers 4.5.6 Enhanced Services 911 / E911 4.5.7 Other EO and Tandem (from Section 15) (Andy Chalk Sprint) (LNP translations in switches, test with ported numbers) 4.5.7.1 Tandem Interactions and Impacts 4.5.7.2 DID tests 4.5.7.3 Other Network Interactions 4.5.7.4 Industry or Standards Interaction

4.6 Unique Situations (from Section 8) (LNP translations in switches, test with ported numbers) 4.6.1 ISDN (Mack Dobkins USW) 4.6.2 Voice Mail and Voice Message Services (Walt Subora Ameritech)

4.7 Cellular and PCS Interconnection (from Section 9) (LNP translations in switches, test with ported numbers) 4.7.1 Cellular & PCS Services Basic Connectivity (Walt to discuss with Barry for discussion at Steering Committee 10/21)

4.8 Operator (OC Jackson ATT), Calling Card and Coin Services (from Section 10) (LNP translations in switches, test with ported numbers) 4.8.1 Call Routing 4.8.2 Vacant Number 4.8.3 Busy Line Verification 4.8.4 Coin Phone Initiated and Terminated Calls 4.8.5 Directory Assistance 4.8.6 Calling Card Validations (LIDB) (Ed Hendrix Bell South - Ralph and ATT to assist and bring information)

4.9 Failure Scenarios (from Section 11) (Using test switches, with ported numbers, lab to lab testing) 4.9.1 SSP Failure 4.9.2 LNP STP Failure 4.9.3 LSP SCP Failure 4.6.2 Tones and Announcements 4.10 Billing Verification (from Section 14) (to be validated internal by each company, usually proprietary information - no specific tests just results of other tests) (LNP translations in switches, test with ported numbers) 4.10.1 LIDB billing 4.10.2 Third party billing 4.10.3 Collect calls 4.10.4 900 - 500 billing 4.10.5 Coin billing 4.10.6 Hotel/Motel billing

4.10.7 Measured rate 4.10.8 Inter and Intra LATA (same and different carrier) 4.10.9 Special calling plans

4.11 NPA Splits (from Section 16) (Walt to provide description) (LNP translations in switches, test with ported numbers)

4.12 Gapping (from Section 17) (Walt to provide description, waiting for finalized test requirements) (LNP translations in switches, test with ported numbers) 4.12.1 Switched Based 6 digit 10 digit 4.12.2 ACG (SCP)

4.13 Choke Networks (from Section 18) (Walt to get exiting tests, choke networks to be done as usual) (LNP translations in switches, test with ported numbers)


				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:6
posted:11/22/2009
language:English
pages:8