AXE Translations

ATT-TELCO-002-205-018Translations: Commercial Mobile Radio Service - 1A,

DMS100, 5E, AXE - SWAbstract:This document replaces TMP 87-06-001 Radio Common Carrier

Audience:NTC Region(s): SW

Product Name:

Effective Date: Immediate

Published : Issue 2, 04/26/10

Expires On: N/A

Related Documents:

Canceled Documents:

Issuing Department: Network Provisioning Translations Support

Business Unit: Network Provisioning

Points Of Contact: See Contact List .

Author(s):Mike Pharris ATTUID mp4177

AT&T Practice ATT-TELCO-002-205-018Issue 2, 04/26/10

AT&T Proprietary (Internal Use Only)Not for use or disclosure outside the AT&T companies, except under written agreement.

©2010 AT&T Intellectual Property. All rights reserved.i

Table Of ContentsINTRODUCTIONGeneralReason For Current Issue1. Reason For Current Issue 22. Translations Ask Yourself 23. 0. GENERAL 4

3.1. 0.1 INTRODUCTION 43.2. 0.2 REASON FOR ISSUE/REISSUE 43.3. 0.3 SERVICE DESCRIPTION 43.4. 0.4 TECHNICAL DESCRIPTION 5

3.4.1. 0.4.1 Background 53.4.2. 0.4.2 CMRS Interconnection Architecture 63.4.3. 0.4.3 Signaling Requirements 73.4.4. 0.4.4 DACC (Directory Assistance Call Completion)- 93.4.5. 0.4.5 AWCP- 103.4.6. 0.4.6 Switch Translations 103.4.7. 0.4.7 Switch Requirements/Restrictions 12

3.4.7.1. 0.4.7.1 ACCESS TANDEMS 123.4.7.2. 0.4.7.2 END OFFICES 133.4.7.3. 0.4.7.3 TOPS 13

3.4.8. 0.4.8 Testing 143.4.9. 0.4.9 Provisioning Flow 14

3.5. 0.5 SUBSCRIBER PROCEDURES 163.6. 0.6 SCREENING REQUIREMENTS 163.7. 0.7 AUTOMATIC MESSAGE ACCOUNTING 163.8. 0.8 Acronyms 17

4. 1. 1AESS 194.1. 1.1 general 19

4.1.1. 1.1.1 Reason For Issue 204.2. 1.2 generic requirements 20

4.2.1. 1.2.1 Base Generic Required 204.2.2. 1.2.2 Feature Requirements 20



©2010 AT&T Intellectual Property. All rights reserved.ii

4.3. 1.3 Translations 204.3.1. 1.3.1 Type 1 Terminating (INC from the CMRS) Translations 204.3.2. 1.3.2 TYPE 1 Originating (OGT to the CMRS) Translation 21

4.3.2.1. 1.3.2.1 Dedicated NXX 214.3.2.2. 1.3.2.2 Partial NXX 22

4.4. 1.4 Type 2A Interconnection 224.5. 1.5 Type 2B Interconnection 22

4.5.1. 1.5.1 Type 2B Terminating (INC from the CMRS) Translations 224.5.2. 1.5.2 Type 2B Originating (OGT to the CMRS) Translations 234.5.3. 1.5.3 Type 2B Two Way ( INC/OGT from/to the CMRS) Translations 234.5.4. 1.5.4 Type 2C - Incoming Wireless E911 Trunk Group 23

4.6. 1.6 CMRS Billing 234.7. 1.7 Hardware 244.8. 1.8 References 24

5. 2. DMS100 245.1. 2.1 GENERAL 24

5.1.1. 2.1.1 REASON FOR ISSUE/REISSUE 245.2. 2.2 GENERIC REQUIREMENTS 25

5.2.1. 2.2.1 BASE GENERIC REQUIRED 255.2.2. 2.2.2 FEATURE REQUIREMENTS 25

5.3. 2.3 TRANSLATIONS 265.3.1. 2.3.1 TYPE 1 265.3.2. 2.3.2 TYPE 2A 305.3.3. 2.3.3 TYPE 2B 345.3.4. 2.3.4 TYPE 2C 355.3.5. 2.3.5 Type 2D 365.3.6. 2.3.6 AREA WIDE CALLING PLAN (AWCP) 44

5.4. 2.4 HARDWARE 465.5. 2.5 REFERENCES 46

6. 3. 5ESS 466.1. 3.1 GENERAL 47

6.1.1. 3.1.1 REASON FOR ISSUE/REISSUE 476.2. 3.2 GENERIC REQUIREMENTS 47

6.2.1. 3.2.1 BASE GENERIC 476.3. 3.3 TRANSLATIONS 47



©2010 AT&T Intellectual Property. All rights reserved.iii

6.3.1. 3.3.1 Type 1 Interconnection 476.3.1.1. 3.3.1.1 Individualized Dialing Feature Definition (RCV 12.17, 5601

Record) 48

6.3.1.2. 3.3.1.2 IDP Group Definition (RCV 9.10, 5601-4 Record) 486.3.1.3. 3.3.1.3 Screening (RCV 10.10, 5301 Record) 496.3.1.4. 3.3.1.4 Charge Index Expansion (RCV 10.12, 5302-1 Record) 506.3.1.5. 3.3.1.5 Trunk Group (RCV 5.1, 5202 Record) 516.3.1.6. 3.3.1.6 BRCS Trunk Group Assignment (RCV 5.4, 5206 Record) 51

6.3.2. 3.3.2 Type 2A Interconnection (Tandem) 526.3.2.1. 3.3.2.1 Secured Features 128 & 160 (RCV 8.22, 5713 Record) 526.3.2.2. 3.3.2.2 Cellular Mobile Carrier Identification (Charging) (RCV 10.16,

5056 Record) 53

6.3.2.3. 3.3.2.3 Trunk Group (RCV 5.1, 5202 Record) 546.3.2.4. 3.3.2.4 AMA Call Type (Charging) (RCV 10.12, 5506 Record) 556.3.2.5. 3.3.2.5 Office Parameters (RCV 8.1, 5509 Record) 56

6.3.3. 3.3.3 Equal Access (Type 2A Tandem Interconnection) 566.3.3.1. 3.3.3.1 Trunk Group (RCV 5.1, 5202 Record) 566.3.3.2. 3.3.3.2 AMA Changes (Call Scenario) 57

6.3.4. 3.3.4 Type 2B Interconnection 576.3.4.1. 3.3.4.1 Trunk Group (RCV 5.1, 5202 Record) 586.3.4.2. 3.3.4.2 InterLata Carrier (RCV 10.3, 5305 Record) 59

6.3.5. 3.3.5 Type 2C Interconnection (Tandem) 596.4. 3.4 HARDWARE 606.5. 3.5 REFERENCES 60

7. 4. Ericsson AXE 607.1. 4.1 General 607.2. 4.2 Reason For Issue/Reissue 607.3. 4.3 Translations 61

7.3.1. 4.3.1 TYPE 1 INTERCONNECTION IN THE AXE 617.3.1.1. 4.3.1.1 SOFTWARE REQUIREMENTS 617.3.1.2. 4.3.1.2 TRANSLATION STANDARDS 617.3.1.3. 4.3.1.3 AXE TABLE DATAFILL 627.3.1.4. 4.3.1.4 CHARGING ANALYSIS 63

7.3.2. 4.3.2 TYPE 2A ORIGINATING (OGT to the MTSO) TRANSLATIONS 647.3.3. 4.3.3 TYPE 2B ORIGINATING (OGT to the MTSO) TRANSLATIONS 65



©2010 AT&T Intellectual Property. All rights reserved.iv

7.3.4. 4.3.4 TYPE 2B TERMINATING (INC from the MTSO) TRANSLATIONS 657.3.5. 4.3.5 TYPE 2B TWO WAY ( INC AND OGT from the MTSO)

TRANSLATIONS 65

7.3.5.1. 4.3.5.1 Translation Standards 657.3.5.2. 4.3.5.2 AXE TYPE 2B MF SIGNALING 667.3.5.3. 4.3.5.3 AXE TYPE 2B SS7 SIGNALING 66

7.4. 4.4 Size Alteration Event - Form 1405 677.5. 4.5 Automatic Message Accounting 677.6. 4.6 References 67

8. Contact List 67A.1. Document Specific Acronyms 68A.2. Acronyms Dictionary 68

Revision Log 68ACRONYMS 68



©2010 AT&T Intellectual Property. All rights reserved.v



©2010 AT&T Intellectual Property. All rights reserved.vi

General

All Methods and Procedures in this document adhere to AT&T’s competition policy which includes compliance with thesection 272 (e)(1) parity service requirements with respect to exchange and exchange access services, and employeesare reminded to consult with Legal regarding any section 272(e)(1) issues or questions. Section 272(e)(1): A Telco shallfulfill any requests from an unaffiliated entity for telephone exchange service and exchange access within a period nolonger than the period in which it provides such telephone exchange service and exchange access to itself or to itsaffiliates.

Reason For Current Issue

Issue Number Date Description Published By

2 04/26/10 Updated to change the titlefrom: Commercial MobileRadio Service; to: Commer-cial Mobile Radio Service -1A, DMS100, 5E, AXE - SW

jr9461

INTRODUCTION

CAUTION CAUTION CAUTION CAUTION CAUTION CAUTION CAUTION

Insertion of CRITICAL TRANSLATIONS can have an adverse effect on customer service. For those routing andcharging translations with the potential to effect large numbers of customers and/or a large number of calls,EXTREME caution should be exercised. It is the responsibility of the local operations forces to develop a 'BACKOUT STRATEGY' and determine if service activation should occur during 'OFF PEAK' hours. Local TXC and SCCmanagers should evaluate the impact of translations on a case by case basis.

General Translation Activation

Check List

Contact your supervisor for assistance if you have any doubt as how to correctly answer the followingquestions.

Do you understand the potential service affecting impact of the task you are being asked to perform?

Are you doing the work in the correct switch?

What is the appropriate time of day to make and test the intended changes?

Do you have all of the necessary provisioning documentation and are they complete and accurate?

Do you have the appropriate translation verifications and a back out plan?



2010 AT&T Intellectual Property. All rights reserved.1

Have you, or when possible a co-worker, double checked your work before implementation?

Is this service dependent on other than switch translations (AIN, Facilties, etc.)?

If so, have you verified the status of the required database or facilities work?

Do you have a comprehensive test plan and know by whom, how and when the plan should be executed?

Do any Network conditions or activities currently exist that would preclude the performance of this activity (End office orSTP generic loads, Simplex equipment etc.)?

1. Reason For Current Issue

DATE ISSUE DESCRIPTION

10/21/2008 1 initial issue

2. Translations Ask Yourself Before you begin your translation work, make sure you can answer YES to each of the following questions:

1. Do I know WHY I am doing this work?

• Do I have the big picture?

• Do I understand the translations requirements?

• Do I understand how the product works?

• Did I attend the Technical Conference Call?

° If not, was the information from the call shared with me?

• Have I read the translation documentation (M&P) and do I understand it?

• Am I using the most current version of the document?




2. Do I know WHAT I am to do?

• Have I reviewed the order?

• Do I have everything I need?

3. Do I know HOW to do the work?

• Am I trained and qualified?

• Have I reviewed the procedure steps in the documentation, or have I laid out a step by step procedure of myown?

• Do I understand the provisioning process?

4. Have I referred my questions to my supervisor, or the author of this document?

5. Have I identified and notified all impacted work groups?

6. Do I have a test plan that includes:

• Making a routing test as soon as I make the translation changes,

• Making an AMA test call?

7. Can I control or prevent a service interruption?

• Do I have a back out plan?

• Do I know what to do if a service interruption occurs?

° who to call

° when to call

° the escalation process

• Did I double check my input messages prior to activation?

• Did I validate my work using the appropriate translations verify message for my switch type (i.e., TRAVER,TRACKER, VFY OFC, etc)?

8. Is this the right time to do this work?




• Have I set aside enough uninterrupted time?

• Should this order be worked out of hours?

• Is this a coordinated order?

• Do I know who to contact?

9. Have I verified that I am in the right office; in the correct translator, view, or table; and positioned on the correctentry for the task I am doing?

10. Did I answer YES to all of the questions?

WARNING: If you didn’t, don’t proceed until you can.

3. 0. GENERAL

3.1. 0.1 INTRODUCTION This TMP provides translations requirements and the technical service descriptions of the various interconnection typesavailable to the Commercial Mobile Radio Service (CMRS) providers. Most of the information contained in this Generalsection has been extracted from the Technical Service Description prepared by the Technology and Product DevelopmentDepartment.

3.2. 0.2 REASON FOR ISSUE/REISSUE This is the seventeenth issue of this TMP. It is revised to reflect the trunk group for SS7 2B parameter changes in theAXE section. Any changes will be indicated with a revision mark | on the right side of the page.

3.3. 0.3 SERVICE DESCRIPTION Consumers use a number of mobile services for their communication needs, many of which require interconnection withthe networks of the Local Exchange Carriers (LECs). The following is a list of five specific interconnection arrangements:

Type 1 - Direct CMRS connection through a LEC end office using MF signaling or SS7 only for outgoing calls.




Type 2A - Direct CMRS connection with a LEC tandem office using MF or SS7 signaling.

Type 2B - Direct CMRS connection with a specific LEC end office using MF or SS7 signaling. The majority of our connec-tions are incoming from the CMRS to the end office. Type 2B Land to CMRS (Mobile) is now tariffed in all 5 SWB regionstates to facilitate tandem relief in place of additional Type 2A connections.

Type 2C - Direct CMRS connection with a LEC 911 tandem office.

Type 2D - Direct CMRS connection with a LEC operator tandem used for operator assisted calls or directory service

3.4. 0.4 TECHNICAL DESCRIPTION This technical service description provides a comprehensive description of the various Commercial Mobile Radio Service(CMRS) interconnection arrangements to the Southwestern Bell network. This document is being issued as a guide torespond to several network changes in response to the Communications Act of 1996 and the F.C.C. interconnectionorders.

The CMRS switched network interconnections are growing approximately 28% a year. In addition to the Cellular andPaging customers, we are now receiving orders from the newly awarded PCS/Major Trading Area (MTA) licensedcustomers. PCS customers will use the same interconnections as provided to Paging and Cellular carriers.

3.4.1. 0.4.1 Background

Listed below are several (but not all) of the major stipulations of the F.C.C.

interconnection order:

-The LEC must provide unbundling of the network where technically feasible.

-Symmetrical and reciprocal compensation for network access between

Telecommunications networks.

-Physical Collocation

-Access to OSS systems for the purpose of pre-ordering, ordering, provisioning, billing,

and maintenance and repair services.

-Access minute of use proxy rates were set if a cost study is not available.

-Transport and switching rates are the elements to be charged for switch

access with a different rate for the end office and the tandem.




-The LEC must provide two-way trunking if technically feasible.

3.4.2. 0.4.2 CMRS Interconnection Architecture

Tandem Interconnections:

Type 2A -

