All,
This is to inform you of the test team conf. call this friday.
When: 03/21/97
Time: 09:00 to 12:00 CST
DialIn: 312-814-8097
Be prepared to talk about the topography of the Illinois FCC Field Trial
including DNs, Point Codes, etc. Also be prepared to start the
discussion on the trunking arrangements needed for the trial.
Also, attached is the writeup from the ICC SCP team about the test plan
portions they have reviewed. If time permits, we should have some
discussion on our response to these for the 04/08 meeting with them.
Walt Subora
walter.subora@ameritech.com
847-248-5418 (ph)
847-248-6746 (fax)
2000 W. Ameritech Dr.
1D50
Hoffman Estates, Il 60196-1025
Illinois LNP SCP Subcommittee Notice: Conference Call Tuesday, March
25, 1997
Our next conference call will be Tuesday, March 25, 1997 from 10 am
to noon CST. The call in number is 800-836-8184, passcode 365259.
Our face to face meeting will be in Chicago on the afternoon of
April 7 (from 1 pm to 5 pm) and morning of April 8. For the
afternoon of April 7 we will be meeting at the Ameritech Training
Center (350 N. Orleans). For the morning of April 8 we will be
meeting at AT&T building in downtown Chicago. The afternoon of
April 7 we will be meeting as the SCP requirements subcommittee.
The morning of April 8 we will be meeting jointly with the Testing
subcommittee. (The Testing Subcommittee meeting will continue the
afternoon of April 8 and all day April 9, for those that want to
stay on. April 10 & 11 will the Operations subcommittee meetings,
also in downtown Chicago.)
Following transmissions will distribute the open issues from Barry
Bishop's Operations Subcommittee, the comments on our document from
the Oregon & Washington SCP subcommittee, and other comments I've
received. I'm also locating the failure information developed by
the Operator Services subcommittee a while ago.
One of the issues we've decided to revisit is applications
availability. Our document currently recommends the LNP
applications be unavailable to the network for no more than 20 hours
per year. This is different than the SS7 availability of the
platform. There have been suggestions that the applications
availability meet current SS7 availability guidelines (unavailable
for no more than 3 minutes per year). This is one of the issues
from Oregon/Washington.
At our last call (3/11) we reviewed Section 3 of the testing
document (Issue 1).
From the previous list, we've decided the following sections are not
of interest to our group:
- Section 3.4 Porting Process
- Section 3.5.2 Features & Services
- Section 4.5.2 Features & Services
- Section 4.5.7 InterLATA calls
The following Sections presented downloading and decoding problems:
- Section 4.5.8 AIN
- Section 4.8 Operator Services
- Section 4.10 Billing
- Section 4.12 NPA Splits (not sure if this relates to our
group's activities)
- Appendix A Test Plan Diagrams
Comments from the call on existing portions of Section 3:
Section 3.2.2 STP Functionality: This section should be revised to
indicate that it describes STP functions in support of the LRN
query. We recommend a new section (3.2.X) for "GTT Functions for
Message Routing in a Portable Environment". This new section would
describe the LNP GTT function that is needed to support routing of
messages for LIDB, CNAM, CLASS and ISVM.
Section 3.2.3 Network Interconnections: This section should include
references to internetwork routing of LRN queries, and to
internetwork routing of SS7 messages for services (CLASS, CNAM,
LIDB, ISVM).
Section 3.2.4.2 SMS: Need content in this section. Should indicate
that "SMS" is carrier's system which receives downloads from NPAC.
SMS needs to support NPAC interface, respond to NPAC audit, etc. In
turn "SMS" needs to support data tables in LNP Application and LNP
GTT Function.
Section 3.2.4.4.1: Delete the parenthetical comment. 10 digit
translations are independent of LRN queries.
Need a new section 3.2.4.4 "LNP GTT Function", to address the
platform which supports the LNP GTT function (could be an STP or SCP
platform, or other comparable system).
Section 3.5.3 CLASS Services: Need to add references to Screening
List Editing. Not sure whether this should be its own subsection,
or included under the "selective" services. Screening List Editing
generates interswitch messages that need to be routed by an LNP GTT
function.
Section 3.5.8 AIN Interactions: Need to develop material that
identifies known interactions between AIN and LNP. (Wayne will work
on text.)
Section 3.6.1 Voice Mail: Need to note there are three DNs which can
be associated with a voice mail service: the user DN, the voice mail
trunk DN, and the DN associated with the SMDI link. Testing should
address the case between the user DN and trunk DN (one or the other
ported, or both ported), and the case where between the user DN and
the SMDI DN (one or the other ported, both ported).
Section 3.8 Operator Services: Subsections on "Bill to Third",
"Collect", and "Calling Card" need to reference queries to LIDB, and
need for LNP GTT function to correctly route LIDB queries for LNP.
Some operator services platforms might also generate LIDB queries to
perform "originating line number screening", an optional capability
not supported by all operator service providers. Operator services
platforms will perform LRN queries to obtain LRNs to include in
billing recordings. Some platforms may also perform LRN queries to
obtain location information when providing rate quotes.
Section 3.9 Failure Scenarios: We would like to see the test plan
address both LRN query failure and LNP GTT failure situations.
These failures have internetwork impacts that can't be tested in the
lab or single network environment. Need to expand on the failure
scenarios listed. Need to add a new subsection 3.9.4 on LNP GTT
Function failures.
Section 3.10.1 should be re-titled "Calling Card" billing.
Section 3.10.2 and 3.10.3: LIDB queries can be associated with "bill
to third" and "collect" calls.
Section 3.12 NPA Splits: Testing should verify NPAC downloads only
apply when the LRN associated with a ported user migrates to a new
NPA. Internal processes are expected to migrate all other records
for ported customers. Testing should verify LRN queries and
messaging for services (LIDB, CNAM, CLASS, ISVM) for both old and
new NPA during permissive period, and rejection of old NPA after
permissive period.
Section 3.13 should be retitled "Network Management". Subsections
should include call gapping, code gapping, choke networks, and SS7
flow controls for GTTs.