These are trunks between the CMRS network and the Access Tandem. This trunk group

is capable of routing intraLATA toll and local traffic to all end offices served by the

Access Tandem. With the addition of software (described in section 6), Southwestern

Bell will provide this trunk group with either MF or SS7 signaling with either one -way

or 2-way operation. These trunk groups are engineered as direct final with no alternate

routing. InterLATA traffic may be combined onto the Type 2A trunk group.

Equal Access -

These are trunks between the CMRS network and the Access Tandem. This trunk group routes InterLATA traffic only.Southwestern Bell will provide this trunk group with either MF or SS7 signaling with either one -way or 2-way operation.These trunk groups are engineered as either direct or alternate final with no alternate routing. The SS7 Cell trunk groupwill support 800 query traffic and requires end office to tandem Feature Group D signaling. The Feature Group D protocolmust be in the standard OZZ/XXXX format where the OZZ tells the access tandem that translation of the XXXX is neces-sary to identify the Interexchange Carrier and it's associated trunk group. The XXXX is the Carrier Identification Code(CIC). The Type 2A and Equal Access groups can be combined using the Cell trunk type (MF) or the Cell option (SS7)and is the preferred interconnection arrangement.

Type 2D - DACC (Directory Assistance Call Completion) -

These are dedicated CMRS one-way trunks to the TOPS operator tandem. End office to tandem Feature Group D protocol,and MF signaling is required. If the CMRS carrier requires only Directory Assistance, then MF signaling with CAMA ANIis required.

AWCP (Area Wide Calling Plan) -

These are tandem trunks to the CMRS network to transport Landline calls to the wireless end user. This service requiresa dedicated NXX and a one-way MF or SS7 trunk group.

911 Emergency Tandem-

This is a one-way trunk group from the CMRS network to either the 911 SWBT tandem or directly to the PSAP. This trunkgroup is required because we plan to eliminate the Miscellaneous/ Junk trunk group type of access interconnection. Thisdedicated trunk group can be provisioned with either MF or SS7 signaling.




Type 2C - Wireless E911

This is a direct trunk group from the CMRS to the SWBT 911 Tandem. This trunk group type requires the CMRS providerto provide a 10 digit ANI (for operator call back) and an additional pseudo ANI to define the location. SS7 signaling is alsorequired.

End Office Interconnections:

Type 1 -

This interconnection is for CMRS trunks to the SWBT end office and transports intraLATA toll and local traffic. This trunkgroup requires MF signaling if it is two-way. SS7 signaling can be provided if the interconnection is one-way out to theCMRS network. The SS7 Type 1 one-way out service is called 'Type 1 Outbound with SS7'.

Type 2B -

This one-way interconnection is from the CMRS network to the end office. This trunk group may be designed as a directfinal trunk group or it may be designed to overflow to a Type 2A trunk group when all of the 2B circuits are busy. Overflowis controlled by the CMRS provider. The calling scope associated with Type 2B interconnection is limited to subscribersserved out of the end office and, in the case of a host office, any remote switches associated with that end office. Callsto numbers that have ported out of the end office will also be permitted. Calls to Operator Services, access to Interex-change Carriers, Service Access Codes (800) or Emergency Services (911) are not permitted. This interconnectionaccommodates either MF or SS7 signaling.

The majority of our Type 2B connections are incoming from the CMRS to the end office. The Type 2B Land to CMRStrunk group is now tariffed in all 5 SWB region states and is being promoted as a means of tandem relief by limiting theaddition of Type 2A tandem ports. The trunk group must be built as outgoing only and will carry traffic terminating to theCMRS codes local to that end office. The routing will include overflow to the access tandem to the Type 2A when boththe end office and CMRS subtend the access tandem.

3.4.3. 0.4.3 Signaling Requirements

Interconnection for wireless supports both Multi-Frequency (MF) and Signaling System 7 (SS7) protocols.

Signaling System 7-

Signaling System Number 7 (SS7) is a set of standardized signaling protocol that has been designed to provide out-of-band signaling capabilities for digital communication networks. Besides the capabilities for handling Plain Old TelephoneService (POTs) calls, it also has the capabilities to support advanced services such as calling number identification andpersonal communications services.

SWBT will offer both Integrated Service Digital Service User Part (ISUP) for call set up and delivery of message trafficand Transaction Capability Application Part (TCAP) for database query/response. There are significant benefits for CMRScarriers to utilize SS7 signaling:




• More efficient utilization of trunking resources between two interconnection networks by reducing call setup delay.

• Fraud prevention and Increased Revenue.

• Supports more extensive exchange of call control information between two interconnecting networks that are neededfor advanced features such as 800, CLASS, operator services, Intelligent Network services, Calling Number Identification,and Flexible Billing Service.

Technical requirements for the ISUP signaling capability are described in the following Bellcore's specifications:

• GR-145-CORE • TR-NWT-000317.

• TR-NWT-000394 • TR-NWT-000246.

• TA-NWT-001434 • TR-TSV-000905.

• TR-TSV-000444 • GR-1083 CORE

SWBT will provide CMRS Carriers with SS7 interconnection access to the SWBT SS7 network so that ISDNUP and TCAPsignaling can be used to setup/release calls and/or launch and receive database queries over Type 2A/2B trunk and linkinterconnection.

The following call types will be supported over Type 2A/2B trunks using ISUP signaling:

LANDLINE-to-CMRS

Outgoing calls from a SWBT tandem switch to a wireless carrier POT can be established to telephone numbers (DNs)served by the carrier. These outgoing calls will be routed to the POT based on the NPA, NXX, or 1000s block of the calledDNs. The CMRS switch is responsible for completing calls to the wireless subscribers.

CMRS-to-LANDLINE

Incoming calls from a wireless carrier POT to a SWBT tandem switch can be established to valid local network officecodes (NXXs) accessible through the tandem switch

Intra-LATA destinations only. Calls to InterLATA destinations will be allowed over a common trunk group when Financehas completed program changes to accommodate dual recordings at the access tandem for both the CMRS minutes ofuse and the InterLATA Access record. The address signaling sequence for incoming calls through the tandem switchesto FG-D or FG-B ICs will be the sequence used for FG-D or FG-B switched access signaling. Services such as directoryassistance and operator service

(0- and 0+) are not available through Type 2A trunk with SS7 ISUP signaling.

Incoming calls from a wireless carrier POT to a SWBT end office is limited to Directory Numbers served by the end officeand, in the case of a host office, any remote switches associated with that end office. This maintains consistency with theinterconnection definitions as specified in Bellcore GR-145-CORE. (An exception to this rule is the case of a call to a




portable NXX that comes in unqueried. The end office will launch the LNP query and if necessary transit the call to therecipient switch, if the number has ported off the donor switch.)

This section describes the ISUP message-flows to be used to setup and release calls over the Type 2A/2B trunks betweenthe CMRS and SWBT networks. Detailed specification of these ISUP messages can be found in Bellcore TA-NWT-001434,TR-TSY-000317, and TR-NWT-000394 specifications.

• Initial Address Message (IAM): This message is sent in the forward direction to initiate a trunk call setup between twointerconnecting networks. It contains the identification of the Type-2A/2B trunk circuit selected, and other necessary callhandling information.

• Continuity Message (COT): This message is sent in the forward direction to indicate the status (success/failure) of theType-2A/2B trunk circuit selected for the call.

• Address Complete Message (ACM): This message is sent in the backward direction from a terminating end office whenthe called party information is complete, and any continuity checks required in the connection are successful.

• Answer Message (ANM): This message is sent in the backward direction from a terminating end office to indicate thatthe call has been answered.

• Release Message (REL): This message is sent in either direction to indicate that the Type-2A/2B trunk circuit used forthe call is being released.

• Release Complete Message (RLC): This message is sent in either direction as a response to an REL message. It tellsthe switch to idle the Type-2A/2B trunk circuit for the next call.

• B-Link quad: For this interconnection arrangement, the SWBT SS7 network shall interface with a CMRS carrier networkvia four B-Links interconnecting a SWBT' mated STP pair with a CMRS carrier's mated STP pair.

• A-Link pair: For this interconnection arrangement, the SWBT SS7 network shall interface with a CMRS Carrier's POTswitch using two A-Links interconnecting the switch to SWBT's mated STP pair.

These two interconnection arrangements will be able to support both Inter/IntraLATA call setup and release. SWBT willhandle all Intra-LATA traffic within its network. However, it will forward all interLATA traffic to the ICs preferred by theCMRS carriers. The signaling method to be used for interLATA calls will depend of the type of network interconnectionsavailable between SWBT and the ICs.

Multi-Frequency Signaling-Southwestern Bell will accommodate MF signaling if it is requested by the CMRS Carrier. Asnoted in previous sections, some types of trunk groups will continue to use MF signaling.

3.4.4. 0.4.4 DACC (Directory Assistance Call Completion)-

For CMRS DACC, NTI has designed TOPS such that CMRS Carriers signal to TOPS using standard FGD signaling ontrunks data filled with a calling ID of COMFGD. The original intent of the COMFGD calling ID was to connect an EqualAccess End Office to an IXC; therefore, all calls on COMFGD trunks are treated as IXC calls. For these calls, call comple-tion services use Equal Access translations.




FGD signaling on a TOPS COMFGD trunk takes place as follows - the Automatic Number Identification (ANI) is sent,followed immediately by the called number stage. Important features of COMFGD signaling are:

Start Translation (ST) digits are not primed (i.e., STP, ST2P and ST3P are not used). Instead, the station class is identifiedbased on the ANI information digits, as specified in TOPS table OSSCAT.

Key Pulse (KP) digits are not primed.

ANI consists of two information digits (II) followed by 10 calling digits for ANI success calls. The resulting pattern is KP-II-NPA-NXX-XXXX-ST.

The digit, 0, is included in the called number as a prefix to indicate that a call is operator assisted. Cellular Carriers forward3/7/10 called digits and the resulting pattern is KP-0-411-ST and KP-0-555-1212-ST or KP-0-NPA-555-1212-ST (KP-0-NPA-555-1212-ST is mandatory with

INPA). There is no wink response between the ANI stage and the called digit stage.

· FGD digit signaling ends with a wink; for calls that are answered and calls that go to an operator, the sending officereceives an off-hook after the wink.

The CMRS Carrier must insure that all 10 digits of the calling number are forwarded to insure correct billing records.Additional documentation on the Type 2D Interface is available in Bellcore Documents GR-145-CORE, Section 2.7 andTR-NWT-000690, Section 3.1.1.2 and supporting sections.

3.4.5. 0.4.5 AWCP-

The Area Wide Calling Plan is a service that allows the Landline user to call the CMRS customer without any toll fee.However, calls placed by the Landline user using 0+ 7/10 digit dialing will incur the operator handling surcharge.

3.4.6. 0.4.6 Switch Translations

Switch Translations for CMRS interconnection center on three primary functions:

· Trunk Translation

· Code Activation

· AMA Recording

Trunk translations are dependent upon the type of interconnection, signaling, directionality, and AMA recording requiredwith the CMRS carrier.




At the access tandem we will utilize new software features that will define a new trunk type as Cellular. For the interimwe will continue to utilize a separate trunk group for CMRS access tandem routed Equal Access traffic. Area Wide CallingPlan traffic will still require a separate trunk group and will require no recording at the access tandem..

The TOPS tandem will require dedicated trunking for the Directory Assistance with CAMA ANI signaling. Directory Assis-tance with Call Completion requires a dedicated trunk group with Feature Group D signaling. Toll Assistance will utilize'SP' (operator supervision capabilities) trunk translations.

The end office treats the Type 1 interconnection as a trunk with line treatment and the switch must provide ANI 7 screeningfor Operator and InterLATA traffic if needed.

CMRS carriers require code activation to serve their subscribers within the market. However, there will no longer be anycharge for code activation per the FCC Interconnection Order (Dockets 96-98 and 95-185). Code activation for CMRSwill follow the same reservation and provisioning procedure as used for all code activation per the Interexchange CarrierCompatibility Forum (ICCF) standards.

The FCC Interconnection order requires reciprocal compensation between the CMRS carrier and the Local ExchangeCompany (LEC). Until recently Southwestern Bell had charged minutes of use access for traffic bound for the CMRSnetwork and only charged a facility channel termination for traffic from the CMRS network. With the FCC order we will nolonger apply these charges. Instead we will charge access minutes of use (MOU) for the inbound CMRS traffic and willbe required to pay access charges for traffic bound towards the CMRS network. Because of this requirement SWBT isimplementing software and associated switch translations to record MOU in both directions.

Traffic routed by the Tandem (Type 2A) will utilize new software and will record Cellular AMA records. At the end officewe will continue to use the 'Trunk with Line Treatment/ PX' translation to generate MOU recordings for the inbound CMRScalls. The outbound traffic will be translated with AIN query trigger translation against the CMRS number to interrupt thecall processing and request the end office to generate an AMA record.

DACC-

CMRS Carriers will need to establish new switch translations in their MTSO(s) and establish FGD signaling over a Type2D Interconnection from their MTSO(s) to TOPS. If a CMRS Carrier already subscribes to 'Home' SP DACC via FGCtrunks, these can be reused for FGD signaling by swinging the FGC trunks over to the new FGD service. All existing SPDACC traffic as well as the new SP DACC traffic can be served over these same trunks. The CMRS Carrier must coordi-nate this conversion with SWBT facilities personnel that support the serving TOPS switch to insure there is no downtime.

The new switch features now explicitly identify each CMRS Carrier with a Carrier Access Code (CAC). With the new NASfeatures, the CAC is now transmitted from the switch to the gateway which allows branding on an individual carrier basis.

DACC functions as follows:

1. Through translations, the call arrives at a DA operator. The operator enters the name and city of the party the Cellularsubscriber wishes to reach.

2. The DA query is launched, and the subscriber is connected to the Interactive Voice System (IVS).

3. The subscriber accepts DACC from the IVS by depressing 1 during the DACC announcement. This is not required ifthe Carrier selects the Auto-Complete option, i.e., automatically providing call completion. If auto-completion is selected,




the Carrier must insure that it routes only those calls intended for this service over the dedicated FGD trunk group toTOPS as all calls arriving on this trunk group will be automatically completed.

DACC Sent Paid enables CMRS carrier customers utilization of DACC in the same manner as 'landline' customers.(Alternately billed DACC calls are not part of this service and will continue to be handled as they are today). Some DAcalls will not be eligible for Call Completion, i.e., non-published numbers, enterprise numbers, 976 numbers, 700 and 900numbers, etc. due to technical, regulatory, legal and/or company policy restraints. (This list is not all inclusive.)

3.4.7. 0.4.7 Switch Requirements/Restrictions

As discussed earlier in this document Southwestern Bell must comply with the FCC interconnection order. Therefore, ourswitch must not only perform the routing and switching of the CMRS call but must also record MOU AMA for calls to andfrom the CMRS network for billing and audit purposes.

3.4.7.1. 0.4.7.1 ACCESS TANDEMS

All of the access tandems (except the Ericsson switch in Mexico, Missouri) have been equipped with new softwarefeatures. These features allow the switch to translate the CMRS trunk as Cellular and generate incoming and outgoingAMA recordings. The software is listed below by switch type:

5ESS -

99-5E-1081 SFID 128 Type 2A/2B CMC via CCS - IMR 529864

99-5E-2540 SFID 160 AMA Capabilities for Type 2A Cellular Interconnection -

IMR 529864

DMS 200 -

EQA00001/4 Type 2A Cellular Interconnection MF -

ISUP00001 Type 'S' Cellular SS7 2A/2B Interconnect

4ESS -

J4A026B-1 List MFZR CCS Trunk Interface to Cellular Type 2A trunk.

Table 3 shows the generic software releases that are deployed with these tandem switches to support Type 2A with SS7service.




Switch Type Software Rls

5ESS 5E7

4ESS 4E16

DMS 100/200 BCS34

DMS 200 BCS34

Table 3 Software Deployed in Tandem Switches

3.4.7.2. 0.4.7.2 END OFFICES

At this time (12-98), we do not plan to add any additional software to the end offices to enable additional functionality forCMRS interconnection. Type 2B will remain a directional arrangement with an incoming trunk group built as a FGDterminating group using CIC 0698 and an outgoing interoffice trunk group built in the standard interconnection form.

In 1997, (subsequent to Issue 1 of this TSD), Technology Planning investigated the feasibility and priority of enhancingthe AIN DID Access Service (DAS) to add Type 1 CMRS telephone numbers to the AIN trigger translations. This function-ality would allow Southwestern Bell to record Paging and other outbound Landline traffic and use these records as anaudit to determine the accuracy of the billing from the CMRS carriers. Results of this investigation were inconclusive, andthe development of this capability was not pursued.

In the 12-96 timeframe (issue 1 of this TSD), the Company reviewed the additions needed for an additional Busy Hour35% recording requirement (Local Service Providers, CMRS, Local access with Independents). Software was loaded intoselected 1AESSs and some DMS 100's added disk space. Ongoing, additional registers and memory may be requiredat the Type 1 serving end offices due to an increase in AMA recordings for audit purposes. Typical Capacity Monitoring/Network Design criteria should be followed to insure the availability of recording equipment.

Currently, there are two known service restrictions associated with end offices:

1. DMS switches cannot complete calls from Access To Carrier (ATC) trunk groups to ATC trunk groups. This inhibits callcompletion when a call is received via Type 2B interconnection (uses an ATC trunk) and the called number is remote callforwarded to an interoffice number routed via another ATC trunk group. This scenario exists regardless of the signalingprotocol, MF versus SS7, and is common to other types of interconnection.

2. Due to translations complexities, Type 2B with SS7 interconnection will not be 'generally available' on the Ericssonswitch. Interconnection arrangements must be negotiated on a customer-specific, case-by-case, basis.

3.4.7.3. 0.4.7.3 TOPS




Southwestern Bell Telephone functionality that provides this capability is located in the TOPS switch and in the database/gateway system. For CMRS DACC to be successful, Marketing has identified the following features that is provided inthe TOPS switch:

· Customized DACC Announcement Capability

· Station Paid Billing Capability for Roamers

· Auto Completion Capability

CMRS carriers must set up dedicated FGD trunks and establish translations to route the SP DACC calls over these trunks.They must insure that the full 10-digit ANI is transmitted to TOPS.

3.4.8. 0.4.8 Testing

Several tests will be required for SS7 trunk interconnection. First, the Intelligent Network Technical Support (INTS) willconduct SS7 protocol and inter-networking compatibility testing between SWBT SS7 Network and the customer's network.The specifics on the types of testing to be conducted are specified in Bellcore's TR-TSV-000905, and SWBT's TP 76638.They are summarized as follows:

• Physical layer test: physical link mechanical and electrical requirements.

• Link layer control functions: signaling unit alignment, error detection, error correction, initial alignment, signaling linkerror monitoring, and flow control.

• Signaling network layer test: Signaling message handling, and signaling network management.

• Transport and routing of SS7 ISDNUP messages for call setup and release.

A subsequent "BETA" test will be conducted to test the ability of SWBT to: take an order for Type 2A with SS7 service,provision the service, coordinate responsibilities, establish signaling link control designation, exchange point code infor-mation, set up translation tables in STPs, exchange traffic information, coordinate link diversity management, receivetrouble reports, report to the customer, and issue bills. When measuring capability is developed, another Beta test will beconducted to test the AMA capability.

Conversion of the Type 2A trunking to 'Cell' trunks will, at a minimum, require transmission continuity testing to turn upthe new trunk group number in the switch. Continuity testing will also be required for the establishment of other types ofnew CMRS trunking (i.e. DA, DACC, 911, Toll and Assistance) as we eliminate the miscellaneous trunk groups.

3.4.9. 0.4.9 Provisioning Flow




Ordering ISUP/TCAP SS7 SS7 network access for out-of-band ISUP/TCAP signaling of calls over Type 2A/2B trunks willbe available in each state in SWBT's territory. The CMRS carrier will be required to participate in the SS7 interconnectioncompatibility testing prior to the live service turn up.-

The SS7 network accesses that can be used for ISUP/TCAP signaling of calls over Type 2A/2B trunks include: A-link pairfor a signaling end point, or B-link quad for STP-to-STP interconnection. After the initial order, the CMRS carrier mayrequest additional links for the linkset, or modifications to the screening and routing tables.

CMRS carrier can order SS7 interconnection by contacting a SWBT marketing representative. The marketing represen-tative will gather needed information from the

CMRS Carrier, coordinate service provisioning activities with CMRS ICSC, and communicate to the customer the serviceconfiguration, time frame, and availability.

The Wireless Interconnection Form (WIF) order should include the following information from the customer:

- Point Codes

Linkset (STP ports and links)

- MTP screening table

- MTP routing table

- Flat rate v. Usage Sensitive Billing options

Normal lead time for trunk interconnection is approximately 60 days from the day the order is received provided that theCMRS Carrier has completed interconnection compatibility testing and has been certified for the particular networkconfiguration.

The provisioning flow for Type 2A/2B with SS7 service is as follows:

• CMRS Carrier orders access to the SWBT network. This may include links to the local or regional STP and trunk groupsto SWBT tandem switch or end office.

• The Dallas Regional Sales staff and the Intelligent Network Technical Support group (INTS) meets with the customerto get ordering information and establish service testing and acceptance criteria.

• Operations installs the SS7 Links and trunk groups to the customer's location.

• IECC staff conducts testing of the installed facilities.

• INTS conducts TR905 compatibility tests and or transmission continuity tests with the customer.




The following SWBT's organizations will be involved in the provisioning flow to established CMRS interconnection servicefor the customer:

• ICSC

• Trunk Management

• Competitive Assurance / Services Planning

• TXC

• NSS

• CPC

• SNAC (CNOC)

• SOCC

• SCC/IECC

Trunk Management will be responsible for monitoring, servicing, and forecasting the trunk capacity requirements for alltypes of CMRS interconnection.

3.5. 0.5 SUBSCRIBER PROCEDURES There are no new procedures relating to CMRS for our subscribers.

3.6. 0.6 SCREENING REQUIREMENTS There are some screening requirements for the different trunk type connections. See section 0.4.2.

3.7. 0.7 AUTOMATIC MESSAGE ACCOUNTING AMA records will comply with GR-1504, TR-NWT-0005333, and GR-1083 specification.

Type 2A-

For LANDLINE-to-CMRS calls over Type 2A trunks using ISDNUP signaling, the SWBT tandem will record call code 119(as appropriate) AMA records. Call code 064 will not be recorded unless the billing department requests a special study.




For CMRS-to-LANDLINE calls over Type 2A trunk using ISDNUP signaling, the SWBT tandem will record 066, 110, 141,and 142 AMA records as the call type dictates.

Type 1-

CMRS-to-LANDLINE - generates a local measured rate AMA recording. This is the present methodology for recordingand billing access.

LANDLINE-to-CMRS - With the implementation of AIN - DAS enhancement for CMRS the end office will generate AMArecordings for DID Access service. Local calls will generate a 067/074 call code. InterLATA will generate a 119 call code.IntraLATA toll will generate a 006 call code.

Type 2B-

LANDLINE-TO-CMRS - standard originating AMA records will be generated based on the originating land line class ofservice. No special cellular AMA will be generated on the type 2B Land to CMRS call.

CMRS-TO LANDLINE - utilizing either MF or SS7 signaling will generate a terminating FG D 119 call code. Note: BecauseSWBT has not currently equipped end offices with the Cellular Interconnection AMA software, Call Code 065 as documen-ted in Bellcore GR-1504 is not available.

AWCP-

LANDLINE-to-CMRS - local calls will generate 067/074 call codes. Note: the coin is not returned from pay stations. Tollcalls will generate a 006 call code at the end office.

DACC-

Bill information (from TOPS AMA recordings) will be returned to the CMRS Carrier for them to bill their customers forusage. Information to be returned to the Carrier will include:

1. Calling Number

2. Called Number

3. Date

4. Start and End Times of the DACC portion of the call

5. DACC Indicator

3.8. 0.8 Acronyms ANI - Automatic Number Identification

ANSI - American National Standards Institute




CMRS - Commercial Mobile Radio Service

BOC - Bell Operation Company

CNOC - Centralized Network Operations Center

CCITT - Consultative Committee on International Telephone & Telegraph

CIC - Carrier Identification Code

CTIA - Cellular Telephone Industry Association

DN - Directory Number

DPC - Destination Point Code

EA - Equal Access

EIA - Electronic Industries Association

ESAC- Electronic Switching Administration Center

ESN - Electronic Serial Number

GS - Gateway Screening

GTI - Global Title Indicator

GTT - Global Title Translation

ICB - Individual Case Basis

INTS - Intelligent Network Technical Support

ISUP - ISDN User Part

ISDN - Integrated Service Digital Network

IC, IEC, IXC - Interexchange Carrier

IS-41 - TIA Interim Standard 41

LATA - Local Access Transport Area

LEC - Local Exchange Carrier

LSTP - Local STP Pair

MTP - Message Transfer Part




MSA - Metropolitan Statistical Area

MFJ - Modified Final Judgment

MIN - Mobile Identification Number

MSU - Message Signaling Unit

NPA - Numbering Plan Area

OA&M - Operation, Administration and Maintenance

OPC - Originating Point Code

OSI - Open System Interconnect

POI - Point of Interface

POT - Point of Termination

PSTN - Public Switch Telephone Network

R/LSTP - Combined Regional and Local STP Pair

SCCP - Signaling Connection Control Part

SNAC - Signaling Network Administration Center

SSP - Signaling System Point

SS7 - Signaling System No. 7

STP - Signal Transfer Point

SSN - Subsystem Number

TIA - Telecommunications Industry Association

WIF - Wireless Interconnection Form

4. 1. 1AESS

4.1. 1.1 general




This TMP provides a description of the various Commercial Mobile Radio Service (CMRS) interconnection arrangementsin the 1AESS. Refer to the General Section of this TMP for a more detailed description of CMRS interconnections to ournetwork.

4.1.1. 1.1.1 Reason For Issue

This is the twelfth issue of this TMP. It has been revised to include translation information on the 2B Two Way trunk groupthat is tariffed in the SWBT states.

4.2. 1.2 generic requirements

4.2.1. 1.2.1 Base Generic Required

The only feature and generic requirement would be for the Wireless E911 feature. All other interconnection types areavailable in all 1As in our network. The Wireless E911 feature is available with 1AE13.02 PPU.

4.2.2. 1.2.2 Feature Requirements

9SW911 - Defines the feature group for the wireless E911 feature. 9SW911 requires the feature groups 9SE911,Enhanced E911 feature, and 9SISUP , Integrated Services User Part.

9FW911 - Defines the feature package for W911. The feature package number is 9F038.

4.3. 1.3 Translations

4.3.1. 1.3.1 Type 1 Terminating (INC from the CMRS) Translations

Incoming traffic from the Mobile Telephone Switching Office (MTS0) will be delivered to SWBT end office (E.O.) or zoneoffice via a one-way incoming or two-way TYPE 6 trunk group (TG). A screening line equipment number (SLEN) must beassociated with the TYPE 6 TG which provides TWLT capabilities to the incoming traffic. The SLEN should be associatedvia recent change (RC) with a billing directory number (DN), a new local measured service (LMS-V18 recordings) lineclass code (LCC) with an originating major class of 27 and an optional presubscribed Primary InterLATA Carrier (PIC).

Any state which currently is not providing LMS will be required to establish an LMS chart column with ANI 7 and anassociated LCC. Oklahoma and Kansas, due to their RCC tariff filing will require an intra office LMS band to be established.Message billing index (MBI) 9 should be used to identify the intra office LMS band. however, Texas will require a newchart column with MBI 9 for all local calls and ANI 7 for operator and interLATA calls. Missouri should duplicate their LMS




chart column and then modify the new chart column to provide ANI 7 for all operator assisted calls. Arkansas will requirea new chart column to be established for RCC. The following are the bands to be established for Arkansas:

RCC Band 1 = MBI 2 (0-7 miles)

RCC Band 2 = MBI 3 (8-14 miles)

RCC Band 3 = MBI 4 (15 and up miles)

The following translations should be used to established the trunk class code associated with the TYPE 6 trunk group:

WORD 1

Outpulsing = MF (001)

Supervision = 0011(E+M)

Trunk Usage = Two Way (10)

WORD 4

Flash Timing = YES

Flash Repeating = YES

CPI = 21

4.3.2. 1.3.2 TYPE 1 Originating (OGT to the CMRS) Translation

Land line originated traffic will be delivered to the CMRS via a dedicated or partial NXX. This trunk group may be MF orSS7 signaling. These trunk groups are built as Type 1 non-special trunk groups.

4.3.2.1. 1.3.2.1 Dedicated NXX

When the RCC is assigned a dedicated NXX, the NXX must be opened in all rate centers and Toll Digit Index translators(TLDI) for every switch in the LATA. For all switches except the zone office providing the TYPE 1 connection, the dedicatedNXX should be routed to the existing trunk groups which route either on a direct or indirect basis to the zone office.




The zone office will require at least one new rate and route pattern (RRP) and a route index pointing to the TG establishedbetween the CMRS and the 1A zone office.

4.3.2.2. 1.3.2.2 Partial NXX

The RCC may be assigned directory numbers (DNs) in blocks of 100 numbers. If the RCC is assigned less than a dedica-ted NXX and if the NXX code provided to the RCC is not currently a normalized office code (NOC) in the 1A zone officeto which the CMRS is connected, then NOC to number group number (NGN) , NGN to rate center (RAC) and DN trans-lations must be established.

The DN subtranslator should be seized and initialized to RI 85 and then the range of DNs purchased by the RCC shouldbe translated with the RI pointing to the CMRS TG. If the RCC is assigned DNs in blocks of 1000 numbers, then the DNhead table should be translated with a route index (RI) pointing to the CMRS TG.

4.4. 1.4 Type 2A Interconnection The Type 2A CMRS connection is an Access Tandem interconnection. The 1AESS is no longer deployed as an accesstandem switch in SWBT, therefor no Type 2A connections should be provisioned.

4.5. 1.5 Type 2B Interconnection The TYPE 2B interconnection will only provide the RCC with originating and terminating access to directory numbersserved by the end office to which it is connected. Calls to numbers that have ported out of the end office should also beallowed to complete. The RCC may choose to route any overflow traffic, originating in the end office, via the accesstandem to which the RCC has a 2A interconnection.

4.5.1. 1.5.1 Type 2B Terminating (INC from the CMRS) Translations

A one-way incoming TG must be established to carry traffic between the CMRS and 1AESS. The trunk group supplementaltranslations should have a CIC=698, CIAMA indicator turned on and the trunk class code should have the TCCID indicatorset to a 1 to allow terminating FGD AMA records to be produced on incoming calls from the CMRS.

In other words, both the TG and the TCC will be translated the same as a direct IC TG. This TG should be associatedwith a TLDI or rate center. In most cases, an additional TLDI or rate center will need to be built and dedicated to thisservice. The additional TLDI or rate center may be copied from the existing TLDI or rate center used to allow IC traffic tocomplete only subtending intraswitch codes.

In order to allow calls to ported out DNs to complete, all subtending codes in this rate center should have the possibletrigger indicator set to 1 in the RAC or TLDI. If this trunk group is assigned to your 'regular' rate center, the codes shouldalready have the possible trigger indicator set to 1.




This trunk group may have either MF or SS7 signaling and would normally be built as a type 10 trunk group.

A carrier common block should be established for carrier identification code (CIC) 698. This common block will be usedto allow CIC 698 to be associated with the CMRS incoming TG and will be used for billing purposes to identify theterminating FGD recording as RCC usage. Therefore, care should be taken to insure any call dialed on a 10XXX(XXX=698) basis is blocked and receives appropriate announcement treatment.

4.5.2. 1.5.2 Type 2B Originating (OGT to the CMRS) Translations

The translations required in a 1AESS for a TYPE 2B RCC connection for originating traffic destined for the CMRS is thesame as the translations required for a TYPE 1 end office connection. Refer to paragraph 1.3.2. for detail information.however, directory numbers assigned for the 2B connection should be in blocks of 1000 numbers if a partial NXX servingarrangement is used

4.5.3. 1.5.3 Type 2B Two Way ( INC/OGT from/to the CMRS) Translations

The translations for TYPE 2B Two Way combine the incoming and outgoing trunk group for the CMRS. The trunk groupmust be built as 2way Type 10 and maybe use MF or SS7 signaling. Refer to paragraph 1.3.2 for detail information onthe outgoing side of this trunk group and Refer to paragraph 1.5.1 for the incoming side of this same trunk group.

4.5.4. 1.5.4 Type 2C - Incoming Wireless E911 Trunk Group

The Wireless E911 Feature handles incoming wireless calls over type 10 and type 15 trunk groups using CCS7 signaling.These trunks are not marked as dedicated E911 trunk groups. However, they must have an ESCO assigned in the Qoption word of the supplementary TGN auxiliary block. The ESCO is used to route the call to the default ESN when thePseudoANI information is missing or does not lead to a valid ESN.

This trunk group is established with a RC:TG: message. This trunk group will not need to be marked as a dedicated E911group or assigned an emergency call digit. The format for this recent change is in 231-318-334.

The 1216 entries will be a Type 17 in KP column 65-66 and the assigned ESCO number in KP columns 76-78.

This trunk group is ordered as a Type 2C Mobile Services Interconnection type.

EHHHHHHHHHHHHHHHH

4.6. 1.6 CMRS Billing Type 1-




CMRS-to-LANDLINE - generates a local measured rate AMA recording. This is the present methodology for recordingand billing access.

Type 2B-

CMRS-TO LANDLINE - utilizing either MF or SS7 signaling will generate a terminating FG D 119 call code. Note: BecauseSWBT has not currently equipped end offices with the Cellular Interconnection AMA software, Call Code 065 as documen-ted in Bellcore GR-1504 is not available.

AWCP-

LANDLINE-to-CMRS - local calls will generate 067/074 call codes. Note: the coin is not returned from pay stations. Tollcalls will generate a 006 call code at the end office.

4.7. 1.7 Hardware NA

4.8. 1.8 References Bellcore Notes on the Networks, Issue 3, December 1997 - Mobile Services Interconnection

LT 231-318-334, Issue 9, August 1998 - Trunk Translation Recent Change Formats

LT 231-090-288, Issue 7, June 1998 - Universal Emergency Service Number 911 Feature Enhanced 911 Service FeatureDocument

5. 2. DMS100

5.1. 2.1 GENERAL This document contains all the interconnection trunking arrangements available to Cellular Mobile Radio Service (CMRS)providers. The detailed description of each service is available in the General section of this method and procedure. Asnoted, this TMP was known as Radio Common Carrier, but is renamed to Cellular Mobile Radio Service. Anyupdates tothis TMP will be found in APEX document SBC-002-204-210.

5.1.1. 2.1.1 REASON FOR ISSUE/REISSUE




The 13 issue of this section of methods updates the AMAOPTS datafill requirements on the CMC tuples. All changes areindicated by a | in the right margin.

5.2. 2.2 GENERIC REQUIREMENTS

5.2.1. 2.2.1 BASE GENERIC REQUIRED

Type 1, Type 2A, Type 2B, Type 2D, All current generics support these interconnection types.

Type 2A Equal Access

Type 2C WEC /911 LEC/LET008 and beyond.

5.2.2. 2.2.2 FEATURE REQUIREMENTS

Type 2A Access Tandem

EQA00001/00004 Type 2A Cellular Interconnection MF

ISUP00001 Type 'S' Cellular SS7 2A Interconnection (includes

Cellular Type 2B)

Type 2C E911 Tandem

One of:

ENS00001 LDT PSAP

or

ENS00002 ACD PSAP

One of:

ENS00003 Small SRDB

or

ENS00004 Large SRDB

ENS00005 E911




ENS00010 Default Routing

ENS00011 E911 Routing via AIN

All base AIN and SS7 software and datafill is required. See TMP 93-07-001 and 95-01-002 for additional softwarerequirements.

Patches RIP04BCI and RIP05BN0 were required in the TRI lab during testing to place pANI in ChargeNumber parameterof the query.

5.3. 2.3 TRANSLATIONS

5.3.1. 2.3.1 TYPE 1

The TYPE 1 CMRS two-way or incoming only connection is an end office implementation that uses the PX trunk grouptype and MF signaling in the DMS 100. The PX trunk group type is the recommended trunk group for all non-PRI or SS7DID/DOD arrangements. The SS7 Type 1 service is called 'Type 1 Outbound with SS7' and is one-way outgoing only.

When the CMRS is assigned a dedicated NXX, the NXX must be opened in all switches in the LATA. The dedicated NXXshould be routed to the existing end office trunk groups which route to the zone office providing the Type 1 trunk group.The zone office will require an OFRT pointing to the trunk group established between the CMRS and the zone office.Through service orders, the range of DNs assigned to the CMRS should be routed to the designated Type 1 trunk groupvia OFRT.

The CMRS may also be assigned directory numbers (DNs) in blocks of 100 numbers. If less than a dedicated NXX isassigned and the NXX code provided is not currently a working NXX in the zone office, the TOFCNAME entry must beestablished. Through service orders, the range of DNs assigned to the CMRS should be routed to the designated Type1 trunk group via OFRT.

The following tables require datafill to provide the TYPE 1 features in the DMS100, datafill examples follow:

CLLI TRKGRP

TRKSGRP TRKMEM

CXGRP (PX trunk group) MRSANAME (PX trunk group) MUMRMBI (PX trunk group) MUMRTAB (PX trunk group)

OFRT

TYPE 1 TWO-WAY

The incoming/two-way CMRS to Land feature requires the line features provisioned through the PX trunk group type andassociated tables.

TABLE CLLI




ALLTELMOB 398 ALL_TEL_MOBILE

TABLE TRKGRP

GRPKEY GRPINFO

ALLTELMOB

PX 27 TLD NCRT 2W CD MIDL Y MOBL NSCR 501 LCL NONE NONE LCA1 N

N 32 MRS5 5012619999 NODIALTN N Y 288 Y LATA528 N $

FIELDRESULT FIELD RESULT

GRPTYP LCANAME LCA1

TRAFSNO LCABILL N

PADGRP TLD AIOD N

NCCLS NCRT PXCGRP 32

DIR MRSA MRS5

TRAFCLS BILLNO 5012619999

SELSEQ MIDL DTONE NODIALTN

TOLL LOCALCMC N

PRTNM MOBL Y

SCRNCL NSCR PIC 288

SNPA 501 CHOICE Y

ORIGSRCE LCL LATANM LATA528

CHGCLSS NONE BCLID N

ZEROMPOS NONE OPTIONS $

TABLE TRKSGRP




ALLTELMOB 0 DS1SIG

STD 2W DP WK N 16 16 DP WK 70 0 N NO NO N N N C 100 UNEQ

FIELDRESULTFIELDRESULT

CARDCODE DS1SIG NUMSTOPS 0

SIGDATA STD GLAREYD N

DIR CCONT NO

IPULSTYP RNGBCK NO

ISTARTSG ESUPR N

OVLP SAT N

PSPDSEIZ REMBSY N

PARTDIAL DIALMODE C

OPULSTYP TRKGRDTM 100

OSTARTSG ECSTAT UNEQ

IDGTIME 70

TABLE CXGRP

CUSTKEY SPB CTD EWATS PXOPTION

32 5012619999 (RMR)(RMT)(FANI 07)$

NOTE: Option RMR = Answer Supervision Originating

Option RMT = Answer Supervision Terminating

Option FANI = ANI 7 (Requires OCCINFO be set Y in both fields ANI and FANI if carrier

wants to receive ANI 7 from the CMRS.)




TABLE MRSANAME

MRSA

MRS5

TABLE MUMRMBI

MUMRKEY DETAILED TIMED RECRDMBI MBI

9

NOTE: MBI 9 will be used only where state LMS or RCC tariffs require an intra office band.

TABLE MUMRTAB

KEY MUMRMBI

MRS5 633 4

TABLE OFRT

RTE RTELIST

410 (N D ALLTELMOB 0 N N ) $

TYPE 1 OUTBOUND with SS7

The one-way outgoing trunk group should be established as an IT type trunk group with SS7 signaling. Land line originatedtraffic will be delivered to the CMRS via a dedicated or partial NXX through table OFRT. The following tables requiredatafill:

CLLI TRKGRP

TRKSGRP TRKMEM

C7TRKMEM ISUPDEST (requires C7RTESET)

OFRT




Standard CCS7 requirements should be met between the CMRS and SWBT networks before SS7 trunk groups aredeployed.

5.3.2. 2.3.2 TYPE 2A

The TYPE 2A CMRS interconnection is to or from an Access Tandem (AT). Previous translations provided billing ofincoming access by the CMRS through the use of a one-way incoming ATC type trunk group, creating call code 119records. New software has been activated in the DMS100 AT for trunk group type CELL (functional group EQA00004introduced MF signaling 2A trunk groups). The IT trunk group has new options to provide CELL 2A trunk groups with SS7signaling (functional group ISUP0001). Three new fields are added to table AMAOPTS which create the new call coderecords 064 and 066 used for incoming and outgoing access.

The CELL trunk group can handle the incoming interlata and intraLata traffic served by the Type 2A group. 800 querytraffic cannot be routed over the MF Cell Type 2A group.

The IT group options are BILLNO and CELL with refinements, for Type 2A SS7. (InterLata and 800 query traffic can alsobe routed using the IT group but has the same AMA implications as the MF CELL trunk group type.)

Both the CELL trunk group and the IT trunk group can be provisioned as two way trunk groups. This will eliminate therequirement for directional trunking that exists currently. (During the conversion process in 1996, trunk groups werecombined if the CMRS customer desired. Some directional arrangements may still exist, but two-way is preferred.)

NOTE: (Previous instructions limited Type 2A Mobile to Land to intralata codes. A separate equal access trunk groupwas required to handle calls bound for an interexchange carrier or an 800 query. This restriction is no longerrequired with the use of CELL trunk group software; intralata local and toll, interlata/carrier access, and 800 query[SS7 IT only] traffic can all be combined on the same Type 2A group.)

Table AMAOPTS has three new fields which control the call code records generated for Cellular Mobile Carriers (CMC).To activate the call code 066 records the entry CMCTERM (Cellular Mobile Carrier Terminating) must be set ON. TupleCMCORIG (Cellular Mobile Carrier Originating) controls call code 064 and should be OFF. A third entry CMCICWK(Cellular Mobile Carrier InterExchange Carrier Wink) controls the connect time recorded when an Equal Access Inter-connection call is recorded. If set ON the connect time is recorded when the billing wink is passed from the IXC, insteadof the time the CMC trunk is seized. A CMC access record is not created unless a billing wink is received from the FGDcarrier. This field should now be set OFF, allowing interlata or carrier bound traffic to create the correct billing in the AMArecord and to generate a CC110 whether the call is answered or not.

An example of datafill for TRKGRP type CELL from documentation follows.

NOTE: ( Local datafill requirements should prevail where different from example.)




· The code in table CLLI for the trunk group is CMCABCAT.

· The trunk group type is CELL.

· The direction is two-way (2W).

· The traffic class is NIL.

· The select sequence is set to MIDL.

· The connecting NPA is 613.

· The STDPRTCT name is PEA.

· No class-of-service screening is required.

· The trunk group is assigned to serving NPA 613.

· The directory number to be used in the billing records is 6211234.

· Carrier connect wink is not required.

TABLE TRKGRP

GRPKEY GRPINFO

CMCABCAT CELL 0 TLA NCRT 2W NIL MIDL 613 PEA NSCR 613 6211234 N

The following datafill reflects the changes required in table AMAOPTS:

TABLE AMAOPTS

OPTION SCHEDULE

CMCICWK OFF

CMCORIG OFF

CMCTERM ON

An example of datafill for TRKGRP type IT optioned for CELL type 2A from documentation follows.. (NOTE: Local datafillrequirements should prevail where different from example.)

TABLE TRKGRP




GRPKEY

GRPINFO

SUP2WIT IT 0 ELO NCRT 2W NIL MIDL 519 PEA NSCR 919 000 N N (BILLNO 9198480833) (CELL 2A)$

Land to CMRS over a Type 2A arrangement requires dedicated NXX to the carrier. The DMS access tandem can routethe call to the CMRS, based on 3 or more digits in HNPACONT.HNPACODE and RTEREF, to the TYPE 2A outgoing ITtrunk group.

A unique office route (OFRT) is required that points to the Type 2A trunk group CLLI.

The CMRS NXX is designated as intraLata; therefore, no entry is required in the LATAXLA table as intraLata/intraStateis the default for digits not found.

Those tandems combined with Traffic Operator Services (TOPS) functionality, must insure that the incoming operator(TOPS) trunk groups class of service screen allows completion of the CMRS NXX to the operator, as well as allowing theoperator to complete to the CMRS NXX.

Combined DMS 100/200, end office and tandem switches may require translations input for the CMRS NXX to the localcalling area screen (LCASCRCN), the measured service area name tables (MUMRTAB, MUMRMBI) and originatingSTDPRTCTs accessed by subscriber lines.

TYPE 2A EQUAL ACCESS

InterLata calls bound for IXCs and 800 calls requiring database lookup can be routed to the AT on separate one-wayincoming Equal Access, e.g. FGD signaling, trunk group arrangement. These trunk groups can be either MF or ISUP(SS7) and are translated as trunk group type IT in the DMS tandems. The AT will translate and route on the first 7- digitsreceived. These are the routing code (0ZZ) and the Carrier Identification Code (CIC).

CMRS 800 queries are done via the Equal Access trunk arrangements and will require FGD signaling in the form 0ZZ0110.Similar translations are in place for independent LEC switches subtending an AT SSP on a contract basis. See TMP92-10-001 800/8XX Portability for details.

Conversion of the Equal Access trunk groups to CELL functionality will generate the 066 and 110 call code records fororiginating and 064 and 119 call code records for terminating access billing in the SWBT AT. Call Code 141 or 142 willalso be generated for 800 queried calls. The result is two records for each Equal Access or 800 call handled by the SWBTAT for the CMRS provider.

The conversion of the Equal Access trunk groups will allow for combining both interLata and intraLata calls on one trunkgroup between the AT and CMRS. This should only be done with consent of the CMRS provider, but is the preferredmethod of interconnection.

Datafill requirements for Type 2A Equal Access are similar to previous work on the intraLata 2A trunk group. The IT trunkgroup type has options BILLNO (10-digits) or billing number and CELL type 2A, for SS7 trunk groups. MF trunk groupsshould be converted from IT to CELL type trunk groups and include a billing number. (NOTE: The CELL trunk group typedoes not support 800 calls from the CMRS to E800 SSP, such calls should be handled via SS7 trunk signaling only.)

TABLE TRKGRP




GRPKEY

GRPINFO

CMRSEAS7 IT 0 ELO NCRT IC NIL MIDL 519 EQA NSCR 919 000 N N (BILLNO 9198480833) (CELL 2A)$

MFCMRSEA CELL 0 TLA NCRT IC NIL MIDL 613 EQA NSCR 613 6211234 N

Table STDPRTCT should be datafilled to allow intralata calls to route and include the 0ZZXXXX required for interexchangecarrier routing. The SS7 Type 2A will include 0ZZ0110 for E800 query processing.

TABLE: STDPRTCT CELL: STDPRT

02 058 D VACT

0590288 0590288 T NP 7 OFRT 142 7 7 NONE (800 response 0ZZ)

0590333 0590333 T NP 7 OFRT 13 7 7 NONE (800 response 0ZZ)

0670110 0670110 NSC DD 7 7 E800 NA (invokes 800 query)

0670288 0670288 T NP 7 OFRT 142 7 7 NONE (direct dial to IXC)

0670333 0670333 T NP 7 OFRT 13 7 7 NONE (direct dial to IXC)

068 09 D VACT

200 410 N NP 0 NA

411 411 D VACT (should not receive DA calls on 2A)




412 9 N NP 0 NA

TABLE AMAOPTS

OPTION SCHEDULE

CMCICWK OFF

Table OCCINFO field CMCMON should be changed to Y for each IXC. This allows the AT to monitor the second stageof signaling to obtain the called number for recording in AMA records. (NOTE: Field CMCMON in table OCCINFO doesnot affect the call code 66 and 110 billing records generated for MF CELL-to-SS7 ATC calls. The called number is alwayscollected and placed in the TERM NPA and TERM NUMBER fields of the billing records if it is available.)

TABLE OCCINFO

CARRNAME CARRNUM ACCESS ORIGCARR INTER INTNTL INTRA ANI

FANI ONISCRN AD1 OVERLAP INTERS INTRAS TERMREC OCCSEPNO

OPSIG PICIND NOA950 INCCPN DTMFIND OPSERV CACBLOCK CTDOA

CMCMON SCRNWATS CRMCRA ATPINCL INTRAOPR

CAR1 777 EAP Y Y

LONG 0

FGRPC Y

Y N

5.3.3. 2.3.3 TYPE 2B

The Type 2B trunk group may be used to provide interconnection for originating and terminating access to and from CMRSat an end office for DNs served by that end office only. (Calls to NXXs subtending the AT portion of a combined Local/Tandem switch will not be permitted via the Type 2B arrangement.) The two-way Type 2B interconnection is establishedusing directionalized trunk groups in order to create access records for calls from the CMRS. Release 12 of methodsintroduces the Land to Mobile Type 2B as a tandem relief mechanism, used in place of, or added to existing type 2Aserving arrangements.

Incoming CMRS to LAND

An ATC type trunk group, either MF or SS7 and assigned a unique STDPRT, is required for incoming calls on the Type2B arrangement. The STDPRTCT allows calls to the EO NXX codes only (both Host and remote), all other digits are




sent to D VACT for treatment. (The CMRS may use a Type 2A arrangement for overflow CMRS to Land traffic, if both theEO and CMRS are connected to the AT.) The ATC trunk group is associated with the pseudo CIC 0698, used for all CMRS2B incoming trunk groups. CIC 0698 requires standard translation datafill in tables OCCNAME and OCCINFO before useon a Type 2B trunk group.

Legal and regulatory have issued guidelines for type 2B incoming trunk groups and LNP interactions, such that; SWBTwill allow unqueried calls to ported numbers routed over Type 2B to be properly routed to their final destination. Thus callsthat are unqueried and the dialed NXX is native to that end office will be completed (for both ported and non-portednumbers). This will require response mapping of the incoming STDPRTCT for LNP calls from the CMRS to end officethrough the AIN Response Mapping capabilities described in TMP 91-05-002. Mapping should be established that allowsthe FLRN returned by the ISCP to be valid for call completion, instead of blocked as it is in the incoming STDPRTCTassociated with the trunk group.

DMS switches cannot complete calls from Access To Carrier (ATC) trunk groups to ATC trunk groups. This inhibits callcompletion when a call is received via Type 2B interconnection and the called number is remote call forwarded to aninteroffice number routed via another ATC trunk group. This scenario exists regardless of the signaling protocol, MF versusSS7. Product Management (Marketing) is aware of this limitation.

Outgoing Land to CMRS

The Type 2B Land to CMRS interconnection requires similar translations input as the TYPE 2A arrangement in the AT,that is an IT trunk group type whether MF or SS7. However, only the CMRS NXX(s) local to that EO should be allowedto route over the outgoing trunk group. Only traffic originating on that switch should use the type 2B trunk group. Alternaterouting of the TYPE 2B to TYPE 2A via the tandem is allowed for overflow, if both EO and CMRS subtend the AT. Tariffswill be filed in all SWB region states for Land to CMRS (MOBILE) Type 2B.

5.3.4. 2.3.4 TYPE 2C

CMRS to E911 PSAP is provisioned using the Type 2C trunking arrangement. Dedicated SS7 trunk groups are requiredfrom the CMRS to the 911 tandem. Depending on the CMRS switch type, SS7 protocol can contain required data in oneof two forms:

Dedicated E911 SS7 Trunk group with CalledParty = 911, CallingParty = MDN, GenericDigits = pANI

or

Dedicated E911 SS7 Trunk group with CalledParty = pANI and CallingParty = MDN

(MDN, mobile directory number and pANI, pseudo ANI representing the tower face)

The trunk group translations must indicate which of the two variations is used. This is accomplished through datafill of thetrunk option E911. SS7 for E911 is built as an IT type trunk group.

TABLE CLLI




ECP911SS7 293 SS7_911_TO_ECP

TABLE TRKGRP

ECP911SS7 IT 0 NPDGP NCRT 2W IT MIDL 000 NPRT NSCR 314 000 N N

(E911 021 900 WRLS_CLD)$

NOTE: The WRLS_CLD table entry means pANI is in the CalledPartyid. A WRLS_STD table entry means pANI is in theGenericDigits parameter. The option E911 includes the ESCO (which will indicate tower number) and default ESNof the trunk group.

TABLE TRKSGRP

ECP911SS7 0 DS1SIG C7UP 2W N N UNEQ NONE Q764 THRH 0 ATLISUPS $ NIL SGRPYLD N

TABLE TRKMEM

ECP911SS7 0 DTC 0 18 9

See TMP 98-09-001, Issue 001 of September, 1998 for full details on Wireless Emergency Services.

5.3.5. 2.3.5 Type 2D

CELLULAR DIRECTORY ASSISTANCE CALL COMPLETION (CDACC)

Cellular callers are connected to the TOPS switch by TOPS type trunk groups from the CMRS. Directory Assistance callscan be completed by the TOPS for the cellular customer. Two methods of DACC are available, however, only one allowsthe cellular roamer (customer not in home area) to use DACC. Feature Group C (FGC) signaling method and Type 2Dinterconnection which uses Feature Group D (FGD) signaling. FGD is required to allow cellular roamers access to DACCservices.

Feature Group C DACC

Currently the FGC method is used. The following translations (example datafill only) are necessary:

DACC SINGLE RATE CELLULAR TRANSLATIONS

TABLE CLLI




I316 147 STLSSMOMV1MD_AM322723_DF_4TFDAG1

TABLE TRKGRP

I316 TOPS EML6 NCRT IC MIDL 314 STLS NLCA NSCR DNLOOKUP 0001 DANI 5310834 N

TABLE TRKSGRP

I316 DS1SIG

STD EI N N Y C UNEQ

TABLE TOPSBC

I316 531 NLCS NSCR 31453 TOPS

TABLE TOPEATRK

I316 CONFORM 288 L520 NSCR NSCR NSCR 314 $

TABLE AMATKOPT

I316 (TRKINFO)

DACC MULTI RATE TRANSLATIONS

TABLE CLLI

I320 150 STLSMOMV1MD_AM322724_DF_4TFDAG2

TABLE TRKGRP

I320 TOPS EML6 NCRT MIDL 314 STLS NLCA NSCR SP DNLOOKUP N Y 10 0001 BELL 20 2 2 Y Y OFFHK N N

TABLE TRKSGRP

I320 DS1SIG

STD EI EI N N Y C UNEQ

TABLE TOPSBC

I320 420 NLCA NSCR 314420 TOPS

TABLE TOPEATRK

I320 CONFORM 288 L520 NSCR NSCR NSCR 314 N N $




TABLE AMATKOPT

I320 (TRKINFO)

In addition to the above translations the following tables are datafilled by the Operator Facilities Group:

TABLES

DATRKOPT TOPSDISP

BRANDOPT BRANDANN

SPLDNID RESTBIL

DARSTBIL DABILL

ADACCOPT RESTAMA

TYPE 2D INTERCONNECTION for DACC

The type 2D interconnection will give the CMRS access to the TOPS for Cellular Directory Assistance Sent Paid (SP)Call Completion Service (DACC). This will include the Cellular Roamers (Cellular callers originating calls outside theirhome area). The CMRS will be required to establish a new TOPS type trunk group, with a calling ID of COMFGD, usingFeature Group D (FGD) signaling from their network to the serving TOPS office. Each CMRS will be uniquely identifiedby a Carrier Identification Code (CIC), call completion will use Equal Access translations.

FGD signaling on a TOPS COMFGD trunk takes place as follows: The Automatic Number Identification (ANI) is sent,followed immediately by the called number stage. Important features of COMFGD signaling are:

Start Translation (ST) digits are not primed (i.e., STP ST2P and ST3P are not used). Instead, the station class is identifiedbased on the ANI information digits, as specified in TOPS table OSSCAT.

Key Pulse (KP) digits are not primed.

ANI consists of two information digits (II) followed by 10 calling digits for ANI success calls. The resulting pattern is KP-II-NPA-NXX-XXXX-ST.

The digit, 0, is included in the called number as a prefix to indicate that the call is operator assisted. Cellular Carriersforward 3/10 called digits and the resulting pattern is KP-0-411-ST and KP-0-NPA-555-1212-ST.

Wink response between the ANI stage and the called digit stage is sent.

FGD digit signaling ends with a wink; for calls that are answered and calls that go to an operator, the sending officereceives an off hook after the wink.

The CMRS must send 10 digits for the calling number to insure correct billing records.

NOTE:




( If a call that arrives from a CMRS turns out to be interLata, call completion will not be offered. However, NationalDA offerings to residential customers created the possibility of call completion by the CMRS network. Methodsfor this service are pending.)

The CMRS Interconnect form will indicate the request for DACC by the provider. This will include the indication for aCOMFGD trunk group type and the CIC associated with the CMRS.

If an existing FGC arrangement exists, the trunk members should be moved into the new FGD trunk group. Both DA andDACC calls can be handled by the FGD trunks. This must be coordinated with the CMRS.

Example translations follow:

TABLE CARRNAME

CELL1

TABLE OCCINFO-

CARRNAME CARRNUM ACCESS ORIGCARR INTER INTNTL INTRA ANI FANI

ONISCRN AD1 OVERLAP INTERS INTRAS TERMREC OCCSEPNO OPSIG PICIND

NOA950 INCCPN DTMFIND OPSERV CACBLOCK CTDOA CMCMON SCRNWATS

CRMCRA ATPINCL INTRAOPR

CELL1 0306 EAP Y N

LONG NONE N

N

N

The following fields should be datafilled as above, all other fields will vary according to the locally offered services of theCMRS:

Access = EAP

Overlap = Y




Inters = Y

Opsig = NONE

Opserv = Y

TABLE CLLI

RCCA 189 RCCA_CELL1_DACC

TABLE TRKGRP-

RCCA TOPS 31 NPDGP NCRT IC MIDL 214 TXLA NCLA NSCR N RC

COMB N N N 0 0000 COMFGD 20 2 2 N N NN

Field descriptions for table TRKGRP (TOPS)

Field or subfield Entry Explanation

GRPKEY Group key see subfield

This field consists of subfield CLLI.

CLLI alphanumeric Common language location identifier

(1 to 16 characters) Enter the common language location identifier (CLLI) code assigned to the trunk group in table CLLI.

GRPINFO see subfields

Variable group data. This field consists of

subfields GRPTYP , TRAFSNO,

PADGRP,NCCLS, DIR, SELSEQ, SNPA,

PRTNM, (CONTMARK on form only),

LCANAME, SCRNCL, OHNXXSCR,

TRAFCLS, STATCLAS, TIMEOUT,

NPANXXRQ, DISPLAY, NBECCODE,CLGINFO, BYPASUTR, and ISDNAREA.

GRPTYP TOPS Group type Enter TOPS to specify the trunk

group type for traffic operator position

systems.




TRAFSNO numeric (0 to 127) Traffic separation number Enter the

incoming and outgoing traffic separation

number assigned to the trunk group. If a

traffic separation number is not required,

enter 0 (zero).

PADGRP alphanumeric Pad group (1 to 5 characters) Enter the name of the pad group assigned to

the trunk group in table PADDATA.

NCCLS NCRT Operational measurements no-circuit class.

This field is not required for TOPS trunk

groups, enter NCRT.

DIR IC or Direction Enter IC to specify that the traffic

flow is incoming, or 2W to specify that the

traffic flow is two-way.

SELSEQ MIDL, LIDL, CWCTH, Select sequence

CCWCTH, ASEQ or DSEQ

SNPA numeric Serving NPA (3 digits) Enter the serving

NPA code for the trunk group. This code, which is specified in table HNPACODE, specifies routing for digit translation.

PRTNM alphanumeric Standard pretranslator name (1 to 4characters) or NPRT If standard pretranslation is required,enter the name of the standard pretranslator defined in table STDPRTCT to which digit translation is to route after thereceipt of the first digit.

If pretranslation is not required, enter NPRT (no pretranslation).

LCANAME alphanumeric Local calling area screening table name (1 to 4 characters) or NLCA If all incoming calls on thistrunk group require the same local calling area screening, enter the name of the local calling area screening subtable.The entry must be datafilled in table LCASCRCN.

Enter NLCA in this field if one of the following conditions is true:




Traffic on this trunk group is from different sources that require different local calling area screening. Field LCANAME isspecified in table TOPSBC for each BILLCODE associated with this trunk group CLLI. No local calling area screening isrequired.

SCRNCL alphanumeric (1 to 32characters) Class-of-service screening table name or NSCR. Enter a class of servicescreening subtable name if all calls incoming on this trunk group require the same class of service screening. The entrymust be datafilled in table SCRNCLAS. Enter NSCR (no screening) in this field if one of

the following conditions is true:

Traffic on this trunk group is from different sources that require different classes of service screening. The applicable fieldSCRNCL value is then specified in table TOPSBC for each field BILLCODE entry associated with the trunk group CLLI.

No class of service screening is required.

OHNXXSCR Y or NXX screening for operator-handled calls Enter Y (yes) if NXX code screening is required on operatorhandled calls. Otherwise enter N (no).

TRAFCLS CA or Traffic usage class Enter the traffic usage class assigned to the trunk group.

STATCLAS Station class Enter the station class of the trunk group.

This field identifies the station type from which the traffic is coming.

COMBINED Combined: a station class for traffic from noncoin, coin (see note concerning coin stations), and hotel stationtypes. DMS uses the TOPS or TSPS pulsing format signals (ST2P, ST3P ST, STP) and the ID digit to determine whethera TOPS position is required (for example, 1+noncoin with ANI goes on AMA tape without operator intervention). Thedisplay on the selected TOPS position screen informs the operator about the kind of call.

TIMEOUT Y or Timeout The entry in this field specifies whether a timeout is required to detect zero minus (0-) calls when0- is indicated by absence of digits following trunk seizure. Enter N to indicate that a timeout is not required.

NPANXXRQ Y or Display originating NPANXX to operator Enter Y if the NPANXX of the originating trunk group isdisplayed to the operator at call arrival. The format of the display is as follows:

ANI SUCCESS - NPA NXX XXXX of the calling number

ANI FAIL - NPANXX obtained from first entry for the trunk group in table TOPSBC

ONI - NPANXX obtained as for ANI FAIL above

DISPLAY numeric (0 to 31) Instructional display to operator

Enter the index into table TOPSDISP that specifies the special instructions to display to the operator on a trunk groupbasis.




NBECCODE numeric(0000 to 9999) Non-Bell exchange company code Enter the non-Bell exchange company

(NBEC) code. Same as CARRNUM.

CLGINFO see subfields Calling number information

This field consists of subfield CLGID and refinements.

CLGID COMFGD Calling identification If the trunk group uses combined equal access feature group D signaling only,enter COMFGD and datafill refinements NOBILLCD, ANISEIZ, ANIPDIAL, TRTMTSUP, ONLNRATE, COINPD, andNXXVER.

NOBILLCD numeric(1 to 63) Number of billing codes Enter the number of billing codes (NXX allocated to originate trafficon this trunk group) plus spares that are reserved in table TOPSBC. Entries outside the indicated range are invalid.

ANISEIZ numeric(2 to 30) ANI seizure timing Enter the number of seconds that the trunk has to wait for reception of firstdigits of the ANI spill.

ANIPDIAL numeric(2 to 30) ANI partial dial timing Enter the number of seconds that the trunk has to wait for reception ofeach ANI signal or digit but the first.

TRTMTSUP Y or Treatment supervision Enter Y to indicate

that off-hook wink is returned for treatment cases or N to indicate on-hook is maintained.

ONLNRATE Y or Online rating Enter Y to provide online

rating for calls on this trunk group. Otherwise enter N.

COINPD Y or Coin paid Enter Y to provide coin signaling

for calls on this trunk group. Otherwise enter N.

NXXVER Y or NXX verification Enter Y to verify the calling NXX in table TOPSBC. Otherwise enter N. Must be N so theNXX of a Roamer is not checked.

TABLE TRKSGRP

RCCA DS1SIG

STD EI EI N N Y C UNEQ

TABLE TOPSBC

RCCA 420 NLCA NSCR 314420 TOPS

TABLE TOPEATRK




RCCA CONFORM CELL1 L552 NSCR NSCR NSCR 214 N N $

TABLE TOPEACAR

CARDIG CARNAME ALTDISP OPLSCLD CAMABILL ALTCARR NATERM

INTERM OPSERV TDBIDX

0306 CELL1 CELL1 CELL1 UNREST

UNREST SERV NOQUERY Y NOQUERY Y BLK N N N Y 3

(If DACC offering is sent paid set

to QUERY otherwise NOQUERY.)

TABLE AMATKOPT

RCCA (TRKINFO)

5.3.6. 2.3.6 AREA WIDE CALLING PLAN (AWCP)

AWCP allows users, specifically those served by Southwestern Bell Telephone Company (SWBT), to originate calls toCMRS subscribers anywhere within a LATA without incurring toll charges. The CMRS provider is billed on per minute ofuse; rates based on the specific state tariff. AWCP is a one-way service only (e.g. only calls from SWBT to CMRSsubscribers avoid toll charges; calls from CMRS subscribers to SWBT will incur normal interconnection charges). SWBTcalls to CMRS networks will be identified for billing by the use a dedicated NXX to the CMRS provider, existing AMArecords for intraLata toll will be recorded in the SWBT end office. When a call is placed 0- or 0+AWCP, the AMA is recordedin TOPS.

The CMRS will order a dedicated outgoing Type 2A trunk group from the SWBT AT to interconnect at the CMRS switch.The order must specify that the trunk group is for AWCP service. No other CMRS NXXs will route from the AT over theAWCP trunk group. There should be no alternate routing of the AWCP traffic to a regular Type 2A trunk group. All CMRSoriginating traffic must access the appropriate trunk groups as previously defined through out this method.

SWBT End Office

AWCP NXXs should be opened in each SWBT end office in the LATA, calls are dialed using existing local dialing plans(e.g. no prefix seven digits, no prefix 10 digits, and 0+10 digits will be allowed.) An intraLata station paid billing record(Call Code 006) should be recorded for no prefix calls.

Existing AWCP methods in TMP 94-10-002 direct that the STDPRTs (for all classes of service except COIN) and theHNPACONT table break out the assigned AWCP NXX and route it to the Access Tandem (AT) or TOPS in the case ofCOIN. Table STDPRTCT.STDPRT is translated to mark the no prefix call as DD. The AWCP NXX is not included inLCASCRCN tables. These translations generate the call code 006 record. However, this scheme is not without troubleand resulted in removing COIN originated calls from the translation scheme. (The current local rate is acceptable for costrecovery for calls from SWBT Coin lines.)




The recommended translations for creating the call code 006 record are to make use of the STDPRTCT.AMAPRTfunctionality. This eliminates the need to break out the AWCP NXX specifically in subtable STDPRT. The AWCP NXXshould be translated as any other local code in both STDPRT and LCASCRCN. The subtable AMAPRT allows overridingthe local call type and generating a call code 006 record for the call.

The following is an example of an AWCP NXX (742):

TABLE STDPRTCT.STDPRT.POTS

FROMDIGS TODIGS PRETRTE

02 P OA 1 NA TSPS

2 N NP 0 NA

TABLE STDPRTCT.AMAPRT.POTS

FROMDIGS TODIGS AMARSLT

742 742 NONE OVRLOCL N (7 digit local dialing)

OR

501742 501742 NONE OVRLOCL N (10 digit local dialing)

TABLE HNPACONT.HNPACODE.501

FROMDIGS TODIGS CDRRTMT

742 742 HRTE 149

TABLE HNPACONT.RTEREF.501

RTE RTESEL

149 0356 (Common route to Access Tandem)

The resulting AMA record with this translation scheme is call code 006, structure code 00500. Detailed billing informationis recorded, including calling DN, called DN, elapsed time, etc. These translations eliminate problems associated withAIN response translations, especially in Response Simplification. LNP would also be impacted in the future when CMRScustomers can port their wireless numbers under the previous translations recommendations.

Tops Translations

Customers who dial 0+10 (coin and non-coin) will be sent to TOPS. Customers will get the initial deposit back on COINlines, as usual, when calls route to TOPS. Operator handling charges will apply on the 0+ calls, POTS customers will be




billed accordingly. Callers from COIN lines will be asked for alternate billing or directed to deposit the appropriate amount.AMA will be recorded in the TOPS.

Customers who dial 0- and ask the operator to assist them in reaching an AWCP NXX must pay the Operator Assistedor Operator Handled charges for the call. One AMA record will be generated for the call in TOPS, the originating partywill pay the OA/OH surcharge and the cellular carrier will pay the minutes of use for the call.

Translations for AWCP NXXs must be coordinated with the Facility Managers in Operator Services to assure correct ratingand billing translations are added to the Operator databases.

5.4. 2.4 HARDWARE No additional or new hardware is required for CMRS interconnection arrangements.

5.5. 2.5 REFERENCES SS7 End Office Connection (One-Way Terminating (Mobile to Land)) Marketing Service Description, November 12, 1998

Technical Service Description for Commercial Mobile Radio Service (CMRS) Interconnection, Ron Oetting, December,1998

DMS-100 Family NA100 Translations Guide LET0009 and up, NTP 297-8021-350, NORTEL NETWORKS, May, 1998

TMP 89-09-005, CCS7 Trunk Signaling

TMP 92-10-001, 800/8XX Portability

TMP 94-10-002, Area Wide Calling Plan (AWCP)

TMP 98-09-001, Wireless 911

NAB 96-020, AWCP NXX from SWBT Coin Lines

NAB 96-024B, Type 2A SS7 conversion

NAB 97-003, Type 1 Outbound with SS7

6. 3. 5ESS




6.1. 3.1 GENERAL There are various interconnection alternatives for the interconnection of a Commercial Mobile Radio Service (CMRS)provider with Southwestern Bell's network. This TMP focuses on five specific arrangements, which include:

Type 1 Interconnection- Direct CMRS connection through a 5ESS end office with a variation for Integrated Services DigitalNetwork (ISDN) interconnection.

Type 2A- Direct CMRS connection through a 5ESS Tandem office using MF or SS7 signaling.

Equal Access (Type 2A) - Direct CMRS connection through a 5ESS Tandem office using MF or SS7 Signaling.

Type 2B- Direct CMRS connection with a specific end office using MF or SS7 signaling.

Type 2C- Direct CMRS connection with a 5ESS Tandem arranged for 911 emergency service.

On SS7 Trunks a unique Serving Point Code (SPC) must be assigned to each CMRS switch connecting to SWBT's SS7network.

See General Section 0 for additional interconnection descriptions.

6.1.1. 3.1.1 REASON FOR ISSUE/REISSUE

Commercial Mobile Radio Service, issue 12, is being revised to indicate that Type 2A Interconnections (either 1-wayoutgoing or 2-way) do not require an AMA record (call code 064) in the outgoing direction. Changes are denoted by arevision mark ( | ) in the right hand margin.

6.2. 3.2 GENERIC REQUIREMENTS

6.2.1. 3.2.1 BASE GENERIC

All current generics support Commercial Mobile Radio Service.

6.3. 3.3 TRANSLATIONS

6.3.1. 3.3.1 Type 1 Interconnection




A Type 1 (one way or two way) Interconnection to the SWBT end office transports Intra-Lata toll and Local traffic. Thistrunk can only provide MF signaling if it is two-way. SS7 signaling can be provided if the Interconnection is one-wayout to the CMRS. This service is referred to as 'Type 1 Outbound with SS7'.

To establish a TYPE 1 Trunk Group, whether one-way or two-way, use the following guidelines.

6.3.1.1. 3.3.1.1 Individualized Dialing Feature Definition (RCV 12.17, 5601Record)

First build a Feature for the Trunk Group:

RECENT CHANGE 12.17

(5601) INDIVIDUAL DIALING FEATURE DEFINITION

*1. FEATURE IDPTGXX 2. REMARKS ________________________________

============================== FEATURE OPTIONS =============================

3. INHIBITC ________

4. ACTIVATE _

5. ALTCODE _

6. GROUPC _

============================= DEFAULT PARAMETERS ===========================

8. IDP GROUP NAME ________

9. DPAT CATEGORY __

10. ICR SFG ____

· Feature- Use something like IDPTGXXX

6.3.1.2. 3.3.1.2 IDP Group Definition (RCV 9.10, 5601-4 Record)

Assign a IDP GROUP for the Trunk Group:

5ESS(R) SWITCH




RECENT CHANGE 9.10

(56014) IDP GROUP DEFINITION (INDIVIDUAL DIALING)

*1. IDPNAME IDPTGXX

2. REMARKS ________________________________ 15. GRPCARRIER XXXX

3. IDPACTIVE 16. GROUP PTC XXXX

4. ACTALW _

5. DPATALW N

6. ERRTREAT _______

8. ERRRTE USEOFFC

9. DPATTREAT _______

11. DPATRTE ________________________________

12. SLE SYMBOL ____

13. CF DT POTS _

14. ESC TO POTS ___

· IDPNAME- IDPTGXX

· DPATALW- N

· ERRTREAT-USEOFFC which escapes to Office Dialing Plan

· GRPCARRIER- PIC of customer

· GROUP PTC- is used to specify the group presubscribed Intra-Lata toll carrier identification number once IntraLata PIC(PIC 2) is available.

NOTE: There will be no entries on the 9.13 IDP Dialed Code Assignment Record. All dialing will useERRTREAT=USEOFFC so digit interpretation occurs in the DAS.

6.3.1.3. 3.3.1.3 Screening (RCV 10.10, 5301 Record)




Use a unique Screening Index for this Trunk Group for regular toll billing. Local calls receive DMTRM (MBI=9), 411 and555 calls are free:

RECENT CHANGE 10.10

(5301) SCREENING ( CHARGING )

*1. SCR ____

*2. CDI ____

3. SCREENING DATA (SCRNDATA)

ROW PFX NPA OFFCOD RTI CHGI TDV CST IECR CBLK CONF

1 ____ ___ ___ ____ ____ ___ ____ _ _ _____

2 ____ ___ ___ ____ ____ ___ ____ _ _ _____

3 ____ ___ ___ ____ ____ ___ ____ _ _ _____

· SCR=XX; Unique screening index

It is important to establish a unique screen index for this TG.

6.3.1.4. 3.3.1.4 Charge Index Expansion (RCV 10.12, 5302-1 Record)

Set the Message billing index field to 9:

5ESS(R) SWITCH

RECENT CHANGE 10.11

(53021) CHARGE INDEX EXPANSION (CHARGING)

*1. CHGIDX XX

#2. AMATYPE DMRTM

3. MBI 9

4. WATSTYPE __

5. DATACI ____




6. RMK ________________

7. ALT SFC ___

8. ALT CC ___

9. MAX OWATS _

· CHGIDX -XX; unique to the Trunk Group

· AMATYPE - DMTRM for detail message rate, timed, Message Bill Index (MBI)

· MBI =9 .

NOTE: ( MBI 9 will be used only where state LMS or RCC tariffs require an intraoffice band)

6.3.1.5. 3.3.1.5 Trunk Group (RCV 5.1, 5202 Record)

Build the trunk group with the following:

10. SCR ____ unique to this TG

12. DAS line type of DAS

#13. TRK CLASS ________ PF or LTOLLCONß

21. INPLS ___________ MF or ISUP7

22. OUTPLS __________ MF or ISUP7

164. BILLING DN __________ optional but may be needed

170. ANI7 set to Y

If trunk group = MF, then use TRK CLASS = PFß

If trunk group = SS7 (ISUP7), then use TRK CLASS = LTOLLCONß

6.3.1.6. 3.3.1.6 BRCS Trunk Group Assignment (RCV 5.4, 5206 Record)

Assign the feature IDPTGXX to the group:




5ESS(R) SWITCH

SCREEN 1 OF RECENT CHANGE 5.4

(5206) BRCS TRUNK GROUP ASSIGNMENT VIEW

*1. TGN XX_

2. FEATURE LIST (FEATENT)

ROW FEATURE A AC ROW FEATURE A AC ROW FEATURE A AC ROW FEATURE A AC

1 IDPTGXX_ _ _ 8 ________ _ _ 15 ________ _ _ 22 ________ _ _

2 ________ _ _ 9 ________ _ _ 16 ________ _ _ 23 ________ _ _

· TGN- XX (from RCV 5.1)

· Feature- IDPTGXX (from RCV 12.17; Section 5.3.1.1)

Building your trunk groups like this allows you to add and delete trunks from the group without having to go to each memberand make a change.

6.3.2. 3.3.2 Type 2A Interconnection (Tandem)

A Type 2A interconnection provides a connection to SWBT's Access Tandem. Type 2A connections can be either MF orSS7 signaling with either one-way or two-way operation.

This trunk group allows completion of Intra-Lata Toll and local traffic to all end offices served by the Tandem.

Originating FGD traffic from the CMRS to the Inter-Exchange Carriers is routed on a separate tandem equal access trunkgroup. Type 2A trunk groups handle originating and terminating Intra-Lata toll traffic. Type 2A trunk groups are engineeredas direct final with no alternate routing.

NOTE: The INDIT/LDIT used for any 2A CMRS incoming or 2-way trunk group type must block OZZCIC digits. Only Intra-Lata traffic should be accepted from the CMRS provider, this includes Public Response Network Services (MassCalling). Calls from an Inter-Exchange Carrier (IEC) are allowed outgoing from the Access Tandem to the CMRSprovider.

6.3.2.1. 3.3.2.1 Secured Features 128 & 160 (RCV 8.22, 5713 Record)




The AMA Capabilities for Type 2A Cellular Interconnections provides the ability to generate a new Cellular Mobile Carrier(CMC) AMA record for each CMC trunk group and for each direction when a call is completed between the 5ESS AccessTandem for Type 2A Cellular Interconnections and mobile customers.

Call Code 066 may be generated for Terminating Cellular Mobile Carrier calls and Call Code 064 may be generated forOriginating Cellular Mobile Carrier Calls.

For the Type 2A Secured Feature (SFID 128); CMC trunks use in-band MF (Multi-Frequency) signaling, that is, CCS7signaling between the CMC and the Access Tandem (AT) is not supported. Available as a 5E9(1) and later SoftwareUpdate, the CMC Type 2A Cellular Interconnections via CCS feature (Secured Feature 160) implements CCS7 signalingbetween the CMC and the Access Tandem.

The Revenue Accounting Office (RAO) will receive additional detailed billing records for Type 2A Interconnections whenthis feature is active and billing records have been requested for at least one CMC. The content of AMA records willchange somewhat when this new feature is activated. In addition, some 800 Service AMA records and originating ICrecords associated with CMC calls will have their fields modified by this feature, specifically, the Originating Number andService Feature fields.

Secured Feature 160 supports Type 2A with CCS7, while Secured Feature 128 supports Type 2A with MF only.

Activate Secured Features 128 and 160:

SCREEN 1 OF RECENT CHANGE 8.22

(57131) SECURED FEATURE UPGRADE

*1. FEATURE ID 128 and 160

*2. MODULE OFC

3. PASSWD (A password from Lucent is required)

4. ACTIVE Y_

6.3.2.2. 3.3.2.2 Cellular Mobile Carrier Identification (Charging) (RCV 10.16,5056 Record)

The Cellular Mobile Carrier Identification (Charging) view is used to associate a 10-digit billing number with a 2-digitCellular Mobile Carrier Identification (CMC ID) number, in order to facilitate billing of a CMRS carrier. The CMC BILL fieldcorresponds to the BILLING DN field on the TKGRP form.

The CMC ID and Billing Number must first be assigned. Insert RCV 10.16:




RECENT CHANGE 10.16

(5056) CELLULAR MOBILE CARRIER IDENTIFICATION (CHARGING)

*1. CMCID01

#2. CMC BILL3142351111


When ORIG CMC (Originating Cellular Mobile Carrier) is '2A'

· BILLING DN must be entered

· CMC must be 'Y'

· OUTPULSING must be 'MF' or 'ISUP'

· TRK DIR must be 'OUT' or '2W'

· TRKCLS must be 'TTOLLCON'

When TERM CMC (Terminating Cellular Mobile Carrier) is '2A'

· BILLING DN must be entered

· CMC must be 'Y'

· TRK DIR must be 'INC or '2W'

· TRKCLS must be 'TTOLLCON'

It has been determined that SBC-SW does not use and therefore does not require call code 064 (outgoing CMC) records,unless temporary special studies are being conducted by CABS. Therefore, 2-way trunk groups will have only TERMCMC equal to 2A. One-way outgoing trunk groups require no entry in either ORIG CMC or TERM CMC. One-way incomingtrunk groups require only TERM CMC be populated with 2A. In the case of a special study, the translations center mayprovision a trunk group's ORIG CMC entry with 2A.

Update RCV 5.1:

EXAMPLE OF 2-WAY TRUNK GROUP:

(*)1. TGN 369 13. CARRIER ID ____ 25. FREE ANS _

(*)2. TRUNK CHAR _______________ 14. FEAT GRP _ 26. PBX ID ____

(*)3. FEND CLLI ___________ 15. INC TND WNK _ 27. PRIVACY _




4. TRK CHAR CELLULAR 16. ATTTN ___ 28. INSEP ___

5. FAR CLLI ___________ 17. TERA RCVY ___ 29. MODULE ___

6. RMK ________________ 18. IAPT _

#7. TRK DIR TWOWAY 19. CALLMON INH VERIFY ONLY

#8. HUNT TYPE 2WB 20. INPLS ISUP7 GRP SIZ ____

9. SCR 126 21. OUTPLS ISUP7 ACT SIZ ____

10. GLARE ACTION ODDEVEN 22. FAR END NPA ___ SATELLITE _

11. DAS 23. GL ANN TGN ____ TERM SFG _

#12. TRK CLASS TTOLLCON

OPERATOR ANNOUNCEMENT CAMA LATA/TTOLL

34. OUTPL REQ _ 42. ANNC CYCL _ 49. VALNPA ___ 58. CMC Y

35. AUDIBLE _ 43. BARGE IN _ 50. VALNXX1 ___ 59. CMC ID1

36. SIGNAL ________ 44. FC AUD _ 51. VALNXX2 ___ 60. ORIG CMC

37. FREE TERM _ 45. SVC GRP ______ 52. VALNXX3 ___ 61. TERM CMC 2A

212. BILLING DN 314-2351111

6.3.2.4. 3.3.2.4 AMA Call Type (Charging) (RCV 10.12, 5506 Record)

For the CMC AMA call codes to be recognized AMA Call TYPE (Charging) must contain the value CMCOT for originatingtandem or CMCTT for CMC terminating tandem. Insert RCV 10.12 for CMCOT and CMCTT:

RECENT CHANGE 10.12

(5506) AMA CALL TYPE (CHARGING)

*1. AMATYPECMCOT (ORIGINATING) OR CMCTT (TERMINATING)

#2. DETAILED Y

#3. TRACE OTHER

#4. MBI/WATS N




#5. DATA CALLED OTHER

6. SPECIAL N

7. CUSTID N

6.3.2.5. 3.3.2.5 Office Parameters (RCV 8.1, 5509 Record)

CMC WINK CONNECT indicates whether the connect time is recorded when an initial wink is received from the Carrier.This field must equal 'Y'.

6.3.3. 3.3.3 Equal Access (Type 2A Tandem Interconnection)

Equal Access interconnections provide a connection to SWBT's Access Tandem. This trunk group can be either MF orSS7 signaling with either one-way or two-way operation.

Originating FGD traffic from the CMRS to the Inter-Exchange Carriers is routed on this trunk group. This trunk group alsosupports 800 traffic and requires Feature Group D protocol signaling. Type 2A allows combining Inter-Lata and Intra-Latatraffic on the same Type 2A trunk group (only if requested by the CMRS provider) or the CMRS provider can convert theirexisting equal access trunk groups to Type 2A.


A CMRS provider with a Type 2A trunk group that handle Intra-Lata and Local calls and a different Type 2A trunk groupthat handle Inter-Lata and 800 calls can have the same Billing DN assigned to both trunk groups. If the Billing DN for bothtrunk groups is the same, the same CMC ID may also be used. However, the Type 2A equal access trunk group may alsobe assigned a different Billing DN which requires a different CMC ID also (see Section 5.3.2.2 for CMC ID provisioning).

Update existing equal access trunk group fields CMC, CMC ID, ORIG CMC, TERM CMC and Billing DN

(*)1. TGN 895 13. CARRIER ID ____ 25. FREE ANS _

(*)2. TRUNK CHAR _______________ 14. FEAT GRP _ 26. PBX ID ____


4. TRK CHAR CELLULAR 16. ATTTN ___ 28. INSEP ___


6. RMK ________________ 18. IAPT _




#7. TRK DIR TWOWAY 19. CALLMON INH VERIFY ONLY

#8. HUNT TYPE 2WB 20. INPLS ISUP7 GRP SIZ ____

9. SCR 120 21. OUTPLS ISUP7 ACT SIZ ____

10. GLARE ACTION ODDEVEN_ 22. FAR END NPA ___ SATELLITE _

11. DAS 23. GL ANN TGN ____ TERM SFG _

#12. TRK CLASS TTOLLCON

OPERATOR ANNOUNCEMENT CAMA LATA/TTOLL

34. OUTPL REQ _ 42. ANNC CYCL _ 49. VALNPA ___ 58. CMC Y_

35. AUDIBLE _ 43. BARGE IN _ 50. VALNXX1 ___ 59. CMC ID2

36. SIGNAL ________ 44. FC AUD _ 51. VALNXX2 ___ 60. ORIG CMC

37. FREE TERM _ 45. SVC GRP ______ 52. VALNXX3 ___ 61. TERM CMC 2A

212. BILLING DN 314-2352222

6.3.3.2. 3.3.3.2 AMA Changes (Call Scenario)

A call code 066 AMA record will now be generated for each Equal Access and 800 call received from CMRS providers.(See section 5.3.2.3 for more information on AMA. All information applies equally to the two products.)

As an example, a Cellular customer completes a call to an InterExchange subscriber trunk from CMC to Access Tandemand from Access Tandem to the Feature Group D carrier. The FGD Carrier Access record (with Structure Code 0625 andCall Code 110) will be generated in conjunction with the Type 2A terminating record (with Structure Code 0625 and CallCode 066).

The originating number in the AMA record is set to the CMC trunk billing number.

6.3.4. 3.3.4 Type 2B Interconnection

SS7 End Office Connection is one way terminating from the CMRS provider to an end office. The CMRS provider canonly terminate to subscribers served out of the particular end office the trunk is connected to. In the case of a host office,calls will terminate to any remotes that home on the host switch.

Although CMRS providers can only terminate to subscribers served out of that office, calls that are unqueried and thedialed NXX is native to that end office will be completed for ported numbers. Example, 210-222 is a NOC (native NXX)in the end office. CMRS provider routes 210-222-1234 (unqueried ported out number) over the 2B trunk group which nolonger terminate in the end office. This NXX (provisioned on the trunk DAS/LDIT) is assigned an LNP trigger, a query is




launched to the LNP database, an LRN is returned and the LRN (NXX) is routed to the appropriate end office based onPost Query DAS (LDIT) provisioning (See TMP 97-09-001 Local Number Portability).

This trunk group must generate terminating FGD billing records for incoming traffic from the CMRS. A minimal carriercommon block must be established for Carrier ID 0698 to allow the CMRS trunk group to be associated with CIC 0698.


Insert RCV 5.1 (the example below is a Type 2B incoming SS7 trunk group):

RECENT CHANGE 5.1

(5200,5202,5213) TRUNK GROUP

(*)1. TGN 688 13. CARRIER ID 0698 25. FREE ANS Y_

(*)2. TRUNK CHAR _______________ 14. FEAT GRP D 26. PBX ID ____


4. TRK CHAR _______________ 16. ATTTN ___ 28. INSEP ___


6. RMK2B SS7 18. IAPT _

#7. TRK DIRINCOM 19. CALLMON INH VERIFY ONLY

#8. HUNT TYPENONE 20. INPLSISUP7 GRP SIZ ____

9. SCR6 21. OUTPLS ________ ACT SIZ ____

10. GLARE ACTION ________ 22. FAR END NPA ___ SATELLITE _

11. DAS 8 23. GL ANN TGN ____ TERM SFG _

#12. TRK CLASSIC 24. BRCS _

· TRK DIR= INCOM; Incoming direction for incoming trunk groups

· HUNT TYPE = NONE; No hunting because trunk group is not used for outgoing calls

· SCR= 6 (example only); the same Screening index used for Feature Group D terminating can be used. This will generateFGDTL call code 119.

· DAS= 8 (example only); Use an incoming trunk DAS




· TRK CLASS= IC; Interexchange Carrier Trunks

· Carrier ID= 0698; used for billing purposes. A minimal carrier common block must be established for Carrier ID 0698 toallow the CMRS trunk group to be associated with CIC 0698.

NOTE: Carrier 0698 must be inserted on Recent Change View 10.3 before populating this field

· FEAT GRP =D

· INPLS = ISUP7; for SS7 signaling

6.3.4.2. 3.3.4.2 InterLata Carrier (RCV 10.3, 5305 Record)

Insert RCV 10.3:

RECENT CHANGE 10.3

(5305) INTER-LATA CARRIER

*1. CARRIER ID 0698 FEATURE GROUP B ONLY

*2. FEAT GRP 12. FGB CDI ____

#3. ACCESS TYPE LTRM 13. FGB RTI ____

4. LONG REC 14. TRANS CARRIER ___

5. MEASUREMENT N

6. DIG ROUTING Y

7. LEC SERVICE N

9. CARRIER NAME _______

10. SEND ANI II N

11. REMARKS ________________

6.3.5. 3.3.5 Type 2C Interconnection (Tandem)




The Federal Communications Commission (FCC) Wireless 911 Mandate require wireless carriers to provide MobileDirectory Number (MDN), cell site information (Pseudo ANI or PANI) and the ability to identify the latitude and longitudefor 911 calls to the Public Safety Answering Points (PSAPs).

Type 2C, ISUP (SS7), dedicated trunks are required to provision Wireless 911 service.

Refer to TMP 98-09-001 (Enhanced 911 Tandem) for translations provisioning.

6.4. 3.4 HARDWARE No additional hardware is required to support this service.

6.5. 3.5 REFERENCES 235-080-100 5ESS TRANSLATIONS GUIDE

235-118-253 RECENT CHANGE REFERENCE MANUAL

Commercial Mobile Radio Service (CMRS) Interconnection TSD, dated 12-01-98

7. 4. Ericsson AXE

7.1. 4.1 General Commercial Mobile Radio Service (CMRS) provides the various types of interconnections and their trunk group types.

Due to translation complexities, Type 1 and Type 2B interconnection will not be 'generally available' on theEricsson switch. Interconnection arrangements must be negotiated on a customer-specific, case-by-case, basis.Translations are provided only for a standard arrangement.

7.2. 4.2 Reason For Issue/Reissue The TMP 87-06-01 is being reissued to change TYPE 2B 2 WAY SS7 signaling parameters.

Generic Requirements

Ericsson switches must be on L10R5.2 or above.




7.3. 4.3 Translations

7.3.1. 4.3.1 TYPE 1 INTERCONNECTION IN THE AXE

Type 1 interconnection can be a 1-Way or 2-Way trunk group between the CMRS and the end office. This allows incomingcalls to utilize the TWLT and connect to lines served by the end office or continue (tandem) to other carriers through thisinterconnection arrangement.

The Type 1 Commercial Mobile Radio Service (CMRS) connection is an end office implementation, which uses the 'BT1'type trunk group in the AXE. With the implementation of Generic L10R5.2, Ericsson has provided limited screeningassignments to BT-1 trunk types. The most important is the ability to assign a Primary InterLATA Carrier to the trunk groupwith the 'MD' parameter. This will allow assignment of a PIC for all calls encountering the 'CI-1' parameter. Lack ofadditional assignments will prevent the screening of calls from a BT-1 trunk group for different calling scopes and dialingprocedures, therefore, the Type 1 CMRS connection can only be made to the Host wire center.

7.3.1.1. 4.3.1.1 SOFTWARE REQUIREMENTS

Type 1 Interconnection can be provided in the L10R5.2 AXE generic. There is no specific AXE feature or feature packagerelated to this service. The Ericsson AXE10 does not have a feature the other switch types do that will associatethe, 'Trunk With Line Treatment (TWLT)', therefore, the default for incoming CMRS traffic will be in the HOSTcalling scope.

7.3.1.2. 4.3.1.2 TRANSLATION STANDARDS

Route/Charge Origins

57 - CMRS Type 1 - (DA - Texas)

58 - CMRS Type 1 - (Miscellaneous - Texas)

59 - CMRS Type 1 - (Local - Texas)

- (All - MOKA)

B-Number Origins

240-249 - CMRS Type 1 Start of Digit Analysis

410-419 - CMRS Type 1 0,1 Analysis




420-429 - CMRS Type 1 Main Analysis

436-445 - CMRS Type 1 011+CC+NN

446-455 - CMRS Type 1 01+CC+NN

470-479 - CMRS Type 1 700

7.3.1.3. 4.3.1.3 AXE TABLE DATAFILL

The following tables require datafill to provide the Type 1 CMRS feature in the AXE:

Route Data

Routing Analysis

B-Number Analysis

Charging Analysis

Secondary Charging Analysis

The following are examples of the datafill required to provide the Type 1 CMRS feature in the AXE. The examples arebased upon the office standards set up for the AXE.

Assumptions:

* CMRS customer not allowed to dial 10XXX

Route Data

Outgoing Trunk Group

EXROI:R=OUTRTEO,TGN=1133,DETY=BT1,FNC=2;

EXRBC:R=OUTRTEO,R1=LOCS,RSV=513,LSV=4096,MIS1=16;

EXRBC:R=OUTRTEO,MIS3=273,ST=0,MIS4=0,MIS5=19275;

EXRBC:R=OUTRTEO,MIS6=12488,CYCLR=0,DS=0,IMS=0;

EXRBC:R=OUTRTEO,OPER=0,COIN=0,DLP=0,MIS7=0,MIS9=0;

Incoming Trunk Group




EXROI:R=INCRTEI,TGN=1132,DETY=BT1,FNC=1;

EXRBC:R=INCRTEI,R1=LOCR,MA=316365XXXX,MC=1,RSV=1;

EXRBC:R=INCRTEI,LSV=32,MIS1=2,BO=0,R0=59,CO=59;

EXRBC:R=INCRTEI,TO=0,TDCL=0,DT=0,MIS4=0,MIS6=15370;

EXRBC:R=INCRTEI,LOD=0,IMS=0,DLP=6,LATA=<xxx>,MIS10=0;

EXRBC:R=INCRTEI,MIS11=0 MD=<pic>;

Routing Analysis

Add route origin(s) to all routing cases existing in the switch and route accordingly.

B-Number Analysis

B-Number '0' may be used for B-Number Analysis for the Host wire center with the implementation of the 'MD' parameteron the incoming Type 1 CMRS trunk group.

7.3.1.4. 4.3.1.4 CHARGING ANALYSIS

Charge Origin(s) must be added to all charging cases. A call type of 110 should be generated where necessary forInterLATA calls. A call type of 001 and MBI of 009 should be generated for all IntraLATA calls from the CMRS customer.

CHARGING CASE 0 (Local No Prefix)

CROPI:CC=0;

CROSI:BC=CO-0&-10&-16&&-18&-20&-24&-26&-28&-30&-34&- 42&-43&-46&-48&LCM-0,ESA=0;

CROSI:BC=LCM-2,ESA=2;

CROSI:BC=CO-55&-56&-61&-63&-78&-80&-81&-85&&-88&LCM- 0,ESA=0;

CROSI:BC=LCM-2,ESA=2;

CROSI:BC=CO-1&-5&&-9&-12&&-15&-19&-21&-23&-25&-27&- 29&- 31&-32&-35&&-41&-44,ES=892;

CROSI:BC=CO-45&-47&-49&-50&-52&&-54&-57&-58&-60&-62&-64&&-67&-71&-77&-79&-82&&-84&-89&&-95,ES=892;




CROSI:BC=CO-2,ESA=5;



CROSI:BC=CO-11&-51,ESA=4;

CROSI:BC=CO-22&-68&&-70&-72&&-76,ESA=3;



CROPE:

Secondary Charging Analysis

Establish new ESA (8) for incoming CMRS traffic.

Secondary Charging Analysis Continued

CRSPI:ESA=8;

CRSSI:BC=CHT-0,CT=1,MBI=9;RAE=1;

CRSSI:BC=CHT-1,CT=NONE;

CRSSI:BC=CHT-2,CT=1&36,MBI=9;RAE=1&36;



CRSPE;

7.3.2. 4.3.2 TYPE 2A ORIGINATING (OGT to the MTSO) TRANSLATIONS

The TYPE 2A CMRS connection is an Access Tandem implementation which makes use of the tandem's terminatingFGD billing capability to produce AMA recordings for traffic received from the MTSO. This connection should allow onlythe completion of: intraLATA traffic to and from the MTSO including calls to Public Response Network Services, and;Interexchange Carrier (IC) traffic to the MTSO. Note that this connection is not used for completion of traffic from theMTSO to: Feature Group (FG) -B, -C, or -D IC services; exchange assistance operator, or; Directory Assistance. Addition-ally this connection is not used for completion of calls from the MTSO to 911, or 976 Services.

All state tariffs' require Land line originated traffic will be delivered to the MTSO via a dedicated NXX.




The Ericsson AXE is currently not deployed in SWBT as an Access Tandem for Type 2A cellular connections. Thereforeno Type 2A cellular connections should be provisioned.

7.3.3. 4.3.3 TYPE 2B ORIGINATING (OGT to the MTSO) TRANSLATIONS

The TYPE 2B interconnection may be used in conjunction with the TYPE 2A interconnection, and provides access for anCMRS at an end office. The TYPE 2B interconnection will only provide the CMRS with originating and terminating accessto directory numbers served by the end office to which it is connected. Calls to codes subtending the toll tandem portionof a combined Local/Toll switch will not be permitted via the TYPE 2B connection. The CMRS may choose to route anyoverflow traffic, originating in the end office, via the access tandem to which the CMRS has a 2A interconnection. Thiscan be either MF or SS7 signaling and generate a terminating

FGD 119 call code.

7.3.4. 4.3.4 TYPE 2B TERMINATING (INC from the MTSO)TRANSLATIONS

Translations for the incoming CMRS to EO calls require a unique B-Origin defined on the incoming trunk BT1/S7BTCtrunk group. This unique B-Table will allow calls to the EO NXX codes only, and will send all other calls to RC=212 (VacantCode). When a call from the CMRS customer is to a ported out NXX the Ericsson End Office will do an LNP query. Callsto DNs that have ported out of this switch will be allowed to complete.

To create the proper billing record on the Automatic Message Accounting (AMA) file a Carrier Code of 698 will be definedin the incoming trunk group using Route Data BT1/S7BTC parameter 'MB' for Primary InterLATA Carrier (PIC).

7.3.5. 4.3.5 TYPE 2B TWO WAY ( INC AND OGT from the MTSO)TRANSLATIONS

Translations for Type 2B Two Way combine the methods for Type 2B terminating with the Type 2B originating. The TYPE2B interconnection will only provide the CMRS with originating and terminating access to directory numbers served bythe end office to which it is connected. Calls to codes subtending the toll tandem portion of a combined Local/Toll switchwill not be permitted via the TYPE 2B connection. Translations for the incoming side (CMRS to EO) require a unique B-Origin defined on the incoming trunk BT1/S7BTC trunk group. This unique B-Table will allow calls to the EO NXX codesonly, and will send all other calls to RC=212 (Vacant Code). When a call from the CMRS customer is to a ported out NXXthe Ericsson End Office will do an LNP query. Calls to DNs that have ported out of this switch will be allowed to complete.

To create the proper billing record on the Automatic Message Accounting (AMA) file a Carrier Code of 698 will be definedin the incoming trunk group using Route Data BT1/S7BTC parameter 'MB' for Primary InterLATA Carrier (PIC).

7.3.5.1. 4.3.5.1 Translation Standards




Route/Charge Origins

65 - CMRS Type 2B (All States)

See Type 1 Section 1.4.1.4. Charge Analysis for Charge Origin 59 for Call Type 001 and MBI 009. Charging will be setupthe same way for CO=65 on Type 2B.

B-Number Origins

236-239 - CMRS Type 2B Start of Digit Analysis

259-262 - CMRS Type 2B Main Analysis

7.3.5.2. 4.3.5.2 AXE TYPE 2B MF SIGNALING

(example is 7-digit dial plan)

ANBSI:B=236-1010698, M=7, N=259, CC=0, CI=10-0698;

ANBSI:B=259-3706, AREA=314, D=1-0, NPA=2-314, TE, L=7;

EXROI:R=ECP5EI, TGN=1031, DETY=BT1, FNC=1;

EXRBC:R=ECP5EI, R1=LOCR, MB=1010698, RSV=257;

EXRBC:R=ECP5EI, LSV=0, MIS1=2, BO=236, CO=65, RO=65;

EXRBC:R=ECP5EI, TO=0, TDCL=0, DT=0, MIS4=0, MIS6=12488;

EXRBC:R=ECP5EI, LOD=0, IMS=0, DLP=0, LATA=<xxx>, MIS10=0;

EXRBC:R=ECP5EI, MIS11=0, MIS12=0;

7.3.5.3. 4.3.5.3 AXE TYPE 2B SS7 SIGNALING

ANBSI:B=54-3, N=49;

ANBSI:B=49-206980, M=6, N=110,CI=10-0698;

EXROI:R=S7LATMO&S7ECP5I, TGN=1032&1033, DETY=S7BTC, FNC=3,DPC=<dpc>




EXRBC:R=S7ECP5I, R1=TC, MB=0698, BO=54;

EXRBC:R=S7ECP5I, CO=65, RO=65, MIS2=65, MIS8=65, MIS9=65;

EXRBC:R=S7ECP5I, MIS3=1, MIS4=3850, MIS7=1, DLP=6;

7.4. 4.4 Size Alteration Event - Form 1405 Local:

SAE 760 - SSILH

Global:

SAE 32 - CRAC

7.5. 4.5 Automatic Message Accounting CMRS TYPE 1: Terminating Traffic Call Type 001, MBI 009 IntraLATA

Terminating Traffic Call Type 119 FGD InterLATA

CMRS TYPE 2B: Terminating Traffic Call Type 119 FGD InterLATA

7.6. 4.6 References Marketing Service Description - SS7 End Officne Connection, 06/12/98

Technical Service Description - Commerical Mobile rado Service, 12/01/98

8. Contact List

Name ATTUID Phone # Department / Responsibility

Mike Pharris mp4177 713-863-4000 Network




Revision Log

Issue Number Date Description Published By

2 04/26/10 Updated to change the titlefrom: Commercial MobileRadio Service; to: Commer-cial Mobile Radio Service -1A, DMS100, 5E, AXE - SW

jr9461

Acronyms

A.1. Document Specific Acronyms

A.2. Acronyms Dictionary Refer to ATT-000-000-020, Acronyms Dictionary.




http://apex.web.att.com/bookview/bookview.jsp?bookname=ATT-000-000-020&section=atdoctitle