Flexent /autoplex Wireless Networks Executive Cellular Processor (ECP) Release 22.0

Flexent/AUTOPLEX Wireless Networks Executive Cellular Processor (ECP) Release 22.
0 Automatic Message Accounting Formats Description Volume 2

Issue 27 May 2004 401-610-133
Lucent TechnologiesProprietary This document contains proprietary information of Lucent Technologies and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2004 Lucent Technologies Unpublished and Not for Publication All rights Reserved
This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of the material.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change.
Federal Communications Commission Statement (FCC) Notification and Repair Information
NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his/her own expense.
Security Statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such event, applicable tariffs require that the customer pay all network charges for traffic. Lucent Technologies cannot be responsible for such charges and will not make any allowance or give any credit for charges that result from unauthorized access.
Trademarks
3Com is a registered trademark of 3Com Corporation. 5ESS is a registered trademark of Lucent Technologies. AUTOPLEX is a registered trademark of Lucent Technologies. BILLDATS Data Manager is a registered trademark of Lucent Technologies. Ethernet is a registered trademark of XEROX Corporation. Flexent is a registered trademark of Lucent Technologies. Sun, Solaris, and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. All SPARC trademarks are licensed exclusively to Sun Microsystems, Inc. UNIX is a registered trademark, licensed exclusively through WatchMark Prospect for Lucent is a trademark of Watchmark Corporation. Other trademarks may appear in this document as well. They are marked on first usage.
Ordering Information
The ordering number for this information product is 401-610-133. To order this or other Lucent Technologies information products, see To obtain documentation, training, and technical support or submit feedback on the 401-010-001 Flexent/ AUTOPLEX Wireless Networks System Documentation CD-ROM or the documentation web site at
https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/.
Technical support
For technical support, see To obtain documentation, training, and technical support or submit feedback on the 401-610-010 Flexent/AUTOPLEX Wireless Networks System Documentation CD-ROM or documentation web site at
https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/.
Lucent TechnologiesProprietary See notice on first page
Contents
About This Document
lxvii lxvii lxvii lxviii lxviii lxviii lxviii lxx lxxi lxxi lxxi lxxii lxxii lxxiii lxxv lxxvi lxxvii lxxviii lxxix lxxx
Introduction Purpose Reason for Reissue Introduction AMA Enhancement of Home Zone Service for Phase 2 and KTF Intelligent Networking Support of KTF Wireless Number Portability Report Call Forwarding Due to No Reply in AMA Records Background Functionality IMSI In-bound Roaming for KTF Documentation Fixes for the Metered Billing Feature Append Specific AMA Modules to Structure Code x2351 Feature Obsolete Features Historical Record of Revisions Safety Labels Intended Audience Prerequisite Skills and Knowledge Conventions Used in This Document To Obtain Technical Support, Documentation, and Training or Submit Feedback
Dynamic Routing Feature

12-1 12-1 12-1 12-2 12-2 12-2 12-2 12-2 12-3
Introduction For Further Information Feature Description Introduction What is the Dynamic Routing Feature? How Does It Work? Benefits AMA Impact
Issue 27 May 2004
iii
401-610-133A
Contents
Changes in Field Definitions Carrier Prefix Origination Indicator Feature Interaction 12-3 12-3 12-3 12-4
Message Recording Service Feature

13-1 13-1 13-1 13-2 13-2 13-2 13-2 13-2 13-2 13-3 13-4 13-4 13-4 13-4 13-4 13-5 13-5 13-5 13-5 13-5 13-6 13-6 13-7 13-7 13-7 13-7 13-7 13-7 13-7 13-8 13-8 13-9 13-9
Introduction For Further Information Feature Description Introduction What is the MRS Feature? How Does It Work? Benefits For Further Information AMA Impact Message Recording with MRS Introduction Called-Party Elapsed Time Digital Called-Party Elapsed Time Message Recording Service Indicator Voice-Channel Seizure Time (Date) Voice-Channel Answer Time (Date) Voice-Channel Elapsed Time Digital Voice-Channel Elapsed Time Initial Radio/Channel Number and Cell Site Last Radio/Channel Number and Cell Site Number of Handoffs Message Retrieval with MRS Introduction Message Retrieval via the Message Retrieval Code Feature Call Answer Status Terminating Number Called-Party Elapsed Time Digital Called-Party Elapsed Time Message Recording Service Indicator Voice-Channel Answer Time (Date) Feature Interaction Conditional Call Forwarding
iv
Issue 27
May 2004
Contents
Call Waiting 13-9
Abbreviated Dialing with AMA Feature

14-1 14-1 14-1 14-2 14-2 14-2 14-2 14-3 14-3 14-3 14-3 14-3 14-4 14-4
Introduction For Further Information Feature Description Introduction What is the Abbreviated Dialing with AMA Feature? Benefit AMA Impact Introduction Call Type Service Feature Target Address Feature Interaction DDAMA and the ADWAMA Feature
Automatic Roamer Greeting Feature

15-1 15-1 15-1 15-2 15-2 15-2 15-2 15-2 15-3 15-3 15-4
Introduction For Further Information Feature Description Introduction What is the ARG Feature? How Does It Work? Benefits AMA Impact Changes in Field Definitions Feature Interaction
Analog/Digital Usage Billing Feature

16-1 16-1 16-1 16-2
Introduction For Further Information Feature Description
Issue 27
May 2004
401-610-133A
Contents
Introduction What is the ADUB Feature? How Does It Work? Benefits AMA Impact Introduction Storage of Type of Technology and Station Class Mark Field Definitions Auxiliary Time Module Fields Feature Interaction With DCCH Non-Public Network Identifiers Feature 16-2 16-2 16-2 16-2 16-3 16-3 16-3 16-3 16-4 16-4 16-6 16-6
AMA Containing Incoming Automatic Number Identification (AMANI) Feature

17-1 17-1 17-1 17-2 17-2 17-2 17-2 17-3 17-3 17-3 17-3 17-4 17-4 17-4 17-4 17-4 17-4
Introduction For Further Information Feature Description Introduction What is the ANI Feature? Benefits AMA Impact Introduction Use of CPN Incoming Calls Module-2 Change in Field Information for AMANI Feature Interactions Introduction With the Call Forwarding Feature With the Call Waiting Feature With Special Cellular Networking Calls With the CPNAD Capability
Calling Number Identification Presentation and Restriction Capability Feature 18-1
Introduction
18-1
vi
Issue 27
May 2004
Contents

For Further Information Feature Descriptions Introduction What is the CNIPR Capability? What Does the CPNAD Feature Do? What Does the CNIP Feature Do? What Does the CNIR Feature Do? AMA Impact Introduction CPN Incoming Calls Module-1 Module CPN Incoming Calls Module-2 Module CPN Outgoing Calls Module Module Generation Criteria for CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module Module Generation Criteria for CPN Outgoing Calls Module ecp Form Introduction Four Fields Generate CPN Outgoing Calls AMA Module Field Generate CPN Incoming Calls AMA Module Field DISPLAY ALLOWED/RESTRICTED CPN Fields Feature Interaction With AMANI Feature (for the CPNAD Feature) With Call Forwarding and Call Waiting
18-1 18-2 18-2 18-2 18-2 18-2 18-2 18-3 18-3 18-3 18-3 18-3
18-4 18-5 18-6 18-6 18-6 18-6 18-6 18-6 18-8 18-8 18-8
LSA Features

19-1 19-1 19-1 19-2 19-2 19-2 19-2 19-2 19-2 19-3 19-3 19-3
Introduction For Further Information Feature Description Introduction What is a Limited Service Area? What is the LSA Feature? What is the LSA128 Feature? Billing Levels Used with the LSA 128 Feature What is the Inter-DCS LSA Feature? What is the Inter-MSC LSA Feature? What is the Silent Administration of LSA (SALSA) Feature?
Issue 27
May 2004
vii
401-610-133A
Contents
AMA Impact for All LSA Features Introduction Aggregate LSA Information Module Generation Criteria for Aggregate LSA Information Module Special Case in Which LSA Modules Are Not Generated For Further Information AMA Impact on LSA in Cases of 3-Port Calls Introduction LSA Status Contents of LSAET Field Voice-Channel Usage Segment Value Digital Voice-Channel Usage Segment Value AMA Impact of the Limited Service Area (LSA) Feature Introduction Aggregate LSA Module AMA Impact for the IDLSA and IMLSA Features Introduction AMA Impact for the IDLSA Feature AMA Impact for the IMLSA Feature Handling of Elapsed Time Expansion of LSA Indicator Field AMA Impact for the LSA 128 Feature Introduction Activation Criteria Older LSA Billing Fields Have Not Changed Treatment of Elapsed Time Rules for Interacting with MSCs That Do Not Have the LSA128 Feature AMA Impact for the Silent Administration of LSA (SALSA) Feature Introduction Special Feature Activation/Deactivation Record Feature Interactions
19-4 19-4 19-4 19-4 19-4 19-4 19-5 19-5 19-5 19-5 19-5 19-6 19-7 19-7 19-7 19-8 19-8 19-8 19-8 19-8 19-8 19-10 19-10 19-10 19-10 19-10 19-10 19-11 19-11 19-11 19-12
Voice Privacy Feature

20-1 20-1 20-1 20-2
viii
Issue 27
May 2004
Contents
Introduction What is the Voice Privacy Feature? Voice Privacy Capability for Service Providers AMA Impact Introduction Type of Technology Field 20-2 20-2 20-2 20-3 20-3 20-3
10
Initial Cell-Based Billing Feature

21-1 21-1 21-1 21-2 21-2 21-2 21-3 21-3 21-3 21-3 21-3 21-4
Introduction For Further Information Feature Description Introduction What is the Initial Cell-Based Billing Feature? AMA Impact Introduction Fields Module Generation Criteria For Further Information Feature Interactions
11
Private Numbering Plan (PNP) Non-Dialable Digits in HLR Return Results Feature 22-1

Introduction For Further Information Feature Description Introduction What is the PNP Non-Dialable Digits in HLR Return Results Feature? How Does It Work? Benefits About the Digit Information Module (Module 621) Introduction Generic Context Identifier for This Feature Digits String Field Module Generation Criteria for This Feature For Further Information
22-1 22-1 22-2 22-2 22-2 22-2 22-2 22-3 22-3 22-3 22-3 22-3 22-3
Issue 27
May 2004
ix
401-610-133A
Contents
Feature Interactions
22-4
12
Multiple Voice Coding Feature

23-1 23-1 23-1 23-2 23-2 23-2 23-2 23-2 23-3 23-3 23-4 23-4 23-4 23-4 23-4 23-4 23-4 23-5 23-6 23-6
Introduction For Further Information Feature Description Introduction What is the MVC Feature? Benefits MVC Capabilities for the Service Provider Multiple Types of Vocoder Supported Vocoding Algorithms Supported AMA Impact Introduction Fields Module Code Field Event Type Field Event Description Field Relative Event Time Field Module Activation Criteria Feature Interactions With the Data Module
13
User Zone Capability

24-1 24-1 24-2
Introduction For Further Information For Information about the DCCH Non-Public Network Identifiers and Non-Public Network Identifiers-Analog Features For Information About the CDMA Private Network and User Zone Feature About User Zones Introduction What is a Non-Public Network? Identifiers for the Non-Public Networks What is a User Zone?
24-2 24-2 24-3 24-3 24-3 24-3 24-3
Issue 27
May 2004
Contents
Benefits of User Zones Feature Descriptions Introduction For Information about the DCCH Non-Public Network Identifiers and Non-Public Network Identifiers-Analog Features For Information About the CDMA Private Network and User Zone Feature AMA Impact Activation/Deactivation of User Zone Tone TDMA and Analog Implementation of the User Zone Module Introduction Fields Module Code Field User Zone Information Field User Zone Sequence Number User Zone ID Type User Zone ID User Zone Elapsed Time Field Module Generation Criteria For Further Information User Zone Module Generation Rules for TDMA and Analog Introduction Charge Recording Data and the User Zone Module Call that Starts and Registers on the Public System Call that Starts on the Public System after Registration in a User Zone Call that Starts in a User Zone and Moves to a Public System Call that Starts in a User Zone and Moves to Another User Zone CDMA Implementation of the User Zone Module Introduction Public System As a User Zone Fields Module Code Field User Zone Information Field User Zone Sequence Number User Zone ID Type User Zone ID User Zone Elapsed Time Field 24-3 24-5 24-5
24-5 24-5 24-6 24-6 24-7 24-7 24-7 24-7 24-7 24-7 24-8 24-8 24-8 24-8 24-9 24-10 24-10 24-10 24-10 24-10 24-11 24-11 24-12 24-12 24-12 24-12 24-12 24-12 24-13 24-13 24-13 24-13
Issue 27
May 2004
xi
401-610-133A
Contents
Module Generation Criteria For Further Information User Zone Module Generation Rules for CDMA Introduction Charge Recording and the User Zone Module Call That Starts and Ends in One User Zone Call that Moves into Other User Zones Call that Continues Past Four Handoffs Feature Interactions For all Features (To Get the Auxiliary Time Module) For Other Feature Interactions
24-14 24-14 24-15 24-15 24-15 24-15 24-15 24-15 24-16 24-16 24-16
14
CDMA Circuit-Mode Data Services Feature

25-1 25-1 25-1 25-2 25-2 25-2 25-2 25-2 25-3 25-3 25-3 25-3 25-3 25-4 25-4 25-5 25-5 25-5 25-5 25-6 25-7 25-7 25-7 25-8 25-9 25-9
Introduction For Further Information Feature Description Introduction What is the CDMA Circuit-Mode Data Service Feature? Use with the Analog Fax Support for CDMA Feature Scope How It Works Introduction Components Reason for the Inter-Working Function (IWF) Definition of the IWF Two Data Paths How the Legs Are Set Up PDP Leg Can Also Activate/Deactivate Features Special Case in Which There is No PDP Leg Setup Scenario for the MDP and the PDP Tracking AMA Activity Exception ADSS and the Circuit-Mode Data Service Feature No Record for the PDP Leg Explanation AMA Impacts New Call Types Records For Which These Call Types Do Not Apply
xii
Issue 27
May 2004
Contents

Records for Which These Call Types Sometimes Apply Call Types Mobile-Originated Circuit Data Call Introduction Purpose Definition Applicable Structure Codes Structure Codes for the MDP Leg Structure Codes for the PDP Leg Mobile-Terminated Circuit Data Call Introduction Purpose Definition Applicable Structure Codes Intra-Switch Terminated Data Call: Only One Record Intra-Switch Terminated Data Call: Structure Codes For Inter-Switch Terminated Data Call: Two or More Records Inter-Switch Terminated Data Call: Structure Codes For Re-routing of Incoming CDMA Circuit-Mode Data Service Calls Data Module Introduction Purpose of the Data Module Data Module Definition Module Code Field Event Type Field Event Description Field Linking Code Field Data Module and the Digital Event Module Data Module Generation Criteria For Further Information AMA Records for CDMA Circuit-Mode Data Service Calls Introduction Mobile Origination Introduction AMA Record for MDP Leg Exceptions: Rationale for Exceptions for a Standard MDP Leg Call AMA Record for PDP Leg Exceptions for a Standard MDP Leg Call Record for PDP Leg with Feature Activation/Deactivation
25-9 25-10 25-11 25-11 25-11 25-11 25-11 25-11 25-11 25-12 25-12 25-12 25-12 25-12 25-12 25-12 25-13 25-13 25-13 25-14 25-14 25-14 25-14 25-14 25-14 25-14 25-15 25-15 25-15 25-16 25-17 25-17 25-18 25-18 25-18 25-18 25-18 25-19 25-20 25-20
Issue 27
May 2004
xiii
401-610-133A
Contents
Exceptions Mobile Termination Introduction AMA Record for Mobile-Terminated Call Exceptions
25-21 25-22 25-22 25-22 25-22
15
Virtual Systems AMA Event Recording Feature

26-1 26-1 26-1 26-2 26-2 26-2 26-2 26-2 26-3 26-3 26-3 26-3 26-3
Introduction For Further Information Feature Description What is the Virtual System AMA Event Recording (VSAMAER) Feature? How Does it Work? Benefits Values for Voice-Channel Elapsed Time AMA Impact Introduction VSHE Record Linking VSHE Records to AMA Records Contents of a VSHE Record
16
Metered Billing Feature

27-1 27-1 27-1 27-2 27-2 27-2 27-2 27-2 27-2 27-3 27-3 27-3 27-3 27-3
Introduction For Further Information Feature Description Introduction What is the Metered Billing Feature? How It Works Three Records Contents of the New Records Event Type Field Linking MBAER Records to AMA Call Records Calls That Will Not Generate MBAERs Cases Where a Major Failure Occurs Limitations
xiv
Issue 27
May 2004
Contents
Record Generation Criteria Introduction For a Mobile Origination Call For a Mobile Termination Call For the End Of the Call Metered Billing Structure Codes Feature Interactions
27-4 27-4 27-4 27-4 27-5 27-6 27-9
17
AMA Enhancements Feature

28-1 28-1 28-1 28-2 28-2 28-2 28-2 28-2 28-4 28-4 28-4 28-4 28-5 28-5 28-5 28-5 28-5 28-5 28-6 28-7 28-7 28-7 28-7 28-7 28-7 28-8 28-8 28-8 28-8 28-8
Introduction For Further Information Feature Description Background Need for AMA Enhancements Feature Need for Modification to Existing Billing Systems Phase I: Three New Modules AMA Impact Introduction Module Definitions Module Generation Criteria Radio Information Module Introduction Definition Availability Generation Criteria Results For Further Information Trunk Information Module Introduction Definition Generation Criteria Additional Disk Space Needed For Further Information Switch Identification Module Introduction Definition Generation Criteria Results
Issue 27
May 2004
xv
401-610-133A
Contents
For Further Information 28-9
18
Wireline Feature Transparency Feature

29-1 29-1 29-1 29-2 29-2 29-2 29-2 29-2 29-3 29-3 29-4 29-4 29-4 29-4 29-5 29-5
Introduction For Further Information Feature Description Introduction What is the Wireline Feature Transparency Feature? How Does It Work? Example of Call Forwarding Without Wireline Feature Transparency Example of Call Forwarding With Wireline Feature Transparency Benefits AMA Impact Introduction Change in Billing for the Voice Channel Bits in Timing Indicator Set Feature Interaction With Call Forwarding Feature
19
AMA Antenna Face Information for TDMA and Analog Feature

30-1 30-1 30-1 30-2 30-2 30-2 30-2 30-3 30-3 30-3
Introduction For Further Information Feature Description Introduction What is the AMA Antenna Face Information for TDMA and Analog Feature? Benefits AMA Impact Information Stored For TDMA and Analog
xvi
Issue 27
May 2004
Contents
20 No Charge Calls in AMA Record Feature

31-1 31-1 31-1 31-2 31-2 31-2 31-3 31-3 31-4
Introduction For Further Information Feature Description What is the No Charge Calls in AMA Record Feature? Benefits AMA Impact New Call Type Feature Interactions
21
Calling Name Presentation and Restriction Feature

32-1 32-1 32-1 32-2 32-2 32-2 32-2 32-3 32-4 32-4 32-4 32-4 32-4 32-5 32-5
Introduction For Further Information Feature Description Introduction What is the CNAP Feature? What is the CNAR Feature? Types of Name Control AMA Impact Introduction Calling Name Incoming Calls Module Calling Name Outgoing Calls Module Module Generation Criteria for the Calling Name Incoming Calls Module Module Generation Criteria for the Calling Name Outgoing Call Module For More About the Modules
22
MIN-MDN Separation Feature

33-1 33-1 33-1 33-2 33-2 33-2
Introduction For Further Information Feature Description Introduction What is the MIN-MDN Separation Feature?
Issue 27
May 2004
xvii
401-610-133A
Contents
Benefits AMA Impact Introduction Summary of Changes MIN In the Billing Number Field Introduction Where Billing Number is Zero Database Description for Field Does Not Work if Billing Number is Populated Subscriber Number can be Reset to ANI or MIN Introduction Where VLR is Not Received ANI MIN Database Description for Field Does Not Work if VLR is Present MIN Can be Stored in a DIM Module Introduction Need for MIN Database Description for the Field Generic Context Identifier for This Feature Digits String Field Module Generation Criteria for This Feature Result Note For Further Information IMSI Can be Stored in a DIM Module Introduction Need for IMSI Database Description for the Field Generic Context Identifier for This Feature Digits String Field Module Generation Criteria for This Feature Result Note For More Information Feature Interactions
33-2 33-3 33-3 33-3 33-4 33-4 33-4 33-4 33-4 33-5 33-5 33-5 33-5 33-5 33-5 33-6 33-7 33-7 33-7 33-7 33-7 33-7 33-7 33-8 33-8 33-8 33-9 33-9 33-9 33-9 33-9 33-9 33-9 33-10 33-10 33-10 33-11
xviii
Issue 27
May 2004
Contents
23 CDMA Packet-Mode Data Services Features

34-1 34-1 34-1 34-2 34-2 34-2 34-2 34-2 34-3 34-3 34-4 34-4 34-5 34-6 34-6 34-6 34-6 34-6 34-6 34-7 34-8 34-8 34-8 34-8 34-8 34-10 34-10 34-10 34-10 34-10 34-11 34-11 34-11 34-12 34-12
Introduction For Further Information About the CDMA Packet Mode Data Services Family of Features Introduction What is a CDMA Packet-Mode Data Services Feature? What Benefit Do These Features Provide for Service Providers? What Benefits Do These Features Give the Subscriber? Scope Limitation AMA Impact Introduction Call Types Event Types Introduction What Is an Event Type? What is an AMA Event? Event Types for CDMA Packet Mode Data Services Features Event Type 010 Event Type 011 Event Descriptions Introduction What is an Event Description? CDMA Packet Mode Data Services Event Descriptions Differentiating Features by Use of Event Description Appended Module Introduction About the Data Module About the Digital Event Module Precedence Suppressing Data Collection Records Suppressing Duplicate CDPD Records Suppressing Duplicate IP Records Feature Interactions Introduction
Issue 27
May 2004
xix
401-610-133A
Contents
24 AMA Calling Party Category Information Feature

35-1 35-1 35-1 35-2 35-2 35-2 35-2 35-2 35-2 35-3
Introduction For Further Information Feature Description Introduction What is the AMA Calling Party Category Information Feature? How Does It Work? Layout of Field Limitations Feature Interactions
25
Wireless Number Portability Feature

36-1 36-1 36-1 36-2 36-2 36-2 36-2 36-2 36-2 36-3 36-3 36-3 36-4 36-6 36-6 36-6 36-6 36-7 36-7 36-8 36-8 36-9 36-9 36-9
Introduction For Further Information Feature Description Introduction What is the WNP Feature? Scope Other Types of Portability Not Covered in Wireless Number Portability Background Introduction Need for the Feature Glossary of WNP Terms How It Works Introduction NP-SCP Database Call Setup (by the Originating Switch) Call Setup (by the Recipient Switch) Tandem MSC AMA Impact Introduction Wireless Number Portability Module Introduction Purpose of the Wireless Number Portability Module
xx
Issue 27
May 2004
Contents
Wireless Number Portability Module Definition Module Generation Criteria for Wireless Number Portability Feature Four Possible Request Response Results No Query Failure Time-Out Conditions Return Error Message No Query Performed For Further Information Digit Information Module with JIP Information Introduction Purpose of the Digit Information Module Jurisdiction Indicator Parameter Generic Context Identifier for JIP Value of JIP Module Generation Criteria for Wireless Number Portability Feature For Further Information Feature Interaction Dependency For Further Information 36-9 36-9 36-10 36-10 36-10 36-10 36-11 36-11 36-12 36-12 36-12 36-12 36-12 36-12 36-12 36-13 36-14 36-14 36-14
26
Flexible Alerting Feature
37-1 37-1 37-1 37-1 37-1 37-3 37-3 37-3 37-4 37-4 37-4 37-4 37-4 37-5 37-5 37-5
Introduction Supported Technologies About FAFs for Flexible Alerting For Further Information Feature Description Introduction Need for the Feature What is the Flexible Alerting Feature? Pilot DN Other DNs About Flexible Alerting Groups Subscriber Assignment Feature Benefits for the Service Provider Feature Benefits for the Subscriber For Further Information
Issue 27
May 2004
xxi
401-610-133A
Contents
AMA Impact 37-6 Introduction 37-6 Control of AMA Record Generation for Unanswered Call Legs37-6 Control of AMA Modules for Flexible Alerting 37-6 Subscriber-Controlled Change in Activation Status 37-6 Changes in Billing of AMA Records for Flexible Alerting 37-7 Two New Generic Context Identifiers 37-7 Digit Information Module 37-8 Introduction 37-8 Purpose of the Digit Information Module 37-8 Two Generic Context Identifiers 37-8 Module Generation Criteria for DIM Storing the Pilot DN 37-8 Module Generation Criteria for DIM Storing the FA Leg DN 37-8 For Further Information 37-9 BIN Module 37-10 Introduction 37-10 Purpose of the BIN Module 37-10 BIN Module Generation Criteria 37-10 For Further Information 37-11 Feature Interactions 37-12 With the Special Routing Feature 37-12 With the Increased Court-Ordered Surveillance (ICOS) Feature 37-12
27
ANSI-41 Billing Module and ANSI-41 Billing Module with Service 38-1 Type Features

Introduction For Further Information Feature Description for ANSI-41 Billing Module Feature Introduction What is the ANSI-41 Billing Module Feature? About the DMH Need for the Feature Benefit Feature Description for ANSI-41 Billing Module with Service Type Feature Introduction What is the ANSI-41 Billing Module with
38-1 38-1 38-2 38-2 38-2 38-2 38-2 38-3 38-4 38-4
xxii
Issue 27
May 2004
Contents
Service Type Feature? Service ID versus Service Type About the DMH Need for the Feature AMA Impact AMA Impact of the ANSI-41 Billing Module Feature AMA Impact of the ANSI-41 Billing Module with Service Type Feature Digit Information Module Introduction Purpose of the Digit Information Module New Generic Context Identifiers Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Account Code Digits Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Alternate Billing Digits Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Billing Digits Module Generation Criteria for the ANSI-41 Billing Module Feature for the Digit Information Module Storing ANSI-41 DMH Redirection Indicator Module Generation Criteria for DIM Storing Service ID For Further Information Feature Dependencies Feature Interactions 38-4 38-4 38-4 38-4 38-5 38-5 38-5 38-6 38-6 38-6 38-6
38-7
38-7 38-7
38-8 38-8 38-8 38-9 38-10
28
CDMA Full IMSI Feature

39-1 39-1 39-1 39-2 39-2 39-2 39-2 39-2 39-2 39-3 39-4
Introduction For Further Information Feature Description Introduction What is IMSI? Need for the IMSI Benefit of IMSI MIN-Based IMSI What is the CDMA Full IMSI Feature? AMA Impact
Issue 27
May 2004
xxiii
401-610-133A
Contents
Introduction About the Digit Information Module Introduction Generic Context Identifier for This Feature Module Generation Criteria for This Feature AMA Records for Different Types of IMSI Two Modules May Be Attached to One Call Record For Further Information
39-4 39-5 39-5 39-5 39-5 39-5 39-6 39-6
29
TDMA Circuit-Mode Data Services Feature

40-1 40-1 40-1 40-2 40-2 40-2 40-2 40-3 40-3 40-3 40-3 40-3 40-4 40-4 40-5 40-5 40-5 40-5 40-6 40-7 40-7 40-7 40-7 40-8 40-8 40-8 40-8 40-8
Introduction For Further Information Feature Description Introduction What is the TDMA Circuit-Mode Data Services Feature? Scope How It Works Introduction Components Reason for the Inter-Working Function (IWF) Definition of the IWF Two Data Paths How the Legs Are Set Up During Call Origination PDP Leg Can Also Activate/Deactivate Features Special Case in Which There is No PDP Leg Setup Scenario for the MDP and the PDP During an Incoming Call Tracking AMA Activity AMA Impact Call Types New Call Types Records For Which These Call Types Do Not Apply Records for Which These Call Types Sometimes Apply Mobile-Originated Circuit Data Call Introduction Purpose Definition Applicable Structure Codes
xxiv
Issue 27
May 2004
Contents
Structure Codes for the MDP Leg Structure Codes for the PDP Leg Mobile-Terminated Circuit Data Call Introduction Purpose Definition Applicable Structure Codes Intra-Switch Terminated Data Call: Only One Record Intra-Switch Terminated Data Call: Structure Codes For Inter-Switch Terminated Data Call: Two or More Records Inter-Switch Terminated Data Call: Structure Codes For Re-routing of Incoming TDMA Circuit-Mode Data Services Calls Data Module Purpose of the Data Module Data Module Definition Module Code Field Event Type Field Event Description Field AMASE Table Linking Code Defined Linking Code for Mobile-Originating Calls Linking Code for Mobile-Terminating Calls Data Module Generation Criteria For Further Information AMA Records for TDMA Circuit-Mode Data Services Calls Introduction Mobile Origination Introduction AMA Record for MDP Leg Exceptions: Rationale for Exceptions for a Standard MDP Leg Call AMA Record for PDP Leg Exceptions for a Standard PDP Leg Call Record for PDP Leg with Feature Activation/Deactivation Exceptions Mobile Termination Introduction AMA Record for Mobile-Terminated Call Exceptions
40-8 40-8 40-9 40-9 40-9 40-9 40-9 40-9 40-9 40-10 40-10 40-10 40-11 40-11 40-11 40-11 40-11 40-11 40-12 40-12 40-12 40-12 40-12 40-13 40-14 40-14 40-15 40-15 40-15 40-15 40-15 40-17 40-17 40-18 40-18 40-20 40-20 40-20 40-20
Issue 27
May 2004
xxv
401-610-133A
Contents
Feature Dependencies Hardware Requirements Feature Interactions
40-21 40-21 40-21
30
TSI Bridging Feature

41-1 41-1 41-1 41-2 41-2 41-2 41-2 41-2 41-2 41-3 41-4 41-4 41-4 41-4 41-4 41-5 41-6 41-6 41-6 41-6 41-6 41-6 41-7 41-8
Introduction For Further Information Feature Description Introduction What is the TSI Bridging Feature? Previous Method of Court-Ordered Surveillance Mandate for a New Way of Monitoring Additional Benefits About the LAES Feature How It Works Introduction What is the Time Slot Bridge? TSI Bridging Creates a Copy of the Call LAES Feature Implementation Figure AMA Impact Introduction Use of Existing Trunk Information Module New Value for Trunk Direction, Trunk Type, and Release Cause Field Module Generation Criteria for TSI Bridging Feature Table For More About the Trunk Information Module Feature Dependencies
31
LAES Feature

42-1 42-1 42-1 42-2 42-2
Introduction For Further Information Feature Description What is the LAES Feature?
xxvi
Issue 27
May 2004
Contents
Previous Method of Court-Ordered Surveillance Mandate for a New Way of Monitoring Additional Benefits For More Information About the TSI Bridging Feature For More Information About the LAES Project AMA Impact Introduction Use of Existing Trunk Information Module Table Module Code Field Trunk Identification Field Trunk/Facilities Seizure Date Field Trunk/Facilities Seizure Time Field Trunk Elapsed Time Field Trunk Direction Field Trunk Type Field Release Cause Field Module Generation Criteria for LAES Feature Feature Dependencies 42-2 42-2 42-2 42-3 42-3 42-4 42-4 42-4 42-4 42-4 42-4 42-4 42-5 42-5 42-5 42-5 42-5 42-5 42-6
32
TDMA IMSI Feature

43-1 43-1 43-1 43-2 43-2 43-2 43-2 43-2 43-3 43-3 43-4 43-4 43-5 43-5 43-5 43-5 43-5 43-6
Introduction For Further Information Feature Description What is IMSI? IMSI Compared to the MIN and the DN Need for the IMSI Benefit of IMSI What is the TDMA IMSI Feature? Independence from the CDMA IMSI Feature AMA Impact Introduction About the Digit Information Module Introduction Generic Context Identifier for This Feature Module Generation Criteria for This Feature For Further Information Feature Interactions
Issue 27
May 2004
xxvii
401-610-133A
Contents
33 IP Billing Feature

44-1 44-1 44-1 44-2 44-3 44-3 44-3 44-3 44-3 44-3 44-4 44-4 44-4 44-4 44-4 44-5 44-5 44-6 44-6 44-7
Introduction Feature Dependency For Further Information Feature Description What is the IP Billing Feature? How It Works Storage of DIA Number in Call Record Benefit of the IP Billing Feature For Further Information AMA Impact Introduction New Service Code What is a TDMA DIA Call? Potential Places for Storing the DIA Table Storage in the DIM for TDMA DIA Storage in the DIM for DDAMA Storage in the Terminating Number Field Feature Dependencies
34
CDMA Circuit IP Services Feature

45-1 45-1 45-1 45-2 45-3 45-3 45-3 45-3 45-3 45-4 45-5 45-5 45-5 45-5 45-5
Introduction Feature Dependency For Further Information Feature Description What is the CDMA Circuit IP Services Feature? How It Works Benefit of the CDMA Circuit IP Services Feature New CDMA Circuit IP Services Indicator Storage of the Dialed Numeric Digits From the IWF AMA Impact Introduction Use of Existing DDAMA Feature Use of Existing Digit Information Module Call Disposition Indicator
xxviii
Issue 27
May 2004
Contents
The DDAMA Feature: How It Works Introduction How It Works In What Cases is the DIM Used? When is the Terminating Number Field Used? Table More About the DIM Module For Further Information The DDAMA Feature as Used by the CDMA Circuit IP Services Feature Introduction How It Works About the Digit Information Module as Used by the DDAMA and CDMA Circuit IP Services Features Introduction Generic Context Identifier for the DDAMA Feature For Further Information
45-6 45-6 45-6 45-6 45-6 45-7 45-7 45-7 45-8 45-8 45-8 45-9 45-9 45-9 45-9
35
Primary Rate Interface Feature

46-1 46-1 46-1 46-2 46-2 46-2 46-2 46-2 46-2 46-3 46-4 46-4 46-4 46-4 46-4 46-5 46-5 46-5 46-6
Introduction For Further Information Capability Description Introduction What is the PRI Capability? Terminology What AMA Information is Stored for PRI? How Does It Work? Limitations AMA Impact Signalling Type for PRI/PRA Five Locations Calling Party Category Field Trunk Network Number Field Incoming Tandem TNN Field Outgoing Tandem TNN Field Trunk Information Module Note About CPN Modules
Issue 27
May 2004
xxix
401-610-133A
Contents
36 Seven Digit AMA Block Sequence Number

47-1 47-1 47-1 47-2 47-2 47-2 47-2 47-2 47-3 47-3 47-3 47-3 47-3 47-4 47-4 47-4 47-4 47-4 47-4 47-5
Introduction For Further Information Feature Description Introduction Background How Many Block Sequence Numbers Are Needed? Why is This Feature Needed? How Does the Feature Work? Why is This an Optional Feature? Software Changes Required New Hardware Required CAUTION! AMA Impact Introduction AMA Block Sequence Number Increased No Change in Field Size Fields Tools Updated Feature Interaction
37
IS-826 Prepaid Base Feature

48-1 48-1 48-1 48-2 48-2 48-2 48-2 48-3 48-3 48-3 48-3 48-3 48-3
Introduction For Further Information Feature Description Introduction What is Prepaid Charging? How Does Prepaid Charging Work? AMA Impact Introduction Generic Context ID Use of Existing Digit Information Module Module Generation Criteria for IS-826 Prepaid Base Feature WIN Standard DMH Service ID Stored in Digits Recorded Field
xxx
Issue 27
May 2004
Contents
Contents of WIN Standard DMH Service ID Table Multiple WIN Standard DMH Service IDs Feature Interaction 48-4 48-4 48-4 48-5
38
Speech Handler Trunk Information in AMA Feature

49-1 49-1 49-1 49-2 49-2 49-2 49-3 49-3 49-3 49-3 49-3 49-3 49-4 49-5
Introduction Availability Feature Description Introduction Feature Description AMA Impact Introduction Generic Context ID Use of Existing Digit Information Module Module Generation Criteria Contents of Digits Recorded Field Table Feature Interaction
39
Specific Digit String Trigger Features

50-1 50-1 50-1 50-2 50-2 50-2 50-2 50-2 50-2 50-3 50-3 50-3 50-3
Introduction For Further Information Feature Descriptions Introduction What is the Specific Called Party Digit String Trigger Feature? What is the IS-826 Locally-Allowed Specific Digit String Trigger Feature? Warning Accessing Information for These Features AMA Impact for the Specific Called Party Digit String Trigger Feature Introduction Generic Context IDs Use of Existing Digit Information Module
Issue 27
May 2004
xxxi
401-610-133A
Contents
Module Generation Criteria IS-848 Billing Indicator in Digits Recorded Field IS-848 Charge Information in Digits Recorded Field AMA Impact for the IS-826 Locally-Allowed Specific Digit String Trigger Feature Introduction Generic Context IDs Use of Existing Digit Information Module Module Generation Criteria IS-848 Charge Information in the Digits Recorded Field Feature Dependencies Feature Interactions 50-3 50-4 50-4 50-5 50-5 50-5 50-5 50-5 50-5 50-7 50-8
40
TDMA Channel Usage Tracking Tool Feature

51-1 51-1 51-1 51-2 51-2 51-2 51-2 51-2 51-2 51-2 51-3 51-3 51-4 51-4 51-4 51-5 51-5 51-5 51-5 51-6 51-6 51-7 51-7 51-8
Introduction For Further Information Feature Description Introduction Feature Definition How Does It Work? What Information is Recorded? How is the Information Stored? Benefits Increased Disk Usage For Further Information AMA Impact Overview New Structures Channel Usage Module Introduction Channel Usage Module - Description Module Generation Criteria for the Channel Usage Module New AMASE Table Table Related AMA Tool Tool Updated Feature Interaction
xxxii
Issue 27
May 2004
Contents
41 Far End Release Cause Values in AMA Records
52-1 52-1 52-1 52-2 52-2 52-2 52-2 52-2 52-3 52-3 52-3 52-3 52-3 52-3 52-3 52-4 52-4 52-4 52-5 52-6 52-7
Introduction For Further Information Feature Description Introduction What is the FERCV Feature? What is the Enhanced FERCV Feature? Benefits AMA Impacts Introduction Generic Context ID for FERCV Generic Context ID for Enhanced FERCV Use of Existing Digit Information Module Module Generation Criteria for FERCV Module Generation Criteria for Enhanced FERCV Digits Recorded Field for FERCV Table Digits Recorded Field for Enhanced FERCV Table Feature Dependencies Feature Interactions
42
Customized ESN Format in AMA Record
53-1 53-1 53-1 53-2 53-2 53-2 53-2 53-3 53-3 53-3 53-3 53-4 53-5 53-6
Introduction For Further Information Feature Description Introduction Feature Definition What is 2-step Decimal Format? AMA Impacts Introduction New Service Feature Code Related Structure Code Layouts New Treatment of Mobile Serial Number Feature Dependencies Feature Interactions
Issue 27
May 2004
xxxiii
401-610-133A
Contents
Related Documentation
53-7
43
Selectable Mode Vocoder on PHV
54-1 54-1 54-1 54-2 54-2 54-2 54-2 54-3 54-3 54-4 54-4 54-4 54-4 54-4 54-4 54-4 54-5 54-6 54-6 54-6 54-6 54-6 54-6 54-7 54-7 54-8 54-9 54-10
Introduction For Further Information Feature Description Introduction What is the SMV on PHV Feature? Additional Storage Required AMA Impacts Introduction Digital Event Module Introduction Fields Module Code Field Event Type Field Event Description Field Relative Event Time Field Module Generation Criteria Digit Information Module Introduction Fields Module Code Field Module Size Field Generic Context Identifier Digits Recorded Field for SMV on PHV Table Module Generation Criteria for SMV on PHV Feature Dependencies Feature Interactions
44
Limited Mobility Services with Multiple SDCAs/MDNs
55-1 55-1 55-1 55-2
xxxiv
Issue 27
May 2004
Contents
What the Feature does AMA Impacts New Service Feature Code Subscriber DN Home Mobile DN Incoming Called Digits for the Mobile-Terminated Call Feature Dependencies
55-2 55-3 55-3 55-3 55-3 55-3 55-5
45
Maintain Selected AMA Measurement Data Reporting
56-1 56-1 56-1 56-2 56-2 56-2 56-3 56-3 56-3 56-4 56-5
Introduction For Further Information Feature Description What the Feature does How the Feature Works AMA Impacts New Generic Context ID Digits Recorded field for Generic Context ID 90062 Module Generation Criteria for Maintain Selected AMA Measurement Data Reporting Feature Feature Interactions
46
AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service Feature57-1
Introduction For Further Information Feature Description Introduction Feature Description AMA Impact Introduction Use of Existing Digit Information Module with a New Generic Context ID Module Generation Criteria Table Feature Interaction Home Zone Service Phase 2
57-1 57-1 57-2 57-2 57-2 57-3 57-3 57-3 57-3 57-4 57-6 57-6
Issue 27
May 2004
xxxv
401-610-133A
Contents
KTF Intelligent Network Service (KTFINS) 57-6
Call Scenarios
Introduction Location of DCSs Ratio of AMA Records to DCSs Timing Tables Call Scenarios and Structure Codes Structure Code Starting with 4 AMA Record Generation Call Scenario Use of AMA Records Call Scenario Composition Mobile Origination How It Starts What Happens Figure Mobile Origination (not Home DCS) How It Starts What Happens Figure Mobile Origination with Internal DCS Handoff How It Starts What Happens Figure Mobile Origination with Handoff How It Starts What Happens Figures Mobile Origination with Handoff and Handback How It Starts What Happens Figures Mobile Termination How It Starts What Happens Figure Mobile Termination (not Home DCS) How It Starts
A-1 A-1 A-1 A-1 A-2 A-2 A-4 A-8 A-12 A-15 A-15 A-15 A-15 A-16 A-16 A-16 A-16 A-17 A-17 A-17 A-17 A-18 A-18 A-18 A-18 A-20 A-20 A-20 A-21 A-23 A-23 A-23 A-23 A-24 A-24
xxxvi
Issue 27
May 2004
Contents
What Happens Figures Mobile Termination (No Page Response) How It Starts What Happens Figure Mobile Termination (Failed) How It Starts What Happens Figure Mobile Termination (Unanswered) How It Starts What Happens Figure Mobile Termination Overflow How It Starts What Happens Figure Mobile Termination with Handoff How It Starts What Happens Figures Mobile Termination with Handback How It Starts What Happens Figures Mobile Termination with Handoff and Handback How It Starts What Happens Figures Mobile Termination with Handoff to 2, 3, and 2 How It Starts What Happens Figures Mobile to Mobile How It Starts What Happens Figure Mobile to Mobile with Tandem How It Starts
A-24 A-24 A-26 A-26 A-26 A-26 A-27 A-27 A-27 A-27 A-28 A-28 A-28 A-28 A-29 A-29 A-29 A-29 A-30 A-30 A-30 A-30 A-32 A-32 A-32 A-32 A-34 A-34 A-34 A-34 A-37 A-37 A-37 A-37 A-40 A-40 A-40 A-40 A-41 A-41
Issue 27
May 2004
xxxvii
401-610-133A
Contents
What Happens Figure Call Delivery (via Internal Trunks) How It Starts What Happens Figure Call Delivery (via ANSI-41) How It Starts What Happens Figure Call Delivery (Internal) with Handoff How It Starts What Happens Figure Call Delivery (ANSI-41) with Handoff How It Starts What Happens Figures Call Delivery to Call Waiting How It Starts What Happens Figures Call Forwarding to Mobile How It Starts What Happens Figure Call Waiting (No Answer Forward to PSTN) How It Starts What Happens Figures Call Waiting (No Answer Transfer to Voice Mail) How It Starts What Happens Figures Mobile Termination with Call Waiting How It Starts What Happens Figures Mobile Origination with Call Waiting How It Starts
xxxviii
Issue 27
May 2004
Contents
What Happens Figures Mobile Origination with Three-Way Calling How It Starts What Happens Figure Three-Way Calling with Handoff How It Starts What Happens Figure Call Transfer from a Mobile-Originated Call What Happens How it Works Call Transfer from a Mobile-Terminated Call What Happens How it Works Voice-Mail Retrieval via Mobile (Revertive) How It Starts What Happens Figure Voice-Mail Retrieval via Mobile (*Feature Code) How It Starts What Happens Figure Voice-Mail Retrieval via PSTN How It Starts What Happens Figure Feature Activation/Deactivation How It Starts What Happens Figure Wiretap/Court-Ordered Surveillance How It Starts What Happens Figure Mobile Security Entry How It Starts What Happens Figure
Issue 27
May 2004
xxxix
401-610-133A
Contents
Virtual Switch Handoff How It Starts What Happens Figure Callback How It Starts What Happens Figure Mobile Termination (not Home DCS) with Call Forwarding How It Starts What Happens Figures Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail How It Starts What Happens Figures Test Calls How It Starts What Happens Tracer Records
A-75 A-75 A-75 A-75 A-76 A-76 A-76 A-76 A-77 A-77 A-77 A-77 A-79 A-79 A-79 A-79 A-81 A-81 A-81 A-82
History of Revisions
Changes for ECP Release 22.0 AMA Enhancement of Home Zone Service for Phase 2 and KTF Intelligent Networking Support of KTF Wireless Number Portability Report Call Forwarding Due to No Reply in AMA Records Background Functionality Imsi In-bound Roaming for KTF Documentation Fixes for the Metered Billing Feature Append Specific AMA Modules to Structure Code x2351 Feature Obsolete Features Changes for ECP Release 21.0 Reason for Reissue Introduction
B-1 B-2 B-2 B-4 B-4 B-4 B-5 B-5 B-5 B-8 B-9 B-10 B-10
xl
Issue 27
May 2004
Contents
Charging Band for Metering Pulse Providing Redirection Information in KTF Recall Service Answer Hold Call Drop Handling Limited Mobility Services with Multiple SDCAs/MDNs Maintain AMA Measurement Data Reporting What the Feature Does How the Feature Works Per-Call Measurement Data (PCMD) AMA Enhancements of Home Zone Service Phase 2 and KTF Intelligent Network Service Call Scenarios Documentation Fixes Changes for ECP Release 20.0 Introduction IS-826 Locally-Allowed Specific Digit String Trigger Selectable Mode Vocoder on PHV KTF Home Zone Service Phase 2 Documentation Fix Consolidation of 15 Digit DN Information Changes for ECP 19.0 Introduction Table Speech Handler Trunk Information in AMA Seven Digit AMA Block Sequence Number Fix to Radio Channel Number Range Specific Called Party Digit String Trigger TDMA Channel Usage Tracking Tool Feature Enhancement to Far End Release Cause Values in AMA Records Documentation Fix for MDCR Feature Documentation Fix for 15 Digit DN Feature Customized ESN Format in AMA Record Documentation Fixes for Service Feature Codes Documentation Fix for Structure Code x2351 Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records Service Feature Code for Unknown Feature Activation/Deactivation B-10 B-12 B-12 B-13 B-14 B-16 B-16 B-16 B-17 B-18 B-20 B-20 B-21 B-21 B-22 B-23 B-24 B-25 B-25 B-26 B-26 B-26 B-27 B-27 B-28 B-28 B-29 B-31 B-32 B-32 B-33 B-33 B-33
B-34 B-34
Issue 27
May 2004
xli
401-610-133A
Contents
Changes for ECP 18.0 Introduction Table 15 Digit DN - REMINDER Seven Digit AMA Block Sequence Number Intermediate AMA for LDC Support New Service Option of 13K Service IS-826 Prepaid Base Cell Origination Request Time Stamps WIN-Based Flexible Alerting Measurement Data in Call Records Documentation Fix for Module 621 User Interactive SMS Documentation Fixes New Information on Storage of MIN and IMSI Changes for ECP 17.0 and ECP 17.1 Introduction AMA Linking Functionality Charge Class Population in AMA R2 and ISUP Charge Indication in AMA TDMA IMSI Feature Correction Removal of Obsolete Service Feature Code Remote Feature Control Feature Corrections to Timing Indicator Information More Information About Appended Modules Connect Resource Operations (Terminations) SKT PrePaid Service CDMA Network Directed System Selection (NDSS) New Mobile Security Indicator Changes for ECP Release 16.0 Introduction 15 Digit DN Changes Summary of Changes Other Changes for 16.0 5ESS Switch Wireless PRI for CDMA Dual Mode Mobiles TDMA Circuit-Mode Data Services Feature IP Billing Feature TDMA IMSI Feature CDMA IP Packet Switched Data
B-36 B-36 B-36 B-37 B-37 B-38 B-40 B-40 B-41 B-42 B-43 B-43 B-44 B-45 B-45 B-46 B-46 B-47 B-48 B-49 B-50 B-51 B-52 B-52 B-54 B-54 B-55 B-58 B-59 B-60 B-61 B-61 B-61 B-61 B-61 B-62 B-63 B-64 B-66 B-67
xlii
Issue 27
May 2004
Contents
3G-1X Low Speed Packet Data Service Metered Billing for TDMA Circuit Switch Data Calls Feature Append Module 331 to 1336 AMA Record FERCV AMA Record Generation for Redirecting Number Information Added to TDMA Chapter Information Added to CDMA Chapter Changes for ECP Release 15.0 Introduction ANSI-41 Billing Module with Service Type Changeable No Answer Timer TDMA Circuit-Mode Data Services Feature IP Billing Feature CDMA Meter Pulse TSI Bridging Feature LAES Feature TDMA IMSI Feature Increase AMA Record Storage with DAT Feature CDMA Circuit IP Services Improvements Not Related to a Feature Changes for ECP Release 14.1 Introduction About the 14.1 Re-Release of This Document Calling Name Presentation for TDMA Feature, Phase 2 CDMA Full IMSI Incoming Call Dialed Digits in AMA Record ANSI-41 Rev C Call Transfer Circuit Data IWF Indicator in AMA IS53 Preferred Language Analog Fax Support for CDMA Mobile Inactive Trigger AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature Technical Changes Not Related to a Feature CAROD KC02196 Changes for ECP Release 14.0 Introduction Calling Name Presentation for TDMA Feature, Phase 2 CDMA Full IMSI Incoming Call Dialed Digits in AMA Record ANSI-41 Rev C Call Transfer B-68 B-69 B-71 B-72 B-73 B-74 B-75 B-76 B-76 B-77 B-78 B-79 B-80 B-81 B-82 B-83 B-84 B-84 B-85 B-86 B-88 B-88 B-88 B-89 B-89 B-90 B-91 B-92 B-93 B-94 B-95 B-98 B-98 B-99 B-100 B-100 B-100 B-101 B-102 B-103
Issue 27
May 2004
xliii
401-610-133A
Contents
Circuit Data IWF Indicator in AMA IS53 Preferred Language Analog Fax Support for CDMA Mobile Inactive Trigger AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature Technical Changes Not Related to a Feature CAROD KC02196 Changes for ECP Release 13.0 Introduction No Charge Calls in AMA Record AMA Calling Party Category Information Wireless Number Portability Over the Air Activation Feature Last Call Return Feature Calling Name Presentation for TDMA Feature Separation of MSID-MDN Feature Flexible Alerting Feature CDMA Packet-Mode Data Service Feature CDMA Private Network and User Zone ANSI-41 Billing Module Changes for ECP Release 12.0 Changes Made in ECP Release 11.0 New Features Changes Changes for ECP Release 10.0 New Features Changes New Features for ECP Release 9.0 New Features New Features for ECP Release 8.0 New Features New Features for ECP Release 7.0 New Features New Features for ECP Release 6.1+ New Features B-104 B-105 B-106 B-107 B-109 B-109 B-110 B-111 B-111 B-112 B-113 B-115 B-117 B-118 B-119 B-121 B-123 B-125 B-127 B-128 B-131 B-132 B-132 B-132 B-135 B-135 B-135 B-138 B-138 B-139 B-139 B-140 B-140 B-141 B-141
Basic Voice-Channel Elapsed Time Values
Introduction
C-1
xliv
Issue 27
May 2004
Contents

Basic Voice-Channel Usage Basic Digital Voice-Channel Usage Basic Analog Voice-Channel Usage
C-2 C-3 C-4
Physical and Logical Radio Number Assignment for TDMA Flexent Cells

Introduction Table
D-1 D-2
Changes for the 15 Digit DN Feature
Introduction What is the 15 Digit DN Feature? Massive Changes to AMA Use of Italic Font For Further Information Documentation Impact of 15 Digit DN Feature Introduction One Version of AMA Formats From 21.0 Forward One Version of AMA Search From 21.0 Forward Summary of Changes to Structure Code Layouts Introduction What was Changed? Changes not Related to 15 Digit DN What did not Change? Quick Reference List Deleted Fields Fields Moved Into Existing Modules Introduction PAS Information LSA Indicator and Elapsed Time Three-Way Transition Elapsed Time New Time Type for Three-Way Transition Elapsed Time DCS Outpulsed Digits Quick Reference to Structure Code Layouts Introduction
E-1 E-1 E-1 E-1 E-2 E-3 E-3 E-3 E-3 E-4 E-4 E-4 E-4 E-5 E-5 E-5 E-6 E-6 E-6 E-6 E-6 E-6 E-7 E-8 E-8
Issue 27
May 2004
xlv
401-610-133A
Contents
Table Summary of Changes to AMASE Tables Introduction Contents New AMASE Tables Introduction Terminology Tables AMASE Record Fields Moved to a Different Table Introduction Impacted AMASE Tables Fields Moved Out of AMASE Table 7 Introduction Table Fields Moved Out of AMASE Table 12 Introduction Multiple Service Feature Codes Split Apart Table Fields Moved Out of AMASE Table 364 Introduction Multiple Special Routing Feature Indicator Split Apart Table Fields Moved Out of AMASE Table 365 Introduction Multiple Service Feature Codes Split Apart Table Fields Moved Out of AMASE Table 569 Introduction Table Modified AMASE Tables Introduction Modified Tables Deleted AMASE Tables Table Other AMASE Table Changes Introduction Fields Moved Into Modules New AMASE Table Empty Elements Added for Future Expansion Summary of Changes to Modules
E-8 E-11 E-11 E-11 E-12 E-12 E-12 E-12 E-16 E-16 E-16 E-17 E-17 E-17 E-19 E-19 E-19 E-19 E-22 E-22 E-22 E-22 E-24 E-24 E-24 E-24 E-30 E-30 E-30 E-31 E-31 E-31 E-33 E-33 E-35 E-35 E-35 E-35 E-35 E-36
xlvi
Issue 27
May 2004
Contents
Introduction New Modules Introduction Table Renamed Module Introduction Table Deleted Modules Introduction Table
E-36 E-37 E-37 E-37 E-38 E-38 E-38 E-39 E-39 E-39
IN
Index
IN-1
Issue 27
May 2004
xlvii
401-610-133A
Contents
xlviii
Issue 27
May 2004
Figures
About This Document
12
13
14
15
16
17
18
Calling Number Identification Presentation and Restriction Capability Feature
19
LSA Features
Issue 27
May 2004
xlvii
401-610-133A
Figures
20
21
22
Private Numbering Plan (PNP) Non-Dialable Digits in HLR Return Results Feature
23
24
25

25-1. The Inter-Working Function--How It Works 25-4
26
27
28
xlviii
Issue 27
May 2004
Figures
29
30
31
No Charge Calls in AMA Record Feature
32
33
34
CDMA Packet-Mode Data Services Features
35
AMA Calling Party Category Information Feature
36
37
Issue 27
May 2004
xlix
401-610-133A
Figures
38
ANSI-41 Billing Module and ANSI-41 Billing Module with Service Type Features
39
40

40-1. The Inter-Working Function--How It Works 40-4
41

41-1. TSI Bridging 41-5
42
LAES Feature
43
TDMA IMSI Feature
44
IP Billing Feature
45
Issue 27
May 2004
Figures
46
47
Seven Digit AMA Block Sequence Number
48
49
50
51
52
Far End Release Cause Values in AMA Records
53
54
Issue 27
May 2004
li
401-610-133A
Figures
55
56
57
AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service Feature
Call Scenarios
A-1. A-2. A-3. A-4. A-5. Mobile Origination Mobile Origination (not Home DCS) Mobile Origination with Internal DCS Handoff Mobile Origination with Handoff Call Segment Relationships for Mobile Origination with Handoff A-6. Mobile Origination with Handoff and Handback A-7. Call Segment Relationships for Mobile Origination with Handoff and Handback A-8. Mobile Termination A-9. Mobile Termination (not Home DCS) A-10. Call Segment Relationships for Mobile Termination (not Home DCS) A-11. Incomplete Mobile Termination (No Page Response) A-12. Mobile Termination (Failed) A-13. Mobile Termination (Unanswered) A-14. Mobile Termination Overflow A-15. Mobile Termination with Handoff A-16. Call Segment Relationships for Mobile Termination with Handoff A-17. Mobile Termination with Handback A-15 A-16 A-17 A-18 A-19 A-21 A-22 A-23 A-24 A-25 A-26 A-27 A-28 A-29 A-30 A-31 A-33
lii
Issue 27
May 2004
Figures
A-18. Call Segment Relationships for Mobile Termination with Handback A-19. Mobile Termination with Handoff and Handback A-20. Call Segment Relationship for Mobile Termination with Handoff and Handback A-21. Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2 A-22. Call Segment Relationships for Mobile Termination with Handoff to 2, Handoff to 3, and Handback 2 A-23. Mobile to Mobile Termination A-24. Mobile to Mobile with Tandem A-25. Call Delivery (via Internal Trunks) A-26. Call Delivery (via ANSI-41) A-27. Call Delivery (Internal) with Handoff A-28. Call Delivery (ANSI-41) with Handoff 1-29. Call Segment Relationships for Call Delivery (ANSI-41) with Handoff A-30. Call Delivery to Call Waiting 1-31. Call Segment Relationship for Call Delivery to Call Waiting A-32. Call Forwarding to Mobile A-33. Call Waiting (No Answer Forward to PSTN) A-34. Call Segment Relationships for Call Waiting (No Answer Forward to PSTN) A-35. Call Waiting (No Answer Transfer to Voice Mail) A-36. Call Segment Relationships for Call Waiting (No Answer Transfer to Voice Mail) A-37. Mobile Termination with Call Waiting A-38. Call Segment Relationship for Mobile Termination with Call Waiting A-39. Mobile Origination with Call Waiting A-40. Call Segment Relationships for Mobile Origination with Call Waiting A-41. Mobile Origination with Three-Way Calling A-42. Three-Way Calling with Handoff A-43. Call Transfer Scenario l A-44. Call Segment for a Call Transfer from a Mobile-Originated Call
A-33 A-35 A-36 A-38 A-39 A-40 A-41 A-42 A-43 A-44 A-46 A-46 A-48 A-48 A-50 A-52 A-53 A-54 A-55 A-56 A-57 A-58 A-59 A-60 A-62 A-64 A-64
Issue 27
May 2004
liii
401-610-133A
Figures
A-45. Call Transfer Scenario 2 A-46. Call Segment for a Call Transfer from a Mobile-Terminated Call A-47. Voice-Mail Retrieval via Mobile (Revertive) A-48. Voice-Mail Retrieval via Mobile (*Feature Code) A-49. Voice-Mail Retrieval via PSTN A-50. Feature Activation/Deactivation A-51. Wiretap/Court-Ordered Surveillance A-52. Mobile Security Entry 1-53. Virtual Switch Handoff A-54. Callback A-55. Mobile Termination (not Home DCS) with Call Forwarding A-56. Call Segment Relationships for Mobile Termination (not Home DCS) with Call Forwarding A-57. Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail A-58. Call Segment Relationships for Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail A-66 A-67 A-68 A-69 A-70 A-72 A-73 A-74 A-75 A-76 A-78 A-78 A-79
A-80
B-1. Generation of Linked AMA Records for a Connect Resource Operations (Terminations) Feature Call B-56
Physical and Logical Radio Number Assignment for TDMA
liv
Issue 27
May 2004
Figures
Flexent Cells
Issue 27
May 2004
lv
401-610-133A
Figures
lvi
Issue 27
May 2004
Tables
About This Document
57
AB
About This Document

1. 2. Table of Contents for Changed Features Section Changes for the Support of KTF Wireless Number Portability Feature 3. Changes for the Report Call Forwarding Due to No Reply in AMA Records Feature 4. Changes for the IMSI In-bound Roaming for KTF Feature 5. Changes for the Metered Billing Feature 6. Changes for the Append Specific AMA Modules to Structure Code x2351 Feature 1-68 1-70 1-71 1-72 1-72 1-73
12
13
14
15

Issue 27
May 2004
lvii
401-610-133A
Tables
16
17
18

18-1. ecp Form CPN Incoming Calls Module Fields Entries Summary 18-7
19
LSA Features
20
21
22
23

lviii
Issue 27
May 2004
Tables
24
25
26
27

27-1. AMA Record Fields and AMASE Tables Used by Metered Billing 27-6
28

28-1. AMA Module Definitions 28-4
29
30
31

31-1. Structure Codes for Call Type 074 31-3
Issue 27
May 2004
lix
401-610-133A
Tables
32
33
34

34-1. CDMA Packet Mode Data Services Features and the Event Descriptions Used by Each 34-9
35
36
37
38
39

39-1. AMA Records for Different Types of IMSI 39-5
lx
Issue 27
May 2004
Tables
40

40-1. Storage of a Dialed Digit String by the DDAMA Feature 40-16
41
42
LAES Feature
43
TDMA IMSI Feature
44
IP Billing Feature
44-1. How to Determine Where a TDMA DIA Number Will Be Placed in the AMA Record 44-5
45

45-1. Definition of CDMA Circuit IP Services Indicator 45-2. Storage of a Dialed Digit String by the DDAMA Feature 45-3. Storage of Dialed Digits by the DDAMA Feature 45-5 45-7 45-8
46
Issue 27
May 2004
lxi
401-610-133A
Tables
47
48

48-1. Digits Recorded Field as Used by the IS-826 Prepaid Base Feature 48-4
49

49-1. Digits Recorded Field as Used by the Speech Handler Trunk Information in AMA Feature 49-4
50
51
52

52-1. Digits Recorded Field as Used by the FERCV Feature 52-2. Digits Recorded Field as Used by the Enhanced FERCV Feature 52-4 52-5
53
lxii
Issue 27
May 2004
Tables
54

54-1. Digits Recorded Field as Used by the SMV on PHV Feature 54-7
55
56

56-1. Digits Recorded field for Generic Context ID 90062 56-3
57
57-1. AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service Feature 57-4
Call Scenarios
A-1. A-2. A-3. A-4. A-5. AMA Call Related Scenario Mapping Call Scenario Summary AMA Record Completeness Summary Scenario Composition Tracer Records A-3 A-4 A-8 A-12 A-82
3. Table of Contents for Changed Features Section B-1
Issue 27
May 2004
lxiii
401-610-133A
Tables
4. 5. 6. 7. 8. H-1. H-2. H-3. H-4. H-5. H-6. H-7. H-8. H-9. H-10. H-11. H-12. H-13. H-14. H-15. H-16. H-17. H-18. H-19. H-20. H-21. Changes for the Support of KTF Wireless Number Portability Feature Changes for the Report Call Forwarding Due to No Reply in AMA Records feature Changes for the IMSI In-bound Roaming for KTF Feature Changes for the Metered Billing Feature Changes for Append Specific AMA Modules to Structure Code x2351 Table of Contents for Changed Features Section Changes for Charging Band for Metering Pulse feature Changes for Providing Redirection Information in KTF Recall Service Feature Changes for Answer Hold feature Changes for Call Drop Handling feature Changes for Limited Mobility Services with Multiple SDCAs/MDNs Changes for Maintain Selected AMA Measurement Data Reporting Changes for Per-Call Measurement Data feature Changes for FID 10468.0 Table of Contents for Changed Features Section Changes for IS-826 Locally-Allowed Specific Digit String Trigger Feature Changes for Selectable Mode Vocoder on PHV Feature Changes for KTF Home Zone Service Phase 2 Feature Table of Contents for Changed Features Section Changes for Speech Handler Trunk Information in AMA Feature Changes for Seven Digit AMA Block Sequence Number Feature Changes for Specific Called Party Digit String Trigger Feature Feature Changes for TDMA Channel Usage Tracking Tool Feature Changes for Enhancement to Far End Release Cause Values in AMA Records Feature Customized ESN Format in AMA Record Feature Changes for Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records Feature
B-3 B-4 B-5 B-5 B-6 B-8 B-9 B-10 B-11 B-12 B-13 B-14 B-15 B-17 B-19 B-20 B-21 B-23 B-24 B-25 B-26 B-27 B-28 B-30 B-31
B-32
lxiv
Issue 27
May 2004
Tables
H-22. Changes for New Service Feature Code for Unknown Feature Activation/Deactivation H-23. Table of Contents for Changed Features Section H-24. Changes for Seven Digit AMA Block Sequence Number Feature H-25. Changes for Intermediate AMA for LDC Feature H-26. Changes for Support New Service Option of 13K Service Feature H-27. Changes for IS-826 Prepaid Base Feature H-28. Cell Origination Request Time Stamps Feature H-29. WIN-Based Flexible Alerting Feature H-30. Documentation Fix for Module 621 H-31. User Interactive SMS Feature H-32. Table of Contents for Changed Features Section H-33. AMA Linking Functionality Feature H-34. Charge Class Population in AMA Feature H-35. R2 and ISUP Charge Indication in AMA Feature H-36. Changes for TDMA IMSI Feature H-37. Correction H-38. Removal of Obsolete Service Feature Code H-39. Remote Feature Control Feature H-40. Pages Changed to Clarify Timing Indicator Information H-41. Pages Changed to Add More Information About Appended Modules H-42. Connect Resource Operations (Terminations) Feature H-43. SKT PrePaid Service Feature H-44. CDMA Network Directed System Selection Feature H-45. Changes for New Mobile Security Indicator H-46. Table of Contents for Changed Features Section H-47. Technical Changes for 5ESS Switch Wireless Primary Rate Interface for CDMA Dual Mode Mobiles Feature H-48. Technical Changes for TDMA Circuit-Mode Data Services Feature H-49. Technical Changes for IP Billing Feature H-50. Technical Changes for TDMA IMSI Feature H-51. Technical Changes for CDMA IP Packet Switched Data
B-33 B-34 B-36 B-37 B-38 B-39 B-40 B-40 B-41 B-43 B-44 B-45 B-46 B-48 B-49 B-49 B-50 B-51 B-52 B-52 B-56 B-57 B-57 B-58 B-60
B-61 B-62 B-63 B-64 B-65
Issue 27
May 2004
lxv
401-610-133A
Tables
H-52. Technical Changes for 3G-1X Low Speed Packet Data Service Feature H-53. Metered Billing for TDMA Circuit Switch Data Calls Feature H-54. Append Module 331 to 1336 AMA Record Feature H-55. Far End Release Cause Values for ISUP and R2 in the AMA Record Feature H-56. AMA Record Generation for Redirecting Number Feature H-57. TDMA Circuit-Mode Data Services Chapter H-58. CDMA Circuit-Mode Data Services Chapter H-59. Table of Contents for Changed Features Section H-60. Changes for ANSI-41 Billing Module With Service Type Feature H-61. Changes for Changeable No Answer Timer Feature H-62. Changes for Authentication Indicator in AMA for Home Subscribers Feature H-63. Changes for TDMA Circuit-Mode Data Services Feature H-64. Changes for IP Billing Feature H-65. Changes for CDMA Meter Pulse Feature H-66. Changes for TSI Bridging Feature H-67. Changes to LAES Feature H-68. Changes for TDMA IMSI Feature H-69. Changes for Increase AMA Record Storage with DAT Feature H-70. CDMA Circuit IP Services H-71. Improvements in AMASE Table 497 H-72. Missing Information Added in AMASE Table 365 H-73. Changed Pages Per Feature H-74. Changes for Calling Name Presentation for TDMA Feature, Phase 2 H-75. Changes for CDMA Full IMSI Feature H-76. Changes for Incoming Call Dialed Digits in AMA Record Feature H-77. Changes for ANSI-41 Rev C Call Transfer Feature H-78. Changes for Circuit Data IWF Indicator in AMA Feature H-79. Changes for IS53 Preferred Language Feature H-80. Changes for Analog Fax Support for CDMA Feature H-81. Changes for Mobile Inactive Trigger Feature
B-67 B-68 B-69 B-70 B-71 B-72 B-73 B-74 B-76 B-77 B-77 B-78 B-79 B-80 B-81 B-81 B-82 B-83 B-84 B-84 B-85 B-86 B-87 B-88 B-89 B-90 B-91 B-92 B-93 B-95
lxvi
Issue 27
May 2004
Tables
H-82. Changes for AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature B-96 H-83. Changes for Authentication Indicator in AMA Feature B-97 H-84. Technical Changes Not Related to New Features B-98 H-85. Changes for CAROD KC02196 B-99 H-86. Changed Pages Per Feature B-100 H-87. Changes for Calling Name Presentation for TDMA Feature, Phase 2 B-101 H-88. Changes for CDMA Full IMSI Feature B-102 H-89. Changes for Incoming Call Dialed Digits in AMA Record Feature B-102 H-90. Changes for ANSI-41 Rev C Call Transfer Feature B-104 H-91. Changes for Circuit Data IWF Indicator in AMA Feature B-105 H-92. Changes for IS53 Preferred Language Feature B-106 H-93. Changes for Analog Fax Support for CDMA Feature B-107 H-94. Changes for Mobile Inactive Trigger Feature B-108 H-95. Changes for AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature B-109 H-96. Changes for Authentication Indicator in AMA Feature B-110 H-97. Technical Changes Not Related to New Features B-111 H-98. Changes for CAROD KC02196 B-112 H-99. Changed Pages Per Feature B-113 H-100.Changes for No Charge Calls in AMA Record Feature B-114 H-101.Changes for AMA Calling Party Category Information FeatureB-116 H-102.Changes for Wireless Number Portability Feature B-117 H-103.Changes for Over the Air Activation Feature B-120 H-104.Changes for Last Call Return Feature B-121 H-105.Changes for Calling Name Presentation for TDMA Feature B-121 H-106.Changes for Separation of MSID-MDN Feature B-123 H-107.Changes for Flexible Alerting Feature B-125 H-108.Changes for CDMA Packet-Mode Data Services Feature B-128 H-109.Changes for CDMA Private Network and User Zone Feature B-130 H-110.Changes for ANSI-41 Billing Module Feature B-131
Issue 27
May 2004
lxvii
401-610-133A
Tables
D-1. Correlation between Physical Radio Numbers and Logical Radio Numbers for TDMA Flexent Cells D-2

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Current Layouts Compared to Previous Layouts New AMASE Tables Values Moved From Table 7 to Tables 7, 2002 and 2007 Values Moved From Table 12 to Table 2002 Values Moved From Table 364 to Table 2002 Values Moved From Table 365 to Table 2002 Values Moved From Table 569 to Table 237 Modified AMASE Tables Deleted AMASE Tables New Modules Renamed Module Deleted Modules E-9 E-13 E-17 E-19 E-22 E-24 E-30 E-31 E-33 E-37 E-38 E-39
lxviii
Issue 27
May 2004
About This Document
Introduction
Purpose
This AMA Formats Description manual describes the Automated Message Accounting (AMA) formats for the Flexent/AUTOPLEX wireless network Executive Cellular Processor (ECP) software. For a complete list of the new material and changes to this document for the current ECP release, see the Reason for Reissue on page lxviii. Also covered in this document is an overview of AMA, structure code numbers and structure code layouts, and AMA record fields. Finally, this document gives descriptions of AMA-related features and the AMA impact for each feature.
Issue 27
May 2004
lxvii
401-610-133A
Reason for Reissue

Introduction
This issue of the AMA Formats Description includes information about new features for the following releases:

ECP Release 22.0 Software Updates (SUs) that were released since the previous issue of this document.
Table 1 on page lxviii lists the features that impact AMA and gives the page number of the writeup in this section that summarizes the technical changes for the feature. Table 1 Table of Contents for Changed Features Section Feature ID 10468.1 10643.0 10667.0 10796.0 NA 10904.0 3876.0 and 3876.1 Page lxviii lxviii lxx lxxi lxxii lxxiii lxxiii
Feature AMA Enhancement of Home Zone Service Phase 2 and KTF Intelligent Networking Support of KTF Wireless Number Portability Report Call Forwarding Due to No Reply in AMA Records Imsi In-Bound Roaming for KTF Documentation Fixes for Metered Billing Append Specific AMA Modules to Structure Code x2351 Obsolete Features
AMA Enhancement of Home Zone Service for Phase 2 and KTF Intelligent Networking
The changes for Feature Identifier (FID) 10468.1 were covered under FID 10468.0 in ECP Release 21.0.
Support of KTF Wireless Number Portability

This section gives an overview of the WNP feature and the functionality of the Support of KTF Wireless Number Portability feature.
lxviii
Issue 27
May 2004
Overview of Wireless Number Portability

The Wireless Number Portability (WNP) feature allows a mobile user to retain the same Directory Number (DN) while the mobile user moves from one service provider to another service provider. The three types of Number Portability (NP) are as follows: Service Portability, Location Portability and Service Provider Portability.
Functionality
The Support of KTF Wireless Number Portability feature allows a mobile user to retain the same Mobile Directory Number (MDN) when the mobile user moves from one service provider to another service provider. AMA functionality for the Support of Wireless Number Portability (KTFWNPT) feature is similar to AMA for WNP, except that in the case of KTFWNPT, the

Location Routing Number can be 11 digits. Service provider ID appears in the WNP module (Service Provider ID field). ported status appears in the WNP module (BCD character 4 of the Supporting Information field).
NOTE: This feature does not apply to landline DNs. The Support of KTF Wireless Number Portability feature introduces the following Feature Activation File (FAF): Support of KTF Wireless Number Portability (KTFWNPT).
Issue 27
May 2004
lxix
401-610-133A
Table 2
Changes for the Support of KTF Wireless Number Portability Feature Caused... the following changes:
This Change... Use of Digit Information Module
In... Chapter 4AMASE Tables
AMASE "Table 731 Location Routing Number (LRN)" on page 4-84 (A note is added to BCD 1 and the existing note in BCD 2 is modified to include KTFWNPT information.) "Table 732 Service Provider Identity" on page 4-85 (A note is added.) "Table 734 Supporting Information" on page 4-87 (A note is added under BCD character 4.)
changes to
Chapter 5Modules
"Module 720Wireless Number Portability Module" on page 5-73.The KTFWNPT feature is added to
"Features that Use this Module" on page 5-73. "Module Generation Criteria" on page 5-73 and the note that follows the module generation criteria is modified. the "Module Generation Criteria for Wireless Number Portability Feature" on page 36-9. (The first bullet item is modified to include the KTFWNPT FAF). Chapter 36Wireless Number Portability Feature
changes to
Report Call Forwarding Due to No Reply in AMA Records

This section provides the background and the functionality that are associated with the Report Call Fowarding Due to No Reply in AMA Records feature.
lxx
Issue 27
May 2004
Background
Prior to the Report Call Forwarding due to No Reply in AMA Records feature, when a call is forwarded, the service feature field in the AMA record indicates the following: Call ForwardingBusy/Dont Answer/No Page Response (14). The reason for forwarding the call is not indicated. When the Conditional Call Forwarding (CCF) feature is active and the Show CCF sub-case in AMA records field in the Executive Cellular Processor (ecp) form is set to y, the following service feature codes are displayed, Call ForwardingBusy (152) and Call ForwardingNo Reply (153). The reason for forwarding the call is not indicated.
Functionality
The Report Call Forwarding Due to No Reply in AMA Records feature introduces two service feature codes: Call ForwardingNo Page Response, (154) and Call ForwardingMobile Inactive, (155). The Report Call Forwarding Due to No Reply in AMA Records feature indicates a reason in the service feature code for a forwarded call when there is no reply. Table 3 Changes for the Report Call Forwarding Due to No Reply in AMA Records Feature Caused... the addition of the following 2 new service feature codes:
This Change... New service feature codes
154 = Call Forwarding - No Page Response in "Table 2002 Service Feature Code" on page 4-119 and 155 = Call Forwarding - Mobile Inactive in "Table 2002 Service Feature Code" on page 4-119.
IMSI In-bound Roaming for KTF

The IMSI In-bound Roaming for KTF feature allows Global System for Mobile Communications (GSM) subscribers to roam into the Code Division Multiple Access (CDMA) network and avail origination and termination services. GSM subscribers use CDMA handsets with GSM sim cards. Roaming Gateway maps CDMA messages to GSM and vice versa to communicate with the GSM system. AMA marks GSM roaming subscriber as 8 to denote that it is a GSM subscriber.
Issue 27
May 2004
lxxi
401-610-133A
Table 4
Changes for the IMSI In-bound Roaming for KTF Feature Caused... the addition of
This Change... Denoting type of technology
08 = GSM in Table 471 Type of Technology
Documentation Fixes for the Metered Billing Feature

Chapter 27Metered Billing Feature is updated to include changes as per AR-075102. Special Routing/Increased Court Ordered Surveillance (ICOS) functionality is added to Metered Billing and is available in ECP Release 17.0 and later. Table 5 on page lxxii refers to how Metered Billing uses the AMASE tables and AMA Record fields. Table 5 Changes for the Metered Billing Feature Caused...
This Change... information about ICOS supporting Metered Billing
In... Chapter 27Metered Billing Feature
the addition of Table 27-1 "AMA Record Fields and AMASE Tables Used by Metered Billing" on page 27-6.
Append Specific AMA Modules to Structure Code x2351 Feature

If the Append AMA Specific AMA Modules to Structure Code x2351 FAF is on, the following AMA modules are appended to the structure code x2351:

330 331 621 with Generic Context Identifier 10843 621 with Generic Context Identifier 10860 621 with Generic Context Identifier 90002 621 with Generic Context Identifier 90010 623
lxxii
Issue 27
May 2004
Table 6
Changes for the Append Specific AMA Modules to Structure Code x2351 Feature Caused...
This Change... use of structure code x2351
In... Chapter 3Structure Code Layouts Chapter 5Modules
modifications to Table 3-28 "Valid Modules for Structure Code x2351" on page 3-48 modifications to Table 5-3, Module Generation Criteria. additions to "Modules 330 and 331CPN Incoming Calls Modules" on page 5-28 additions to "Module 621 - Digit Information Module" on page 5-46 with generic context identifiers 90002, 90010, 10843, 10860 modifications to "Module 623 Trunk Information Module" on page 5-70 adding structure code x2351 to Module 331 in "Use of CPN Incoming Calls Module-2" on page 17-3 modifications to "Module Generation Criteria for CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module" on page 18-4 modifications to "Trunk Information Module" on page 28-7
the following change:
Chapter 17AMA Containing Incoming Automatic Number Identification (AMANI) Feature Chapter 18Calling Number Identification Presentation and Restriction Capability Feature Chapter 28AMA Enhancements Feature
Obsolete Features
The following features are obsolete and have been deleted from the book:

IS41 Roamer Administration Service (IS41-RAS) Authentication Indicator in AMA Records (FID 3876.0) Authentication Indicator in AMA for Home Subscribers (FID 3876.1)
Issue 27
May 2004
lxxiii
401-610-133A
lxxiv
Issue 27
May 2004
Historical Record of Revisions

For a listing of revisions that have been made to this manual in previous ECP releases, read Appendix BHistory of Revisions.
Issue 27
May 2004
lxxv
401-610-133A
Safety Labels
This information product may contain the following types of safety labels:
A CAUTION admonishment indicates a hazard that can or will cause minor personal injury, loss of data, service interruption, or property damage if the hazard is not avoided.
CAUTION:
A WARNING admonishment indicates a hazard that can cause death or severe personal injury if the hazard is not avoided.
WARNING:
A DANGER admonishment indicates a hazard that will cause death or severe personal injury if the hazard is not avoided.
DANGER:
lxxvi
Issue 27
May 2004
Intended Audience
This document is intended for engineers, technicians, and administrators who work with AMA record formats and the AMA teleprocessing (AMATP) layouts and who have turned on the 15 Digit DN AMA record structures for their system (the Variable 15 DN Enhanced AMA Recording field on the ecp RC/V form).
Issue 27
May 2004
lxxvii
401-610-133A
Prerequisite Skills and Knowledge

To use this document effectively, you should have a general understanding of call processing, the basic concepts of wireless technology, and of Binary Coded Decimal (BCD) and hexadecimal notation.
lxxviii
Issue 27
May 2004
Conventions Used in This Document

The conventions that follow are used throughout this document:
Constant width typeface is used for the following:

AMASE table field names Recent change and verify (RC/V) form names, status, and display page names
Bold typeface is used for the NOTES and for points that need special emphasis. Italic typeface is used for the following: Titles of other documents. For example, Flexent/AUTOPLEX Wireless Network Output Messages (401-610-057). Emphasis within text. For example, This option can only be used if the Dynamic Output Message Routing feature is supported.
Issue 27
May 2004
lxxix
401-610-133A
To Obtain Technical Support, Documentation, and Training or Submit Feedback

The 401-010-001 Flexent/AUTOPLEX Wireless Networks Systems Documentation CD-ROM and web site provide a To obtain documentation, training, and technical support or send feedback document. That document explains how to

obtain technical support register as an authorized user of the Lucent Technologies customer technical support web site access the most current AMPS/PCS and related 5ESS Digital Cellular Switch (DCS) documentation on the site order system and product documentation order training products or register for classroom training courses submit comments and feedback about documentation and training
The To obtain documentation, training, and technical support or submit feedback document is available on the 401-010-001 Flexent/AUTOPLEX Wireless Networks System Documentation CD-ROM or the documentation web site at https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/.
lxxx
Issue 27
May 2004
12
12-1 12-1 12-2 12-2 12-2 12-2 12-2 12-3 12-3 12-3 12-3 12-4

Introduction What is the Dynamic Routing Feature? How Does It Work? Benefits Changes in Field Definitions Carrier Prefix Origination Indicator
AMA Impact

Feature Interaction
Issue 27
May 2004
12-i
401-610-133A
12-ii
Issue 27
May 2004
12
Introduction
This chapter provides information on the Dynamic Routing optional feature and describes how AMA functionality is affected by this feature.
For Further Information

There is no optional feature document for this feature. For more about this feature, contact Lucent Technologies technical support.
Issue 27
May 2004
12-1
401-610-133A
Feature Description
Introduction
This section describes the Dynamic Routing feature.
What is the Dynamic Routing Feature?

Dynamic Routing allows the system operator to control the routing of subscriberoriginated calls to network interface trunks depending upon the time of day and day of year.
How Does It Work?

With Dynamic Routing, routing is performed in accordance with a routing plan that represents a mapping from the digits received from a particular subscriber to a set of trunk groups and information specifying the outpulsing digit formation. Of the multiple plans available with Dynamic Routing, the plan in effect can be changed either manually by the system operator or according to a time schedule prespecified by the system operator.
Benefits
The Dynamic Routing capability can be applied by the system operator to take advantage of variations in carrier rate structures over time. This can allow the system operator to lower system operational costs and to offer new services.
12-2
Issue 27
May 2004
AMA Impact
Changes in Field Definitions
Dynamic routing affects the structure codes for cellular-originated calls with and without Carrier Interconnect (CI) information. The Dynamic Routing feature results in the following changes in the field definitions of the structure codes for cellularoriginated calls.
Carrier Prefix
For calls that need a carrier, the Carrier Prefix field indicates the XXX code of the dynamically selected carrier when dynamic routing is implemented, the XXX code of a subscriber-dialed carrier (for example, 10XXX is dialed), or the XXX code of the pre-selected carrier when basic routing is implemented. This field is used in structure codes x2330 and x2332. NOTE: The 10XXX digits become 101XXXX when the Carrier ID Expansion for Feature Group D feature is active.
Origination Indicator
The Origination Indicator field indicates if dynamic routing or basic routing is used. This field is used in structure codes x2329, x2330, x2332, and x2333. NOTE: If the Dynamic Routing feature is not active and if the subscriber does not have an assigned PIC and has not dialed an interexchange carrier, then the Origination Indicator indicates basic routing as the default.
Issue 27
May 2004
12-3
401-610-133A
Feature Interaction
This feature does not interact with other AMA features.
12-4
Issue 27
May 2004
13
13-1 13-1 13-2 13-2 13-2 13-2 13-2 13-2 13-3 13-4 13-4 13-4 13-4 13-4 13-5 13-5 13-5 13-5 13-5 13-6 13-6 13-7

Introduction What is the MRS Feature? How Does It Work? Benefits For Further Information
AMA Impact Message Recording with MRS

Introduction Called-Party Elapsed Time Digital Called-Party Elapsed Time Message Recording Service Indicator Voice-Channel Seizure Time (Date) Voice-Channel Answer Time (Date) Voice-Channel Elapsed Time Digital Voice-Channel Elapsed Time Initial Radio/Channel Number and Cell Site Last Radio/Channel Number and Cell Site Number of Handoffs
Message Retrieval with MRS
Issue 27
May 2004
13-i
401-610-133A
Introduction Message Retrieval via the Message Retrieval Code Feature Call Answer Status Terminating Number Called-Party Elapsed Time Digital Called-Party Elapsed Time Message Recording Service Indicator Voice-Channel Answer Time (Date) Conditional Call Forwarding Call Waiting
13-7 13-7 13-7 13-7 13-7 13-7 13-8 13-8 13-9 13-9 13-9
Feature Interaction

13-ii
Issue 27
May 2004
13
Introduction
This chapter provides information on the Message Recording Service (MRS) feature and describes how AMA functionality is affected by this feature. This chapter also summarizes feature interactions of the MRS feature with other features.

More detailed information about this feature can be found in 401-601-021, Message Recording Service Optional Feature.
Issue 27
May 2004
13-1
401-610-133A
Feature Description
Introduction
This section describes the MRS feature.
What is the MRS Feature?

The Flexent/AUTOPLEX Wireless Network Message Recording Service (MRS) feature allows a subscriber to have calls conditionally forwarded to a voice mail storage system (VMSS) where the calling party can leave messages for the subscriber if the MRS feature is activated and the subscriber is busy, doesnt answer, or is under a no-page response condition. Depending on the vendor equipment, the subscriber can then access the VMSS to listen to new messages, re-listen to old messages, or change the personal greeting the caller is to receive.
How Does It Work?

The MRS feature uses a VMSS. The VMSS is a vendor-supplied product that is connected to the digital cellular switch (DCS) over a special trunk group defined as a record-only trunk group. The connection is made by forwarding the call to the VMSS when the MRS feature is activated and the no-answer criteria are met.
Benefits
This feature allows a subscriber to receive calls when the subscriber is busy or does not have the mobile unit turned on.

For sample scenarios using MRS for retrieval, read:

Voice-Mail Retrieval via Mobile (Revertive) on page A-68 Voice-Mail Retrieval via Mobile (*Feature Code) on page A-69 Voice-Mail Retrieval via PSTN on page A-70.
For sample scenarios using MRS for recording, read:

Call Waiting (No Answer Transfer to Voice Mail) on page A-54 Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail on page A-79.
13-2
Issue 27
May 2004
AMA Impact
The MRS feature affects the structure codes for cellular-originated calls without CI information and the structure codes for cellular-terminated calls. The following sections provide information on message recording and message retrieval using MRS.
Issue 27
May 2004
13-3
401-610-133A
Message Recording with MRS

Introduction
Calls to a cellular subscriber who has activated the MRS feature are routed to a Message Storage System (MSS). A termination AMA record is generated for the message recording time. The AMA record follows the format used for a cellularterminated call with certain changes in field definitions. The following paragraphs show the changes in field definitions caused by message recording via the MRS feature. NOTE: In the case of a message recording dont answer call, a voice channel is initially assigned. When the call is forwarded to an MSS, the voice channel is released, but the call is assumed to continue in the initial assigned mode (digital or analog) for the rest of the call.
Called-Party Elapsed Time

The Called-Party Elapsed Time field contains the time duration from the time that the MSC establishes a connection with the MSS (voice-channel answer time) to the time when a disconnect signal is received from the MSS or the originating office. This field contains both the analog and the digital portion of the elapsed time.
Digital Called-Party Elapsed Time

(Optionalcontained in the Auxiliary Time Module.) The Digital CalledParty Elapsed Time field contains the digital portion of the called-party elapsed time that is defined in the Called-Party Elapsed Time field. If the Digital Called-Party Elapsed Time field is non-zero, an Auxiliary Time Module of time type 001 (Digital Called-Party Elapsed Time) will be appended to the AMA record. If the Digital Called-Party Elapsed Time field is zero, an Auxiliary Time Module of time type 001 will not be appended.
Message Recording Service Indicator

The Message Recording Service Indicator field indicates the type of MSS that was accessed, and that an attempt was made to record a message(s).
13-4
Issue 27
May 2004
Voice-Channel Seizure Time (Date)

The Voice-Channel Seizure Time (Date) field contains one of the following:

If the cellular unit was alerted, the time (date) of voice-channel seizure If the cellular unit was not alerted, the time (date) that the incoming call was routed to the MSS.
Voice-Channel Answer Time (Date)

The voice-channel answer time (date) is the time (date) that the MSC establishes a connection with the MSS.
Voice-Channel Elapsed Time

The voice-channel elapsed time indicates the time duration from voice-channel seizure to the time when a disconnect signal is received from the MSS or the originating office. This field contains both the analog and the digital portion of the elapsed time.
Digital Voice-Channel Elapsed Time

(Optional - contained in the Auxiliary Time Module) The Digital VoiceChannel Elapsed Time (Digital VCET) field contains the digital portion of the VCET that is defined in the Voice Channel Elapsed Time field. If the Digital VCET field is non-zero, an Auxiliary Time Module of time type 002 (Digital Voice-Channel Elapsed Time) will be appended to the AMA record. If the Digital VCET field is zero, an Auxiliary Time Module of time type 002 will not be appended.
Initial Radio/Channel Number and Cell Site

For MRS dont answer calls, the Initial Radio/Channel Number and Cell Site field contains the radio number and cell site that served the call; otherwise, this field is filled with zeroes.
Issue 27
May 2004
13-5
401-610-133A
Last Radio/Channel Number and Cell Site

For MRS dont answer calls, if the Last RN/CS feature is active, the Last Radio/Channel Number and Cell Site field contains the radio number and cell site that were serving the call when alerting timed out. This is the same information as is placed in the Initial Radio Number and Cell Site field. For other MRS calls, this field is filled with zeroes.
Number of Handoffs
The Number of Handoffs field is filled with zeroes.
13-6
Issue 27
May 2004
Message Retrieval with MRS

Introduction
The AMA record format for the message retrieval capability of the MRS feature depends on how the MSS is accessed and from where the MSS is accessed. The following paragraphs provide information on message retrieval access and associated changes in field definitions.
Message Retrieval via the Message Retrieval Code Feature

An AMA record is generated for message retrieval whenever a cellular unit originates a call using a feature code (for example *XY) to access an MSS via the MSC. The AMA record follows the format used for a cellular-originated call with certain changes in the field definitions. The following paragraphs show the changes in field definitions caused by message retrieval via the MRS feature.
Call Answer Status

The Call Answer Status field indicates whether the call was answered by the MSS.
Terminating Number
The Terminating Number field indicates the number of the subscriber who activated the MRS feature.
Called-Party Elapsed Time

The called-party elapsed time is the time duration from the time that the MSS answers the call (voice-channel answer time) to the time when a disconnect signal is received from the MSS or when the cellular unit has released the voice channel. This field contains both the analog and digital portion of the elapsed time.
Digital Called-Party Elapsed Time

(Optionalcontained in the Auxiliary Time Module.) The Digital CalledParty Elapsed Time field contains the digital portion of the called-party elapsed time that is defined in the Called-Party Elapsed Time field. If the
Issue 27
May 2004
13-7
401-610-133A
Digital Called-Party Elapsed Time field is non-zero, an Auxiliary Time Module of time type 001 (Digital Called-Party Elapsed Time) will be appended to the AMA record. If the Digital Called-Party Elapsed Time field is zero, an Auxiliary Time Module of time type 001 will not be appended.
Message Recording Service Indicator

The Message Recording Service Indicator field indicates the type of MSS that was accessed and that the attempt was made to retrieve a message(s).
Voice-Channel Answer Time (Date)

The Voice-Channel Answer Time (Date) field indicates the time (date) that the MSS answers the call.
13-8
Issue 27
May 2004
Feature Interaction
Conditional Call Forwarding
If the subscriber has both the Conditional Call Forwarding and the MRS features, the Conditional Call Forwarding takes precedence over MRS. The Immediate Call Forwarding feature takes precedence over both the Conditional Call Forwarding feature and the MRS feature.
Call Waiting
If the subscriber has both the Call Waiting and the MRS feature, the subscriber can let the waiting party of a call go to the MRS recording device by not flashing to answer the third-party call. If the third party stays on the line until no-answer timing expires, they are connected to the VMSS.
Issue 27
May 2004
13-9
401-610-133A
13-10
Issue 27
May 2004
14
14-1 14-1 14-2 14-2 14-2 14-2 14-3 14-3 14-3 14-3 14-3 14-4 14-4

Introduction What is the Abbreviated Dialing with AMA Feature? Benefit Introduction Call Type Service Feature Target Address DDAMA and the ADWAMA Feature
AMA Impact

Feature Interaction
Issue 27
May 2004
14-i
401-610-133A
14-ii
Issue 27
May 2004
14
Introduction
This chapter provides information on the Abbreviated Dialing with AMA (ADWAMA) feature and describes how AMA functionality is affected by this feature. This chapter also summarizes feature interactions of the Abbreviated Dialing with AMA feature with other features.

There is no optional feature document for this feature. For more about this feature, contact Lucent Technologies technical support.
Issue 27
May 2004
14-1
401-610-133A
Feature Description
Introduction
This section describes the ADWAMA feature.
What is the Abbreviated Dialing with AMA Feature?

The Abbreviated Dialing with AMA (ADWAMA) feature allows subscribers to dial a *xx code, which generates an AMA record and returns a confirmation tone to the subscriber.
Benefit
The ADWAMA feature can be used to record the location of the subscriber using the AMA record. This was an old form of mobile registration used before the registration capability was built into the mobile. The ADWAMA feature was used with follow me roaming types of services.
14-2
Issue 27
May 2004
AMA Impact
Introduction
The Abbreviated Dialing with AMA feature uses structure code x2411. Whenever a subscriber dials an ADWAMA feature code (for example, *XX), a structure code x2411 is produced with certain changes in the field definitions. The paragraphs in the rest of this section describe these changes in field definitions.
Call Type
The Call Type field contains 308 for Flexent/AUTOPLEX wireless network Activation/Deactivation.
Service Feature
The Service Feature field contains 109 for ADWAMA.
Target Address
The Target Address field contains the ADWAMA feature code (XX without the *) dialed by the subscriber.
Issue 27
May 2004
14-3
401-610-133A
Feature Interaction
DDAMA and the ADWAMA Feature
The ADWAMA feature doesnt depend on the Dialed Digits in AMA (DDAMA) feature, but the DDAMA feature enhances the ADWAMA feature. For example, if the ADWAMA feature is active but the DDAMA feature is not and a mobile subscriber dials the ADWAMA code (for example *34), the AMA record will contain only the digits 34. If the DDAMA feature and the ADWAMA feature are active when the subscriber dials the *34, the AMA record will contain the full *34.
14-4
Issue 27
May 2004
15
15-1 15-1 15-2 15-2 15-2 15-2 15-2 15-3 15-3 15-4

Introduction What is the ARG Feature? How Does It Work? Benefits Changes in Field Definitions
AMA Impact
Feature Interaction
Issue 27
May 2004
15-i
401-610-133A
15-ii
Issue 27
May 2004
15
Introduction
This chapter provides information on the Automatic Roamer Greeting (ARG) feature and describes how AMA functionality is affected by this feature. This chapter also summarizes feature interactions of the ARG feature with other features.

More detailed information about this feature can be found in 401-612-003, Automatic Roamer Greeting Optional Feature.
Issue 27
May 2004
15-1
401-610-133A
Feature Description
Introduction
This section describes the ARG feature.
What is the ARG Feature?

The ARG feature automatically calls roamers upon entry into the cellular service area. When a roamer registers, the registration notifies the Flexent/AUTOPLEX wireless network that a roamer has entered the serving area. The Flexent/ AUTOPLEX wireless network, in turn, can connect an announcement to the roamer, providing any information the service provider chooses. For example, the announcement might provide dialing procedures and roamer access numbers.
How Does It Work?

Several filtering schemes are used to determine which roamers will receive such a greeting. For more information about these, refer to 401-612-003, Automatic Roamer Greeting Optional Feature.
Benefits
The ARG feature makes it easier for roamers to initiate and receive calls. Upon entering the cellular service area, roamers receive information (via an announcement) that instructs them on how to obtain service. Having informed roamers translates into more roamer activity on the MSC which, in turn, translates into increased revenue.
15-2
Issue 27
May 2004
AMA Impact
Changes in Field Definitions
The Automatic Roamer Greeting (ARG) feature allows service providers to connect roamers to an announcement once the roamer has entered a cellular service providers area. An AMA record is generated for the ARG time. The AMA record follows the format used for a cellular-terminated call except that the Trunk Network Number (TNN) for an ARG call is set to zero. This feature creates an x2331 structure code.
Issue 27
May 2004
15-3
401-610-133A
Feature Interaction
This feature is excluded from CDMA Circuit-Mode Data service. The Automatic Roamer Greeting is still sent to a data-capable mobile, but if that mobile responds to a greeting termination with a data or fax service option, the call is not completed. A new field in the ecp database is used to determine whether the subscriber is marked as having received the call. If it is not marked, further attempts are made to send the greeting even though this would result in wasted resources if the mobile is never switched out of data-only mode. If it is marked, no further attempts are made to send the greeting.
15-4
Issue 27
May 2004
16
16-1 16-1 16-2 16-2 16-2 16-2 16-2 16-3 16-3 16-3 16-3 16-4 16-4 16-4 16-4 16-5 16-6 16-6

Introduction What is the ADUB Feature? How Does It Work? Benefits Introduction Storage of Type of Technology and Station Class Mark Field Definitions Fields Module Code Field Time Type Field Elapsed Time Field With DCCH Non-Public Network Identifiers Feature
AMA Impact

Auxiliary Time Module
Feature Interaction
Issue 27
May 2004
16-i
401-610-133A
16-ii
Issue 27
May 2004
16
Introduction
This chapter provides information on the Analog/Digital Usage Billing (ADUB) feature and describes how AMA functionality is affected by this feature. This chapter also summarizes feature interactions of the Analog/Digital Usage Billing (ADUB) feature with other features.

More detailed information about this feature can be found in 401-601-008, Analog/ Digital Usage Billing Optional Feature.
Issue 27
May 2004
16-1
401-610-133A
Feature Description
Introduction
This section describes the ADUB feature.
What is the ADUB Feature?

The ADUB feature provides information on the usage of analog versus digital facilities in the AMA record. This allows the service provider to determine the total amount of time spent on each technology.
How Does It Work?

This feature stores information on digital usage in a module that is then appended to existing AMA records. The use of this module allows the structure and content of the existing fields in the AMA records to remain unchanged.
Benefits
The ADUB feature enables the service provider to distinguish digital elapsed time from analog elapsed time. It also affords the service provider the flexibility to design service plans that do the following:

Provide incentives to current subscribers to switch to digital service Allow different billing rates for analog and digital usage Include a yes/no indication of whether or not voice privacy was active at any time during the call in the AMA record.
16-2
Issue 27
May 2004
AMA Impact
Introduction
The ADUB feature impacts AMA records in two ways:
Use of existing fields in the structure code layouts to store Type of Technology and Station Class. Use of Auxiliary Time Module to provide elapsed time for the call.
Both impacts are described in this section.
Storage of Type of Technology and Station Class Mark

The service provider is able to store the mobiles type of technology and station class mark in AMA structure code layouts. The following structure code layouts can store this information: x2329, x2338, x2411, and x2415.
Field Definitions
For the ADUB feature, the Type of Technology field (see Table 4-39 "AMASE Table 471" on page 4-62) contains the mobiles technology type. The Station Class field (see Table 4-40 "AMASE Table 472" on page 4-65) contains the mobiles station class mark.
Issue 27
May 2004
16-3
401-610-133A
Auxiliary Time Module

The Auxiliary Time Module records the total amount of elapsed time spent on facilities. Since there may be different types of elapsed time recorded for a particular call, several different Auxiliary Time Modules may be appended to a single AMA record. Each Auxiliary Time Module records the digital portion of a specific type of elapsed time. See Time Type Field on page 16-4 for a listing of the valid types of elapsed time for the Flexent/AUTOPLEX wireless network. The following structure codes may generate the Auxiliary Time Module: x2329 through x2338 and x2411.
Fields
The Auxiliary Time Module contains the following fields:

Module Code Time Type Elapsed Time
Module Code Field

The Module Code field is set to 326.
Time Type Field

The Time Type field in the Auxiliary Time Module is used to indicate the particular type of elapsed time for which usage is being recorded. The possible types of elapsed time are defined by Table 4-43 "AMASE Table 473" on page 4-68 and include:

Digital Called-Party Elapsed Time Digital Voice-Channel Elapsed Time Total Digital LSA Elapsed Time Digital Three-Way Transition Elapsed Time Three-Way Transition Elapsed Time Digital Initial Voice-Channel Answer Elapsed Time Digital Total Voice-Channel Elapsed Time Digital LSA Level 1 Elapsed Time Digital LSA Level 2 Elapsed Time
16-4
Issue 27
May 2004
Digital LSA Level 3 Elapsed Time Digital User Zone Sequence Number 1 Elapsed Time Digital User Zone Sequence Number 2 Elapsed Time.
NOTE: An Auxiliary Time Module is appended only for elapsed time types that are nonzero. That is, for a given structure code, the number of Auxiliary Time Modules that will be appended to an AMA record depends on the number of Elapsed Time fields containing non-zero data.
Elapsed Time Field

The Elapsed Time field for digital time types contains the digital portion of the elapsed time. The Elapsed Time fields for AMA records generated by a slave system will span only the time in which the call is served by that system. However, the Elapsed Time fields for AMA records generated at a CPS will span the total call duration. The following elapsed time fields include both the analog and the digital portion of the elapsed time:

Called-Party Elapsed Time Voice-Channel Elapsed Time LSA Elapsed Time Three-Way Transition Elapsed Time Initial Voice-Channel Answer Elapsed Time Total Voice-Channel Elapsed Time User Zone Elapsed Time.
NOTE: Two Flexent/AUTOPLEX wireless network systems that are in an inter-vendor relationship are treated the same as in an inter-vendor relationship between an Flexent/AUTOPLEX and a non-Flexent/AUTOPLEX wireless network.
Issue 27
May 2004
16-5
401-610-133A
Feature Interaction
With DCCH Non-Public Network Identifiers Feature
The Service Provider is able to generate the Auxiliary Time Module with time types of 010 (Digital User Zone Sequence Number 1 Elapsed Time) and 011 (Digital User Zone Sequence Number 2 Elapsed Time) for structure codes x2329 - x2335, if the following conditions are true:

The ADUB feature is active in the FAF Either the DCCH Non-Public Network Identifiers feature or the Non-Public Network Identifiers-Analog feature is active in the FAF The ecp database field for Append User Zone Module to AMA Record? is set to y The Auxiliary Time Module is activated via RC/V.
16-6
Issue 27
May 2004
17
17-1 17-1 17-2 17-2 17-2 17-2 17-3 17-3 17-3 17-3 17-4 17-4 17-4 17-4 17-4 17-4

Introduction What is the ANI Feature? Benefits Introduction Use of CPN Incoming Calls Module-2 Change in Field Information for AMANI Introduction With the Call Forwarding Feature With the Call Waiting Feature With Special Cellular Networking Calls With the CPNAD Capability
AMA Impact


Issue 27
May 2004
17-i
401-610-133A
17-ii
Issue 27
May 2004
17
Introduction
This chapter describes how the AMA Automatic Number Identification (AMANI) feature impacts AMA. It also talks about how the AMANI feature interacts with other features, such as call forwarding, call waiting, and CPNAD, and how AMANI affects cellular networking calls.

More detailed information about this feature can be found in 401-612-213, AMA Calling Party Category Information Optional Feature. See also the AMA Containing Incoming ANI Optional Feature, 401-601-007.
Issue 27
May 2004
17-1
401-610-133A
Feature Description
Introduction
This section describes the AMANI feature and lists its benefits.
What is the ANI Feature?

The AMA Containing Incoming Automatic Number Identification (AMANI) feature provides the capability of including the incoming ANI in the AMA record for all subscribers of an AMANI service provider. ANI encompasses:
R2-signaled calling party identification (either calling party billing directory number or calling party number) ISUP-signaled calling party number Calling party mobile number of a mobile to mobile call
Benefits
This feature may increase revenue production for the service provider by generating distance sensitive billing for the subscribers.
17-2
Issue 27
May 2004
AMA Containing Incoming Automatic Number
AMA Impact
Introduction
This section describes the impact on AMA of the AMANI feature.
Use of CPN Incoming Calls Module-2

If the AMANI feature is activated, and the incoming ANI is available, then the CPN Incoming Calls Module-2 (see Table 5-7 on page 5-28) Module is appended to existing AMA records with the following structure codes: x2331, x2334, x2335 and x2351. NOTE: To append the structure code x2351, the Append Specific AMA Modules to Structure Code x2351 FAF must also be on.
Change in Field Information for AMANI

For the AMANI feature, the Disposition of CPN/Calling Name Information field is marked as Not Applicable. (This includes BCD characters 1, 2, and 3.) ANI is stored in the CPN Digits 1 through 11 and the CPN Digits 12 through 20 fields.
Issue 27
May 2004
17-3
401-610-133A
Introduction
This section describes interactions of the AMANI feature with other AMA features and capabilities.
With the Call Forwarding Feature

For a call forwarding call, the original calling party's ANI, not the forwarded subscriber's ANI, will be stored in the CPN Incoming Module-2 Module for the AMA record associated with the forwarded call.
With the Call Waiting Feature

For a call waiting call that comes in during a mobile-terminated or a mobileoriginated call, the call waiting partys ANI will be stored in the CPN Incoming Call Module-2 Module for the call waiting AMA record. If the original call was a mobiletermination, the original partys ANI will be stored in the CPN Incoming Calls Module-2 Module for the original partys AMA record. If the original call was a mobile-origination, then no ANI information exists (for the original leg of the call).
With Special Cellular Networking Calls

For Special Cellular Networking (CN) calls, the original calling partys ANI, not the TLDN, will be displayed in the CPN Incoming Calls Module-2 Module for the AMA record associated with the terminating party.
With the CPNAD Capability

Both the Calling Party Number Acceptance/Delivery (CPNAD) and AMANI features can append CPN Incoming Calls Modules (either Module-1 or Module-2) to an AMA record. However, only one CPN Incoming Call Module can be appended to any given AMA record. CPNAD will take precedence over AMANI in deciding which CPN Incoming Calls Module to append. For example, if the criteria are met for CPNAD to append the CPN Incoming Call Module-1 Module and for AMANI to append the CPN Incoming Calls Module-2 Module to the same AMA record, only the CPN Incoming Calls Module-1 Module will be appended since CPNAD takes precedence over AMANI.
17-4
Issue 27
May 2004
18
18-1 18-1 18-2 18-2 18-2 18-2 18-2 18-2 18-3 18-3 18-3 18-3 18-3 18-4 18-5 18-6 18-6 18-6 18-6 18-6 18-6
Introduction For Further Information Feature Descriptions

Introduction What is the CNIPR Capability? What Does the CPNAD Feature Do? What Does the CNIP Feature Do? What Does the CNIR Feature Do? Introduction CPN Incoming Calls Module-1 Module CPN Incoming Calls Module-2 Module CPN Outgoing Calls Module Module Generation Criteria for CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module Module Generation Criteria for CPN Outgoing Calls Module Introduction Four Fields Generate CPN Outgoing Calls AMA Module Field Generate CPN Incoming Calls AMA Module Field DISPLAY ALLOWED/RESTRICTED CPN Fields
AMA Impact

ecp Form

Issue 27
May 2004
18-i
401-610-133A
Feature Interaction

18-8 18-8 18-8
With AMANI Feature (for the CPNAD Feature) With Call Forwarding and Call Waiting
18-ii
Issue 27
May 2004
18
Introduction
This chapter introduces the Calling Number Identification Presentation and Restriction (CNIPR) capability. This chapter describes how AMA functionality is affected by CNIPR and also summarizes feature interactions of the CNIPR features with other features.

More detailed information about this feature can be found in 401-612-006, Calling Number Identification Presentation and Restriction Optional Feature.
Issue 27
May 2004
18-1
401-610-133A
Feature Descriptions
Introduction
This section describes the CNIPR capability and its three features.
What is the CNIPR Capability?

The CNIPR capability provides a subscriber (mobile or land subscriber) with the ability to view a caller's directory number on the mobile unit display. The CNIPR capability consists of three features:

CPN Acceptance/Delivery (CPNAD) feature Calling Number Identification Presentation (CNIP) feature Calling Number Identification Restriction (CNIR) feature.
The CPNAD and CNIP features are Feature Activation File controlled. The CNIR feature comes automatically with the purchase of the CPNAD feature.
What Does the CPNAD Feature Do?

The CPNAD feature allows the MSC to convey CPN information with outgoing calls routed by the MSC and to accept CPN information received with incoming calls to the MSC.
What Does the CNIP Feature Do?

The CNIP feature displays the CPN for subscribers with the display option when they are alerted for incoming calls if the CPN is available and display is allowed.
What Does the CNIR Feature Do?

The CNIR feature allows service providers to prevent the display of a given mobile subscriber's CPN at the called party's phone, by making the appropriate entry in the subscriber's data base. On a per-call basis, mobile subscribers can also allow (or prevent) displaying their CPN at the called party's phone by dialing the CNIP (or the CNIR) feature access code prior to dialing the called number.
18-2
Issue 27
May 2004
AMA Impact
Introduction
The CNIPR Capability enhances AMA functionality by adding three modules that can be appended to existing AMA records. This section describes the following three modules that are used by the CNIPR capability:

The CPN Incoming Calls Module-1 Module The CPN Incoming Calls Module-2 Module The CPN Outgoing Calls Module.
CPN Incoming Calls Module-1 Module

The CPN Incoming Calls Module-1 Module contains the Disposition of CPN/Calling Name Information field (see AMASE Table 477 on page 4-73). For more about this module, go to Modules 330 and 331CPN Incoming Calls Modules on page 5-28.
CPN Incoming Calls Module-2 Module

The CPN Incoming Calls Module-2 Module contains the following:

The Disposition of CPN/Calling Name Information field The Number of Significant Digits in Multiple Field(s) field (see Meaning for CPN Digits on page 4-44) The CPN Digits 1 through 11 field (see Calling Party Number Digits 1 Through 11 Field on page 4-58) The CPN Digits 12 through 20 field (see Calling Party Number Digits 12 Through 20 on page 4-59).
CPN digits are the directory number digits of the calling party. For more about this module, go to Modules 330 and 331CPN Incoming Calls Modules on page 5-28.
CPN Outgoing Calls Module

The CPN Outgoing Calls Module contains the following fields:
Issue 27
May 2004
18-3
401-610-133A
Per-Call CPN/Calling Name Enable and Restriction Usage field. The Per-Call CPN/Calling Name Enable and Restriction Usage field indicates whether the mobile subscriber has dialed the CNIP or the CNIR feature access code prior to dialing the called number. For more about this field see AMASE Table 476 on page 4-71, and AMASE Table 477 on page 4-73.
The Disposition of CPN/Calling Name Information field. The Disposition of CPN/Calling Name Information field indicates whether the CPN digits may be displayed to the called party, whether the CPN digits have been sent to the mobile unit for display, and whether the CPN information has been conveyed to another DCS. In the CPN Outgoing Calls Module, the last two subfields in the Disposition of CPN/Calling Name Information field is marked as n/a. For more about this field see AMASE Table 477 on page 4-73.
For more about this module, go to Module 329CPN Outgoing Calls Module on page 5-27.
Module Generation Criteria for CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module
The CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module will be appended to AMA records with structure codes x2331, x2334, x2335 and x2351, if all of the following conditions are true:

The 5ESS Switch SS7 Call Signaling feature is activated. The CPNAD feature is activated. The CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module is activated via ecp RC/V. The CPN digits are received.
NOTE: To append the structure code x2351, the Append Specific AMA Modules to Structure Code x2351 FAF must be on. The CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module is appended to AMA records with structure codes x2329, x2330, x2332 and x2333 if all of the following conditions are true:

The 5ESS Switch SS7 Call Signaling feature is activated. The CPNAD feature is activated. The CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module is activated via RC/V.
18-4
Issue 27
May 2004
The CPN digits are received. The call has one of the following custom calling features: call forwarding, call delivery to call waiting, or special cellular networking (that is, with service feature codes 012, 014, 055, 083, or 100 as listed in AMASE Table 2002 on page 4-119).
Module Generation Criteria for CPN Outgoing Calls Module

The CPN Outgoing Calls Module is appended to the existing AMA record for structure codes x2329, x2330, x2332, and x2333 if the following conditions are true:
The Calling Party Number Acceptance/Delivery feature is active in the Feature Activation File. The CPN Outgoing Calls Module is turned on in the ecp RC/V form. The Calling Party Number was delivered.
Issue 27
May 2004
18-5
401-610-133A
ecp Form
Introduction
This section describes how to use the ecp form to allow/disable the generation of the CNIPR-related modules.
Four Fields
The following four fields on the ecp form are used to allow/disable the generation of the CPN Incoming Calls Module-1 Module, the CPN Incoming Calls Module-2 Module, and the CPN Outgoing Calls Module fields via RC/V:

Generate CPN Outgoing Calls AMA Module(s)? Generate CPN Incoming Calls AMA Module(s)? Include DISPLAY ALLOWED CPN? Include DISPLAY RESTRICTED CPN?
These fields can be set to either y (yes) or n (no) to either allow or disable the generation of the related modules.
Generate CPN Outgoing Calls AMA Module Field

If the Generate CPN Outgoing Calls AMA Module(s)? field is set to y, the CPN Outgoing Calls Module is turned on. Otherwise the module is off.
Generate CPN Incoming Calls AMA Module Field

When the Generate CPN Incoming Calls AMA Module(s)? field is set to n both CPN Incoming Calls Module-1 and Module-2 are disabled.
DISPLAY ALLOWED/RESTRICTED CPN Fields

When the Generate CPN Incoming Calls AMA Module(s)? field is set to y, the status of the CPN Incoming Call Modules depends on the values set for the Include DISPLAY ALLOWED/RESTRICTED CPN fields.
18-6
Issue 27
May 2004
All four combinations for the ecp form fields associated with the CPN Incoming Calls (Module-1, and Module-2) Modules are summarized below. Table 18-1.
ecp Form CPN Incoming Calls Module Fields Entries Summary
Fields on the ecp form Generate CPN Incoming Calls Module(s)? n Include DISPLAY ALLOWED CPN? y/n Include DISPLAY RESTRICTED CPN? y/n Status of the CPN Incoming Calls Modules (modules Module-1 and Module-2) Neither the CPN Incoming Calls Module-1 Module nor the CPN Incoming Calls Module-2 Module will be generated. CPN Incoming Calls Module-1 Module can be generated. CPN Incoming Calls Module-2 Module will not be generated. y y n CPN Incoming Calls Module-1 Module can be generated if CPN digits are not allowed to be displayed on the called partys phone. CPN Incoming Calls Module-2 Module can be generated if CPN digits are allowed to be displayed on the called partys phone. y y y CPN Incoming Calls Module-1 Module will not be generated. CPN Incoming Calls Module-2 Module can be generated
y/n
Issue 27
May 2004
18-7
401-610-133A
Feature Interaction
With AMANI Feature (for the CPNAD Feature)
Both the CPNAD and AMANI features can append CPN Incoming Calls Modules (either Module-1 or Module-2) to an AMA record. However, only one CPN Incoming Calls Module can be appended to any given AMA record. CPNAD will take precedence over AMANI in deciding which CPN Incoming Calls Module to append. For example, if the criteria are met for CPNAD to append the CPN Incoming Call Module-1 Module and for AMANI to append the CPN Incoming Calls Module-2 Module to the same AMA record, only the CPN Incoming Calls Module-1 Module will be appended since CPNAD takes precedence over AMANI.
With Call Forwarding and Call Waiting

This feature also interacts with Call Forwarding and with Call Waiting features. For a description of these interactions, read 401-612-006, Calling Number Identification Presentation and Restriction Optional Feature.
18-8
Issue 27
May 2004
LSA Features
19
19-1 19-1 19-2 19-2 19-2 19-2 19-2 19-2 19-3 19-3 19-3 19-4 19-4 19-4 19-4 19-4 19-4 19-5 19-5 19-5 19-5 19-5

Introduction What is a Limited Service Area? What is the LSA Feature? What is the LSA128 Feature? Billing Levels Used with the LSA 128 Feature What is the Inter-DCS LSA Feature? What is the Inter-MSC LSA Feature? What is the Silent Administration of LSA (SALSA) Feature? Introduction Aggregate LSA Information Module Generation Criteria for Aggregate LSA Information Module Special Case in Which LSA Modules Are Not Generated For Further Information Introduction LSA Status Contents of LSAET Field Voice-Channel Usage Segment Value
AMA Impact for All LSA Features

AMA Impact on LSA in Cases of 3-Port Calls

Issue 27
May 2004
19-i
401-610-133A
Digital Voice-Channel Usage Segment Value Introduction Aggregate LSA Module Introduction AMA Impact for the IDLSA Feature AMA Impact for the IMLSA Feature Handling of Elapsed Time Expansion of LSA Indicator Field Introduction Activation Criteria Older LSA Billing Fields Have Not Changed Treatment of Elapsed Time Rules for Interacting with MSCs That Do Not Have the LSA128 Feature
19-6 19-7 19-7 19-7 19-8 19-8 19-8 19-8 19-8 19-8 19-10 19-10 19-10 19-10 19-10 19-10 19-11 19-11 19-11 19-12
AMA Impact of the Limited Service Area (LSA) Feature

AMA Impact for the IDLSA and IMLSA Features

AMA Impact for the LSA 128 Feature

AMA Impact for the Silent Administration of LSA (SALSA) Feature

Introduction Special Feature Activation/Deactivation Record
19-ii
Issue 27
May 2004
LSA Features
19
Introduction
This chapter provides information on Limited Service Area (LSA) features and describes how AMA functionality is affected by these features. This chapter also summarizes feature interactions of the LSA features with other features.

For more information about all the LSA features, read the Limited Service Area Optional Feature (401-601-030).
Issue 27
May 2004
19-1
401-610-133A
Feature Description
Introduction
This section defines the term Limited Service Area and lists and describes the LSA features.
What is a Limited Service Area?

A Limited Service Area is a special physical area defined by a service provider. For mobile-originated calls started within this area, subscribers are usually billed at a different rate than for other calls. A given LSA may be as small as one cell face or as large as the entire service coverage area. LSAs may overlap one another, and all cells (or cell faces) do not have to be contiguous with one another. A cell site (or cell face) may be in more than one LSA.
What is the LSA Feature?

The Limited Service Area (LSA) feature allows the service provider to identify a small set of Limited Service Areas within its coverage area and set up a maximum of one different subscriber billing level for LSAs. If the LSA128 feature is inactive and the LSA feature is active, then up to 24 LSAs may be defined with only one LSA billing level possible. The billing rate for this billing level will be a level three billing rate (the most highly-discounted rate). See the description of the LSA128 feature for a discussion of the levels of billing rates.
What is the LSA128 Feature?

The LSA128 feature allows the service provider to identify up to 128 Limited Service Areas (LSAs) in its service coverage area and a maximum of three different billing levels. To activate this feature, a Feature Activation File (FAF) must be installed on the ECP with both the LSA128 and LSA features marked active.
Billing Levels Used with the LSA 128 Feature

If the LSA 128 feature is active, the service provider can define a maximum of three different billing levels for LSA calls. A given LSA can be assigned to any billing level per subscriber. The current billing levels are defined as follows:
19-2
Issue 27
May 2004
LSA Features
Billing level 3most highly discounted rate Billing level 2next highest discounted rate Billing level 1least discounted rate Billing level 0indicates not in any LSA
What is the Inter-DCS LSA Feature?

The IDLSA feature allows LSA boundaries to be defined across multiple DCSs within an MSC.
What is the Inter-MSC LSA Feature?

The IMLSA feature allows LSA boundaries to be defined across multiple MSCs.
What is the Silent Administration of LSA (SALSA) Feature?

The SALSA feature permits the subscriber to allow/disallow the LSA tone that is normally generated whenever the subscriber initially leaves the LSA or originates/ receives a call outside the LSA. The LSA tone is allowed or inhibited through a feature activation/deactivation code dialed by the subscriber.
Issue 27
May 2004
19-3
401-610-133A
AMA Impact for All LSA Features

Introduction
All the LSA features share one common module. This section describes the LSA module.
Aggregate LSA Information Module

The LSA feature requires a module: the Aggregate LSA Information Module. This module is needed to supply the LSA Number field (containing the last LSA zone number that the cellular subscriber was in), which is not available in AMA records. NOTE: This module also contains the LSA Indicator and LSA Elapsed Time fields. These fields contain information already available in the cellular originated and cellular terminated AMA records.
Generation Criteria for Aggregate LSA Information Module

The Aggregate LSA Information Module may be appended to all cellular originated and cellular terminated structure codes to provide this information if:

The LSA feature(s) is/are turned on. The ecp database form indicates that generation of this module is allowed. The subscriber has the LSA feature privilege.
Special Case in Which LSA Modules Are Not Generated

LSA modules are not appended to AMA records having an LSA Elapsed Time of zero.

For further information about the LSA Module, read Module 333Aggregate LSA Information Module on page 5-32.
19-4
Issue 27
May 2004
LSA Features
AMA Impact on LSA in Cases of 3-Port Calls

Introduction
This section describes changes that can occur to LSA records in cases involving three-port calls.
LSA Status
The LSA status of a three-port call is based on the state of the original leg of the call at the time the three-port call starts. As a result, the Initial Radio Number and Cell Site field of the third party billing record may display a valid LSA cell site while the value in the LSA Indicator field is zero. Refer to AMASE Table 2003 on page 4-124 and Limited Service Area (LSA) Indicator Field on page 4-45.
Contents of LSAET Field

For 3-port calls, the LSAET field contains both the analog and the digital portion of the elapsed time. The Digital LSAET field contains the digital portion of the LSAET field. The LSAET field is evaluated from the time of dropback (that is, three-way transition time) rather than from the seizure time. As a result, if an LSA transition hand off (that is, change of state) occurs at or prior to dropback, then the LSAET is set to zero, and the LSA Indicator is also set to zero. If the transition handoff occurs after dropback, then the LSAET is greater than zero, and the LSA Indicator is set to 1. Refer to LSA Elapsed Time Field on page 4-25.
Voice-Channel Usage Segment Value

The voice-channel usage segment (both analog and digital) for the three-port leg of an LSA call that is independent of the original leg equals the Voice-Channel Elapsed Time minus the Three-Way Transition Elapsed Time (VCET minus TWTET) for three-port calls, in general, and is composed of two parts. The duration of the first part is equal to the LSAET. The duration of the second part is equal to the difference of the independent voice-channel segment with the LSAET, or (VCET - TWTET) - LSAET.
Issue 27
May 2004
19-5
401-610-133A
Digital Voice-Channel Usage Segment Value

Similarly, the digital voice-channel usage segment for the three-port leg of an LSA call that is independent of the original leg equals the Digital VoiceChannel Elapsed Time minus the Digital Three-Way Elapsed Time (Digital VCET minus Digital TWTET) for three-port calls. It is composed of two parts. The duration of the first part is equal to the Digital LSAET. The duration of the second part is equal to the difference of the independent Digital Voice-channel segment with the digital LSAET, or (digital VCET minus digital TWTET) minus digital LSAET.
19-6
Issue 27
May 2004
LSA Features
AMA Impact of the Limited Service Area (LSA) Feature

Introduction
This section describes AMA impact for the basic LSA feature.
Aggregate LSA Module

All LSA feature usage is stored in the LSA Module. For more about the Aggregate LSA Module, see Module 333Aggregate LSA Information Module on page 5-32.
Issue 27
May 2004
19-7
401-610-133A
AMA Impact for the IDLSA and IMLSA Features

Introduction
Both the IDLSA and IMLSA features expand upon the current LSA feature. Both features provide the following expanded AMA functionality defined in this section.
AMA Impact for the IDLSA Feature

The IDLSA feature allows LSA boundaries to be defined across multiple DCSs within an MSC. For example, if the subscriber performs a handoff to another DCS, but remains within the LSA, LSA information (including the LSA Elapsed Time stored in the CPS AMA record) will continue to be accumulated for that subscriber.
AMA Impact for the IMLSA Feature

The IMLSA feature allows LSA boundaries to be defined across multiple MSCs. Therefore, the example given above for the IDLSA feature also applies to this case in the event that the subscriber performs a handoff to another MSC.
Handling of Elapsed Time

For both features, the LSA elapsed time is cumulative. Prior to the introduction of the IDLSA and IMLSA features, LSA Elapsed Time would be calculated and stored in the AMA record whenever the subscriber left the LSA (with no further adjustments to the LSA Elapsed Time, even if the subscriber re-entered the LSA). The IDLSA and IMLSA features automatically begin accumulation of additional LSA Elapsed Time, should the subscriber re-enter the LSA. (This includes intraDCS, inter-DCS and inter-MSC handoff cases.) The digital LSA Elapsed Time is also cumulative in the same manner.
Expansion of LSA Indicator Field

For both these features, the LSA Indicator field has been expanded to display the following information about the subscriber (if applicable):

The subscriber does not have the LSA feature privilege. The subscriber does have the LSA feature active, but no LSA elapsed time was recorded since the call was completely outside the subscribers LSA.
19-8
Issue 27
May 2004
LSA Features
The subscriber does have the LSA feature active, and LSA Elapsed Time was recorded since the call was either partially or completely inside the subscribers LSA.
NOTE: LSA128 expands the use of the LSA Indicator field. See AMA Impact for the LSA 128 Feature on page 19-10. For both features, the LSA Indicator and LSA Elapsed Time will be stored in the Control Point Switch and CN Slave Switch AMA records. The CN Handback AMA record will not contain LSA information.
Issue 27
May 2004
19-9
401-610-133A
AMA Impact for the LSA 128 Feature

Introduction
This section describes AMA impact for the LSA 128 feature.
Activation Criteria
To activate this feature, a Feature Activation File (FAF) must be installed on the ECP with both the LSA128 and LSA features marked active. If the LSA128 feature is inactive and the LSA feature is active, then up to 24 LSAs may be defined with only one LSA billing level possible (level 3).
Older LSA Billing Fields Have Not Changed

For backward compatibility, the following LSA Billing fields will continue to be formatted in AMA records with no change in meaning or usage:
LSA Elapsed Time fieldrepresents total LSA elapsed time (based on the LSA Indicator field) LSA Indicator fieldrepresents the overall status of LSA feature usage for the call.
Treatment of Elapsed Time

Total LSA Elapsed Time for CN inter-switch terminations (structure code x2335) will be formatted in addition to formatting individual Aggregate LSA Information Modules appended to the AMA record per LSA billing level. Total Digital LSA Elapsed Time will not be formatted. Instead, individual Auxiliary Time Modules will be appended to the AMA record per LSA billing level.
Rules for Interacting with MSCs That Do Not Have the LSA128 Feature
For LSA compatibility with MSCs that do not have the LSA128 feature active, when LSA information is received from a non-LSA128 compatible MSC, the first eight LSAs sequentially defined (in the 24 LSA bit-map) will be used for Visitor Location Register/Home Location Register(VLR/HLR) compatibility. Those LSAs will be given a billing level of three. In the reverse case, when sending LSA data to an MSC that is non-LSA128 compatible, those LSAs with a value of 24 or less, regardless of billing level, will be populated in the 24-bit bitmap.
19-10
Issue 27
May 2004
LSA Features
AMA Impact for the Silent Administration of LSA (SALSA) Feature

Introduction
This section describes AMA impact for the Silent Administration of LSA (SALSA) feature.
Special Feature Activation/Deactivation Record

This action generates a Feature Activation/Deactivation AMA record (structure x2411) with a field value of 021 indicating the SALSA feature (see Table 4-70 on page 4-119).
Issue 27
May 2004
19-11
401-610-133A
The LSA features have many interactions with other features. For a complete list of these, read the Limited Service Area Optional Feature (401-601-030).
19-12
Issue 27
May 2004
20
20-1 20-1 20-2 20-2 20-2 20-2 20-3 20-3 20-3

Introduction What is the Voice Privacy Feature? Voice Privacy Capability for Service Providers Introduction Type of Technology Field
AMA Impact

Issue 27
May 2004
20-i
401-610-133A
20-ii
Issue 27
May 2004
20
Introduction
Voice privacy provides security for cellular communications by encrypting the voice path between the mobile and the cell. This chapter describes the voice privacy feature and explains the features impact on AMA records.

For more information about this feature, read the Voice Privacy Optional Feature (401-612-046).
Issue 27
May 2004
20-1
401-610-133A
Feature Description
Introduction
This section describes how the Voice Privacy feature works.
What is the Voice Privacy Feature?

Voice privacy provides security for cellular communications by encrypting the voice path between the mobile and the cell.
Voice Privacy Capability for Service Providers

The Voice Privacy feature enables the service provider to do the following:
Include a yes/no indication of whether or not voice privacy was active at any time during the call Include a yes/no indication of whether or not voice privacy was ever autonomously removed from the call by the serving MSC, on calls during which voice privacy was active, without the subscriber indicating that voice privacy should be removed.
20-2
Issue 27
May 2004
AMA Impact
Introduction
This section describes AMASE Table 471, which used by the Voice Privacy feature.
Type of Technology Field

The first BCD character in the Type of Technology field (see Table 4-39 on page 4-62) is used to record the voice privacy usage.
Issue 27
May 2004
20-3
401-610-133A
20-4
Issue 27
May 2004
21
21-1 21-1 21-2 21-2 21-2 21-3 21-3 21-3 21-3 21-3 21-4

Introduction What is the Initial Cell-Based Billing Feature? Introduction Fields Module Generation Criteria For Further Information
AMA Impact

Issue 27
May 2004
21-i
401-610-133A
21-ii
Issue 27
May 2004
21
Introduction
This chapter introduces the Initial Cell-Based Billing feature and describes how AMA functionality is affected using the Cell Information Module.

More detailed information about this feature can be found in the document Initial Cell-Based Billing Optional Feature (401-612-111).
Issue 27
May 2004
21-1
401-610-133A
Feature Description
Introduction
This section describes the Initial Cell-Based Billing feature.
What is the Initial Cell-Based Billing Feature?

The Initial Cell-Based Billing feature allows the initial cell site number, radio number and associated Extended System Identification (ESID) that is used at the beginning of a call to be appended to existing AMA call records as an optional AMA module (Cell Information Module - Module Code 622).
21-2
Issue 27
May 2004
AMA Impact
Introduction
The Initial Cell-Based Billing feature affects AMA by adding a module, the Cell Information Module. The rest of this section describes the Cell Information Module.
Fields
The Cell Information Module contains the Radio/Channel Number and Cell Site field (defined by AMASE Table 2003 on page 4-124) and the associated Serving ESID Information field (defined by AMASE Table 379 on page 4-54).
Module Generation Criteria

The Cell Information Module may be appended to structure codes x2329, x2330, x2331, x2332, x2333, x2334, and x2335. This module will be appended to the AMA record if the following conditions are true:

The Initial Cell-Based Billing feature is active in the FAF. The Cell Information Module (y/n) field on ecp form is set to y. The initial cell site number, radio number, and serving ESID for when the call was first set up do not match the initial cell, radio and ESID information of the airtime segment represented in this AMA record (as in the case of an inter-switch handback scenario). The initial cell, radio and ESID information of the airtime segment represented in this AMA record is zero (as in the case of an inter-switch cellular networking call delivery where the serving cell is on a switch other than the control point switch [CPS]).

For more about the Cell Information Module, read Module 622Cell Information Module on page 5-68.
Issue 27
May 2004
21-3
401-610-133A
The Initial Cell-Based Billing feature has no interaction with other features.
21-4
Issue 27
May 2004
Private Numbering Plan (PNP) NonDialable Digits in HLR Return Results Feature
22
22-1 22-1 22-2 22-2 22-2 22-2 22-2 22-3 22-3 22-3 22-3 22-3 22-3 22-4

Introduction What is the PNP Non-Dialable Digits in HLR Return Results Feature? How Does It Work? Benefits Introduction Generic Context Identifier for This Feature Digits String Field Module Generation Criteria for This Feature For Further Information
About the Digit Information Module (Module 621)

Issue 27
May 2004
22-i
401-610-133A
22-ii
Issue 27
May 2004
Private Numbering Plan (PNP) NonDialable Digits in HLR Return Results Feature
22
Introduction
This chapter introduces the PNP Non-Dialable Digits in Home Location Register (HLR) Return Results feature and describes how it affects AMA functionality.

No optional feature document for this feature exists. For more information about this feature, contact Lucent Technologies technical support.
Issue 27
May 2004
22-1
401-610-133A
Feature Description
Introduction
This section describes the PNP Non-Dialable Digits in Home Location Register Return Results feature.
What is the PNP Non-Dialable Digits in HLR Return Results Feature?

The PNP Non-Dialable Digits in HLR Return Results feature enables its users to call other members of their Closed User Group (CUG) by dialing an extension number, usually the last four digits of a users telephone number. The CUG consists of a group of users who share the same numbering plan. CUG users are served by their regions HLR.
How Does It Work?

The number dialed by the CUG user is expanded by the HLR into a digit string which is greater than sixteen digits in length (maximum length is thirty-two digits) and returned to the MSC. The digit string returned by the HLR includes a six or seven non-dialable digit prefix followed by a North American Numbering Plan number. The PNP feature uses the non-dialable hexadecimal digits as a security and routing mechanism. Since the digits are non-dialable, it is assumed that an unauthorized user would be unable to gain access to PNP services. In addition, the non-dialable digits are used to do some routing.
Benefits
This feature allows the MSC equipment to process digit strings containing nondialable hexadecimal digits returned as part of the return result from standalone HLR. This feature also allows the entire digit string, returned as part of the HLR return result (including the non-dialable digits), to be recorded in the Digit Information Module and appended to the AMA record.
22-2
Issue 27
May 2004
About the Digit Information Module (Module 621)

Introduction
This section describes the Digit Information Module as used by the PNP NonDialable Digits in HLR Return Results feature.
Generic Context Identifier for This Feature

The value of the Generic Context Identifier field for this feature is 90000.
Digits String Field

The Digits String field for this feature contains the string of digits dialed by the CUG.
Module Generation Criteria for This Feature

The Digit Information Module will be appended to AMA records with the x2118, x2119, x2329, x2330, x2332, and x2333 structure codes if the following conditions are true:
The Digit Information Module is activated via ecp RC/V for adding DIM for HLR Routing Return Results. The SCP Routing Digits (y/n) field on the ecp form is set to y. The HLR Routing Return Result digit count is non-zero.

For more about the Digit Information Module, read Module 621 - Digit Information Module on page 5-46.
Issue 27
May 2004
22-3
401-610-133A
The PNP Non-Dialable Digits in HLR Return Results feature has no interaction with other features.
22-4
Issue 27
May 2004
23
23-1 23-1 23-2 23-2 23-2 23-2 23-2 23-3 23-3 23-4 23-4 23-4 23-4 23-4 23-4 23-4 23-5 23-6 23-6

Introduction What is the MVC Feature? Benefits MVC Capabilities for the Service Provider Multiple Types of Vocoder Supported Vocoding Algorithms Supported Introduction Fields Module Code Field Event Type Field Event Description Field Relative Event Time Field Module Activation Criteria With the Data Module
AMA Impact

Issue 27
May 2004
23-i
401-610-133A
23-ii
Issue 27
May 2004
23
Introduction
This chapter introduces the Multiple Voice Coding (MVC) feature and describes how AMA functionality is affected using the Digital Event Module (DEM).

For further information on this feature, see the Multiple Vocoding Based FeaturesMVC,EVRC,USON Optional Feature, 401-612-115.
Issue 27
May 2004
23-1
401-610-133A
Feature Description
Introduction
This section describes the MVC feature.
What is the MVC Feature?

The MVC feature allows the Flexent/AUTOPLEX wireless network to support various CDMA voice calls employing different voice coding algorithms. This feature provides a base platform for allowing the service provider to deploy new vocoding algorithms from a set of pre-defined vocoding algorithms and to modify the rules for which voice services are offered to subscribers. This feature should be viewed as independent of any and all voice coding algorithms and voice coders.
Benefits
The MVC feature provides the following benefits to service providers and subscribers:
Maximizes utilization of vocoder types by allowing configuration of resources Provides a base platform to simplify future expansion for additional CDMA vocoder types Accommodates mobile phones in a single service area using differing vocoder service options and negotiation types Reduces CDMA call rejection rate by service negotiation for alternate vocoding algorithms and by analog redirection if vocoder resources are unavailable
MVC Capabilities for the Service Provider

The MVC feature gives the service provider the ability to:

Alter the supported vocoding algorithms per ECP Designate the type of voice service offered to the mobile depending on the CDMA call request Specify whether or not a call request will be redirected to analog if CDMA vocoder resources are busy
23-2
Issue 27
May 2004
Select a preferred vocoding algorithm for mobile page messages Bill subscriber calls according to vocoder type used (it is assumed the vocoder type will not change during a call)
Multiple Types of Vocoder Supported

The 5ESS Switch will support multiple vocoder types on the same switch.
Vocoding Algorithms Supported

The MVC feature supports the following CDMA vocoding algorithms:

8K Voice 8K Markov 8K Mobile Loopback Test 9.6K Async Data 9.6K Fax 13K Voice 13K Markov 13K Mobile Loopback Test 14.4K Async Data 14.4K Fax EVRC 8K Voice
Issue 27
May 2004
23-3
401-610-133A
AMA Impact
Introduction
The Multiple Voice Coding AMA capability enables the service provider to bill usage of various voice coding algorithms differently through use of the Digital Event Module. This section describes the Digital Event Module.
Fields
The Digital Event Module (Module 334) contains the following fields:

Module Code Event Type Event Description Relative Event Time.
Module Code Field

The Module Code field identifies the type of module that is appended to the existing AMA record.
Event Type Field

The Event Type field signifies mutually exclusive events. The following event type is applicable for the MVC feature:
002 = Initial CDMA Assigned Service Option.
Event Description Field

The corresponding Event Description field (Table 4-46 on page 4-76) indicates the Initial CDMA Assigned Service Option with values ranging from 00001 to 99999.
Relative Event Time Field

The Relative Event Time is the elapsed time between the event and the beginning of the call. Note that for event type 002, the Relative Event Time field is filled with zeroes.
23-4
Issue 27
May 2004
For more information about the DEM fields and their associated AMASE Tables, see Module 334Digital Event Module on 5-34.
Module Activation Criteria

The Digital Event Module will be appended to AMA records with the x2329-x2335 structure codes if the following conditions are true:

The MVC feature is active in the Feature Activation File. The The ecp database field for Append Digital Event Module to the AMA Record? is set to y.
Issue 27
May 2004
23-5
401-610-133A
With the Data Module
For software releases ECP R11.0 and later, a Data Module may take the place of the Digital Event Module that records the Initial CDMA Assigned Service Option. If the Data Module is appended, the Digital Event Module that records the Initial CDMA Assigned Service Option will not appear. The Data Module is used by the Circuit-Mode Data Services feature. For more about the Data Module and the Circuit-Mode Data Services feature, see Chapter 25, CDMA Circuit-Mode Data Services Feature.
23-6
Issue 27
May 2004
24
24-1 24-2 24-2 24-2 24-3 24-3 24-3 24-3 24-3 24-3 24-5 24-5 24-5 24-5 24-6 24-6 24-7 24-7 24-7
Introduction For Further Information
For Information about the DCCH Non-Public Network Identifiers and Non-Public Network Identifiers-Analog Features For Information About the CDMA Private Network and User Zone Feature Introduction What is a Non-Public Network? Identifiers for the Non-Public Networks What is a User Zone? Benefits of User Zones Feature Descriptions Introduction For Information about the DCCH Non-Public Network Identifiers and Non-Public Network Identifiers-Analog Features For Information About the CDMA Private Network and User Zone Feature Activation/Deactivation of User Zone Tone Introduction Fields
About User Zones

AMA Impact
TDMA and Analog Implementation of the User Zone Module

Issue 27
May 2004
24-i
401-610-133A
Module Code Field User Zone Information Field User Zone Sequence Number User Zone ID Type User Zone ID User Zone Elapsed Time Field Module Generation Criteria For Further Information Introduction Charge Recording Data and the User Zone Module Call that Starts and Registers on the Public System Call that Starts on the Public System after Registration in a User Zone Call that Starts in a User Zone and Moves to a Public System Call that Starts in a User Zone and Moves to Another User Zone Introduction Public System As a User Zone Fields Module Code Field User Zone Information Field User Zone Sequence Number User Zone ID Type User Zone ID User Zone Elapsed Time Field Module Generation Criteria For Further Information Introduction Charge Recording and the User Zone Module Call That Starts and Ends in One User Zone Call that Moves into Other User Zones Call that Continues Past Four Handoffs For all Features (To Get the Auxiliary Time Module) For Other Feature Interactions
24-7 24-7 24-7 24-8 24-8 24-8 24-8 24-9 24-10 24-10 24-10 24-10 24-10 24-11 24-11 24-12 24-12 24-12 24-12 24-12 24-12 24-13 24-13 24-13 24-13 24-14 24-14 24-15 24-15 24-15 24-15 24-15 24-15 24-16 24-16 24-16
User Zone Module Generation Rules for TDMA and Analog

CDMA Implementation of the User Zone Module

User Zone Module Generation Rules for CDMA


24-ii
Issue 27
May 2004
24
Introduction
The User Zone capability allows the service provider to distinguish public network system elapsed time from non-public network system elapsed time, allowing the two systems to be billed at different rates. The following three different features provide this capability for TDMA, AMPS and CDMA:

DCCH Non-Public Network Identifiers feature - for TDMA1 Non-Public Network Identifiers-Analog feature - for Analog CDMA Private Network and User Zone feature - for CDMA
This chapter provides information on these three features and describes how they affect AMA functionality. This chapter also summarizes feature interactions of these three features with other features.
This requires TDMA cells that are DCCH-capable.
Issue 27
May 2004
24-1
401-610-133A

For Information about the DCCH Non-Public Network Identifiers and Non-Public Network Identifiers-Analog Features
For more detailed information about the DCCH Non-Public Network Identifiers feature and Non-Public Network Identifiers-Analog features, read 401-612-126, IS-136 Non-Public Network Identifiers and Charging Areas Optional Feature.
For Information About the CDMA Private Network and User Zone Feature
For more detailed information about the CDMA Private Network and User Zone Feature, read 401-612-182, CDMA Private Network and User Zone Optional Feature.
24-2
Issue 27
May 2004
About User Zones

Introduction
This section defines non-public networks and the concept of the User Zone. It also lists the benefits of the User Zone capability.
What is a Non-Public Network?

A non-public network is a part of a service providers service area that can provide special services to a limited group of subscribers. A non-public network typically provides different features and different billing rates than a public network, even if the two networks share the same geographic area or the same service provider.
Identifiers for the Non-Public Networks

In analog and TDMA usage, non-public networks are known as private or residential systems. In CDMA usage, non-public networks are known as private networks. In TDMA and analog systems, a private system is known by an identifier, called the Private System Identifier (PSID) or Residential System Identifier (RSID). In CDMA systems, this private system identifier is called the System Identifier (SID)/ Network Identifier (NID).
What is a User Zone?

User Zones are geographical areas defined by service providers by SID/NID. User Zones allow service providers to logically group a set of subscribers and to provide them with unique billing arrangements and special services.
Benefits of User Zones

When the User Zone capability is in effect, a business customer can get preferential rates for calls made by employees from their work locations (within a pre-defined User Zone). The special rates, however, will not apply for any calls made from outside the business location (User Zone), even though the same mobile unit is used. Thus, both the business customers and their employees get appropriate billing treatment (whether for business or non-business use) using a single phone and a single Directory Number (DN).
Issue 27
May 2004
24-3
401-610-133A
An individual subscriber can then use the same mobile unit at work and at home, and does not have to switch mobile units to keep personal and business calls separate. These benefits promote the following:

Ease of use for end users Reduced cost for business customers Increased revenue for the service provider
24-4
Issue 27
May 2004
Introduction
These features are complex and are implemented differently for the three different technologies. These features are best learned about by reading the entire optional feature documents for them.
For Information about the DCCH Non-Public Network Identifiers and Non-Public Network Identifiers-Analog Features
For more detailed information about the DCCH Non-Public Network Identifiers feature and Non-Public Network Identifiers-Analog features, read 401-612-126, IS-136 Non-Public Network Identifiers and Charging Areas Optional Feature.
For Information About the CDMA Private Network and User Zone Feature
For more detailed information about the CDMA Private Network and User Zone Feature, read 401-612-182, CDMA Private Network and User Zone Optional Feature.
Issue 27
May 2004
24-5
401-610-133A
AMA Impact
The User Zone capability has two major two AMA Impacts:

Generation of an AMA record for activation/deactivation of User Zone tone Use of User Zone Module.
Activation/Deactivation of User Zone Tone

An AMA record with a structure code of x2411 is generated when activation/ deactivation of User Zone tone is received. The mobile subscriber may wish to disable any User Zone tone from being played in a call. This can be done by dialing the appropriate *xy code. User Zone tone may be re-enabled through a different *xy code.
24-6
Issue 27
May 2004
TDMA and Analog Implementation of the User Zone Module

Introduction
The TDMA DCCH Non-Public Network Identifiers feature and the Non-Public Network Identifiers-Analog feature allow the service provider to add User Zone information and User Zone elapsed time to existing AMA records by appending up to two User Zone Modules. This section summarizes the TDMA and analog use of the User Zone module.
Fields
The User Zone Module contains the following fields:

Module Code User Zone Information User Zone Elapsed Time.
Module Code Field

User Zone Information Field

The User Zone Information field includes the following:

User Zone Sequence Number User Zone ID Type User Zone ID
User Zone Sequence Number

For TDMA and analog systems, the User Zone Sequence Number is either 1 or 2. User Zone Sequence Number 1 indicates that the mobile subscriber started the call on this User Zone. User Zone Sequence Number 2 indicates that the mobile subscriber started the call on the public system or on a different User Zone before changing to the current User Zone.
Issue 27
May 2004
24-7
401-610-133A
User Zone ID Type

The User Zone ID Type is either 0 or 1. 0 indicates a private system. 1 indicates a residential system.
User Zone ID
The User Zone ID is the ID of the User Zone.
User Zone Elapsed Time Field

The User Zone Elapsed Time is the total (analog plus digital) elapsed time that the mobile subscriber stays in that User Zone. If the service provider is interested in the digital portion of the User Zone Elapsed Time, the Auxiliary Time Module can be used to store the User Zone Digital Elapsed Time. NOTE: The ADUB feature needs to be on in order to turn on the Auxiliary Time Module via RC/V. Two more time types were added to the Time Type field (AMASE Table 473) of the Auxiliary Time Module to support the User Zone capability.

010Digital User Zone Sequence Number 1 elapsed time. 011Digital User Zone Sequence Number 2 elapsed time.

The User Zone Module will be appended to AMA records for TDMA or Analog calls with the x2329-x2335 structure codes if the following conditions are true:
Either the DCCH Non-Public Network Identifiers feature or the Non-Public Network Identifiers-Analog feature is active in the FAF. The ecp Form field for Append User Zone Module to the AMA Record is set to y. The User Zone Sequence Number 1 or Sequence Number 2 is of nonpublic type. The User Zone Sequence Number 1 or Sequence Number 2 Elapsed Time field has a non-zero value.
NOTE: The ADUB feature must be active in the FAF and the Auxiliary Time Module turned on via RC/V so the Digital User Zone Elapsed Time Sequence Number 1 or
24-8
Issue 27
May 2004
Sequence Number 2 can be collected in the Auxiliary Time Module and appended to an existing AMA record.

For more about the User Zone Module, read Module 336User Zone Module on page 5-36.
Issue 27
May 2004
24-9
401-610-133A
User Zone Module Generation Rules for TDMA and Analog

Introduction
This section gives rules for when User Zone Modules for TDMA or analog are generated, depending upon where a call starts and where it ends. These rules only apply to the TDMA and analog calls.
Charge Recording Data and the User Zone Module

Charge recording data will contain User Zone information for up to two User Zones per call. If a call remains entirely in the public system, no User Zone Module will be appended.
Call that Starts and Registers on the Public System

If the mobile subscriber registers on the public system, starts a call on the public system and later moves to User Zone X, then no User Zone Module will be appended for User Zone X. It is assumed that the intent of the mobile subscriber is to remain in the public system for the duration of the call.
Call that Starts on the Public System after Registration in a User Zone
If the mobile subscriber registers in a User Zone, moves to an area without any subscriber User Zones and then starts a call without a new registration, then the call will initially be billed to the public system. A subsequent handoff to a User Zone will cause a User Zone Module to be appended. The User Zone elapsed time is the elapsed time from the time that the mobile subscriber changes to User Zone X until the end of the call, even if the mobile subscriber later hands off into different User Zones or the public system. In other words, any handoff into a second, third, or more User Zone or into the public system shall continue to be recorded in the elapsed time field for User Zone X and will not be differentiated in that data.
24-10
Issue 27
May 2004
Call that Starts in a User Zone and Moves to a Public System

If the mobile subscriber starts the call in User Zone Y and later changes to the public system, only one User Zone Module will be appended for User Zone Y. The User Zone Elapsed Time is the elapsed time that the mobile subscriber was in User Zone Y. Any subsequent hand off after the public system will not be recorded in the charge recording data.
Call that Starts in a User Zone and Moves to Another User Zone
If the mobile subscriber starts the call in User Zone X and later changes to User Zone Y, two User Zone Modules will be appended: one for the time spent in User Zone X and one for the time spent in User Zone Y. The User Zone elapsed time for the User Zone Y is from the time the mobile subscriber changes to User Zone Y until the end of the call. If the mobile subscriber later moves from User Zone Y to different User Zones, or into the public system, elapsed time in these User Zones or public system is included in the User Zone elapsed time of User Zone Y.
Issue 27
May 2004
24-11
401-610-133A
CDMA Implementation of the User Zone Module

Introduction
The CDMA Private Network and User Zone feature allows the service provider to add User Zone information and User Zone elapsed time to existing AMA records by appending one to four User Zone Modules. This section summarizes the use of the User Zone module for CDMA.
Public System As a User Zone

In the CDMA Private Network and User Zone feature, the Public System is treated as a User Zone with a User Zone ID of 0.
Fields
The User Zone Module contains the following fields:

User Zone Information User Zone Elapsed Time.
Module Code Field

User Zone Information Field

The User Zone Information field includes the following:

User Zone Sequence Number User Zone ID Type User Zone ID
24-12
Issue 27
May 2004
User Zone Sequence Number

The User Zone Sequence Number for CDMA can have one of the following four values:
1 - Indicates that the mobile subscriber started the call on this User Zone 2 - Indicates the second User Zone of the current call 3 - Indicates the third User Zone of the current call 4 - Indicates the fourth User Zone of the current call
User Zone ID Type

The User Zone ID Type is either 0 or 1. 0 indicates a private system. 1 indicates a residential system.
User Zone ID
The User Zone ID is the ID of the User Zone.
User Zone Elapsed Time Field

The User Zone Elapsed Time is the total (analog plus digital) elapsed time that the mobile subscriber stays in that User Zone. If the service provider is interested in the digital portion of the User Zone Elapsed Time, the Auxiliary Time Module can be used to store the User Zone Digital Elapsed Time. NOTE: The ADUB feature needs to be on in order to turn on the Auxiliary Time Module via RC/V. Four more time types were added to the Time Type field (AMASE Table 473) of the Auxiliary Time Module to support the User Zone capability.

010Digital User Zone Sequence Number 1 elapsed time. 011Digital User Zone Sequence Number 2 elapsed time. 012Digital User Zone Sequence Number 3 elapsed time. 013Digital User Zone Sequence Number 4 elapsed time.
Issue 27
May 2004
24-13
401-610-133A

The User Zone Module will be appended to AMA records for CDMA calls with the x2329-x2335 structure codes, if the following conditions are true:

The CDMA Private Network and User Zone feature is active in the FAF. The ecp form field for Append User Zone Module to the AMA Record is set to y. The User Zone Sequence Number 1 or Sequence Number 2 or Sequence Number 3 or Sequence Number 4 Elapsed Time field has a non-zero value.
NOTE: The ADUB feature must be active in the FAF and the Auxiliary Time Module turned on via RC/V so the Digital User Zone Elapsed Time Sequence Number 1 or Sequence Number 2 or Sequence Number 3 or Sequence Number 4 can be collected in the Auxiliary Time Module and appended to an existing AMA record.

For more about the User Zone Module, read Module 336User Zone Module on page 5-36.
24-14
Issue 27
May 2004
User Zone Module Generation Rules for CDMA

Introduction
This section gives rules for when CDMA User Zone Modules are generated, depending upon where a call starts and where it ends. These rules only apply to the CDMA implementation of the User Zone.
Charge Recording and the User Zone Module

Charge recording data will contain User Zone information for up to four User Zones per call.
Call That Starts and Ends in One User Zone

If a call starts and ends in one User Zone, only one User Zone Module will be appended to the record. In CDMA, the Public System is considered a User Zone. Therefore, if a call starts and ends in the Public System, a single User Zone Module will be appended to the record.
Call that Moves into Other User Zones

A subsequent handoff of a call into another User Zone will cause a second User Zone Module to be appended. A handoff to a third user then will create a third User Zone Module. A handoff for a fourth User Zone will create a fourth User Zone Module.
Call that Continues Past Four Handoffs

From the time that the mobile subscriber changes to the fourth User Zone until the end of the call, no new User Zone Module will be created. The elapsed time shown in the fourth User Zone Module will show the time that the mobile subscriber changed into the fourth User Zone until the end of the call, even if the mobile subscriber later hands off into a different User Zone or back into the Public System. In other words, any handoff into a fifth, sixth or more User Zones or back into the Public System after being in the fourth User Zone will continue to be recorded in the elapsed time field for the fourth User Zone Module and will not be differentiated in that data.
Issue 27
May 2004
24-15
401-610-133A
For all Features (To Get the Auxiliary Time Module)
In order to append the Digital User Zone Sequence Number 1 (or 2 or 3 or 4) field to the AMA record using the Auxiliary Time Module, the following conditions need to be true:

The ADUB feature is active in the FAF The Auxiliary Time Module needs to be turned on via RC/V
For Other Feature Interactions

For feature interactions that are not AMA-related, read the optional feature documents for these features:
401-612-126, IS-136 Non-Public Network Identifiers and Charging Areas Optional Feature 401-612-182, CDMA Private Network and User Zone Optional Feature
24-16
Issue 27
May 2004
25
25-1 25-1 25-2 25-2 25-2 25-2 25-2 25-3 25-3 25-3 25-3 25-3 25-4 25-4 25-5 25-5 25-5 25-5 25-6 25-7 25-7 25-7

Introduction What is the CDMA Circuit-Mode Data Service Feature? Use with the Analog Fax Support for CDMA Feature Scope Introduction Components Reason for the Inter-Working Function (IWF) Definition of the IWF Two Data Paths How the Legs Are Set Up PDP Leg Can Also Activate/Deactivate Features Special Case in Which There is No PDP Leg Setup Scenario for the MDP and the PDP Tracking AMA Activity Exception No Record for the PDP Leg Explanation
How It Works

ADSS and the Circuit-Mode Data Service Feature

Issue 27
May 2004
25-i
401-610-133A
AMA Impacts New Call Types

25-8 25-9 25-9 25-9 25-10 25-11 25-11 25-11 25-11 25-11 25-11 25-11 25-12 25-12 25-12 25-12 25-12 25-12 25-12 25-13 25-13 25-13 25-14 25-14 25-14 25-14 25-14 25-14 25-14 25-15 25-15 25-15 25-16 25-17 25-17 25-18 25-18 25-18
Records For Which These Call Types Do Not Apply Records for Which These Call Types Sometimes Apply
Call Types Mobile-Originated Circuit Data Call

Introduction Purpose Definition Applicable Structure Codes Structure Codes for the MDP Leg Structure Codes for the PDP Leg Introduction Purpose Definition Applicable Structure Codes Intra-Switch Terminated Data Call: Only One Record Intra-Switch Terminated Data Call: Structure Codes For Inter-Switch Terminated Data Call: Two or More Records Inter-Switch Terminated Data Call: Structure Codes For Re-routing of Incoming CDMA Circuit-Mode Data Service Calls Introduction Purpose of the Data Module Data Module Definition Module Code Field Event Type Field Event Description Field Linking Code Field Data Module and the Digital Event Module Data Module Generation Criteria For Further Information Introduction Introduction AMA Record for MDP Leg
Mobile-Terminated Circuit Data Call

Data Module

AMA Records for CDMA Circuit-Mode Data Service Calls
Mobile Origination

25-ii
Issue 27
May 2004
Exceptions: Rationale for Exceptions for a Standard MDP Leg Call AMA Record for PDP Leg Exceptions for a Standard MDP Leg Call Record for PDP Leg with Feature Activation/Deactivation Exceptions Introduction AMA Record for Mobile-Terminated Call Exceptions
25-18 25-18 25-19 25-20 25-20 25-21 25-22 25-22 25-22 25-22
Mobile Termination

Issue 27
May 2004
25-iii
401-610-133A
25-iv
Issue 27
May 2004
25
Introduction
This chapter introduces the CDMA Circuit-Mode Data Service feature and describes the two new call types and one new module created for this feature. The chapter also explains how the CDMA Circuit-Mode Data Service feature affects AMA records. Finally, the chapter describes interactions of the CDMA Circuit-Mode Data Service feature with other features. This chapter covers the CDMA implementation of the Circuit-Mode Data Service feature. For the TDMA implementation, see Chapter 40, TDMA Circuit-Mode Data Services Feature.

For more information about this feature, read the CDMA Circuit-Mode Data Description and Set Up Procedures, 401-610-098.
Issue 27
May 2004
25-1
401-610-133A
Feature Description
Introduction
This section describes the CDMA Circuit-Mode Data Service feature.
What is the CDMA Circuit-Mode Data Service Feature?

The CDMA Circuit-Mode Data Service feature provides a subscriber having the appropriate mobile station configuration the ability to communicate with existing asynchronous modems and group-3 facsimile machines using the CDMA air interface.
Use with the Analog Fax Support for CDMA Feature

This feature, when used in conjunction with the Analog Fax Support for CDMA feature, allows mobile subscribers who have fax machines with an analog output to send and receive faxes in a CDMA environment. This feature is used primarily for wireless local loop. The Analog Fax Support for CDMA feature provides two new Initial CDMA Assigned Service Options (defined in AMASE Table 497 Event Description Values for Event Type 002 on page 4-76). For more about this feature, read the Analog Fax Support for CDMA Optional Feature document, 401-612-235.
Scope
Mobile-originated, mobile-terminated, and mobile-to-mobile circuit-mode data calls are supported.1
A mobile-to-mobile data call is treated as a combination of a mobile-originated data call and a mobile-terminated data call.
25-2
Issue 27
May 2004
How It Works
Introduction
This section gives an overview of how the CDMA Circuit-Mode Data Service feature works.
Components
A typical mobile station configuration consists of a data terminal, such as a laptop computer, connected via an RS-232 cable to a CDMA mobile device conforming to TIA/EIA/IS-99, the circuit-mode data service standard. This mobile device presents an interface to the data terminal that allows the data terminal application to treat the mobile device as if it were an asynchronous data or facsimile modem. The mobile device uses the CDMA air interface to access an Inter-Working Function (IWF) connected to the Digital Cellular Switch (DCS) of a Mobile Switching Center (MSC). The IWF delivers the actual modem functions being controlled by the data terminal.
Reason for the Inter-Working Function (IWF)

The CDMA vocoder cannot carry voice-band modem tones at the higher modulation rates popular today. These modem tones carry a rich set of frequency, phase, and amplitude relationships that low-bit-rate vocoders cannot reproduce. Therefore, the CDMA air interface must carry the data in digital form to an interworking function (IWF) that generates the modem tones for communication through the PSTN.
Definition of the IWF

The IWF is a separate piece of hardware that is connected to the Digital Cellular Switch (DCS) of a Mobile Switching Center (MSC). The IWF delivers the actual modem functions being controlled by the data terminal, as shown in Figure 25-1 on page 25-4.
Issue 27
May 2004
25-3
401-610-133A
ECPC
ECP-cell link ECP-DCS link
cell
packet pipe
DCS
PSTN trunk
PSTN
signaling links
mobile data path leg
IWF
PSTN data path leg
Figure 25-1.
The Inter-Working Function--How It Works
Two Data Paths

A circuit-mode data call is treated as two independent calls at the DCS. These are the mobile data path (MDP) leg and the PSTN data path (PDP) leg. The mobile data path leg refers to the connection between the subscriber and the IWF. The mobile data path leg carries digital data between the mobile device and the IWF. The PSTN data path leg refers to the connection between the IWF and the PSTN. The PSTN data path leg carries modem tones between the IWF and the PSTN. The IWF connects to the PSTN through the DCS; it has no direct PSTN connections.
How the Legs Are Set Up

When a subscriber originates a CDMA Circuit-Mode Data Service call (via an ATD command), the MDP leg is established first. Once the MDP leg is established, a stable connection exists between the data terminal and the IWF. Based on instructions downloaded from the data terminal, the IWF can now initiate a call to the PSTN on behalf of the subscriber. This call from the IWF to the PSTN is the PDP leg. Once the setup of the PDP leg is finished, a complete communication link from the subscribers terminal equipment to the PSTN-connected modem is established. One AMA record is generated for the MDP leg with a structure code number of x2329 or x2333. One AMA record is generated for the PDP leg with a structure code number of x2118 or x2119.
25-4
Issue 27
May 2004
PDP Leg Can Also Activate/Deactivate Features

Instead of a call that is routed to the PSTN, the call made from the IWF can also be used to activate and/or deactivate features for the mobile. If the mobile causes the IWF to dial the appropriate feature codes (for example, *72 to activate call forwarding), the PDP leg will cause the appropriate feature to be activated or deactivated. One AMA record is generated with a structure code number of x2411 for the feature activation/deactivation.
Special Case in Which There is No PDP Leg

It is also possible for no subsequent PSTN call to be generated by the IWF. The mobile may simply download various parameters from the IWF and then end the call. In this case, there is no PDP leg to a Circuit-Mode Data Services call.
Setup Scenario for the MDP and the PDP

When a subscriber receives an incoming CDMA Circuit-Mode Data Service call (that is, mobile termination), the setup of the MDP and the PDP legs is done in parallel. The incoming call from the PSTN is associated with the PDP leg. Upon receipt of this incoming call, the mobile will be paged. If the call is a CDMA CircuitMode Data Service call, the setup of the MPD leg begins after the mobile responds to the page. When the subscriber answers the call, the setup of the PDP leg is completed by forwarding the incoming call to a trunk associated with the same IWF used for the MDP leg. Once the forwarding of the incoming call to the IWF is complete, a complete communication link from the subscribers terminal equipment to the PSTN-connected modem is established. One AMA record is generated for the CDMA Circuit-Mode Data Mobile Terminated call with a structure code number of x2331, x2334, or x2335.
Tracking AMA Activity

AMA activity on both these legs is tracked in AMA records. See the section called AMA Records for CDMA Circuit-Mode Data Service Calls on page 25-17 for information on how this is done.
Issue 27
May 2004
25-5
401-610-133A
Exception
An immediate billing record will not be generated for the PDP leg of a CDMA Data (or Fax) Origination. See ADSS and the Circuit-Mode Data Service Feature on page 25-7.
25-6
Issue 27
May 2004
ADSS and the Circuit-Mode Data Service Feature

No Record for the PDP Leg
An immediate billing record will not be generated for the PDP leg of a CDMA Data (or Fax) Origination.
Explanation
Normally, two AMA records are generated on a Data Origination, one for the MDP, and another for the PDP. The reason that billing records are not generated for the PDP leg of a CDMA Data (or Fax) call is that this call uses existing Tandem Trunk Switching to do the PDP, and ADSS is not done on TTS calls.
Issue 27
May 2004
25-7
401-610-133A
AMA Impacts
The major impacts of CDMA Circuit-Mode Data Service on AMA are:
Two call types: Mobile-Originated Circuit Data Call Mobile-Terminated Circuit Data Call. One new module, the Data Module
These impacts are discussed in the following sections.
25-8
Issue 27
May 2004
New Call Types

Two new call types have been created for the CDMA Circuit-Mode Data Service feature. They are:

059 - Mobile-Originated Circuit Data Call 053 - Mobile-Terminated Circuit Data Call.
These new AMA call types are being introduced to identify a call as a circuit-mode data services call. These call types are described in the following sections.
Records For Which These Call Types Do Not Apply

The 059 and 053 call types do not apply to x2337 and x2338 AMA records generated during a data call; for these records, normal call types apply.
Records for Which These Call Types Sometimes Apply

Structure code layout number x2336 can apply to two types of records: hand-off record, and inter-switch termination record. For structure code layout number x2336 records for handoffs, the 059 and 053 call types do not apply. For structure code layout number x2336 records for inter-switch terminations, only the 053 call type applies.
Issue 27
May 2004
25-9
401-610-133A
Call Types
Two new call types were created for the CDMA Circuit-Mode Data Service feature. They are:

059 - Mobile-Originated Circuit Data Call 053 - Mobile-Terminated Circuit Data Call
These AMA call types identify a call as a circuit-mode data services call. NOTE: These call types do not apply to x2337 or x2338 AMA records generated during a data call; normal call types apply instead. These call types are described in the following sections.
25-10
Issue 27
May 2004
Mobile-Originated Circuit Data Call

Introduction
This section describes the Mobile-Originated Circuit Data Call Call Type.
Purpose
The Mobile-Originated Circuit Data Call Call Type is used for mobile-originated data calls.
Definition
The Call Type number for the Mobile-Originated Circuit Data Call is 059.
Applicable Structure Codes

This Call Type applies to AMA records generated for both the mobile data path (MDP) and the PSTN data path (PDP) legs of a mobile origination and applies to structure codes x2118, x2119, x2329, x2333, and x2411.
Structure Codes for the MDP Leg

The AMA record on the mobile data path leg of a mobile-originated CDMA CircuitMode Data Service call will use structure codes x2329 and x2333.
Structure Codes for the PDP Leg

The AMA record on the PSTN path leg that is routed to an outgoing trunk of a mobile-originated CDMA Circuit-Mode Data Service call will use a x2118, x2119, and x2411 structure code. The AMA record on the PSTN path leg that is used for feature activation/ deactivation of a mobile-originated Circuit-Mode Data Services call will use a x2411 structure code. NOTE: For a mobile-originated Circuit-Mode Data Services call that does not cause the IWF to generate a PDP leg, only one AMA record will be generated by the call for the MDP leg.
Issue 27
May 2004
25-11
401-610-133A

Introduction
This section describes the Mobile-Terminated Circuit Data Call Call Type.
Purpose
The Mobile-Terminated Circuit Data Call Call Type is used for mobile-terminated data calls.
Definition
The Call Type number for this Call Type is 053. Like the Mobile-Originated Circuit Data Call Call Type, the Mobile-Terminated Circuit Data Call Call Type applies to AMA records generated for both the mobile data path (MDP) and the PSTN data path (PDP) legs of a call.

The Mobile-Terminated Circuit Data Call Call Type applies to structure codes x2331, x2334, x2335, and x23362.
Intra-Switch Terminated Data Call: Only One Record

For a mobile-terminated data call that goes through only one DCS at call setup time, the MDP and PDP legs of the call will generate AMA information equivalent to a similar type of call termination for a non-data call. For these non-interswitch terminating calls (the usual case) this will generate a single AMA record.
Intra-Switch Terminated Data Call: Structure Codes For

The AMA record for a non-interswitch mobile-terminated CDMA Circuit-Mode Data Service call will use structure codes x2331 and x2334.
The AMA record for an inter-switch termination only.
25-12
Issue 27
May 2004
Inter-Switch Terminated Data Call: Two or More Records

For a mobile-terminated CDMA Circuit-Mode Data Service call that goes through more than one DCS at call setup time, call processing will generate two or more AMA records3. The control point switch AMA record for these inter-switch mobileterminated circuit data calls will use structure code x2335.
Inter-Switch Terminated Data Call: Structure Codes For

For interswitch mobile-terminated CDMA Circuit-Mode Data Service calls, the slave (or serving) switch AMA record will use an x2336 structure code.
Re-routing of Incoming CDMA Circuit-Mode Data Service Calls

Incoming CDMA Circuit-Mode Data Service calls can be re-routed via either the call forwarding or message recording service (voice mail) features. Normal AMA records for those features will apply.
This second case has nothing to do with the IWF; a separate AMA record is always generated for each DCS involved in an interswitch call.
Issue 27
May 2004
25-13
401-610-133A
Data Module
Introduction
The Data Module is used for the CDMA Circuit-Mode Data Service feature. This module is described in this section.
Purpose of the Data Module

The Data Module is used to store the Initial CDMA Assigned Service Option. The Data Module also provides a link between the two separate AMA records that are created for a CDMA Circuit-Mode Data Service mobile-originating call.
Data Module Definition

The Data Module contains the following fields:

Module Code Event Type Event Description Linking Code
Module Code Field

The Module Code field identifies the type of module that is appended to the existing AMA record. The value of the module code for the Data Module is 344.
Event Type Field

The Event Type field defines the same type of information as the event type used in a Digital Event Module. For a CDMA Circuit-Mode Data Service call, the event type will be set to 002 to indicate that the event description contains the Initial CDMA Assigned Service Option for a CDMA call.

The Event Description field defines the same type of information as the event description used in a Digital Event Module for type 002. For a CDMA Circuit-Mode Data Service call, the event description holds the Initial CDMA
25-14
Issue 27
May 2004
Assigned Service Option for the CDMA call. For a complete list of possible values for this field, go to Table 4-46 "AMASE Table 497 Event Description Values for Event Type 002" on page 4-76.
Linking Code Field

The Linking Code field is used to provide a link between the two separate AMA records that are created for a CDMA Circuit-Mode Data Service mobileoriginating call. The linking code consists of a sign digit plus a seven-digit nonzero number that will be set to the same value in both AMA records generated by the CDMA Circuit-Mode Data Service mobile-originating call. For CDMA CircuitMode Data Service mobile-terminating calls, the linking code will be set to 04. The Linking Code is unique across the CDNs and is created and assigned when the MCR for the PSTN path leg is created.
Data Module and the Digital Event Module

A Data Module can be considered a type of Digital Event Module since, like one type of Digital Event Module, it records the Initial CDMA Assigned Service Option. Therefore, if a Data Module is appended to a record, the Digital Event Module that records the Initial CDMA Assigned Service Option will not be appended, since the Data Module has already reported the Initial CDMA Assigned Service Option.
Data Module Generation Criteria

A Data Module will replace the Digital Event Module that records the Initial CDMA Assigned Service Option in a CDMA AMA record if the following generation criteria are met:
The CDMA Circuit-Mode Data Service Feature Activation File (FAF) entry is active. The Data Module is turned on via ecp RC/V. A CDMA mobile has originated or received a CDMA Circuit-Mode Data Service call.
If these generation criteria have been met, a Data Module will be appended to AMA records that have structure codes x2118, x2119, x2329, x2331, x2333 x2335, and x2411.
For mobile-terminating calls, both AMA records are combined into one, so a Linking Code is not needed.
Issue 27
May 2004
25-15
401-610-133A

For more about the Data Module, read Module 344Data Module on page 5-38.
25-16
Issue 27
May 2004
AMA Records for CDMA Circuit-Mode Data Service Calls

Introduction
The type and quantity of AMA records generated for a CDMA Circuit-Mode Data Service call are dependent on the type of call (origination vs. termination). Each call type and its associated AMA records is discussed in the following sections.
Issue 27
May 2004
25-17
401-610-133A
Mobile Origination
Introduction
A mobile-originated CDMA Circuit-Mode Data Service call consists of two parts:

A call from the mobile to the IWF, known as the mobile data path (MDP) A call from the IWF to the PSTN (or another mobile), known as the PSTN data path (PDP).
Separate AMA records are generated for each of these two parts of the call. These AMA records are linked with a linking code to allow the records to be associated with each other by the downstream billing process.
AMA Record for MDP Leg

The AMA record created by the MDP part of the call will be typically a standard mobile origination record using structure code x2329 (or structure code x2333 if an Inter-DCS or Inter-MSC Soft Handoff occurs during the call).
Exceptions: Rationale for

Some exceptions must occur because many of the fields in a typical x2329 AMA record are generated and derived during digit analysis done on the dialed digits on a mobile-originating call. For the CDMA Circuit-Mode Data Service feature, digit analysis is not performed on the mobile data path leg of the call; rather, digit analysis is done on the digits received in the incoming call for the PSTN data path leg of the call. Thus, many AMA data fields related to routing for an x2329 AMA record must be defaulted to generate a meaningful AMA record.
Exceptions for a Standard MDP Leg Call

The following exceptions to the standard mobile origination record occur for a Mobile Origination CDMA Circuit-Mode Data Service call:
The Call Type field will be set to Mobile Originated Circuit Data Call. The Call Type value used to indicate Mobile Originated Circuit Data Call is 059. The call from the mobile to the IWF does not contain any destination digits. (As already explained, the called number is not known until after the mobile is connected to the IWF.) Thus, the following Digit-Related fields in the record are set by default:
25-18
Issue 27
May 2004
The Terminating Number field is set to all zeroes (unless the Dialed Digits in AMA feature is on; see the discussion of Dialed Digits in AMA, later in this set of lists.) BCD Character 5 of the Origination Indicator will be set to 5 (Basic Routing). BCD Character 6 of the Origination Indicator will be set to 0 (No Operator Involved). The Dialed Digits in AMA field (whether in the Terminating Number field or in a Digit Information Module) will be set to the digits received from the mobile. Note that the mobile is not required to send any digits in the origination message received from the cell. The mobile may communicate the dialed digits directly to the IWF via an ATD modem command. If no digits are received, the dialed digits will be all zeroes.
The Call Answer Status will be set to Answered if the IWF answered the MDP portion of the call. Note that this field does NOT indicate whether the call was answered at the far end. The Call Answer Status in the PDP leg of the call must be examined to determine the answer status of the outgoing call. The Called Party Answer Date and Time fields will indicate the time that the IWF answered the MDP portion of the call. Note that this is NOT the time/date that the far end answered the call. The Called Party Answer Time and Date fields in the PDP leg of the call must be examined to determine the answer time of the outgoing call. The Called Party Elapsed Time field will indicate the time from when the IWF answered the MDP portion of the call to when the call was disconnected. Note that this is NOT the elapsed time that the mobile was talking to the far end. The Called Party Elapsed Time field in the PDP leg of the call must be examined to determine the elapsed time of the outgoing call. The Trunk Network Number field will contain information on the Switched Virtual Circuit (SVC) trunk used to connect the mobile to the IWF. If the appropriate flag in the ecp database form is set to y, the Data Module will be appended to the AMA record. (See Call Types on page 25-10 for more details on the Data Module.)
AMA Record for PDP Leg

The AMA record for the PDP portion of a CDMA Circuit-Mode Data Service call will use a Tandem Trunk Switching structure code if the call is routed to an outgoing trunk. If an interexchange carrier is used for the call, structure code x2118 will be used. Otherwise, structure code x2119 will be used.
Issue 27
May 2004
25-19
401-610-133A

The values in the fields of the Tandem Trunk Switching record will be similar to a standard Tandem Trunk Switching call with the following exceptions:
The Call Type field will be set to Mobile Originated Circuit Data Call. The Call Type value used to indicate Mobile Originated Circuit Call is 059. The Subscriber Number field will be set to the originating mobiles directory number. All of the destination digit related fields will be filled in normally based on the destination of the outgoing call. The Call Answer Status field will be set to Answered if the far end answers the outgoing call. The Called Party Answer Date and Time fields will be filled in with the date and time that the far end answered the call. The Called Party Elapsed Time field will be filled in with the elapsed time from when the far end answered the call until the call was disconnected. The Outgoing Tandem TNN field will contain the outgoing trunk for the call. The Incoming Tandem TNN field will contain the ISDN B Channel (IBC) trunk used to connect the IWF to the outgoing trunk for routing out to the PSTN. If the Data Module is turned on via ecp RC/V, the Data Module will be appended to the AMA record. (See Call Types on page 25-10 for more details on the Data Module.)
Record for PDP Leg with Feature Activation/ Deactivation

It is possible for the PDP portion of a CDMA Circuit-Mode Data Service Feature call to involve a feature activation/deactivation rather than a call to be routed to the PSTN. In this case, feature activation/deactivation AMA structure codes will be used in the same way as they are for a feature activation/deactivation call made by a normal voice mobile. Structure code x2411 will be used. If the appropriate flag in the ecp database is set to y, the value in the fields of the x2411 record will be similar to standard values used in a feature activation/deactivation call made by a voice mobile with certain exceptions.
25-20
Issue 27
May 2004
Exceptions
The following exceptions apply in this case:
The Call Type field will be set to Mobile-Originated Circuit Data Call. The Call Type value used to indicate Mobile-Originated Circuit Data Call is 059. If the appropriate flag in the ecp database is set to y, the Data Module will be appended to the AMA record. (See Call Types on page 25-10 for more details on the Data Module.)
Issue 27
May 2004
25-21
401-610-133A
Mobile Termination
Introduction
A mobile-terminated CDMA Circuit-Mode Data Service call also consists of the MDP and PDP portions of the call as described for a mobile-originated CDMA Circuit-Mode Data Service call. The major difference is that usually only one AMA record will be generated for a mobile-terminated CDMA Circuit-Mode Data Service call. (See Inter-Switch Terminated Data Call: Two or More Records on page 25-13 for an exception to this rule.)
AMA Record for Mobile-Terminated Call

The AMA record created by a mobile-terminated CDMA Circuit-Mode Data Service call will be typically a standard mobile-terminated record, using structure code x2331 for intra-DCS terminations or x2334 or x2335 for terminations involving more than one DCS.
Exceptions
The following exceptions to the standard mobile-terminated record apply:
The Call Type field will be set to Mobile Terminated Circuit Data Call. The Call Type value used to indicate Mobile Terminated Circuit Data Call is 053. The Voice Channel Answer Time and Date fields will be set to the time that the answer is received from the IWF over the IBC trunk. Note that this time and date will be a few seconds later than the time that the mobile answered the call on the traffic channel. The answer from the IWF represents the time that a full voice path (here, a data path) is available for the call. If the Data Module is turned on via ecp RC/V, the Data Module will be appended to the AMA record. (See Call Types on page 25-10 for more details on the Data Module.)
25-22
Issue 27
May 2004
26
26-1 26-1 26-2 26-2 26-2 26-2 26-2 26-3 26-3 26-3 26-3 26-3
What is the Virtual System AMA Event Recording (VSAMAER) Feature? How Does it Work? Benefits Values for Voice-Channel Elapsed Time Introduction VSHE Record Linking VSHE Records to AMA Records Contents of a VSHE Record
AMA Impact

Issue 27
May 2004
26-i
401-610-133A
26-ii
Issue 27
May 2004
26
Introduction
This chapter introduces the Virtual System AMA Event Recording (VSAMAER) feature and describes its impact on AMA.

For more about this feature, read the Virtual System AMA Event Recording (VSAMAER) Optional Feature, 401-612-028.
Issue 27
May 2004
26-1
401-610-133A
Feature Description
What is the Virtual System AMA Event Recording (VSAMAER) Feature?
With the increased use of Rural Service Areas (RSAs) and the resale of voice radio air time to RSA service providers, the need has become apparent to provide the ability to segment a call record when different service providers share the same DCS. The Virtual Systems (VS) Call Routing feature allows a service provider to logically break up a DCS into one physical switch and many virtual switches to allow multiple service providers to share one DCS. (In the case of RSAs, the main service provider would presumably be assigned to the physical switch, and all RSA service providers would be assigned to different virtual switches).
How Does it Work?

This feature allows AMA to mark Virtual System (VS) boundaries with AMA event records whenever a switch boundary is crossed and data is required for air time apportioning. The event recorded by this feature is the intra-DCS handoff involving virtual switches on a single physical DCS (that is, physical to virtual, virtual to physical, and virtual to virtual) when the switch boundary requires the recorded event (as defined by a data base entry). The event record indicates the time when the call began to be handled by a different switch (physical or virtual).
Benefits
This feature provides a better record of intra-DCS calls and the ability to apportion revenue more precisely between different service providers, allowing for a more exact division of revenue.
Values for Voice-Channel Elapsed Time

For a list of values for the components of voice-channel elapsed time for several feature sets, see Appendix C, Basic Voice-Channel Elapsed Time Values.
26-2
Issue 27
May 2004
AMA Impact
Introduction
This section describes the AMA Impact of the VSAMAER feature.
VSHE Record
Without the VSAMAER feature, only one AMA record is generated for all of the air time a mobile spends on a given DCS, regardless of handoffs between the physical and virtual switches that may occur while on that DCS. (For the purposes of discussion, this one AMA record will be referred to as the regular AMA record throughout this section.) The VSAMAER feature causes Virtual Systems Handoff Event (VSHE) records to be generated when a cellular unit hands off from one physical/virtual switch to another switch (that is, physical to virtual, virtual to physical, or virtual to virtual) while on the same DCS. A VSHE record is a special record that keeps track of the event date and time, that is, the date and time the call was handed off to a different physical/virtual switch. Thus, the air-time usage provided by each physical/virtual switch can be determined, so that division of revenue between service providers can be accomplished (see Table 4-50 on page 4-80 and Table 4-13 on page 4-19).
Linking VSHE Records to AMA Records

The Mobile Serial Number Field on page 4-28, Voice-Channel Seizure Date Field on page 4-82, and Voice-Channel Seizure Time Field on page 4-22 fields in the VSHE record will allow the VSHE record to be linked back to the one regular AMA record generated for all the air time spent on the one DCS. A VSHE record and a regular AMA record are considered linked if the values in all three fields for both records are identical. Note that many VSHE records may be linked to one regular AMA record (if several VSHEs occur within one DCS).
Contents of a VSHE Record

The contents of the VSHE record are as follows:
Mobile Serial NumberThe mobile serial number is that of the mobile unit involved in the call. This field is provided to link the VSHE record back to the regular AMA record for the call. See Mobile Serial Number Field on page 4-28.
Issue 27
May 2004
26-3
401-610-133A
Voice-Channel Seizure DateThe voice-channel seizure date for the call at the DCS. This field is not the date of the handoff from one physical/virtual switch to another. This field is provided to link the VSHE record back to the regular AMA record for the call. See Voice-Channel Seizure Date Field on page 4-82. Voice-Channel Seizure TimeThe voice-channel seizure time for the call at the DCS. This field is not the time of the handoff from one physical/virtual switch to another. This field is provided to link the VSHE record back to the regular AMA record for the call. See Voice-Channel Seizure Time Field on page 4-22. Handoff to SwitchThe physical or virtual switch number that served the call after the handoff. See AMASE Table 454 on page 4-61. Handoff from SwitchThe physical or virtual switch number that served the call before the handoff. See AMASE Table 454 on page 4-61. Handoff to Radio/Channel Number and Cell Site The radio/channel number and cell site that served the call after the handoff. Table 336 LSA/Handoffs/DCSs Number on page 4-48. Handoff from Radio/Channel Number and Cell SiteThe radio number and cell site that served the call before the handoff. See AMASE Table 454 on page 4-61.
NOTE: When handoffs occur between two DCSs, VSHE records are not generated. Instead, regular Cellular Networking AMA applies (see Chapter 9, Cellular Networking Overview).
26-4
Issue 27
May 2004
27
27-1 27-1 27-2 27-2 27-2 27-2 27-2 27-2 27-3 27-3 27-3 27-3 27-3 27-4 27-4 27-4 27-4 27-5 27-6 27-9

Introduction What is the Metered Billing Feature? How It Works Three Records Contents of the New Records Event Type Field Linking MBAER Records to AMA Call Records Calls That Will Not Generate MBAERs Cases Where a Major Failure Occurs Limitations Introduction For a Mobile Origination Call For a Mobile Termination Call For the End Of the Call
Record Generation Criteria

Metered Billing Structure Codes Feature Interactions
Issue 27
May 2004
27-i
401-610-133A
27-ii
Issue 27
May 2004
27
Introduction
This section describes the Metered Billing feature and its impact on AMA.

For more information on this feature, read the Metered Billing Optional Feature, 401-612-136.
Issue 27
May 2004
27-1
401-610-133A
Feature Description
Introduction
This section describes the Metered Billing feature. For more information about Record Generation, see Limitations on page 27-3.
What is the Metered Billing Feature?

The Metered Billing feature provides for generation of three AMA Event records (structure codes 02800, 02801, and 02802) at the point of call answer and call end. This allows the service provider to implement a method of subscriber prepayment, and, using information from these Metered Billing AMA Event records, debit the subscribers pre-paid account. Metered Billing is available for data calls as well as for voice calls.
How It Works
The Metered Billing feature generates Metered Billing AMA Event records (MBAER) at the point of answer during a mobile origination or mobile termination and at the end of the call. Existing AMA functionality is not altered (for example, standard AMA call records are still generated for mobile originations, mobile terminations, inter-switch handoffs, and so on).
Three Records
The three Metered Billing AMA Event Records are

02800 - Origination Answered MBAER (AMBAER) 02801 - Termination Answered MBAER (TAMBAER) 02802 - End of Call MBAER (EOCMBAER)
Contents of the New Records

The MBAERs contain the event time, subscriber information, and a method of linking together AMA records generated by the same call.
27-2
Issue 27
May 2004
Event Type Field

The Metered Billing Event Type field provides a three-digit code that identifies an AMA event recorded for billing purposes. The definition for this field is given by AMASE Table 453 and the BCD characters are explained in Table 4-37 on page 4-60.
Linking MBAER Records to AMA Call Records

Each MBAER contains independent linkage to the overall AMA call record (for example, structure codes x2329, x2330, x2331, x2332, x2333, x2334, and x2335) using either the Mobile Serial Number, First Voice-Channel Seizure Date and First Voice-Channel Seizure Time (as in the case of non-CPS call records - structure codes x2329, x2330, and x2331) or Transaction Code I, Transaction Code II (as in the case of CPS call records - structure codes x2332, x2333, x2334, and x2335) or both. If conflicts occur, Mobile Serial Number, First Voice-Channel Seizure Date and First Voice-Channel Seizure Time will take precedence.
Calls That Will Not Generate MBAERs

Calls that do not receive answer supervision (appearing unanswered), such as operator-assisted and calls to certain announcements and/or services will not generate MBAERs.
Cases Where a Major Failure Occurs

If a major failure such as a hardware fault in a CDN occurs for a call that was answered prior to the hardware failure, an End Of Call MBAER may not be generated, even though an earlier mobile origination or mobile termination MBAER may have been generated.
Limitations
Metered Billing subscribers should not be assigned features such as Call Waiting and Three Way Calling since free calls may result. If a call ends abnormally no End of Call MBAER will be generated.
Issue 27
May 2004
27-3
401-610-133A
Record Generation Criteria

Introduction
An MBAER is generated when an answer occurs on a mobile origination or mobile termination or at the end of a call. This section describes generation criteria for the three MBAER records. NOTE: The Metered Billing records identified here are in addition to standard records created for the call.
For a Mobile Origination Call

The Metered Billing feature generates an Origination Answered MBAER (OAMBAER) if the following conditions exist:

Answer supervision is detected. The Origination Answered Metered Billing Event Record feature is active in the FAF. The Metered Billing AMA: Origination Answered field in the ecp form is set to y. The Metered Billing field is set to y on the sub or vlr form for the subscriber. The origination destination is not an unrestricted number.
For a Mobile Termination Call

The Metered Billing feature generates a Termination Answered MBAER (TAMBAER) if the following conditions exist:

Answer supervision is detected. The Termination Answered Metered Billing Event Record feature is active in the FAF. The Metered Billing AMA: Termination Answered field in the ecp form is set to y. The Metered Billing field is set to y on the sub or vlr form for the subscriber.
27-4
Issue 27
May 2004
For the End Of the Call

The Metered Billing feature generates an End Of Call MBAER (EOCMBAER) if the following conditions exist:

The End Of Call is detected. The End Of Call Metered Billing Event Record feature is active in the FAF. The Metered Billing AMA: End Of Call field on the ecp form is set to y. The Metered Billing field is set to y in the sub or vlr form for the subscriber. Either an Origination Answered or Termination Answered MBAER has been generated.
NOTE: If the Origination Answered Metered Billing Event Record feature or the Termination Answered Metered Billing Event Record feature is not active on the FAF, the End Of Call MBAERs will not be generated even if the End Of Call Metered Billing Event Record feature is active.
Issue 27
May 2004
27-5
401-610-133A
Metered Billing Structure Codes

The Origination Answered Metered Billing AMA record has a structure code of 02800. The Termination Answered Metered Billing AMA record has a structure code of 02801. The End of Call Metered Billing AMA record has a structure code of 02802. The record fields and associated AMASE (AMA standard entry) tables that are used by the Metered Billing feature are shown in Table 27-1 on page 27-6. Table 27-1. AMA Record Fields and AMASE Tables Used by Metered Billing
AMA Record Field Call Type
AMASE Table Table 1 - Call Type on page 4-7 Table 666 Date on page 4-80
How the Field is Used... Existing and unmodified. Matches the AMA record generated for the call. Existing and unmodified. Corresponds to the answer date for Origination Answered or Termination Answered Metered Billing Answer Event Records (MBAERs) or the mobile unit release date for End of Call MBAER. Existing and unmodified. Corresponds to the answer time for Origination Answered or Termination Answered MBAERs or the mobile unit release time for End of Call MBAER. This is the time of day and not elapsed time.
Event Date
Event Time
Table 18 - Time on page 4-19
NOTE:
27-6
Issue 27
May 2004
AMA Record Field Event Type
AMASE Table Table 453 Event Type on page 4-60
How the Field is Used... Existing with the following four additional event type codes:

006=Origination Answer 007=Termination Answer 008=End of Call 009=Abnormal End of Call (unimplemented)
First Voice-Channel Table 666 Date on Seizure Date page 4-80
Existing and unmodified. Allows linkage of the MBAER to the AMA Call Record and specifies the date that the first voice channel was successfully seized on the call. Existing and unmodified. Allows linkage of the MBAER to the AMA Call Record and specifies the time that the first voice channel was successfully seized on the call. Existing and unmodified. Allows linkage of the MBAER to the AMA Call Record. Existing and unmodified. Contains the current or the last available radio/channel number and cell site at the time of event. Existing and unmodified.
First Voice-Channel Table 18 - Time on Seizure Time page 4-19
Mobile Serial Number Initial Radio Number and Cell Site
Table 32 11-Digit Number on page 4-28 Table 2003 Radio/ Channel/Cell Information on page 4-124
Recording Office ID Table 5 - Recording Office Identification on page 4-12 Recording Office Type Sensor ID
Existing and unmodified. Table 4 - Recording Office Type on page 4-11 Table 3 - Sensor Identification on page 4-10 Table 2 - Sensor Type on page 4-9 Existing and unmodified.
Sensor Type
Existing and unmodified.
Issue 27
May 2004
27-7
401-610-133A
AMA Record Field Serving System ID
AMASE Table Table 803 5-Digit Number on page 4-93
How the Field is Used... Existing and unmodified. Contains the current or last available System Identification (SID) of the serving cell at the time of event. If a cell site is not available, then the SID of the Digital Cellular Switch (DCS) is used. Existing and unmodified. Matches the AMA record generated for the call. Existing and unmodified. This field is used in the Origination Answered MBAER and matches the AMA Call Record that is generated for the call. Existing and unmodified. This field provides a unique number to link the Metered Billing records for the same call together. If the current call is a Cellular Networking (CN) or IS41 CPS call, this number matches the Transaction Code 1 that is generated in the CPS AMA Call Record.
Subscriber Number Table 2000 Number on page 4-115 Terminating Number Table 2000 Number on page 4-115
Transaction Code 1 Table 378 Transaction Code I on page 4-53
NOTE:
Transaction Code 2 Table 379 Serving ESID Information/ Transaction Code II on page 4-54
Existing with the following additional air-time segment value in BCD character 10:
7= Metered Billing
27-8
Issue 27
May 2004
The Metered Billing features interacts with several other features. For more information about these feature interactions, read the Metered Billing Optional Feature document, 401-612-136.
Issue 27
May 2004
27-9
401-610-133A
27-10
Issue 27
May 2004
28
28-1 28-1 28-2 28-2 28-2 28-2 28-2 28-4 28-4 28-4 28-4 28-5 28-5 28-5 28-5 28-5 28-5 28-6 28-7 28-7 28-7 28-7

Background Need for AMA Enhancements Feature Need for Modification to Existing Billing Systems Phase I: Three New Modules Introduction Module Definitions Module Generation Criteria Introduction Definition Availability Generation Criteria Results For Further Information Introduction Definition Generation Criteria
AMA Impact

Radio Information Module

Trunk Information Module

Issue 27
May 2004
28-i
401-610-133A
Additional Disk Space Needed For Further Information Introduction Definition Generation Criteria Results For Further Information
28-7 28-7 28-8 28-8 28-8 28-8 28-8 28-9
Switch Identification Module

28-ii
Issue 27
May 2004
28
Introduction
The AMA Enhancements feature adds new, more detailed call record information to existing Bellcore formatted AMA records through the use of modules. This chapter explains how AMA functionality is affected when using the AMA Enhancements feature and summarizes the implemented modules.1

No optional feature document for this feature exists. For more information about this feature, contact Lucent Technologies Technical Support.
This feature is related to the Data Message Handler (DMH) feature, which provides Customer Care applications with call detail records formatted according to the TR45.2 interim standard IS-124. Availability of the Flexent/AUTOPLEX Wireless Network DMH feature is to-be-determined.
Issue 27
May 2004
28-1
401-610-133A
Feature Description
Background
The Telecommunications Industry Association (TIA) TR45.2 Technical Subcommittee has developed a standard for the reliable transfer of call information, in near real-time, to various billing collection entities. This standard can be used to support Customer Care (CC) applications that require immediate real-time billing information. Examples of these applications include Billing, Real Time Rating, and Settlement. This standard, known as the IS-124 interim standard and entitled Cellular Radio Telecommunications Intersystem NonSignaling Data Communications, was published in November 1993.
Need for AMA Enhancements Feature

The existing AMA data stream provides much, but not all, of the call information necessary to allow the mapping of AMA data into fully conforming IS-124 call detail records. To address this issue and support the migration of the Flexent/ AUTOPLEX wireless network to compliance with the IS-124 interim standard, the AMA Enhancements feature is being provided. This feature adds new, more detailed call record information to existing Bellcore formatted AMA records through the use of modules.
Need for Modification to Existing Billing Systems

The additional AMA data/modules that are provided with the AMA Enhancements feature, if selected, will require existing billing systems to make modifications to handle the new available data to assure smooth billing operations. Existing AMA record structures are backward compatible.
Phase I: Three New Modules

Phase I of the AMA Enhancements feature provides support for the following new modules:
Radio InformationThis module provides the first and/or the last radio information for the airtime segment represented in this AMA record. If the Cell Information Module is appended, this module provides the radio information for the radio in the Cell Information Module. This module is available only with TDMA. Trunk InformationThis module provides more detailed trunk information for the call.
28-2
Issue 27
May 2004
Switch IdentificationThis module provides the system identifier, switch number, and switch type of the switch.
Each of these modules is described in its own section, later in this chapter.
Issue 27
May 2004
28-3
401-610-133A
AMA Impact
Introduction
This section describes the three modules associated with the AMA Enhancements feature.
Module Definitions
Complete definitions for the AMA Enhancements - Phase 1 modules, including field names, the associated AMASE tables used to define the module fields, and total number of BCD characters per field, are given in Table 28-1 on page 28-4. Table 28-1. AMA Module Definitions AMASE Table Number 88 953 244 88 2004 666 18 19 954 No. of BCD Chars. 4 8 10 4 12 10 8 10 6 Page Number 4-35 4-101 4-42 4-35 4-42 4-80 4-19 4-23 4-103
Information Radio Information Module Module Code (901) Radio Channel Number Trunk Information Trunk Information Module Module Code (623) Trunk Identification Trunk/Facilities Seizure Date Trunk/Facilities Seizure Time Trunk Elapsed Time Trunk Direction, Trunk Type, and Release Cause Switch Identification Module Module Code (907) Serving ESID Information
88 379
4 12
4-35 4-54

One or more modules can be appended to an existing AMA record based on specific generation criteria. The criteria defined for each module associated with AMA Enhancements (Phase 1) is outlined in the section for the module.
28-4
Issue 27
May 2004
Radio Information Module

Introduction
This section describes the Radio Information Module.
Definition
The Radio Information Module provides the first and/or the last radio information for the airtime segment represented in this AMA record. If the Cell Information Module is appended, the Radio Information Module provides the radio information for the radio in the Cell Information Module. For the AMPS or TDMA radio, the module provides its time slot identity and channel number. For the CDMA radio, the module will provide its channel code and frame offset.
Availability
At present, the Radio Information Module is only available for TDMA.
Generation Criteria
The generation criteria for appending the Radio Information Module to AMA records includes:

The AMA Radio Information FAF entry is active The ecp form field Radio Information Module is set to y via RC/V.
Results
If the generation criteria have been met, a Radio Information Module for the Initial Radio of the airtime segment represented in this AMA record will be appended to AMA records with structure codes 2329-x2334, x2336-x2338, x2411, and x2415. If the generation criteria have been met and the Cell Information Module has already been appended, a Radio Information Module for the Initial Billing Radio used when the call was first set up will be appended to AMA records with structure codes x2329-x2335. If the generation criteria have been met, a Radio Information Module for the Last Radio will be appended to AMA records with structure codes x2329-x2334, and x2336-x2338.
Issue 27
May 2004
28-5
401-610-133A
To summarize, the Radio Information Module may be appended to the same AMA record three times: once for the initial radio, once for the initial billing radio (for the Cell Information Module) and once for the last radio.

For more about the Radio Information Module, see Module 901Radio Information Module on page 5-81.
28-6
Issue 27
May 2004

Introduction
This section describes the Trunk Information Module.
Definition
The Trunk Information Module provides the following additional trunk information to AMA records: Trunk Identification, Trunk/Facilities Seizure Date and Time, Trunk Elapsed Time, Trunk Direction, Trunk Type, and Trunk Release Cause.
Generation Criteria
AMA appends the Trunk Information Module to AMA records with structure codes x2118, x2119, x2329-x2338, x2411, x2415, x2351 if the following generation criteria are met:

The AMA Trunk Information feature FAF entry is active The ecp form field Trunk Information Module is set to y via RC/V.
NOTE: To append structure code x2351, the Append Specific AMA Modules to Structure Code x2351 FAF must also be active.
Additional Disk Space Needed

The Trunk Information Module feature increases the size of AMA records by 22 bytes. Since one AMA record usually appends two Trunk Information Modules, this about a 20% increase if the original, average AMA record size is 200 bytes. If the original, average AMA record size is 150 bytes, the increase is about 30%. When this feature and module are turned on, more/additional disk space is needed to hold the additional AMA data for the same call volume.

For more about the Trunk Information Module, see Module 623Trunk Information Module on page 5-70.
Issue 27
May 2004
28-7
401-610-133A
Switch Identification Module

Introduction
This section describes the Switch Identification Module.
Definition
Switch Identification consists of the following information:

System Identification (SID) Switch Number (ECP Number [1-16] + DCS Number [1-16]) Switch Type (Serving, Target, To [Virtual Switch Handoff Call], From [Virtual Switch Handoff Call], Incoming [Tandem Call] and Outgoing [Tandem Call]).
Generation Criteria
AMA appends the Switch Identification Module information to structure codes x2118, x2119, x2332-x2338, x2411, x2415, and x2421 if the following generation criteria are met:

The AMA Switch Identification Number FAF entry is active The ecp form field Switch Information Module is set to y via RC/V.
Results
If the generation criteria have been met, a Switch Identification Module for the Serving Switch will be appended to AMA records with structure codes x2411 and x2415. If the generation criteria have been met, a Switch Identification Module for the Target Switch will be appended to AMA records with structure code x2332-x2338. If the generation criteria have been met, a Switch Identification Module for the Incoming Switch and a Switch Identification Module for the Outgoing Switch will be appended to AMA records with structure codes x2118 and x2119. If the generation criteria have been met and virtual DCS handoff occurs, a Switch Identification Module for the FROM Switch and a Switch Identification Module for the TO Switch will be appended to the resulting AMA record with structure code x2421.
28-8
Issue 27
May 2004

For more about the Switch Identification Module, see Module 907Switch Identification Module on page 5-83.
Issue 27
May 2004
28-9
401-610-133A
28-10
Issue 27
May 2004
29
29-1 29-1 29-2 29-2 29-2 29-2 29-2 29-3 29-3 29-4 29-4 29-4 29-4 29-5 29-5

Introduction What is the Wireline Feature Transparency Feature? How Does It Work? Example of Call Forwarding Without Wireline Feature Transparency Example of Call Forwarding With Wireline Feature Transparency Benefits Introduction Change in Billing for the Voice Channel Bits in Timing Indicator Set With Call Forwarding Feature
AMA Impact

Feature Interaction
Issue 27
May 2004
29-i
401-610-133A
29-ii
Issue 27
May 2004
29
Introduction
This chapter provides information on the Wireline Feature Transparency feature and describes how AMA functionality is affected by this feature. This chapter also summarizes feature interactions of the Wireline Feature Transparency feature with other features.

More detailed information about this feature can be found in 401-612-141, Wireline Feature Transparency Optional Feature document.
Issue 27
May 2004
29-1
401-610-133A
Feature Description
Introduction
This section describes the Wireline Feature Transparency feature.
What is the Wireline Feature Transparency Feature?

The Wireline Feature Transparency optional feature allows the wireless versions of certain call originations to more closely emulate their wireline equivalents.
How Does It Work?

This feature provides a network dial tone when a subscriber dials certain feature codes and then waits for the subscriber to enter additional digits. In the initial release, the feature only applies to originations containing the feature activation codes for Call Forwarding1. The next two subsections show examples of how Wireline Feature Transparency can support the Call Forwarding feature.
Example of Call Forwarding Without Wireline Feature Transparency

A subscriber with the Call Forwarding feature who does not have the Wireline Feature Transparency feature would use the following procedure to activate his or her call forwarding: 1. Dial the Call Forwarding feature activation code. 2. To use the same destination that was used last time the feature was activated, go directly to Step 3 without entering any digits. Otherwise, enter a new destination DN to which calls will be forwarded. 3. Press <SEND>. While this may seem simple to experienced users, it can be confusing to new subscribers who are more accustomed to the landline version. To alleviate the problem, Wireline Feature Transparency changes the procedure.
For more information, see 401-601-011Call Forwarding.
29-2
Issue 27
May 2004
Example of Call Forwarding With Wireline Feature Transparency

A subscriber with the Call Forwarding feature and with the Wireline Feature Transparency feature active would use the following procedure to activate or reactivate his or her Call Forwarding: 1. Dial the Call Forwarding feature activation code. 2. Press <SEND>. 3. Wait for the network dial tone. 4. Enter a new destination DN to which calls will be forwarded. 5. Wait for the Confirmation Tone. 6. Press <END>. Note that the original activation procedure (dialing the feature code followed by a forward-to destination followed by <SEND>) still works for subscribers with Wireline Feature Transparency.
Benefits
The Wireline Feature Transparency optional feature is intended to make it easy for customers subscribing to certain custom calling features in the landline environment to adapt to using the same features in the wireless environment. The objective is to eliminate subscriber confusion regarding these services and boost their acceptance (and hopefully, usage) of them. Also, this feature will help to support fixed wireless applications.
Issue 27
May 2004
29-3
401-610-133A
AMA Impact
Introduction
This section describes the impact on AMA of the Wireline Feature Transparency feature.
Change in Billing for the Voice Channel

Billing for Wireline Feature Transparency originations starts when the voice channel is assigned. Because a voice channel is required to play the dial tone and collect digits, the time spent listening to the network dial tone and collecting digits is included in the voice channel elapsed time.
Bits in Timing Indicator Set

Calls using Wireline Feature Transparency may be identified by the fact that the Network Dialtone bit the Origination Indicator field is set and the Charge Guard bit of the Timing Indicator field is set. See also Table 4-76 "AMASE Table 2007" on page 4-138 and Table 4-11 "AMASE Table 7" on page 4-15.
29-4
Issue 27
May 2004
Feature Interaction
With Call Forwarding Feature
The Wireline Feature Transparency feature interacts with Call Forwarding as described in Feature Description on page 29-2.
Issue 27
May 2004
29-5
401-610-133A
29-6
Issue 27
May 2004
30
30-1 30-1 30-2 30-2 30-2 30-2 30-3 30-3 30-3

Introduction What is the AMA Antenna Face Information for TDMA and Analog Feature? Benefits Information Stored For TDMA and Analog
AMA Impact

Issue 27
May 2004
30-i
401-610-133A
30-ii
Issue 27
May 2004
30
Introduction
This chapter introduces the AMA Antenna Face Information for TDMA and Analog feature and describes how it affects AMA functionality. This chapter also describes the feature interactions of the AMA Antenna Face Information for TDMA and Analog feature with the Partial Station Class Mark feature.

No optional feature document was written about the AMA Antenna Face Information for TDMA and Analog feature, since this feature is small and merely gives to TDMA and Analog a capability that was already available in CDMA.
Issue 27
May 2004
30-1
401-610-133A
Feature Description
Introduction
This section describes the AMA Antenna Face Information for TDMA and Analog feature and lists benefits and availability of this feature.
What is the AMA Antenna Face Information for TDMA and Analog Feature?
The AMA Antenna Face Information for TDMA and Analog feature provides for TDMA and analog technology a capability already available for CDMA technology: reporting the antenna face associated with a particular call.
Benefits
This feature gives TDMA and analog service providers the ability to offer differential billing to customers, depending on where the call was initiated. (CDMA service providers already have this capability.)
30-2
Issue 27
May 2004
AMA Impact
Information Stored
The second BCD character in AMASE Table 2003 is used to store the antenna face associated with a particular call. For a description of this field and how it can be used by the AMA Antenna Face Information for TDMA and Analog feature, see Table 4-72 on page 4-127 and Table 4-71 on page 4-124 in Chapter 4, AMASE Tables.
For TDMA and Analog

If the AMA Antenna Face Information for TDMA and Analog feature is turned on during a TDMA or analog call, the value stored in the second BCD character in AMASE Table 2003 represents the antenna face used by the call. If this feature is not turned on, the value stored in the second BCD character in AMA Table 2003 is 0.
Issue 27
May 2004
30-3
401-610-133A
30-4
Issue 27
May 2004
31
31-1 31-1 31-2 31-2 31-2 31-3 31-3 31-4

What is the No Charge Calls in AMA Record Feature? Benefits New Call Type
AMA Impact
Issue 27
May 2004
31-i
401-610-133A
31-ii
Issue 27
May 2004
31
Introduction
This chapter introduces the No Charge Calls in AMA Record feature and describes how AMA functionality is affected.

More detailed information about this feature can be found in 401-612-178, AMA Free Calls Optional Feature document.
Issue 27
May 2004
31-1
401-610-133A
Feature Description
What is the No Charge Calls in AMA Record Feature?
The No Charge Calls in AMA Record optional feature allows service providers to categorize mobile to land calls that should be free or marked as no charge in the AMA record. Such calls include 911 calls. This feature uses a new call type, 074 - Free/No Charge Call.
Benefits
The No Charge Calls in AMA Record optional feature is intended to allow cellular service providers to distinguish free/no charge calls from other calls. This will give better service to customers who will no longer have to pay for these types of calls.
31-2
Issue 27
May 2004
AMA Impact
New Call Type
When a mobile originates a call that falls into the free or no charge category, a new call type will be used in the structure code. This call type (074 - Free/No Charge Call) allows service providers to classify certain calls as calls that are either free or have no charge in the AMA record. The following table lists all structure codes that can use call type 074. Table 31-1. Call Type 074 Structure Codes for Call Type 074 Structure Code (Note) 02800 02802 x2329 x2330 x2332 x2333 x2421 Call Condition
Type of Call
Free/No Charge Call
Origination Answered Metered Billing End of Call Metered Billing Cellular-Originated Call without CI Information Cellular-Originated Call with CI Information CPS Cellular-Originated Call with CI Information CPS Cellular-Originated Call without CI Information AMA Event Recording
Issue 27
May 2004
31-3
401-610-133A
This feature has no interactions with other AMA features.
31-4
Issue 27
May 2004
32
32-1 32-1 32-2 32-2 32-2 32-2 32-3 32-4 32-4 32-4 32-4 32-4 32-5 32-5

Introduction What is the CNAP Feature? What is the CNAR Feature? Types of Name Control Introduction Calling Name Incoming Calls Module Calling Name Outgoing Calls Module Module Generation Criteria for the Calling Name Incoming Calls Module Module Generation Criteria for the Calling Name Outgoing Call Module For More About the Modules
AMA Impact

Issue 27
May 2004
32-i
401-610-133A
32-ii
Issue 27
May 2004
32
Introduction
This chapter introduces the Calling Name Presentation (CNAP) and Restriction (CNAR) features. This chapter also describes how AMA functionality is affected by these features and summarizes feature interactions of the these features with other features.

The CNAP feature has two phases.The CNAP Phase 1 feature is covered in 401612-210, the Calling Name Presentation (CNAP) Optional Feature document. The CNAP Phase 2 and CNAR features are covered in 401-612-245, the Calling Name Presentation and Restriction (CNAP/CNAR) Optional Feature document.
Issue 27
May 2004
32-1
401-610-133A
Feature Description
Introduction
This section describes the CNAP and CNAR features. NOTE: These two separate features are always sold together.
What is the CNAP Feature?

The Calling Name Presentation (CNAP) feature is a terminating feature (that is, it only affects incoming calls). CNAP is under the control of the Feature Activation File (FAF). The CNAP feature displays the name of the calling party (up to 20 characters) for land and mobile terminations on IS-136A/IS-95B-compliant, display-capable mobiles operating in the digital mode. With the CNAP feature, the Mobile Switching Center (MSC) sends calling party information to the cell. The cell sends that information to the mobile unit. A subscriber may subscribe to Calling Number Identification Presentation (CNIP), CNAP, or both with the calling number and/or the calling name information delivered to the mobile unit.1
What is the CNAR Feature?

The Calling Name Restriction (CNAR) feature is an originating feature (that is, it only affects outgoing calls). The CNAR feature is not under the control of the FAF. The CNAR feature controls presentation of a CNAP subscriber's calling name information to the called party. The terminating network may receive the calling name identification as part of basic call setup or as a result of a database query. With CNAR, name privacy control is possible for any calling party whose number and name are listed in the queried database. The CNAP subscriber's calling name information is considered public when presentation to the called party is allowed and private when presentation to the called party is restricted.
The CNIP feature is covered in 401-612-006, the Calling Number Identification Presentation and Restriction (CNIP/CNIR) Optional Feature document.
32-2
Issue 27
May 2004
The CNAR feature allows the calling party to change the CNAP feature for an outgoing call. In other words, the CNAR feature allows the subscriber to restrict the subscriber's name and/or number from possibly appearing on the display of the called party. This feature complies with the FCC mandate for a privacy option to be available with the CNAP feature.
Types of Name Control

The CNAR feature has five types of possible name control:

Calling Party Number or Calling Party Name Restriction Calling Party Number or Calling Party Name Enable Calling Party Number and Calling Party Name Restriction Calling Party Number and Calling Party Name Enable Calling Party Name Toggle
Issue 27
May 2004
32-3
401-610-133A
AMA Impact
Introduction
The CNAP/CNAR features add two modules that can be appended to existing AMA records:

Calling Name Incoming Calls Module Calling Name Outgoing Calls Module
Calling Name Incoming Calls Module

The Calling Name Incoming Calls Module contains the Disposition of CPN/ Calling Name Information field (see AMASE Table 477 on page 4-73).
Calling Name Outgoing Calls Module

The Calling Name Outgoing Calls Module contains the Per-Call CPN/ Calling Name Enable and Restriction Usage field (see AMASE Table 476 on page 4-71) and the Disposition of CPN/Calling Name Information field (see AMASE Table 477 on page 4-73).
Module Generation Criteria for the Calling Name Incoming Calls Module
The Calling Name Incoming Calls Module is appended to the existing AMA record for structure codes x2331, x2334, and x2335 if the following conditions are met:
The Calling Name Presentation (CNAP) feature is active in the Feature Activation File. The Calling Name Incoming Calls Module is turned on in the ecp RC/V form. Calling Name Information is received.
The Calling Name Incoming Call Module is also appended to the existing AMA record for structure codes x2329, x2330, x2332, and x2333 if the following conditions are met:
The Calling Name Presentation (CNAP) feature is active in the Feature Activation File. The Calling Name Incoming Call Module is turned on in the ecp RC/V form.
32-4
Issue 27
May 2004
Calling Name Information is received. The call has one of the following custom calling feature: call forwarding, call delivery to call waiting, or special cellular networking (that is, with service codes 012, 014, 055, 083, or 100 as listed in AMASE Table 2002 on page 4-119).
Module Generation Criteria for the Calling Name Outgoing Call Module
The Calling Name Outgoing Calls Module is appended to the existing AMA record for structure codes x2329, x2330, x2332, and x2333, if the following conditions are true:
The Calling Name Presentation (CNAP) feature is active in the Feature Activation File. The Calling Name Outgoing Calls Module is turned on in the ecp RC/V form. Calling Name Information was delivered with the outgoing call.
For More About the Modules

For more about the Calling Name Incoming Calls Module, read Module 981 Calling Name Incoming Calls Module on page 5-86. For more about the Calling Name Outgoing Calls Module, read Module 980 Calling Name Outgoing Calls Module on page 5-85.
Issue 27
May 2004
32-5
401-610-133A
32-6
Issue 27
May 2004
33
33-1 33-1 33-2 33-2 33-2 33-2 33-3 33-3 33-3 33-4 33-4 33-4 33-4 33-4 33-5 33-5 33-5 33-5 33-5 33-5 33-6 33-7

Introduction What is the MIN-MDN Separation Feature? Benefits Introduction Summary of Changes Introduction Where Billing Number is Zero Database Description for Field Does Not Work if Billing Number is Populated Introduction Where VLR is Not Received ANI MIN Database Description for Field Does Not Work if VLR is Present
AMA Impact

MIN In the Billing Number Field

Subscriber Number can be Reset to ANI or MIN

MIN Can be Stored in a DIM Module
Issue 27
May 2004
33-i
401-610-133A
Introduction Need for MIN Database Description for the Field Generic Context Identifier for This Feature Digits String Field Module Generation Criteria for This Feature Result Note For Further Information Introduction Need for IMSI Database Description for the Field Generic Context Identifier for This Feature Digits String Field Module Generation Criteria for This Feature Result Note For More Information
33-7 33-7 33-7 33-7 33-7 33-7 33-8 33-8 33-8 33-9 33-9 33-9 33-9 33-9 33-9 33-9 33-10 33-10 33-10 33-11
IMSI Can be Stored in a DIM Module

33-ii
Issue 27
May 2004
33
Introduction
This chapter provides information on the MIN-MDN Separation feature and describes how AMA functionality is affected by this feature.

No optional feature document for this feature exists. For more information about this feature, contact Lucent Technologies technical support.
Issue 27
May 2004
33-1
401-610-133A
Feature Description
Introduction
This section describes the MIN-MDN Separation feature.
What is the MIN-MDN Separation Feature?

The MIN-MDN Separation feature separates a mobile subscribers Mobile Station Identifier (MSID) from the mobile subscribers Mobile Directory Number (MDN). This separation takes place throughout the Flexent/AUTOPLEX wireless network, including call processing, OA&M, and billing. An MSID in the Flexent/AUTOPLEX wireless network can be the Mobile Identification Number (MIN) or the International Mobile Station Identity (IMSI). Prior to the MIN-MDN Separation feature, the MIN and MDN were used interchangeably throughout the Flexent/AUTOPLEX wireless network software.
Benefits
The MIN-MDN Separation feature is a necessary step in the move towards Wireless Number Portability and other future features.
33-2
Issue 27
May 2004
AMA Impact
Introduction
The MIN-MDN Separation feature affects the Subscriber Number and Billing Number AMA fields. This section lists the changes.
Summary of Changes
The separation of MIN from MDN has led to some new options for storage of MIN and IMSI:

MIN Can Now be populated in the Billing Number Field Subscriber Number can be reset to ANI or MIN MIN Can be Stored in an Appended Module IMSI Can be stored in an Appended Module
Each of these topics is described in the following pages.
Issue 27
May 2004
33-3
401-610-133A
MIN In the Billing Number Field

Introduction
This section describes a way to populate the MIN in the Billing Number field.
Where Billing Number is Zero

In cases where the Billing Number is zero, the MIN can be populated in the Billing Number field by going to the RC/V cco form and setting the Populate the MIN as the Billing Number field to y.
Database Description for Field

The database description for the Populate the MIN as the Billing Number field is: Allow customer to populate the MIN as the Billing Number in the case when there is no VLR at call origination and as a result the billing number is set to NULL in the AMA record.
Does Not Work if Billing Number is Populated

Note that this method does NOT override the contents of the Billing Number field if the Billing Number is already populated.
33-4
Issue 27
May 2004
Subscriber Number can be Reset to ANI or MIN

Introduction
This section describes how MIN (or ANI) is used by the system to populate the Subscriber Number field when VLR information is not available.
Where VLR is Not Received

In cases where the mobile is roaming and does NOT receive a VLR within its TIMEOUT period (call time registration), rather than leave the Subscriber Number field set to 0 (it is typically filled in from the VLR for roaming cases), the Subscriber Number field will be defaulted to one of two possibilities:

ANI MIN
ANI
If the Send System Type (ANI, MIN) field on the RC/V ecp field is set to ANI, the Subscriber Number field will be set to the System Automatic Number Identifier value from the RC/V switch form.
MIN
If the Send System Type (ANI, MIN) field on the RC/V ecp form is set to MIN, the Subscriber Number field will be set to the MIN.
Database Description for Field

The database description for the Send System Type (ANI, MIN) field is: Used to populate the ANI field with MIN or the System ANI field from the switch form for call time registration when the MDN is not available before sending the message to the network to set up the call.
Issue 27
May 2004
33-5
401-610-133A
Does Not Work if VLR is Present

Note that this is ONLY for the VLR TIMEOUT roaming case. If the Subscriber Number (mobile directory number) is present, (that is, if VLR information has been supplied by the roaming mobile) the Subscriber Number (mobile directory number) information will not be overwritten.
33-6
Issue 27
May 2004
MIN Can be Stored in a DIM Module

Introduction
This section describes how the MIN can be stored in a DIM Module and attached to a record.
Need for MIN

In cases where the MIN is needed to meet billing requirements (for example, the MIN-MDN Separation feature is in use, or the MDN is not available), the MIN may be appended to call-related AMA records, if it is available, by setting the RC/V ecp field Digit Information Module for MIN to y.
Database Description for the Field

The database description for the Digit Information Module for MIN field is: Indicates whether the Digit Information Module for Mobile Identification Number (MIN) is to be appended to the AMA record.

The value of the Generic Context Identifier field for this feature is 10830 for MIN.
Digits String Field

The Digits String field for this feature contains the MIN.

The Digit Information Module will be appended to AMA records with the x2118, x2119, x2329-x2338, x2351, x2411, x2415, or x2421 structure codes if the following generation criteria are met:
The entry Append Digit Information Module for MIN? on the ECP RC/V form is set to y. The mobile associated with the call record has a MIN or MIN-based IMSI.
Issue 27
May 2004
33-7
401-610-133A
Result
This will cause an AMA module with module code 621 to be appended to the AMA records with a Generic Context Identifier of 10830 (MIN type).
Note
If the MIN is not available, the Digit Information Module with the MIN will not be populated.

33-8
Issue 27
May 2004
IMSI Can be Stored in a DIM Module

Introduction
This section describes how the IMSI can be stored in a DIM Module and attached to a record.
Need for IMSI

In cases where the IMSI is needed to meet billing requirements (for example, the MIN-MDN Separation feature is in use, or the MDN is not available), the IMSI may be appended to call-related AMA records, if it is available, by setting the RC/V ecp field Digit Information Module for IMSI to y.
Database Description for the Field

The database description for the Digit Information Module for IMSI field is Indicates whether the Digit Information Module for IMSI is to be appended to the AMA record.

The value of the Generic Context Identifier field for this feature is 10832 for IMSI.
Digits String Field

The Digits String field for this feature contains the IMSI.

The Digit Information Module will be appended to AMA records with the x2118, x2119, x2329-x2338, x2351, x2411, x2415, or x2421 structure codes if the following generation criteria are met:
The entry Append Digit Information Module for IMSI? on the ECP RC/V form is set to y. The mobile associated with the call record has an IMSI.
Issue 27
May 2004
33-9
401-610-133A
Result
This will cause an AMA module with module code 621 to be appended to the AMA records with a Generic Context Identifier of 10832 [E.212 International Mobile System Identity (IMSI) type].
Note
If IMSI is not available, the Digit Information Module with the IMSI is not be populated. If the KTF WNP feature is on, the mobile is programmed with a MINbased IMSI (not a true IMSI), then the MIN escape code + MIN are stored as IMSI in the DIM module.
For More Information

See Chapter 39, CDMA Full IMSI Feature, and Chapter 43, TDMA IMSI Feature. See also Module 621 - Digit Information Module on page 5-46.
33-10
Issue 27
May 2004
The MIN-MDN Separation feature does not have feature interactions with any other feature.
Issue 27
May 2004
33-11
401-610-133A
33-12
Issue 27
May 2004
34
34-1 34-1 34-2 34-2 34-2 34-2 34-2 34-3 34-3 34-4 34-4 34-5 34-6 34-6 34-6 34-6 34-6 34-6 34-7 34-8 34-8
Introduction For Further Information About the CDMA Packet Mode Data Services Family of Features

Introduction What is a CDMA Packet-Mode Data Services Feature? What Benefit Do These Features Provide for Service Providers? What Benefits Do These Features Give the Subscriber? Scope Limitation Introduction
AMA Impact
Call Types Event Types

Introduction What Is an Event Type? What is an AMA Event? Event Types for CDMA Packet Mode Data Services Features Event Type 010 Event Type 011 Introduction
Event Descriptions
Issue 27
May 2004
34-i
401-610-133A
What is an Event Description? CDMA Packet Mode Data Services Event Descriptions Differentiating Features by Use of Event Description Introduction About the Data Module About the Digital Event Module Precedence Suppressing Duplicate CDPD Records Suppressing Duplicate IP Records Introduction
34-8 34-8 34-8 34-10 34-10 34-10 34-10 34-10 34-11 34-11 34-11 34-12 34-12
Appended Module

Suppressing Data Collection Records

34-ii
Issue 27
May 2004
34
Introduction
This chapter discusses the following CDMA Packet-Mode Data Service features and explains how these features impact AMA:

3G1X Packet Data Services features (3833.0 and 3834.0) CDPD Packet Data Services (2038.0) IP Packet Data Services (4424.0)

For more information about these features, see the following documents:

3G-1X Data Features, 401-612-388 Cellular Digital Packet Data (CDPD) Optional Feature, 401-601-042 CDMA 2G Simple IP Packet Data Optional Feature, 410-612-353
Issue 27
May 2004
34-1
401-610-133A
About the CDMA Packet Mode Data Services Family of Features

Introduction
The family of CDMA Packet Data Services features all work in very similar fashions. The following sections describe the aspects that these features have in common.
What is a CDMA Packet-Mode Data Services Feature?

All the CDMA Packet-Mode Data Services features provide a subscriber having the appropriate mobile station configuration the ability to transmit and receive bursts of data over a packet data network via the CDMA air interface. This provides the infrastructure for mobile users with laptop computers or other data devices conforming to the TIA/EIA/IS-657 or TIA/EIA/IS-707 standard to access various data applications, such as e-mail, file transfer, field service automation, and fleet dispatch.
What Benefit Do These Features Provide for Service Providers?

Service providers are looking for ways to add new services to the existing wireless network. The explosive growth in Internet usage fuels service providers interest in providing cost-effective wireless Internet access. This feature allows service providers the ability to offer packet-mode data services, such as interconnection services between mobile stations and the Internet or other existing IP networks, using the existing CDMA network. It also allows service providers the ability to provide value-added services to mobile users in a CDMA cellular or PCS network. Services currently provided by on-line and Internet service providers such as E-mail, Universal Mailbox, database services, and web server are examples of value-added services.
What Benefits Do These Features Give the Subscriber?

Packet-mode data services provide mobile subscribers with a more economical method of accessing the packet data network when compared with circuit-mode asynchronous data services. The cost savings are two-fold. Firstly, user packets are sent over the Internet instead of the more costly PSTN network. Secondly,
34-2
Issue 27
May 2004
with packet-mode data services, the airlink will be dropped after a period of inactivity and then reconnected as data arrives. This savings of time is transparent to user applications and to the user, but results in significant cost savings. (Also, the subscriber can use the mobile for other services while the packet mode connection is in a dormant mode.)
Scope
Mobile origination, mobile reactivation, and network reactivation are supported for establishing an active packet data network connection. Mobile termination for initiating a packet data network connection is not supported.
Limitation
Inter-MSC paging is not supported for network reactivations.
Issue 27
May 2004
34-3
401-610-133A
AMA Impact
Introduction
The CDMA Packet Mode Data Services features added the following to AMA:

Two packet-data call types Two event types Several event descriptions
These event types and event descriptions are stored in one of two previouslyexisting modules: the Data Module or the Digital Event Module. All of these changes are described in the following section.
34-4
Issue 27
May 2004
Call Types
Two call types were created for the CDMA Packet-Mode Data Services feature. They are:

450 - Mobile-Originated Packet Data Call (x2329, x2333) 451 - Mobile-Terminated Packet Data Call (x2331, x2334)
These AMA call types were introduced to identify a call as a packet-mode data services call.
Issue 27
May 2004
34-5
401-610-133A
Event Types
Introduction
This section explains event types and lists the event types that were added to support the CDMA Packet Data Services features.
What Is an Event Type?

An Event Type is a three-digit number that reports an AMA event. Event types are used by service providers to categorize calls. A complete list of AMA event types is given in Table 4-37, "AMASE Table 453.
What is an AMA Event?

An AMA event is any occurrence that causes an AMA record to be generated. Examples of AMA events include a Virtual System Handoff or the occurrence of a CDMA Packet Data Link Layer Connection (LLC) Reactivation.
Event Types for CDMA Packet Mode Data Services Features

The following two event types were introduced for CDMA Packet Mode Data Services features:

010 - CDMA Packet Data LLC Open Service Option 011 - CDMA Packet Data LLC Reactivation Service Option
Event Type 010

The event type Packet Data Link Layer Connection Open was added to the AMA record to report that a Packet-Mode Data Services call has opened a Link layer connection. The event type will be recorded in either the Data Module or the Digital Event Module associated with the call record.
34-6
Issue 27
May 2004
Event Type 011

The event type Packet Data Link Layer Reactivation Open is added to the AMA record to report that a Packet-Mode Data Services call has reactivated a Link layer connection. The event type will be recorded in either the Data Module or the Digital Event Module associated with the call record.
Issue 27
May 2004
34-7
401-610-133A
Event Descriptions
Introduction
This section explains event descriptions and lists the event descriptions that were added to support the CDMA Packet Data Services features.
What is an Event Description?

Event Descriptions are codes that give further information about certain Event Types. Event Descriptions are also called Service Options. Not all event types have Event Descriptions, but all CDMA Packet Mode Data Services Event Types will have Event Descriptions.
CDMA Packet Mode Data Services Event Descriptions

The two event types for CDMA packet mode data services (010 and 011) share a common set of event descriptions. For event types 010 and 011, the event descriptions specify the type of CDMA Packet Mode Data Service used in the call. Table 4-47, "AMASE Table 497 Event Description Values for Event Types 010 and 011, lists these event descriptions.
Differentiating Features by Use of Event Description

For CDMA Packet Mode Data Services calls, the Event Description is used to tell which CDMA Packet Mode Data Service feature was used for the call.
34-8
Issue 27
May 2004
Table 34-1 on page 34-9 lists all CDMA Packet Mode Data Services features for which AMA information is available, and lists the Event Descriptions used by each feature. Table 34-1. CDMA Packet Mode Data Services Features and the Event Descriptions Used by Each with feature ID... 4424.0 uses the following Event Description...
This feature...
2G CDMA Packet Switched Data*
00007 = 9.6K IP Service (9.6 Kbps IP Revision 0) 00015 = 14.4K IP Service (14.4 Kbps IP Revision 04103 = 9.6K IP Service, Version 1 (9.6 Kbps IP Revision 1)
CDMA Packet Switched Data
2038.0
00008 = 9.6K CDPD Service (9.6 Kbps CDPD 00016 = 14.4K CDPD Service (14.4 Kbps CDPD 04104 = 9.6K CDPD Service, Version 1 (9.6
3G-1X Packet Data Service
3833.0 and 3834.0
00033 = 3G-1X IP Service 00034 = 3G-1X CDPD Service
* Often referred to as 2G IP. Often referred to as 2G CDPD.
Issue 27
May 2004
34-9
401-610-133A
Appended Module
Introduction
Either the Data Module or the Digital Event Module will be attached to the call record for a CDMA Packet Mode Data Services call. The module is used to store the Event Type and Event Description for the call. This section tells when each module is used and tells where in this manual to find an explanation of each module.
About the Data Module

The Data Module is the default module used to store the CDMA Packet Mode Data Services Event Type and Event Description for the call. For generation criteria and other information about the Data Module, read Module 344Data Module on page 5-38. NOTE: For a CDMA Packet Mode Data Services call, the Linking Code field in the Data Module will always contain a zero.
About the Digital Event Module

If the Data Module is not turned on, the Digital Event Module is turned on, and if the Multiple Vocoding (MVC) feature is active in the FAF file, then the Digital Event Module will be used to store the CDMA Packet Mode Data Services Event Type and Event Description for the call. For generation criteria and other information about the Digital Event Module, read Module 334Digital Event Module on page 5-34. NOTE: A maximum of four Digital Event Modules are allowed. Therefore, if a Data Module is present, and Digital Event Modules are also generated, a maximum of three Digital Event Modules can be generated for this particular record.
Precedence
If both modules are turned on, the Data Module takes precedence.
34-10
Issue 27
May 2004
Suppressing Data Collection Records

Suppressing Duplicate CDPD Records
Accounting data for CDPD packet data service is collected at the Interworking Function (IWF), which produces its own AMA records. Thus, some service providers may wish to turn off the ECPC-generated AMA record collection for these calls. A service provider can turn off AMA record generation for CDPD packet data calls by setting the value of the AMA Suppression for CDPD Service parameter on the ecp form to y.
Suppressing Duplicate IP Records

Accounting data for IP packet data service is collected at the Interworking Function (IWF), which produces its own AMA records. Thus, some service providers may wish to turn off the ECPC-generated AMA record collection for these calls. A service provider can turn off AMA record generation for IP packet data calls by setting the value of the AMA Suppression for IP Service parameter on the ecp form to y.
Issue 27
May 2004
34-11
401-610-133A
Introduction
Because the CDMA Packet-Mode Data Services features are data features, they cause many voice features to be disabled. For example, the ECPC disables the call waiting feature during CDMA Packet-Mode Data Services calls. To see if the CDMA Packet-Mode Data Services feature impacts a particular feature, see the optional feature document for the particular CDMA Packet Data feature.
34-12
Issue 27
May 2004
35
35-1 35-1 35-2 35-2 35-2 35-2 35-2 35-2 35-3

Introduction What is the AMA Calling Party Category Information Feature? How Does It Work? Layout of Field Limitations
Issue 27
May 2004
35-i
401-610-133A
35-ii
Issue 27
May 2004
35
Introduction
This chapter provides information on the AMA Calling Party Category Information feature and describes how AMA functionality is affected by this feature. This chapter also summarizes feature interactions of the AMA Calling Party Category Information feature with other features.

More detailed information about this feature can be found in 401-612-213, AMA Calling Party Category Information Optional Feature.
Issue 27
May 2004
35-1
401-610-133A
Feature Description
Introduction
This section describes the AMA Calling Party Category Information feature.
What is the AMA Calling Party Category Information Feature?

The AMA Calling Party Category Information feature provides a category code and signaling type with an incoming call. This information gives service providers the ability to distinguish calls for which the calling party pays from calls for which the mobile subscriber pays.
How Does It Work?

This feature stores the Calling Party Category and signaling type in the Calling Party Category field in the base structure code layout.
Layout of Field
The Calling Party Category field and signaling type are defined in Table 4-49 "AMASE Table 566" on page 4-79.
Limitations
At present, only land-to-mobile calls can use this feature.
35-2
Issue 27
May 2004
The Calling Party Category field is filled with zeroes unless ANI or CPN information is present. For more information on ANI, read Chapter 17, AMA Containing Incoming Automatic Number Identification (AMANI) Feature. For more information on Calling Party Number, read Chapter 18, Calling Number Identification Presentation and Restriction Capability Feature.
Issue 27
May 2004
35-3
401-610-133A
35-4
Issue 27
May 2004
36
36-1 36-1 36-2 36-2 36-2 36-2 36-2 36-2 36-3 36-3 36-3 36-4 36-6 36-6 36-6 36-6 36-7 36-7 36-8 36-8 36-9

Introduction What is the WNP Feature? Scope Other Types of Portability Not Covered in Wireless Number Portability Introduction Need for the Feature
Background

Glossary of WNP Terms How It Works

Introduction NP-SCP Database Call Setup (by the Originating Switch) Call Setup (by the Recipient Switch) Tandem MSC Introduction
AMA Impact
Wireless Number Portability Module
Issue 27
May 2004
36-i
401-610-133A
Introduction Purpose of the Wireless Number Portability Module Wireless Number Portability Module Definition Module Generation Criteria for Wireless Number Portability Feature Four Possible Request Response Results No Query Failure Time-Out Conditions Return Error Message No Query Performed For Further Information Introduction Purpose of the Digit Information Module Jurisdiction Indicator Parameter Generic Context Identifier for JIP Value of JIP Module Generation Criteria for Wireless Number Portability Feature For Further Information Dependency For Further Information
36-9 36-9 36-9 36-9 36-10 36-10 36-10 36-10 36-11 36-11 36-12 36-12 36-12 36-12 36-12 36-12 36-12 36-13 36-14 36-14 36-14
Digit Information Module with JIP Information

Feature Interaction

36-ii
Issue 27
May 2004
36
Introduction
This chapter provides information on the Wireless Number Portability (WNP) feature and describes how AMA functionality is affected by this feature. This chapter also lists feature interactions of the WNP feature with other features.

More detailed information about this feature can be found in 401-612-195, Wireless Number Portability Optional Feature.
Issue 27
May 2004
36-1
401-610-133A
Feature Description
Introduction
This section describes the WNP feature.
What is the WNP Feature?

The WNP feature provides service provider portability, which gives a wireless subscriber the ability to port a telephone number from one service provider to another service provider, both within the subscribers service area. This gives a subscriber the ability to retain his or her telephone number when changing to a different service provider within the subscribers service area. This change in service providers can be from wireless to wireless, from wireless to landline, or from landline to wireless.
Scope
The Wireless Number Portability feature is used only in the North American Region (NAR). WNP is designed to work with the North American Numbering Plan (NANP), which is based on a 10-digit MON.
Other Types of Portability

Two other types of portability are possible:
Location portability, which gives a mobile subscriber the ability to retain the same telephone number when moving from one location to another location that is outside the subscribers service area. Service portability, which gives a mobile subscriber the ability to retain the same telephone number when moving from one telecommunication service to another telecommunication service provided by the same service provider.
Not Covered in Wireless Number Portability

Location portability and service portability are not included in the Wireless Number Portability feature. Wherever possible, however, flexibility has been designed into the Wireless Number Portability to help in possible future implementation of these types of portability.
36-2
Issue 27
May 2004
Background
Introduction
This section describes the need for this feature and the FCC requirements governing its creation and development.
Need for the Feature

The Federal Communications Commission (FCC) Number Portability Report and Order, CC Docket 95-116, mandates that all Commercial Mobile Radio Service (CMRS) providers provide the capability to deliver calls from their network to ported numbers, that is, numbers that have been transferred from one telephone to another.
Issue 27
May 2004
36-3
401-610-133A
Glossary of WNP Terms

To understand WNP, you must know the following terms:
Donor SwitchThe switch that the MDN was ported from. (See Recipient Switch.) Jurisdiction Information Parameter (JIP)The address of the Originating MSC. This number is six digits long, equating to the NPA-NXX of the Location Routing Number (LRN). Location Routing Number (LRN)In North America, a 10-digit number that uniquely identifies an exchange. Every ported subscribers MDN is associated with an LRN (assigned by the service provider). This number will be used for routing a call to the ported subscriber. The number will point to the entry point exchange to which the calls will be routed for the MDN. Mobile Directory Number (MDN)A type of directory number. In North America, a 10-digit directory number in the format of NPA-NXX-XXXX. Mobile Station Identifier (MSID)A number to identify the mobile. This number could be a 10-digit Mobile Identification Number (MIN) in the NPANXX-XXXX format or an E.212 International Mobile Station Identity (IMSI). MobilityThe ability for a wireless subscriber to temporarily move from one location to another and access the wireless service. Mobility is not location portability. Non-Ported NumberThis term is used for a directory number (DN) that might have been a ported number but turned out not to be a ported number. This situation occurs because ported numbers are tracked on an NPA-NXX basis, not on a full 10-digit directory number basis. Once a number from a particular NPA-NXX has been ported, every number belonging to that NPA-NXX is considered suspect. A Number Portability Request must now be made every time a number within that NPA-NXX is called. Any remaining number that still belongs to that NPA-NXX group but has not been ported is called a non-ported number. Number Portability SCPA network element that contains a database of the mapping of a subscribers MDN to a Location Routing Number. This network element shall be capable of receiving and processing ANSI-41 number portability query messages and responding to the querying network entity. Number Portability TriggerA trigger in the MSC that will result in a Number Portability Request if the specific criteria for the trigger are met.
36-4
Issue 27
May 2004
Ported BlockA block of numbers (signified by a common NPA-NXX) that contains one or more ported numbers. Any number belonging to the ported block must now be considered as a potential ported number and a Number Portability Request must be done when performing call processing for that number. Recipient SwitchThe switch that the MDN was ported to. (See Donor Switch.)
Issue 27
May 2004
36-5
401-610-133A
How It Works
Introduction
This section gives a brief overview of how the WNP feature works, from an AMA perspective. For a more complete discussion of how this feature works, read the Wireless Number Portability Optional Feature, 401-612-195.
NP-SCP Database
The WNP feature uses a database, the Number Portability-Signaling Control Point (NP-SCP) database, to store information about ported numbers. The NP-SCP database keeps track of two items for each ported number:

The subscribers Mobile Directory Number (MDN) The Location Routing Number of the switch that the ported number currently resides on (the Recipient Switch).
Call Setup (by the Originating Switch)

Once the WNP feature has been installed in a Service Providers network, the Flexent/AUTOPLEX wireless network call processing software will begin sending ANSI-41 Number Portability Request messages to the NP-SCP database for call attempts. (Number Portability Request messages will not be sent for every call attempt; Number Portability Request messages will only be sent for call attempts in cases where the NPA-NXX of the called number belongs to a ported block.) The Number Portability Request message sent contains the subscribers MDN. The NP-SCP database then sends back a Number Portability Request Response message. This message either is empty (indicating that the calling number is not a ported number) or it contains the Location Routing Number of the Recipient Switch that is currently handling the ported subscribers MDN. The call processing software then uses this information to set up the call. If an LRN is received, indicating that the terminating number is indeed a ported number, then the call processing software will carry out the following steps:
The Wireless Number Portability Module will be appended to the AMA record for the originating call. This module will contain the LRN information that was returned in the Request Response message. A Jurisdiction Information Parameter (JIP) containing the LRN of the originating MSC will be sent to the terminating MSC.
36-6
Issue 27
May 2004
Call Setup (by the Recipient Switch)

The Recipient Switch completes the call setup. The Recipient Switch also adds a Digit Information Module to the AMA record for the call termination. This Digit Information Module contains the JIP that was received from the originating MSC.1
Tandem MSC
A Number Portability query can also be performed by a tandem MSC.
The Digit Information Module is ONLY added in cases where the Recipient Switch receives a JIP parameter in the call setup information from the Originating Switch.
Issue 27
May 2004
36-7
401-610-133A
AMA Impact
Introduction
The WNP feature uses two modules to store WNP-related information:

The Wireless Number Portability Module The Digit Information Module with Jurisdiction Information Parameter.
Each is explained below.
36-8
Issue 27
May 2004
Wireless Number Portability Module

Introduction
The section describes the Wireless Number Portability Module.
Purpose of the Wireless Number Portability Module

The Wireless Number Portability Module is used to store the Location Routing Number (LRN) of the Recipient Switch for a ported call or to provide status of the query if the query fails.
Wireless Number Portability Module Definition

The Wireless Number Portability Module contains the following fields:

Module Code Party Identifier Location Routing Number Service Provider ID Location Supporting Info
For a definition of these fields, read Module 720Wireless Number Portability Module on page 5-73.
Module Generation Criteria for Wireless Number Portability Feature

AMA appends the Wireless Number Portability Module to AMA records with structure codes x2118, x2119, x2329, x2330, x2332, and x2333 if the following conditions are true:

Either the Wireless Number Portability FAF or the KTFWNPT FAF is active. The ecp form field Append Wireless Number Portability Module to AMA records? is set to y via RC/V and if one of the following is true:
Issue 27
May 2004
36-9
401-610-133A
A Wireless Number Portability Request has been performed (a query to get the Location Routing Number [LRN] of the ported telephone number). An LRN was received in the incoming ISUP call, so a Request is not necessary; the information is already at hand. (This can happen with tandem or with terminating MSCs.)
Four Possible Request Response Results

There are four possible Request Response results from the MSCs Request message to the NP-SCP. They are:

The MSC receives an LRN from the NP-SCP. The MSC receives an empty message (that is, the number in question is not a ported number). A time-out condition occurs at the MSC before the return result is received. A Return Error or a Reject message is received.
No Query Failure
This value (01) will be returned in cases where a WNP query has been performed and an answer has been received. In these cases, the Supporting Information field will be populated with No Query Failure. This includes both of the following scenarios:
The MSC received a ported number back from the query (Request message). The MSC received a return result message with an empty parameter, indicating that the called number is a non-ported number.
Time-Out Conditions
If the WNP query has been performed for a ported mobile and the query timed out with no response, the supporting information field will be populated with No query response message received (02) for time-out conditions.
Return Error Message

If the WNP query has been performed for a ported mobile and the MSC received a Return Error message the supporting information field will be populated with Return Error (05) for Received Number Portability Return Result.
36-10
Issue 27
May 2004
No Query Performed
If the WNP query has not been performed the supporting information field will be populated with the value of (09), indicating that no query was performed. This condition occurs in cases where a query has already been performed and the results have been received. For instance, if a tandem MSC receives the LRN in the incoming ISUP message, there is no need to do another query. For these cases, an AMA record will be generated at the tandem MSC, with the value of No Query Performed.

For more about the Wireless Number Portability Module, read Module 720 Wireless Number Portability Module on page 5-73.
Issue 27
May 2004
36-11
401-610-133A
Digit Information Module with JIP Information

Introduction
This section describes the Digit Information Module with JIP information that is produced by the Wireless Number Portability feature.
Purpose of the Digit Information Module

The Digit Information Module is used to store a number; for the WNP feature, this is the Jurisdiction Information Parameter (JIP) number.
Jurisdiction Indicator Parameter

The portability process requires that the Originating Switch send its address to the Recipient Switch. The Originating Switch does this using a six-digit field called the Jurisdiction Information Parameter (JIP). This parameter is sent with the call setup information to the Recipient Switch. Note that the JIP only has to be 6 digits long, since only the NPA-NXX is needed to identify the Originating MSC.
Generic Context Identifier for JIP

The Generic Context Identifier value for JIP is 10831. For the layout of the generic context identifier and an explanation of its BCD characters, see Table 4-24 on page 4-39.
Value of JIP
The value of the JIP is stored as a six-digit number in the Digits Recorded field in the Digit Information Module.
Module Generation Criteria for Wireless Number Portability Feature

The Digit Information Module with Jurisdiction Information Parameter (JIP) Information will be appended to AMA records with the x2118, x2119, x2331, x2334, and x2335 structure codes if the following generation criteria are met:
36-12
Issue 27
May 2004
The Digit Information Module is activated via ECP RC/V because the entry Append Jurisdiction Information Parameter to AMA Records? is ON. The Wireless Number Portability feature is active. A JIP has been received at the Recipient Switch.

For an explanation of the Digit Information Module, read Module 621 - Digit Information Module on page 5-46.
Issue 27
May 2004
36-13
401-610-133A
Feature Interaction
Dependency
The WNP feature depends upon the following feature to offer Number Portability (NP) to wireless subscribers:
Separation of MSID-MIN2

For AMA information on the Separation of MSID-MIN feature, read Chapter 33, MIN-MDN Separation Feature. For more information about the interaction of the WNP feature with other features, read the Wireless Number Portability Optional Feature, 401-612-195.
The Separation of MSID-MIN feature is necessary only to offer Number Portability to wireless subscribers (the second part of the FCC mandate). If you are only using Wireless Number Portability to port wireline numbers to wireless numbers, you do not need the Separation of MSID-MIN feature.
36-14
Issue 27
May 2004
37
37-1 37-1 37-1 37-1 37-3 37-3 37-3 37-4 37-4 37-4 37-4 37-4 37-5 37-5 37-5 37-6 37-6 37-6 37-6 37-6 37-7 37-7 37-8
Introduction

Supported Technologies About FAFs for Flexible Alerting For Further Information Introduction Need for the Feature What is the Flexible Alerting Feature? Pilot DN Other DNs About Flexible Alerting Groups Subscriber Assignment Feature Benefits for the Service Provider Feature Benefits for the Subscriber For Further Information Introduction Control of AMA Record Generation for Unanswered Call Legs Control of AMA Modules for Flexible Alerting Subscriber-Controlled Change in Activation Status Changes in Billing of AMA Records for Flexible Alerting Two New Generic Context Identifiers
Feature Description

AMA Impact

Digit Information Module
Issue 27
May 2004
37-i
401-610-133A
Introduction Purpose of the Digit Information Module Two Generic Context Identifiers Module Generation Criteria for DIM Storing the Pilot DN Module Generation Criteria for DIM Storing the FA Leg DN For Further Information Introduction Purpose of the BIN Module BIN Module Generation Criteria For Further Information
37-8 37-8 37-8 37-8 37-8 37-9 37-10 37-10 37-10 37-10 37-11 37-12
BIN Module


With the Special Routing Feature... 37-12 With the Increased Court-Ordered Surveillance (ICOS) Feature 37-12
37-ii
Issue 27
May 2004
37
Introduction
This chapter introduces the Flexible Alerting feature and describes the two modules used for this feature. The chapter also explains how the Flexible Alerting feature affects AMA records.
Supported Technologies
This chapter covers both the TDMA/Analog implementation of the Flexible Alerting feature and the Wireless Intelligent Network (WIN)-based implementation of this feature.
About FAFs for Flexible Alerting

Multiple Feature Activation Files (FAFs) exist for the TDMA/Analog version of this feature. A separate FAF exists for the WIN-Based version of this feature. See the appropriate optional feature document for the correct FAF information for your feature

For more information about the TDMA/Analog implementation of this feature, read the Flexible Alerting Optional Feature document, 401-612-223.
Issue 27
May 2004
37-1
401-610-133A
For more information about the WIN implementation of this feature, read the WINBased Flexible Alerting Optional Feature document, 401-612-518.
37-2
Issue 27
May 2004
Feature Description
Introduction
This section gives an overview of the Flexible Alerting feature.

As a result of the tremendous growth in the wireless telephone subscriber base in recent years, many wireless subscribers now have one or more wireless phones along with one or more wired phones. Some phones may be dedicated for personal use, some for business use and even some for shared business and personal use. The increasing number of phones per subscriber has certainly stimulated subscribers to originate calls. However, since each wireless and wired phone is usually assigned a different DN, attempting to reach the intended subscribers is becoming increasingly difficult. In particular, some or all of the following problems can result:
The called subscribers have to advertise more than one DN to potential callers. The caller has to know of more than one DN to use to reach the called subscribers. The caller may have to attempt to call multiple DNs. If the first call attempt does not reach the called subscribers, then the alternate DNs are tried. This can be burdensome to the caller given the amount of time it may take to try to reach the subscriber. In addition, the caller may not be certain which DN to try first (wireless, wired, personal, business) to reach the called subscribers.
The problem of a lower call completion rate also implies less network usage than would be expected, given the increasing number of phones per subscriber. The Flexible Alerting feature provides a solution to these problems by providing a way for called subscribers to provide one number to potential callers. This one number can be used to reach called subscribers at any of the called subscribers phones.
Issue 27
May 2004
37-3
401-610-133A
What is the Flexible Alerting Feature?

The Flexible Alerting feature provides a way for a mobile subscriber to combine more than one DN into one group represented by one directory number (the pilot DN). When that one number (the pilot DN) is called, all the phones of all the DNs represented in the group are alerted simultaneously. When the call is answered on any DN in the group, the network will complete the call to the answered DN and abandon the attempt to alert the other DNs.
Pilot DN
A pilot DN is the single directory number that identifies the Flexible Alerting Group. Incoming calls that use Flexible Alerting come to the pilot DN. Each Flexible Alerting Group has only one pilot DN. Any call that comes to the pilot DN will cause Flexible Alerting to all DNs currently part of the Flexible Alerting Group. The pilot DN may be a mobile DN, or it may be a special DN that is not associated with a particular mobile phone.
Other DNs
The non-pilot DNs in a Flexible Alerting Group can receive calls directly, as well as via the pilot DN. If a non-pilot DN receives a call directly, the other members of the Flexible Alerting Group will not be alerted about the incoming call. A given mobile DN or PSTN DN can be a non-pilot member for more than one Flexible Alerting Group.
About Flexible Alerting Groups

The DNs in a Flexible Alerting Group can be any combination of mobile phone DNs and/or PSTN DNs. The list of DNs in a Flexible Alerting Group will be maintained at the Stand-alone HLR/Wireless Service Control Point and administered by the service provider.
Subscriber Assignment
A subscriber can be assigned as a demand or permanent subscriber. A demand subscriber has control over his/her activation status in a given Flexible Alerting Group, where a permanent subscriber has no such control.
37-4
Issue 27
May 2004
Feature Benefits for the Service Provider

Potential benefits to the service provider include:
Increased revenue as a result of an increased call completion rate, and associated network usage. From a service providers perspective, completing a call is preferential to the caller abandoning the attempt before answering, or leaving a short message. Revenue for the feature activation and monthly usage fees.
Feature Benefits for the Subscriber

The potential benefits to subscribers are readily apparent.
The called subscriber does not have to advertise all DNs to potential callers. Advertising only one DN (the pilot DN) may be satisfactory. The caller does not have to know more than one DN to reach the called subscriber, or attempt to use more than one DN. The probability of completing the call on the first attempt is clearly maximized. The called subscriber does not have to set up call forwarding from one DN to another in the group, in an attempt to receive important calls as soon as possible.

For an in-depth look at the Flexible Alerting feature and its feature dependencies, read the Flexible Alerting Optional Feature document, 401-612-223. See also the WIN-Based Flexible Alerting Optional Feature document, 401-612-518.
Issue 27
May 2004
37-5
401-610-133A
AMA Impact
Introduction
This section describes the impact on AMA of the Flexible Alerting feature.
Control of AMA Record Generation for Unanswered Call Legs

In AMA, AMA records are produced for all call attempts, whether they are answered or not. The service provider has control of AMA record generation for records reporting unanswered call legs that occur as a result of Flexible Alerting invocation. The control is provided via the ecp RC/V entry AMA recording for unanswered multi-leg termination?. If that entry is set to n, then no AMA record will be generated for an unanswered call leg that occurs as a result of Flexible Alerting invocation. Also, the REPT:CP IMMEDIATE BILLING message will be suppressed for each unanswered call leg.
Control of AMA Modules for Flexible Alerting

The Flexible Alerting feature uses the following two AMA modules:

Digit Information Module (DIM) Billing Identification Module (BIN)
The service provider can control whether AMA modules are appended to the generated AMA records for the Flexible Alerting call via the ecp RC/V entry Appending AMA module for Flexible Alerting?. If that entry is set to y, then the Digit Information Module and the BIN Module will be appended to the generated AMA records for all call legs for Flexible Alerting calls. See Digit Information Module on page 37-8 and BIN Module on page 37-10 for more about these modules and the Flexible Alerting feature.
Subscriber-Controlled Change in Activation Status

Each time a subscriber activates or deactivates a particular DN in a given Flexible Alerting Group, an AMA record with structure code x2411 will be generated. One or more of the following service features (AMASE 2002) will appear in the record:

Flexible Alerting (067) PIN (800)
37-6
Issue 27
May 2004
Special Cellular Networking (100)
If the ecp RC/V entry Append AMA Module for Flexible Alerting? is set to y and the pilot DN exists, then the Digit Information Module containing the pilot DN will be appended to the generated AMA record with structure code x2411.
Changes in Billing of AMA Records for Flexible Alerting

An AMA record is generated for each call leg attempted during Flexible Alerting invocation. These records have the following differences from non-Flexible Alerting AMA records:
These records are billed to the pilot DN. This means that the pilot DN is stored in the subscriber number field instead of the mobile DN. Then a Digit Information Module is added to the record to store the mobile DN. These records are linked together by a BIN number. This is done by adding a BIN module to each record.
Two New Generic Context Identifiers

Two Generic Context Identifier values have been created for Flexible Alerting:

90015 - FA Leg Directory Number, that is, the mobile directory number 90016 - FA Pilot DN.
Issue 27
May 2004
37-7
401-610-133A

Introduction
This section describes the Digit Information Module (DIM) as it is used by the Flexible Alerting feature.

The Digit Information Module is used to store a digit string. The Generic Context Identifier field indicates the type of digits that are stored in the Digit String field.
Two Generic Context Identifiers

Two Generic Context Identifier values are used in the DIM for Flexible Alerting:

90015 - FA Leg Directory Number, that is, the mobile directory number 90016 - FA Pilot DN.
For the layout of the generic context identifier and an explanation of its BCD characters, see Table 4-24 on page 4-39.
Module Generation Criteria for DIM Storing the Pilot DN

The Digit Information Module storing the pilot DN will be appended to the AMA record with structure code x2411 if the following criteria are met:
The Digit Information Module is activated via ecp RC/V entry Append AMA modules for Flexible Alerting?. The Pilot DN exists. The Flexible Alerting feature is active.
Module Generation Criteria for DIM Storing the FA Leg DN

The Digit Information Module storing the leg directory number for the Flexible Alerting call (that is, the mobile DN) will be appended to the AMA records with structure codes x2331, x2334, or x2335 if the following criteria are met:
37-8
Issue 27
May 2004
The Digit Information Module is activated via ecp RC/V entry Append AMA modules for Flexible Alerting?. The Pilot DN exists. The Flexible Alerting feature is active.
The Digit Information Module storing the leg directory number for the Flexible Alerting call (that is, the mobile DN) will be appended to the AMA records with structure codes x2329, x2330, x2332, or x2333 if the following criteria are met:
The Digit Information Module is activated via ecp RC/V entry Append AMA modules for Flexible Alerting?. The ecp RC/V entry AMA recording for unanswered multi-leg termination is set to y. The Pilot DN exists. The Flexible Alerting feature is active. The call has one of the following custom calling features: Call Forwarding or Special Cellular Networking (that is with service feature code 012, 014, or 100 as listed in Table 2002 Service Feature Code on page 4-119).

Issue 27
May 2004
37-9
401-610-133A
BIN Module
Introduction
A module called the Billing Identification Number (BIN) module was added for the Flexible Alerting feature. This module is described in this section.
Purpose of the BIN Module

The purpose of the BIN Module is to provide a unique number that can be used to link separate AMA records that belong to the same call.
BIN Module Generation Criteria

The BIN Module will be appended to the AMA records with structure codes x2331, x2334, or x2335 if the following criteria are met:
The BIN Module is activated via ecp RC/V entry Append AMA modules for Flexible Alerting?. The ecp RC/V entry AMA Recording for Unanswered Multi-leg termination is set to y. The Pilot DN exists. A Flexible Alerting feature is active in the FAF file. The BIN number exists.
The BIN module will be appended to the AMA records with structure codes X2329, x2330, x2332, or x2333 if the following criteria are met:
The BIN Module is activated via ecp RC/V entry Append AMA modules for Flexible Alerting?. The Pilot DN exists. The Flexible Alerting feature is active. The call has one of the following custom calling features: Call Forwarding or Special Cellular Networking (that is with service feature code 012, 014, or 100 as listed in Table 2002 Service Feature Code on page 4-119).
The BIN number exists.
37-10
Issue 27
May 2004

For more about the BIN Module, read Module 900Billing Identification Number Module on page 5-78.
Issue 27
May 2004
37-11
401-610-133A
This section describes AMA-related feature interactions of the Flexible Alerting feature with other features.
With the Special Routing Feature

If the Flexible Alerting feature is on while the Special Routing feature is active, any AMA records that are produced for Special Routing will have the BIN module appended and will contain the Pilot DN number for the call.
With the Increased Court-Ordered Surveillance (ICOS) Feature

If the Flexible Alerting feature is on while the ICOS feature is active, any AMA records that are produced for ICOS will have the BIN module appended and will contain the Pilot DN number for the call.
37-12
Issue 27
May 2004
ANSI-41 Billing Module and ANSI41 Billing Module with Service Type Features
38
38-1 38-1 38-2 38-2 38-2 38-2 38-2 38-3 38-4 38-4 38-4 38-4 38-4 38-4 38-5 38-5 38-5 38-6 38-6 38-6
Introduction For Further Information Feature Description for ANSI-41 Billing Module Feature

Introduction What is the ANSI-41 Billing Module Feature? About the DMH Need for the Feature Benefit
Feature Description for ANSI-41 Billing Module with Service Type Feature

Introduction What is the ANSI-41 Billing Module with Service Type Feature? Service ID versus Service Type About the DMH Need for the Feature AMA Impact of the ANSI-41 Billing Module Feature AMA Impact of the ANSI-41 Billing Module with Service Type Feature Introduction Purpose of the Digit Information Module
AMA Impact


Issue 27
May 2004
38-i
401-610-133A
New Generic Context Identifiers Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Account Code Digits Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Alternate Billing Digits Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Billing Digits Module Generation Criteria for the ANSI-41 Billing Module Feature for the Digit Information Module Storing ANSI-41 DMH Redirection Indicator Module Generation Criteria for DIM Storing Service ID For Further Information
38-6 38-7 38-7 38-7
38-8 38-8 38-8 38-9 38-10
Feature Dependencies Feature Interactions
38-ii
Issue 27
May 2004
38
Introduction
This chapter provides information on the following two features:

ANSI-41 Billing Module ANSI-41 Billing Module with Service Type

More detailed information about these features can be found in 401-612-216, ANSI-41 Billing Module and Billing Module with Service Type Optional Feature document.
Issue 27
May 2004
38-1
401-610-133A
Feature Description for ANSI-41 Billing Module Feature

Introduction
This section describes the ANSI-41 Billing Module feature.
What is the ANSI-41 Billing Module Feature?

The ANSI-41 Billing Module feature adds the following ANSI-41 Revision C parameters to the AMA records:

ANSI-41 DMH Account Code Digits ANSI-41 DMH Alternate Billing Digits ANSI-41 DMH Billing Digits ANSI-41 DMH Redirection Indicator
These parameters are used by Wireless Intelligent Network (WIN) applications. The Digit Information Module will be used to store these parameters. These ANSI-41 Revision C billing parameters will be used by WIN applications to direct the MSC on how to bill a call. These parameters are generic enough to be used by any WIN (or non-WIN) application.
About the DMH

The DMH mentioned in the ANSI-41 parameter titles merely reflects the title given in the IS-124 billing standard. It does not imply a need for either of these features to support the IS-124 billing standard.

New enhanced services provided by the Wireless Intelligent Network (WIN) will require additional billing capabilities on the Mobile Switching Center (MSC). Currently, the MSC has a limited number of fields in the AMA record to support enhanced services. As more customers introduce WIN applications into their networks, more requests are made to manipulate the existing AMA record to support the billing of their particular WIN service. Additionally, one customers request often may contradict a request from another customer.
38-2
Issue 27
May 2004
This feature solves these problems by supply new billing parameters that can be used to store additional information but are flexible enough to be used by many different WIN (or non-WIN) applications.
Benefit
The ANSI-41 Billing Module feature will allow customers ultimate flexibility in billing enhanced services provided by the WIN.
Issue 27
May 2004
38-3
401-610-133A
Feature Description for ANSI-41 Billing Module with Service Type Feature
Introduction
This section describes the ANSI-41 Billing Module with Service Type feature.
What is the ANSI-41 Billing Module with Service Type Feature?

The ANSI-41 Billing Module with Service Type feature adds the following parameter to the parameters available with the earlier ANSI-41 Billing Module feature:
Service ID
Service ID versus Service Type

The term Service Type and Service ID are both used to describe the new billing parameter added by the ANSI-41 Billing Module with Service Type feature. The confusion arises because Service ID is the official name for this parameter. However, in the feature, the parameter is called Service Type. In this documentation, Service Type will be used when referring to the name of the feature, and Service ID will be used for the parameter itself. Both terms refer to the same parameter.
About the DMH

The DMH mentioned in the ANSI-41 parameter titles merely reflects the title given in the IS-124 billing standard. This DMH has nothing to do with the Data Message Handler billing standard.

Although the additional billing capabilities on the Mobile Switching Center (MSC) provided by the ANSI-41 Billing Module feature were helpful, the need was apparent for a Service Type parameter, which is being added in this feature.
38-4
Issue 27
May 2004
AMA Impact
AMA Impact of the ANSI-41 Billing Module Feature
The ANSI-41 Billing Module feature adds the following new Generic Context Identifiers to the Digit Information Module (DIM):

ANSI-41 DMH Account Code Digits (90006) ANSI-41 DMH Alternate Billing Digits (90007) ANSI-41 DMH Billing Digits (90008) ANSI-41 DMH Redirection Indicator (90022)
AMA Impact of the ANSI-41 Billing Module with Service Type Feature
The ANSI-41 Billing Module with Service Type feature adds the following new Generic Context Identifier to the DIM:
Service ID (90009)
Issue 27
May 2004
38-5
401-610-133A

Introduction
This section describes the Digit Information Module that is used by the ANSI-41 Billing Module feature.

The Digit Information Module is used to store a digit string. For the ANSI-41 Billing Module feature, this string can be any of the following numbers:

ANSI-41 DMH Account Code Digits ANSI-41 DMH Alternate Billing Digits ANSI-41 DMH Billing Digits ANSI-41 DMH Redirection Indicator
For the ANSI-41 Billing Module with Service Type feature, this string is the
Service ID
New Generic Context Identifiers

The following new Generic Context Identifier values have been created for the features discussed in this chapter. For the ANSI-41 Billing Module feature:

90006 - ANSI-41 DMH Account Code Digits 90007 - ANSI-41 DMH Alternate Billing Digits 90008 - ANSI-41 DMH Billing Digits 90022 - ANSI-41 DMH Redirection Indicator
For the ANSI-41 Billing Module with Service Type feature:
90009 - Service ID
For the layout of the generic context identifier and an explanation of its BCD characters, see Table 4-24 on page 4-39.
38-6
Issue 27
May 2004
Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Account Code Digits
The Digit Information Module storing the ANSI-41 Account Code Digits will be appended to AMA records with the x2329, x2330, x2331, x2332, x2333, x2334, and x2335 structure codes if the following generation criteria are met:

The ANSI-41 Billing Module Feature is activated via the ecp form. The ANSI-41 Billing Module feature is active. ANSI-41 Account Code Digits exist.
Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Alternate Billing Digits
The Digit Information Module storing the ANSI-41 Alternate Billing Digits will be appended to AMA records with the x2329, x2330, x2331, x2332, x2333, x2334, and x2335 structure codes if the following generation criteria are met:

The ANSI-41 Billing Module feature is activated via the ecp form. The ANSI-41 Billing Module feature is active. ANSI-41 Alternate Billing Digits exist.
Module Generation Criteria for ANSI-41 Billing Module Feature for DIM Storing ANSI-41 DMH Billing Digits
The Digit Information Module storing the ANSI-41 Billing Digits will be appended to AMA records with the x2329, x2330, x2331, x2332, x2333, x2334, and x2335 structure codes if the following generation criteria are met:

The ANSI-41 Billing Module feature is activated via the ecp form. The ANSI-41 Billing Module feature is active. ANSI-41 Billing Digits exist.
Issue 27
May 2004
38-7
401-610-133A
Module Generation Criteria for the ANSI-41 Billing Module Feature for the Digit Information Module Storing ANSI-41 DMH Redirection Indicator
The Digit Information Module Storing ANSI-41 DMH Redirection Indicator will be appended to AMA records with the x2329, x2330, x2331, x2332, x2333, x2334, and x2335 structure codes if the following generation criteria are met:
The Digit Information Module is activated via ecp RC/V entry Append ANSI-41 Billing Modules? The ANSI-41 Billing Module feature is active. An ANSI-41 DMH Redirection Indicator exists.
Module Generation Criteria for DIM Storing Service ID

The Digit Information Module storing the Service Type will be appended to the AMA record with structure codes x2329, x2330, x2331, x2332, x2333, x2334, and x2335 if the following criteria are met:

The ANSI-41 Billing Module feature is active. The ANSI-41 Billing Module feature is activated via ecp RC/V entry. The ANSI-41 Billing Module with Service Type feature is activated via ecp RC/V entry. (The actual entry for this feature on the ecp RC/V form reads Service ID.) A Service ID parameter is received in the ANSI-41 message.

For an explanation of the Digit Information Module, read Module 621 - Digit Information Module on page 5-46.
38-8
Issue 27
May 2004
Feature Dependencies
This feature has only one feature dependency. The ANSI-41 Billing Module feature must be turned on for this feature to work correctly.
Issue 27
May 2004
38-9
401-610-133A
None.
38-10
Issue 27
May 2004
39
39-1 39-1 39-2 39-2 39-2 39-2 39-2 39-2 39-3 39-4 39-4 39-5 39-5 39-5 39-5 39-5 39-6 39-6

Introduction What is IMSI? Need for the IMSI Benefit of IMSI MIN-Based IMSI What is the CDMA Full IMSI Feature? Introduction Introduction Generic Context Identifier for This Feature Module Generation Criteria for This Feature AMA Records for Different Types of IMSI Two Modules May Be Attached to One Call Record For Further Information
AMA Impact
About the Digit Information Module

Issue 27
May 2004
39-i
401-610-133A
39-ii
Issue 27
May 2004
39
Introduction
This chapter introduces the CDMA Full International Mobile Station Identity (IMSI) feature (feature ID 2034). This chapter also describes how AMA functionality is affected by this feature and summarizes feature interactions of the CDMA Full IMSI feature with other features.

For further information about the CDMA Full IMSI feature, read the CDMA Full International Mobile Station Identity (IMSI) optional feature document, 401-612297. (For information on the TDMA implementation for IMSI, read Chapter 43, TDMA IMSI Feature.)
Issue 27
May 2004
39-1
401-610-133A
Feature Description
Introduction
This section describes the CDMA Full IMSI feature.
What is IMSI?
IMSI stands for International Mobile Station Identity (IMSI). CDMA mobiles are identified by the IMSI, which is a number that is at most 15 digits in length, with the first three digits being the Mobile Country Code (MCC) followed by the National Mobile Station Identify (NMSI). Included in the National Mobile Station Identity is the Mobile Network Code (MNC) and the Mobile Station Identification Number (MSIN).
Need for the IMSI

IMSI was introduced in standards to resolve problems with the existing Mobile Identification Number (MIN), which was usually set equal to the Wireless Directory Number based on the North American Numbering Plan (NANP). Countries outside World Zone 1 not using the NANP did not have a standard way of defining unique MINs.
Benefit of IMSI
Use of IMSI has several benefits:
It gives countries throughout the world a standard way of defining unique mobile station identifiers. It supports IMSI as a national identifier. It provides functionality that is necessary in order to provide International Roaming (at a future date). It increases the security on the air interface since the IMSI does not have to be as widely known as the DN.
MIN-Based IMSI
All of the mobiles currently deployed in CDMA and PCS systems already support IMSI. However, because all networks did not fully support IMSI when these mobiles were deployed, each of these mobiles was programmed with a MIN in the least significant IMSI digits. This approach is called MIN-based IMSI.
39-2
Issue 27
May 2004
What is the CDMA Full IMSI Feature?

CDMA Full IMSI is an optional feature available with ECP 15.0 that allows CDMA mobiles to access the system and be identified by their full IMSI. When CDMA Full IMSI is not active, only the 10 least significant IMSI digits (IMSI_S) are used for system access and mobile identification.
Issue 27
May 2004
39-3
401-610-133A
AMA Impact
Introduction
The CDMA Full IMSI feature changes AMA in the following ways:

Adding a Generic Context Identifier Expanded use of the existing Digit Information Module.
Both are described in the next section.
39-4
Issue 27
May 2004

Introduction
This section describes the Digit Information Module as used by the CDMA Full IMSI feature.

The value of the Generic Context Identifier field for this feature is 10832 - E.212 International Mobile System Identity.

The Digit Information Module will be appended to AMA records with the x2118, x2119, x2329 - x2338, x2351, x2411, x2415, and 2421 structure codes if the following generation criteria are met:

The CDMA Full IMSI feature is active. Digit Information Module for IMSI is turned on the RC/V ecp form. The mobile associated with the call record has a true IMSI.
NOTE: If the true IMSI is not available, the Digit Information Module with the IMSI will not be appended.
AMA Records for Different Types of IMSI

The type of IMSI(s) programmed in the mobile will have an effect on what AMA records are generated for the call. Table 39-1. AMA Records for Different Types of IMSI Then the following AMA record will be produced... A Digit Information Module containing the MIN A Digit Information Module containing the IMSI Two Digit Information Modules, one containing the MIN and one containing the IMSI
If the mobile has... MIN-based IMSI only True IMSI only Both MIN-based IMSI and true IMSI
Issue 27
May 2004
39-5
401-610-133A
The actual criteria for what DIMs are produced comes from the database. The mobile only sends one ID. The number of IDs for the mobile in the database determines how many modules will be produced.
Two Modules May Be Attached to One Call Record

Note that in cases where a mobile has both a MIN-based IMSI and a true IMSI programmed into it, (assuming that the DIM module is turned on) two modules will be appended to the record for the mobile: one containing the MIN and one containing the IMSI.

39-6
Issue 27
May 2004
40
40-1 40-1 40-2 40-2 40-2 40-2 40-3 40-3 40-3 40-3 40-3 40-4 40-4 40-5 40-5 40-5 40-5 40-6 40-7 40-7 40-7

Introduction What is the TDMA Circuit-Mode Data Services Feature? Scope Introduction Components Reason for the Inter-Working Function (IWF) Definition of the IWF Two Data Paths How the Legs Are Set Up During Call Origination PDP Leg Can Also Activate/Deactivate Features Special Case in Which There is No PDP Leg Setup Scenario for the MDP and the PDP During an Incoming Call Tracking AMA Activity
How It Works

AMA Impact Call Types

New Call Types Records For Which These Call Types Do Not Apply
Issue 27
May 2004
40-i
401-610-133A
Records for Which These Call Types Sometimes Apply Introduction Purpose Definition Applicable Structure Codes Structure Codes for the MDP Leg Structure Codes for the PDP Leg Introduction Purpose Definition Applicable Structure Codes Intra-Switch Terminated Data Call: Only One Record Intra-Switch Terminated Data Call: Structure Codes For Inter-Switch Terminated Data Call: Two or More Records Inter-Switch Terminated Data Call: Structure Codes For Re-routing of Incoming TDMA Circuit-Mode Data Services Calls Purpose of the Data Module Data Module Definition Module Code Field Event Type Field Event Description Field AMASE Table Linking Code Defined Linking Code for Mobile-Originating Calls Linking Code for Mobile-Terminating Calls Data Module Generation Criteria For Further Information Introduction Introduction AMA Record for MDP Leg Exceptions: Rationale for Exceptions for a Standard MDP Leg Call AMA Record for PDP Leg Exceptions for a Standard PDP Leg Call
40-7 40-8 40-8 40-8 40-8 40-8 40-8 40-8 40-9 40-9 40-9 40-9 40-9 40-9 40-9 40-10 40-10 40-10 40-11 40-11 40-11 40-11 40-11 40-11 40-12 40-12 40-12 40-12 40-12 40-13 40-14 40-14 40-15 40-15 40-15 40-15 40-15 40-17 40-17


Data Module

AMA Records for TDMA Circuit-Mode Data Services Calls
Mobile Origination

40-ii
Issue 27
May 2004
Record for PDP Leg with Feature Activation/Deactivation Exceptions Introduction AMA Record for Mobile-Terminated Call Exceptions Hardware Requirements Feature Interactions
40-18 40-18 40-20 40-20 40-20 40-20 40-21 40-21 40-21
Mobile Termination


Issue 27
May 2004
40-iii
401-610-133A
40-iv
Issue 27
May 2004
40
Introduction
This chapter introduces the TDMA Circuit-Mode Data Services feature and describes the two call types and one module used for this feature. The chapter also explains how the TDMA Circuit-Mode Data Services feature affects AMA records. Finally, the chapter describes interactions of the TDMA Circuit-Mode Data Services feature with other features. This chapter covers the TDMA implementation of the Circuit-Mode Data Services feature. For information about the CDMA implementation of the Circuit-Mode Data Services feature, read Chapter 25, CDMA Circuit-Mode Data Services Feature.

For more information about this feature, read the TDMA Circuit-Mode Data Services Optional Feature document, 401-612-211.
Issue 27
May 2004
40-1
401-610-133A
Feature Description
Introduction
This section describes the TDMA Circuit-Mode Data Services feature.
What is the TDMA Circuit-Mode Data Services Feature?

The TDMA Circuit-Mode Data Services feature provides a subscriber having the appropriate mobile station configuration the ability to communicate with existing asynchronous modems and group-3 facsimile machines using the TDMA air interface.
Scope
Mobile-originated, mobile-terminated, and mobile-to-mobile circuit-mode data calls are supported.1
A mobile-to-mobile data call is treated as a combination of a mobile-originated data call and a mobile-terminated data call.
40-2
Issue 27
May 2004
How It Works
Introduction
This section gives an overview of how the TDMA Circuit-Mode Data Services feature works.
Components
A typical mobile station configuration consists of a data terminal, such as a laptop computer, connected via an RS-232 cable to a TDMA mobile device conforming to TIA/EIA/IS-99, the circuit-mode data service standard. This mobile device presents an interface to the data terminal that allows the data terminal application to treat the mobile device as if it were an asynchronous data or facsimile modem. The mobile device uses the TDMA air interface to access an Inter-Working Function (IWF) connected to the Digital Cellular Switch (DCS) of a Mobile Switching Center (MSC). The IWF delivers the actual modem functions being controlled by the data terminal.
Reason for the Inter-Working Function (IWF)

The TDMA vocoder cannot carry voice-band modem tones at the higher modulation rates popular today. These modem tones carry a rich set of frequency, phase, and amplitude relationships that low-bit-rate vocoders cannot reproduce. Therefore, the TDMA air interface must carry the data in digital form to an interworking function (IWF) that generates the modem tones for communication through the PSTN.
Definition of the IWF

The IWF is a separate piece of hardware that is connected to the Digital Cellular Switch (DCS) of a Mobile Switching Center (MSC). The IWF delivers the actual modem functions being controlled by the data terminal, as shown in Figure 40-1 on page 40-4.
Issue 27
May 2004
40-3
401-610-133A
ECPC
ECP-cell link ECP-DCS link
cell
packet pipe
DCS
PSTN trunk
PSTN
signaling links
mobile data path leg
IWF
PSTN data path leg
Figure 40-1.
The Inter-Working Function--How It Works
Two Data Paths

A circuit-mode data call is treated as two independent calls at the DCS. These are the mobile data path (MDP) leg and the PSTN data path (PDP) leg. The mobile data path leg refers to the connection between the subscriber and the IWF. The mobile data path leg carries digital data between the mobile device and the IWF. The PSTN data path leg refers to the connection between the IWF and the PSTN. The PSTN data path leg carries modem tones between the IWF and the PSTN. The IWF connects to the PSTN through the DCS; it has no direct PSTN connections.
How the Legs Are Set Up During Call Origination

When a subscriber originates a TDMA Circuit-Mode Data Services call (via an ATD command), the MDP leg is established first. Once the MDP leg is established, a stable connection exists between the data terminal and the IWF. Based on instructions downloaded from the data terminal, the IWF can now initiate a call to the PSTN on behalf of the subscriber. This call from the IWF to the PSTN is the PDP leg. Once the setup of the PDP leg is finished, a complete communication link from the subscribers terminal equipment to the PSTNconnected modem is established. One AMA record is generated for the MDP leg with a structure code number of x2329 or x2333. One AMA record is generated for the PDP leg with a structure code number of x2118 or x2119.
40-4
Issue 27
May 2004
PDP Leg Can Also Activate/Deactivate Features

Instead of a call that is routed to the PSTN, the call made from the IWF can also be used to activate and/or deactivate features for the mobile. If the mobile causes the IWF to dial the appropriate feature codes (for example, *72 to activate call forwarding), the PDP leg will cause the appropriate feature to be activated or deactivated. One AMA record is generated with a structure code number of x2411 for the feature activation/deactivation.
Special Case in Which There is No PDP Leg

It is also possible for no subsequent PSTN call to be generated by the IWF. The mobile may simply download various parameters from the IWF and then end the call. In this case, there is no PDP leg to a Circuit-Mode Data Services call.
Setup Scenario for the MDP and the PDP During an Incoming Call
When a subscriber receives an incoming TDMA Circuit-Mode Data Services call (that is, mobile termination), the setup of the MDP and the PDP legs is done in parallel. The incoming call from the PSTN is associated with the PDP leg. Upon receipt of this incoming call, the mobile will be paged. If the call is a TDMA CircuitMode Data Services call, the setup of the MPD leg begins after the mobile responds to the page. When the subscriber answers the call, the setup of the PDP leg is completed by forwarding the incoming call to a trunk associated with the same IWF used for the MDP leg. Once the forwarding of the incoming call to the IWF is complete, a complete communication link from the subscribers terminal equipment to the PSTN-connected modem is established. One AMA record is generated for the TDMA Circuit-Mode Data Mobile Terminated call with a structure code number of x2331, x2334, or x2335.
Tracking AMA Activity

AMA activity on both these legs is tracked in AMA records. See the section called AMA Records for TDMA Circuit-Mode Data Services Calls on page 40-14 for information on how this is done.
Issue 27
May 2004
40-5
401-610-133A
AMA Impact
The major impacts of TDMA Circuit-Mode Data Services on AMA are:
Two new call types: Mobile-Originated Data Call Mobile-Terminated Data Call Use of the Data Module with a new Event Type - Initial Assigned TDMA Data Service Configuration and its associated event description
These impacts are discussed in the following sections.
40-6
Issue 27
May 2004
Call Types
New Call Types
Two new call types are used in the TDMA Circuit-Mode Data Services feature. They are:

059 - Mobile-Originated Circuit Data Call 053 - Mobile-Terminated Circuit Data Call
These AMA call types are used to identify a call as a circuit-mode data services call. These call types are described in the following sections.
Records For Which These Call Types Do Not Apply

The 059 and 053 call types do not apply to x2337 or x2338 AMA records generated during a data call; for these records, normal call types apply.
Records for Which These Call Types Sometimes Apply

Structure code layout number x2336 can apply to two types of records: hand-off record, and inter-switch termination record. For structure code layout number x2336 records for handoffs, the 059 and 053 call types do not apply. For structure code layout number x2336 records for inter-switch terminations, only the 053 call type applies.
Issue 27
May 2004
40-7
401-610-133A

Introduction
This section describes the Mobile-Originated Circuit Data Call Call Type.
Purpose
The Mobile-Originated Circuit Data Call Call Type is used for mobile-originated data calls.
Definition
The Call Type number for the Mobile-Originated Circuit Data Call is 059.

This Call Type applies to AMA records generated for both the mobile data path (MDP) and the PSTN data path (PDP) legs of a mobile origination and applies to structure codes x2118, x2119, x2329, x2333, and x2411.
Structure Codes for the MDP Leg

The AMA record on the mobile data path leg of a mobile-originated TDMA CircuitMode Data Services call will use structure codes x2329 and x2333.
Structure Codes for the PDP Leg

The AMA record on the PSTN path leg that is routed to an outgoing trunk of a mobile-originated TDMA Circuit-Mode Data Services call will use a x2118 or x2119 structure code. The AMA record on the PSTN path leg that is used for feature activation/ deactivation of a mobile-originated TDMA Circuit-Mode Data Services call will use a x2411 structure code. NOTE: For a mobile-originated Circuit-Mode Data Services call that does not cause the IWF to generate a PDP leg, only one AMA record will be generated by the call for the MDP leg.
40-8
Issue 27
May 2004

Introduction
This section describes the Mobile-Terminated Circuit Data Call Call Type.
Purpose
The Mobile-Terminated Circuit Data Call Call Type is used for mobile-terminated data calls.
Definition
The Call Type number for this Call Type is 053. Like the Mobile-Originated Circuit Data Call Call Type, the Mobile-Terminated Circuit Data Call Call Type applies to AMA records generated for both the mobile data path (MDP) and the PSTN data path (PDP) legs of a call.

The Mobile-Terminated Circuit Data Call Call Type applies to structure codes x2331, x2334, x2335, and x23362.
Intra-Switch Terminated Data Call: Only One Record

For a mobile-terminated data call that goes through only one DCS at call setup time, the MDP and PDP legs of the call will generate AMA information equivalent to a similar type of call termination for a non-data call. For these non-interswitch terminating calls (the usual case) this will generate a single AMA record.
Intra-Switch Terminated Data Call: Structure Codes For

The AMA record for a non-interswitch mobile-terminated TDMA Circuit-Mode Data Services call will use structure codes x2331 or x2334.
The AMA record for an inter-switch termination only.
Issue 27
May 2004
40-9
401-610-133A
Inter-Switch Terminated Data Call: Two or More Records

For a mobile-terminated TDMA Circuit-Mode Data Services call that goes through more than one DCS at call setup time, call processing will generate two or more AMA records3. The control point switch AMA record for these inter-switch mobileterminated data calls will use structure codes x2335.
Inter-Switch Terminated Data Call: Structure Codes For

For interswitch mobile-terminated TDMA Circuit-Mode Data Services calls, the slave (or serving) switch AMA record will use a x2336 structure code.
Re-routing of Incoming TDMA Circuit-Mode Data Services Calls

Incoming TDMA Circuit-Mode Data Services calls can be re-routed via either the call forwarding or message recording service (voice mail) features. Normal AMA records for those features will apply.
This second case has nothing to do with the IWF; a separate AMA record is always generated for each DCS involved in an inter-switch call.
40-10
Issue 27
May 2004
Data Module
Purpose of the Data Module
The Data Module is used to store the Initial Assigned TDMA Data Service Configuration. It also provides a link between the two separate AMA records that are created for a TDMA Circuit-Mode Data Services mobile-originating call.
Data Module Definition

The Data Module contains the following fields:

Module Code Event Type Event Description Linking Code
Module Code Field

The Module Code field identifies the type of module that is appended to the existing AMA record. The value of the module code for the Data Module is 344.
Event Type Field

For a TDMA Circuit-Mode Data Services call, the event type will be set to 012 to indicate that the Event Description contains the Initial Assigned TDMA Data Service Configuration.

For a TDMA Circuit-Mode Data Services call, the Event Description field holds the following information:

TDMA Service Code (Async data or G3 fax) TDMA Data Mode Data Privacy Flag TDMA Data Mode Cyclic Redundancy Check Value
Issue 27
May 2004
40-11
401-610-133A
AMASE Table
The new TDMA Event Type caused a redefinition of the fields in AMASE Table 497, Event Description. Table 4-48 on page 4-77 shows the special layout created in the Event Description field for Event Type 012 (Initial Assigned TDMA Data Service Configuration).
Linking Code Defined

The Linking Code field is used to provide a link between the two separate AMA records that are created for a TDMA Circuit-Mode Data Services mobileoriginating call. The linking code consists of a sign digit plus a seven-digit nonzero number. The Linking Code is unique across the CDNs and is created and assigned when the MCR for the PSTN path leg is created.
Linking Code for Mobile-Originating Calls

For TDMA Circuit-Mode Data Services mobile-originating calls, the linking code will be used to associate the separate AMA records that describe the MDP and the PSTN path legs of the call.
Linking Code for Mobile-Terminating Calls

No Linking Code is needed for mobile-terminating calls, because for a mobileterminating call only one AMA record is generated.
Data Module Generation Criteria

A Data Module will be generated for a TDMA AMA record that has one of the following structure codes: x2118, x2119, x2329, x2331, x2333-x2335, and x2411 if the following generation criteria are met:
The TDMA Circuit-Mode Data Services Feature Activation File (FAF) entry is active. The Data Module is turned on via ecp RC/V. A TDMA mobile has originated or received a TDMA Circuit-Mode Data Services call.
40-12
Issue 27
May 2004

For more about the Data Module, read Module 344Data Module on page 5-38.
Issue 27
May 2004
40-13
401-610-133A
AMA Records for TDMA Circuit-Mode Data Services Calls

Introduction
The type and quantity of AMA records generated for a TDMA Circuit-Mode Data Services call are dependent on the type of call (origination vs. termination). Each call type and its associated AMA records is discussed in the following sections.
40-14
Issue 27
May 2004
Mobile Origination
Introduction
A mobile-originated TDMA Circuit-Mode Data Services call consists of two parts:

A call from the mobile to the IWF, known as the mobile data path (MDP) A call from the IWF to the PSTN (or another mobile), known as the PSTN data path (PDP).
Separate AMA records are generated for each of these two parts of the call. These AMA records are linked with a linking code to allow the records to be associated with each other by the downstream billing process.
AMA Record for MDP Leg

The AMA record created by the MDP part of the call will be typically a standard mobile origination record using structure code x2329 (or structure code x2333 if an Inter-DCS or Inter-MSC Soft Handoff occurs during the call).
Exceptions: Rationale for

Some exceptions must occur because many of the fields in a typical x2329 AMA record are generated and derived during digit analysis done on the dialed digits on a mobile originating call. For the TDMA Circuit-Mode Data Services feature, digit analysis is not performed on the mobile data path leg of the call; rather, digit analysis is done on the digits received in the incoming call for the PSTN data path leg of the call. Thus, many AMA Data fields related to routing for an x2329 AMA record must be defaulted to generate a meaningful AMA record.

The following exceptions to the standard mobile origination record occur for a Mobile Origination TDMA Circuit-Mode Data Services call:
The Call Type field will be set to Mobile Originated Circuit Data Call. The Call Type value used to indicate Mobile Originated Circuit Data Call is 059. The call from the mobile to the IWF does not contain any destination digits. (As already explained, the called number is not known until after the mobile is connected to the IWF.) Thus, the following Digit-Related fields in the record are set by default:
Issue 27
May 2004
40-15
401-610-133A
BCD Character 5 of the Origination Indicator will be set to 5 (Basic Routing). BCD Character 6 of the Origination Indicator will be set to 0 (No Operator Involved). The Terminating Number field can have different information stored in the field, depending on which features are active. See Table 40-1 on page 40-16 for a graphical depiction of the following information:4
If the Dialed Digits in AMA (DDAMA)5 feature is on, and the ECP RC/V Entry for Digit Information Module for DDAMA is on, these fields contain the digit analysis results. However, no digit analysis is performed for TDMA Circuit-Mode Data mobile-originating calls, so this field is filled with zeroes. If the Dialed Digits in AMA (DDAMA) feature is on, and the ECP RC/V Entry for Digit Information Module for DDAMA is off, these fields contain the dialed digits. For a TDMA CircuitMode Data mobile-originating call, these fields are filled with meaningless data and should be ignored. If the Dialed Digits in AMA (DDAMA) feature is off in the FAF, zeroes (the digit analysis results) will be stored.
Table 40-1 on page 40-16 summarizes this logic. Table 40-1. Storage of a Dialed Digit String by the DDAMA Feature (Page 1 of 2) and the ECP RC/V Entry for Digit Information Module for DDAMA is... ON then the Terminating Number and NPA Fields contain... the digit analysis results the dialed digits string and the Digit Information Module is... Created and contains the dialed digits string not created
If the DDAMA FAF is...
ON
ON
OFF
The contents of the Terminating NPA and Terminating Number fields can also vary depending upon whether the TDMA IP Billing feature is turned on. For more information on these fields and how they are impacted by the presence of a TDMA Direct Internet Access number, see the section AMA Impact on page 44-4 in Chapter 44, IP Billing Feature on page 44-1. For more about the DDAMA feature, see the DIaled Digits in AMA optional feature document (401-612-097).
40-16
Issue 27
May 2004
Table 40-1.
Storage of a Dialed Digit String by the DDAMA Feature (Page 2 of 2) and the ECP RC/V Entry for Digit Information Module for DDAMA is... OFF then the Terminating Number and NPA Fields contain... the digit analysis results and the Digit Information Module is... not created
OFF
The Call Answer Status will be set to Answered if the IWF answered the MDP portion of the call. Note that this field does NOT indicate whether the call was answered at the far end. The Call Answer Status in the PDP leg of the call must be examined to determine the answer status of the outgoing call. The Called Party Answer Date and Time fields will indicate the time that the IWF answered the MDP portion of the call. Note that this is NOT the time/date that the far end answered the call. The Called Party Answer Time and Date fields in the PDP leg of the call must be examined to determine the answer time of the outgoing call. The Called Party Elapsed Time field will indicate the time from when the IWF answered the MDP portion of the call to when the call was disconnected. Note that this is NOT the elapsed time that the mobile was talking to the far end. The Called Party Elapsed Time field in the PDP leg of the call must be examined to determine the elapsed time of the outgoing call. The Trunk Network Number field will contain information on the Switched Virtual Circuit (SVC) trunk used to connect the mobile to the IWF. If the appropriate flag in the ecp database is set to y, the Data Module will be appended to the AMA record. (See Data Module on page 40-11 for more details on the Data Module.)
AMA Record for PDP Leg

The AMA record for the PDP portion of a TDMA Circuit-Mode Data Services call will use a Tandem Trunk Switching structure code if the call is routed to an outgoing trunk. If an interexchange carrier is used for the call, structure code x2118 will be used. Otherwise, structure code x2119 will be used.
Exceptions for a Standard PDP Leg Call

The values in the fields of the Tandem Trunk Switching record will be similar to a standard Tandem Trunk Switching call with the following exceptions:
Issue 27
May 2004
40-17
401-610-133A
The Call Type field will be set to Mobile Originated Circuit Data Call. The Call Type value used to indicate Mobile Originated Circuit Data Call is 059. The Subscriber Number field will be set to the originating mobiles directory number. All of the destination digit related fields will be filled in normally based on the destination of the outgoing call. The Call Answer Status field will be set to Answered if the far end answers the outgoing call. The Called Party Answer Date and Time fields will be filled in with the date and time that the far end answered the call. The Called Party Answer Elapsed Time field will be filled in with the elapsed time from when the far end answered the call until the call was disconnected. The Outgoing Tandem TNN field will contain the outgoing trunk for the call. The Incoming Tandem TNN field will contain the ISDN B Channel (IBC) trunk used to connect the IWF to the outgoing trunk for routing out to the PSTN. If the Data Module is turned on via ecp RC/V, the Data Module will be appended to the AMA record. (See Data Module on page 40-11 for more details on the Data Module.)
Record for PDP Leg with Feature Activation/ Deactivation

It is possible for the PDP portion of a TDMA Circuit-Mode Data Services feature call to involve a feature activation/deactivation rather than a call to be routed to the PSTN. In this case, feature activation/deactivation AMA structure codes will be used in the same way as they are for a feature activation/deactivation call made by a normal voice mobile. Structure code x2411 will be used. If the appropriate flag in the ecp database is set to y, the values in the fields of the x2411 records will be similar to standard values used in a feature activation/ deactivation call made by a voice mobile with certain exceptions.
Exceptions
The following exceptions apply in this case:
The Call Type field will be set to Mobile-Originated Data Call. The Call Type value used to indicate Mobile-Originated Data Call is 059.
40-18
Issue 27
May 2004
If the appropriate flag in the ecp database is set to y, the Data Module will be appended to the AMA record. (See Data Module on page 40-11 for more details on the Data Module.)
Issue 27
May 2004
40-19
401-610-133A
Mobile Termination
Introduction
A mobile-terminated TDMA Circuit-Mode Data Services call also consists of the MDP and PDP portions of the call as described for a mobile-originated TDMA Circuit-Mode Data Services call. The major difference is that usually only one AMA record will be generated for a mobile-terminated TDMA Circuit-Mode Data Services call. (See Inter-Switch Terminated Data Call: Two or More Records on page 40-10 for an exception to this rule.)
AMA Record for Mobile-Terminated Call

The AMA record created by a mobile-terminated TDMA Circuit-Mode Data Services call will be typically a standard mobile-terminated record, using structure code x2331 for intra-DCS terminations or x2334 or x2335 for terminations involving more than one DCS.
Exceptions
The following exceptions to the standard mobile-terminated record apply:
The Call Type field will be set to Mobile Terminated Circuit Data Call. The Call Type value used to indicate Mobile Terminated Circuit Data Call is 053. The Voice Channel Answer Time and Date fields will be set to the time that the answer is received from the IWF over the IBC trunk. Note that this time and date will be a few seconds later than the time that the mobile answered the call on the traffic channel. The answer from the IWF represents the time that a full voice path (here, a data path) is available for the call. If the Data Module is turned on via ecp RC/V, the Data Module will be appended to the AMA record. (See Data Module on page 40-11 for more details on the Data Module.)
40-20
Issue 27
May 2004
The TDMA Circuit-Mode Data Services feature requires the TDMA Vocoder Relocation feature to be in place.
Hardware Requirements
TDMA cell sites must display the DCCH via Enhanced Digital Radio Unit (EDRU) to perform call setup. The TDMA Circuit-Module Data Services feature will only be available at cell sites that deploy EDRUs with DCS-based vocoder (using the TDMA Vocoder Relocation feature). A data call forced to hand off to a cell without the Vocoder Relocation feature will be dropped.
Refer to the TDMA Circuit-Mode Data Services Optional Feature document, 401612-211, for a list of feature interactions for this feature.
Issue 27
May 2004
40-21
401-610-133A
40-22
Issue 27
May 2004
41
41-1 41-1 41-2 41-2 41-2 41-2 41-2 41-2 41-3 41-4 41-4 41-4 41-4 41-4 41-5 41-6 41-6 41-6

Introduction What is the TSI Bridging Feature? Previous Method of Court-Ordered Surveillance Mandate for a New Way of Monitoring Additional Benefits About the LAES Feature Introduction What is the Time Slot Bridge? TSI Bridging Creates a Copy of the Call LAES Feature Implementation Figure Introduction Use of Existing Trunk Information Module New Value for Trunk Direction, Trunk Type, and Release Cause Field41-6 Module Generation Criteria for TSI Bridging Feature Table
How It Works

AMA Impact

41-6 41-6
Issue 27
May 2004
41-i
401-610-133A
For More About the Trunk Information Module
41-7 41-8
41-ii
Issue 27
May 2004
41
Introduction
This chapter provides information on the TSI Bridging feature and describes how AMA functionality is affected by this feature.

More detailed information about this feature can be found in 401-601-209, Lawfully Authorized Electronic Surveillance (LAES) for CALEA Optional Feature document.
Issue 27
May 2004
41-1
401-610-133A
Feature Description
Introduction
This section describes the TSI Bridging feature.
What is the TSI Bridging Feature?

The TSI Bridging feature provides a new method of tapping a cellular call. This method uses the Time Slot Interchange (TSI) hardware in the 5ESS Switch and depends upon the availability of the Time Slot Bridging for Wireless - CALEA feature in the 5ESS Switch. The TSI Bridging feature is designed to be used in conjunction with applications such as the LAES feature.
Previous Method of Court-Ordered Surveillance

Traditionally, in the Flexent/AUTOPLEX wireless network, monitoring was provided using the Increased Court Order Surveillance (ICOS) feature. However, because of the increasing sophistication of wireless networks, it was becoming increasingly difficult for ICOS to provide complete voice and conversation monitoring for all call types and features.
Mandate for a New Way of Monitoring

In 1994, the United States government passed a law mandating more sophisticated surveillance techniques. The TSI Bridging feature, when used in conjunction with the LAES feature, ensures 100 percent compliance with the requirements of the Federal law.
Additional Benefits
Additional benefits exist with the TSI Bridging method of call surveillance:
The ICOS feature caused a three- to four-second delay in call setup for calls that were under surveillance. TSI Bridging does not have this delay. A TSI bridge can be easily installed or torn down at different stages of a call.
41-2
Issue 27
May 2004
The bridge trunks provided by the TSI Bridging are separate from the voice trunks used for the call. If for some reason one of the TSI Bridging trunks should fail, the voice call will continue undisturbed. This was not the case with the ICOS feature.
About the LAES Feature

Because the TSI Bridging capability may be used in the future to support other features, the LAES feature is described in a separate chapter in this document. For information about the AMA impact of the LAES feature, read Chapter 42, LAES Feature. For more information about the LAES feature in general, read the Lawfully Authorized Electronic Surveillance (LAES) for CALEA Optional Feature document, 401-601-209.
Issue 27
May 2004
41-3
401-610-133A
How It Works
Introduction
The TSI Bridging feature uses a Time Slot Bridge in the 5ESS Switch to set up a TSI bridge for a selected call.
What is the Time Slot Bridge?

The Time Slot Bridge is a unit made up of two additional TSIs and two channels in the Time Multiplexed Switch (TMS). One TSI with a TMS channel is used to bridge the originating TSI of the call and the other TSI with a TMS channel is used to bridge the terminating TSI of the call.
TSI Bridging Creates a Copy of the Call

The TSI Bridging feature causes two additional time slots in the TSI to be assigned to a copy of the call (in real time). Two additional trunk members are also assigned to the copy of the call. Information received from the copy of the call can go to another application or to a piece of hardware designed to monitor and track call surveillance, such as the Delivery box (as shown in Figure 41-1 on page 41-5).
LAES Feature Implementation

In the LAES feature implementation, the information collected from the TSI bridge is sent over the transmitting trunk to a separate piece of hardware called the Delivery box. The Delivery box filters call event and call content information and sends it to the Law Enforcement Agency. For information about the AMA impact of LAES, read Chapter 42, LAES Feature, in this document. For more information about LAES in general, read the Lawfully Authorized Electronic Surveillance (LAES) for CALEA Optional Feature document, 401-612-209.
41-4
Issue 27
May 2004
Figure
Delivery box or other application Connections to Other Party Transmit Trunk Receive Trunk
DCS
TSI
Loop Channel Cell Site Trunk
Mobile
Figure 41-1.
TSI Bridging
Issue 27
May 2004
41-5
401-610-133A
AMA Impact
Introduction
For the TSI Bridging feature, information on each trunk group member assigned to the TSI Bridge will be appended to the AMA record for the call.
Use of Existing Trunk Information Module

AMA uses the existing Trunk Information Module to record information on each trunk group member assigned to the TSI Bridge. Up to two Trunk Information Modules will be generated for a TSI Bridge.
New Value for Trunk Direction, Trunk Type, and Release Cause Field
For the TSI Bridging feature, a new value (3 in BCD Character 1 for TSI Bridging) is defined in the Trunk Direction field. This value is shown in Table 4-62 "AMASE Table 954" on page 4-103. The TSI Bridging value identifies the use of bridge trunks to connect to the direction of the third party. The third party is defined to differentiate from the calling and called parties.
Module Generation Criteria for TSI Bridging Feature

AMA will append the Trunk Information Module for the TSI Bridging feature to AMA records with structure codes x2118, x2119, x2329-x2338, x2411, and x2415 if the following conditions are true:

The TSI Bridging FAF entry is active. The ecp form field Trunk Information Module for TSI Bridging is set to y via RC/V.
Table
Table 5-17 "Trunk Information Module Layout" on page 5-70 defines the Trunk Direction field and all other fields in the Trunk Information Module.
41-6
Issue 27
May 2004
For More About the Trunk Information Module

For a description of the Trunk Information Module, read Module 623Trunk Information Module on page 5-70.
Issue 27
May 2004
41-7
401-610-133A
This feature depends upon the 5ESS Switch feature Time Slot Bridging for Wireless - CALEA.
41-8
Issue 27
May 2004
LAES Feature
42
42-1 42-1 42-2 42-2 42-2 42-2 42-2 42-3 42-3 42-4 42-4 42-4 42-4 42-4 42-4 42-4 42-5 42-5 42-5 42-5 42-5 42-5

What is the LAES Feature? Previous Method of Court-Ordered Surveillance Mandate for a New Way of Monitoring Additional Benefits For More Information About the TSI Bridging Feature For More Information About the LAES Project Introduction Use of Existing Trunk Information Module Table Module Code Field Trunk Identification Field Trunk/Facilities Seizure Date Field Trunk/Facilities Seizure Time Field Trunk Elapsed Time Field Trunk Direction Field Trunk Type Field Release Cause Field Module Generation Criteria for LAES Feature
AMA Impact

Issue 27
May 2004
42-i
401-610-133A
42-6
42-ii
Issue 27
May 2004
LAES Feature
42
Introduction
This chapter provides information on Phase 3 of the Lawfully Authorized Electronic Surveillance (LAES) feature. Phase 3 of this feature is also called the LAES feature.

More detailed information about this feature can be found in 401-601-209, Lawfully Authorized Electronic Surveillance for CALEA Optional Feature document.
Issue 27
May 2004
42-1
401-610-133A
Feature Description
What is the LAES Feature?
The LAES feature provides a means for legally authorized Law Enforcement Agencies (LEAs) to obtain access to the content of the intercept targets (also called subject) communications. It also provides call identifying information about those communications. The LAES feature is totally transparent and completely undetectable to the target.
Previous Method of Court-Ordered Surveillance

Traditionally, in the Flexent/AUTOPLEX wireless network, monitoring was provided using the Increased Court Order Surveillance (ICOS) feature. However, because of the increasing sophistication of wireless networks, it was becoming increasingly difficult for ICOS to provide complete voice and conversation monitoring for all call types and features. The traditional LAES system using ICOS monitoring is still available in ECP 15.0. However, the traditional LAES system using loop-around trunk-based monitoring does not ensure 100 percent compliance with the Federal law passed in 1994.
Mandate for a New Way of Monitoring

In 1994, the United States government passed a law mandating more sophisticated surveillance techniques. The LAES feature ensures 100 percent compliance with the requirements of the Federal law.
Additional Benefits
Two additional benefits exist with the TSI Bridging method of call surveillance:
The ICOS feature caused a three- to four-second delay in call setup for calls that were under surveillance. TSI Bridging does not have this delay. A TSI bridge can be easily torn down at different stages of a call. The bridge trunks used by the TSI Bridging feature are separate from the voice trunks used for the call. If for some reason one of the TSI Bridging trunks should fail, the voice call will continue undisturbed. This was not the case with the ICOS feature.
42-2
Issue 27
May 2004
LAES Feature
For More Information About the TSI Bridging Feature

More information about the TSI Bridging feature is given in the Lawfully Authorized Electronic Surveillance for CALEA Optional Feature document, 401612-209. AMA impacts of the TSI Bridging feature are discussed in this document in Chapter 41, TSI Bridging Feature.
For More Information About the LAES Project

For more information about all three phases of LAES, read the Lawfully Authorized Electronic Surveillance for CALEA Optional Feature document, 401612-209.
Issue 27
May 2004
42-3
401-610-133A
AMA Impact
Introduction
For the LAES feature, information on each trunk group member assigned to the TSI Bridge will be appended to the AMA record for the call.
Use of Existing Trunk Information Module

AMA uses the existing Trunk Information Module to record information on each trunk group member assigned to the TSI Bridge. Up to two Trunk Information Modules will be generated. For a description of the Trunk Information Module, read Module 623Trunk Information Module on page 5-70.
Table
Table 5-17 "Trunk Information Module Layout" on page 5-70 defines all the fields in the Trunk Information Module. The impacts of the LAES feature on each field of the Trunk Information Module are discussed in the following sections.
Module Code Field

The Module Code field will contain the value 623, to indicate Trunk Information Module.
Trunk Identification Field

The Trunk Identification Field contains the Trunk Group Identifier and Trunk Member Number of the associated trunk. This identifies the trunk member used for the LAES call.
Trunk/Facilities Seizure Date Field

This field will be set to 0.
42-4
Issue 27
May 2004
LAES Feature
Trunk/Facilities Seizure Time Field

Trunk Elapsed Time Field

Trunk Direction Field

For the LAES feature, the value of 3 (for TSI Bridging) is used in the Trunk Direction Field. This value was new for the TSI Bridging feature; it is not new for the LAES feature.
Trunk Type Field

For the LAES feature, the value in the Trunk Type field is used to specify whether the record belongs to the Primary or Secondary trunk group member in the pair of trunks used in the TSI Bridge. For the LAES feature, the value specified will be one of the following:

6 - LAES Primary 7 - LAES Secondary
Release Cause Field

For the LAES feature, the value in the Release Cause field will be one of the following (depending on in what fashion the call was released):

0 - Disconnect with Unidentified Reason (for normal releases) 29 - Abnormal Switch Release (for abnormal releases)
Module Generation Criteria for LAES Feature

AMA will append one Trunk Information Module for each trunk used by the LAES feature for AMA call for records with structure codes x2118, x2119, x2329-x2338, x2411, and 2415 if the individual subscriber to be tapped is in the LAES database and set up for an audio tap, and if the following conditions are true:

The TSI Bridging FAF entry is active. The Lawfully Authorized Electronic Surveillance (LAES) FAF entry is active. The ecp form field Trunk Information Module for TSI Bridging is set to y.
Issue 27
May 2004
42-5
401-610-133A
The TSI Bridging feature depends upon the 5ESS Switch feature Time Slot Bridging for Wireless - CALEA.
42-6
Issue 27
May 2004
TDMA IMSI Feature
43
43-1 43-1 43-2 43-2 43-2 43-2 43-2 43-3 43-3 43-4 43-4 43-5 43-5 43-5 43-5 43-5 43-6

What is IMSI? IMSI Compared to the MIN and the DN Need for the IMSI Benefit of IMSI What is the TDMA IMSI Feature? Independence from the CDMA IMSI Feature Introduction Introduction Generic Context Identifier for This Feature Module Generation Criteria for This Feature For Further Information
AMA Impact

Issue 27
May 2004
43-i
401-610-133A
43-ii
Issue 27
May 2004
TDMA IMSI Feature
43
Introduction
This chapter introduces the TDMA International Mobile Station Identity (IMSI) feature (feature ID 3176.0). This chapter also describes how AMA functionality is affected by this feature and summarizes feature interactions of the TDMA IMSI feature with other features.

For further information about the TDMA IMSI feature, read the International Mobile Station Identity Optional Feature document, 401-612-241. (For information on the CDMA implementation for IMSI, read Chapter 39, CDMA Full IMSI Feature.)
Issue 27
May 2004
43-1
401-610-133A
Feature Description
What is IMSI?
IMSI stands for International Mobile Station Identity (IMSI). The IMSI is an international mobile identifier that can be used throughout the world. The IMSI is replacing the Directory Number (DN)-based national identifier Mobile Identification Number (MIN) used by previous TDMA cellular releases. The IMSI is a numeric code that can be up to 15 digits long, with the first three digits being the Mobile Country Code (MCC) followed by the National Mobile Station Identity (NMSI). Included in the National Mobile Station Identity is the Mobile Network Code (MNC) and the Mobile Station Identification Number (MSIN).
IMSI Compared to the MIN and the DN

The Mobile Identification Number (MIN) is DN-based, is 10 digits long, and is not unique internationally. Because of these two limitations of the MIN, the IMSI was created. Both MIN and IMSI are owned by the Service Provider and assigned by the Service Provider. The DN, on the other hand, is owned by the subscriber and is what the subscriber sees as the ID for the phone.
Need for the IMSI

IMSI was introduced in standards to resolve problems with the existing Mobile Identification Number (MIN), which was usually set to equal the Wireless Directory Number based on the North American Numbering Plan (NANP). Countries outside World Zone 1 not using the NANP did not have a standard way of defining unique MINs.
Benefit of IMSI
Use of IMSI has several benefits:
It gives countries throughout the world a standard way of defining unique mobile station identifiers. It supports IMSI as a national identifier. It provides functionality that is necessary in order to provide International Roaming (at a future date).
43-2
Issue 27
May 2004
TDMA IMSI Feature
It increases the security on the air interface since the IMSI does not have to be as widely known as the DN.
What is the TDMA IMSI Feature?

The TDMA IMSI feature makes possible the use of IMSI as a unique mobile identifier for all TDMA operations. The IMSI replaces the DN-based MIN. The mobile uses the IMSI to identify itself to the TDMA network. The TDMA network uses the IMSI to address the mobile, access subscriber information, and perform all call processing for the mobile.
Independence from the CDMA IMSI Feature

The TDMA IMSI feature can be activated independently, without the CDMA Full IMSI feature.
Issue 27
May 2004
43-3
401-610-133A
AMA Impact
Introduction
No new AMA software was added to support the TDMA IMSI feature. Instead, the TDMA IMSI feature uses the following previously-existing items in AMA:
The Generic Context Identifier that was added for the CDMA Full IMSI feature The Digit Information Module
Both are described in the next section.
43-4
Issue 27
May 2004
TDMA IMSI Feature

Introduction
This section describes the Digit Information Module as used by the CDMA Full IMSI feature.

The value of the Generic Context Identifier field for this feature is 10832 - E.212 International Mobile System Identity.

The Digit Information Module will be appended to AMA records with the x2118, x2119, x2329 - x2338, x2411, x2415, and x2421 structure codes if the following generation criteria are met:

The CDMA Full IMSI feature is active. Digit Information Module for IMSI is turned on the RC/V ecp form. The mobile associated with the call record has a true IMSI.
NOTE: If the true IMSI is not available, the Digit Information Module with the IMSI will not be appended.

Issue 27
May 2004
43-5
401-610-133A
The following features are affected by IMSI:

Roaming Authentication Short Message Service Over The Air Activation Message Waiting Indicator Call Forwarding MU SDN Flexible Alerting Special Routing TDMA Circuit Mode Data CNIP.
For a description of these feature dependencies, read the International Mobile Station Identity Optional Feature document, 401-612-241.
43-6
Issue 27
May 2004
IP Billing Feature
44
44-1 44-1 44-2 44-3 44-3 44-3 44-3 44-3 44-3 44-4 44-4 44-4 44-4 44-4 44-5 44-5 44-6 44-6 44-7
Introduction Feature Dependency For Further Information Feature Description

What is the IP Billing Feature? How It Works Storage of DIA Number in Call Record Benefit of the IP Billing Feature For Further Information Introduction New Service Code What is a TDMA DIA Call? Potential Places for Storing the DIA Table Storage in the DIM for TDMA DIA Storage in the DIM for DDAMA Storage in the Terminating Number Field
AMA Impact

Issue 27
May 2004
44-i
401-610-133A
44-ii
Issue 27
May 2004
IP Billing Feature
44
Introduction
This chapter introduces the IP Billing feature (feature ID 3561.0). This chapter also describes how AMA functionality is affected by this feature and lists feature dependencies for this feature.
Feature Dependency
IP Billing is a feature that is closely related to the TDMA Circuit-Mode Data Services feature. Though IP Billing is described here in a separate chapter, before reading this chapter the reader should read Chapter 40, TDMA Circuit-Mode Data Services Feature.
Issue 27
May 2004
44-1
401-610-133A

For further information about the IP Billing feature, including information about its availability, read the TDMA Circuit Switched Data Optional Feature document, 401-612-211.
44-2
Issue 27
May 2004
IP Billing Feature
Feature Description
What is the IP Billing Feature?
The IP Billing feature gives a Service Provider the ability to bill Direct Internet Access (DIA) for TDMA mobile-originating circuit-mode data calls.
How It Works
TDMA mobile-originating Direct Internet Access data calls are routed to the Interworking Function (IWF), in the same way as other Circuit-Mode Data Services calls. However, once the IWF detects that the number dialed is a Direct Internet Access number, the IWF routes the call to a special Tunneling Server instead of to the Public Switched Telephone Number (PSTN).
Storage of DIA Number in Call Record

For TDMA mobile-originating DIA calls, the DIA number is stored in the call record, for billing purposes. For more on this topic, see AMA Impact on page 44-4.
Benefit of the IP Billing Feature

The IP Billing feature gives Service Providers the opportunity to bill for Internet access. This new service opportunity should increase revenue for Service Providers.

Direct Internet Access is a type of TDMA circuit-mode data call. For AMA-related information on the TDMA Circuit-Mode Data Services feature, read Chapter 40, TDMA Circuit-Mode Data Services Feature. For information about the IP Billing feature, read the TDMA Circuit Switched Data Optional Feature, 401-612-211.
Issue 27
May 2004
44-3
401-610-133A
AMA Impact
Introduction
This section describes AMA impacts of the IP Billing feature.
New Service Code

The IP Billing feature adds a new Service Code for the Event Description Field Value for Event Type 012 for the Data Module (Initial Assigned TDMA Data Service Configuration). The value for this new Service Code is 0x2, Direct Internet Access. For the layout of this field within AMASE Table 497, see Table 4-47 on page 4-77 in Chapter 4, AMASE Tables.
What is a TDMA DIA Call?

For AMA purposes, a call is defined as a TDMA DIA call if data is received from the IWF and the Service Feature Code indicates Async Direct Internet Access (0x2). For all TDMA DIA calls, the Direct Internet Access number can be stored in the AMA record.
Potential Places for Storing the DIA

Service Providers have the option of storing the DIA number for a TDMA DIA call in one of several places in the call record for the call:
the Digit Information Module for Direct Internet Access (using the DIM for TDMA DIA entry on the ecp RC/V form) the Digit Information Module for DDAMA (using the DDAMA feature and the DIM for DDAMA entry on the ecp RC/V form) the Terminating Number field in the base structure code layout
Table 44-1, "How to Determine Where a TDMA DIA Number Will Be Placed in the AMA Record, shows where the DIA number will be placed in the call record, for various possible settings of the related FAF and ecp RC/V forms.
44-4
Issue 27
May 2004
IP Billing Feature
Table
Table 44-1 on page 44-5 shows where the DIA number will be placed in the call record, for the various possible settings of FAF and ecp RC/V forms. Table 44-1. How to Determine Where a TDMA DIA Number Will Be Placed in the AMA Record and the ECP RC/V Entry for Digit Information Module for DDAMA is... ON or OFF and the DDAMA Feature in the FAF file is.... then the Terminating Number Field contains... and the Digit Information Module for TDMA DIA is... and the Digit Information Module for DDAMA is...
If the ECP RC/V Entry Digit Information Module for TDMA DIA is... ON
ON or OFF
zeroes*
Created and contains the DIA number not created
not created.
OFF
ON
ON
zeroes*
created and contains the DIA number not created not created
OFF OFF
OFF ON or OFF
ON OFF
the DIA number the DIA number
not created not created
* Technically speaking, this is the digit analysis results. However, no digit analysis is performed for a TDMA Circuit-Mode Data mobile-originated call, so zeroes are placed in this field.
Storage in the DIM for TDMA DIA

If the Digit Information Module for TDMA DIA entry is set to y on the ecp RC/V form, the DIA number will be stored in the Digit Information Module for TDMA DIA (whether the DDAMA feature and DIM for DDAMA via ecp RC/V line are on, or not). This method can store a DIA number of up to 50 digits. The Generic Context ID used to identify the DIM for TDMA DIA is 90011.
Issue 27
May 2004
44-5
401-610-133A
Storage in the DIM for DDAMA

If you turn off the Digit Information Module for TDMA DIA entry on the ecp RC/V form, and turn on the Digit Information Module for DDAMA entry on the ecp RC/V form, and turn on DDAMA in the FAF file, the DIA will be stored in the Digit Information Module for DDAMA. This method can store a DIA number of up to 50 digits. The Generic Context ID used to identify the DIM for DDAMA is 90002. NOTE: If both the DIM for TDAM DIA and the DIM for DDAMA are on and the DDAMA FAF is on, then only the DIM for TDMA DIA will be appended. Since both modules would contain the same information (the Direct Internet Access number) the DIM for DDAMA is suppressed.
Storage in the Terminating Number Field

If you turn off both the Digit Information Module for TDMA DIA and Digit Information Module for DDAMA entries on the ecp RC/V form and the DDAMA FAF is on, the DIA information will be placed in the Terminating Number field in the base structure code layouts. This method can store a DIA of up to 15 digits. If you turn off the Digit Information Module for TDMA DIA on the ecp RC/V form and the Digit Information Module for DDAMA entry on the ecp RC/V form is on or off, and the DDAMA FAF is off, the DIA information will be placed in the Terminating Number field in the base structure code layouts. This method can store a DIA of up to 15 digits.
44-6
Issue 27
May 2004
IP Billing Feature
The IP Billing feature depends upon the TDMA Circuit-Mode Data Services feature. For AMA information about the TDMA Circuit-Mode Data Services feature, read Chapter 40, TDMA Circuit-Mode Data Services Feature. For more general information about the TDMA Circuit-Mode Data Services feature, read the TDMA Circuit Switched Data Optional Feature, 401-612-211.
Issue 27
May 2004
44-7
401-610-133A
44-8
Issue 27
May 2004
45
45-1 45-1 45-2 45-3 45-3 45-3 45-3 45-3 45-4 45-5 45-5 45-5 45-5 45-5 45-6 45-6 45-6 45-6 45-6 45-7 45-7 45-7
Introduction Feature Dependency For Further Information Feature Description

What is the CDMA Circuit IP Services Feature? How It Works Benefit of the CDMA Circuit IP Services Feature New CDMA Circuit IP Services Indicator Storage of the Dialed Numeric Digits From the IWF Introduction Use of Existing DDAMA Feature Use of Existing Digit Information Module Call Disposition Indicator Introduction How It Works In What Cases is the DIM Used? When is the Terminating Number Field Used? Table More About the DIM Module For Further Information
AMA Impact

The DDAMA Feature: How It Works

Issue 27
May 2004
45-i
401-610-133A
The DDAMA Feature as Used by the CDMA Circuit IP Services Feature

45-8 45-8 45-8 45-9 45-9 45-9 45-9
Introduction How It Works
About the Digit Information Module as Used by the DDAMA and CDMA Circuit IP Services Features

Introduction Generic Context Identifier for the DDAMA Feature For Further Information
45-ii
Issue 27
May 2004
45
Introduction
This chapter introduces the CDMA Circuit IP Services feature (feature ID 4475.0). This chapter also describes how AMA functionality is affected by this feature and lists feature dependencies for this feature.
Feature Dependency
The CDMA Circuit IP Services feature depends upon the CDMA Circuit-Mode Data Services feature. For AMA information on the CDMA Circuit-Mode Data Services feature, read Chapter 25, CDMA Circuit-Mode Data Services Feature. For more general information about the CDMA Circuit-Mode Data Services feature, read the CDMA Circuit-Mode Data Service Description and Set-up document, 401-610-098.
Issue 27
May 2004
45-1
401-610-133A

For further information about the CDMA Circuit IP Services feature, read the CDMA Circuit IP Services Optional Feature document, 401-612-347.
45-2
Issue 27
May 2004
Feature Description
What is the CDMA Circuit IP Services Feature?
The CDMA Circuit IP Services feature gives a Service Provider the ability to control access to intranets and the general internet for CDMA Circuit-Data Quick Net Connect calls. In addition, information has been added to AMA so that access to service provider intranets can be billed at a different rate than access to the general internet.
How It Works
CDMA Circuit Data Quick Net Connect data calls are routed to the Inter-Working Function (IWF) in the same way as other circuit-data calls. However, once the IWF detects that the call is a Quick Net Connect call, the call is routed to an IP network, rather than to the Public Switched Telephone Network (PSTN). CDMA Circuit IP Services adds a comparison of the dialed digits to a set of Vanity Dial Codes in the IWF. If there is a match, then the mobile IP address is selected from the IP address pool associated with the Vanity Dial Code. The service providers IP network can be configured to allow or prohibit access to specific IP networks based on the mobile IP address. After a Quick Net Connect call ends, the IWF returns the dialed digits and a disposition code to the ECP. The ECP adds the dialed numeric digits1 and the CDMA Circuit IP Services Indicator to the AMA record.
Benefit of the CDMA Circuit IP Services Feature

The CDMA Circuit IP Services feature gives Service Providers a way to control access to intranet and internet networks. The feature also provides additional information in the AMA records so that access to intranets can be billed differently from access to the general internet.
New CDMA Circuit IP Services Indicator

A new Generic Context ID has been created to indicate CDMA Circuit IP Services calls. The new value for Generic Context ID is 90025.
Any * or # digits that are in the digits string are stripped off.
Issue 27
May 2004
45-3
401-610-133A
Storage of the Dialed Numeric Digits From the IWF

The CDMA Circuit IP Services feature uses the existing Dialed Digits in AMA (DDAMA) feature to store the dialed numeric digits from the IWF in the Digit Information Module (DIM) if the DDAMA feature is on2 and the Digit Information Module for DDAMA is on via ecp RC/V. If the module is not on, the dialed numeric digits from the IWF are stored in the Terminating Number field in the AMA record for the call, instead. For more on this topic, see The DDAMA Feature: How It Works on page 45-6 and The DDAMA Feature as Used by the CDMA Circuit IP Services Feature on page 45-8.
If the DDAMA feature is off the number is discarded.
45-4
Issue 27
May 2004
AMA Impact
Introduction
This section describes AMA impacts of the CDMA Circuit IP Services feature.
Use of Existing DDAMA Feature

The CDMA Circuit IP Services feature makes use of the existing Dialed Digits in AMA (DDAMA) feature to store the dialed numeric digits received from the IWF. For more about the DDAMA feature, see The DDAMA Feature: How It Works on page 45-6.
Use of Existing Digit Information Module

The CDMA Circuit IP Services feature uses the Digit Information Module to store an indicator of the type of call and the call disposition as received from the IWF at the end of the call. For more about the Digit Information Module as used by the CDMA Circuit IP Services feature, see Module Generation Criteria for CDMA Circuit IP Services on page 45-8.
Call Disposition Indicator

The CDMA Circuit IP Services Indicator is defined in Table 45-1 on page 45-5. Table 45-1. Byte Byte 1 (leftmost byte) Definition of CDMA Circuit IP Services Indicator Definition Type of Quick Net Connect call 1 = Single Stack. 2 = Double Stack. Byte 2 through 4 - IWF disposition code 000 = Normal/Success. 001 = RADIUS Authentication Failure. 255 = Other Failure.
Issue 27
May 2004
45-5
401-610-133A
The DDAMA Feature: How It Works

Introduction
The Dialed Digits in AMA (DDAMA) feature is a previously-existing AMA feature that captures the exact digit string dialed by the cellular subscriber when accessing the Flexent/AUTOPLEX wireless network.
How It Works
The DDAMA feature captures the dialed numeric digits from the IWF by the cellular subscriber and places this information into one of the following two places in the AMA record for the call:

in the appended Digit Information Module (DIM) for DDAMA in the Terminating Number field of the AMA record for this call
In What Cases is the DIM Used?

If both the DDAMA Feature Activation File (FAF) and the ECP RC/V entry Append Digit Information Module for DDAMA are turned on, then the dialed numeric digits from the IWF will be stored in the Digit Information Module. In this case, the Terminating Number field of the AMASE record for this call is blank.
When is the Terminating Number Field Used?

If the DDAMA Feature Activation File (FAF) is turned on but the ECP RC/V entry Append Digit Information Module for DDAMA is turned off, then the dialed numeric digits from the IWF will be stored in the Terminating Number field of the AMASE record for this call.
45-6
Issue 27
May 2004
Table
Table 45-2 on page 45-7 shows the different scenarios for storage of an incoming dialed numeric digits from the IWF by the DDAMA feature. Table 45-2. Storage of a Dialed Digit String by the DDAMA Feature and the ECP RC/V Entry for Digit Information Module for DDAMA is... ON then the Terminating Number Field contains... the digit analysis results and the Digit Information Module is... Created and contains the dialed numeric digits from the IWF not created
ON
ON
OFF
the dialed digits string (without any * or #) the digit analysis results
OFF
OFF
not created
More About the DIM Module

For more about the DIM Module as used by the DDAMA (and CDMA Circuit IP Services) features, read About the Digit Information Module as Used by the DDAMA and CDMA Circuit IP Services Features on page 45-9.

For further information about the DDAMA feature, read the Dialed Digits in Automatic Message Accounting (DDAMA) Optional Feature document, 401-612097.
Issue 27
May 2004
45-7
401-610-133A
The DDAMA Feature as Used by the CDMA Circuit IP Services Feature

Introduction
The CDMA Circuit IP Services feature uses the DDAMA feature to store the dialed numeric digits received by the IWF as the digits dialed in the AMA record for the call.
How It Works
The DDAMA feature as used by the CDMA Circuit IP Services feature works in the same way as described in The DDAMA Feature: How It Works on page 45-6. Table 45-3 on page 45-8 shows how the CDMA Circuit IP Services dialed numeric digits from the IWF are stored by the DDAMA feature. Table 45-3. Storage of Dialed Digits by the DDAMA Feature and the ECP RC/V Entry for Digit Information Module for DDAMA is... ON then the Terminating Number Field contains... zeroes* and the Digit Information Module is... created and contains the dialed digits not created not created
ON
ON OFF
OFF OFF
the dialed digits zeroes*
* The digit analysis results are stored in this field. However, no digit analysis is performed for a CDMA Circuit-Mode Data call, so zeroes are placed in this field. AMA Search will print these fields as blank. For Quick Net Connect calls that are attempted but do not complete, two different possibilities exist for these fields. If accounting data is received from the IWF, zeroes are stored in the Terminating Number field, and AMA Search will print this field as zeroes. If the call fails and no accounting data is received from the IWF, meaningless digits will be stored in this field and AMA Search will print this field as blanks.
45-8
Issue 27
May 2004
About the Digit Information Module as Used by the DDAMA and CDMA Circuit IP Services Features
Introduction
This section describes the Digit Information Module as used by the DDAMA feature and the CDMA Circuit IP Services feature.
Generic Context Identifier for the DDAMA Feature

The value of the Generic Context Identifier field for the DDAMA feature is 90002 - Dialed Digits in AMA.

Issue 27
May 2004
45-9
401-610-133A
45-10
Issue 27
May 2004
46
46-1 46-1 46-2 46-2 46-2 46-2 46-2 46-2 46-3 46-4 46-4 46-4 46-4 46-4 46-5 46-5 46-5 46-6
Introduction For Further Information Capability Description

Introduction What is the PRI Capability? Terminology What AMA Information is Stored for PRI? How Does It Work? Limitations Signalling Type for PRI/PRA Five Locations Calling Party Category Field Trunk Network Number Field Incoming Tandem TNN Field Outgoing Tandem TNN Field Trunk Information Module
AMA Impact

Note About CPN Modules
Issue 27
May 2004
46-i
401-610-133A
46-ii
Issue 27
May 2004
46
Introduction
This chapter provides information on the Primary Rate Interface (PRI) capability provided in the AMA subsystem. This capability is used by a CDMA feature, 5ESS Switch Wireless Primary Rate Interface for CDMA Dual Mode Mobiles feature (feature ID 2741).

More detailed information about this feature can be found in 401-612-333, 5ESS DCS Wireless Primary Rate Interface for CDMA Optional Feature document.
Issue 27
May 2004
46-1
401-610-133A
Capability Description
Introduction
This section describes the Primary Rate Interface capability and tells how it is used by the 5ESS Wireless Primary Rate Interface for CDMA Dual Mode Mobiles feature.
What is the PRI Capability?

The Primary Rate Interface Capability provides the ability to connect Customer Premises Equipment (CPE) directly to the Flexent/AUTOPLEX wireless network. This CPE could be a Private Branch Exchange (PBX) or any other equipment that is compatible with the ISDN Primary Rate Interface specifications (which are applicable to the United States) or ISDN Primary Rate Access (PRA) specifications (which are applicable to countries outside the United States).1
Terminology
The term Primary Rate Interface when used to refer to countries outside of the United States is called Primary Rate Access (PRA). In this document the term Primary Rate Interface will be used to stand for either term.
What AMA Information is Stored for PRI?

For the PRI capability, AMA records store the PRI/PRA signaling type and the calling party category code. This information gives service providers the ability to distinguish calls on Network Trunk Group (NTG) trunks that use PRI/PRA signaling.
How Does It Work?

To report the AMA information, the PRI capability makes use of a previouslyexisting feature, the Calling Party Category feature. The Calling Party Category feature stores the signaling type and the category of the incoming call in the Calling Party Category Module.
PRA (for international applications) is being considered for a future release.
46-2
Issue 27
May 2004
For more information on the Calling Party Category feature, see Chapter 35, AMA Calling Party Category Information Feature.
Limitations
This feature only works for calls between a CDMA mobile and customer premises equipment (CPE) that is connected to the 5ESS Switch using a Network Trunk Group (NTG) that uses PRI/PRA signaling.
Issue 27
May 2004
46-3
401-610-133A
AMA Impact
Signalling Type for PRI/PRA
The PRI capability adds a Signaling Type for PRI/PRA (BCD character 2, value 3 in AMASE Table 566 on page 4-79 and BCD character 1, value 3 in AMASE Table 2004 on page 4-130). For a complete list of valid signalling types, see Table 4-49 on page 4-79.
Five Locations
The PRI/PRA Signalling type can print in five locations in AMA records:

the Calling Party Category field in the base structure code layout the Trunk Network Number field in the base structure code layout the Incoming Tandem TNN field in the base structure code layout the Outgoing Tandem TNN field in the base structure code layout the Trunk Information Module
Calling Party Category Field

If there is Calling Party Category information in the record, this information will be placed in the Calling Party Category field in the base structure code layout.2 The Calling Party Category field appears in the following base structure code layouts: x2118, x2119, and x2329 - x2335.
Trunk Network Number Field

PRI/PRA signalling type information can also appear in the Trunk Network Number field in the base structure code layout. The Trunk Network Number field appears in the following base structure code layouts: x2329 - x2336 and x2415.
No other criteria is needed. For more information on this, see Chapter 35, AMA Calling Party Category Information Feature.
46-4
Issue 27
May 2004
Incoming Tandem TNN Field

PRI/PRA signalling type information can also appear in the Incoming Tandem TNN field in the base structure code layout. The Incoming Tandem TNN field appears in the following base structure code layouts: x2118 and x2119.
Outgoing Tandem TNN Field

PRI/PRA signalling type information can also appear in the Outgoing Tandem TNN field in the base structure code layout. The Outgoing Tandem TNN field appears in the following base structure code layouts: x2118 and x2119.

PRI/PRA signalling type information can also appear in the Trunk Information Module. For more about this, see Primary Rate Interface Feature on page 5-72.
Issue 27
May 2004
46-5
401-610-133A
Note About CPN Modules

The Calling Party Number (CPN) Outgoing Calls Module (329) and Calling Party Number Incoming Calls Module-1 and Module-2 (330 and 331) may be appended to the AMA record for PRI calls. For more about CPN and the rules for displaying and not displaying a CPN, see the Module Generation Criteria for these modules in Chapter 18, Calling Number Identification Presentation and Restriction Capability Feature.
46-6
Issue 27
May 2004
47
47-1 47-1 47-2 47-2 47-2 47-2 47-2 47-3 47-3 47-3 47-3 47-3 47-4 47-4 47-4 47-4 47-4 47-4 47-5

Introduction Background How Many Block Sequence Numbers Are Needed? Why is This Feature Needed? How Does the Feature Work? Why is This an Optional Feature? Software Changes Required New Hardware Required CAUTION! Introduction AMA Block Sequence Number Increased No Change in Field Size Fields Tools Updated
AMA Impact

Feature Interaction
Issue 27
May 2004
47-i
401-610-133A
47-ii
Issue 27
May 2004
47
Introduction
This chapter provides information on the Seven Digit AMA Block Sequence Number optional feature and describes how AMA functionality is affected by this feature.

For further information about this feature, including an explanation of the input and output messages associated with it, and how to turn on the feature, see 401-612511, Seven Digit AMA Block Sequence Number optional feature document. Wireless Lucent Alert 01-222 also explains this feature.
Issue 27
May 2004
47-1
401-610-133A
Feature Description
Introduction
This section describes the Seven Digit AMA Block Sequence Number feature.
Background
AMA records are combined into AMA blocks before being sent off the ECP.1 Each AMA block on the ECP is assigned a unique number called an AMA block sequence number. The numbers are assigned and incremented sequentially, and they roll over from 999,999 to 000,000. Although permanent storage of AMA records takes place elsewhere than the ECP2 the standards advise that two days worth of AMA records be kept on the ECP.
How Many Block Sequence Numbers Are Needed?

Traditionally, AMA block sequence numbers are represented by six digits ranging from 000,000 to 999,999, for a total of 1 million AMA blocks. On the average, an AMA block stores about ten AMA records. Thus the one million maximum AMA blocks can store approximately up to ten million AMA records without overflowing.
Why is This Feature Needed?

With the increase in call capacity provided by ECP R18.0, one million AMA blocks may not be sufficient to store two days worth of AMA records. The current sixdigit AMA block sequence numbers will overflow and begin to overwrite by wraparound once call capacity approaches or exceeds approximately 500K BHCA. This results in loss of AMA records.
1 2
For more about AMA blocks, read About AMA Blocks on page 8-6. For more information about permanent storage of AMA records, and how AMA works in general, see Chapter 1Overview of AMA.
47-2
Issue 27
May 2004
How Does the Feature Work?

To enable service providers to store at least two days worth of backup AMA data even after 700K Busy Hour Call Attempt threshold is reached, this feature increases the valid AMA block sequence number range to seven digits (9,999,999). The new AMA block sequence number increase will be represented in seven digits ranging from 0,000,000 to 9,999,999. These ten million AMA block numbers can store approximately up to one hundred million AMA records without overflowing.
Why is This an Optional Feature?

Only service providers who have high call capacity in their networks (approximately above 500K BHCA) will require this feature.
Software Changes Required

Service providers who choose to use the Seven Digit AMA Block Sequence Number feature need to upgrade their Billing Mediation Devices (BMDs) to handle seven-digit AMA block sequence numbers.
New Hardware Required

Service providers requiring the use of the Seven Digit AMA Block Sequence Number feature also need to add one extra disk pair (Moving Head Disk, or MHD) to store the additional AMA blocks. The addition of this new MHD pair may require new hardware configurations.
CAUTION!
Service providers who switch to use of seven-digit AMA block sequence numbers SHOULD NOT switch back to use of six-digit AMA block sequence numbers. Switching back will cause the software to ignore all block sequence numbers greater than 999,999. This could cause loss of the majority of the AMA records.
Issue 27
May 2004
47-3
401-610-133A
AMA Impact
Introduction
This section describes changes to AMA caused by the Seven Digit AMA Block Sequence Number feature.
AMA Block Sequence Number Increased

The Seven Digit AMA Block Sequence Number feature increases the AMA block sequence number by one digit. AMASE Table 804, Seven Digit Number, is used to record the AMA Block Sequence number.
No Change in Field Size

There is no change in field size for AMASE Table 804 for this feature. Before the Seven Digit AMA Block Sequence Number feature was introduced, the traditional AMA block sequence number used one pad digit plus six digits to show range. The Seven Digit AMA Block Sequence Number feature uses seven digits (six plus the former pad digit) to show a greater range. Thus, the Seven Digit AMA Block Sequence Number feature did NOT change the field size in AMASE Table 804.
Fields
The AMA block sequence number is stored in two fields in two different structure code layouts: First Disk Block Sequence Number in structure code layout 09038, CLDS Header Tape-Only Tracer, and Last Disk Block Sequence Number in structure code layout 09039, CLDS Trailer Tape-Only Tracer. These fields are explained in:

First/Last Disk Block Sequence Number Ranges on page 4-98 Ranges with Seven Digit AMA Block Sequence Number Feature on page 4-99
Tools Updated
All AMA tools have been updated to recognize the seven digit AMA block sequence number.
47-4
Issue 27
May 2004
Feature Interaction
Issue 27
May 2004
47-5
401-610-133A
47-6
Issue 27
May 2004
48
48-1 48-1 48-2 48-2 48-2 48-2 48-3 48-3 48-3 48-3 48-3 48-3 48-4 48-4 48-4 48-5

Introduction What is Prepaid Charging? How Does Prepaid Charging Work? Introduction Generic Context ID Use of Existing Digit Information Module Module Generation Criteria for IS-826 Prepaid Base Feature WIN Standard DMH Service ID Stored in Digits Recorded Field Contents of WIN Standard DMH Service ID Table Multiple WIN Standard DMH Service IDs
AMA Impact

Feature Interaction
Issue 27
May 2004
48-i
401-610-133A
48-ii
Issue 27
May 2004
48
Introduction
This chapter describes the IS-826 Prepaid Base optional feature and describes how to interpret the AMA records produced by this feature.

For further information about this feature, see 401-612-513, IS-826 Prepaid Base optional feature document.
Issue 27
May 2004
48-1
401-610-133A
Feature Description
Introduction
This section describes the IS-826 Prepaid Base feature, which sets up standards so that service providers can implement Prepaid Charging.
What is Prepaid Charging?

Prepaid Charging (PPC) allows subscribers to pay for voice telecommunications service prior to usage.
How Does Prepaid Charging Work?

A PPC subscriber establishes an account with the service provider to access voice telecommunication service at home and in roaming networks. Charges for voice telecommunication services are applied to the PPC account by decrementing the account in real time. The PPC subscriber may be notified about the account information at the beginning or during the end of the voice telecommunication service. When the account balance is low, the subscriber may be notified so that the subscriber may refill the account. When the account balance is below a predefined threshold, the subscriber's use of voice telecommunications service may be de-authorized.
48-2
Issue 27
May 2004
AMA Impact
Introduction
This section describes changes to AMA caused by the IS-826 Prepaid Base feature.
Generic Context ID
The IS-826 Prepaid Base feature uses a new Generic Context ID of 90026, for WIN Standard DMH Service ID.

This feature uses the existing Digit Information Module 621 (DIM) for structure codes x2329, x2330, x2331, x2332, x2333, x2334, and x2335.
Module Generation Criteria for IS-826 Prepaid Base Feature

The Digit Information Module storing the WIN Standard DMH Service ID will be appended to AMA records with the x2329 - x2335 structure codes if the following generation criteria are met:

The WINCAP FAF feature is active in the FAF file. The Append Standard DMH_ServiceID to AMA record field on the ecp RC/V form is set to y. A WIN Standard DMH Service ID exists for the call.
WIN Standard DMH Service ID Stored in Digits Recorded Field

The Digits Recorded field in the Digit Information Module is used by the IS826 Prepaid Base feature to store between one and three thirteen-digit WIN Standard DMH Service IDs.
Issue 27
May 2004
48-3
401-610-133A
Contents of WIN Standard DMH Service ID

The WIN Standard DMH Service ID consists of thirteen characters: a 5 digit Market ID (ranging in values from 0-65535), a 3 digit Market Segment ID (ranging in values from 0-255) and a 5 digit DMH Service ID (ranging in values from 065535).
Table
Table 48-1 on page 48-4 shows the first thirteen digits of the Digits Recorded field as used by the IS-826 Prepaid Base feature to store one WIN Standard DMH Service ID. Table 48-1. Digits Recorded Field as Used by the IS-826 Prepaid Base Feature Meaning First Market ID (ranging in values from 0-65535) First Market Segment ID (ranging in values from 0255) First Market DMH Service ID (ranging in values from 0-65535)
BCD Characters 1-5 6-8 9-13
Multiple WIN Standard DMH Service IDs

Up to three WIN Standard DMH Service IDs, for a total of 39 digits, can be stored in the Digits Recorded field for a single call.
48-4
Issue 27
May 2004
Feature Interaction
Issue 27
May 2004
48-5
401-610-133A
48-6
Issue 27
May 2004
49
49-1 49-1 49-2 49-2 49-2 49-3 49-3 49-3 49-3 49-3 49-3 49-4 49-5
Introduction Availability Feature Description

Introduction Feature Description Introduction Generic Context ID Use of Existing Digit Information Module Module Generation Criteria Contents of Digits Recorded Field Table
AMA Impact

Feature Interaction
Issue 27
May 2004
49-i
401-610-133A
49-ii
Issue 27
May 2004
49
Introduction
This chapter describes the Speech Handler Trunk Information in AMA feature and describes how to interpret the AMA records produced by this feature.
Availability
The Speech Handler Trunk Information in AMA feature is a TDMA only feature.
Issue 27
May 2004
49-1
401-610-133A
Feature Description
Introduction
This section describes the Speech Handler Trunk Information in AMA feature.
Feature Description
The Speech Handler Trunk Information in AMA feature gives service providers a way of reporting speech handler information on a per call basis. Service providers can use this information for trouble analysis and to anticipate potential problems with the speech handlers. Service providers can access this information in real time using the AMA Dump for Selected Subscribers feature or print formatted reports using the amasearch tool. For more information, see AMA Search with 15 Digit DN, 401-612-080, and AMA Dump for Selected Subscribers, 401-601-029.
49-2
Issue 27
May 2004
AMA Impact
Introduction
This section describes changes to AMA caused by the Speech Handler Trunk Information in AMA feature.
Generic Context ID
The Speech Handler Trunk Information in AMA feature uses a new Generic Context ID of 10836, for Speech Handler Trunk Information in AMA.

This feature uses the existing Digit Information Module 621 (DIM) for structure codes x2411, x2421, and x2329 - 2338.

The Digit Information Module storing Speech Handler Trunk Information in AMA information will be appended to AMA records for each TDMA call with the x2411, x2421, and x2329 - 2338 structure codes if the following generation criteria is met:
The Speech Handler Information in AMA field on the ecp RC/ V form is set to y.
Contents of Digits Recorded Field

The Digits Recorded field in the Digit Information Module is used by the Speech Handler Trunk Information in AMA feature to record the speech handler information for the TDMA call, which consists of the following three numbers:

DCS number Speech handler trunk group number Speech handler trunk member number
In the Digit Information Module the numbers are stored together in the Digits Recorded field in the order shown in Table 49-1 on page 49-4.
Issue 27
May 2004
49-3
401-610-133A
Table
Table 49-1 on page 49-4 shows the first ten digits of the Digits Recorded field as used by the Speech Handler Trunk Information in AMA feature to store speech handler information. Table 49-1. Digits Recorded Field as Used by the Speech Handler Trunk Information in AMA Feature Meaning Padding Two-digit DCS number associated with the trunk (ranging in value from 0-99) Speech Handler Trunk Group Number Speech Handler Trunk Member Number SIGN (C)
BCD Characters 1 2-3 4-7 8-11 12
NOTE: Information in each of these fields will be right justified and padded with zeroes.
49-4
Issue 27
May 2004
Feature Interaction
Issue 27
May 2004
49-5
401-610-133A
49-6
Issue 27
May 2004
50
50-1 50-1 50-2 50-2 50-2 50-2 50-2 50-2 50-3 50-3 50-3 50-3 50-3 50-4 50-4 50-5 50-5 50-5 50-5
Introduction For Further Information Feature Descriptions

Introduction What is the Specific Called Party Digit String Trigger Feature? What is the IS-826 Locally-Allowed Specific Digit String Trigger Feature? Warning Accessing Information for These Features
AMA Impact for the Specific Called Party Digit String Trigger Feature

Introduction Generic Context IDs Use of Existing Digit Information Module Module Generation Criteria IS-848 Billing Indicator in Digits Recorded Field IS-848 Charge Information in Digits Recorded Field
AMA Impact for the IS-826 Locally-Allowed Specific Digit String Trigger Feature

Introduction Generic Context IDs Use of Existing Digit Information Module
Issue 27
May 2004
50-i
401-610-133A
Module Generation Criteria IS-848 Charge Information in the Digits Recorded Field
50-5 50-5 50-7 50-8
50-ii
Issue 27
May 2004
50
Introduction
This chapter describes the following two WIN specific digit string trigger features

Specific Called Party Digit String Trigger feature IS-826 Locally-Allowed Specific Digit String Trigger feature
and tells how to interpret the AMA records produced by them.

For further information about the Specific Called Party Digit String Trigger feature, see the IS-771 Specific Called Party Digit String Trigger optional feature document, 401-612-542. For further information about the IS-826 Locally-Allowed Specific Digit String Trigger feature, see 401-612-609, IS-826 Locally Allowed Specific Digit String Trigger Optional Feature document.
Issue 27
May 2004
50-1
401-610-133A
Introduction
This section describes the two WIN specific digit string trigger features.
What is the Specific Called Party Digit String Trigger Feature?

The Specific Called Party Digit String Trigger feature is a Win office-based trigger that has been defined for mobile call originations in IS-771 WIN standards. The Specific Called Party Digit String trigger (SCPDS) is detected when a subscriber dials an appropriate sequence of digits according to the dialing plan in use. One use for this feature would be to provide a specific sequence of digits as the SCPDS trigger which could trigger a unique service for a given subscriber.
What is the IS-826 Locally-Allowed Specific Digit String Trigger Feature?

The IS-826 Locally-Allowed Specific Digit String Trigger feature provides the service provider the Wireless Intelligent Network (WIN) standard provision to deal with locally-allowed numbers (for example, 911). This feature also allows the service provider to implement emergency service regardless of the subscribers account balance. The AMA change for the IS-826 Locally-Allowed Specific Digit String Trigger feature is to capture the IS-848 charging information for the call in the AMA record.
Warning
Any numbering plan used must ensure that emergency service numbers are distinct from the provisionable specific digit string.
Accessing Information for These Features

Service providers can access information for these features in real time using the AMA Dump for Selected Subscribers feature or print formatted reports using the amasearch tool. For more information, see AMA Search with 15 Digit DN, 401612-080A, and AMA Dump for Selected Subscribers, 401-601-029.
50-2
Issue 27
May 2004
AMA Impact for the Specific Called Party Digit String Trigger Feature
Introduction
This section describes changes to AMA caused by the Specific Called Party Digit String Trigger feature.
Generic Context IDs

The Specific Called Party Digit String Trigger feature uses the following new Generic Context IDs:

90031 - for IS-848 Billing Indicator 90032 - for IS-848 Charge Information

This feature uses the existing Digit Information Module 621 (DIM) for structure code layouts x2329, x2330, x2332 and x2333.

The Digit Information Modules storing the IS-848 Billing Indicator and IS-848 Charge Information will be appended to AMA records with the x2329, x2330, x2332 and x2333 structure code layouts if the following generation criteria is met:

The WINCAP Feature Activation File (FAF) is ON. The WINSCPDSORIG Feature Activation File (FAF) is ON. The ECP RC/V entry IS-848 Billing Indicator is set to Y. The ECP RC/V entry IS-848 Charging Information is set to Y.
NOTE: If both RC/V forms are turned on, you will get two DIM modules, one containing the IS-848 Billing Indicator and one containing the IS-848 Charge Information. Separate RC/V controls are given for IS-848 Billing Indicator and IS-848 Charge Information, so a service provider can choose to receive both, one or the other, or neither.
Issue 27
May 2004
50-3
401-610-133A
IS-848 Billing Indicator in Digits Recorded Field

When the Generic Context ID of 90031 is used, the two FAFs listed in Module Generation Criteria on page 50-3 are turned on, and the ECP RC/V entry IS-848 Billing Indicator is set to Y, the Digits Recorded field in the Digit Information Module stores the IS-848 Billing Indicator. The IS-848 Billing Indicator is stored as four BCD characters where BCD characters 1-3 are the number and BCD character 4 is the SIGN (hex C).
IS-848 Charge Information in Digits Recorded Field

When the Generic Context ID of 90032 is used, the two FAFs listed in Module Generation Criteria on page 50-3 are turned on, and the ECP RC/V entry IS-848 Charging Information is set to Y, the Digits Recorded field in the Digit Information Module stores the IS-848 Charge Information. The IS-848 Charge Information is stored as four BCD characters where BCD characters 1-3 are the number and BCD character 4 is the SIGN (hex C).
50-4
Issue 27
May 2004
AMA Impact for the IS-826 LocallyAllowed Specific Digit String Trigger Feature
Introduction
This section describes changes to AMA caused by the IS-826 Locally-Allowed Specific Digit String Trigger feature.
Generic Context IDs

The IS-826 Locally-Allowed Specific Digit String Trigger feature uses the following Generic Context ID:
90032 - for IS-848 Charge Information

This feature uses the existing Digit Information Module 621 (DIM) for structure code layouts x2329, x2330, x2332 and x2333.

The Digit Information Module storing the IS-848 Charge Information will be appended to AMA records with the x2329, x2330, x2332 and x2333 structure code layouts if the following module generation criteria is met:

The WINCAP Feature Activation File (FAF) is ON. The Feature Activation File for the IS-826 Locally-Allowed Specific Digit String Trigger feature is ON. The ECP RC/V entry IS-848 Charging Information is set to Y. IS-848 charge information exists for the call.
IS-848 Charge Information in the Digits Recorded Field

When the Generic Context ID of 90032 is used, the FAF listed in Module Generation Criteria on page 50-5 is turned on, and the ECP RC/V entry IS-848 Charging Information is set to Y, the Digits Recorded field in the Digit Information Module stores the IS-848 Charge Information.
Issue 27
May 2004
50-5
401-610-133A
The IS-848 Charge Information is stored as four BCD characters where BCD characters 1-3 are the number and BCD character 4 is the SIGN (hex C).
50-6
Issue 27
May 2004
These features depend on the WINCAP feature.
Issue 27
May 2004
50-7
401-610-133A
The two WIN specific digit string trigger features do not have any feature interactions.
50-8
Issue 27
May 2004
51
51-1 51-1 51-2 51-2 51-2 51-2 51-2 51-2 51-2 51-3 51-3 51-4 51-4 51-4 51-5 51-5 51-5 51-5 51-6 51-6 51-7

Introduction Feature Definition How Does It Work? What Information is Recorded? How is the Information Stored? Benefits Increased Disk Usage For Further Information Overview New Structures Introduction Channel Usage Module - Description Module Generation Criteria for the Channel Usage Module Table
AMA Impact

Channel Usage Module

New AMASE Table
Related AMA Tool
Issue 27
May 2004
51-i
401-610-133A
Tool Updated
51-7 51-8
Feature Interaction
51-ii
Issue 27
May 2004
51
Introduction
The TDMA Channel Usage Tracking Tool feature provides an AMA module to collect data concerning TDMA channel usage. This chapter provides information on the TDMA Channel Usage Tracking Tool feature and describes the new AMA functionality added for this feature.

For more information about the TDMA Channel Usage Tracking Tool feature, read the Flexible Channel Allocation (FLCA) Optional Feature document, 401-612-238.
Issue 27
May 2004
51-1
401-610-133A
Feature Description
Introduction
This section describes the TDMA Channel Usage Tracking Tool feature, which works only for TDMA or AMPS calls.
Feature Definition
The TDMA Channel Usage Tracking Tool feature allows service providers to identify the channel or channels that were used for a particular TDMA or AMPS call by collecting channel usage information on a per call basis.
How Does It Work?

Using this feature, channel usage information is collected for each channel used for a call. Up to seven sets of channel usage information are collected for each call. Channel usage information is collected for both FLCA channels and fixed channels.
What Information is Recorded?

In addition to storing the channel used, this feature also stores the associated resources for the call, such as the Cell and PAF number, radio number, carrier number, and so forth. This information can help service providers isolate problem channels.
How is the Information Stored?

The channel usage information collected for a call is stored in a flexible module created for this feature, the Channel Usage Module, and printed as part of the AMA record for the call.
Benefits
The introduction of the Flexible Channel Allocation (FLCA) feature, while allowing greater channel capacity and improved voice quality, also made it difficult to identify channels that might be causing degradation in the network. With Flexible
51-2
Issue 27
May 2004
Channel Allocation, channels are assigned using dynamic channel allocation. Thus, with FLCA, a service provider cannot tell which FLCA channel is asigned on a specific cell or sector at any given time. The TDMA Channel Usage Tracking Tool feature allows service providers to identify the channel or channels that were used for a particular call. This information will help service providers troubleshoot defective channels in their networks.
Increased Disk Usage

The service provider should be aware that there will be significantly increased disk usage on the ECP with this feature.

For more FLCA and about administering the TDMA Channel Usage Tracking Tool feature, read the Flexible Channel Allocation (FLCA) Optional Feature document, 401-612-238.
Issue 27
May 2004
51-3
401-610-133A
AMA Impact
Overview
This section describes AMA impacts for this feature.
New Structures
The following AMA structures were created for the TDMA Channel Usage Tracking Tool feature:

One new AMASE table One new module
Each of these impacts is described in more detail in this chapter.
51-4
Issue 27
May 2004
Channel Usage Module

Introduction
This section describes the Channel Usage Module (800) added by the TDMA Channel Usage Tracking Tool feature.
Channel Usage Module - Description

The Channel Usage Module stores channel usage and associated resource information for each channel used in a call. For more about this module, see Module 800Channel Usage Module on page 5-75.
Module Generation Criteria for the Channel Usage Module

The Channel Usage Module will be appended to the AMA records with structure codes 2329 - x2338 and x2411 if the following criteria are met:

The TDMA Channel Usage Tracking Tool feature is active in the FAF file. The Channel Usage Module is activated via ecp RC/V entry Append to the AMA record: Enable FTchanuse and Append CPCHAN Module to AMA Record. Channel usage information is received for the call. The call is a TDMA or AMPS call.
Issue 27
May 2004
51-5
401-610-133A
New AMASE Table

Table
An AMASE table was added by the TDMA Channel Usage Tracking Tool feature to record channel usage and associated resource information. For a description of the table, see Table 1000 Channel Usage Information on page 4-113.
51-6
Issue 27
May 2004
Related AMA Tool

Tool Updated
The amasearch tool has been updated to recognize the AMASE table and module added for the TDMA Channel Usage Tracking Tool feature.
Issue 27
May 2004
51-7
401-610-133A
Feature Interaction
The TDMA Channel Usage Tracking Tool feature has no interactions with other Flexent/AUTOPLEX wireless network features.
51-8
Issue 27
May 2004
52
52-1 52-1 52-2 52-2 52-2 52-2 52-2 52-3 52-3 52-3 52-3 52-3 52-3 52-3 52-4 52-4 52-4 52-5 52-6 52-7
Introduction
For Further Information Introduction What is the FERCV Feature? What is the Enhanced FERCV Feature? Benefits Introduction Generic Context ID for FERCV Generic Context ID for Enhanced FERCV Use of Existing Digit Information Module Module Generation Criteria for FERCV Module Generation Criteria for Enhanced FERCV Digits Recorded Field for FERCV Table Digits Recorded Field for Enhanced FERCV Table
Feature Description

AMA Impacts

Issue 27
May 2004
52-i
401-610-133A
52-ii
Issue 27
May 2004
52
Introduction
This chapter describes the following two features:
Far End Release Cause Values for ISUP and R2 in the AMA Record (FERCV) feature Enhancement to Far End Release Cause Values in AMA Records (Enhanced FERCV) feature
This chapter also describes how to interpret the AMA records produced by these features.

For more information about these features, read the Far End Release Cause Values for ISUP and R2 in AMA Records optional feature document, 401-612-343.
Issue 27
May 2004
52-1
401-610-133A
Feature Description
Introduction
This section describes both the FERCV and the Enhanced FERCV features.
What is the FERCV Feature?

The Far End Release Cause Values for ISUP and R2 in the AMA Record (FERCV) feature makes it possible for Far End Release Cause values received from the Digital Cellular Switch (DCS) to be placed in the AMA record. If ISUP signaling is used, the following types of calls are recorded: mobile originations, mobile terminations, three-way calls, call forwarding, tandem and special routing calls. If R2 signaling is used, the following mobile-originated calls are recorded: mobile originations, three-way calls, call forwarding tandem and special routing calls.
What is the Enhanced FERCV Feature?

The Enhanced FERCV feature builds upon the Far End Release Cause Value feature by adding the following information to the AMA record for the call:

far end release cause value direction of trunk (incoming or outgoing) on which release cause value is obtained stage (complete or incomplete call) For ISUP, whether a disconnect is received before (incomplete) or after (complete) the connect acknowledge message For R2, whether the call is a network-released incomplete call or complete call, or whether a message with called party status is not available (incomplete) or available (complete) is received.
Benefits
The FERCV and Enhanced FERCV features help the service provider improve analysis of network failures.
52-2
Issue 27
May 2004
AMA Impacts
Introduction
This section describes changes to AMA caused by these features.
Generic Context ID for FERCV

The FERCV feature uses a new Generic Context ID of 90013 (Far End Release Cause Value).
Generic Context ID for Enhanced FERCV

The Enhanced FERCV feature uses a new Generic Context ID of 90034 (Enhanced Far End Release Cause Value).

Both of these features use the existing Digit Information Module 621 (DIM) for structure codes x2118, x2119, x2330 - x2335 and x2339.
Module Generation Criteria for FERCV

The Digit Information Module storing the Far End Release Cause Values for ISUP and R2 in the AMA Record (FERCV) information will be appended to AMA records with the x2118, x2119, and x2329 - x2335 structure codes if the following generation criteria are met:
The Far End Release Cause Values for ISUP and R2 in the AMA Record feature is active in the FAF file. The Digit Information Module is activated via ecp RC/V entry Record Far End Release Cause Values to AMA Record. A non-zero Release Cause Value is received.
Module Generation Criteria for Enhanced FERCV

The Digit Information Module storing information for the Enhanced FERCV feature will be appended to AMA records for each call with the x2118, x2119, x2330 x2335 and x2339 structure codes if the following generation criteria is met:
The FERCV feature is activated in the Feature Activation File (FAF).
Issue 27
May 2004
52-3
401-610-133A
The Enhanced Far End Release Cause Values field on the ecp RC/V form is set to y. A non-zero cause value is received in the DCS messages for a particular call.
Digits Recorded Field for FERCV

The Digits Recorded field in the Digit Information Module is used by the FERCV feature to record the following Enhanced FERCV information:
far end release cause value
In the Digit Information Module numbers conveying this information are stored together in the Digits Recorded field in the order shown in Table 52-1 on page 52-4.
Table
Table 52-1 on page 52-4 shows the Digits Recorded field as used by the FERCV feature. Table 52-1. Digits Recorded Field as Used by the FERCV Feature Meaning Far end release cause value SIGN (hex C) unused
BCD Characters 1-3 4 5-50
Digits Recorded Field for Enhanced FERCV

The Digits Recorded field in the Digit Information Module is used by the Enhanced FERCV feature to record the following Enhanced FERCV information:

far end release cause value direction of trunk (incoming or outgoing) on which release cause value is obtained stage (complete or incomplete call) For ISUP, whether a disconnect is received before (incomplete) or after (complete) the connect acknowledge message
52-4
Issue 27
May 2004
For R2, whether the call is a network-released incomplete call or complete call, or whether a message with called party status is not available (incomplete) or available (complete) is received. In the Digit Information Module numbers conveying this information are stored together in the Digits Recorded field in the order shown in Table 52-2 on page 52-5.
Table
Table 52-2 on page 52-5 shows the Digits Recorded field as used by the Enhanced FERCV feature. Table 52-2. Digits Recorded Field as Used by the Enhanced FERCV Feature Meaning Direction of trunk on which release is obtained: 0 = Incoming; release received on Incoming Trunk 1 = Outgoing; Release received on Outgoing Trunk 2 Stage: 0 = not used 1 = incomplete call 2 = complete call 3-5 6 7-50 Far end release cause value SIGN (hex C) unused
BCD Characters 1
Issue 27
May 2004
52-5
401-610-133A
For the Enhanced FERCV feature to work properly, both the Enhanced FERCV feature and the Far End Release Cause Values for ISUP and R2 in the AMA Record feature must be active. To record the far end (ISUP signaling) release cause values in AMA for ISUP calls, the 5E-ISUP signaling feature must be active. Systems that have R2 signaling only do not require activation of the 5E-ISUP signaling feature. In addition, for the Enhanced FERCV feature, the Record TNN in AMA for Network Released Incomplete Mobile Origination feature must be active.
52-6
Issue 27
May 2004
The FERCV feature and the Enhancd FERCV feature do not interact with any other features. Note that if both of these features are activated on the RC/V form, the Enhanced FERCV feature takes precedence. Therefore, if both of these features are activated on the RC/V form, the Enhanced FERCV feature module will appear and the FERCV feature module will not appear.
Issue 27
May 2004
52-7
401-610-133A
52-8
Issue 27
May 2004
53
53-1 53-1 53-2 53-2 53-2 53-2 53-3 53-3 53-3 53-3 53-4 53-5 53-6 53-7
Introduction
For Further Information Introduction Feature Definition What is 2-step Decimal Format? Introduction New Service Feature Code Related Structure Code Layouts New Treatment of Mobile Serial Number
Feature Description

AMA Impacts

Feature Dependencies Feature Interactions Related Documentation
Issue 27
May 2004
53-i
401-610-133A
53-ii
Issue 27
May 2004
53
Introduction
This chapter describes the Customized ESN Format in AMA Record feature. This chapter also describes how to interpret the AMA records produced by this feature.

For more information about this feature, read the Customized ESN Format in AMA optional feature document, 401-612-583.
Issue 27
May 2004
53-1
401-610-133A
Feature Description
Introduction
This section describes the Customized ESN Format in AMA Record feature.
Feature Definition
The Customized ESN Format in AMA Record feature produces a customized Electronic Serial Number (ESN) format in the AMA record for the call. This customized format is an 11-digit decimal number produced in 2-step decimal format.
What is 2-step Decimal Format?

Two-step decimal format is a customized format for an ESN number produced by carrying out the following steps:
First, the 32-bit ESN is divided into two parts, the upper (most significant bit) 8 bits and the lower 24 bits Next, the upper 8 bits are converted to a 3-digit decimal number and the lower 24 bits are converted to an 8-digit decimal number. Lastly, these two decimal numbers are concatenated to make the 11-digit customized ESN.
53-2
Issue 27
May 2004
AMA Impacts
Introduction
This section describes changes to AMA caused by this feature:

New service feature code New treatment of Mobile Serial Number
New Service Feature Code

The Customized ESN Format in AMA Record feature uses a service feature code of 320. This service feature code is listed in Table 4-70 "AMASE Table 2002" on page 4-119.
Related Structure Code Layouts

If the Customized ESN Format in AMA Record feature is used, the Service Feature field in the following structure code layouts will show the service feature code of 320:

2329 - Cellular-Originated Call Without CI Information 2330 - Cellular-Originated Call With CI Information 2331 - Cellular-Terminated Call 2332 - CPS Cellular-Originated Call With CI Information 2333 - CPS Cellular-Originated Call Without CI Information 2334 - CPS Cellular-Terminated Call-Facility and Air-Time Record 2335 - CPS Cellular-Terminated Call-ICT Facility Timing Record 2337 - CN Handback - Answered Segment Air-Time Record 2411 - Feature Activation/Deactivation
Issue 27
May 2004
53-3
401-610-133A
New Treatment of Mobile Serial Number

If the Customized ESN Format in AMA Record feature is used, the ESN given in the Mobile Serial Number field in the following structure code layouts will be formatted using the 2-step decimal format:

2329 - Cellular-Originated Call Without CI Information 2330 - Cellular-Originated Call With CI Information 2331 - Cellular-Terminated Call 2332 - CPS Cellular-Originated Call With CI Information 2333 - CPS Cellular-Originated Call Without CI Information 2334 - CPS Cellular-Terminated Call-Facility and Air-Time Record 2335 - CPS Cellular-Terminated Call-ICT Facility Timing Record 2336 - CN Slave Switch - Facility and Air-Time Record 2337 - CN Handback - Answered Segment Air-Time Record 2338 - CN Handback - Intermediate Segment Air-Time Record 2411 - Feature Activation/Deactivation 2415 - Mobile Security Entry 2421 - Virtual System AMA Event Recording 2800 - Origination Event 2801 - Termination Event 2802 - Metered Billing
53-4
Issue 27
May 2004
This feature is not dependent on any other feature.
Issue 27
May 2004
53-5
401-610-133A
The Customized ESN Format in AMA Record feature does not interact with any other features.
53-6
Issue 27
May 2004
Related Documentation
The AMA Dump for Selected Subscriber (ADSS) output report (REPT:CP IMMEDIATE BILLING) will indicate that the ESN is in the customized format. For more about this output report, see the AMA Dump for Selected Subscribers optional feature document, 401-601-029. See also the AMA Search optional feature document, 401-610-080, and the Customized ESN Format in AMA optional feature document, 401-612-583.
Issue 27
May 2004
53-7
401-610-133A
53-8
Issue 27
May 2004
54
54-1 54-1 54-2 54-2 54-2 54-2 54-3 54-3 54-4 54-4 54-4 54-4 54-4 54-4 54-4 54-5 54-6 54-6 54-6 54-6 54-6 54-6
Introduction
For Further Information Introduction What is the SMV on PHV Feature? Additional Storage Required Introduction Introduction Fields Module Code Field Event Type Field Event Description Field Relative Event Time Field Module Generation Criteria Introduction Fields Module Code Field Module Size Field Generic Context Identifier
Feature Description

AMA Impacts
Digital Event Module


Issue 27
May 2004
54-i
401-610-133A
Digits Recorded Field for SMV on PHV Table Module Generation Criteria for SMV on PHV
54-7 54-7 54-8 54-9 54-10
54-ii
Issue 27
May 2004
54
Introduction
This chapter describes the Selectable Mode Vocoder on PHV feature and describes how to interpret the AMA records produced by this feature.

Although the AMA work for the Selectable Mode Vocoder on PHV feature has been completed, deployment of the Selectable Mode Vocoder on PHV feature must wait until SMV vocoders are commercially available. Once SMV vocoders are commercially available, an optional feature document will be produced for this feature.
Issue 27
May 2004
54-1
401-610-133A
Feature Description
Introduction
This section describes Selectable Mode Vocoder on PHV feature.
What is the SMV on PHV Feature?

The Selectable Mode Vocoder on PHV feature enables the Mobile Switching Center (MSC) to provide Selectable Mode Vocoder service. The Selectable Mode Vocoder is a new Code Division Multiple Access (CDMA) third generation vocoder that gives more options for improving voice quality or improving radio frequency (RF) capacity.
Additional Storage Required

The Digit Information Module for SMV contains 10 bytes. The Digital Event Module for SMV contains 12 bytes. Based on an average AMA record size of 150 bytes, the SMV feature will cause a 15 percent increase in consumption of disk storage space for those records that contain SMV information.
54-2
Issue 27
May 2004
AMA Impacts
Introduction
Every record for a Selectable Mode Vocoder on PHV feature call appends two modules:
a Digital Event Module (storing a new Event Description created for this feature) a Digit Information Module (containing a new Generic Context Identifier created for this feature and to store the forward/reverse initial assigned SMV mode in the Digits Recorded Field)
These AMA impacts are described in the following sections.
Issue 27
May 2004
54-3
401-610-133A
Digital Event Module

Introduction
This section describes the fields in the Digital Event Module as used by the Selectable Mode Vocoder on PHV feature.
Fields
The Digital Event Module (Module 334) contains the following fields:

Module Code Event Type Event Description Relative Event Time
Module Code Field

The Module Code field identifies the type of module that is appended to the existing AMA record. For the Digital Event Module, this is 334.
Event Type Field

The Event Type field signifies mutually exclusive events. The event type used by the Selectable Mode Vocoder on PHV feature is 002, Initial CDMA Assigned Service Option.

Several different Event Description values are possible with the Initial CDMA Assigned Service Option event type (as shown in Table 4-46 on page 4-76). The Event Description created for the Selectable Mode Vocoder on PHV feature is 00056, SMV Voice.
Relative Event Time Field

The Relative Event Time is the elapsed time between the event and the beginning of the call. Note that for event type 002, the Relative Event Time field is filled with zeroes.
54-4
Issue 27
May 2004
For more information about the DEM fields and their associated AMASE Tables, see Module 334Digital Event Module on 5-34.

The Digital Event Module will be appended to AMA records with the x2329-x2335 structure codes if all of the following conditions are true:

The SMV on PHV feature is active in the Feature Activation File. The ECP database field for Append to the AMA Record: Digital Event Module is set to y. The inital assigned CDMA service option is 56.
Issue 27
May 2004
54-5
401-610-133A

Introduction
This section describes the fields in the Digit Information Module as used by the Selectable Mode Vocoder on PHV feature.
Fields
The Digit Information Module (Module 661) contains the following fields:

Module Code Module Size Generic Context Identifier Digits Recorded
Module Code Field

The Module Code field identifies the type of module that is appended to the existing AMA record. For the Digit Information Module, this is 621.
Module Size Field

The Module Size field specifies a number from one to three digits. In the Digit Information Module this number is used to specify the number of bytes (1 byte = 2 BCD characters) that make up the complete 621 module for the AMA record. This count includes all digits for the Module Code, the Module Size, the Generic Context Identifier, and the Digits Recorded fields.
Generic Context Identifier

The Selectable Mode Vocoder on PHV feature uses a new Generic Context ID of 90030 (Forward/Reverse Inital Assigned SMV Mode).
54-6
Issue 27
May 2004
Digits Recorded Field for SMV on PHV

The Digits Recorded field in the Digit Information Module is used by the SMV on PHV feature to store information describing the forward/reverse initial assigned SMV mode in the order shown in Table 54-1 on page 54-7. In the Digit Information Module numbers conveying vocoder type and mode are stored together in the Digits Recorded field in the order shown in Table 54-1 on page 54-7.
Table
Table 54-1 on page 54-7 shows the Digits Recorded field as used by the Selectable Mode Vocoder on PHV feature. Table 54-1. Digits Recorded Field as Used by the SMV on PHV Feature Meaning 0 (Padding) SMV mode used in call setup and received by the forward channel (one of the following): 0 = Premium 1 = Standard 2 = Economy 3 = Capacity-Saving 4 = Half Rate Max Mode 0 5 = Half Rate Max Mode 1 3 SMV mode used on call setup and received by the reverse channel (one of the following): 0 = Premium 1 = Standard 2 = Economy 3 = Capacity-Saving 4 = Half Rate Max Mode 0 5 = Half Rate Max Mode 1 4 5-50 SIGN (hex C) Unused
BCD Characters 1 2
Issue 27
May 2004
54-7
401-610-133A
Module Generation Criteria for SMV on PHV

The Digit Information Module storing the Selectable Mode Vocoder on PHV feature information will be appended to AMA records with the 2329 - 2335 structure code layouts if the following generation criteria are met:

The Selectable Mode Vocoder on PHV feature FAF is turned on. The Digit Information Module is activated via ecp RC/V entry Append DIM for SMV. The inital assigned CDMA service option is 56.
54-8
Issue 27
May 2004
These features have no feature dependencies.
Issue 27
May 2004
54-9
401-610-133A
None.
54-10
Issue 27
May 2004
55
55-1 55-1 55-2 55-2 55-3 55-3 55-3 55-3 55-3 55-3 55-5
Introduction
For Further Information What the Feature does New Service Feature Code Subscriber DN Home Mobile DN Incoming Called Digits for the Mobile-Terminated Call Module Generation Criteria for Limited Mobility Services with Multiple SDCAs/MDNs feature
Feature Description
AMA Impacts

Issue 27
May 2004
55-i
401-610-133A
55-ii
Issue 27
May 2004
55
Introduction
This chapter describes the Limited Mobility Services with Multiple SDCAs/MDNs (LMSMSM) feature and describes how to interpret the AMA records produced by this feature.

Refer to 401-612-664, Limited Mobility Services with Multiple SDCAs/MDNs optional feature description.
Issue 27
May 2004
55-1
401-610-133A
Feature Description
This section describes the Limited Mobility Services with Multiple SDCAs/MDNs feature.
What the Feature does

The LMSMSM feature provides roaming capability for the mobile subscriber by allowing service in different pre-selected Short Distance Charging Areas (SDCAs) with different numbers. For the Lucent Integrated Home Location Register Mobile Switching Center (IHLR MSC), the LMSMSM feature allows the service provider to pre-assign up to four different SDCAs with four different Mobile Directory Numbers (MDNs) to a mobile unit (including the home MDN). All the MDNs that are assigned to a subscriber are tied to one Mobile Identification Number (MIN). The mobiles primary MDN is the mobiles home MDN and it is associated with its home SDCA. If the mobile is in its pre-assigned SDCA, all mobile-originated and mobile-terminated calls are allowed. However, if the mobile is not in its pre-assigned SDCA, then mobile-originated and mobile-terminated calls are not allowed. When a subscriber who is in a call moves outside an SDCA boundary, the call is dropped and re-registration is done. Additionally, when a mobile moves from one pre-assigned SDCA to another pre-assigned SDCA, the new pre-assigned SDCA name is sent to the subscriber for display. When the mobile moves from a pre-assigned SDCA to an SDCA that is not pre-assigned, a blank is sent to the mobile as display.
55-2
Issue 27
May 2004
AMA Impacts
This section gives an overview of how the Limited Mobility Services with Multiple SDCAs/MDNs feature affects AMA.
New Service Feature Code

A new service feature code, 327 (Limited Mobility Services with Multiple SDCAs/ MDNs) is added to the AMASE Table 2002 on page 4-119 for the Limited Mobility Services with Multiple SDCAs/MDNs feature.
Subscriber DN
If the mobile is in its pre-assigned SDCA, then the pre-assigned MDN for the SDCA (also called the active MDN) is used as the subscriber DN in the AMA record for both mobile-originated and mobile-terminated calls. For Immediate Call Forwarding and Call Forwarding No Page Response calls, the active MDN is not available. The Home MDN is used as the subscriber MDN on the AMA record.
Home Mobile DN
The Home Mobile DN can be mapped by the MIN which is stored in the Digit Information Module with Generic Context Identifier 10830.
Incoming Called Digits for the Mobile-Terminated Call

If the mobile is in its pre-assigned SDCA, then the incoming called digits for a mobile-terminated call is stored in the Digit Information Module with Generic Context Identifier 90010.
Module Generation Criteria for Limited Mobility Services with Multiple SDCAs/MDNs feature
The incoming called digits are stored in the DIgit Information Module with Generic Context identifier 90010 with the following structure code layouts: x2331, x2334 and x2335 for mobile terminated calls or x2329, x2330, x2332 and x2333 with service feature fields set to special cellular network, Call Forwarding Busy, Immediate Call Forwarding, Call Forwarding No Page Response, Call Forwarding No Answer, if the following module generation criteria are met:
Issue 27
May 2004
55-3
401-610-133A
The Limited Mobility Service with Multiple SDCAs/MDNs FAF is on. The Append to the AMA record: Incoming Called Digits Module field in the ecp form is set to y.
55-4
Issue 27
May 2004
The Limited Mobility Services with Multiple SDCAs/MDNs FAF can be activated only if the following FAFs/QFAFs are activated:

CDMA Private Network and User Zone (both FAF and QFAF) Enhanced CDMA Private Network and User Zone
Issue 27
May 2004
55-5
401-610-133A
55-6
Issue 27
May 2004
56
56-1 56-1 56-2 56-2 56-2 56-3 56-3 56-3 56-3 56-4 56-5
Introduction
For Further Information What the Feature does How the Feature Works New Generic Context ID Digits Recorded field for Generic Context ID 90062 Use of Structure Codes Module Generation Criteria for Maintain Selected AMA Measurement Data Reporting Feature
Feature Description

AMA Impacts

Issue 27
May 2004
56-i
401-610-133A
56-ii
Issue 27
May 2004
56
Introduction
This chapter describes the Maintain Selected AMA Measurements Data Reporting feature and describes how to interpret the AMA records produced by this feature.

Refer to 401-612-679, Maintain Selected AMA Measurements Data Reporting Optional Feature Description.
Issue 27
May 2004
56-1
401-610-133A
Feature Description
This section describes the Maintain Selected AMA Measurements Data Reporting feature.
What the Feature does

The Maintain Selected AMA Measurements Data Reporting feature will provide selected information of the measurement data to the billing system through a new DIM module with a new Generic Context Identifier, 90062.
How the Feature Works

The Maintain Selected AMA Measurements Data Reporting feature collects the following measurement data in AMA call records:

Assigned Radio Frequency Carrier Assigned CDMA Technology Version Service Option Allocated Call Final Class Call Final Class Qualifier
56-2
Issue 27
May 2004
AMA Impacts
This section gives an overview of how the Maintain Selected AMA Measurements Data Reporting feature affects AMA. The Maintain Selected AMA Measurements Data Reporting feature adds a new Generic Context Identifier, 90062, called Maintain Selected AMA Measurements Data Reporting in the Digit Information Module (DIM) 621 to record measurement data.
New Generic Context ID

The following Generic Context Identifier is added for the Maintain Selected AMA Measurements Data Reporting feature:
90062
Digits Recorded field for Generic Context ID 90062

The Digits Recorded field for Generic Context ID 90062 contains all the measurement data as shown in Table 56-1 "Digits Recorded field for Generic Context ID 90062" on page 56-3. Table 56-1. Digits Recorded field for Generic Context ID 90062 AMASE table Number of BCD characters
Field name Assigned RF Carrier
961
2 (without padding and sign) (where the maximum value must not exceed 18) 1 (without sign) 5 (without sign) 2 (without padding and sign) 4 (with sign)
Assigned CDMA Technology Version
963 497 964 965
Service Option Allocated Call Final Class Call Final Class Qualifiers Use of Structure Codes
The following structure codes are used for the feature:

x2118 x2119 x2329
Issue 27
May 2004
56-3
401-610-133A
x2330 x2331 x2332 x2333 x2334 x2336 x2411 x2415
Module Generation Criteria for Maintain Selected AMA Measurement Data Reporting Feature
The Digit Information module that stores the Maintain Selected AMA Measurement Data Reporting information is appended to the AMA records with the following structure code layouts: x2118, x2119, x2329, x2330, x2331, x2332, x2333, x2334, x2336, x2411 and x2415, if the following module generation criteria are met:
The Maintain Selected AMA Measurement Data Reporting FAF is on. The Append to the AMA record: Selected AMA Measurement Data to AMA Reporting field in the RC/V ecp form is set to y.
56-4
Issue 27
May 2004
The Maintain Selected AMA Measurements Data Reporting feature does not interact with any other feature.
Issue 27
May 2004
56-5
401-610-133A
56-6
Issue 27
May 2004
57
57-1 57-1 57-2 57-2 57-2 57-3 57-3 57-3 57-3 57-4 57-6 57-6 57-6
Introduction
For Further Information Introduction Feature Description Introduction Use of Existing Digit Information Module with a New Generic Context ID Module Generation Criteria Table Home Zone Service Phase 2 KTF Intelligent Network Service (KTFINS)
Feature Description

AMA Impact

Feature Interaction

Issue 27
May 2004
57-i
401-610-133A
57-ii
Issue 27
May 2004
57
Introduction
This chapter describes the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature and describes how to interpret the AMA records produced by this feature.

Refer to 401-612-646 Issue 2 and later, Home Zone Service for TIA-41 Optional Feature Description.
Issue 27
May 2004
57-1
401-610-133A
Feature Description
Introduction
This section describes the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature.
Feature Description
The AMA Enhancement of Home Zone Service Phase II feature enhances the following existing features to correctly bill subscribers:

Home Zone Service Phase 2 KTF Intelligent Network Services including KTF WIN, KTF VPN and trigger features
The AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature appends DIM 621 with the Generic Context Identifier 90064 to AMA records when the affected features are used. This features DIM overrides the functionality of using the Service Feature Codes 323 (Home Zone Service Discount Rate) and 324 (Home Zone Service Normal Rate) that are associated with the Home Zone Service Phase 2 feature. In other words, if the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature is active and the KTF Intelligent Network Service Phase 2 field on the ecp form is on, the Home Zone Service Discount/ Normal Rate that is stored in the DIM with the Generic Context Identifier 90064 takes precedence over the service feature field.
57-2
Issue 27
May 2004
AMA Enhancements of Home Zone Service Phase II
AMA Impact
Introduction
This section describes changes to AMA that are caused by the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature.
Use of Existing Digit Information Module with a New Generic Context ID

This feature uses the existing Digit Information Module 621 (DIM) with a new Generic Context ID 90064 for structure codes x2329, x2330, x2332 and x2333.

The Digit Information Module with Generic Context Identifier 90064 that stores the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service information is appended to the AMA records with the following structure code layouts: x2329, x2330, x2332 and x2333, if the following generation criteria are met:
The Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service (EHZP2KTFINS) FAF is on. The KTF Intelligent Network and Home Zone Service 2 Module field in the ecp form is set to y. If any of the following features are used: Home Zone Service Phase 2 KTF Intelligent Network Service including WIN, VPN and trigger features.
Issue 27
May 2004
57-3
401-610-133A
Table
Table 57-1 on page 57-4 shows the first 3 BCD characters of the Digits Recorded field as used by the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature to store the Home Zone Service Phase 2 and KTF Intelligent Network Services feature information. Table 57-1. AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service Feature Meaning (KTF Service) Normal Rate for Home Zone Service II Discount Rate for Home Zone Service II KTF WIN KTF VPN KTF all trigger features with routing prefix 0940 & 0950 KTF all trigger features with routing prefix 097x KTF all trigger features with routing prefix 098 KTF all trigger features with routing prefix 09410947 & 0956 BGMS with routing prefix 099800 SCS with routing prefix 099801 HZS2 Normal Rate and BGMS with Routing Prefix 099800 (The HZS2 BGMS and SCS Billing Enhancement FAF must be on.) HZS2 Discount Rate and BGMS with Routing prefix 099800 (The HZS2 BGMS and SCS Billing Enhancement FAF must be on.) HZS2 Normal Rate and SCS with Routing Prefix 099801 (The HZS2 BGMS and SCS Billing Enhancement FAF must be on.) HZS2 Discount Rate and SCS with Routing Prefix 099801 (The HZS2 BGMS and SCS Billing Enhancement FAF must be on.) BCD Character 4 SIGN (Hex C) BGMS=Background Music Service
BCD Characters (1-3) 000 001 002 003 006 007 008 009 010 011 012
013
014
015
57-4
Issue 27
May 2004
AMA Enhancements of Home Zone Service Phase II
SCS=Sound Call Service
Issue 27
May 2004
57-5
401-610-133A
Feature Interaction
The AMA Enhancements of Home Zone Service Phase II and KTF intelligent Network Service feature interacts withe the following features;

Home Zone Service Phase 2 (HZS2) KTF Intelligent Network Services (KTFINS)
Home Zone Service Phase 2

If the Home Zone Service Phase 2 (HOMEZONEPH2) and the Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service (EHZP2KTFINS) FAFs are on and the KTF and Home Zone 2 Services Module field in the ecp form is set to y, then the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature appends DIM 621 with the Generic Context Identifier 90064 to AMA records. This features DIM overrides the functionality of the service feature codes that are used by the Home Zone Service Phase 2 feature.
KTF Intelligent Network Service (KTFINS)

If the KTF Intelligent Network Services (KTFINS) and the Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service (EHZP2KTFINS) FAFs are on and the KTF and Home Zone 2 Services Module field in the ecp form is set to y, then the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature appends DIM 621 with the Generic Context Identifier 90064 to AMA records.
57-6
Issue 27
May 2004
Call Scenarios
Introduction
This appendix describes a non-exhaustive set of Flexent/AUTOPLEX wireless network call scenarios including simple mobile originations and terminations to specific feature-related call scenarios. Other call scenarios can be derived from the call scenarios listed here.
Location of DCSs
In the scenarios where multiple Digital Cellular Switches (DCSs) are used, unless otherwise noted, DCSs may be located on the same Mobile Switching Center (MSC), or may be located on different MSCs.
Ratio of AMA Records to DCSs

One or more Automatic Message Accounting (AMA) records are generated per DCS.
Timing Tables
Some call scenarios contain timing tables. These tables illustrate the timing dependencies and associated AMA records of the scenario.
Issue 27
May 2004
A-1
401-610-133A
Call Scenarios and Structure Codes

The basic structure codes for AMA records are listed in Table A-1 on page A-3. The structure codes are referenced in the scenarios described in the following section. There are many variations of the basic call types. Use of features, use of interMSC or intra-MSC networking, use of voice mail resources, and so forth, all affect the type of the call. The structure code provides a key indication to the basic call type.
Structure Code Starting with 4

This AMA option allows modules to be appended to standard AMA records. Use of this option is indicated by a structure code starting with 4.
A-2
Issue 27
May 2004
Call Scenarios
Table A-1. Structure Code (AMA Record) x2118 x2119 x2329 x2330 x2331 x2332 x2333 x2334 x2335 x2336 x2337 x2338 x2411 x2415 x2421
AMA Call Related Scenario Mapping Meaning Type of Call (Record)
Tandem Call with Carrier Interconnect (CI) Information Tandem Call without CI Information Cellular-Originated Call without CI Information Cellular-Originated Call with CI Information Cellular-Terminated Call Control Point Switch (CPS) Cellular-Originated Call with CI Information CPS Cellular-Originated Call without CI Information CPS Cellular-Terminated Call - Facility and AirTime Record CPS Cellular-Terminated Call - Interswitch Call Termination (ICT) Facility TIming Record Cellular Networking (CN) Slave Switch Facility and Air-Time Record CN Handback - Answered Segment Air-Time Record CN Handback - Intermediate Segment AirTime Record Feature Activation/Deactivation Mobile Security Entry Virtual System AMA Event Recording
Tandem Tandem Mobile Origination Mobile Origination Mobile Termination Mobile Origination/Handoff Mobile Origination/Handoff Mobile Termination/ Handoff Mobile Termination Mobile Termination/ Handoff Handback Handback Feature-Related Event and/or Activity Mobile Security Activity Handoff Activity
Issue 27
May 2004
A-3
401-610-133A
AMA Record Generation

The table below summarizes the AMA records generated for each call scenario. The last record listed for each scenario contains the total time for the call, except where noted. Table A-2. Scenario Mobile Origination Mobile Origination (not Home DCS) Mobile Origination with Internal DCS Handoff Mobile Origination with Handoff Mobile Origination with Handoff and Handback Mobile Termination Mobile Termination (not Home DCS) Mobile Termination (No Page response) Mobile Termination (Failed) Call Scenario Summary (Page 1 of 4) AMA Record Description Origination: x2329/x2330 Origination: x2329/x2330 see Mobile Origination Handoff: x2336 Origination: x2332/x2333 Termination: x2336 Handback: x2337 Origination: x2332/x2333 Termination: x2331 Redirection (Handoff): x2336 Termination (Redirection): x2335 not supported Termination: x2331
Page No. A-15 A-16 A-17 A-18 A-20
A-23 A-24 A-26 A-27
Radio Communication Failure!= No failure A-28 A-29 A-30 A-32 A-34 Call Answer Status!= Answer
Mobile Termination (Unanswered) Mobile Termination Overflow Mobile Termination with Handoff Mobile Termination with Handback Mobile Termination with Handoff and Handback
Termination: x2331
Redirection: x2118/x2119 Termination: x2331 Handoff: x2336 Termination: x2334 Handoff: x2336 Termination: x2334 Handoff: x2336 Handback: x2337 Termination: x2334
A-4
Issue 27
May 2004
Call Scenarios
Table A-2. Scenario
Call Scenario Summary (Page 2 of 4) AMA Record Description Handoff: x2336 Handback: x2338 Termination: x2334 Origination: x2329/x2330, and separately Termination: x2331 Origination: x2329/x2330, and separately Redirection: x2118/x2119 Termination: x2331 Redirection (Handoff): x2336 Termination (Redirection): x2335 Redirection: x2329/x2330 Service Feature = Special Cellular Networking Termination: x2331
Page No. A-37
Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2 Mobile to Mobile
A-40
Mobile to Mobile with Tandem
A-41
Call Delivery (via Internal Trunks) Call Delivery (via ANSI-41)
A-42 A-43
Service Feature = Special Cellular Networking A-44
Call Delivery (Internal) with Handoff
Handoff: x2336 Redirection (Handoff): x2336 Termination (Redirection): x2335 Handoff: x2336 Termination: x2334
Call Delivery (via ANSI-41) with Handoff
A-45
Service Feature = Special Cellular Networking Service Feature = Special Cellular Networking A-47
Redirection: x2329/x2330
Call Delivery to Call Waiting
Origination: x2329/x2330, and separately Redirection: x2329
Service Feature = Call Delivery to Call Waiting Service Feature = Call Waiting
Termination: x2331
Issue 27
May 2004
A-5
401-610-133A
Table A-2. Scenario
Call Scenario Summary (Page 3 of 4) AMA Record Description Redirection: x2329/x2330 Service Feature = Call Forwarding (one of several) Origination: x2329/x2330 Redirection: x2329/x2330
Page No. A-49
Call Forwarding to Mobile
Call Waiting (No Answer Forward to PSTN)
A-51
Service Feature = Call Waiting + Call Forward Dont Answer A-54
Call Waiting (No Answer Transfer to Voice Mail)
Origination: x2329/x2330 Termination: x2331

Service Feature = Call Waiting MRS Indicator = Recording A-56
Mobile Termination with Call Waiting
Termination 1: x2331 Termination 2: x2331
Service Feature = Call Waiting A-58
Mobile Origination with Call Waiting
Origination: x2329/x2330, and separately Termination: x2331
Service Feature = Call Waiting A-60
Mobile Origination with Three-Way Calling
Origination 1: x2329/x2330 Origination 2: x2329/x2330
Service Feature = Three-Way Calling A-61
Three-Way Calling with Handoff
Origination 1: x2332/x2333 Handoff: x2336 Origination 2: x2329/x2330
Service Feature = Three-Way Calling A-68
Voice-Mail Retrieval via Mobile (Revertive) Voice-Mail Retrieval via Mobile (*Feature Code) Voice-Mail Retrieval via PSTN
Origination: x2329/x2330 Termination: x2331
MRS Indicator = Recording A-69 A-70 MRS Indicator = Retrieval MRS Indicator = Recording
Origination: x2329/x2330
Termination: x2331
A-6
Issue 27
May 2004
Call Scenarios
Table A-2. Scenario
Call Scenario Summary (Page 4 of 4) AMA Record Description Event: x2411
Page No. A-71
Feature Activation/Deactivation
Service Feature = Call Forwarding, ADWA, Voice Mail, or Special Routing A-73 Special Routing Feature Indicator = ICOS, Special Routing Feature Indicator = ICOS A-74 A-75 A-76 A-77 A-79
Wiretap/Court-Ordered Surveillance
Termination: x2331
or Origination: x2329/x2330
Mobile Security Entry Virtual Switch Handoff Callback Mobile Termination (not Home DCS) with Call Forwarding Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail Test Calls Tracer Records
Event: x2415 Event: x2421 Same as held party that initiated the callback. Origination: x2332 /x2333 Handoff: x2336 Termination: x2334 Handoff: x2336
Service Feature = Mobile Station Test
A-81 A-82
Event: 01047, 09042, 09043
Issue 27
May 2004
A-7
401-610-133A
Call Scenario Use of AMA Records

This section is provided to verify that all Flexent/AUTOPLEX wireless network AMA records have been discussed in the scenarios listed in Table A-3 on page A-8. The table below lists the AMA records described in those scenarios. Table A-3. Record 01047 x2118 x2119 x2329 AMA Record Completeness Summary (Page 1 of 4) Meaning Call Assembly Tracer Tandem with CI Tandem without CI Cellular-Originated without CI Scenario Tracer Records Mobile Termination Overflow Mobile to Mobile with Tandem Mobile Termination Overflow Mobile to Mobile with Tandem Mobile Origination Mobile Origination (not Home DCS) Mobile to Mobile Mobile to Mobile with Tandem Call Delivery (via ANSI-41) Call Delivery (via ANSI-41) with Handoff Call Delivery to Call Waiting Call Forwarding to Mobile Mobile Origination with Call Waiting Call Waiting (No Answer Forward to PSTN) Call Waiting (No Answer Transfer to Voice Mail) Mobile Origination with Three-Way Calling Three-Way Calling with Handoff Voice-Mail Retrieval via Mobile (Revertive) Voice-Mail Retrieval via Mobile (*Feature Code) Wiretap/Court-Ordered Surveillance
A-8
Issue 27
May 2004
Call Scenarios
Table A-3. Record x2330
AMA Record Completeness Summary (Page 2 of 4) Meaning Cellular-Originated with CI Scenario Mobile Origination Mobile Origination (not Home DCS) Mobile to Mobile Mobile to Mobile with Tandem Call Delivery (via ANSI-41) Call Delivery (via ANSI-41) with Handoff Call Delivery to Call Waiting Call Forwarding to Mobile Mobile Origination with Call Waiting Call Waiting (No Answer Forward to PSTN) Call Waiting (No Answer Transfer to Voice Mail) Mobile Origination with Three-Way Calling Three-Way Calling with Handoff Voice-Mail Retrieval via Mobile (Revertive) Wiretap/Court-Ordered Surveillance Mobile Termination Mobile Termination (Failed) Mobile Termination (Unanswered) Mobile to Mobile Mobile Termination Overflow Mobile to Mobile with Tandem Call Delivery (via ANSI-41) Call Delivery to Call Waiting Mobile Origination with Call Waiting Call Waiting (No Answer Transfer to Voice Mail) Mobile Termination with Call Waiting Voice-Mail Retrieval via Mobile (Revertive) Voice-Mail Retrieval via PSTN Wiretap/Court-Ordered Surveillance
x2331
Cellular-Terminated
x2332
CPS Cellular-Originated with CI
Mobile Origination with Handoff Mobile Origination with Handoff and Handback Three-Way Calling with Handoff Mobile Termination (not Home DCS) with Call Forwarding Mobile Origination with Handoff Mobile Origination with Handoff and Handback Three-Way Calling with Handoff Mobile Termination (not Home DCS) with Call Forwarding
x2333
CPS Cellular-Originated without CI
Issue 27
May 2004
A-9
401-610-133A
Table A-3. Record x2334
AMA Record Completeness Summary (Page 3 of 4) Meaning CPS Cellular-Terminated - Facility and Air-Time Scenario Mobile Termination with Handoff Mobile Termination with Handback Mobile Termination with Handoff and Handback Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2 Call Delivery (via ANSI-41) with Handoff Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail Mobile Termination (not Home DCS) Call Delivery (via Internal Trunks) Call Delivery (Internal) with Handoff Mobile Termination (not Home DCS) Mobile Termination with Handoff Mobile Termination with Handback Mobile Termination with Handoff and Handback Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2 Mobile Origination with Handoff Mobile Origination with Handoff and Handback Call Delivery (via Internal Trunks) Call Delivery (Internal) with Handoff Call Delivery (via ANSI-41) with Handoff Three-Way Calling with Handoff Mobile Termination (not Home DCS) with Call Forwarding Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail Mobile Termination with Handoff and Handback Mobile Origination with Handoff and Handback Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2 Feature Activation/Deactivation Mobile Security Entry Virtual Switch Handoff none (but included in tracer record counts)
x2335
CPS Cellular-Terminated - ICT Facility Timing CN Slave Switch - Facility and Air-Time
x2336
x2337
CN Handback Answered Segment AirTime CN Handback Intermediate Segment Air-Time CF Act/Deact Mobile Security Entry AMA Event Record TIme Change Statistical Label
x2338
x2411 x2415 x2421 09000
A-10
Issue 27
May 2004
Call Scenarios
Table A-3. Record 09036 09037 09038 09039 09042 09043 +40000
AMA Record Completeness Summary (Page 4 of 4) Meaning Beginning of Recording End of Recording Collector Logical Data Set (CLDS) Header CLDS Trailer Primary Tracer Secondary Tracer Modules Scenario n/a n/a na n/a Tracer Records Tracer Records any
Issue 27
May 2004
A-11
401-610-133A
Call Scenario Composition

This section describes the composition of Flexent/AUTOPLEX wireless network call scenarios. This is a component set; a non-exhaustive list of scenarios and scenario components. Other scenarios can be derived from these. The following table summarizes the scenarios. Table A-4. Scenario Mobile Origination Mobile Origination (not Home DCS) Mobile Origination with Internal DCS Handoff Mobile Origination with Handoff Mobile Origination with Handoff and Handback Mobile Termination Mobile Termination (not Home DCS) Mobile Termination (No Page Response) Mobile Termination (Failed) Mobile Termination (Unanswered) Mobile Termination Overflow Mobile Termination with Handoff Mobile Termination with Handback Mobile Termination with Handoff and Handback Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2 Mobile to Mobile Mobile to Mobile with Tandem Call Delivery (via Internal Trunks) Scenario Composition (Page 1 of 3) Composition Mobile Origination Mobile Origination Mobile Termination + Intra-DCS Handoff Mobile Origination + Handoff Mobile Origination + Handoff + Handback Mobile Termination Mobile Termination + Redirection Mobile Termination + No Page Response Mobile Termination + Call Failure Mobile Termination + No Answer Mobile Termination + Redirection Mobile Termination + Handoff Mobile Termination + Handback Mobile Termination + Handoff + Handback Mobile Termination + Handoff + Handoff + Handback Mobile Origination + Mobile Termination Mobile Termination + Mobile Origination + Redirection Mobile Termination + Redirection Page No. A-15 A-16 A-17 A-18 A-20 A-23 A-24 A-26 A-27 A-28 A-29 A-30 A-32 A-34 A-37 A-40 A-41 A-42
A-12
Issue 27
May 2004
Call Scenarios
Table A-4. Scenario
Scenario Composition (Page 2 of 3) Composition Mobile Origination + Mobile Termination Mobile Termination + Redirection + Handoff Mobile Termination + Redirection + Handoff Mobile Origination + Call Waiting Mobile Origination + Mobile Termination Mobile Termination + Call Waiting + Call Forwarding Mobile Termination + Call Waiting + Transfer to Voice Mail Mobile Termination + Call Waiting Mobile Origination + Call Waiting Mobile Origination + Three Way Mobile Origination + Three Way + Handoff Mobile Origination + Mobile Termination Mobile Origination PSTN Termination Feature Activation/Deactivation Mobile Termination/Mobile Origination Security/Fraud Event Handoff same as original call scenario Mobile Termination + Call Forwarding Page No. A-43 A-44 A-45 A-47 A-49 A-51 A-54 A-56 A-58 A-60 A-61 A-68 A-69 A-70 A-71 A-73 A-74 A-75 A-76 A-77
Call Delivery (via ANSI-41) Call Delivery (Internal) with Handoff Call Delivery (via ANSI-41) with Handoff Call Delivery to Call Waiting Call Forwarding to Mobile Call Waiting (No Answer Forward to PSTN) Call Waiting (No Answer Transfer to Voice Mail) Mobile Termination with Call Waiting Mobile Origination with Call Waiting Mobile Origination with Three-Way Calling Three-Way Calling with Handoff Voice-Mail Retrieval via Mobile (Revertive) Voice-Mail Retrieval via Mobile (*Feature Code) Voice-Mail Retrieval via PSTN Feature Activation/Deactivation Wiretap/Court-Ordered Surveillance Mobile Security Entry Virtual Switch Handoff Callback Mobile Termination (not Home DCS) with Call Forwarding
Issue 27
May 2004
A-13
401-610-133A
Table A-4. Scenario
Scenario Composition (Page 3 of 3) Composition Mobile Termination + Transfer to Voice Mail same as original call scenario not applicable Page No. A-79
Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail Test Calls Tracer Records
A-81 A-82
A-14
Issue 27
May 2004
Call Scenarios
Mobile Origination
How It Starts
In this scenario, the mobile subscriber originates a call to a Public Switched Telephone Network (PSTN) number. The call is activated.
What Happens
The ECP generates an x2329 or an x2330 AMA record for the DCS on call end. An x2330 AMA record is used when an Interexchange Carrier (IEC) is specified. Otherwise an x2329 AMA record is used.
Figure
Figure A-1 on page A-15 shows the scenario.
PSTN AMA or x2330 x2329 DCS AMA
Figure A-1.
Mobile Origination
Issue 27
May 2004
A-15
401-610-133A
Mobile Origination (not Home DCS)

How It Starts
In this scenario, the mobile subscriber, served by a DCS other than his home DCS, originates a call to a PSTN number.
What Happens
The call is routed directly to the PSTN. The call is completed. The Executive Cellular Processor (ECP) generates an x2329 or an x2330 AMA record for the serving DCS on call end, like in AMA Record Generation on page A-4.
Figure
PSTN AMA or x2330 x2329 AMA
DCS
serving CPS
Figure A-2.
Mobile Origination (not Home DCS)
A-16
Issue 27
May 2004
Call Scenarios
Mobile Origination with Internal DCS Handoff

How It Starts
A mobile subscriber originates a call and is handed off to a cell served by the same DCS.
What Happens
No AMA structure code changes are made for internal handoffs. The Number of Handoffs AMA field contains the count of intra-DCS handoffs. This intra-DCS handoff treatment applies to mobile terminations as well as mobile originations. No special AMA records are emitted for the intra-DCS handoff. Normal mobile origination or mobile termination AMA records are emitted; a summary of the intra-DCS handoffs is contained in the AMA record. Any call scenarios containing mobile air-time may have intra-DCS handoffs.
Figure
PSTN
DCS
CS
handoff
CS
Figure A-3.
Mobile Origination with Internal DCS Handoff
Issue 27
May 2004
A-17
401-610-133A
Mobile Origination with Handoff

How It Starts
A mobile subscriber originates a call and is handed off to a cell served by another DCS.
What Happens
The ECP generates an x2336 AMA record for the serving DCS when the call ends. The ECP generates an x2332 or x2333 AMA record for the Control Point Switch (CPS) when the call ends. The x2332 AMA record is generated if an IEC is specified. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields. The x2332 and x2333 AMA records contain the total call time.
Figures
PSTN handoff CPS DCS ITG DCS serving
AMA or x2333 x2332
AMA
AMA x2336
Figure A-4.
Mobile Origination with Handoff
A-18
Issue 27
May 2004
Call Scenarios
The relationship between the various call segments involved in this call is shown in Figure A-5 on page A-19.
DCS A call placed (MO) AirSeg 1
DCS B
call handed off
call handoff received AirSeg 2
call ends
call ends x2336
x2332/x2333
Figure A-5.
Call Segment Relationships for Mobile Origination with Handoff
Issue 27
May 2004
A-19
401-610-133A
Mobile Origination with Handoff and Handback

How It Starts
A mobile subscriber originates a call on a DCS and is handed off to another DCS. The subscriber is handed back to his original DCS, as shown in Figure A-6 on page A-21.
What Happens
The ECP generates an x2336 AMA record (see number 2 in Figure A-6 on page A-21) for the serving DCS when it hands back the call to the CPS. The ECP generates an x2337 AMA record (see number 1 in Figure A-6 on page A-21) for the CPS when the mobile is handed back. The ECP generates an x2332 or x2333 AMA record (see number 3 in Figure A-6 on page A-21) for the CPS DCS when the call ends. The x2332 AMA record is generated when carrier interconnect is used. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields. The x2332/x2333 AMA records contain the total call time.
A-20
Issue 27
May 2004
Call Scenarios
Figures
PSTN handoff CPS DCS1

1 3
ITG handback
DCS2 serving
2
AMA
1
AMA
2
x2337 AMA
x2336
AMA
3
x2332 or x2333
Figure A-6.
Mobile Origination with Handoff and Handback
Issue 27
May 2004
A-21
401-610-133A
DCS 1 call placed (MO) AirSeg 1
DCS 2
call handed off
call handed back AirSeg 3 x2337
handback call x2336
call ends x2332/x2333
Figure A-7.
Call Segment Relationships for Mobile Origination with Handoff and Handback
A-22
Issue 27
May 2004
Call Scenarios
Mobile Termination
How It Starts
In this scenario, the mobile subscriber is the recipient of a call from a PSTN number. The call is completed.
What Happens
The ECP generates an x2331 AMA record for the DCS on call end. This is a single AMA record. The mobile termination scenario is not changed by handoffs between cell sites on the same DCS. If the Service Feature (SF) = 000 (No Service Feature), then the x2331 AMA record is the only record for the call from an AMA point of view. If the SF = 056 (Call Waiting) or 100 (Special Cellular Networking) then there are other records.
Figure
PSTN AMA x2331 DCS
Figure A-8.
Mobile Termination
Issue 27
May 2004
A-23
401-610-133A
Mobile Termination (not Home DCS)

How It Starts
In this scenario, the mobile subscriber is the recipient of a call from a PSTN number. The mobile is being served by a cell served by a DCS other than his home DCS. The call is completed. This scenario is also known as an inter-switch call termination.
What Happens
The ECP generates an x2336 AMA record for DCS 2 on call end. The ECP generates an x2335 AMA record for the CPS (DCS 1) on call end. AMA records are linked by the Transaction Code I and Transaction Code II AMA fields. The x2335 AMA record contains the total call time.
Figures
PSTN
CPS DCS 1
ITG
DCS 2
AMA x2335
AMA x2336
Figure A-9.
Mobile Termination (not Home DCS)
A-24
Issue 27
May 2004
Call Scenarios
DCS 1 a call arrives for the mobile and is redirected
DCS 2 the mobile answers AirSeg 2
the call ends x2335
the call ends x2336
Figure A-10.
Call Segment Relationships for Mobile Termination (not Home DCS)
Issue 27
May 2004
A-25
401-610-133A
Mobile Termination (No Page Response)

How It Starts
In this scenario, a call is attempted to a mobile from a PSTN number. There is no page response from the mobile.
What Happens
No AMA record is generated since no air resources were allocated. Trunk resources may have been allocated.
Figure
PSTN AMA none DCS
Figure A-11.
Incomplete Mobile Termination (No Page Response)
A-26
Issue 27
May 2004
Call Scenarios
Mobile Termination (Failed)

How It Starts
In this scenario, a call is attempted to a mobile from a PSTN number. Paging is successful but there is a radio communication failure after successfully seizing a voice channel.
What Happens
An x2331 record is generated and handled similarly to Mobile Termination on page A-23. Call failure can happen to mobile originations as well.
Figure
PSTN AMA x2331 DCS Radio Comm Failure!= No failure
Figure A-12.
Mobile Termination (Failed)
Issue 27
May 2004
A-27
401-610-133A
Mobile Termination (Unanswered)

How It Starts
In this scenario, a call is attempted to a mobile from a PSTN number. Paging is successful but the call is not answered by the mobile.
What Happens
An x2331 record is generated and handled similarly to Mobile Termination on page A-23. Unanswered calls can occur to mobile originations as well.
Figure
PSTN AMA x2331 DCS Call Answer Status = Unanswered
Figure A-13.
Mobile Termination (Unanswered)
A-28
Issue 27
May 2004
Call Scenarios
Mobile Termination Overflow

How It Starts
In this scenario, a call is directed at the mobile. The mobiles DCS has no available PSTN trunks. The call is routed over an available trunk to another DCS and then over internal trunks to the mobiles home DCS.
What Happens
The ECP emits an x2118 or x2119 AMA record for the overflow DCS. The call termination is handled normally. These AMA records are not linked. This scenario is not supported over ANSI-41.
Figure
PSTN No available trunks Overflow DCS DCS ITG DCS CPS
AMA or x2119 x2118
AMA
AMA x2331
Figure A-14.
Mobile Termination Overflow
Issue 27
May 2004
A-29
401-610-133A
Mobile Termination with Handoff

How It Starts
In this scenario, the mobile receives a call through its CPS DCS. The mobile subscriber is eventually handed off to a different DCS.
What Happens
The ECP emits an x2336 AMA record for the serving DCS (the one that received the handoff) when the call ends. The ECP emits an x2334 AMA record for the CPS DCS when the call ends. These AMA records are linked by Transaction Code I and Transaction Code II AMA fields. The x2334 AMA record contains the total call time.
Figures
PSTN
CPS
DCS
ITG handoff
DCS
AMA x2334
AMA x2336
Figure A-15.
Mobile Termination with Handoff
A-30
Issue 27
May 2004
Call Scenarios
DCS A call placed (MT) AirSeg 1
DCS B
call handed off
call ends x2334
call ends x2336
Figure A-16.
Call Segment Relationships for Mobile Termination with Handoff
Issue 27
May 2004
A-31
401-610-133A
Mobile Termination with Handback

How It Starts
In this scenario, the mobile receives a call. This call is delivered to the mobiles currently serving DCS. The mobile subscriber is eventually handed back to his CPS.
What Happens
The ECP emits an x2336 AMA record (see number 1 in Figure A-17 on page A-33) for the serving DCS when the call is handed back to the CPS DCS. Since there was no prior air-time on the CPS, no handback record is written (no x2337 or x2338 AMA record is generated.) When the call ends, the ECP emits a x2334 record (see number 2 in Figure A-17 on page A-33) for the CPS DCS. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields. The x2334 AMA record contains the total call time.
Figures
A-32
Issue 27
May 2004
Call Scenarios
PSTN internal call delivery CPS DCS

2
ITG handback
1
DCS
AMA x2334
AMA x2336
Figure A-17.
Mobile Termination with Handback
DCS A call placed (MT)
DCS B mobile termination received AirSeg 1
call handed back AirSeg 2
handback call x2336
call ends
x2334
Figure A-18.
Call Segment Relationships for Mobile Termination with Handback
Issue 27
May 2004
A-33
401-610-133A
Mobile Termination with Handoff and Handback

How It Starts
In this scenario, the mobile receives a call. This call is eventually handed off to a serving DCS and then handed back to his CPS DCS.
What Happens
The ECP emits an x2336 AMA record (see number 2 in Figure A-19 on page A-35) for the DCS receiving the handoff (Serving DCS) at the time of handback. At handback time the ECP emits an x2337 AMA record (see number 1 in Figure A-19 on page A-35). This record contains the air-time prior to the last handoff for the CPS DCS. When the call ends, the ECP emits an x2334 record (see number 3 in Figure A-19 on page A-35) for the CPS DCS. The x2334 record contains the total call time. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields.
Figures
A-34
Issue 27
May 2004
Call Scenarios
PSTN handoff CPS DCS

1 3
ITG handback
2
DCS
Serving DCS
AMA
1
AMA
2
x2337 AMA
x2336
x2334
Figure A-19.
Mobile Termination with Handoff and Handback
The relationship between the various call segments involved in this call is shown in Figure A-20 on page A-36. The tandem duration is not available in either the x2337 or x2334 AMA record.
Issue 27
May 2004
A-35
401-610-133A
CPS call placed (MT) AirSeg 1
Serving DCS
call handed off
call handed back AirSeg 3 x2337
handback call x2336
call ends x2334
Figure A-20.
Call Segment Relationship for Mobile Termination with Handoff and Handback
A-36
Issue 27
May 2004
Call Scenarios
Mobile Termination with Handoff to 2, 3, and 2

How It Starts
In this scenario, the subscriber receives a call. This call is eventually handed off to another serving DCS (DCS #2). The call is handed off to yet another serving DCS (DCS #3) and then handed back to the first serving DCS (DCS #2).
What Happens
At call handback, the ECP emits an x2338 AMA record (see number 2 in Figure A21 on page A-38) for DCS #2 (receiving the handoff). The ECP emits an x2336 AMA record (see number 3 in Figure A-21 on page A-38) for DCS #3 (the one that received the handoff). When the call ends, the ECP emits an x2336 AMA record (see number 4 in Figure A-21 on page A-38) containing the air-time after handback until call end for DCS #2. The ECP emits an x2334 record (see number 1 in Figure A-21 on page A-38) for DCS #1. The x2334 AMA record contains the total call time. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields.
Figures
Issue 27
May 2004
A-37
401-610-133A
PSTN handoff CPS DCS #1

1
ITG
Serving DCS DCS #2

2 4
handoff ITG handback
Serving DCS DCS #3

3
AMA
1
AMA
2
AMA
3
x2334
x2338 AMA
x2336
x2336
Figure A-21.
Mobile Termination with Handoff to 2, Handoff to 3, and Handback to 2
The relationship between the various call segments involved in this call is shown in Figure A-22 on page A-39. The duration of tandem segment for DCS #2 is not available in either the x2336 or x2338 AMA record.
A-38
Issue 27
May 2004
Call Scenarios
DCS 1 call placed (MT) AirSeg 1
DCS 2
DCS 3
call handed off to DCS #2
call handed off to DCS #3
AirSeg 2
call handed back to DCS #2 AirSeg 4 x2338
AirSeg 3 x2336 x2334 x2336 Issue 27 May 2004
call ends
Figure A-22.
Call Segment Relationships for Mobile Termination with Handoff to 2, Handoff to 3, and Handback 2
A-39
401-610-133A
Mobile to Mobile
How It Starts
In this scenario, a call is made to a mobile from another mobile on the same DCS. The call is completed.
What Happens
The originating mobile initiates a normal mobile origination. This is described in AMA Record Generation on page A-4. An x2330 AMA record is not generated since carrier interconnect is not used on intra-DCS calls.
Figure
LTG
DCS
AMA x2331
AMA or x2330 x2329
AMA
Figure A-23.
Mobile to Mobile Termination
A-40
Issue 27
May 2004
Call Scenarios

How It Starts
In this scenario, a mobile originates a call to another mobile. The call is routed to the DCS where the called mobile is homed.
What Happens
The mobile origination results in x2329 or x2330 AMA records; their treatment is as described in AMA Record Generation on page A-4. The ECP of the called mobile emits an x2118 or x2119 AMA record (because the call is redirected through a Loop Around Trunk Group (LTG) for the DCS. The call termination (x2331 AMA record) is handled normally.
Figure
LTG TTG
LTG
Mobile 1 CPS
DCS
DCS
Mobile 2 CPS
AMA
AMA
x2329 or x2330 AMA AMA x2118 or x2119
AMA or x2119 x2118 AMA x2331
AMA
Figure A-24.
Issue 27
May 2004
A-41
401-610-133A
Call Delivery (via Internal Trunks)

How It Starts
In this scenario, the mobile receives a call from the PSTN. This scenario uses internal Flexent/AUTOPLEX wireless network trunking between the DCSs. The DCSs may be on the same switch and an MSC boundary may be involved.
What Happens
The ECP generates an x2336 AMA record for the serving DCS. The ECP generates an x2335 AMA record for the CPS DCS on call end. This record contains the total call time. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields.
Figure
PSTN
MSC boundary perhaps ITG
CPS
DCS
DCS
AMA x2335 Figure A-25. Call Delivery (via Internal Trunks)
AMA x2336
A-42
Issue 27
May 2004
Call Scenarios
Call Delivery (via ANSI-41)

How It Starts
In this scenario, the mobile receives a call from the PSTN. This call case uses ANSI-41 networking between the DCSs. The DCSs may be on the same ECP. An MSC boundary may be involved.
What Happens
The ECP generates an x2329 or x2330 AMA record with SF = 100 (Special Cellular Networking) for DCS 1 on call end. The x2330 AMA record is generated if carrier interconnect is used. The ECP generates an x2331 AMA record with SF = 100 (Special Cellular Networking) for DCS 2. These AMA records are not linked, as shown in Figure A-26 on page A-43.
Figure
PSTN
PSTN NTG
DCS 1 NTG
DCS 2
CPS
AMA
AMA
AMA x2331 SF = SCN
x2329 or x2330 SF = SCN Figure A-26. Call Delivery (via ANSI-41)
Issue 27
May 2004
A-43
401-610-133A

How It Starts
In this scenario, the mobile receives a call via internal call delivery from a PSTN number. This call is handled off to another DCS as the mobile travels.
What Happens
The call delivery results in the ECP generating a x2335 AMA record for DCS 1 on call end. Each subsequent handoff (for example, to DCS 2, then to DCS 3) causes the ECP to generate an x2336 AMA record for the DCS. These AMA records are linked by the Transaction Code I and Transaction Code II AMA fields.
Figure
PSTN NTG CPS DCS 1 ITG DCS 2 ITG handoff DCS 3
AMA x2335
AMA x2336
AMA x2336
Figure A-27.
A-44
Issue 27
May 2004
Call Scenarios
Call Delivery (ANSI-41) with Handoff

How It Starts
In this scenario, the mobile receives a call via ANSI-41 Call Delivery from a PSTN number. This call is handed off to another DCS as the mobile travels.
What Happens
The ANSI-41 Call Delivery causes the ECP to generate an x2329 or x2330 AMA record for DCS 1 with service feature set to SF = 100 (Special Cellular Networking) on call end. The ECP of the system to which the call is redirected generates an x2334 AMA record (DCS 2) with service feature set to SF = 100 (Special Cellular Networking) on call end. Each subsequent handoff causes the ECP to generate an x2336 AMA record for the DCS (DCS 3). The x2329 or x2330 AMA records are not linked to any other AMA record. The x2334 and x2336 AMA records are linked by the Transaction Code I and Transaction Code II AMA fields.
Figures
Issue 27
May 2004
A-45
401-610-133A
PSTN NTG DCS 1 NTG
PSTN NTG CPS DCS 2 ITG handoff DCS 3
AMA
AMA
AMA x2334 SF = SCN
AMA x2336
x2329 or x2330 SF = SCN Figure A-28.
Call Delivery (ANSI-41) with Handoff
The relationship between the various call segments involved in this call is shown in Figure 1-29 on page A-46.
DCS 1 a call arrives for the mobile at DCS 1 and is redirected to DCS 2
DCS 2 AirSeg 1
DCS 3 the mobile answers
call handed off to DCS AirSeg 2
the call ends x2329/x2330 Figure 1-29. x2334
the call ends x2336
Call Segment Relationships for Call Delivery (ANSI-41) with Handoff
A-46
Issue 27
May 2004
Call Scenarios

How It Starts
In this scenario, the mobile subscriber is on a call at a serving DCS. The subscriber then receives a call via Call Delivery over an internal trunk. The mobile answers the call waiting call then terminates the original call.
What Happens
The mobile originated call (see number 1 in Figure A-30 on page A-48) causes the ECP to generate an x2329 or x2330 AMA record for the DCS. This record is treated as a normal mobile origination. The second call, the inter-switch termination call (see number 2 in Figure A-30 on page A-48), causes the ECP to generate an x2329 AMA record for the DCS with SF = 083 (Call Delivery to Call Waiting). The delivery of the inter-switch termination call (see number 3 in Figure A-30 on page A-48) results in a x2331 AMA record. This record is marked with SF = 056 (Call Waiting). None of these AMA records are linked.
Figures
Issue 27
May 2004
A-47
401-610-133A
PSTN
2
PSTN
1 2
DCS 1
DCS 2
1 3
AMA
2
AMA
1
AMA
x2329
x2329 or x2330 AMA

3
SF = CDCW
x2331 SF = CW
Figure A-30.
The relationship between the various call segments of this call is shown in Figure 1-31 on page A-48.
DCS 1
DCS 2 AirSeg 1 the mobile originates a call
call arrives at DCS 1 call is delivered to DCS 2
call arrives CW treatment applied the CW call is answered the first call ends
AirSeg 2
x2329/x2330 the CW call ends x2331
the CW call ends
x2329 Figure 1-31.
Call Segment Relationship for Call Delivery to Call Waiting
A-48
Issue 27
May 2004
Call Scenarios
Call Forwarding to Mobile

How It Starts
In this scenario, a call comes in from the PSTN to the mobile. The mobile has call forwarding set to a mobile number. The call is forwarded via the PSTN to the mobile number.
What Happens
This call looks like a mobile origination, but has the service feature set to one of the Call Forwarding values. (An LTG may be used instead of redirection through the PSTN.) The Flexent/AUTOPLEX wireless network AMA uses one service feature value for Call Forwarding Busy, Dont Answer, and No Page Response. The mobile termination portion of this call is any of the standard Mobile Termination scenarios. The records resulting from the mobile termination portion of the call are not linked to the call forwarding portions of the call. Use of trunk group mapping is required to determine the destination of a redirection (that is, redirection to a mobile or land station).
Figure
Issue 27
May 2004
A-49
401-610-133A
PSTN This portion of the call generates a separate set of AMA records.
DCS
DCS
AMA
AMA
x2329 or x2330 SF = ICF or CCF Figure A-32. Call Forwarding to Mobile
A-50
Issue 27
May 2004
Call Scenarios

How It Starts
In this scenario, the mobile is on a mobile originated call. During this call another call attempts to connect to the mobile. This call is not answered but is forwarded to a PSTN number.
What Happens
The first call (see number 1 in Figure A-33 on page A-52) results in normal mobile origination call records. The second call (see number 2 in Figure A-33 on page A-52) attempts to reach the mobile but eventually no answer is indicated. The call is redirected to the forward to number on the PSTN. The second origination record (an x2329 or x2330 AMA record) has service feature codes of 056 (Call Waiting) plus 014 (Call Forwarding-Dont Answer). The two x2329/x2330 AMA records are not linked. NOTE: One service feature code will be placed in the structure code layout and one in the module. There is no determining which service feature code will go in the structure code layout and which will be placed in the module.
Figures
Issue 27
May 2004
A-51
401-610-133A
Mobile Origination PSTN AMA AMA x2329 or x2330

2 1
Mobile Termination (CW-CFDA to PSTN) AMA AMA x2329 or x2330 SF = CW-CFDA
3port DCS
Figure A-33.
The relationship between the various call segments and legs involved in the call waiting portion of this call is shown in Figure A-34 on page A-53.
A-52
Issue 27
May 2004
Call Scenarios
DCS the mobile originates a call CW call arrives ring starts at mobile CW ringing ends call transferred
the second call ends x2329/x2330 SF = CW-CFDA x2329/x2330 Figure A-34. Call Segment Relationships for Call Waiting (No Answer Forward to PSTN)
the mobiles original call ends
Issue 27
May 2004
A-53
401-610-133A

How It Starts
In this scenario, the mobile is on a mobile originated call. During this call another call attempts to connect to the mobile. This call is not answered but is transferred to a voice mail system.
What Happens
The first call (see number 1 in Figure A-35 on page A-54) results in normal mobile origination call records. The second call (see number 2 in Figure A-35 on page A-54) attempts to reach the mobile but eventually no answer is indicated. The call is redirected to the voice mail system. These AMA records are not linked.
Figures
Mobile Origination PSTN AMA AMA x2329 or x2330

2 1
Mobile Termination (CWDA to VMX) AMA x2331 SF = CW MRSIND = Recording
3port DCS VMX
Figure A-35.
A-54
Issue 27
May 2004
Call Scenarios
The relationship between the various call segments and legs involved in the call waiting portion of this call is shown in Figure A-36 on page A-55.
DCS the mobile originates a call CW call arrives ring starts at mobile CW ringing ends call transferred
the second call ends x2331 SF = CW MRSIND=Recording x2329/x2330 Figure A-36. Call Segment Relationships for Call Waiting (No Answer Transfer to Voice Mail)
the mobiles original call ends
Issue 27
May 2004
A-55
401-610-133A

How It Starts
In this scenario, the mobile is on a mobile termination call. During this call another call attempts to connect to the mobile. The mobile has call waiting activated.
What Happens
The first call (see number 1 in Figure A-37 on page A-56) results in normal mobile termination call records. The second call (see number 2 in Figure A-37 on page A-56) is an incoming mobile termination attempt that invokes call waiting. This results in a x2331 AMA record being generated with SF = 056 (Call Waiting). The AMA records of these two calls are not linked.
Figures
PSTN A party DCS B party
A party Mobile Termination AMA x2331
B party Call Waiting Call Mobile Termination AMA x2331 SF = CW
Figure A-37.
The relationship between the various call segments and legs involved in this call is shown in Figure A-38 on page A-57.
A-56
Issue 27
May 2004
Call Scenarios
DCS the mobile receives a call CW call arrives ring starts at mobile
the second call ends x2331 SF = CW
the mobiles original call ends x2331 Figure A-38.
Call Segment Relationship for Mobile Termination with Call Waiting
Issue 27
May 2004
A-57
401-610-133A

How It Starts
In this scenario, the mobile is on a mobile originated call. During this call another call attempts to connect to the mobile. The mobile has no call forwarding features activated, but has call waiting activated.
What Happens
The first call (see number 1 in Figure A-39 on page A-58) results in normal mobile origination call records. The second call (see number 2 in Figure A-39 on page A-58) results in an x2331 AMA record with SF = 056 (Call Waiting). The AMA records of these two calls are not linked.
Figures
A party Mobile Origination PSTN B party AMA AMA
B party Mobile Termination (Call Waiting) AMA x2331 SF = CW
x2329 or x2330 A party
3port DCS
Figure A-39.
A-58
Issue 27
May 2004
Call Scenarios
The relationship between the various call segments and legs involved in this call is shown in Figure A-40 on page A-59.
DCS the mobile originates a call CW call arrives ring starts at mobile
second call ends x2331 SF = CW
the mobiles original call ends x2329/x2330 Figure A-40.
Call Segment Relationships for Mobile Origination with Call Waiting
Issue 27
May 2004
A-59
401-610-133A

How It Starts
In this scenario, the mobile subscriber originates a call, and adds another party to the call.
What Happens
The origination and handling of the first call (see number 1 in Figure A-41 on page A-60) are normal. The mobile puts the call on hold and originates another call (see number 2 in Figure A-41 on page A-60). This results in another x2329 or x2330 AMA record with SF = 010 (Three-Way Calling). No more parties can be added by the originating mobile subscriber. These AMA records are not linked.
Figure
Mobile Origination PSTN AMA 3port DCS AMA
Mobile Origination AMA AMA
x2329 or x2330
x2329 or x2330 SF = TWC
Figure A-41.
A-60
Issue 27
May 2004
Call Scenarios

How It Starts
In this scenario the mobile subscriber originates a call, and adds another party (by origination) to the call. The call is handled off to another DCS.
What Happens
The origination and handling of the first call (see number 1 in Figure A-42 on page A-62) is a normal mobile origination with an inter-DCS handoff. The mobile puts the call on hold and originates a call (see number 2 in Figure A42 on page A-62). This results in an x2329 or x2330 AMA record with SF = 010 (Three-Way Calling). The handoff results in an x2336 AMA record (generated at call end). The x2336 AMA record is linked to the x2332/x2333 AMA record of the first mobile origination (see number 1 in Figure A-42 on page A-62) by the Transaction Code I and Transaction code II AMA fields. The x2336 record is not linked to the second mobile origination (see number 2 in Figure A-42 on page A-62).
Figure
Issue 27
May 2004
A-61
401-610-133A
PSTN 3port DCS ITG handoff DCS
Mobile Origination AMA AMA x2332 or x2333
Mobile Origination AMA AMA x2329 or x2330 SF = TWC
Handoff AMA x2336
Figure A-42.
A-62
Issue 27
May 2004
Call Scenarios
Call Transfer from a Mobile-Originated Call

This scenario describes a Call Transfer that takes place from a mobile-originated call.
What Happens
A mobile subscriber originates a call to Party A and then adds Party B to the call. The mobile subscriber makes the call transfer.
How it Works
The following steps are involved in the call transfer: 1. The mobile subscriber places a call to Party A. This call is a mobile-originated call. Refer to number 1 in Figure A-43 on page A-64. 2. The mobile subscriber puts Party A on hold and originate a call to Party B. 3. The mobile subscriber hits the END key and Party A and Party B begin to talk. 4. As a result of the call transfer, either a x2329 or a x2330 AMA record with Service Feature (SF)=077 (call transfer) is created. Refer to number 2 in Figure A-43 on page A-64. The 3-way elapsed time equals the vc elapsed time in the AMA record. The 3-way elapsed time indicates the amount of elapsed time when all 3 parties are there before the call transfer happens. The AMA records for the two calls are not linked.
NOTE:
Issue 27
May 2004
A-63
401-610-133A
PSTN
Party A 1 3 port DCS
Party B 2 1 Mobile Originations AMA X2329 Or AMA X2330 2 Mobile Originations AMA X2329 Or SF=CT AMA X2330
Figure A-43.
Call Transfer Scenario l
DCS
Moble originates a call to party A Mobile originate a call to party B Mobile makes call transfer VC elapsed time
VC elapsed time Called party elapsed time
3-way elapsed time
Called party elapsed time
Party A or B ends the call X2329/X2330 call to party A X2329/X2330 call to party B with CT
Figure A-44.
Call Segment for a Call Transfer from a Mobile-Originated Call
A-64
Issue 27
May 2004
Call Scenarios
Call Transfer from a Mobile-Terminated Call

This scenario describes a call transfer from a mobile-terminated call.
What Happens
The mobile subscriber receives a call from Party A. During this call, the mobile subscriber originates a call to Party B. The mobile subscriber makes the call transfer.
How it Works
The following steps are involved in the call transfer: 1. Party A places a call to a mobile subscriber. This is a normal mobile-termination call. Refer to number 1 in Figure A-45 on page A-66. 2. The mobile subscriber puts Party A on hold and originates a call to Party B. Refer to number 2 in Figure A-45 on page A-66. 3. The mobile subscriber hits the END key and Party A and Party B begin to talk. 4. As a result of the call transfer, a AMA record that is marked as SF=077 (call transfer) is created. The 3-way elapsed time equals the vc elapsed time in the AMA record. Refer to number 2 in Figure A-45 on page A-66. The 3-way elapsed time indicates the amount of elapsed time when all 3 parties are there before the call transfer happens. The AMA records for the two calls are not linked.
NOTE:
Issue 27
May 2004
A-65
401-610-133A
PSTN
Party A 1 3 port DCS
Party B 2
1 Mobile Termination AMA X2331
2 Mobile Originator AMA AMA X2329 Or X2330
SF=CT
Figure A-45.
Call Transfer Scenario 2
A-66
Issue 27
May 2004
Call Scenarios
DCS
Mobile receives a call from party A Mobile originates a call to party B Mobile makes call transfer
VC elapsed time VC elapsed time 3-way elapsed time Called party elapsed time
Called party elapsed time
Party A or B ends the call X2329/X2330 with CT, call to party B X2331 call to from party A
Figure A-46.
Call Segment for a Call Transfer from a Mobile-Terminated Call
Issue 27
May 2004
A-67
401-610-133A
Voice-Mail Retrieval via Mobile (Revertive)

How It Starts
In this scenario, the mobile subscriber retrieves his voice mail by making a revertive call (a call to his own MIN).
What Happens
A mobile can retrieve his voice mail either by making a revertive call (dialing his own Mobile Identification Number (MIN)) or by using the feature code for his system (*FC). If the mobile subscriber makes a revertive call, the subscriber is routed through a loop around trunk to his voice mail system. A mobile origination (x2329 or x2330) AMA record is generated with no feature indication for voice mail retrieval, and SF!= 083 (Call Delivery to Call Waiting). However, the dialed digits match the MIN of the mobile. For the portion of the call inbound to the voice mail system an x2331 AMA record is generated with MRS Indicator = 1 (Message Recording Call). These two AMA records are not linked.
Figure
LTG DCS VMX AMA AMA AMA x2331 MRSIND = Recording Figure A-47. Voice-Mail Retrieval via Mobile (Revertive)
x2329 or x2330
A-68
Issue 27
May 2004
Call Scenarios
Voice-Mail Retrieval via Mobile (*Feature Code)

How It Starts
In this scenario, the mobile subscriber retrieves his voice mail by entering a feature code.
What Happens
A mobile can retrieve his voice mail either by making a revertive call (dialing his own MIN) or by using the feature code for his system (*FC). If the mobile makes a (*FC) call, the mobile is routed to the voice mail system. An x2329 AMA record indicating MRS Indicator = 2 (Message Retrieval Call) is generated.
Figure
VMX
DCS
AMA x2329 MRSIND = Retrieval Figure A-48. Voice-Mail Retrieval via Mobile (*Feature Code)
Issue 27
May 2004
A-69
401-610-133A
Voice-Mail Retrieval via PSTN

How It Starts
In this scenario, a subscriber retrieves his voice mail messages remotely over the PSTN.
What Happens
The DCS emits an x2331 AMA record with MRS Indicator = 1 (Message Recording Call) indicating that voice mail recording was used. This scenario is the same as the termination portion of the scenario described under Voice-Mail Retrieval via Mobile (Revertive) on page A-68.
Figure
PSTN AMA DCS x2331 MRSIND = Recording
VMX Figure A-49. Voice-Mail Retrieval via PSTN
A-70
Issue 27
May 2004
Call Scenarios
How It Starts
In this scenario, the mobile subscriber activates a feature, such as setting his forward to number. Alternatively, the mobile may be activating the feature remotely over the PSTN.
What Happens
The mobile subscriber enters a key sequence to activate or deactivate a feature. The ECP emits an x2411 AMA record (for call forwarding or Abbreviated Dialing with AMA [ADWA]) indicating the feature, the activation or deactivation status, and the number involved. If features are activated at an MSC other than the subscribers home MSC, then feature activation/deactivation AMA records are generated at both the serving MSC and the home MSC. If features are activated remotely, such as over the PSTN, then feature activation/deactivation records are generated by the ECP. These AMA records are not linked. Feature activation or deactivation can occur during a call, and the feature activation/deactivation AMA records and call AMA records are not linked.
Figure
Issue 27
May 2004
A-71
401-610-133A
PSTN
Local
PSTN
Remote
DCS
ECP
AMA x2411
AMA x2411
Figure A-50.
A-72
Issue 27
May 2004
Call Scenarios
How It Starts
In this scenario, a law enforcement agency has requested a wiretap on a particular subscriber. Any calls made or received by the subscriber are routed through a special loop around trunk to the appropriate monitoring facilities.
What Happens
Wiretap calls are the same as unwiretapped calls, except that the AMA record will contain a Service Code (AMASE Table 2002) value of SRFI = 302 (Increased Court Ordered Surveillance [ICOS]).
Figure
PSTN to monitoring facilities DCS
PSTN to monitoring facilities DCS
AMA x2331 SRFI = ICOS Figure A-51.
AMA
AMA
x2329 or x2330 SRFI = ICOS
Issue 27
May 2004
A-73
401-610-133A
Mobile Security Entry

How It Starts
In this scenario, the DCS detected an event of significance to the security of a mobile.
What Happens
The ECP emits an x2415 AMA record for the DCS indicating the type of security problem.
Figure
PSTN AMA DCS x2415
Figure A-52.
Mobile Security Entry
A-74
Issue 27
May 2004
Call Scenarios
Virtual Switch Handoff

How It Starts
In this scenario, one physical DCS is logically split to support two virtual DCSs. The virtual DCSs support two separate cellular systems, such as when a switch is shared between two markets. Each virtual DCS is dedicated to one system. This activity occurs when handoffs occur between systems-between virtual DCSs.
What Happens
Here the mobile subscriber originates a call on one virtual DCS and is handed off to another virtual DCS. The origination and handling of the mobile origination is normal. Note that origination is shown, but virtual switch handoff can occur for any call scenario. The ECP of the serving virtual DCS supplies an x2421 AMA record when it receives a handoff of this type. This AMA record identifies the to and from switch and cell. The x2329 AMA record (or other AMA records associated with the call) reports the air-time and other pertinent call details.
Figure
Figure 1-53 on page A-75 shows the scenario.
PSTN
Virtual Switch Division Physical DCS The DCSv numbers must be different. The CGSA numbers may be the same or may be different.
DCSv
DCSv
handoff
AMA x2329 Figure 1-53. Virtual Switch Handoff
AMA x2421
Issue 27
May 2004
A-75
401-610-133A
Callback
How It Starts
In this scenario, the mobile has originated or terminated a call. Another user wishes to talk to the mobile so the user calls the mobile and is placed on hold by the Call Waiting feature. When the mobile releases, the Flexent/AUTOPLEX wireless network reconnects the call waiting (held) Party to the mobile.
What Happens
The mobile origination (see number 1 in Figure A-54 on page A-76) and the call waiting call (see number 2 in Figure A-54 on page A-76) are handled as described in Mobile Origination with Call Waiting on page A-58. When the Flexent/ AUTOPLEX wireless network makes the callback connection (see number 2 in Figure A-54 on page A-76) to the mobile, it is seen (in AMA) as a normal call of the same type that was on hold. There is no indication of any special feature use. (Air usage accumulates for the call waiting call while it is on hold.)
Figure
PSTN on hold via call waiting DCS
PSTN
DCS
Figure A-54.
Callback
A-76
Issue 27
May 2004
Call Scenarios
Mobile Termination (not Home DCS) with Call Forwarding

How It Starts
In this scenario, the mobile subscriber is the recipient of a call from a PSTN number. The mobile is being served by a cell served by a DCS other than his home DCS. The mobile has Call Forwarding - Dont Answer enabled and the mobile does not answer the call. The call is forwarded.
What Happens
The ECP generates an x2336 AMA record for DCS 2 on call end. The ECP generates an x2332 or x2333 AMA record for the CPS (DCS 1) on call end. The AMA records are linked by the Transaction Code I and Transaction Code II AMA fields. The x2332 or x2333 AMA record contains the total call time.
Figures
Issue 27
May 2004
A-77
401-610-133A
PSTN
PSTN
CPS
DCS 1
ITG
DCS 2
AMA
AMA
AMA x2336
x2332 or x2333
SF = CF-Busy/No Answer/ No Page Response Figure A-55. Mobile Termination (not Home DCS) with Call Forwarding
DCS 2 the mobile is paged
the call is forwarded
paging times out x2336
the call ends x2332/x2333
Figure A-56.
Call Segment Relationships for Mobile Termination (not Home DCS) with Call Forwarding
A-78
Issue 27
May 2004
Call Scenarios
Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail
How It Starts
In this scenario, the mobile subscriber is the recipient of a call from a PSTN number. The mobile is being served by a cell served by a DCS other than his home DCS. The mobile has Call Forwarding - Dont Answer to Voice Mail enabled and the mobile does not answer the call. The call is forwarded to voice mail.
What Happens
The ECP generates an x2336 AMA record for DCS 2 on call end. The ECP generates an x2334 AMA record for the CPS (DCS 1) on call end. The AMA records are linked by the Transaction Code I and Transaction Code II AMA fields. The x2334 AMA record contains the total call time.
Figures
PSTN VMX ITG
CPS
DCS 1
DCS 2
AMA x2334 MRSIND = Recording Figure A-57.
AMA x2336
Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail
Issue 27
May 2004
A-79
401-610-133A
DCS 2 the mobile is paged
the call is forwarded to voice mail
paging times out x2336
the call ends x2334
Figure A-58.
Call Segment Relationships for Mobile Termination (not Home DCS) with No Answer Transfer to Voice Mail
A-80
Issue 27
May 2004
Call Scenarios
Test Calls
How It Starts
In this scenario, switch personnel are testing the system by originating or terminating calls.
What Happens
These calls are marked with SF = 104 (Mobile Station Test).
Issue 27
May 2004
A-81
401-610-133A
Tracer Records
The Flexent/AUTOPLEX wireless network system sends out statistical records. These include: Table A-5. Tracer Records Description Contains hourly call processing statistics. (See Structure Code 01047 on page 3-5.) Contains hourly AMA teleprocessing statistics. (See 401-612-023, AMA Teleprocessing and Structure Code 09042 on page 3-72.) Contains statistics related to the teleprocessing of secondary AMA records. (See 401-612-023, AMA Teleprocessing and Structure Code 09043 - Secondary Tracer on page 3-74.) Contains statistics related to the writing to tape of AMA records. (See the following:

Tracer Record Type Call Assembly Tracer Records (01047) Primary Tracer Records (09042)
Secondary Tracer Records (09043)
Tape-Only Tracer Records (09036, 09037, 09038, 09039)
Structure Code 09036 on page 3-64 Structure Code 09037 on page 3-66 Structure Code 09038 - CLDS Header Tape-Only Tracer on page 3-68 Structure Code 09039 - CLDS Trailer Tape-Only Tracer on page 3-70)
A-82
Issue 27
May 2004
Changes for ECP Release 22.0

This issue of the AMA Formats Description includes information about new features for the following releases:

ECP Release 22.0 Software Updates (SUs) that were released since the previous issue of this document
Table B-1 on page B-1 lists the features that impact AMA and gives the page number of the writeup in this section that summarizes the technical changes for the feature. Table B-1. Feature AMA Enhancement of Home Zone Service Phase 2 and KTF Intelligent Networking Support of KTF Wireless Number Portability Report Call Forwarding Due to No Reply in AMA Records Imsi In-Bound Roaming for KTF Feature ID 10468.1 10643.0 10667.0 10796.0 Page B-2 B-2 B-4 B-5
Issue 27
May 2004
B-1
401-610-133A
Feature Documentation Fixes for Metered Billing Append Specific AMA Modules to Structure Code x2351 Obsolete Features
Feature ID NA 10904.0 3876.0 and 3876.1
Page B-5 B-7 B-8
AMA Enhancement of Home Zone Service for Phase 2 and KTF Intelligent Networking
The changes for Feature Identifier (FID) 10468.1 were covered under FID 10468.0 in ECP Release 21.0.
Support of KTF Wireless Number Portability

This section gives an overview of the WNP feature and the functionality of the Support of KTF Wireless Number Portability feature.
Overview of Wireless Number Portability

The Wireless Number Portability (WNP) feature allows a mobile user to retain the same Directory Number (DN) while the mobile user moves from one service provider to another service provider. There types of Number Portability (NP) are as follows: Service Portability, Location Portability and Service Provider Portability.
Functionality
The Support of KTF Wireless Number Portability feature allows a mobile user to retain the same Mobile Directory Number (MDN) when the mobile user moves from one service provider to another service provider. AMA functionality for the Support of Wireless Number Portability (KTFWNPT) feature is similar to AMA for WNP, except that in the case of KTFWNPT, the

Location Routing Number can be 11 digits. Service provider ID appears in the WNP module (Service Provider ID field). ported status appears in the WNP module (BCD character 4 of the Supporting Information field).
NOTE: This feature does not apply to landline DNs.
B-2
Issue 27
May 2004
The Support of KTF Wireless Number Portability feature introduces the following Feature Activation File (FAF): Support of KTF Wireless Number Portability (KTFWNPT). Table B-2. Changes for the Support of KTF Wireless Number Portability Feature Caused... the following changes:
AMASE Table 731 Location Routing Number (LRN) on page 4-84 (A note is added to BCD 1 and the existing note in BCD 2 is modified to include KTFWNPT information.) Table 732 Service Provider Identity on page 4-85 (A note is added.) Table 734 Supporting Information on page 4-87 (A note is added under BCD character 4.)
changes to
Chapter 5Modules
Module 720Wireless Number Portability Module on page 5-73.The KTFWNPT feature is added to
Features that Use this Module on page 5-73. Module Generation Criteria on page 5-73 and the note that follows the module generation criteria is modified. the Module Generation Criteria for Wireless Number Portability Feature on page 36-9. (The first bullet item is modified to include the KTFWNPT FAF). Chapter 36Wireless Number Portability Feature
changes to
Issue 27
May 2004
B-3
401-610-133A
Report Call Forwarding Due to No Reply in AMA Records

This section provides the background and the functionality that is associated with the Report Call Fowarding Due to No Reply in AMA Records feature.
Background
Prior to the Report Call Forwarding due to No Reply in AMA Records feature, when a call is forwarded, the service feature field in the AMA record indicates the following: Call ForwardingBusy/Dont Answer/No Page Response (14). The reason for forwarding the call is not indicated. When the Conditional Call Forwarding (CCF) feature is active and the Show CCF sub-case in AMA records field in the Executive Cellular Processor (ecp) form is set to y, the following service feature codes are displayed, Call ForwardingBusy (152) and Call ForwardingNo Reply (153). The reason for forwarding the call is not indicated.
Functionality
The Report Call Forwarding Due to No Reply in AMA Records feature introduces two service feature codes, Call ForwardingNo Page Response, (154) and Call ForwardingMobile Inactive, (155). The Report Call Forwarding Due to No Reply in AMA Records feature indicates a reason in the service feature code for a forwarded call when there is no reply. Table B-3. Changes for the Report Call Forwarding Due to No Reply in AMA Records feature Caused... the addition of the following 2 new service feature codes:
This Change... New service feature codes
154 = Call Forwarding - No Page Response in Table 2002 Service Feature Code on page 4-119 and 155 = Call Forwarding - Mobile Inactive in Table 2002 Service Feature Code on page 4-119.
B-4
Issue 27
May 2004
Imsi In-bound Roaming for KTF

The Imsi In-bound Roaming for KTF feature allows Global System for Mobile Communications (GSM) subscribers to roam in to Code Division Multiple Access (CDMA) network and avail origination and termination services. GSM subscribers use CDMA handsets with GSM sim cards. Roaming Gateway maps CDMA messages to GSM and vice versa to communicate with the GSM system. AMA marks GSM roaming subscriber as 8 to denote that it is a GSM subscriber. Table B-4. Changes for the IMSI In-bound Roaming for KTF Feature Caused... the addition of
This Change... Denoting type of technology
08 = GSM in Table "Table 471 Type of Technology" on page 4-62
Documentation Fixes for the Metered Billing Feature

Chapter 27Metered Billing Feature is updated to include changes as per AR075102. Special Routing/Increased Court Ordered Surveillance (ICOS) functionality is added to Metered Billing and is available from ECP Release 17.0. Table B-5 on page B-5 refers to how Metered Billing uses the AMASE tables and AMA Record fields. Table B-5. Changes for the Metered Billing Feature Caused...
This Change... information about ICOS supporting Metered Billing
In... Chapter 27Metered Billing Feature
the addition of Table 27-1 on page 27-6
Append Specific AMA Modules to Structure Code x2351 Feature

If the Append AMA Specific AMA Modules to Structure Code x2351 FAF is on, the following AMA modules are appended to the structure code x2351:

330 331 621 with Generic Context Identifier 10843
Issue 27
May 2004
B-5
401-610-133A
621 with Generic Context Identifier 10860 621 with Generic Context Identifier 90002 621 with Generic Context Identifier 90010 623
B-6
Issue 27
May 2004
Table B-6.
Changes for Append Specific AMA Modules to Structure Code x2351

Caused... the following change:
This Change... use of structure code x2351
In... Chapter 3Structure Code Layouts
modifications to Table 3-28 "Valid Modules for Structure Code x2351" on page 3-48 modifications to Table 5-3 "Module Generation Criteria" on page 5-13. additions to Modules 330 and 331CPN Incoming Calls Modules on page 5-28 additions to Module 621 - Digit Information Module on page 5-46 with generic context identifiers 90002, 90010, 10843, 10860 modifications to Module 623 Trunk Information Module on page 5-70 adding structure code x2351 to Module 331 in Use of CPN Incoming Calls Module-2 on page 17-3 modifications to Module Generation Criteria for CPN Incoming Calls Module-1 Module or the CPN Incoming Calls Module-2 Module on page 18-4 modifications to Trunk Information Module on page 28-7
the following changes:
Chapter 5Modules
Chapter 17AMA Containing Incoming Automatic Number Identification (AMANI) Feature Chapter 18Calling Number Identification Presentation and Restriction Capability Feature
Chapter 28AMA Enhancements Feature
Issue 27
May 2004
B-7
401-610-133A
Obsolete Features
The following features are obsolete and have been deleted from the book:

IS41 Roamer Administration Service (IS41-RAS) Authentication Indicator in AMA Records (FID 3876.0) Authentication Indicator in AMA for Home Subscribers (FID 3876.1)
B-8
Issue 27
May 2004

This appendix gives a history of revisions to this manual for current and previous ECP software releases.
Issue 27
May 2004
B-9
401-610-133A
Reason for Reissue

Introduction
This issue of the AMA Formats Description with 15 Digit DN includes information about new features for the following releases:

Table B-7 on page B-10 lists the features that impact AMA and gives the page number of the writeup in this section that summarizes the technical changes for the feature. . Table B-7. Feature Charging Band for Metering Pulse Providing Redirection Information in KTF Recall Service Answer Hold Call Drop Handling Limited Mobility Services with Multiple SDCAs/MDNs Maintain Selected AMA Measurement Data Reporting Per-Call Measurement Data (PCMD) AMA Enhancements of Home Zone Service Phase 2 and KTF Intelligent Network Service Call Scenarios Documentation fixes Table of Contents for Changed Features Section Feature ID 9224.0 9276.0 9185.0 9186.0 10315.0 10316.0 4417.2 10468.0 NA NA Page B-10 B-12 B-12 B-13 B-14 B-16 B-17 B-18 B-20 B-20
Charging Band for Metering Pulse

The Charging Band for Metering Pulse feature requests the Lucent MSC to deliver meter pulses to the wireless pay phone when the Lucent MSC receives ISUP CRG message from DTAX. For more information on the Charging Band for Metering Pulse feature, see 401-612-687, Charging Band for Metering Pulse optional feature description.
B-10
Issue 27
May 2004
Public Call Office (PCO) Mobiles

If the call originates from a Public Call Office (PCO) mobile that works like a pay phone, the MSC calculates the metering pulse based on the Charge Band Number that is received and sends the pulse to the wireless phone. The Charge Band number replaces the Charge Index that is used to meter the pulse calculation. The service provider can provision the Call Treatment Information (CTREAT) and Charge Index Expansion Information (CXIEP) Recent Change/Verify forms with values that range from 0 to 255 for the Charging Band for Metering Pulse feature. The MSC records the Charge Band Number to AMA.
Non-PCO Mobiles
If the call originates from a non-PCO subscriber, the MSC simply records the Charge Band Number to the AMA. Table B-8. Changes for Charging Band for Metering Pulse feature Caused... Addition of the following generic context identifier to Table 4-24 "AMASE Table 237" on page 4-39
This Change... New Generic Context Identifier
90060 = Charging Band for Metering Pulse on page 4-40
Use of Digit Information Module
Addition of
Chapter 5Modules
Module generation criteria for the Digit Information Module with the Charging Band for Metering Pulse feature on page 5-19
90060 on page 5-48 for Charging Band for Metering Pulse (x2118, x2119, x2329, x2330, x2332 and x2333) on page 5-48 Charging Band for Metering Pulse on page 5-51 Charging Band for Metering Pulse on page 5-66
Issue 27
May 2004
B-11
401-610-133A
Providing Redirection Information in KTF Recall Service

This section describes the enhancement to the KTF Recall Service feature.
Background
The KTF Recall Service feature routes incomplete calls to a Recall Service Center (RCS) based on a new redirection indicator and routing number. The RCS cannot play an announcement to the calling party when the call is forwarded.
Enhancement to the KTF Recall Service

FID 9276, Providing Redirection Information in KTF Recall Service feature allows MSCs to receive and interpret the reason for forwarding a call from the HLR. The Providing Redirection Information in KTF Recall Service feature also passes this information to the RCS when the ISUP IAM message is sent to the RCS. Because the information is provided to the RCS, the RCS can play a proper announcement to the calling party informing them why the call was dropped. For more information on Providing Redirection Information in KTF Recall Service, refer to 401-612-503, KTF Recall Service optional feature description. Table B-9. Changes for Providing Redirection Information in KTF Recall Service Feature Caused... Addition of the following service feature code to AMASE Table 2002 on page 4-119
This Change... New feature service code
326 = Recall Service on page 4-121
Answer Hold
This section describes the Answer Hold feature.
How the feature works

The Answer Hold feature allows an authorized Answer Hold (AH) subscriber to answer incoming calls but selectively delay the conversation. The incoming call is given an appropriate network announcement to notify the calling party to hold, while the subscriber receives a confirmation tone.
B-12
Issue 27
May 2004
Table B-10.
Changes for Answer Hold feature Caused... Addition of the following service feature code to AMASE Table 2002 on page 4-119
325 = Answer Hold on page 4-121 Chapter 4AMASE Tables
New generic context identifier
Addition of the following generic context identifier to Table 4-24 on page 4-39
90063 = Call Released in Answer Hold State on page 4-40
Addition of
Modules on page 5-1
Module generation criteria for the Digit Information Module with the Answer Hold feature on page5-19 90063, Call Released in Answer Hold State (x2329, x2330, x2331, x2332, x2333, x2334, x2335) on page 5-48 and Module 621 - Digit Information Module on page 5-46 Answer Hold on page 5-51 Answer Hold on page 5-66
Call Drop Handling

This section describes the Call Drop Handling feature.
Background
Before the Call Drop Handling feature was introduced, the MSCs (in a subscribers network) did not know if calls were dropped in a counterpart MSC, for example, an originating MSC did not know if a call was dropped in the terminating MSC or a terminating MSC did not know if a call was dropped in the originating MSC.
Issue 27
May 2004
B-13
401-610-133A
What the feature does

The Call Drop Handling feature allows the MSC to know if a call is dropped in the counterpart MSC. If the terminating MSC drops a call, the terminating MSC sends an ISUP release message to the originating MSC with the cause value. When the originating MSC receives the ISUP release message with the cause value of H29 that indicates temporary failure, the originating MSC indicates the call drop (in the counterpart MSC) in the AMA record of the originating MSC. If the originating MSC drops a call, the originating MSC sends an ISUP release message to the terminating MSC with a cause value. When the terminating MSC receives the ISUP release message, the terminating MSC indicates the call drop (in the counterpart MSC) in the Communicate failure indicator field of the AMA record of the terminating MSC. NOTE: The Call Drop Handling feature is applicable only to mobile-to-mobile calls that originate and terminate in the service providers network, however, if the mobile-to-mobile call is delivered by Public Switched Telephone Network (PSTN) or other service providers to the terminating MSC, the Call Drop Handling feature is not applicable. Table B-11. Changes for Call Drop Handling feature Caused... Addition of the following code to AMASE Table 2005 on page 4-132
This Change... New communication failure code
010 = Counterpart MSC Call Drops on page 4-132

The LMSMSM feature provides roaming capability for the mobile subscriber by allowing service in different pre-selected Short Distance Charging Areas (SDCAs) with different numbers.
B-14
Issue 27
May 2004
Table B-12.
Changes for Limited Mobility Services with Multiple SDCAs/MDNs Caused... Addition of the following service feature code to AMASE Table 2002 on page 4-119
In... AMASE Tables on page 4-1
327 = Limited Mobility Services with Multiple SDCAs/ MDNs on page 4-121 Chapter 4AMASE Tables
Use of Generic Context Identifier
A reference to the following Generic Context Identifiers in AMASE Table 237 on page 4-39
10830 = 10-digit Mobile Identification Number on page 4-39 90010 = Incoming Called Digits on page 4-40
The addition of
Chapter 5Modules
Module generation criteria for the Limited Mobility Services with Multiple SDCAs/MDNs feature on page5-19 Mobile Identification Number (MIN) (for Structure Codes x2118, x2119, x2329-x2338, x2351, x2411, x2415, and x2421) on page 5-47 Incoming Called Digits (for Structure Codes x2331, x2334, and x2335, x2329, x2330, x2332, x2333, x2351) on page 5-47 Limited Mobility Services with Multiple SDCAs/MDNs on page 5-51 Incoming Called Digits in AMA on page 5-59 Chapter 55Limited Mobility Services with Multiple SDCAs/MDNs
All
New chapter that explains this feature
Issue 27
May 2004
B-15
401-610-133A
Maintain AMA Measurement Data Reporting

This section describes the Maintain AMA Measurement Data Reporting feature.
What the Feature Does

The Maintain Selected AMA Measurements Data Reporting feature provides selected information of the measurement data to the billing system through a new DIM module with a new Generic Context Identifier 90062.
How the Feature Works

The Maintain Selected AMA Measurements Data Reporting feature collects the following measurement data in AMA call records:

Assigned Radio Frequency Carrier Assigned CDMA Technology Version Service Option Allocated Call Final Class Call Final Class Qualifier
Table B-13.
Changes for Maintain Selected AMA Measurement Data Reporting Caused... Addition of the following generic context identifier to Table 4-24 on page 4-39
This Change... New generic context identifier
90062 = Maintain Selected AMA Measurement Data Reporting on page 4-40
B-16
Issue 27
May 2004
Caused... Addition of
In... Modules on page 5-1
Module generation criteria for the Digit Information Module with the Maintain Selected AMA Measurements Data Reporting feature on page5-19 90062 on page 5-48 and Maintain Selected AMA Measurement Data Reporting (x2118, x2119, x2329, x2330, x2331, x2332, x2333, x2334, x2336, x2411, x2415) on page 5-48 Maintain Selected AMA Measurement Data Reporting on page 5-51 Maintain Selected AMA Measurement Data Reporting on page 5-66 Chapter 56, Maintain Selected AMA Measurement Data Reporting
All
A new chapter that explains this feature
Per-Call Measurement Data (PCMD)

The Per-Call Measurement Data feature replaces the Measurement Data in Call Records (MDCR) feature. Table B-14. Changes for Per-Call Measurement Data feature Caused... Removes the MDCR chapter In... from the book
This Change...
Issue 27
May 2004
B-17
401-610-133A
This Change... Discontinuing the use of four Modules
Caused... Removes the use of the following DIMs:

In... Modules on page 5-1
MDCR (990) Service Measurement Module (991) Pilot Measurement Strength Message (PSSM) (992) Non-Reference PSSM (993) Chapter 4AMASE Tables
Discontinuing the use of four AMASE tables
Removes the use of the following AMASE tables:

Table 960-Cell Type Table 966-PSSM Data from Non-Reference Cell Table 968-Service Measurement Counts Table 969-Band Class Chapter 4AMASE Tables
Modifying Call Final Class Qualifiers
In AMASE Table 965 on page 4-109, the following apply:
502 = Speech handler activation failure (This was speech handler activation/ protocol failure). added 509 = Speech handler protocol failure added 604 = Walsh code unavailable
AMA Enhancements of Home Zone Service Phase 2 and KTF Intelligent Network Service
The AMA Enhancement of Home Zone Service Phase II feature enhances the following existing features to correctly bill subscribers:

Home Zone Service Phase 2 KTF Intelligent Network Services including KTF WIN, KTF VPN and trigger features
The AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature appends DIM 621 with the Generic Context Identifier 90064 to AMA records when the affected features are used.
B-18
Issue 27
May 2004
NOTE: This features DIM overrides the functionality of using the Service Feature Codes 323 (Home Zone Service Discount Rate) and 324 (Home Zone Service Normal Rate) that are associated with the Home Zone Service Phase 2 feature. In other words, if the AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature is active and the KTF Intelligent Network Service Phase 2 field on the ecp form is on, the Home Zone Service Discount/ Normal Rate that is stored in the DIM with the Generic Context Identifier 90064 takes precedence over the service feature field. Table B-15. Changes for FID 10468.0 Caused... Addition of the following generic context identifier to Table 4-24 on page 4-39
This Change... New generic context identifier
90064 = KTF Intelligent Network and Home Zone 2 Services on page 4-40
Addition of
Modules on page 5-1
Module generation criteria for the Digit Information Module with the AMA Enhancements for Home Zone Service Phase 2 and KTF Intelligent Network Service feature on page5-19 90064 on page 5-48 and KTF Intelligent Network and Home Zone 2 Services (x2329, x2330, x2331, x2332) on page 5-48 AMA Enhancements of Home Zone Services Phase 2 and KTF Intelligent Network Service on page 5-51 AMA Enhancements of Home Zone Service Phase 2 and KTF Intelligent Network Service on page 5-66
Issue 27
May 2004
B-19
401-610-133A
This Change... All
Caused... A new chapter that explains this feature
In... Chapter 57, AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service Feature
Call Scenarios
Two new call scenarios for Call Transfer were added. See the following sections in Appendix ACall Scenarios:

Call Transfer from a Mobile-Originated Call on page A-63 Call Transfer from a Mobile-Terminated Call on page A-65
Documentation Fixes
The following documentation fixes were made to the document in In Chapter 5, Modules on page 5-1
In Module 720Wireless Number Portability Module on page 5-73, the following correction was made to the criteria that is provided for Wireless Number Portability Module: An LRN was received in the incoming ISUP message, so a Number Portability Request is not necessary; the information is already at hand. (This can happen with tandem MSCs.) This correction removes a reference to terminating MSCs.
NOTE:
Under the module generation criteria for CPNAD on page 5-30, the last bullet item is enhanced to include message recording to a VMSS. A note is also added. Under the module generation criteria for Incoming Called Digits in AMA on page 5-59, the last bullet item is enhanced to include message recording to a VMSS.
B-20
Issue 27
May 2004

Introduction
This issue of the AMA Formats Description with 15 digit DN includes information about new features for the following releases:

Table B-16 on page B-21 lists the features that impact AMA and gives the page number of the writeup in this section that summarizes the technical changes for the feature. Table B-16. Feature IS-826 Locally-Allowed Specific Digit String Trigger Selectable Mode Vocoder on PHV KTF Home Zone Service Phase 2 Documentation Fix Consolidation of 15 Digit DN Information Table of Contents for Changed Features Section Feature ID 4575.2 4884 8126.1 NA NA Page B-22 B-23 B-24 B-25 B-25
Issue 27
May 2004
B-21
401-610-133A
IS-826 Locally-Allowed Specific Digit String Trigger

The IS-826 Locally-Allowed Specific Digit String Trigger feature gives the service provider the Wireless Intelligent Network (WIN) standard provision to deal with locally-allowed numbers (for example, 911). The AMA change for this feature is to capture the IS-848 Charging Information for the call in the AMA record. This feature builds upon 4575.1, the Specific Called Party Digit String Trigger feature. For an explanation of the Specific Called Party Digit String Trigger Feature, go to page B-28 in Appendix BHistory of Revisions. NOTE: In the ECP Release 19.0 version of this document, the two fields captured by the 4575.1 and 4575.2 features were referred to as DMH Charge Information and DMH Billing Information. However, the RC/V forms were called IS-848 Billing Indicator and IS-848 Charge Information. (DMH Charge Information and DMH Billing Information are defined in the IS-848 standard.) To be more consistent, the documentation for the 4575.1 and 4575.2 features in the ECP Release 20.0 version of this document has been changed to use the terms IS848 Billing Indicator and IS-848 Charge Information. (The definitions for the 90031 and 90032 Generic Context IDs have also been changed. See 90031 = IS-848 Billing Indicator on page 4-40 and 90032 = IS-848 Charge Information on page 4-40.) Table B-17 on page B-22 shows changes made to support the IS-826 LocallyAllowed Specific Digit String Trigger feature in this document. Table B-17. Changes for IS-826 Locally-Allowed Specific Digit String Trigger Feature Caused... Addition of:
This Change... use of Digit Information Module
In... Chapter 5Modules
Module generation criteria for the Digit Information Module for this feature on page 5-19 Module generation criteria for the Digit Information Module for the Specific Called Party Digit String Trigger feature on page 5-19* IS-826 Locally-Allowed Specific Digit String Trigger on page 5-51 IS-826 Locally-Allowed Specific Digit String Trigger on page 5-65
B-22
Issue 27
May 2004
Table B-17.
Changes for IS-826 Locally-Allowed Specific Digit String Trigger Feature Caused... revision of existing chapter In... Chapter 50Specific Digit String Trigger Features
This Change... revision of chapter on Specific Called Party Digit String Trigger feature to include the IS-826 LocallyAllowed Specific Digit String Trigger feature
* This corrects an omission from the documentation for the Specific Called Party Digit String Trigger feature (4575.1). (An entry for DIM containing DMH Billing Indicator for the Specific Called Party Digit String Trigger feature was also added.)

The Selectable Mode Vocoder on PHV feature enables the Mobile Switching Center (MSC) to provide Selectable Mode Vocoder service. The Selectable Mode Vocoder is a new Code Division Multiple Access (CDMA) third generation vocoder that gives more options for improving voice quality or improving radio frequency (RF) capacity. Table B-18 on page B-23 shows changes made to support the Selectable Mode Vocoder on PHV feature in this document. Table B-18. Changes for Selectable Mode Vocoder on PHV Feature Caused... Addition of the following Event Description to Table 4-46 "AMASE Table 497 Event Description Values for Event Type 002" on page 4-76
This Change... new Event Description
00056 = SMV Voice Chapter 4AMASE Tables
new Generic Context Identifier
Addition of the following generic context identifier to Table 4-24 "AMASE Table 237" on page 4-39:
90030 = Forward/Reverse Initial Assigned SMV Mode
Issue 27
May 2004
B-23
401-610-133A
Table B-18.
Changes for Selectable Mode Vocoder on PHV Feature Caused... Addition of:
This Change... use of Digital Event Module
Module generation criteria for the Digital Event Module with the Selectable Mode Vocoder on PHV feature to Module Generation Criteria Table on page 5-16 Selectable Mode Vocoder on PHV on page 5-34 Addition of Selectable Mode Vocoder on PHV feature to the Module Generation Criteria on page 5-34 Chapter 5Modules
use of Digit Information Module
Addition of:
Module generation criteria for the Digit Information Module with the Selectable Mode Vocoder on PHV feature to Module Generation Criteria Table on page5-19 Forward/Reverse Initial Assigned SMV Mode (x2329, x2330, x2331, x2332, x2333, x2334, and x2335) on page 5-48 Selectable Mode Vocoder on PHV on page 5-51 Selectable Mode Vocoder on PHV on page 5-52 Selectable Mode Vocoder on PHV on page 5-65 Chapter 54Selectable Mode Vocoder on PHV
all
new chapter explaining this feature
KTF Home Zone Service Phase 2

The KTF Home Zone Service Phase 2 feature allows subscribers to be charged a pre-arranged discount rate when originating calls from a pre-arranged area called a Home Zone.
B-24
Issue 27
May 2004
For more information on this feature, see the Home Zone Service Phase II optional feature document, 401-612-646. Table B-18 on page B-23 shows changes made to support the KTF Home Zone Service Phase 2 feature in this document. Table B-19. Changes for KTF Home Zone Service Phase 2 Feature Caused... Addition of the following service feature codes to Table 4-70 "AMASE Table 2002" on page 4-119
This Change... two new service feature codes
323 = Home Zone Service Discount Rate 324 = Home Zone Service Normal Rate
Documentation Fix
In ECP 18.0, when the Measurement Data in Call Record (MDCR) feature was introduced, a definition was omitted. The value of the Keep Indicator field that is associated with MDCR data was omitted from AMASE Table 801. This information has been placed in Table 801 in this version of the document. See Keep Indicator Field on page 4-89 and Keep Indicator Field on page 4-90.
Consolidation of 15 Digit DN Information

ECP releases, information about changes made for the 15 Digit DN feature has been consolidated into Appendix EChanges for the 15 Digit DN Feature. NOTE: The title of this document will remain AMA Formats Description with 15 Digit DN and the document number will remain 401-610-133A until ECP 17.0 is no longer available, to avoid confusion with the older document, AMA Formats Description (401-610-133). The 401-610-133 will remain on the documentation CD-ROM until ECP 17.0 is no longer available.
Issue 27
May 2004
B-25
401-610-133A
Changes for ECP 19.0

Introduction
The ECP 19.0 issue of the AMA Formats Description with 15 Digit DN includes information about new features for the following releases:

ECP 19.0 SUs that were released since the previous issue of this document
Table
Table B-20 on page B-26 lists AMA-impacting features and gives the page number of the section in this chapter that summarizes the technical changes for the feature. Table B-20. Feature Speech Handler Trunk Information in AMA Seven-Digit AMA Block Sequence Number Fix to Radio Channel Number Range Specific Called Party Digit String Trigger TDMA Channel Usage Tracking Tool Enhancement to Far End Release Cause Values in AMA Records Documentation Fix for MDCR Feature Documentation Fix for 15 Digit DN Feature Customized ESN Format in AMA Record Documentation Fixes for Service Feature Codes Documentation Fix for Structure Code x2351 Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records Service Feature Code for Unknown Feature Activation/ Deactivation Table of Contents for Changed Features Section Feature ID 4663 4429.1 NA 4575.1 2200.20 8262.0 4417.0 3513.0 9117.0 NA NA 8937.0 NA Page B-27 B-37 B-28 B-28 B-29 B-31 B-32 B-32 B-33 B-33 B-33 B-34 B-35
B-26
Issue 27
May 2004
Speech Handler Trunk Information in AMA

The Speech Handler Trunk Information in AMA feature allows the service provider to store speech handler information for each call in the Digit Information Module. At present, the Speech Handler Trunk Information in AMA feature is available for TDMA only. Table B-21 on page B-27 shows changes made to support the Speech Handler Trunk Information in AMA feature in this document. Table B-21. Changes for Speech Handler Trunk Information in AMA Feature Caused... Addition of: 10836 = Speech Handler Trunk Information on page 4-39 Addition of:
This Change... New Generic Context ID
Chapter 5Modules
Speech Handler Trunk Information in AMA (for Structure Codes x2411, x2421, and x2329 - 2338) on page 5-47 Speech Handler Trunk Information in AMA on page 5-51 Speech Handler Trunk Information in AMA on page 5-64 Chapter 49Speech Handler Trunk Information in AMA Feature
new feature
Addition of new chapter describing Speech Handler Trunk Information in AMA feature

With the increase in call capacity soon to be provided in the Flexent/AUTOPLEX system, one million AMA blocks may not be sufficient to store two days worth of AMA records. The current six-digit AMA block sequence numbers will overflow and begin to overwrite by wrap-around once call capacity approaches or exceeds approximately 500K BHCA. This results in loss of AMA records.
Issue 27
May 2004
B-27
401-610-133A
To enable service providers to store at least two days worth of backup AMA data even after 700K Busy Hour Call Attempt threshold is reached, this feature increases the valid AMA block sequence number range to seven digits (9,999,999). The 700K Busy Hour Call Attempt feature will be delivered in ECP 19.0. The information on Seven Digit AMA Block Sequence Number was included in the ECP 18.0 issue of this document, but is reprinted here for ease of access. Only service providers who have high call capacity in their networks (approximately above 500K BHCA) will require this feature.
Once you start using seven-digit AMA block sequence numbers, DO NOT switch back to six-digit AMA block sequence numbers. Switching back could cause loss of AMA records. Table B-22 on page B-28 shows changes made to support the Seven Digit AMA Block Sequence Number feature in this document. Table B-22. Changes for Seven Digit AMA Block Sequence Number Feature Caused... new section, Ranges with Seven Digit AMA Block Sequence Number Feature on page 4-99 In... Chapter 4AMASE Tables
CAUTION:
This Change... use of formerly unused (padding) digit in Table 804 7-Digit Number on page 4-95 new feature
Addition of new chapter describing Seven Digit AMA Block Sequence Number feature
Chapter 47Seven Digit AMA Block Sequence Number
Fix to Radio Channel Number Range

The maximum Radio Channel Number range has changed. The old range, 11023, was changed to a new range of 2 - 1998. The documentation was changed on page 4-102 to reflect this change.
Specific Called Party Digit String Trigger

The Specific Called Party Digit String Trigger Feature feature allows the service provider to store WIN trigger DMH Billing Indicator and DMH Charge Information in the AMA record.
B-28
Issue 27
May 2004
Table B-23 on page B-29 shows changes made to support the Specific Called Party Digit String Trigger Feature feature in this document. Table B-23. Changes for Specific Called Party Digit String Trigger Feature Feature Caused... Addition of:
This Change... New Generic Context IDs
90031 = IS-848 Billing Indicator on page 4-40 90032 = IS-848 Charge Information on page 4-40
Addition of:
Chapter 5Modules
DMH Billing Indicator (x2329, x2330, x2332, and x2333) on page 5-48 DMH Charge Information (x2329, x2330, x2332, and x2333) on page 5-48 Specific Called Party Digit String Trigger on page 5-51 Specific Called Party Digit String Trigger on page 5-64 Chapter 50Specific Digit String Trigger Features
new feature
Addition of new chapter describing Specific Called Party Digit String Trigger Feature feature

The TDMA Channel Usage Tracking Tool feature provides an AMA module to collect data concerning TDMA channel usage. For more information on this feature, see the Flexible Channel Allocation (FLCA) Optional Feature document, 401-612-238.
Issue 27
May 2004
B-29
401-610-133A
Table B-24 on page B-30 shows changes made to support the TDMA Channel Usage Tracking Tool feature in this document. Table B-24. Changes for TDMA Channel Usage Tracking Tool Feature (Page 1 of 2) Caused... The Channel Usage Module (800) to be added as a valid module to the following structure code layouts:
This Change... TDMA Channel Usage Tracking Tool
In... Chapter 3 Structure Code Layouts
Structure Code x2329 - CellularOriginated Call Without CI Information on page 3-13 Structure Code x2330 - CellularOriginated Call with CI Information on page 3-17 Structure Code x2331 - CellularTerminated Call on page 3-21 Structure Code x2332 - CPS Cellular-Originated Call with CI Information on page 3-24 Structure Code x2333 - CPS Cellular-Originated Call Without CI Information on page 3-28 Structure Code x2334 - CPS Cellular-Terminated Call-Facility and Air-Time Record on page 3-32 Structure Code x2335 - CPS Cellular-Terminated Call-ICT Facility Timing Record on page 3-36 Structure Code x2336 - CN Slave Switch - Facility and Air-Time Record on page 3-39 Structure Code x2337 - CN Handback - Answered Segment Air-Time Record on page 3-42 Structure Code x2338 - CN Handback - Intermediate Segment Air-Time Record on page 3-45 Structure Code x2411 - Feature Activation/Deactivation on page 3-49
B-30
Issue 27
May 2004
Table B-24.
Changes for TDMA Channel Usage Tracking Tool Feature (Page 2 of 2) Caused... The following new AMASE table to be added:
This Change...
In... Chapter 4 AMASE Tables
Table 1000 Channel Usage Information on page 4-113 Chapter 5 Modules
The following new module to be added:
Module 800Channel Usage Module on page 5-75
The following changes to be made:
New module added to Quick Reference Table of AMA Module Definitions on page 5-7 New module added to Module Generation Criteria Table, Table 53 on page 5-13
Chapter 5 Modules
The new module to be added to Table 421 "AMASE Table 88" on page 4-35
Chapter 4 AMASE Tables Chapter 51 TDMA Channel Usage Tracking Tool Feature
new chapter to be written
Enhancement to Far End Release Cause Values in AMA Records

The Enhancement to Far End Release Cause Values in AMA Records (Enhanced FERCV) feature builds upon the Far End Release Cause Value feature by adding the following information to the AMA record for the call:

far end release cause value direction of trunk (incoming or outgoing) on which release cause value is obtained stage (complete or incomplete call)
Issue 27
May 2004
B-31
401-610-133A
Table B-25 on page B-32 shows changes made to support the Enhancement to Far End Release Cause Values in AMA Records feature in this document. Table B-25. Changes for Enhancement to Far End Release Cause Values in AMA Records Feature Caused... Addition of:
90034 = Enhanced Far End Release Cause Code on page 4-40
Addition of:
Chapter 5Modules
Enhanced Far End Release Cause Code (x2118, x2119, x2330 - x2335 and x2339) on page 5-48 Enhancement to Far End Release Cause Values in AMA Records (Enhanced FERCV) on page 5-51 Enhanced FERCV on page 5-52 Enhanced FERCV on page 5-64 Chapter 52Far End Release Cause Values in AMA Records
new feature
Addition of new chapter describing Enhancement to Far End Release Cause Values in AMA Records feature
Documentation Fix for MDCR Feature

In ECP 18.0, when the MDCR feature was introduced, an error was made in a table specification. In Module 992 a reference was made twice to AMASE Table 804 as a four-byte table. The reference was wrong and has been changed. AMASE Table 802 is the actual two-byte table used in the module. This error has been fixed in Table 5-2, Quick Reference Table of AMA Module Definitions.
Documentation Fix for 15 Digit DN Feature

When the pre-15 Digit DN structure code layout numbers in Table 6-1 on page 6-9 were updated for the 15 Digit DN feature, three old structure code layout numbers were overlooked. The error has been fixed in this issue.
B-32
Issue 27
May 2004
In Table 6-1 on page 6-9, under Mobile Terminated Call, structure code layout numbers x0421, 00801, and 00802 have been corrected to x2421, 02801, and 02802, respectively.

The Customized ESN Format in AMA Record feature gives a service provider the ability to change the format in which the mobiles Electronic Serial Number (ESN) is shown in the AMA record for the call. A new Service Feature Code (320) has been created for this feature. For more information on the Customized ESN Format in AMA Record feature, see the Customized ESN Format in AMA Record Optional Feature document, 401612-583. Table B-26 on page B-33 shows changes made to support the Customized ESN Format in AMA Record feature in this document. Table B-26. Customized ESN Format in AMA Record Feature Caused... Addition of:
This Change... New Service Feature Code
320 = Customized ESN Format on page 4-121
new feature
Addition of new chapter describing the Customized ESN Format in AMA Record
Chapter 53 Customized ESN Format in AMA Record
Documentation Fixes for Service Feature Codes

Service feature code 100 stands for Special Cellular Networking. The word Special was inadvertently omitted in previous issues. This error has been fixed in Table 4-70 "AMASE Table 2002" on page 4-119. Also, service feature code 081 was added to the same table. 081, SKT Call Hold (SKTCH) was added to the code in a previous release but was inadvertently omitted from the documentation.
Documentation Fix for Structure Code x2351

Structure code layout x2351 was added to the documentation with the MDCR feature. At that time, structure code layout x2351 was inadvertently omitted from Chapter 6Call Types. Structure code layout x2351 has now been added to Table 6-1 "Call Types and Associated Structure Codes" on page 6-9.
Issue 27
May 2004
B-33
401-610-133A
Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records
The Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records feature (FID 8937.0) provides a way to store local release cause values in the AMA record for a call. For more information about this feature, see the Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records optional feature document, 401-612-592. Table B-27 on page B-34 shows changes made to support the Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records feature in this document. Table B-27. Changes for Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records Feature Caused... Addition of:
90040 = Local Release Cause Code on page 4-40
Addition of:
Chapter 5Modules
Local Release Cause Code (x2118, x2119, x2329 - x2331 and x2351) on page 5-48 Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records on page 5-51 Local Release Cause Value on page 5-52 Local Release Cause Value on page 5-65
Service Feature Code for Unknown Feature Activation/Deactivation

A new service feature code has been added, as a result of AR1-0532431 (Unknown 1111/2411 AMA records and Immediate Billing messages).
B-34
Issue 27
May 2004
Table B-28 on page B-35 shows changes made to add the new service feature code to this document. Table B-28. Changes for New Service Feature Code for Unknown Feature Activation/ Deactivation Caused... Addition of:
816 = Unknown Feature Activation/Deactivation on page 4-121
Issue 27
May 2004
B-35
401-610-133A
Changes for ECP 18.0

Introduction
This ECP 18.0 version of the AMA Formats Description with 15 Digit DN included information about new features for the following releases:

ECP 18.0 SUs that were released since the previous issue of this document
Table
Table B-29 on page B-36 lists AMA-impacting features and gives the page number of the section in this chapter that summarizes the technical changes for the feature. Table B-29. Feature 15 Digit DN - REMINDER Seven-Digit AMA Block Sequence Number Intermediate AMA for LDC Support New SO of 13K Service IS-826 WIN Prepaid Base Cell Origination Request Time Stamps WIN-Based Flexible Alerting Measurement Data in Call Records Documentation Fix for Module 621 User Interactive SMS Documentation Fixes New Information on Storage of MIN and IMSI Table of Contents for Changed Features Section Feature ID 3513.0 4429.1 8193.0 8144 7006.0 8280.0 7044.0 4417.0 NA 4915.0 NA NA Page B-37 B-37 B-38 B-40 B-40 B-41 B-42 B-43 B-43 B-44 B-45 B-45
B-36
Issue 27
May 2004
15 Digit DN - REMINDER
The ECP Release 16.0 15 Digit Directory Number feature expanded mobile directory numbers and called numbers. Mobile directory numbers can now be variable in length up to 14 digits. Called numbers can now be variable in length up to 15 digits. Detailed information about this feature can be found in the 15 Digit DN Feature Description, 401-610-622. All call-related AMA structure code layouts were changed for this feature. Many modules were changed as well. Within RC/V a new key, National Significant Number, was added to the sub, vlr and dn2e forms and 27 screens were changed to accommodate the variable-length directory number. Use of the new 15 Digit DN AMA record structures was optional in ECP 16.0 and ECP 17.0. However, use of the new 15 Digit DN AMA record structures is MANDATORY in ECP 18.0. This document, AMA Formats Description with 15 Digit DN, 401-610-133A, explains all the new 15 Digit DN AMA record structures, which become MANDATORY with ECP 18.0. Wireless Lucent Alert 01-213 reminds service providers about this upcoming change. Fax Flash 00-124a, dated May 15, 2000, gives the original specifications about 15 Digit DN. Changes in this issue for 15 Digit DN are summarized in Appendix EChanges for the 15 Digit DN Feature.

With the increase in call capacity soon to be provided in the Flexent/AUTOPLEX system, one million AMA blocks may not be sufficient to store two days worth of AMA records. The current six-digit AMA block sequence numbers will overflow and begin to overwrite by wrap-around once call capacity approaches or exceeds approximately 500K BHCA. This results in loss of AMA records. To enable service providers to store at least two days worth of backup AMA data even after 700K Busy Hour Call Attempt threshold is reached, this feature increases the valid AMA block sequence number range to seven digits (9,999,999). The 700K Busy Hour Call Attempt feature will be delivered in a later release. The information on Seven Digit AMA Block Sequence Number is included here as advance information.
Issue 27
May 2004
B-37
401-610-133A
Only service providers who have high call capacity in their networks (approximately above 500K BHCA) will require this feature.
Once you start using seven-digit AMA block sequence numbers, DO NOT switch back to six-digit AMA block sequence numbers. Switching back could cause loss of AMA records. Table B-30 on page B-38 shows changes made to support the Seven Digit AMA Block Sequence Number feature in this document. Table B-30. Changes for Seven Digit AMA Block Sequence Number Feature Caused... new section, Ranges with Seven Digit AMA Block Sequence Number Feature on page 4-99 In... Chapter 4AMASE Tables
CAUTION:
This Change... use of formerly unused (padding) digit in Table 804 7-Digit Number on page 4-95 new feature
Addition of new chapter describing Seven Digit AMA Block Sequence Number feature
Chapter 47Seven Digit AMA Block Sequence Number
Intermediate AMA for LDC

The Intermediate AMA for LDC (IAMA for LDC) feature enables service providers to generate intermediate partial Automatic Message Accounting (AMA) billing records for a long duration call at a predefined customer-changeable time interval. The IAMA for LDC feature generates intermediate partial AMA billing records at the expiration of the customer-defined time interval, which can be set to a minimum of 30 minutes and a maximum of 12 hours in 15-minute intervals. The IAMA for LDC feature adds two new event types (for IAMA for LDC originating and terminating calls). For more information on this feature, see the Intermediate AMA for Long Duration Calls Optional Feature Description, 401-612-504.
B-38
Issue 27
May 2004
Table B-31 on page B-39 shows changes made to support the Intermediate AMA for LDC feature in this document. Table B-31. Changes for Intermediate AMA for LDC Feature Caused... Addition of the following in AMASE Table 453, Event Type:
This Change... Two new event types
004 = Intermediate AMA for LDC Origination Event on page 4-60 005 = Intermediate AMA for LDC Termination Event on page 4-60 Chapter 4AMASE Tables
Addition of the following explanatory notes:
Event Time Field as Used by the IAMA for LDC Feature on page 4-20 Event Date Field as Used by the IAMA for LDC Feature on page 4-81 Chapter 3Structure Code Layouts
Names of 02800 and 02801 structure codes changed to reflect more generic usage. New names are:
Origination Event Structure Code (02800) Termination Event Structure Code (02801) Chapter 3Structure Code Layouts
Event Type 004 - IAMA for LDC Origination Event added as a valid event in structure code layout 02800, Origination Event Structure Code, on page 3-57 Event Type 005 - IAMA for LDC Termination Event added as a valid event in structure code layout 02801, Termination Event Structure Code, on page 3-59
Chapter 3Structure Code Layouts
Issue 27
May 2004
B-39
401-610-133A
Support New Service Option of 13K Service

The Support New Service Option of 13K Service feature adds a new industrystandard service option for 13K Voice service for CDMA customers. The new value is 11 (hex) or 17 (decimal). The previous 13K Voice service option of 8000 (hex) or 32768 (decimal) was developed for the Qualcomm proprietary vocoder. Table B-32 on page B-40 shows changes made to support the Support New Service Option of 13K Service feature in this document. Table B-32. Changes for Support New Service Option of 13K Service Feature Caused... Addition of the following in AMASE Table 497 Event Description Values for Event Type 002 on page 4-76:
This Change... One new CDMA Event Description
00017 = 13K Voice (Official Service Option Number assigned by standard body to replace 32768) on page 4-76 Chapter 4AMASE Tables
Note added to explain that the previous CDMA 13K Voice service option was a proprietary number assigned to Qualcomm vocoder:
32768 = 13K Voice (Proprietary Service Option Number assigned to Qualcomm Vocoder) on page 4-76
IS-826 Prepaid Base

The IS-826 Prepaid Base feature sets up standards for allowing subscribers to pay for voice telecommunications service prior to usage.
B-40
Issue 27
May 2004
Table B-33 on page B-41 shows changes made to support the IS-826 Prepaid Base feature in this document. Table B-33. Changes for IS-826 Prepaid Base Feature Caused... Addition of: 90026 = WIN Standard DMH Service ID on page 4-40 Addition of:
Chapter 5Modules
WIN Standard DMH Service ID (x2329, x2330, x2331, x2332, x2333, x2334, and x2335) on page 5-48 IS-826 Prepaid Base on page 5-51 IS-826 Prepaid on page 5-52 IS-826 Prepaid Base Feature on page 5-63 Chapter 48IS-826 Prepaid Base Feature
new feature
Addition of new chapter describing IS826 Prepaid Base feature
Cell Origination Request Time Stamps

The Cell Origination Request Time Stamps feature gives the service provider a way of recording a particular time stamp in the AMA record for the call. The time stamp records the moment at which the MSC receives a seizure request from a cell for a mobile-originated call. The Cell Origination Request Time Stamps feature appends the Automatic Message Accounting (AMA) Digit Information Module (Module 621) into the AMA record to store the time stamp. A new Generic Context Identifier (10860) has been created for this feature. For more information on the Cell Origination Request Time Stamps feature, see the Cell Origination Request Time Stamps Optional Feature document, 401-612528.
Issue 27
May 2004
B-41
401-610-133A
Table B-34 on page B-42 shows changes made to support the Cell Origination Request Time Stamps feature in this document. Table B-34. Cell Origination Request Time Stamps Feature Caused... Addition of:
10860 = Cell Origination Request Time Stamps Indicator on page 4-39
Addition of:
Chapter 5Modules
Cell Origination Request Time Stamps Indicator (for Structure Codes x2329, x2330, x2332, x2333, x2411, x2351) on page 5-47 Cell Origination Request Time Stamps on page 5-51 Cell Origination Request Time Stamps on page 5-63
WIN-Based Flexible Alerting

The WIN-Based Flexible Alerting feature extends the Flexible Alerting feature to the WIN environment. AMA for the WIN-Based Flexible Alerting feature works in exactly the same manner as for the TDMA version of Flexible Alerting, except that there is a different Feature Activation File (FAF). For more information on the WIN-Based Flexible Alerting feature, see the WINBased Flexible Alerting Optional Feature document, 401-612-518. Table B-35 on page B-42 shows changes made to support the WIN-Based Flexible Alerting feature in this document. Table B-35. WIN-Based Flexible Alerting Feature (Page 1 of 2) Caused... Addition of WIN-Based Flexible Alerting information In... Chapter 37Flexible Alerting Feature
This Change... Expansion of Flexible Alerting feature to cover WIN-based applications
B-42
Issue 27
May 2004
Table B-35.
WIN-Based Flexible Alerting Feature (Page 2 of 2) Caused... Explanation about the separate FAF for WIN-Based Flexible Alerting added to the following pages:

This Change...
5-17 5-22 5-56 5-79 5-80
Measurement Data in Call Records

The Measurement Data in Call Records feature gives service providers the opportunity to collect selected call measurement data for every call individually and to store that data in an AMA record. For more information on this feature, see the Measurement Data in Call Records Optional Feature Description, 401-612-510.
Documentation Fix for Module 621

The Digit Information Module with Mobile Identification Number (MIN), that uses generic context ID of 10830, can append to more structure code layouts than was previously listed in this manual. Table B-36 on page B-43 shows changes made to correct this error. Table B-36. Documentation Fix for Module 621 Caused... Changes to:
This Change... Expanded list of complete structure code layouts to which the DIM with MIN can append
the entry for DIM with MIN in Table 5-3, Module Generation Criteria on page 5-17 Chapter 5Modules
Updating of structure code layouts list for 10830 in Table 5-15, Digit Information Module Layout on page 5-47
Issue 27
May 2004
B-43
401-610-133A
Table B-36.
Documentation Fix for Module 621 Caused... Updating of structure code layouts list in Separation of MSID-MDN Feature on page 5-55 Updating of structure code layouts list
This Change...
in Module Generation Criteria for This Feature on page 33-7 in Module Generation Criteria for This Feature on page 33-9
Chapter 33MIN-MDN Separation Feature
NOTE: The DIM with IMSI can append to the same structure code layouts as the DIM with MIN. In one place in the manual (for Generic Context ID 10832 on page 5-47) the list of structure code layouts for the DIM with IMSI was incomplete. That error has been fixed in this version.
User Interactive SMS

The User Interactive SMS feature provides a mobile the ability to set up a special session on a traffic channel to be used for sending and receiving Short Message Service (SMS) messages. A new Service Feature Code (309) has been created for this feature. For more information on the User Interactive SMS feature, see the User Interactive SMS Optional Feature document, 401-612-417. NOTE: The User Interactive SMS feature is available in Release 17.0 and later. Documentation on this feature was inadvertently omitted from the 17.0 version of this document. NOTE: The User Interactive SMS feature is available ONLY with the 15 Digit DN AMA record structures. The User Interactive SMS feature will not work for ECP 17.0 customers who do not have the ecp RC/V field Variable 15 DN Enhanced AMA Recording set to y.
B-44
Issue 27
May 2004
Table B-37 on page B-45 shows changes made to support the User Interactive SMS feature in this document. Table B-37. User Interactive SMS Feature Caused... Addition of:
309 = Voice Channel Only No Land Connection on page 4-121
Documentation Fixes
The following fixes were added to the documentation for ECP 18.0:
Supporting information on 9-track tape drives was removed from Chapter 8, Magnetic Tape Structure and Labels. Nine track tape drives are not supported for ECP 18.0 and later. The definition of PAS was corrected on page E-35. The Module Size field lists number of bytes, not number of BCD characters. This error was corrected on pages 5-44 and 5-49.
New Information on Storage of MIN and IMSI

Added to this document, in Chapter 33MIN-MDN Separation Feature, are some new options for storage of MIN and IMSI. See pages 33-3 through 33-9.
Issue 27
May 2004
B-45
401-610-133A
Changes for ECP 17.0 and ECP 17.1

Introduction
Issue 20 of the AMA Formats Description with 15 Digit DN included information about new features for the following releases:

ECP 17.0 SUs that have been released since December 2000 ECP 17.1 (ECP 17.1 information is included for informational purposes only and is subject to change.)
Table B-38 on page B-46 lists all AMA-impacting features added to this document or to the software product for ECP 17.0 and 17.1 and gives the page number of the section in this chapter that summarizes technical changes made for each feature. Table B-38. Feature AMA Linking Functionality Charge Class Population in AMA R2 and ISUP Charge Indication in AMA TDMA IMSI* Correction Removal of Obsolete Service Feature Code Remote Feature Control Corrections to Timing Indicator Information More Information About Appended Modules Connect Resource Operations SKT PrePaid Service CDMA Network Directed System Selection (NDSS) New Mobile Security Indicator Table of Contents for Changed Features Section Feature ID 5039.0 4854.0 4857.0 3176.0 NA NA 3210.2 NA NA 4508.0 4955.0 4898.0 NA Page B-47 B-48 B-49 B-50 B-51 B-52 B-53 B-54 B-54 B-55 B-58 B-59 B-60
* Documentation for this feature has been in this manual since ECP 15.0. The list of what changes were made for this feature is repeated here in the ECP 17.0 version of this manual to help the user.
B-46
Issue 27
May 2004
AMA Linking Functionality

The AMA Linking Functionality feature provides a unique sequence number (called the Link Sequence Number) to link all of the AMA records that pertain to a single intra-DCS mobile-to-mobile call over ISUP loop around trunks.
This feature is designed to be used only for mobile to mobile intra-DCS calls using ISUP loop-around trunks. The AMA Linking Functionality feature appends the Automatic Message Accounting (AMA) Digit Information Module (Module 621) into the AMA record to store the Link Sequence Number for the call. A new Generic Context Identifier (10843) has been created for this feature. The AMA Linking Functionality feature is available in Release 17.0. For more information on this feature, see the AMA Linking Functionality Optional Feature document, 401-612-409. NOTE: The AMA Linking Functionality feature is available ONLY with the 15 Digit DN AMA record structures. The AMA Linking Functionality feature will not work for ECP 17.0 customers who do not have the ecp RC/V field Variable 15 DN Enhanced AMA Recording set to y. Table B-39 on page B-47 shows changes made to support the AMA Linking Functionality feature in this document. Table B-39. AMA Linking Functionality Feature (Page 1 of 2) Caused... Addition of:
CAUTION:
10843 = AMA Linking Functionality Sequence Number on page 4-39
Issue 27
May 2004
B-47
401-610-133A
Table B-39.
AMA Linking Functionality Feature (Page 2 of 2) Caused... Addition of:
AMA Linking Functionality Sequence Number (for Structure Codes x2329-x2335 and x2351) on page 5-47 AMA Linking Functionality on page 5-51 AMA Linking Functionality on page 5-61
Charge Class Population in AMA

The Charge Class Population in AMA feature gives the service provider a way of recording the charge class of the subscriber in the AMA record for the call. The charge class code tells who is to be charged for the call. The Charge Class Population in AMA feature appends the Automatic Message Accounting (AMA) Digit Information Module (Module 621) into the AMA record to store the charge class for the call. A new Generic Context Identifier (10703) has been created for this feature. The Charge Class Population in AMA feature is available in Release 17.0. For more information on this feature, see the Charge Class Population in AMA Optional Feature document, 401-612-412. NOTE: The Charge Class Population in AMA feature is available ONLY with the 15 Digit DN AMA record structures. The Charge Class Population in AMA feature will not work for ECP 17.0 customers who do not have the ecp RC/V field Variable 15 DN Enhanced AMA Recording set to y. Table B-40 on page B-48 shows changes made to support the Charge Class Population in AMA feature in this document. Table B-40. Charge Class Population in AMA Feature (Page 1 of 2) Caused... Addition of:
10703 = Charge Class on page 4-39
B-48
Issue 27
May 2004
Table B-40.
Charge Class Population in AMA Feature (Page 2 of 2) Caused... Addition of:
Charge Class (for Structure Codes x2411 and x2329 x2335) on page 5-46 Charge Class Population in AMA on page 5-51 Charge Class Population in AMA on page 5-62
R2 and ISUP Charge Indication in AMA

The R2 and ISUP Charge Indication in AMA feature gives the service provider a way of recording the signalling type and a charge indicator in the AMA record for the call. The signaling type (R2 or ISUP) and charge indicator are defined by the service provider. The R2 and ISUP Charge Indication in AMA feature appends the Automatic Message Accounting (AMA) Digit Information Module (Module 621) into the AMA record to store the signaling type and charge indication for the call. A new Generic Context Identifier (10842) has been created for this feature. The R2 and ISUP Charge Indication in AMA feature is available in Release 17.0. For more information on this feature, see the R2 and ISUP Charge Indication in AMA Optional Feature document, 401-612-432. NOTE: The R2 and ISUP Charge Indication in AMA feature is available ONLY with the 15 Digit DN AMA record structures. The R2 and ISUP Charge Indication in AMA feature will not work for ECP 17.0 customers who do not have the ecp RC/V field Variable 15 DN Enhanced AMA Recording set to y.
Issue 27
May 2004
B-49
401-610-133A
Table B-41 on page B-50 shows changes made to support the R2 and ISUP Charge Indication in AMA feature in this document. Table B-41. R2 and ISUP Charge Indication in AMA Feature Caused... Addition of:
10842 = R2 and ISUP Charge Indication in AMA on page 4-39
Addition of:
Chapter 5Modules
R2 and ISUP Charge Indication in AMA (for Structure Codes x2118, x2119, x2329x2330, x2332 and x2333) on page 5-47 R2 and ISUP Charge Indication in AMA on page 5-51 R2 and ISUP Charge Indication in AMA on page 5-63
TDMA IMSI Feature

For information about the TDMA IMSI feature, read Chapter 43, TDMA IMSI Feature in this document or refer to the TDMA International Mobile Station Identity Optional Feature document, 401-612-241.
B-50
Issue 27
May 2004
Table B-42 on page B-51 lists the changes made to this document for this feature.1 Table B-42. Changes for TDMA IMSI Feature Caused... Added the following entries:
This Change... Re-Use of Existing Digit Information Module
The TDMA International Mobile Station Identity (IMSI) feature is active on page 5-18 TDMA IMSI on page 5-50 TDMA IMSI on page 5-58
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (all) new chapter Chapter 43TDMA IMSI Feature
Correction
Table B-43 on page B-51 shows changes made to fix two errors in the document. Table B-43. Correction Caused... Change of Table 26 to Table 2006 in:

This Change... Error correction
Table 3-29 on page 3-49 Table 3-31 on page 3-52
Documentation for this feature has been in this manual since ECP 15.0. However, the software was not available until ECP 17.0. The list of what changes were made for this feature is repeated here in the ECP 17.0 version of this manual to help the user.
Issue 27
May 2004
B-51
401-610-133A
Removal of Obsolete Service Feature Code

The Priority Queuing Service Feature Code (150) is obsolete. Table B-44 on page B-52 shows the changes made to this document to correct this information. Table B-44. Removal of Obsolete Service Feature Code Here... Chapter 4AMASE Tables
This change was made... 150 = Priority Queuing was removed from Table 4-70 on page 4-119
Remote Feature Control Feature Description

The Remote Feature Control feature allows a mobile subscriber to activate or deactivate custom-calling features remotely, from any land or mobile phone. The Remote Feature Control feature uses a new service feature code (319). The Remote Feature Control service feature code is stored in structure code layout 02411 (Feature Activation/Deactivation).
Availability
The Remote Feature Control feature will be available in Release 17.1.
New Record
This feature introduces a new, additional AMA record that is generated at the MSC that first receives the Remote Feature Control call. This AMA record uses call type 308 (Wireless Network Activation/Deactivation) and Service Feature Code 319 (Remote Feature Control). The purpose of the new AMA record is to indicate that a Remote Feature Control call was made. SeeException on page B-52.
Exception
If the incall MSC is also the HLR for the RFC call, and is using 15 Digit DN AMA record structures, then the new, additional AMA record will not appear. Instead, the Service Feature Code of 319 will be placed in a Service Feature Code module attached to the other AMA record for the call.
B-52
Issue 27
May 2004
Definition of Fields for AMA Records with Call Type of 308 and Service Feature Code of 319
For the new AMA record with call type of 308 and Service Feature Code of 319, the two DN fields in the 02411 structure code layout are used as follows:
the Activating/Deactivating Number field contains the mobile directory number (MDN) of the cellular phone for which custom calling features are being activated or deactivated the Billing Number field contains zeroes
The software is designed with the assumption that the first digits dialed by the customer are the MDN of the cellular phone for which custom calling features are being activated or deactivated. If the first digits dialed by the customer are not the MDN of the cellular phone for which custom calling features are being activated or deactivated, inaccurate data will be placed in the Activating/Deactivating Number field in the record.
CAUTION:

For an explanation of the other AMA record generated by this feature, and of what information can be stored in the RFC AMA records for different call scenarios, see the Remote Feature Control Optional Feature document, 401-612-268, for 17.1.
AMA Changes for This Feature

Table B-45 on page B-53 shows changes made to support the Remote Feature Control feature in this document. Table B-45. Remote Feature Control Feature (Page 1 of 2) Here... Chapter 4AMASE Tables
This information was added... 319 = Remote Feature Control on page 4-121 (new service feature code)
Issue 27
May 2004
B-53
401-610-133A
Table B-45.
Remote Feature Control Feature (Page 2 of 2) Here... Chapter 6Call Types
This information was added... Paragraph starting For example, call type 308 with structure code layout x2411 on page 6-7
NOTE:
The call type used for the RFC feature says Wireless Network Activation/Deactivation, not Remote Feature Control. Wireless Network Activation/Deactivation is a call type used for a variety of wireless network special features.
Corrections to Timing Indicator Information

Table B-46 on page B-54 shows the changes made to this document to clarify statements about the Timing Indicator. Table B-46. Pages Changed to Clarify Timing Indicator Information Here... Chapter 4AMASE Tables and Chapter 6Call Types
This information was added... Footnote added on pages 4-123 and 6-7 and sentence added to APX Activation or Deactivation on page 4-139 to explain cases where the Timing Indicator does not differentiate between activation and deactivation.
More Information About Appended Modules

Table B-47 on page B-54 shows the changes made to this document to add information about when modules are typically appended. Table B-47. Pages Changed to Add More Information About Appended Modules Here... Chapter 5Modules
This information was added... When is a Module Typically Appended? on page 5-5 and Multiple Modules Appended to a Structure Code on page 5-5
B-54
Issue 27
May 2004
Connect Resource Operations (Terminations) Overview

The Connect Resource Operations (Terminations) feature changes MSC call processing to allow a set of messages to be sent between the MSC and the SCP during call set up without any impact on the call from the subscribers point of view. These messages set up a call to an Intelligent Peripheral (IP) that handles extra processing for such applications as prepaid service.
How It Works
For a Connect Resource Operations (Terminations) call, two AMA records are generated. Before the subscribers call completes, an additional AMA record is generated. The additional AMA record contains information about the call from the MSC to the IP. Then after the call completes, a standard AMA record is generated for the call. Because the two AMA records are separate and take place at different times, a way of linking the records is needed. The records are linked using a shared Link Sequence Number.
How the AMA Records Are Generated

Figure B-1 on page B-56 shows one of several different Connect Resource scenarios for AMA.
Issue 27
May 2004
B-55
401-610-133A
6 Location Request Return Result (RR)
Disconnect Resource (DISCRES) 5
SCP IP
Connect Resource (CONRES) 3
Location Request (LOCREQ) 2
First Call (First AMA Record)
MSC 1 Incoming Call 1
Second Call (Second AMA Record) 7
MSC 2
Figure B-1.
Generation of Linked AMA Records for a Connect Resource Operations (Terminations) Feature Call
The call goes through the following stages (which are numbered in the figure for ease of reference): 1. The incoming call reaches MSC 1. 2. MSC 1 sends a Location Request message to the SCP. 3. The SCP sends a Connect Resource message back to MSC 1. 4. MSC 1 then connects the incoming party to the IP. 5. The SCP sends a Disconnect Resource message to MSC 1. (This step may not always occur.) After the call ends, an AMA record is generated for the call, with the Service Feature Code field marked as 815. MSC 1 also appends a Digit Information Module (621) containing a Link Sequence Number for this AMA record.
B-56
Issue 27
May 2004
6. The SCP sends a Return Result message to MSC 1. 7. MSC 1 routes the subscribers call to MSC 2. A second AMA record is created for this call by MSC1. MSC1 also creates a Digit Information Module (621) containing the same Link Sequence Number that was used in the first AMA record. The two Digit Information Modules (Module 621) that contain the same Link Sequence Number are used to connect the two AMA records. The shared Link Sequence Number unites the two call records. In this scenario, MSC2 produces an additional AMA record for the call. That record is not linked to the first two AMA records. NOTE: This type of call does not require a second MSC. MSC2 in Figure B-1 on page B-56 could be replaced by MSC1 or by the PSTN.
Availability
The Connect Resource Operations (Terminations) feature will be available in Release 17.1. Information on the AMA changes for this feature is included for informational purposes and may change between now and release of the feature. NOTE: The Connect Resource Operations (Terminations) feature will be available ONLY with the 15 Digit DN AMA record structures. The Connect Resource Operations (Terminations) feature will not work for ECP 17.0 customers who do not have the ecp RC/V field Variable 15 DN Enhanced AMA Recording set to y.

When the Connect Resource Operations (Terminations) feature becomes available, information on this feature will be in the Connect Resource Operations (Terminations) Optional Feature document, 401-612-431.
Issue 27
May 2004
B-57
401-610-133A
Changes to AMA For This Feature

Table B-48 on page B-58 shows changes made to support the Connect Resource Operations (Terminations) feature in this document. Table B-48. Connect Resource Operations (Terminations) Feature Caused... Addition of:
815 = Intelligent Peripheral Trunk, ConnectResource on page 4-121
Addition of:
Chapter 5Modules
Connect Resource Operations (Terminations) on page 5-51 Link Sequence Number and Connect Resource Operations on page 5-62
SKT PrePaid Service

The SKT PrePaid Service feature gives the service provider a way to monitor the amount of pre-paid time left for the subscriber as a call is in progress and to terminate the call if the amount of pre-paid time runs out during the call. A new Service Feature Code (310) has been created for this feature. The 310 Service Feature Code is used in records for SKT PrePaid Service calls for which a Call Return Result (CRR) value is not received from the PPS SCP. NOTE: The SKT PrePaid Service feature will be available in Release 17.1. Information on the AMA changes for this feature is included for informational purposes and may change between now and release of the feature. When the SKT PrePaid Service feature becomes available, information on this feature will be in the SKT PrePaid Service Optional Feature document, 401-612-410. NOTE: The SKT PrePaid Service feature will be available ONLY with the 15 Digit DN AMA record structures. The SKT PrePaid Service feature will not work for ECP 17.0 customers who do not have the ecp RC/V field Variable 15 DN Enhanced AMA Recording set to y.
B-58
Issue 27
May 2004
Table B-49 on page B-59 shows changes made to support the SKT PrePaid Service feature in this document. Table B-49. SKT PrePaid Service Feature Caused... Addition of:
310 = SKT PrePaid Service (PPS) on page 4-121
CDMA Network Directed System Selection (NDSS)

The CDMA Network Directed System Selection feature enables service providers to redirect voice calls from a 3G network to a 2G network for a 2Gpreferred3G mobile, or from a 2G network to a 3G network for a 3Gpreferred3G mobile. If a 2Gpreferred3G mobile or a 3Gpreferred3G mobile originates a high-speed data call (Service Option 33/34), this call will be redirected from a 2G network to an overlaid 3G network. The CDMA Network Directed System Selection feature appends the Automatic Message Accounting (AMA) Digit Information Module (Module 621) into the AMA record to store the Preferred System for the mobile subscriber. A new Generic Context Identifier (10844) has been created for this feature. The CDMA Network Directed System Selection feature is available in a Release 17.0 Software Update. For more information on this feature, see the CDMA Network Directed System Selection Optional Feature document, 401-612-449. Table B-50 on page B-59 shows changes made to support the CDMA Network Directed System Selection feature in this document. Table B-50. CDMA Network Directed System Selection Feature (Page 1 of 2) Caused... Addition of:
10844 = Preferred System Information Indicator on page 4-39
Issue 27
May 2004
B-59
401-610-133A
Table B-50.
CDMA Network Directed System Selection Feature (Page 2 of 2) Caused... Addition of:
CDMA Network Directed System Selection on page 5-51 Preferred System Information (for Structure Codes x2329x2335) on page 5-47 NDSS on page 5-51 CDMA Network Directed System Selection (NDSS) on page 5-62
New Mobile Security Indicator

A new mobile security indicator will be added to AMASE Table 2008. This new indicator, Unknown Call, will replace the AM 759 assert. This change is in response to AR1-0308555/1-0325290. The Unknown Call indicator will be used by the Mobile Security Entry (x2415) structure code layout. This change will be made in an ECP 17.0 SU and will be made retroactive to ECP 16.0. Table B-51 on page B-60 lists the changes to this document to add the new mobile security indicator. Table B-51. Changes for New Mobile Security Indicator Caused... Addition of:
This Change... Addition of new Mobile Security Entry
08 = Unknown Call on page 4-141
B-60
Issue 27
May 2004

Introduction
This section summarizes changes to this document for ECP 16.0, including those made for the 15 Digit DN feature.
15 Digit DN Changes
This version of the AMA Formats Description manual, called the AMA Formats Description with 15 Digit DN, was completely rewritten to reflect the new 15 Digit DN AMA record structures. Almost every chapter was changed. The major changes, however, are in:

Chapter 3, Structure Code Layouts Chapter 4, AMASE Tables Chapter 5, Modules
Summary of Changes
Changes for 15 Digit DN are summarized in Appendix EChanges for the 15 Digit DN Feature.
Other Changes for 16.0

This document also includes information about other new features for the following releases:

ECP 16.0 SUs that have been released since April 2000
Issue 27
May 2004
B-61
401-610-133A
Table B-52 on page B-62 lists all AMA-impacting features that were added to this document or to the software product for ECP 16.0 and gives the page number of the section in this chapter that summarizes technical changes made for that feature. Table B-52. Feature 5ESS DCS Wireless Primary Rate interface for CDMA Dual Mode Mobiles TDMA Circuit-Mode Data Services* IP Billing* TDMA IMSI* CDMA IP Packet Switched Data Table of Contents for Changed Features Section Feature ID 2741.0 2290.0 3561.0 3176.0 3833.0 and 4424.0s 3833.0 5095.0 4528.0 4491.0 4521.0 2290.0 4475.0 Page B-62 B-79 B-80 B-84 B-125
3G-1X Low Speed Packet-Data Service Metered Billing for TDMA Circuit Switch Data Calls Append Module 331 to 1336 AMA Record Far End Release Cause Values for ISUP and R2 in the AMA Record AMA Record Generation for Redirecting Number Information Added to TDMA Chapter Information Added to CDMA Chapter
B-69 B-70 B-71 B-72 B-73 B-74 B-75
* Documentation for these features has been in this manual since ECP 15.0. However, the software was not available until later. Documentation for this feature has been in this manual since ECP 13.0. However, the software was not available until later.
5ESS Switch Wireless PRI for CDMA Dual Mode Mobiles

The 5ESS Switch Wireless Primary Rate Interface for CDMA Dual Mode Mobiles feature is available in ECP release 16.0 and later. The 5ESS Switch Primary Rate Interface for CDMA Dual Mode Mobiles feature provides a category code with an incoming call. This information gives Service Providers the ability to distinguish PRI calls from other types of calls.
B-62
Issue 27
May 2004
Table B-53 on page B-63 lists the technical changes made to this document for this feature. Table B-53. Technical Changes for 5ESS Switch Wireless Primary Rate Interface for CDMA Dual Mode Mobiles Feature Caused.... In...
This Change... Addition of New Signalling Type
Addition of 3 = PRI/PRA (Primary Rate Chapter 4AMASE Tables Interface/Primary Rate Access) on page 4-79 in Table 4-49, AMASE Table 566 Addition of PRI code into Table 4-73, AMASE Table 2004 Addition of 5ESS DCS Wireless Primary Rate interface for CDMA Dual Mode Mobiles on page 5-70 Addition of Primary Rate Interface Feature on page 5-72 new chapter to be written Chapter 4AMASE Tables Chapter 5Modules
Chapter 5Modules Chapter 46Primary Rate Interface Feature

The TDMA Circuit-Mode Data Services feature provides a subscriber having the appropriate mobile station configuration the ability to communicate with existing asynchronous modems and group-3 facsimile machines using the TDMA air interface. NOTE: This information was released in Issue 14 of this manual. This information was reprinted here because the TDMA Circuit-Mode Data Services feature was available with ECP 16.0. For more information about this feature, read the TDMA Circuit-Mode Data Services Optional Feature, 401-612-211. Table B-54 on page B-64 lists the technical changes made to this document for this feature.
Issue 27
May 2004
B-63
401-610-133A
NOTE: New information was added to this section for ECP 16.0. Table B-54. Technical Changes for TDMA Circuit-Mode Data Services Feature Caused... Addition of the following new TDMA event type in Table 4-37 on page 4-60:
This Change... one new Event Type
012 = Initial Assigned TDMA Data Service Configuration Chapter 4AMASE Tables
redefinition of AMASE Table 497, Event Description, for the new Event Type Re-Use of Existing Data Module
Creation of Table 4-48 on page 4-77
Addition of TDMA CircuitMode Data Services feature is active on page 5-16 (in Feature Activation/Control Column of table) Information for this feature to be added to Module 621 Digit Information Module on page 5-46
Chapter 5Modules
(all)
Chapter 40TDMA Circuit-Mode Data Services Feature
NOTE:
For ECP 16.0, clarifying information was added. The Terminating Number field can have different information stored in the field, depending on which features are active. on page 40-16.
IP Billing Feature
The TDMA IP Billing feature gives a Service Provider the ability to bill Direct Internet Access mobile-originated TDMA circuit-mode data calls.
B-64
Issue 27
May 2004
NOTE: This information was released in Issue 14 of this manual. This information was reprinted here because the IP Billing feature was available with ECP 16.0. No AMA code changes were made since ECP 15.0 for this feature. For more information about this feature, read the TDMA Circuit-Mode Data Services Optional Feature, 401-612-211. Table B-55 on page B-65 lists the technical changes made to this document for this feature. NOTE: New information was added to this section for ECP 16.0. Table B-55. Technical Changes for IP Billing Feature (Page 1 of 2) Caused... Addition of the following in Table 4-24, AMASE Table 237:
This Change... New Generic Context Identifier
90011 = TDMA Direct Internet Access on page 4-40 Chapter 4AMASE Tables
New Event Description field service code value
Addition of the service code
2 = Direct Internet Access on page 4-77
in Table 4-48, AMASE Table 497 Event Description Values for Event Type 012 Re-Use of Existing Digit Information Module The following information for this feature to be added to the section for Module 621 - Digit Information Module:

Chapter 5Modules
90011 on page 5-47 IP Billing on page 5-50 Direct Internet Access Number on page 5-54
Issue 27
May 2004
B-65
401-610-133A
Table B-55.
Technical Changes for IP Billing Feature (Page 2 of 2) Caused... The following note and the information listed under it to be added on page 40-16: The Terminating Number field can have different information stored in the field, depending on which features are active. new chapter to be written Chapter 44IP Billing Feature In... Chapter 40TDMA Circuit-Mode Data Services Feature
This Change... (all)
TDMA IMSI Feature

For information about the TDMA IMSI feature, read Chapter 43, TDMA IMSI Feature in this document or refer to the TDMA International Mobile Station Identity Optional Feature document, 401-612-241. Table B-56 on page B-66 lists the technical changes made to this document for this feature. Table B-56. Technical Changes for TDMA IMSI Feature Caused... Added the following entries:
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. Information for the TDMA IMSI feature is now in Module 621. See Module 621 - Digit Information Module on page 5-46. (all) new chapter Chapter 43TDMA IMSI Feature
B-66
Issue 27
May 2004
CDMA IP Packet Switched Data

The CDMA IP Packet Switched Data feature provides a subscriber having the appropriate mobile station configuration the ability to transmit and receive bursts of data over a packet data network via the CDMA air interface. This provides the infrastructure for mobile users with laptop computers or other data devices conforming to the TIA/EIA/IS-657 or TIA/EIA/IS-707 standard to access various data applications, such as e-mail, file transfer, field service automation, and fleet dispatch. Table B-57 on page B-67 lists the technical changes made to this document for this feature. Table B-57. Technical Changes for CDMA IP Packet Switched Data (Page 1 of 2) Caused... Addition of an entry for MobileOriginated Packet Data Call in Table 6-1, Call Types and Associated Structure Codes on page 6-9 Addition of an entry for MobileTerminated Packet Data Call in Table 6-1, Call Types and Associated Structure Codes on page 6-9 Added mention of call type 450 to the following structure codes:

This Change... Two New Call Types
In... Chapter 6Call Types
Chapter 6Call Types
x2329 on page 3-13 x2333 on page 3-28 Chapter 3Structure Code Layouts
Added mention of call type 451 to the following structure codes:

x2331 on page 3-21 x2334 on page 3-32 Chapter 4AMASE Tables
Two New Event Types
Two new Event Types in Table 4-37, AMASE Table 453 on page 4-60:
010 = Packet Data Link Layer Connection Open 011 = Packet Data Link Layer Connection Reactivation
Issue 27
May 2004
B-67
401-610-133A
Table B-57.
Technical Changes for CDMA IP Packet Switched Data (Page 2 of 2) Caused... Definition of the first BCD character in Table 4-39, AMASE Table 471 for values 0-5 on page 4-62 CDMA Packet-Mode Data Services feature information to be added to the section Module 344Data Module on page 5-38 CDMA Packet-Mode Data Services feature information to be added to the section Module 334Digital Event Module on page 5-34 Addition of new Event Descriptions in Table 4-47, AMASE Table 497 Event Description Values for Event Types 010 and 011 on page 4-77:
This Change... Redefinition of part of Technology Type Field Re-Use of Existing Data Module
In... Chapter 4AMASE Tables Chapter 5Modules
Re-Use of Existing Digital Event Module
Chapter 5Modules
New Event Descriptions
Chapter 4AMASE Tables
00007 = 9.6K IP Service (9.6 Kbps IP Revision 0) 00008 = 9.6K CDPD Service (9.6 Kbps CDPD Revision 0) 00015 = 14.4K IP Service (14.4 Kbps IP Revision 0) 00016 = 14.4K CDPD Service (14.4 Kbps CDPD Revision 0) 04103 = 9.6K IP Service, Version 1 (9.6 Kbps IP Revision 1) 04104 = 9.6K CDPD Service, Version 1 (9.6 Kbps CDPD Revision 1) Chapter 34CDMA Packet-Mode Data Services Features
(all)
new chapter
3G-1X Low Speed Packet Data Service

The 3G-1X Low Speed Packet Data Service feature gives a subscriber having the appropriate mobile station configuration the ability to transmit and receive bursts of data at high speeds over a packet data network via the CDMA air interface, using the 3G-1X platforms.
B-68
Issue 27
May 2004
Table B-58 on page B-69 lists the technical changes made to this document for this feature. Table B-58. Technical Changes for 3G-1X Low Speed Packet Data Service Feature Caused... Addition of two new Event Descriptions in Table 4-47, AMASE Table 497 Event Description Values for Event Types 010 and 011 on page 4-77:

This Change... Two New Event Descriptions
00033 = 3G-1X IP Service 00034 = 3G-1X CDPD Service Chapter 34CDMA Packet-Mode Data Services Features Chapter 34CDMA Packet-Mode Data Services Features
Changes to allow suppression of duplicate AMA records (all)
new section, Suppressing Data Collection Records on page 34-11
revision to existing chapter
Metered Billing for TDMA Circuit Switch Data Calls Feature

The Metered Billing for TDMA Circuit Switch Data Calls feature makes it possible for Metered Billing to be used for data calls.
Issue 27
May 2004
B-69
401-610-133A
Table B-59 on page B-70 shows changes made to support this feature in this document. Table B-59. Metered Billing for TDMA Circuit Switch Data Calls Feature Caused... The Call Types for Mobile-Originated Circuit Data Call (059) and MobileOriginated Packet Data Call (450) to be added to:
This Change... Addition of call types for data calls to Metered Billing structure code layouts
Structure Code 02800 Origination Event on page 3-56 Structure Code 02802 Metered Billing on page 3-60
NOTE:
The Mobile-Originated Packet Data Call Type was added to AMA for future reference. It is not needed for this feature. The Call Types for Mobile-Terminated Circuit Data Call (053) and MobileTerminated Packet Data Call (451) to be added to:
Structure Code 02801 Termination Event on page 3-58 Structure Code 02802 Metered Billing on page 3-60
NOTE:
The Mobile-Terminated Packet Data Call Type was added to AMA for future reference. It is not needed for this feature. Addition of sentence Metered Billing is available for data calls as well as for voice calls. on page 27-2. Chapter 27Metered Billing Feature
B-70
Issue 27
May 2004
Append Module 331 to 1336 AMA Record

The Append Module 331 to 1336 AMA Record feature makes it possible for Calling Party Number (CPN) information to be attached to the 2336 structure code layout. This provides Calling Party Number information for mobile terminations to roamers using CN call delivery. Before this feature existed, CPN information was only attached to the 2335 AMA record. AMA work to support this feature is complete and is described in this manual. However, the Append Module 331 to 1336 AMA Record feature will be made generally available at a later date. After the Append Module 331 to 1336 AMA Record feature is released, the Append Module 331 to 1336 AMA Record Optional Feature document, 401-612-354, will be available to further describe this feature. NOTE: In ECP 16.0 in the 15 Digit DN AMA record structures2, structure code layout x1336 was changed to x2336. The 1336 in the title and in the above description has been left because that is the name of the feature. However, please be aware that the structure code layout number has changed to 2336 in this document for ECP Release 16.0 and later. Table B-60 on page B-71 shows changes made to support the Append Module 331 to 1336 AMA Record feature in this document. Table B-60. Append Module 331 to 1336 AMA Record Feature Caused... Addition of:
This Change... Addition of Module 331 as a valid module for structure code layout x2336 New feature
331 on page 3-41
Addition of:

Chapter 5Modules
section 331 on page 5-15 Append Module 331 to 2336 AMA Record on page 5-30
These structures are optional for ECP 16.0. See 401-610-133A, AMA Formats
Description with 15 Digit DN.
Issue 27
May 2004
B-71
401-610-133A
FERCV
The Far End Release Cause Values for ISUP and R2 in the AMA Record feature makes it possible for Far End Release Cause values received from the Digital Cellular Switch (DCS) to be placed in the AMA record. If ISUP signaling is used, the following types of calls are recorded: mobile originations, mobile terminations, three-way calls, call forwarding, tandem and special routing calls. If R2 signaling is used, the following mobile-originated calls are recorded: mobile originations, three-way calls, call forwarding tandem and special routing calls. This feature appends the Automatic Message Accounting (AMA) Digit Information Module (Module 621) into the AMA record for both mobile originated and terminated calls. A new Generic Context Identifier (90013) has been created for this feature. AMA work to support this feature is complete and is described in this manual. However, the Far End Release Cause Values for ISUP and R2 in the AMA Record feature will be released at a later date. When the Far End Release Cause Values for ISUP and R2 in the AMA Record feature is released, the Far End Release Cause Values for ISUP and R2 in the AMA Record Optional Feature document, 401-612-343, will be available to further describe this feature. Table B-61 on page B-72 shows changes made to support the Far End Release Cause Values for ISUP and R2 in the AMA Record feature in this document. Table B-61. Far End Release Cause Values for ISUP and R2 in the AMA Record Feature (Page 1 of 2) Caused... Addition of:
90013 = Far End Release Cause Value Indicator on page 4-40
B-72
Issue 27
May 2004
Table B-61.
Far End Release Cause Values for ISUP and R2 in the AMA Record Feature (Page 2 of 2) Caused... Addition of:
Far End Release Cause Value Indicator (for structure codes x2118, x2119, and x2329 x2335) on page 5-47 About The Far End Release Cause Value Indicator on page 5-49 Far End Release Cause Values for ISUP and R2 in the AMA Record on page 5-51 FERCV on page 5-61
AMA Record Generation for Redirecting Number

The AMA Record Generation for Redirecting Number feature allows the service provider to bill for the second leg of a forwarded call by appending the Redirecting Party Number (RDPN) information for the call to an AMA record. The RDPN can be a number of up to twenty digits in length. The AMA Record Generation for Redirecting Number feature stores the RDPN in the Digit Information Module. A new Generic Context Identifier (10835) has been created for this feature. See the AMA Record Generation for Redirecting Number Optional Feature document, 401-612-343, for further information about this feature. Table B-62 on page B-73 shows the changes made to support the AMA Record Generation for Redirecting Number feature in this document. Table B-62. AMA Record Generation for Redirecting Number Feature (Page 1 of 2) Caused... Addition of:
10835 = Redirecting Party Number on page 4-39
Issue 27
May 2004
B-73
401-610-133A
Table B-62.
AMA Record Generation for Redirecting Number Feature (Page 2 of 2) Caused... Addition of:
This Change... Use of Digit Information Module to store RPDN
Redirecting Party Number (for Structure Codes x2118, x2119, and x2329-x2335) on page 5-47 (as a valid Generic Context ID for the Digit Information Module) AMA Record Generation for Redirecting Number on page 5-51 (as a feature that uses the Digit Information Module) AMA Record Generation for Redirecting Number on page 5-61
Information Added to TDMA Chapter

Chapter 40TDMA Circuit-Mode Data Services Feature was rewritten to remove redundant information and to help the user understand this feature. No new AMA functionality was added Table B-63 on page B-74 summarizes the changes made. Table B-63. TDMA Circuit-Mode Data Services Chapter Here... In the sections:
This information was added... a description of which AMA records would appear at certain points in a TDMA CircuitMode Data Services call, and which structure code layout numbers would be associated with these records.
How the Legs Are Set Up During Call Origination on page 40-4 PDP Leg Can Also Activate/ Deactivate Features on page 40-5, and Setup Scenario for the MDP and the PDP During an Incoming Call on page 40-5
the section Records for Which These Call Types Sometimes Apply
on page 40-7
B-74
Issue 27
May 2004
Information Added to CDMA Chapter

Chapter 25CDMA Circuit-Mode Data Services Feature was rewritten to remove redundant information and to help the user understand this feature. No new AMA functionality was added Table B-64 on page B-75 summarizes the changes made. Table B-64. CDMA Circuit-Mode Data Services Chapter Here... In the sections:
This information was added... a description of which AMA records would appear at certain points in a CDMA CircuitMode Data Services call, and which structure code layout numbers would be associated with these records.
How the Legs Are Set Up on page 25-4 PDP Leg Can Also Activate/ Deactivate Features on page 25-5, and Setup Scenario for the MDP and the PDP on page 25-5
the section Records for Which These Call Types Sometimes Apply
on page 25-9
Issue 27
May 2004
B-75
401-610-133A

Introduction
This document was reissued for ECP 15.0 to include information about features for the following releases:

ECP 15.0 SUs that were released since September 1999
Table B-65 on page B-76 lists all AMA-impacting features that were added to this document since September 1999 and gives the page number of the section in this chapter that summarizes changes made for that feature. Table B-65. Feature ANSI-41 Billing Module With Service Type Correction Regarding an Earlier Feature CDMA Full IMSI Changeable No Answer Timer TDMA Circuit-Mode Data IP Billing CDMA Meter Pulse TSI Bridging LAES TDMA IMSI Increase AMA Record Storage with DAT CDMA Circuit IP Services Improvements Not Related to a Feature Table of Contents for Changed Features Section Feature ID 3558.1 NA 2034.0 4191.0 2290.0 3561.0 3508.1 3702.1 3055.3 3176.0 4181.0 4475.0 NA B-89 B-78 B-79 B-80 B-81 B-82 B-83 B-84 B-85 B-85 B-86 Page B-77
B-76
Issue 27
May 2004
ANSI-41 Billing Module with Service Type

The ANSI-41 Billing Module with Service Type feature is built upon the ANSI-41 Billing Module feature, which was described in the ECP 13.0 version of this document. See ANSI-41 Billing Module on page B-128 for a description of the ANSI-41 Billing Module feature. The ANSI-41 Billing Module with Service Type feature adds a new ANSI-41 billing parameter (Service ID) to the ANSI-41 billing parameters previously available with the ANSI-41 Billing Module feature. The ANSI-41 standard uses the term Service ID in section 6.5.2.59 in the TIA/ EIA-41-D Standard for Cellular Radio Telecommunications Intersystem Operations. Thus, Service ID is the official name for this parameter. However, in the feature, the parameter is called Service Type. In this documentation, Service Type will be used when referring to the name of the feature, and Service ID will be used for the parameter itself. Both terms refer to the same parameter. For more about the ANSI-41 Billing Module with Service Type feature, read Chapter 38, ANSI-41 Billing Module and ANSI-41 Billing Module with Service Type Features in this document or refer to the ANSI-41 Billing Module and ANSI41 Billing Module with Service Type Optional Feature document, 401-612-216. Table B-66 on page B-78 lists the changes made to this document for this feature.
Issue 27
May 2004
B-77
401-610-133A
Table B-66.
Changes for ANSI-41 Billing Module With Service Type Feature Caused... Addition of the following new generic context identifiers to Table 4-24 on page 4-39:
This Change... One New Generic Context Identifier
90009 = Service ID Chapter 5Modules
Re-Use of Existing Digit Information Module 611
Added the following entries:
Turn on the Service ID on page 5-17 90009 on page 5-47 ANSI-41 Billing Module with Service Type on page 5-50 ANSI-41 Billing Module Feature and Account Code Digits on page 5-57
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (both) rewriting of chapter Chapter 38ANSI-41 Billing Module and ANSI-41 Billing Module with Service Type Features
Changeable No Answer Timer

The Changeable No Answer Timer (CNAT) feature allows the service provider to specify a timer value, to clear the call if no answer is received on an outgoing call set up over network interface trunks. For more about the Changeable No Answer Timer feature, read the Changeable No Answer Timer Optional Feature document, 401-612-296, Issue 1.
B-78
Issue 27
May 2004
Table B-67 on page B-79 lists the changes made to this document for this feature. Table B-67. Changes for Changeable No Answer Timer Feature Caused... Addition of the following new Timing Indicator value in AMASE Table 7, BCD character 1 (Table 4-11 on page 4-15) for calls released upon expiration of the answer timer:
This Change... One New Timing Indicator value
4 = Unanswered Call Release Chapter 4AMASE Tables
new section on page 4-16:
Unanswered Call Release

The TDMA Circuit-Mode Data Services feature provides a subscriber having the appropriate mobile station configuration the ability to communicate with existing asynchronous modems and group-3 facsimile machines using the TDMA air interface. For more information about this feature, read the TDMA Circuit-Mode Data Services Optional Feature document, 401-612-211. Table B-68 on page B-79 lists the changes made to this document for this feature. Table B-68. Changes for TDMA Circuit-Mode Data Services Feature (Page 1 of 2) Caused... Addition of the following new TDMA event type in Table 4-37 on page 4-60:
This Change... one new Event Type
012 = Initial Assigned TDMA Data Service Configuration Chapter 4AMASE Tables
redefinition of AMASE Table 497, Event Description, for the new Event Type
Creation of Table 4-48 on page 4-77
Issue 27
May 2004
B-79
401-610-133A
Table B-68.
Changes for TDMA Circuit-Mode Data Services Feature (Page 2 of 2) Caused...
This Change... Re-Use of Existing Data Module
Addition of TDMA CircuitMode Data Services feature is active on page 5-16 (in Feature Activation/Control Column of table) Information for this feature to be added to Module 344 Data Module on page 5-38
(all)
Chapter 40TDMA Circuit-Mode Data Services Feature
IP Billing Feature
The TDMA IP Billing feature gives a service provider the ability to bill direct internet access mobile-originated TDMA circuit-mode data calls. For more information about this feature, read the TDMA Circuit-Mode Data Services Optional Feature document, 401-612-211. Table B-69 on page B-80 lists the changes made to this document for this feature. Table B-69. Changes for IP Billing Feature (Page 1 of 2) Caused... Addition of the service code
This Change... New Event Description field service code value
2 = Direct Internet Access on page 4-77
in Table 4-48, AMASE Table 497 Event Description Values for Event Type 012
B-80
Issue 27
May 2004
Table B-69.
Changes for IP Billing Feature (Page 2 of 2) Caused... The following information for this feature to be added to the section for Module 621 - Digit Information Module:

IP Billing on page 5-50 Direct Internet Access Number on page 5-54
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (all) The following note and the information listed under it to be added on page 40-16: The Terminating Number field can have different information stored in the field, depending on which features are active. (all) new chapter to be written Chapter 44IP Billing Feature Chapter 40TDMA Circuit-Mode Data Services Feature
CDMA Meter Pulse

The CDMA Meter Pulse feature gives the Service Provider the ability to offer flexible centralized control of wireless pay phone end user billing. The pay phone provider is billed via existing AMA methods. This feature is an originating call feature only. This feature uses two new call types. The CDMA Meter Pulse feature is available in ECP Release 15.0 and all later releases. For more information about this feature, read the Meter Pulse Optional Feature document, 401-612-320.
Issue 27
May 2004
B-81
401-610-133A
Table B-70 on page B-82 lists the changes made to this document for this feature. Table B-70. Changes for CDMA Meter Pulse Feature Caused... In...
Addition of 700 and 701 as valid call Chapter 3Structure types in the following structure codes: Code Layouts

x2329 on page 3-13 x2330 on page 3-19 x2332 on page 3-24 x2333 on page 3-28 Chapter 4AMASE Tables
Addition of the following in Table 4-5, AMASE Table 1:

Local Coin Call on page 4-8 Toll Coin Call on page 4-8 Chapter 6Call Types
Addition of:
Local Coin Call (Call Type 700) on page 6-8 Toll Coin Call (Call Type 701) on page 6-8
Addition of in the following in Table 6-1, Chapter 6Call Types Call Types and Associated Structure Codes:

Local Coin Call on page 6-15 Toll Coin Call on page 6-15

For information about the TSI Bridging feature, read Chapter 41, TSI Bridging Feature in this document or refer to the Lawfully Authorized Electronic Surveillance (LAES) for CALEA Optional Feature document, 401-612-209. Table B-71 on page B-82 lists the changes made to this document for this feature. Table B-71. Changes for TSI Bridging Feature (Page 1 of 2) Caused... New value in Table 4-62 on page 4-103:
This Change... A new value for the Trunk Direction field
3 - TSI Bridging
B-82
Issue 27
May 2004
Table B-71.
Changes for TSI Bridging Feature (Page 2 of 2) Caused... Added the following entries:
This Change... Re-Use of Existing Trunk Information Module
TSI Bridging feature is active on page 5-21 TSI Bridging on page 5-70 TSI Bridging Feature on page 5-71 Chapter 41TSI Bridging Feature
(both)
new chapter
LAES Feature
For information about the LAES feature, read Chapter 42, LAES Feature in this document or refer to the Lawfully Authorized Electronic Surveillance (LAES) for CALEA Optional Feature document, 401-612-209. Table B-72 on page B-83 lists the changes made to this document for this feature. Table B-72. Changes to LAES Feature Caused... NOTE: In ECP 16.0 the LAES code was moved into the Service Feature Code table. See 306 in Table 4-70 on page 4-119. New values in Table 4-62 on page 4-103:

This Change... Use of existing special routing code for LAES
Two new values for the Trunk Direction field
6 - LAES Primary 7 - LAES Secondary Chapter 5Modules
Re-Use of Existing Trunk Information Module
Lawfully Authorized Electronic Surveillance (LAES) feature is active on page 5-21 LAES on page 5-70 LAES Feature on page 5-71 Chapter 42LAES Feature
(all)
new chapter
Issue 27
May 2004
B-83
401-610-133A
TDMA IMSI Feature

For information about the TDMA IMSI feature, read Chapter 43, TDMA IMSI Feature in this document or refer to the TDMA International Mobile Station Identity Optional Feature document, 401-612-241. Table B-73 on page B-84 lists the changes made to this document for this feature. Table B-73. Changes for TDMA IMSI Feature Caused... Added the following entries:
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (all) new chapter Chapter 43TDMA IMSI Feature
Increase AMA Record Storage with DAT Feature

The Increase AMA Record Storage with DAT feature gives a service provider the ability to put 600,000 blocks of AMA data on a single DAT tape. For information about the Increase AMA Record Storage with DAT feature, refer to the Increase AMA Record Storage with DAT Optional Feature document, 401612-329.
B-84
Issue 27
May 2004
Table B-74 on page B-85 lists the changes made to this document for this feature. Table B-74. Changes for Increase AMA Record Storage with DAT Feature Caused... Revision of the following sections:
This Change... Feature added that allows Service Provider to write 15 times as many AMA data blocks on a DAT tape
In... Chapter 8Magnetic Tape Structure and Labels
About Digital Audio Tapes on page 8-40 About Digital Audio Tapes on page 8-40 About Digital Audio Tapes on page 8-40
Two new sections:
Traditional Storage on DAT Tape on page 8-41 Increased Storage on DAT Tape on page 8-43
Chapter 8Magnetic Tape Structure and Labels
CDMA Circuit IP Services

For the CDMA Circuit IP Services feature, the CDMA Circuit IP Services Indicator is recorded in Module 621 (Digit Information Module), with new Context ID 90025. This module can be appended optionally to AMA records with structure codes x2329 and x2333. The CDMA Circuit IP Services feature is used to identify Internet calls for billing purposes. For more information about the CDMA Circuit IP Services feature, read the CDMA Circuit IP Services optional feature document, 401-612-347.
Issue 27
May 2004
B-85
401-610-133A
Table B-75 on page B-86 lists the changes made to this document for this feature. Table B-75. CDMA Circuit IP Services Caused... Addition of the following new context identifier to Table 4-24 on page 4-39:
This Change... One New Context Identifier
= 90025 = CDMA Circuit IP Services on page 4-40 Chapter 5Modules
Re-Use of Existing Digit Information Module
Turn on the CDMA Circuit IP Services AMA field on page 5-17 CDMA Circuit IP Services Indicator (x2329, x2333) on page 5-48 CDMA Circuit IP Services on page 5-50 CDMA Circuit IP Services on page 5-60 Chapter 45CDMA Circuit IP Services Feature
(all)
Improvements Not Related to a Feature

In this issue, AMASE Table 497 was broken apart to show more clearly the differences between the Event Descriptions for varying Event Types. Table B-76 on page B-86 shows the new table created for Event Types 010 and 0-11. Table B-76. Improvements in AMASE Table 497 (Page 1 of 2) Caused... Creation of Table 4-48 on page 4-77 (described previously in this section under TDMA Circuit-Mode Data Services Feature on page B-79) In... Chapter 4AMASE Tables
This Change... Addition of TDMA Event Type 012
B-86
Issue 27
May 2004
Table B-76.
Improvements in AMASE Table 497 (Page 2 of 2) Caused... Creation of Table 4-47 on page 4-77 In... Chapter 4AMASE Tables
This Change... Splitting Apart of Event Descriptions for Event Types 010 and 011
Also in this issue, a missing CN Special Routing code was added to the documentation. Table B-77 on page B-87 shows the change. Table B-77. Missing Information Added in AMASE Table 365 Caused... Addition of 014 = CN Special Routing Feature #3 in Table 364, Special Routing Feature Indicator. In... Chapter 4AMASE Tables
This Change... Addition of CN Special Routing Feature 3 to documentation (this was already in the code)
NOTE:
Table 364, Special Routing Feature Indicator has been deleted and its contents merged with Table 2002. CN Special Routing Feature #3 is now replaced by the values 100 and 003 in Table 4-70, AMASE Table 2002.
Issue 27
May 2004
B-87
401-610-133A

Introduction
Issue 14 of this document included information about features for the following releases:

CDMA 13.0 ECP 14.0 SUs that were released between January 1999 and September 1999
Table B-78 on page B-88 lists all AMA-impacting features that were added to Issue 14 of this document and gives the page number of the section in this appendix that summarizes changes made for that feature.
About the 14.1 Re-Release of This Document

This document was re-released for CDMA Release 14.1 to include new information for that release. The items highlighted in bold in the section called Analog Fax Support for CDMA in this Reason for Reissue section point to the new information for CDMA Release 14.1. Table B-78. Feature Calling Name Presentation for TDMA, Phase 2 CDMA Full International Mobile Station Identity (IMSI) Incoming Call Dialed Digits in AMA Record ANSI-41 Rev C Call Transfer Circuit Data IWF Indicator in AMA IS53 Preferred Language Analog Fax for CDMA Mobile Inactive Trigger AUTOPLEX AMA Tape IBM Label Y2K Compliance Technical Changes Not Related to a Feature CAROD KC02196 Changed Pages Per Feature Feature ID 2896.1 2034.0 3711.0 3710.0 3873.0 2730.1 3606.0 3942.0 4161.0 N/A N/A Page B-89 B-89 B-90 B-91 B-92 B-93 B-94 B-95 B-98 B-98 B-99
B-88
Issue 27
May 2004
Calling Name Presentation for TDMA Feature, Phase 2

The Calling Name Presentation for TDMA feature, Phase 2, expanded the existing TDMA Calling Name Presentation feature. Phase 2 of this feature was available with ECP 14.0. Table B-79 on page B-89 lists the changes made to this document for this feature. Table B-79. Changes for Calling Name Presentation for TDMA Feature, Phase 2 Caused... Addition of the following fields to Table 4-44, AMASE Table 476 in Chapter 4AMASE Tables:
This Change... Addition of Per-Call Calling Name Enable and Restriction Usage
5 = Per-Call Calling Party Number and Calling Party Name Restriction Used on page 4-71 6 = Per-Call Calling Party Number and Calling Party Name Enable Used on page 4-71 7 = Per-Call Calling Party Name Toggle Used on page 4-71 9 = Unknown on page 4-71 Chapter 5Modules
documentation fix
Revision of section Module 980 Calling Name Outgoing Calls on page 5-85 revision of existing chapter
(all)
Chapter 32Calling Name Presentation and Restriction Feature
CDMA Full IMSI

The IMSI is an international mobile station identity designed to be used in TDMA and CDMA systems. The CDMA Full IMSI feature allows a CDMA mobile to access the system and to be addressed using a full IMSI.
Issue 27
May 2004
B-89
401-610-133A
Table B-80 on page B-90 lists the changes made to this document for this feature. Table B-80. Changes for CDMA Full IMSI Feature Caused... Addition of the section 10832 = E.212 International Mobile System Identity on page 4-39 in Table 4-24, AMASE Table 237 Addition of the following:
This Change... Addition of a new generic context identifier Use of the DIM module to store CDMA Full IMSI information
Chapter 5Modules
section "The CDMA Full International Mobile Station Identity (IMSI) feature is active" on page 5-18 Chapter 5Modules
Editing of the section Module 621 Digit Information Module on page 5-46 to add information for this feature. (all) new chapter
Chapter 39CDMA Full IMSI Feature
Incoming Call Dialed Digits in AMA Record

The Incoming Call Dialed Digits in AMA Record feature captures the exact digit string that the cellular subscriber received with an incoming call. With this feature, the exact received digits are placed in the AMA record for the call. For more about this feature, read the Incoming Call Dialed Digits in AMA Record Optional Feature document, 401-612-243. Table B-81 on page B-90 lists the changes made to this document for this feature. Table B-81. Changes for Incoming Call Dialed Digits in AMA Record Feature (Page 1 of 2) Caused... Addition of the section 90010 = Incoming Called Digits on page 4-40 in Table 4-24, AMASE Table 237 In... Chapter 4AMASE Tables
This Change... Addition of a new generic context identifier
B-90
Issue 27
May 2004
Table B-81.
Changes for Incoming Call Dialed Digits in AMA Record Feature (Page 2 of 2) Caused... Addition of the following:
This Change... Use of the DIM module to store Incoming Call Dialed Digit information
The Incoming Called Digits in AMA feature is active. on page 5-18 Chapter 5Modules
Addition of the following:
Incoming Call Dialed Digits in AMA Record on page 5-50 Incoming Called Digits in AMA on page 5-59
ANSI-41 Rev C Call Transfer

The ANSI-41 Rev C Call Transfer feature gives mobile subscribers the ability to transfer a call using ANSI-41 facilities. For more about this feature, read the ANSI-41 Rev C Call Transfer Optional Feature document, 401-612-248.
Issue 27
May 2004
B-91
401-610-133A
Table B-82 on page B-92 lists the changes made to this document for this feature. Table B-82. Changes for ANSI-41 Rev C Call Transfer Feature Caused... Addition of the following in Table 4-41, AMASE Table 365 Service Feature:

This Change... Addition of four new service feature codes
077 = Call Transfer 078 = PIN and Call Transfer 079 = CN and Call Transfer 080 = PIN and CN and Call Transfer
NOTE:
Table 365, Service Feature, has been deleted and replaced by Table 2002. Also, multiple service features codes have been split into their individual entities. See the following in Table 4-70, AMASE Table 2002
077 = Call Transfer on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121
Circuit Data IWF Indicator in AMA

The IS-634 Circuit Data IWF Indicator in AMA feature gives a service provider the ability to discriminate Internet access calls from other calls. This gives the service provider flexibility in billing enhanced services for Internet access calls. The Circuit Data IWF Indicator in AMA feature is dependent upon the CDMA Circuit Mode Data Services feature. For more information about this feature, read the Circuit Data IWF Indicator in AMA Optional Feature document, 401-612-253.
B-92
Issue 27
May 2004
Table B-83 on page B-93 lists the changes made to this document for this feature. Table B-83. Changes for Circuit Data IWF Indicator in AMA Feature Caused...
section 03 = IWF Cause Code in Table 4-61, AMASE Table 569 5-Digit Context ID
NOTE:
Table 569, 5-Digit Context ID, has been deleted and its contents merged with Table 237. See 90023 = IWF Cause Code on page 4-40 in Table 4-24, AMASE Table 237. Editing of the section Module 616--5Digit Information Module to add information for this feature. Chapter 5Modules
NOTE:
Module 616, 5-Digit Information Module, has been deleted and its contents replaced with Module 621. See Circuit Data IWF Indicator in AMA on page 5-59 (in the Digit Information Module 621 section).
IS53 Preferred Language

The IS53 Preferred Language feature will be available in a future CDMA release. Information about this feature is given here for planning purposes only and is subject to change. The IS53 Preferred Language feature allows a mobile subscriber to choose a preferred language for network services. Such network services include directory assistance, recorded announcements, operator services, emergency services and help line calls. The Phase 2 version of this feature, which is documented here, provides four new service feature codes for service providers to use in billing subscribers for Preferred Language services provided. For more about this feature, read the IS53 Preferred Language Optional Feature document, 401-612-260.
Issue 27
May 2004
B-93
401-610-133A
Table B-84 on page B-94 lists the changes made to this document for this feature. Table B-84. Changes for IS53 Preferred Language Feature Caused... Addition of the following in Table 4-41, AMASE Table 365 Service Feature:

071 = Preferred Language 072 = PIN and Preferred Language 073 = CN and Preferred Language 074 = PIN and CN and Preferred Language
NOTE:
Table 365, Service Feature, has been deleted and replaced by Table 2002. Also, multiple service features codes have been split into their individual entities. See the following in Table 4-70, AMASE Table 2002:
071 = Preferred Language on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121
Analog Fax Support for CDMA

The Analog Fax Support for CDMA feature is available with ECP Release 14.1 and all later releases. The Analog Fax Support for CDMA feature allows mobile subscribers who have fax machines with an analog output to send and receive faxes in a CDMA environment. This feature is used primarily for wireless local loop. The Analog Fax support for CDMA feature is dependent upon the CDMA Circuit Mode Data Services feature. The Analog Fax Support for CDMA feature provides two new Initial CDMA Assigned Service Options for service providers to use in billing users of the Analog Fax Support for CDMA feature.
B-94
Issue 27
May 2004
For more about this feature, read the Analog Fax Support for CDMA Optional Feature document, 401-612-235. Table B-85 on page B-95 lists the changes made to this document for this feature. Table B-85. Changes for Analog Fax Support for CDMA Feature Caused... Addition of the following in Table 4-46, AMASE Table 497 Event Description Values for Event Type 002:
This Change... Addition of two new service option codes
00020 = 9.6K Analog Fax Service on page 4-76 00021 = 14.4K Analog Fax Service on page 4-76 Chapter 5Modules
Addition of the following Analog Fax service option codes to CDMA Circuit-Mode Data Services on page 5-39:
9.6K Analog Fax on page 5-39 14.4K Analog Fax on page 5-39 Chapter 25CDMA Circuit-Mode Data Services Feature Chapter 25CDMA Circuit-Mode Data Services Feature Chapter 25CDMA Circuit-Mode Data Services Feature
Addition of the section Use with the Analog Fax Support for CDMA Feature on page 25-2 Addition of the section ADSS and the Circuit-Mode Data Service Feature on page 25-7 Reference added in the section called Event Description Field on page 25-14 to Table 4-46, AMASE Table 497 Event Description Values for Event Type 002
Mobile Inactive Trigger

The Mobile Inactive Trigger (MIT) feature is available in ECP R13.0 SU 99-0008 and all later releases.
Issue 27
May 2004
B-95
401-610-133A
The Mobile Inactive Trigger feature provides the added functionality of allowing the service provider to send mobile inactive status notification to a Service Control Point (SCP). An SCP-based application, such as Global Locator Service (GLS), can then use the information to respond to queries from the wireline network. For more information about the Mobile Inactive Trigger feature, see the Mobile Inactive Trigger Optional Feature document, 401-612-271. For information about the Global Locator Service feature, refer to 401-612-149, Global Locator Service Optional Feature document.
B-96
Issue 27
May 2004
Table B-86 on page B-97 lists the changes made to this document for this feature. Table B-86. Changes for Mobile Inactive Trigger Feature Caused... Renaming of the following in AMASE Table 365, Service Feature:
This Change... Renaming of four existing service feature codes
063 = Mobile Inactive Trigger (formerly named Global Locator Service) 064 = PIN and Mobile Inactive Trigger (formerly named PIN and Global Locator Service) 065 = CN and Mobile Inactive Trigger (formerly named CN and Global Locator Service) 066 = PIN and CN and Mobile Inactive Trigger (formerly named PIN and CN and Global Locator Service)
NOTE:
These service feature codes were originally given Global Locator Service names. With the coming of the Mobile Inactive Trigger feature, however, these service feature codes were renamed with more generic names, to allow future use of these codes by more than one feature. This is a name change only. There is NO change to the meaning of these values. NO change to customer billing systems is required.
NOTE:
063 = Mobile Inactive Trigger on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121 Appendix BHistory of Revisions
Addition of notes about MIT in existing GLS documentation:

page B-135 page B-136
Issue 27
May 2004
B-97
401-610-133A
AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature

The AUTOPLEX AMA Tape IBM Label Y2K Compliance feature provides the added functionality of allowing the service provider to specify the century in the HDR1 field in the AMA IBM Tape Label field HDR1. The default in this field is to leave the field blank (allowing the field to remain the same). For information on how to populate this field, see Century Indicator on page 8-30 in Chapter 8, Magnetic Tape Structure and Labels. Table B-87 on page B-98 lists the changes made to this document for this feature. Table B-87. Changes for AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature Caused... The following changes:
This Change... Adding a value for the previously blank century indicator in the IBM standard HDR1 tape label field
New values in the table under Creation Date on page 8-30 New section, Century Indicator on page 8-30
NOTE:
This change also affects Expiration Date on page 8-31.
Technical Changes Not Related to a Feature

Table B-88 on page B-98 lists technical changes made to this document that are unrelated to new features. Table B-88. Technical Changes Not Related to New Features Was Made In... Table 4-62 on page 4-103 in Chapter 4 AMASE Tables Table 4-71 on page 4-124 in Chapter 4 AMASE Tables
This Change... Changed the value of the outgoing trunk direction from 2 to 1 Note added that for TDMA Flexent cells, the radio number that prints is the logical radio number instead of the physical radio number New appendix created
Appendix D, Physical and Logical Radio Number Assignment for TDMA Flexent Cells
B-98
Issue 27
May 2004
CAROD KC02196
Before this CAROD was resolved, the Cellular Networking Service Feature Code was used even for cases where a Cellular Networking call scenario included call waiting. To resolve this CAROD, a new Service Feature Code was added, to be used for calls in which Cellular Networking was taking place and the Call Waiting feature was used. Table B-89 on page B-99 lists the changes to this document for CAROD KC02196. Table B-89. Changes for CAROD KC02196 Caused...
This Change... Addition of a new service feature code for SCN plus CW
section 814 = Cellular Networking (SCN) and Call Waiting (CW) in AMASE Table 12, Service Feature Code
NOTE:
Table 12, Service Feature Code, has been deleted and replaced by Table 2002. Also, multiple service features codes have been split into their individual entities. See the following in Table 4-70, AMASE Table 2002:
056 = Call Waiting on page 4-120 100 = Special Cellular Networking on page 4-120 Chapter 11Cellular Networking Custom Calling
Addition of new sections Service Features for Cellular Networking on page 11-30 and Cellular Networking (CN) and Call Waiting on page 11-30
Issue 27
May 2004
B-99
401-610-133A

Introduction
Issue 14 of this document included information about features for the following releases:

CDMA 13.0 ECP 14.0 SUs that were released between January 1999 and September 1999
Table B-90 on page B-100 lists all AMA-impacting features that were added to Issue 14 of this document and gives the page number of the section in this appendix that summarizes changes made for that feature. Table B-90. Feature Calling Name Presentation for TDMA, Phase 2 CDMA Full International Mobile Station Identity (IMSI) Incoming Call Dialed Digits in AMA Record ANSI-41 Rev C Call Transfer Circuit Data IWF Indicator in AMA IS53 Preferred Language Analog Fax for CDMA Mobile Inactive Trigger AUTOPLEX AMA Tape IBM Label Y2K Compliance Technical Cleanup Not Related to a Feature CAROD KC02196 Changed Pages Per Feature Feature ID 2896.1 2034.0 3711.0 3710.0 3873.0 2730.1 3606.0 3942.0 4161.0 N/A N/A Page B-100 B-101 B-102 B-103 B-104 B-105 B-106 B-107 B-109 B-109 B-110
Calling Name Presentation for TDMA Feature, Phase 2

The Calling Name Presentation for TDMA feature, Phase 2, expanded the existing TDMA Calling Name Presentation feature.
B-100
Issue 27
May 2004
Table B-91 on page B-101 lists the changes made to this document for this feature. Table B-91. Changes for Calling Name Presentation for TDMA Feature, Phase 2 Caused... Addition of the following fields to Table 4-44, AMASE Table 476 in Chapter 4, AMASE Tables:
This Change... Addition of Per-Call Calling Name Enable and Restriction Usage
5 = Per-Call Calling Party Number and Calling Party Name Restriction Used on page 4-71 6 = Per-Call Calling Party Number and Calling Party Name Enable Used on page 4-71 7 = Per-Call Calling Party Name Toggle Used on page 4-71 9 = Unknown on page 4-71 Chapter 5Modules
documentation fix
Revision of section Module 980 Calling Name Outgoing Calls on page 5-85 revision of existing chapter
(all)
CDMA Full IMSI

The IMSI is an international mobile station identity designed to be used in TDMA and CDMA systems. The CDMA Full IMSI feature allows a CDMA mobile to access the system and to be addressed using a full IMSI.
Issue 27
May 2004
B-101
401-610-133A
Table B-92 on page B-102 lists the changes made to this document for this feature. Table B-92. Changes for CDMA Full IMSI Feature Caused... Addition of section 10832 = E.212 International Mobile System Identity on page 4-39 in Table 4-24, AMASE Table 237 Addition of the following:
This Change... Addition of a new generic context identifier Use of the DIM module to store CDMA Full IMSI information
Chapter 5Modules
section "The CDMA Full International Mobile Station Identity (IMSI) feature is active" on page 5-18 Chapter 5Modules
Editing of the section Module 621 Digit Information Module on page 5-46 to add information for this feature. (all) new chapter
Chapter 39CDMA Full IMSI Feature
Incoming Call Dialed Digits in AMA Record

The Incoming Call Dialed Digits in AMA Record feature captures the exact digit string that the cellular subscriber received with an incoming call. With this feature, the exact received digits are placed in the AMA record for the call. The GA date for this feature has yet to be scheduled. For more about this feature, read the Incoming Call Dialed Digits in AMA Record Optional Feature document, 401-612-243. Table B-93 on page B-102 lists the changes made to this document for this feature. Table B-93. Changes for Incoming Call Dialed Digits in AMA Record Feature (Page 1 of 2) Caused... Addition of the section 90010 = Incoming Called Digits on page 4-40 in Table 4-24, AMASE Table 237 In... Chapter 4AMASE Tables
B-102
Issue 27
May 2004
Table B-93.
Changes for Incoming Call Dialed Digits in AMA Record Feature (Page 2 of 2) Caused... Addition of the following:
This Change... Use of the DIM module to store Incoming Call Dialed Digit information
The Incoming Called Digits in AMA feature is active. on page 5-18 Incoming Call Dialed Digits in AMA Record on page 5-50 Chapter 5Modules
Addition of the following:
Incoming Called Digits in AMA on page 5-59
ANSI-41 Rev C Call Transfer

The ANSI-41 Rev C Call Transfer feature gives mobile subscribers the ability to transfer a call using ANSI-41 facilities. For more about this feature, read the ANSI-41 Rev C Call Transfer Optional Feature document, 401-612-248.
Issue 27
May 2004
B-103
401-610-133A
Table B-94 on page B-104 lists the changes made to this document for this feature. Table B-94. Changes for ANSI-41 Rev C Call Transfer Feature Caused... Addition of the following in Table 4-41, AMASE Table 365 Service Feature:

077 = Call Transfer 078 = PIN and Call Transfer 079 = CN and Call Transfer 080 = PIN and CN and Call Transfer
NOTE:
Table 365, Service Feature, has been deleted and replaced by Table 2002. Also, multiple service features codes have been split into their individual entities. See the following in Table 4-70, AMASE Table 2002
077 = Call Transfer on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121
Circuit Data IWF Indicator in AMA

The IS-634 Circuit Data IWF Indicator in AMA feature gives a service provider the ability to discriminate Internet access calls from other calls. This gives the service provider flexibility in billing enhanced services for Internet access calls. The Circuit Data IWF Indicator in AMA feature is dependent upon the CDMA Circuit Mode Data Services feature. For more information about this feature, read the Circuit Data IWF Indicator in AMA Optional Feature document, 401-612-253.
B-104
Issue 27
May 2004
Table B-95 on page B-105 lists the changes made to this document for this feature. Table B-95. Changes for Circuit Data IWF Indicator in AMA Feature Caused...
section 03 = IWF Cause Code in Table 4-61, AMASE Table 569 5-Digit Context ID
NOTE:
Table 569, 5-Digit Context ID, has been deleted and its contents merged with Table 237. See 90023 = IWF Cause Code on page 4-40 in Table 4-24, AMASE Table 237. Editing of the section Module 616 5-Digit Information Module to add information for this feature. Chapter 5Modules
NOTE:
Module 616, 5-Digit Information Module, has been deleted and its contents replaced with Module 621. See Circuit Data IWF Indicator in AMA on page 5-59 (in the Digit Information Module 621 section).
IS53 Preferred Language

The IS53 Preferred Language feature will be available in a future CDMA release. Information about this feature is given here for planning purposes only and is subject to change. The IS53 Preferred Language feature allows a mobile subscriber to choose a preferred language for network services. Such network services include directory assistance, recorded announcements, operator services, emergency services and help line calls. The Phase 2 version of this feature, which is documented here, provides four new service feature codes for service providers to use in billing subscribers for Preferred Language services provided. For more about this feature, read the IS53 Preferred Language Optional Feature document, 401-612-260.
Issue 27
May 2004
B-105
401-610-133A
Table B-96 on page B-106 lists the changes made to this document for this feature. Table B-96. Changes for IS53 Preferred Language Feature Caused... Addition of the following in Table 4-41, AMASE Table 365 Service Feature:

071 = Preferred Language 072 = PIN and Preferred Language 073 = CN and Preferred Language 074 = PIN and CN and Preferred Language
NOTE:
071 = Preferred Language on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121
Analog Fax Support for CDMA

The Analog Fax Support for CDMA feature allows mobile subscribers who have fax machines with an analog output to send and receive faxes in a CDMA environment. This feature is used primarily for wireless local loop. The Analog Fax support for CDMA feature is dependent upon the CDMA Circuit Mode Data Services feature. The Analog Fax Support for CDMA feature provides two new Initial CDMA Assigned Service Options for service providers to use in billing users of the Analog Fax Support for CDMA feature.
B-106
Issue 27
May 2004
For more about this feature, read the Analog Fax Support for CDMA Optional Feature document, 401-612-235. Table B-97 on page B-107 lists the changes made to this document for this feature. Table B-97. Changes for Analog Fax Support for CDMA Feature Caused... Addition of the following in Table 4-46, AMASE Table 497 Event Description Values for Event Type 002:
This Change... Addition of two new service option codes
00020 = 9.6K Analog Fax Service on page 4-76 00021 = 14.4K Analog Fax Service on page 4-76 Chapter 5Modules
Addition of the following Analog Fax service option codes to CDMA Circuit-Mode Data Services on page 5-39:
9.6K Analog Fax on page 5-39 14.4K Analog Fax on page 5-39 Chapter 25CDMA Circuit-Mode Data Services Feature Chapter 25CDMA Circuit-Mode Data Services Feature Chapter 25CDMA Circuit-Mode Data Services Feature
Addition of the section Use with the Analog Fax Support for CDMA Feature on page 25-2 Addition of the section ADSS and the Circuit-Mode Data Service Feature on page 25-7 Reference added in the section called Event Description Field on page 25-14 to Table 4-46, AMASE Table 497 Event Description Values for Event Type 002
Mobile Inactive Trigger

The Mobile Inactive Trigger feature provides the added functionality of allowing the service provider to send mobile inactive status notification to a Service Control Point (SCP). An SCP-based application, such as Global Locator Service (GLS), can then use the information to respond to queries from the wireline network.
Issue 27
May 2004
B-107
401-610-133A
For more information about the Mobile Inactive Trigger feature, see the Mobile Inactive Trigger Optional Feature document, 401-612-271. For information about the Global Locator Service feature, refer to 401-612-149, Global Locator Service Optional Feature document. Table B-98 on page B-108 lists the changes made to this document for this feature. Table B-98. Changes for Mobile Inactive Trigger Feature Caused... Renaming of the following in AMASE Table 365, Service Feature:
This Change... Renaming of four existing service feature codes
063 = Mobile Inactive Trigger (formerly named Global Locator Service) 064 = PIN and Mobile Inactive Trigger (formerly named PIN and Global Locator Service) 065 = CN and Mobile Inactive Trigger (formerly named CN and Global Locator Service) 066 = PIN and CN and Mobile Inactive Trigger (formerly named PIN and CN and Global Locator Service)
NOTE:
These service feature codes were originally given Global Locator Service names. With the coming of the Mobile Inactive Trigger feature, however, these service feature codes were renamed with more generic names, to allow future use of these codes by more than one feature. This is a name change only. There is NO change to the meaning of these values. NO change to customer billing systems is required.
NOTE:
063 = Mobile Inactive Trigger on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121 Appendix BHistory of Revisions
Addition of notes about MIT in existing GLS documentation:

page B-135 page B-136
B-108
Issue 27
May 2004
AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature

The AUTOPLEX AMA Tape IBM Label Y2K Compliance feature provides the added functionality of allowing the service provider to specify the century in the HDR1 field in the AMA IBM Tape Label field HDR1. The default in this field is to leave the field blank (allowing the field to remain the same). For information on how to populate this field, see Century Indicator on page 8-30 in Chapter 8, Magnetic Tape Structure and Labels. Table B-99 on page B-109 lists the changes made to this document for this feature. Table B-99. Changes for AUTOPLEX AMA Tape IBM Label Y2K Compliance Feature Caused... The following changes:
This Change... Adding a value for the previously blank century indicator in the IBM standard HDR1 tape label field
New values in the table under Creation Date on page 8-30 New section, Century Indicator on page 8-30
NOTE:
This change also affects Expiration Date on page 8-31.
Technical Changes Not Related to a Feature

Table B-100 on page B-109 lists technical changes made to this document that are unrelated to new features. Table B-100. Technical Changes Not Related to New Features Was Made In... Table 4-62 on page 4-103 in Chapter 4 AMASE Tables Table 4-71 on page 4-124 in Chapter 4 AMASE Tables
This Change... Changed the value of the outgoing trunk direction from 2 to 1 Note added that for TDMA Flexent cells, the radio number that prints is the logical radio number instead of the physical radio number New appendix created
Appendix D, Physical and Logical Radio Number Assignment for TDMA Flexent Cells
Issue 27
May 2004
B-109
401-610-133A
CAROD KC02196
Before this CAROD was resolved, the Cellular Networking Service Feature Code was used even for cases where a Cellular Networking call scenario included call waiting. To resolve this CAROD, a new Service Feature Code was added, to be used for calls in which Cellular Networking was taking place and the Call Waiting feature was used. Table B-101 on page B-110 lists the changes to this document for CAROD KC02196. Table B-101. Changes for CAROD KC02196 Caused...
This Change... Addition of a new service feature code for SCN plus CW
section 814 = Cellular Networking (SCN) and Call Waiting (CW) in AMASE Table 12, Service Feature Code
NOTE:
Table 12, Service Feature Code, has been deleted and replaced by Table 2002. Also, multiple service features codes have been split into their individual entities. See the following in Table 4-70, AMASE Table 2002:
056 = Call Waiting on page 4-120 100 = Special Cellular Networking on page 4-120 Chapter 11Cellular Networking Custom Calling
Addition of new sections Service Features for Cellular Networking on page 11-30 and Cellular Networking (CN) and Call Waiting on page 11-30
B-110
Issue 27
May 2004

Introduction
Issue 13 of this manual included information about features for the following releases:

ECP 13.0 CDMA 13.0 SUs that were released between January and December of 1998
Table B-102 on page B-111 lists all AMA-impacting features that were added to this document for the ECP 13.0 delivery and gives the page number of the section in this appendix that summarizes changes made for each of these features. Table B-102. Feature No Charge Calls in AMA Record AMA Calling Party Category Information Wireless Number Portability Over the Air Activation for TDMA Last Call Return Calling Name Presentation for TDMA Separation of MSID-MDN Flexible Alerting CDMA Packet-Mode Data Service CDMA Private Network and User Zone ANSI-41 Billing Module Changed Pages Per Feature Feature ID 3364 3365 2726 2420.0 2521 2896 2901 2835 2038 2748.0 3558 Page B-112 B-113 B-115 B-117 B-118 B-119 B-121 B-123 B-125 B-127 B-128
Issue 27
May 2004
B-111
401-610-133A
No Charge Calls in AMA Record

The No Charge Calls in AMA Record feature allows service providers to categorize calls that should be free or marked as no charge in the AMA record. Such calls include emergency calls3. This feature uses a new call type, 074 Free Land/No Charge Call. Table B-103 on page B-112 lists the changes made to this document for this feature. Table B-103. Changes for No Charge Calls in AMA Record Feature Caused... Addition of Free/No Charge Call (Call Type 074) on page 6-7 Addition of Call Type 074 on page 6-12 in Table 6-1, Call Types and Associated Structure Codes Addition of 074 on page 4-7 in Table 4-5, AMASE Table 1 Addition of 074 as a valid call type in the following structure codes:

This Change... New Call Type
In... Chapter 6Call Types Chapter 6Call Types
Chapter 4AMASE Tables Chapter 3Structure Code Layouts
x2329 on page 3-13 x2330 on page 3-17 x2332 on page 3-24 x2333 on page 3-28 x2421 on page 3-54 02800 on page 3-56 02802 on page 3-60 Chapter 31No Charge Calls in AMA Record Feature
(all)
new chapter
In the United States, these are typically 911 calls.
B-112
Issue 27
May 2004
AMA Calling Party Category Information

The AMA Calling Party Category Information feature provides a category code with an incoming call. This information gives Service Providers the ability to distinguish calls for which the calling party pays from calls for which the mobile subscriber pays. This feature added a new module, the Calling Party Category Module. NOTE: The Calling Party Category Module was deleted when new AMA record structures were created for 15 Digit DN, in ECP 16.0. Information for this module was moved into the base structure code layouts.
Issue 27
May 2004
B-113
401-610-133A
Table B-104 on page B-114 lists the changes made to this document for this feature. Table B-104. Changes for AMA Calling Party Category Information Feature (Page 1 of 2) Caused.... Addition of Module 903--Calling Party Category Module. In... Chapter 5Modules
This Change... One New Module
NOTE:
This module has been deleted. This information is now in the base structure code layouts. Addition of 903 = Calling Party Category Module to Table 4-21, AMASE Table 88 on page 4-35. Chapter 4AMASE Tables
NOTE:
The reference to this module has been deleted. Calling Party Category information is now in the base structure code layouts. Addition of mention of Calling Party Category Module as a valid module to the following structure code layouts:

x2329 on page 3-13 x2330 on page 3-17 x2331 on page 3-21 x2334 on page 3-32 x2335 on page 3-36
NOTE:
The reference to this module has been deleted. Calling Party Category information is now in the base structure code layouts. new table Addition of Table 4-49, AMASE Table 566 on page 4-79 Chapter 4AMASE Tables
NOTE:
This table still exists. It is now called by the base structure code layouts instead of by a module.
B-114
Issue 27
May 2004
Table B-104.
Changes for AMA Calling Party Category Information Feature (Page 2 of 2) Caused.... new chapter In... Chapter 35AMA Calling Party Category Information Feature
This Change... (all)
NOTE:
Chapter 35 was rewritten in ECP 16.0 to show that the information is now placed in the base structure code layouts instead of in a module.
Wireless Number Portability

The Wireless Number Portability feature provides service provider portability, which gives a wireless subscriber the ability to port a telephone number from one service provider to another service provider, both within the subscribers service area. This gives a subscriber the ability to retain his or her telephone number when changing to a different service provider within the subscribers service area. This feature adds a new module, the Wireless Number Portability Module, and also makes use of an existing module, the Digit Information Module. Table B-105 on page B-115 lists the changes made to this document for this feature. Table B-105. Changes for Wireless Number Portability Feature (Page 1 of 3) Caused... Addition of line 10831 = Jurisdiction Information Parameter to Table 4-24, AMASE Table 237 on page 4-39 Addition of Table 4-51 "AMASE Table 730" on page 4-83 Addition of Table 4-52 "AMASE Table 731" on page 4-84 Addition of Table 4-53 "AMASE Table 732" on page 4-85 Addition of Table 4-54 "AMASE Table 733" on page 4-86 Addition of Table 4-55 "AMASE Table 734" on page 4-87 In... Chapter 4AMASE Tables Chapter 4AMASE Tables Chapter 4AMASE Tables Chapter 4AMASE Tables Chapter 4AMASE Tables Chapter 4AMASE Tables
This Change... New Generic Context Identifier Five New Tables
Issue 27
May 2004
B-115
401-610-133A
Table B-105.
Changes for Wireless Number Portability Feature (Page 2 of 3) Caused... Addition of Module 720Wireless Number Portability Module on pages 5-8, 5-21, and 5-73 Addition of 720 = Wireless Number Portability Module to AMASE Table 88 on page 4-35 Addition of mention of Wireless Number Portability Module as a valid module to the following structure code layouts:

This Change... One New Module
x2118 on page 3-6 x2119 on page 3-10 x2329 on page 3-13 x2330 on page 3-17 x2332 on page 3-24 x2333 on page 3-28
B-116
Issue 27
May 2004
Table B-105.
Changes for Wireless Number Portability Feature (Page 3 of 3) Caused... WNP information to be added to the section describing the Digit Information Module 1. In... Chapter 5Modules
This Change... Re-Use of Existing Digit Information Module 1
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Wireless Number Portability on page 5-55 in the Module 621 - Digit Information Module section. Addition of mention of Digit Information Module 1 as a valid module to the following structure codes:

x2118 on page 3-6 x2119 on page 3-10 x2331 on page 3-21 x2334 on page 3-32 x2335 on page 3-36
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (all) new chapter Chapter 36Wireless Number Portability Feature
Over the Air Activation Feature

The Over the Air Activation feature consists of procedures that allow a potential cellular/PCS service subscriber to activate (that is, become authorized for) new service without the intervention of a third party.
Issue 27
May 2004
B-117
401-610-133A
Table B-106 on page B-118 lists the changes made to this document for this feature. Table B-106. Changes for Over the Air Activation Feature Caused... Addition of service feature code 812 = Over the Air Activation in AMASE Table 12. In... Chapter 4AMASE Tables
NOTE:
AMASE Table 12 was deleted in ECP 16.0 and replaced with Table 2002. See 812 = Over the Air Activation (OTA) on page 4-121 in Table 4-70, AMASE Table 2002. Removal of text in AMASE Tables 13, 14, and 16 that said that OTA worked like Dialed Digits in AMA. For both CDMA and TDMA, this is not true.
NOTE:
AMASE Tables 13, 14 and 16 were deleted in ECP 16.0 and replaced with AMASE Table 2000.
Last Call Return Feature

The Last Call Return (LCR) feature enables a customer to return the last incoming call if the customers phone was alerted.
B-118
Issue 27
May 2004
Table B-107 on page B-119 lists the changes made to this document for this feature. Table B-107. Changes for Last Call Return Feature Caused... Addition of the following service feature codes in AMASE Table 12: 301 = Last Call Return in AMASE Table 12 Service Feature Code 154 = Last Call Return and ThreeWay Calling In... Chapter 4AMASE Tables
This Change... Two New Service Feature Codes
NOTE:
Table 12, Service Feature Code, was deleted in ECP 16.0 and replaced by Table 2002. Also, multiple service features codes have been split into their individual entities. See the following in Table 4-70, AMASE Table 2002:
010 = Three-Way Calling on page 4-120 301 = Last Call Return on page 4-121
Calling Name Presentation for TDMA Feature

The Calling Name Presentation for TDMA feature provides the name identification of the calling party (for example, personal name, company name, restricted or not available) to the called subscriber. Table B-108 on page B-119 lists the changes made to this document for this feature. Table B-108. Changes for Calling Name Presentation for TDMA Feature (Page 1 of 3) Caused... Addition of Module 981Calling Name Incoming Calls on pages 5-9, 5-22, and 5-86 In... Chapter 5Modules
This Change... Two New Modules
Issue 27
May 2004
B-119
401-610-133A
Table B-108.
Changes for Calling Name Presentation for TDMA Feature (Page 2 of 3) Caused... Addition of 981 = Calling Name Incoming Calls Module as a valid module to AMASE Table 88 Module Code on page 4-35 Addition of 981 as a valid module in the following structure codes:

This Change...
x2329 on page 3-13 x2331 on page 3-21 x2332 on page 3-24 x2333 on page 3-28 x2334 on page 3-32 x2335 on page 3-36 Chapter 5Modules
Addition of Module 980Calling Name Outgoing Calls on pages 5-9, 5-22, and 5-85 Addition of 980 = Calling Name Outgoing Calls Module on page 4-36 in Table 4-21, AMASE Table 88 Addition of 980 as a valid module in the following structure codes:

x2329 on page 3-13 x2330 on page 3-17 x2332 on page 3-24 x2333 on page 3-28 Chapter 4AMASE Tables
Modifying existing CPN fields to add Calling Name Presentation information
Changed title of and wording of fields of AMASE Table 477 on page 4-73 to add Calling Name Presentation Information to this table Changed title of and wording of fields of AMASE Table 476 on page 4-71 in to add Calling Name Presentation Information to this table
B-120
Issue 27
May 2004
Table B-108.
Changes for Calling Name Presentation for TDMA Feature (Page 3 of 3) Caused... Addition of Calling Name Incoming/ Outgoing Calls Modules on page 4-74 to explain the CNAP usage of this field Addition of Usage in the Calling Name Outgoing Call Module on page 4-72 to explain the CNAP usage of this field In... Chapter 4AMASE Tables
This Change...
(all)
new chapter
Separation of MSID-MDN Feature

The Separation of MSID-MDN feature separates a mobile subscriberss Mobile Station Identifier (MSID) from the mobile subscribers Mobile Directory Number (MDN). Table B-109 on page B-121 lists the changes made to this document for this feature. Table B-109. Changes for Separation of MSID-MDN Feature (Page 1 of 2) Caused... Addition of 10830 = 10-digit Mobile Identification Number to Table 4-24, AMASE Table 237 on page 4-39 Separation of MSID-MDN feature information to be added to the section describing the Digit Information Module 1. In... Chapter 4AMASE Tables Chapter 5Modules
This Change... New Generic Context Identifier Re-Use of Existing Digit Information Module 1 (DIM1)
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46.
Issue 27
May 2004
B-121
401-610-133A
Table B-109.
Changes for Separation of MSID-MDN Feature (Page 2 of 2) Caused... Addition of the Digit Information Module as a valid module in the following structure codes:
This Change... Re-Use of Existing Digit Information Module 1 (DIM1) (Cont.)
x1116 on page 3-6
NOTE:
Structure code layout x1116 was deleted in ECP 16.0 and its contents merged with x2411.

x2118 on page 3-6 x2119 on page 3-10 x2329 on page 3-13 x2330 on page 3-17 x2331 on page 3-21 x2332 on page 3-24 x2333 on page 3-28 x2334 on page 3-32 x2335 on page 3-36 x2336 on page 3-39 x2337 on page 3-42 x2338 on page 3-45 x2411 on page 3-47 x2415 on page 3-52 x2421 on page 3-54
NOTE:
Some of these structure codes already had the DIM as a valid module for other features.
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (all) new chapter Chapter 33MIN-MDN Separation Feature
B-122
Issue 27
May 2004

The Flexible Alerting feature provides the ability to group more than one DN together (as a flexible alerting group) for the purpose of alerting them simultaneously. This feature applies to both TDMA and analog technologies and can be used in both cellular and PCS TDMA and analog systems. The Flexible Alerting feature will be available for TDMA/Analog technologies. Table B-110 on page B-123 lists the changes made to this document for this feature. Table B-110. Changes for Flexible Alerting Feature (Page 1 of 3) Caused... Addition of 90015 = FA Leg Directory Number in Table 4-24, AMASE Table 237 on page 4-39 Addition of 90016 = FA Pilot Directory Number in Table 4-24, AMASE Table 237 on page 4-39 In... Chapter 4AMASE Tables Chapter 4AMASE Tables
This Change... Two New Generic Context Identifiers
Issue 27
May 2004
B-123
401-610-133A
Table B-110.
Changes for Flexible Alerting Feature (Page 2 of 3) Caused... Added the following new service features codes in Table 4-41, AMASE Table 365 Service Feature.

This Change... Four New Service Feature Codes
067 = Flexible Alerting 068 = PIN and Flexible Alerting 069 = CN and Flexible Alerting 070 = CN and PIN and Flexible Alerting
NOTE:
067 = Flexible Alerting on page 4-120 100 = Special Cellular Networking on page 4-120 800 = PIN on page 4-121 Chapter 5Modules
Re-Use of Existing Digit Information Module 1 (DIM1)
Flexible Alerting feature information to be added to the section describing the Digit Information Module 1.
NOTE:
Module 611, Digit Information Module 1, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. One New Module Addition of Module 900Billing Identification Number Module on pages 5-9, 5-21, and 5-78 Addition of 900 as a valid module to AMASE Table 88 Module Code on page 4-35 Chapter 5Modules
B-124
Issue 27
May 2004
Table B-110.
Changes for Flexible Alerting Feature (Page 3 of 3) Caused... Addition of 900 as a valid module in the following structure codes:

This Change...
x2329 on page 3-13 x2330 on page 3-17 x2331 on page 3-21 x2332 on page 3-24 x2333 on page 3-28 x2334 on page 3-32 x2335 on page 3-36 Chapter 4AMASE Tables Chapter 37Flexible Alerting Feature
One New Table (to support New Module) (all)
Addition of Table 950 Billing ID Number (BIN) Number on page 4-100 new chapter
CDMA Packet-Mode Data Service Feature

The CDMA Packet-Mode Data Service feature provides a subscriber having the appropriate mobile station configuration the ability to transmit and receive bursts of data over a packet data network via the CDMA air interface. This provides the infrastructure for mobile users with laptop computers or other data devices conforming to the TIA/EIA/IS-657 or TIA/EIA/IS-707 standard to access various data applications, such as e-mail, file transfer, field service automation, and fleet dispatch.
Issue 27
May 2004
B-125
401-610-133A
Table B-111 on page B-126 lists the changes made to this document for this feature. Table B-111. Changes for CDMA Packet-Mode Data Services Feature (Page 1 of 2) Caused... Addition of section Mobile-Originated Packet Data Call (Call Type 450) on page 6-8 Addition of section MobileTerminated Packet Data Call (Call Type 451) on page 6-8 Addition of an entry for MobileOriginated Packet Data Call in Table 6-1, Call Types and Associated Structure Codes on page 6-9 Addition of an entry for MobileTerminated Packet Data Call in Table 6-1, Call Types and Associated Structure Codes on page 6-9 Added mention of call type 450 to the following structure codes:

In... Chapter 6Call Types
Chapter 6Call Types
Chapter 6Call Types
Chapter 6Call Types
x2329 on page 3-13 x2333 on page 3-28 Chapter 3Structure Code Layouts
Added mention of call type 451 to the following structure codes:

x2331 on page 3-21 x2334 on page 3-32 Chapter 4AMASE Tables
Two New Event Types
Two new Event Types in Table 4-37, AMASE Table 453 on page 4-60:
010 = Packet Data Link Layer Connection Open 011 = Packet Data Link Layer Connection Reactivation Chapter 4AMASE Tables
Redefinition of part of Technology Type Field
Definition of the first BCD character in Table 4-39, AMASE Table 471 for values 0-5 on page 4-62
B-126
Issue 27
May 2004
Table B-111.
Changes for CDMA Packet-Mode Data Services Feature (Page 2 of 2) Caused... CDMA Packet-Mode Data Services feature information to be added to the section Module 344Data Module on page 5-38 Addition of six new Event Descriptions in Table 4-47, AMASE Table 497 Event Description Values for Event Types 010 and 011 on page 4-77:
This Change... Re-Use of Existing Data Module
Six New Event Descriptions
00007 = 9.6K IP Service (9.6 Kbps IP Revision 0) 00008 = 9.6K CDPD Service (9.6 Kbps CDPD Revision 0) 00015 = 14.4K IP Service (14.4 Kbps IP Revision 0) 00016 = 14.4K CDPD Service (14.4 Kbps CDPD Revision 0) 04103 = 9.6K IP Service, Version 1 (9.6 Kbps IP Revision 1) 04104 = 9.6K CDPD Service, Version 1 (9.6 Kbps CDPD Revision 1) Chapter 34CDMA Packet-Mode Data Services Features
(all)
new chapter
CDMA Private Network and User Zone

The CDMA Private Network and User Zone feature allows the CDMA service provider to distinguish public network system elapsed time from non-public network system elapsed time, allowing the two systems to be billed at different rates. (This capability is already available for TDMA and for analog.)
Issue 27
May 2004
B-127
401-610-133A
Table B-112 on page B-128 lists the changes made to this document for this feature. Table B-112. Changes for CDMA Private Network and User Zone Feature Caused... Addition of two new time types for CDMA to Table 4-43, AMASE Table 473 on page 4-68:
This Change... Two New Time Types
012 = Digital User Zone Sequence Number 3 Elapsed Time - digital only 013 = Digital User Zone Sequence Number 4 Elapsed Time - digital only Chapter 5Modules
Re-Use of Existing User Zone Module
Revision of Module 336User Zone Module on page 5-36 to include CDMA Private Network and User Zone information Revision of chapter to add CDMA Private Network and User Zone feature information
(both)
Chapter 24User Zone Capability
ANSI-41 Billing Module

The ANSI-41 Billing Module feature adds three ANSI-41 Revision C parameters to AMA records. These parameters will be used by WIN applications to direct the MSC on how to bill a call.
B-128
Issue 27
May 2004
Table B-113 on page B-129 lists the changes made to this document for this feature. Table B-113. Changes for ANSI-41 Billing Module Feature (Page 1 of 2) Caused... Addition of the following new generic context identifiers to Table 4-24 on page 4-39:
This Change... Three New Generic Context Identifiers
90006 = ANSI-41 DMH Account Code Digits 90007 = ANSI-41 DMH Alternate Billing Digits 90008 = ANSI-41 DMH Billing Digits Chapter 4AMASE Tables Chapter 4AMASE Tables Chapter 5Modules
Two New Tables
Addition of Table 305 Roamer Status Indicator on page 4-43 Addition of Table 803 5-Digit Number on page 4-93
Re-Use of Existing Digit Information Modules 611, 612, and 613
ANSI-41 information to be added to the section describing the Digit Information Modules 1, 2 and 3.
NOTE:
Modules 611, 612 and 613, Digit Information Modules 1, 2 and 3, have been deleted and their contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. One New Module Addition of Module 6165-Digit Information Module on selected pages Chapter 5Modules
NOTE:
Module 616, 5-Digit Information Module, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46.
Issue 27
May 2004
B-129
401-610-133A
Table B-113.
Changes for ANSI-41 Billing Module Feature (Page 2 of 2) Caused... Addition of Module 6165-Digit Information Module on selected pages In... Chapter 4AMASE Tables
This Change... One New Module (Cont.)
NOTE:
Module 616, 5-Digit Information Module, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. Addition of Module 616 as a valid module in the following structure codes:

x2329 on page 3-13 x2330 on page 3-17 x2331 on page 3-21 x2332 on page 3-24 x2333 on page 3-28 x2334 on page 3-32 x2335 on page 3-36
NOTE:
Module 616, 5-Digit Information Module, has been deleted and its contents replaced with Module 621. See Module 621 - Digit Information Module on page 5-46. (all) new chapter Chapter 38ANSI-41 Billing Module and ANSI-41 Billing Module with Service Type Features
B-130
Issue 27
May 2004

There was only one code change for AMA for ECP Release 12.0. The CDMA Circuit-Mode Data Services feature was added. Changes for the CDMA Circuit-Mode Data Services feature were published in the ECP 11.0 version of the AMA Formats manual (Issue 11). Therefore, the AMA Formats manual was NOT re-issued for ECP 12.0.
Issue 27
May 2004
B-131
401-610-133A
Changes Made in ECP Release 11.0

New Features
In Issue 11 of this manual, the following features were added for ECP Release 11.0/CDMA Release 6.0:
Circuit-Mode Data Service4The Circuit-Mode Data Service feature provides a subscriber having the appropriate mobile station configuration the ability to communicate with existing asynchronous modems and group-3 facsimile machines using the CDMA air interface. Enhanced Kill CallWhen a call is torn down, either by an automated request or a request from a technician, this is called a call tear down. The ability to do this is provided by the Call Tear Down (KILLCALL) feature. The Enhanced Kill Call feature provides the following new information: after a call has been killed, the AMA record generated for this scenario will indicate Kill Call in the timing indicator field. Call Waiting Call Back (CWCB)A CWCB scenario occurs whenever a mobile subscriber ends a call waiting call and the party on hold, if still present, automatically calls the mobile subscriber back. For such cases, the CWCB feature provides the following information: the AMA record generated for a CWCB call will indicate CWCB in the timing indicator field. AMA Antenna Face Information for TDMA and AnalogThis feature gives TDMA and analog service providers the ability to distinguish from which antenna face the call was initiated. (CDMA service providers already have this capability.)
Changes
In Issue 11 of this manual, the following changes were added for ECP Release 11.0/CDMA Release 6.0:
Circuit-Mode Data ServiceThe Circuit-Mode Data Service feature provides a subscriber having the appropriate mobile station configuration the ability to communicate with existing asynchronous modems and group-3 facsimile machines using the CDMA air interface.
The Circuit-Mode Data Service feature adds two Call Types and one Data Module. This feature impacts the following:
The Circuit-Mode Data Service feature was not available until ECP Release 12.0. The information was released in the ECP 11.0 version of the manual for planning purposes.
B-132
Issue 27
May 2004
Chapter 6, Call TypesTable 6-1, Call Types and Associated Structure Codes Chapter 4, AMASE TablesTable 4-5, AMASE Table 1 Chapter 5, ModulesTable 5-2, Quick Reference Table of AMA Module Definitions Chapter 5, ModulesTable 5-3, Module Generation Criteria Chapter 4, AMASE TablesTable 4-21, AMASE Table 88 Chapter 4, AMASE TablesTable 4-46, AMASE Table 497 Event Description Values for Event Type 002 Chapter 3, Structure Code LayoutsTable 3-29, Structure Code x2411 Chapter 3, Structure Code Layouts--Table 3-12, Special Feature Activation/Deactivation Structure Code x1116
NOTE: Structure code x1116 has been deleted. Information formerly in structure code layout x1116 was placed in structure code layout x2411.

Chapter 3, Structure Code LayoutsTable 3-3, Structure Code x2118 Chapter 3, Structure Code LayoutsTable 3-5, Structure Code x2119 Chapter 3, Structure Code LayoutsTable 3-11, Structure Code x2331 Chapter 3, Structure Code LayoutsTable 3-15, Structure Code x2333 Chapter 3, Structure Code LayoutsTable 3-17, Structure Code x2334 Chapter 3, Structure Code LayoutsTable 3-19, Structure Code x2335 Chapter 3, Structure Code LayoutsTable 3-21, Structure Code x2336 Chapter 3, Structure Code LayoutsTable 3-7, Structure Code x2329 Chapter 4, AMASE TablesTable 4-37, AMASE Table 453 Chapter 6, Call TypesDefinition of Mobile Terminated Data Call and Mobile Originated Data Call Chapter 23, Multiple Voice Coding Featuresection "Feature Interactions" on page 23-6 Chapter 25CDMA Circuit-Mode Data Services Feature
Enhanced Kill CallWhen a call is torn down, either by an automated request or a request from a technician, this is called a call tear down. The ability to do this is provided by the Call Tear Down (KILLCALL) feature. The Enhanced Kill Call feature provides the following new information: after a call has been killed, the AMA record generated for this scenario will indicate Kill Call in the timing indicator field.
Issue 27
May 2004
B-133
401-610-133A
Chapter 4, AMASE TablesTable 4-11, AMASE Table 7 Chapter 4, AMASE TablesTable 4-77, AMASE Table 2008
Call Waiting Call Back (CWCB)A CWCB scenario occurs whenever a mobile subscriber ends a call waiting call and the party on hold, if still present, automatically calls the mobile subscriber back. For such cases, the CWCB feature provides the following information: the AMA record generated for a CWCB call will indicate CWCB in the timing indicator field.

Chapter 4, AMASE TablesTable 4-11, AMASE Table 7 Chapter 10, Custom Calling FeaturesAdded section "Service Feature Code" on page 10-14
AMA Antenna Face Information for TDMA and AnalogThis feature gives TDMA and analog service providers the ability to distinguish from which antenna face the call was initiated. (CDMA service providers already have this capability.)

Chapter 4, AMASE TablesTable 4-72 on page 4-127 Chapter 4, AMASE TablesTable 4-71 on page 4-124 Chapter 29, Wireline Feature Transparency Feature
B-134
Issue 27
May 2004

New Features
In Issue 10 of this manual, the following features were added for ECP Release 10.0/CDMA Release 5.0:
Short Message ServiceAllows subscribers to send alphanumeric pager-like messages of various lengths to SMS display-capable mobile units. Global Locator ServiceProvides the capability of delivering a call to a subscriber regardless of the subscribers current location.
NOTE: See Mobile Inactive Trigger feature (added in ECP Release 13.0 SU 99-0008).
Mobile Loop Back TestAllows a subscriber, a point-of-sale clerk, or a system technician to dial a test line Directory Number (DN) from the mobile unit to invoke either a timed or non-timed mobile loopback test call.
Wireline Feature Transparency(for PCS CDMA deployments). Allows the wireless versions of certain call originations to more closely emulate their land-line equivalents. After a subscriber dials certain feature codes, the system will play a network dialtone and collect additional digits. This feature is being deployed in two phases. Phase 1 (with CDMA 5.0) is for the Call Forwarding feature. Phase 2 (with CDMA 6.0) will support additional Custom Calling features such as Call Waiting and Cancel Call Waiting, Call Transfer, and One Call Un-block. AMA EnhancementsTo support the migration of the Flexent/ AUTOPLEX wireless network to compliance with the IS-124 interim standard, the AMA Enhancements feature is being provided. This feature added new, more detailed call record information to existing AMA records through the use of modules.
Changes
In Issue 10 of this manual, the following changes were added for ECP Release 10.0/CDMA Release 5.0:
Short Message ServiceAllows subscribers to send alphanumeric pagerlike messages of various lengths to SMS display-capable mobile units.
Chapter 4Table 4-46, AMASE Table 497 Event Description Values for Event Type 002 on page 4-76
Issue 27
May 2004
B-135
401-610-133A
Global Locator ServiceProvided the capability of delivering a call to a subscriber regardless of the subscribers current location.
NOTE: The original Global Locator Service Feature Codes were 063 = Global Locator Service, 064 = PIN and Global Locator Service, 065 = CN and Global Locator Service, and 066 = PIN and CN and Global Locator Service. In ECP Release 13.0 SU 99-0008 the definitions of these codes were changed to the following:

063 = Mobile Inactive Trigger 064 = PIN and Mobile Inactive Trigger 065 = CN and Mobile Inactive Trigger 066 = PIN and CN and Mobile Inactive Trigger
NOTE: The functionality of these codes was not changed; only the name. NOTE: In ECP 16.0 the codes were replaced by the following values in the new Table 470, AMASE Table 2002:

063 = Mobile Inactive Trigger 100 = CN 800 = PIN
Mobile Loop Back TestAllows a subscriber, a point-of-sale clerk, or a system technician to dial a test line Directory Number (DN) from the mobile unit to invoke either a timed or non-timed mobile loopback test call.
Chapter 4Table 4-46, AMASE Table 497 Event Description Values for Event Type 002 on page 4-76
Wireline Feature Transparency(for PCS CDMA deployments). Allows the wireless versions of certain call originations to more closely emulate their land-line equivalents. After a subscriber dials certain feature codes, the system will play a network dialtone and collect additional digits. This feature is being deployed in two phases. Phase 1 (with CDMA 5.0) is for the Call Forwarding feature. Phase 2 (with CDMA 6.0) will support additional Custom Calling features such as Call Waiting and Cancel Call Waiting, Call Transfer, and One Call Unblock.
Chapter 4Table 4-11, AMASE Table 7 on page 4-15
B-136
Issue 27
May 2004
AMA EnhancementsTo support the migration of the Flexent/AUTOPLEX wireless network to compliance with the IS-124 interim standard, the AMA Enhancements feature is being provided. This feature added new, more detailed call record information to existing AMA records through the use of modules. This feature impacted the following:

Chapter 5Table 5-3, Module Generation Criteria, on page 5-13 Chapter 5Table 5-2, Quick Reference Table of AMA Module Definitions, on page 5-7 Chapter 4Table 4-21, AMASE Table 88, on page 4-35 Chapter 4Table 4-34, AMASE Table 379, on page 4-54 Chapter 4Table 4-61, AMASE Table 953, on page 4-101 Chapter 4Table 4-62, AMASE Table 954, on page 4-103 Chapter 3Table 3-33, Structure Code x2421, on page 3-54 Chapter 3Table 3-29, Structure Code x2411, on page 3-49 Chapter 3Table 3-31, Structure Code x2415, on page 3-52 Chapter 3Table 3-12, Special Feature Activation/Deactivation Structure Code x1116, (which became part of structure code x2411 in ECP 16.0). Chapter 3Table 3-3, Structure Code x2118, on page 3-7 Chapter 3Table 3-5, Structure Code x2119, on page 3-10 Chapter 3Table 3-9, Structure Code x2330, on page 3-17 Chapter 3Table 3-11, Structure Code x2331, on page 3-21 Chapter 3Table 3-13, Structure Code x2332, on page 3-24 Chapter 3Table 3-15, Structure Code x2333, on page 3-28 Chapter 3Table 3-17, Structure Code x2334, on page 3-32 Chapter 3Table 3-19, Structure Code x2335, on page 3-36 Chapter 3Table 3-21, Structure Code x2336, on page 3-39 Chapter 3Table 3-23, Structure Code x2337, on page 3-42 Chapter 3Table 3-25, Structure Code x2338, on page 3-45 Chapter 3Table 3-7, Structure Code x2329, on page 3-13 Chapter 28, AMA Enhancements Feature
Issue 27
May 2004
B-137
401-610-133A
New Features for ECP Release 9.0

New Features
In Issue 9 of this manual, the following features were added for ECP Release 9.0/ CDMA Release 4.0:
Multiple Voice Coding (MVC)Allows service providers to support CDMA voice calls with different voice coding algorithms. Through RC/V, service providers can deploy voice coding algorithms from a set of pre-defined vocoding algorithms, modify the rules for which voice services are offered to subscribers, and bill subscriber calls according to vocoder type used. Supported vocoding options include 8Kb and 13Kb. DCCH Non-Public Network Charging Area AMA Capability (NPNI) [Also known as User Zone (UZ)] Allows service providers to distinguish public network system elapsed time from non-public network system elapsed time allowing the two systems to be billed at different rates. Metered Billing (MB)enables the service provider to allow subscriber to pre-pay for air time usage.
B-138
Issue 27
May 2004

New Features
In Issue 8 of this manual, the following features were added for ECP Release 8.0/ CDMA Release 3.0:
Limited Service Area 128 (LSA128)Allows the service provider to identify up to 128 Limited Service Areas (LSAs) in its service coverage area and a maximum of three different billing levels. Conditional Call Forwarding Split (CCF Split)Provides users with the ability to define a separate call-forwarding number for the no page response/dont answer and busy cases of CCF (CCF-No Reply and CCF-Busy, respectively). 5ESS Digital Cellular Switch (DCS) Trunk Expansion AMA CapabilityAllows the service provider who uses the 5ESS DCS to store trunk group numbers up to 999 and trunk member numbers up to 999 in the appropriate existing AMA fields.
Also new in the ECP 8.0 version of this document (Issue 8) were the following sections:
Information about the Digital Audio Tape (DAT) unit (see page 8-40 in Chapter 8, Magnetic Tape Structure and Labels). Appendix A, Call Scenarios
Issue 27
May 2004
B-139
401-610-133A

New Features
In Issue 7 of this manual, the following features were added for ECP Release 7.0/ CDMA Release 1.0 and 2.0:
Subscriber PIN Access (SPINA)Allows mobile subscribers to specify when their mobile is/is not allowed to originate calls Personal Communications Services (PCS) Minicell Provides CDMA Release 2.0 support for a PCS minicell
B-140
Issue 27
May 2004
New Features for ECP Release 6.1+

New Features
In Issue 6 of this manual, the following features were added for ECP Release 6.1:

Inter-DCS Limited Service Area (IDLSA) Inter-MSC LSA (IMLSA) Silent Administration of Limited Service Area (SALSA) Voice Privacy Subscriber Personal Identification Number Intercept (SPINI)
Issue 27
May 2004
B-141
401-610-133A
B-142
Issue 27
May 2004
Introduction
This appendix gives different values for the components of voice-channel elapsed time for several feature sets. The values are grouped into the following categories:

Basic Voice-Channel Usage Basic Digital Voice-Channel Usage Basic Analog Voice-Channel Usage
Issue 27
May 2004
C-1
401-610-133A
Basic Voice-Channel Usage
Basic Voice-Channel Usageone component: VCET
Basic Voice-Channel Usage and LSAtwo components: VCET minus LSAET LSAET
Basic Voice-Channel Usage and three-portone independent component: (VCET minus TWTET)
Basic Voice-Channel Usage and three-port and LSAtwo components: (VCET minus TWTET) minus LSAET LSAET.
C-2
Issue 27
May 2004
Basic Digital Voice-Channel Usage
Basic Digital Voice-Channel Usageone component: Digital VCET
Basic Digital Voice-Channel Usage and LSAtwo components: Digital VCET minus Digital LSAET Digital LSAET
Basic Digital Voice-Channel Usage and three-portone independent component: (Digital VCET minus Digital TWTET)
Basic Digital Voice-Channel Usage and three-port and LSAtwo components: (Digital VCET minus Digital TWTET) minus Digital LSAET Digital LSAET.
Issue 27
May 2004
C-3
401-610-133A
Basic Analog Voice-Channel Usage

The values of the components of the analog voice-channel elapsed time (the analog portion of the elapsed time) can be derived from above for several different feature sets. They are shown as follows:
Basic Analog Voice-Channel Usageone component: VCET minus Digital VCET.
Basic Analog Voice-Channel Usage and LSAtwo components: (VCET minus Digital VCET) minus (LSAET minus Digital LSAET) LSAET minus Digital LSAET.
Basic Analog Voice-Channel Usage and three-portone independent component: (VCET minus Digital VCET) minus (TWTET minus Digital TWTET).
Basic Analog Voice-Channel Usage and three-port and LSAtwo components: (VCET minus Digital VCET) minus (TWTET minus Digital TWTET) minus (LSAET minus Digital LSAET). LSAET minus Digital LSAET.
C-4
Issue 27
May 2004
Introduction
For TDMA Flexent cells, radios are grouped into sets of two radios to one board. Each set of two is called a Digital Radio Module (DRM) and has one DRM number. (The DRM number is also called the physical radio number.) To distinguish between the two radios in a DRM, each individual radio on the DRM is assigned a logical radio number by the RCS. In AMA usage and in amasearch output, the radio number that is reported for TDMA Flexent cells is the logical radio number instead of the physical radio number.
Issue 27
May 2004
D-1
401-610-133A
Table
Table D-1 on page D-2 shows the assignment of logical radio numbers to DRM numbers for each cell. Table D-1. Correlation between Physical Radio Numbers and Logical Radio Numbers for TDMA Flexent Cells (Page 1 of 3) MICROCELL NUMBER Microcell 1 DRM NUMBER (RADIOS) DRM1 DRM CARRIER NUMBER Carrier 1 Carrier 2 DRM2 Carrier 1 Carrier 2 DRM3 Carrier 1 Carrier 2 DRM4 Carrier 1 Carrier 2 DRM5 RCS # Microcell 2 DRM1 Carrier 1 Carrier 2 DRM2 Carrier 1 Carrier 2 DRM3 Carrier 1 Carrier 2 DRM4 Carrier 1 Carrier 2 DRM5 Carrier 1 Carrier 2 11 12 13 14 15 16 17 18 19 20 Carrier 1 Carrier 2 LOGICAL RADIO NUMBER 01 02 03 04 05 06 07 08 09 10
D-2
Issue 27
May 2004
Physical and Logical Radio Number Assignment for
Table D-1.
Correlation between Physical Radio Numbers and Logical Radio Numbers for TDMA Flexent Cells (Page 2 of 3) MICROCELL NUMBER Microcell 3 DRM NUMBER (RADIOS) DRM1 DRM CARRIER NUMBER Carrier 1 Carrier 2 DRM2 Carrier 1 Carrier 2 DRM3 Carrier 1 Carrier 2 DRM4 Carrier 1 Carrier 2 DRM5 Carrier 1 Carrier 2 LOGICAL RADIO NUMBER 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
RCS # Microcell 4 DRM1 Carrier 1 Carrier 2 DRM2 Carrier 1 Carrier 2 DRM3 Carrier 1 Carrier 2 DRM4 Carrier 1 Carrier 2 DRM5 Carrier 1 Carrier 2
Issue 27
May 2004
D-3
401-610-133A
Table D-1.
Correlation between Physical Radio Numbers and Logical Radio Numbers for TDMA Flexent Cells (Page 3 of 3) MICROCELL NUMBER Microcell 5 DRM NUMBER (RADIOS) DRM1 DRM CARRIER NUMBER Carrier 1 Carrier 2 DRM2 Carrier 1 Carrier 2 DRM3 Carrier 1 Carrier 2 DRM4 Carrier 1 Carrier 2 DRM5 Carrier 1 Carrier 2 Microcell 6 DRM1 Carrier 1 Carrier 2 DRM2 Carrier 1 Carrier 2 DRM3 Carrier 1 Carrier 2 DRM4 Carrier 1 Carrier 2 DRM5 Carrier 1 Carrier 2 LOGICAL RADIO NUMBER 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
RCS #
D-4
Issue 27
May 2004
Introduction
This appendix summarizes the changes that were made to the AMA Formats Description manual for the 15 Digit DN feature. The purpose of this appendix is to keep a record of what was changed for this feature.
What is the 15 Digit DN Feature?

The 15 Digit DN feature provided a new and more flexible format for DN to meet the needs of international markets while preserving the traditional 10-Digit Mobile Directory Number (MDN) to meet the needs of current service providers.
Massive Changes to AMA

The 15 Digit DN feature introduced widespread changes into the structure code layouts, AMASE tables, and modules for the Flexent/AUTOPLEX wireless network. In addition, the 15 Digit DN AMA structure code layouts, AMASE tables, and modules were incompatible with the previously-existing AMA record structures.
Use of Italic Font

Throughout this appendix, items that were new or changed for 15 Digit DN are marked in italic font, for ease of reference.
Issue 27
May 2004
E-1
401-610-133A

For more about the 15 Digit DN feature, read the 401-610-622, 15 Digit Directory Number Feature Description.
E-2
Issue 27
May 2004
Documentation Impact of 15 Digit DN Feature

Introduction
This section tells how documentation for the 15 Digit DN feature was handled through ECP 19.0 and will be handled in ECP 20.0 and future generics.
One Version of AMA Formats From 21.0 Forward

From ECP 21.0 on, the AMA Formats Description with 15 Digit DN manual (401610-133A) will be the only AMA manual updated. In ECP 22.0, the AMA Formats Description with 15 Digit DN manual will be renamed as AMA Formats Description manual and the document number will be changed to 401-610-133.
One Version of AMA Search From 21.0 Forward

From ECP 21.0 on, the AMA Search with 15 Digit DN manual (401-612-080A) will be the only AMA Search manual to be updated.
Issue 27
May 2004
E-3
401-610-133A
Summary of Changes to Structure Code Layouts

Introduction
This section summarizes changes to structure code layouts made for the 15 Digit DN feature.
What was Changed?

The major change to structure code layouts for the 15 Digit DN feature is that:
All call-related structure code layouts were modified so that the DN is now a generic number field that can be expanded to up to fifteen digits in length.
However, other changes were made at the same time. See Changes not Related to 15 Digit DN on page E-4.
Changes not Related to 15 Digit DN

Since service providers had to reprogram their billing rendering systems to accommodate new structure code layouts for 15 Digit DN, this was a good time to make other structure code layout changes. These changes improved efficiency and made room for future expansion. Major improvements include:
Digital information (type of technology and station class mark) was taken out of the Basic Digital Module (325)1 and added to the base AMA structure code layouts. Calling Party Category information was taken out of the Calling Party Category Module (903)2 and added to the base structure code layouts. Trunk information was taken out of the Extended Information Module (332)3 and added to the base structure code layouts. Service feature codes were simplified and the Service Feature Module (Module 620) was created to hold multiple service feature codes. (Previously, all service feature code information had been stored in the structure code layout, using a service feature code from AMASE Table 12.
1 2 3
This module was then deleted. This module was then deleted This module was then deleted.
E-4
Issue 27
May 2004
AMASE Table 12 was replaced by AMASE Table 2002.) (See Module 620Service Feature Module on page 5-41 for an explanation of how the Service Feature Module works.)
Some fields were taken out of structure code layouts and placed into modules. (For a listing of these fields, see Fields Moved Into Existing Modules on page E-6.) Two old structure code layouts, x1111, Call Forwarding Activation/ Deactivation, and x1116, Special Feature Activation/Deactivation, were combined into one structure code layout x2411, Feature Activation/ Deactivation.
What did not Change?

The following things about structure code layouts did NOT change for 15 Digit DN:

The call recording philosophy did not change. All statistical entry and tracer record structure code layouts (for example, call assembly tracer, 01047) did not change. Call types and event types did not change.
Quick Reference List

For 15 Digit DN, every call-related structure code layout was replaced with a new structure code layout that has a new number. Table 1 on page E-9 provides a quick reference list of each new 15 Digit DN structure code layout and shows which old structure code layout it replaces.
Deleted Fields
Fields deleted for the 15 Digit DN feature are listed in Deleted AMASE Tables on page E-33.
Issue 27
May 2004
E-5
401-610-133A
Fields Moved Into Existing Modules

Introduction
For the 15 Digit DN record structures, the following fields were moved out of the base structure code layouts and into modules:

Project Accounting Service (PAS) Information LSA Indicator and its associated Elapsed Time Three-Way Transition Elapsed Time DCS Outpulsed Digits
The following entries explain what happened to each of these fields.
PAS Information
All PAS information was moved out of the base structure code layouts into the Digit Information Module. This saves space in the structure code layouts. See PAS Information on page 5-53 and What is PAS? on page 5-53.
LSA Indicator and Elapsed Time

LSA Indicator and its associated Elapsed Time field have been removed from the base structure code layouts. The information was placed in Module 333, Aggregate LSA Information Module. There are no new fields in this module because those fields already existed within Module 333.
Three-Way Transition Elapsed Time

The Three-Way Transition Elapsed Time field was taken out of the base structure code layouts and placed in Module 326. Module 326 was renamed Auxiliary Time Module.
New Time Type for Three-Way Transition Elapsed Time

Time Type 020 was created in Table 473 to represent Three-Way Transition Elapsed Time. This field is used in Module 326.
E-6
Issue 27
May 2004
DCS Outpulsed Digits

All DCS Outpulsed Digits information was taken out of the base structure code layouts into the Digit Information Module. See DCS Outpulsed Digits on page 5-53, What is DCS Outpulsed Digits? on page 5-53, and How DCS Outpulsed Digits Information is Stored on page 5-54.
Issue 27
May 2004
E-7
401-610-133A
Quick Reference to Structure Code Layouts

Introduction
A complete list of current structure codes and structure code layouts is given in Table 1 on page E-9. The old (non-15 Digit DN) structure code layouts are also shown.
Table
Table 1 on page E-9 lists all 15 Digit DN structure code layouts and gives the meaning of each.
E-8
Issue 27
May 2004
Table AB-1. New (15Digit DN) Structure Code Layout 01047 x2118 x2119 x2329 x2330 x2331 x2332 x2333 x2334 x2335 x2336 x2337 x2338 x2411
Current Layouts Compared to Previous Layouts (Page 1 of 2) Old (Non15 Digit DN) Structure Code Layout 01047 x1118 x1119 x1339 x1330 x1331 x1332 x1333 x1334 x1335 x1336 x1337 x1338 x1111 x1116 Meaning
Call Assembly Tracer Tandem Call with Carrier Interconnect (CI) Information Tandem Call without CI Information Cellular-Originated Call without CI Information Cellular-Originated Call with CI Information Cellular-Terminated Call Control Point Switch (CPS) Cellular-Originated Call with CI Information CPS Cellular-Originated Call without CI Information CPS Cellular-Terminated Call - Facility and Air-Time Record CPS Cellular-Terminated Call - Interswitch Call Termination (ICT) Facility Timing Record Cellular Networking (CN) Slave Switch - Facility and AirTime Record CN Handback - Answered Segment Air-Time Record CN Handback - Intermediate Segment Air-Time Record Feature Activation/Deactivation
NOTE:
x2411 combines both old x1111 and x1116 structure code layouts.
x2415 x2421 02800 02801 02802
x1115 x0421 00800 00801 00802
Mobile Security Entry Virtual System AMA Event Recording Origination Event Termination Event Metered Billing
Issue 27
May 2004
E-9
401-610-133A
Table AB-1. New (15Digit DN) Structure Code Layout 09000 09036 09037 09038 09039 09042 09043
Current Layouts Compared to Previous Layouts (Page 2 of 2) Old (Non15 Digit DN) Structure Code Layout 09000 09036 09037 09038 09039 09042 09043 Meaning
Time Change Statistical Label Beginning of Recording End of Recording Collector Logical Data Set (CLDS) Header CLDS Trailer Primary Tracer. Generated only when teleprocessing is turned on. Secondary Tracer. Never written to tape or disk. Only used when teleprocessing is turned on.
NOTE: Structure code layouts shown in italic font were new or changed for 15 Digit DN.
E-10
Issue 27
May 2004
Summary of Changes to AMASE Tables

Introduction
This section summarizes changes to structure code layouts made for the 15 Digit DN feature.
Contents
The following sections describe in more detail the changes to the existing AMASE tables caused by the 15 Digit DN feature. Changes are grouped into the following categories:

New Tables - described in New AMASE Tables on page E-12 Movement of Fields between Tables - described in AMASE Record Fields Moved to a Different Table on page E-16 Modified Tables - described in Modified AMASE Tables on page E-31 Deleted Tables - described in Deleted AMASE Tables on page E-33 Other Changes - described in Other AMASE Table Changes on page E-35
Issue 27
May 2004
E-11
401-610-133A
New AMASE Tables

Introduction
This section lists new tables created for the 15 Digit DN feature.
Terminology
Most of these new tables existed before, sometimes even with the same name. Since the numbers were new, however, these were considered new tables.
Tables
Table 2 on page E-13 shows the new AMASE tables for the 15 Digit DN feature.
E-12
Issue 27
May 2004
Table AB-2. This new Table Number... 666
New AMASE Tables (Page 1 of 3) with Table Name... Date is used... It replaces Table... For a description of the New Table, see... AMASE Table 666 on page 4-80.
to indicate date.
6 (Date) for callrelated structure code layouts only. NOTE: Dates in tracer record structure code layouts still use AMASE Table 6.
2000
Number
to record various types of numbers.
13 (Numbering Plan Area), 14 (Originating Number), and 16 (Terminating NPA). None. (This is a new table.)
Table 2000 Number on page 4-115.
2001
Service Feature Code Indicator
to indicate whether there are zero, one, or multiple service feature codes associated with a record.
AMASE Table 2001 on page 4-118.
Issue 27
May 2004
E-13
401-610-133A
New AMASE Tables (Page 2 of 3) with Table Name... Service Feature Code is used... It replaces Table... For a description of the New Table, see... AMASE Table 2002 on page 4-119.
to indicate which feature or features are associated with a record.
12 (Service Feature), 364 (Special Routing Feature Indicator) and 365 (Service Feature).
NOTE:
Combination feature codes, such as 055 (PIN and Three-Way Calling) were eliminated. In place of the combination feature codes, the software used separate codes, for example, 800 and 010 to show PIN and ThreeWay Calling. AMASE Table 2003 on page 4-124.
2003
Radio/ Channel/Cell Information
to list channel technology type and radio, channel, and cell site number associated with a call. to record the trunk group and member information and DCS number associated with a call. to record the reason for communication failure.
335 (Radio/ Channel Number and Cell Site).
2004
DCS and Trunk Information
20 (Special Routing TNN) and 307 (Trunk Network Number)*.
2005
Communication Failure
337 (Radio Communication Failure Indicator).
E-14
Issue 27
May 2004
New AMASE Tables (Page 3 of 3) with Table Name... Billing Number is used... It replaces Table... For a description of the New Table, see... AMASE Table 2006 on page 4-136.
to record the Billing Number Type and Billing Number for the call. to record information about the origination of a call. to report a possibly fraudulent call. to record information about the termination of a call.
318 (Type of Credit Card).
2007
Origination Indicator
85 (Dialing Indicator) and 304 (Operator Dialed Indicator). 338 (Mobile Security Indicator). None. (This is a new table.)
2008
Mobile Security Indicator Termination Indicator
AMASE Table 2008 on page 4-141. AMASE Table 2009 on page 4-143
2009
* Some information was moved out of Table 244 into this table. Some information was moved out of Table 7 into this table.
Issue 27
May 2004
E-15
401-610-133A
AMASE Record Fields Moved to a Different Table

Introduction
The changes made in AMASE record structures for 15 Digit DN caused many fields to be moved from one table to another. This section lists the five existing AMASE tables from which fields were moved. For ease of use the five old tables are shown individually. For each field in each old table, the new AMASE table name, field name and field value is given.
Impacted AMASE Tables

Five AMASE tables had fields moved into new locations for the 15 Digit DN AMA Record structures. The tables are:
AMASE Table 7, Timing Indicator - described in Fields Moved Out of AMASE Table 7 on page E-17 AMASE Table 12, Service Feature Code - described in Fields Moved Out of AMASE Table 12 on page E-19 AMASE Table 364, Special Routing Feature Indicator - described in Fields Moved Out of AMASE Table 364 on page E-22 AMASE Table 365, Service Feature - described in Fields Moved Out of AMASE Table 365 on page E-24 AMASE Table 569, 5-Digit Context ID - described in Fields Moved Out of AMASE Table 569 on page E-30
E-16
Issue 27
May 2004
Fields Moved Out of AMASE Table 7

Introduction
AMASE Table 7, Timing Indicator, was changed in the 15 Digit DN AMA record structures. Some information in AMASE Table 7 was moved into Table 2002, Service Feature and into Table 2007, Origination Indicator. Some information remained in Table 7, Timing Indicator.
Table
Table 3 on page E-17 lists the name and value of each field from the old AMASE Table 7 and shows the new AMASE table location, BCD number, field name and field value for each corresponding field. Table AB-3. BCD # Value # Values Moved From Table 7 to Tables 7, 2002 and 2007 (Page 1 of 2) Meaning AMASE Table # BCD # Value # Meaning
BCD 1 Value=0 BCD 1 Value=1 BCD 1 Value=2 BCD 1 Value=4 BCD 2 Value=0 BCD 2 Value=2 BCD 3 Value=0
Not Used Timed Release Disconnect Table 7 BCD 1 Value=1 Timed Release Disconnect
Blind Unanswered Call Release Table 7 BCD 1 Value=2 Changeable No Answer Timer Table 7 BCD 1 Value=4
Blind Unanswered Call Release
Unanswered Call Release
Not Used Under Minimum Chargeable Duration Not Used Table 7 BCD 2 Value=2 Under Minimum Chargeable Duration
Issue 27
May 2004
E-17
401-610-133A
Table AB-3. BCD # Value #
Values Moved From Table 7 to Tables 7, 2002 and 2007 (Page 2 of 2) Meaning AMASE Table # BCD # Value # Table 2007 BCD 1 Value=1 Table 2007 BCD 1 Value=2 Table 2002 BCD 1-3 Value=304 Table 2002 BCD 1-3 Value=305 Meaning
BCD 3 Value=1 BCD 3 Value=3 BCD 3 Value=5 BCD 3 Value=6 BCD 4 Value=0 BCD 4 Value=1 BCD 4 Value=2 BCD 4 Value=6 BCD 4 Value=7
Activation
Activation
Deactivation
Deactivation
Call Waiting Call Back
Call Waiting Call Back
3-Way Call Back
3-Way Call Back
Not Used Charge Guard Table 7 BCD 4 Value=1 Table 2002 BCD 1-3 Value=307 Table 2007 BCD 2 Value=1 Table 2007 BCD 2 Value=1 Table 2007 BCD 4 Value=1 Charge Guard
Kill Call
Kill Call
Network Dial Tone
Network Dial Tone
Network Dial Tone and Charge Guard
Network Dial Tone
Charge Guard
BCD 5 Value=0 BCD 5 Value=9
Not Used APX Activation or Deactivation Table 2007 BCD 1 Value=3 APX Activation or Deactivation
E-18
Issue 27
May 2004

Introduction
AMASE Table 12, Service Feature Code, was deleted from the 15 Digit DN AMA record structures. The information in AMASE Table 12 was moved into the new AMASE Table 2002, Service Feature Code.
Multiple Service Feature Codes Split Apart

In the 15 Digit DN AMA record structures, single service feature codes that stood for multiple values were split apart into their individual entities. For example, the service feature code 154 in old AMASE Table 12 that stood for Last Call Return and 3-Way Calling was split apart into the following two service feature codes in the new AMASE Table 2002: 301 for Last Call Return and 010 for 3-Way Calling.
Table
Table 4 on page E-19 lists the name and value of all fields from the old AMASE Table 12 and shows the new name and value for the corresponding fields in the new AMASE Table 2002. Table AB-4. Values Moved From Table 12 to Table 2002 (Page 1 of 3) AMASE Table 12 Service Feature Code Value 000 010 012 014 055 Meaning No Service Feature Three-Way Calling Call Forwarding - Immediate (Terminating leg or flat rate) Call Forwarding - Busy/Dont Answer/No Page Response Call Forwarding - Immediate + Busy/Dont Answer/No Page Response Call Waiting Value 000 010 012 014 308 AMASE Table 2002 Service Feature Code Meaning No Service Feature Three-Way Calling Call Forwarding - Immediate (Terminating leg or flat rate) Call Forwarding - Busy/Dont Answer/No Page Response Deactivate All Call Forwarding
056
056
Call Waiting
Issue 27
May 2004
E-19
401-610-133A
Table AB-4.
Values Moved From Table 12 to Table 2002 (Page 2 of 3) AMASE Table 12 Service Feature Code AMASE Table 2002 Service Feature Code Value 075 Meaning PIN + Dynamic Outgoing Call Restrictions (DOCR)
Value 075
Meaning PIN + Dynamic Outgoing Call Restrictions (DOCR)
NOTE:
These two values were left combined because DOCR can only be done on a PIN. 083 089 097 100 103 Call Delivery to Call Waiting Feature Activation/Deactivation via CN Tandem Trunk Special Cellular Networking Call Waiting Plus Call Forwarding - Dont Answer 083 089 097 100 056 Call Delivery to Call Waiting CN Activation/Deactivation Tandem Trunk Special Cellular Networking Call Waiting If Conditional Call Forwarding Split Feature ON 153 Call Forwarding - No Reply If Conditional Call Forwarding Split Feature OFF 014 104 109 151 152 153 154 Mobile Station Test Abbreviated Dialing with AMA Short Message Service CF - Busy CF - No Reply Last Call Return and 3-Way Calling GLS Deactivation Last Call Return 104 109 151 152 153 301 010 063 301 Call Forwarding - Busy/Dont Answer/No Page Response Mobile Station Test Abbreviated Dialing with AMA Short Message Service Call Forwarding - Busy Call Forwarding - No Reply Last Call Return 3-Way Calling Mobile Inactive Trigger Last Call Return
156 301
E-20
Issue 27
May 2004
Table AB-4.
Values Moved From Table 12 to Table 2002 (Page 3 of 3) AMASE Table 12 Service Feature Code AMASE Table 2002 Service Feature Code Value 800 800 010 PIN PIN Three-way Calling PIN Call Forwarding - Immediate (Terminating leg or flat rate) PIN Call Forwarding - Busy/Dont Answer/No Page Response PIN Deactivate All Call Forwarding PIN CN Activation/Deactivation PIN Abbreviated Dialing with AMA PIN Call Forwarding - Busy PIN Call Forwarding - No Reply Information Services Gateway Extended Intelligent Peripheral Tandem Trunk Over the Air Activation (OTA) Special Cellular Networking Call Waiting Meaning
Value 800 801 PIN
Meaning
PIN and Three-way Calling
802
PIN and Immediate Call Forwarding
800 012 800 014 800 308 800 089 800 109 800 152 800 153 810 811 812 100 056
803
PIN and Conditional Call Forwarding
804
PIN and Immediate and Conditional Call Forwarding PIN and Feature De/Activation via CN PIN and Abbreviated Dialing with AMA PIN and Conditional Call Forwarding - Busy PIN and Conditional Call Forwarding - No Reply Information Services Gateway Extended Intelligent Peripheral Tandem Trunk Over the Air Activation (OTA) Special Cellular Networking (SCN) and Call Waiting (CW)
805
806
808
809
810 811 812 814
Issue 27
May 2004
E-21
401-610-133A

Introduction
AMASE Table 364, Special Routing Feature Indicator, was deleted from the 15 Digit DN AMA record structures. The information in AMASE Table 364 was moved into AMASE Table 2002, Service Feature Code.
Multiple Special Routing Feature Indicator Split Apart

In the 15 Digit DN AMA record structures, single special routing feature indicator codes that stood for multiple values were split apart into their individual entities. For example, code 8 in old AMASE Table 364 that stood for Increased Court Ordered Surveillance (ICOS) or Lawfully Authorized Electronic Surveillance (LAES) was split apart into two codes in the new AMASE Table 2002, 302 for Increased Court Ordered Surveillance (ICOS) and 306 for Lawfully Authorized Electronic Surveillance (LAES).
Table
Table 5 on page E-22 lists the name and value of all fields from the old AMASE Table 364 and shows the new name and value for the corresponding fields in the new AMASE Table 2002. Table AB-5. Values Moved From Table 364 to Table 2002 (Page 1 of 2) AMASE Table 364 Special Routing Feature Indicator Value 0 1 2 3 4 5 Not Used Special Routing Feature #1 Special Routing Feature #2 Special Routing Feature #3 Special Routing Feature #4 Special Routing Feature #5 001 002 003 004 005 Special Routing Feature #1 Special Routing Feature #2 Special Routing Feature #3 Special Routing Feature #4 Special Routing Feature #5 Meaning Value AMASE Table 2002 Service Feature Code Meaning
E-22
Issue 27
May 2004
Table AB-5.
Values Moved From Table 364 to Table 2002 (Page 2 of 2) AMASE Table 364 AMASE Table 2002 Service Feature Code Value 006 007 302 Meaning Special Routing Feature #6 Special Routing Feature #7 Increased Court Ordered Surveillance (ICOS) Lawfully Authorized Electronic Surveillance (LAES)
Special Routing Feature Indicator Value 6 7 8 Meaning Special Routing Feature #6 Special Routing Feature #7 Increased Court Ordered Surveillance (ICOS) or Lawfully Authorized Electronic Surveillance (LAES)
306
Issue 27
May 2004
E-23
401-610-133A

Introduction
AMASE Table 365, Service Feature, was deleted from the 15 Digit DN AMA record structures. The information in AMASE Table 365 was moved into the new AMASE Table 2002, Service Feature Code.
Multiple Service Feature Codes Split Apart

In the 15 Digit DN AMA record structures, single service feature codes that stood for multiple values were split apart into their individual entities. For example, the service feature code 034 in old AMASE Table 365 that stood for PIN and SR Deactivation was split apart into two service feature codes in the new AMASE Table 2002, 008 for Deactivate all Special Routing and 800 for PIN.
Table
Table 6 on page E-24 lists the name and value of all fields from the old AMASE Table 365 and shows the new name and value for the corresponding fields in the new AMASE Table 2000. Table AB-6. Values Moved From Table 365 to Table 2002 (Page 1 of 6) AMASE Table 365 Service Feature Value 000 001 002 003 004 005 006 007 008 Not Used Special Routing Feature #1 Special Routing Feature #2 Special Routing Feature #3 Special Routing Feature #4 Special Routing Feature #5 Special Routing Feature #6 Special Routing Feature #7 Deactivate All Special Routing 001 002 003 004 005 006 007 008 Special Routing Feature #1 Special Routing Feature #2 Special Routing Feature #3 Special Routing Feature #4 Special Routing Feature #5 Special Routing Feature #6 Special Routing Feature #7 Deactivate All Special Routing Meaning Value AMASE Table 2002 Service Feature Code Meaning
E-24
Issue 27
May 2004
Table AB-6.
Values Moved From Table 365 to Table 2002 (Page 2 of 6) AMASE Table 365 Service Feature AMASE Table 2002 Service Feature Code Value 009 Meaning Message Recording Service (MRS) Vendor Not Used 089 001 002 003 004 005 006 007 008 009 CN Activation/Deactivation Special Routing Feature #1 Special Routing Feature #2 Special Routing Feature #3 Special Routing Feature #4 Special Routing Feature #5 Special Routing Feature #6 Special Routing Feature #7 Deactivate All Special Routing Message Recording Service (MRS) Vendor SALSA SALSA MUSDN Customer Changeable Primary ESN MCCPE activation PIN Changed PIN Changed PIN Special Routing Feature 1
Value 009 010 011 012 013 014 015 016 017 018 019 020
Meaning Message Recording Service (MRS) Vendor Message Storage System (MSS) CN Feature Activation/ Deactivation CN Special Routing Feature #1* CN Special Routing Feature #2* CN Special Routing Feature #3* CN Special Routing Feature #4* CN Special Routing Feature #5* CN Special Routing Feature #6* CN Special Routing Feature #7* CN Deactivate All Special Routing* CN Message Recording Service Vendor MSS** Silent Administration of LSA (SALSA) CN SALSA* MUSDN Customer Changeable Primary Electronic Serial Number (MCCPE) activation CN MCCPE activation* PIN Changed PIN Changed & CN* PIN and SR Feature 1
021 022 023
021 021 023
024 025 026 027
023 025 025 800 001
Issue 27
May 2004
E-25
401-610-133A
Table AB-6.
Values Moved From Table 365 to Table 2002 (Page 3 of 6) AMASE Table 365 Service Feature AMASE Table 2002 Service Feature Code Value 800 002 PIN Special Routing Feature 2 PIN Special Routing Feature 3 PIN Special Routing Feature 4 PIN Special Routing Feature 5 PIN Special Routing Feature 6 PIN SR Feature 7 PIN Deactivate all Special Routing PIN Message Recording Service (MRS) Vendor PIN CN Activation/Deactivation PIN Special Routing Feature #1 PIN Special Routing Feature #2 PIN Special Routing Feature #3 Meaning
Value 028
Meaning PIN and SR Feature 2
029
PIN and SR Feature 3
800 003
030
800 004
031
800 005
032
800 006
033
800 007
034
PIN and SR Deactivation
800 008
036
PIN and Vendor MSS
800 009
037
PIN and CN de/activation
800 089
038
PIN and CN and SR 1*
800 001
039
800 002
040
800 003
E-26
Issue 27
May 2004
Table AB-6.
Values Moved From Table 365 to Table 2002 (Page 4 of 6) AMASE Table 365 Service Feature AMASE Table 2002 Service Feature Code Value 800 004 PIN Special Routing Feature #4 PIN Special Routing Feature #5 PIN Special Routing Feature #6 PIN Special Routing Feature #7 PIN Deactivate all Special Routing PIN Message Recording Service (MRS) Vendor PIN Silent LSA de(activation) PIN Silent LSA de(activation) PIN MUSDN Customer Changeable Primary ESN PIN MUSDN Customer Changeable Primary ESN Do Not Disturb de(activation) Do Not Disturb de(activation) PIN Do Not Disturb de(activation) Meaning
Value 041
Meaning PIN and CN and SR 4*
042
800 005
043
800 006
044
800 007
045
PIN and CN and SR deactivation*
800 008
046
PIN and CN and Vendor MSS*
800 009
047
PIN and Silent LSA de(activation)
800 021
048
PIN and CN and Silent LSA de(activation)* PIN and MCCPE activation
800 021 800 023
049
050
PIN and CN and MCCPE activation*
800 023 051 051 800 051
051 052 053
Do Not Disturb de(activation) CN and Do Not Disturb* PIN and Do Not Disturb
Issue 27
May 2004
E-27
401-610-133A
Table AB-6.
Values Moved From Table 365 to Table 2002 (Page 5 of 6) AMASE Table 365 Service Feature AMASE Table 2002 Service Feature Code Value 800 051 PIN Do Not Disturb de(activation) User Zone Tone PIN User Zone Tone SPINA SPINA SPINA PIN SPINA PIN User Zone Tone PIN User Zone Tone Mobile Inactive Trigger PIN Mobile Inactive Trigger Mobile Inactive Trigger Meaning
Value 054
Meaning CN and PIN and Do Not Disturb*
055 056
User Zone Tone PIN and User Zone Tone
055 800 055
057 058 059
SPINA SPINA & CN* SPINA & PIN
057 057 057 800
060
SPINA & CN & PIN*
057 800
061 062
CN and User Zone Tone* PIN and CN and User Zone Tone*
055 800 055
063 064
Mobile Inactive Trigger (formerly named Global Locator Service) PIN and Mobile Inactive Trigger (formerly named PIN and Global Locator Service) CN and Mobile Inactive Trigger (formerly named CN and Global Locator Service)* PIN and CN and Mobile Inactive Trigger (formerly named PIN and CN and Global Locator Service)* Flexible Alerting PIN and Flexible Alerting
063 800 063 063
065
066
800 063 067 800 067
PIN Mobile Inactive Trigger Flexible Alerting PIN Flexible Alerting
067 068
E-28
Issue 27
May 2004
Table AB-6.
Values Moved From Table 365 to Table 2002 (Page 6 of 6) AMASE Table 365 Service Feature AMASE Table 2002 Service Feature Code Value 067 800 067 Meaning Flexible Alerting PIN Flexible Alerting Preferred Language PIN Preferred Language Preferred Language PIN Preferred Language PIN PIN + Dynamic Outgoing Call Restrictions (DOCR) PIN PIN + Dynamic Outgoing Call Restrictions (DOCR) Call Transfer PIN Call Transfer Call Transfer PIN Call Transfer
Value 069 070
Meaning CN and Flexible Alerting* CN and PIN and Flexible Alerting*
071 072
Preferred Language PIN and Preferred Language
071 800 071
073 074
CN and Preferred Language* PIN and CN and Preferred Language* PIN and DOCR
071 800 071 800 075
075
076
CN and PIN and DOCR*
800 075
077 078
Call Transfer PIN and Call Transfer
077 800 077
079 080
CN and Call Transfer* PIN and CN and Call Transfer*
077 800 077
Cellular Networking (CN) will not be mapped to any service feature in AMASE Table 2002. This is because when structure code layouts x2332, x2333 or x2334 are used in the AMA record, it is obvious that CN was used.
Issue 27
May 2004
E-29
401-610-133A

Introduction
AMASE Table 569, 5-Digit Context ID, was deleted in the 15 Digit DN AMA record structures. The information in AMASE Table 569 was moved into the new AMASE Table 237, Generic Context Identifier.
Table
Table 7 on page E-30 lists the name and value of all fields from the old AMASE Table 569 and shows the new name and value for the corresponding fields in the new AMASE Table 237. Table AB-7. Values Moved From Table 569 to Table 237 AMASE Table 569 BCD # Value # Meaning AMASE BCD # Value # BCD 1-2 Value=01 BCD 1-2 Value=03 BCD 1-2 Value=05 BCD 3 Number of Significant Digits in the Next Field CDMA Circuit IP Services Indicator IWF Cause Code ANSI-41 DMH Redirection Indicator BCD 1-5 Value=90022 BCD 1-5 Value=90023 BCD 1-5 Value=90025 BCD 6-7 Value=3 Number of Significant Digits in the Next Field CDMA Circuit IP Services Indicator IWF C ause Code ANSI-41 DMH Redirection Indicator AMASE Table 237 Meaning
E-30
Issue 27
May 2004
Modified AMASE Tables

Introduction
Table 8 "Modified AMASE Tables" on page E-31 contains a list of AMASE tables that were modified for 15 Digit DN.
Modified Tables
Table 8 on page E-31 shows the AMASE tables that were modified for the 15 Digit DN feature. Table AB-8. Table number 6 Modified AMASE Tables (Page 1 of 2) Keeps the same name Date. What has changed? Date information used in all call-related structure code layouts was moved into a new table (AMASE Table 666). Table 6 is still used to show date in statistical entry and tracer record structure code layouts. Origination Indicator information was moved into a new table (2007). The Billing Number information is no longer being added to this table. Billing Number information is now stored in AMASE Table 2006 on page 4-136. For a description of the revised table, see... AMASE Table 6 on page 4-13.
Timing Indicator.
AMASE Table 7 on page 4-15. AMASE Table 32 on page 4-28.
32
11-Digit Number.
NOTE:
This table is still used in the Mobile Security Entry Structure Code Layout (x2415).
Issue 27
May 2004
E-31
401-610-133A
Table AB-8. Table number 237
Modified AMASE Tables (Page 2 of 2) Keeps the same name Generic Context ID What has changed? Information from the 5Digit Context ID Table (Table 569) was folded into the existing Generic Context ID table. DCS and Trunk information is no longer being added to this table. DCS and trunk information is now stored in AMASE Table 2004 on page 4-130. For a description of the revised table, see... AMASE Table 237 on page 4-39.
244
Trunk Identification.
NOTE:
This table is still being used for the Radio Information Module. 473 Time Type. A new time type value, 020, was added to identify Three-way Transition Elapsed Time. A new signalling type, Switch Virtual Circuit, was added for SVC trunks. AMASE Table 473 on page 4-68.
566
Calling Party Category
E-32
Issue 27
May 2004
Deleted AMASE Tables

Table
Table 9 on page E-33 shows the AMASE tables that were deleted for 15 Digit DN. Table AB-9. This old Table Number... 12 13 14 15 16 20 21 Deleted AMASE Tables (Page 1 of 2) with Table Name... was replaced by... For more about this, see... AMASE Table 2002 on page 4-119. AMASE Table 2000 on page 4-115. AMASE Table 2000 on page 4-115. AMASE Table 2007 on page 4-138. AMASE Table 2000 on page 4-115. AMASE Table 2004 on page 4-130. Module 621 - Digit Information Module on page 5-46. AMASE Table 2006 on page 4-136. AMASE Table 2006 on page 4-136. AMASE Table 2007 on page 4-138. Module 621 - Digit Information Module on page 5-46. AMASE Table 2007 on page 4-138.
Service Feature Code Numbering Plan Area (NPA) Originating Number Overseas Indicator Terminating NPA Special Routing TNN PAS Account Number
Table 2002 - Service Feature. Table 2000 - Number. Table 2000 - Number. Table 2007 Origination Indicator. Table 2000 - Number. Table 2004 - DCS And Trunk Information. Digits Recorded field in the Digit Information Module. Table 2006 - Billing Number Table 2006 - Billing Number Table 2007 Origination Indicator. a field called Digits Recorded in the Digit Information Module. Table 2007 Origination Indicator.
33 55 85 126
13-Digit Number Significant Digits in Next Field Dialing Indicator Digits String
304
Operator Dialed Indicator
Issue 27
May 2004
E-33
401-610-133A
Table AB-9. This old Table Number... 307 318
Deleted AMASE Tables (Page 2 of 2) with Table Name... was replaced by... For more about this, see... AMASE Table 2004 on page 4-130. AMASE Table 2006 on page 4-136. AMASE Table 2003 on page 4-124. AMASE Table 2005 on page 4-132. AMASE Table 2008 on page 4-141. AMASE Table 2002 on page 4-119. AMASE Table 2002 on page 4-119. NA AMASE Table 237 on page 4-39.
Trunk Network Number Type of Credit Card
Table 2004 - DCS And Trunk Information. Table 2006 Communications Failure. Table 2003 - Radio/ Channel/Cell Information. Table 2005 Communications Failure. Table 2008 - Mobile Security Indicator. Table 2002 - Service Feature. Table 2002 - Service Feature. Fields in the base structure code layouts. Table 237 - Generic Context ID. NOTE: Information from the 5-Digit Context ID Table was folded into the existing Generic Context ID table.
335
Radio/Channel Number and Cell Site Radio Communication Failure Indicator Mobile Security Indicator Special Routing Feature Indicator Service Feature Information Type 5-Digit Context ID
337
338 364
365 478 569
805
9-Digit Number
Table 2006 - Billing Number.
E-34
Issue 27
May 2004
Other AMASE Table Changes

Introduction
Explained in this section are other changes that impacted AMASE tables.
Fields Moved Into Modules

For the 15 Digit DN record structures, several fields were moved out of the base structure code layouts and into modules. (For a listing of these fields, see Fields Moved Into Existing Modules on page E-6.)
New AMASE Table

To give service providers the ability to record information to be used by the Support of Variable NSN Length per Trunk Group feature, a new AMASE table was added, Termination Indicator, AMASE Table 2009. Unlike the other tables listed in New AMASE Tables on page E-13, AMASE Table 2009 on page 4-143 adds new functionality to the AMASE record structures. This new functionality is the ability to record information associated with call terminations.
Empty Elements Added for Future Expansion

Some new or changed tables have empty elements or fields in them. These elements or fields are not currently used, but are placeholders for potential future use. For example, the element represented by BCD character 7 in AMASE Table 2007 on page 4-138 is not used now. This element is a placeholder for potential future use.
Issue 27
May 2004
E-35
401-610-133A
Summary of Changes to Modules

Introduction
This section lists the following types of changes to the existing AMA subsystem modules caused by the 15 Digit DN feature:

New Modules Renamed Module Deleted Modules
These changes are explained in the following sections.
E-36
Issue 27
May 2004
New Modules
Introduction
This section lists new modules for the 15 Digit DN feature. NOTE: Most of these new modules have existed before, sometimes even with the same name. However, since the numbers were updated to reflect the new information in the modules, these were considered new modules.
Table
Table 2 on page E-13 shows the new modules. Table AB-10. This new Module Number... 620 New Modules with Module Name... Service Feature Module is used... For a description of the module, see... Module 620Service Feature Module on page 5-41.
to record service feature code(s) for an AMA record in cases where there are multiple service feature codes for that record. to record strings of digits.
621
Module 621 - Digit Information Module on page 5-46. This replaced the old Digit Information Modules 1, 2, 3 (611-613). Module 622Cell Information Module on page 5-68. This replaced the old Cell Information Module, 335. Module 623Trunk Information Module on page 5-70. This replaced the old Trunk Information Module, 902.
622
Cell Information Module
to store information about the cell serving the call. to store information about the trunk associated with the call.
623
Issue 27
May 2004
E-37
401-610-133A
Renamed Module
Introduction
This section lists the renamed module for the 15 Digit DN feature.
Table
Table 11 on page E-38 shows the module that was renamed for the 15 Digit DN feature. Table AB-11. Renamed Module but this old Module Name... Has changed to this New Module name... For a description of the current module, see...
This old Module Number stays the same... 326
Auxiliary Digital Module
Auxiliary Time Module. The layout of the module is unchanged, but a new Time Type value was identified to reflect usage of the Three-Way Transition Elapsed Time.
Module 326 Auxiliary Time Module on page 5-24.
E-38
Issue 27
May 2004
Deleted Modules
Introduction
This section lists the deleted modules for the 15 Digit DN feature.
Table
Table 9 on page E-33 shows the modules that were deleted for 15 Digit DN. Table AB-12. Deleted Modules with Module Name... Basic Digital Module was replaced by... For more about this, see... Chapter 3, Structure Code Layouts.
This old Module Number... 325
No Module. This information was moved into fields in the base structure code layouts. No Module. This information was moved into fields in the base structure code layouts. the Cell Information Module (622).
332
Extended Information Module
Chapter 3, Structure Code Layouts.
335
Cell Information Module
Module 622Cell Information Module on page 5-68. Module 621 - Digit Information Module on page 5-46.
611 612 613 616
Digit Information Module 1 Digit Information Module 2 Digit Information Module 3 5-Digit Information Module
the Digit Information Module (621).
Issue 27
May 2004
E-39
401-610-133A
Table AB-12.
Deleted Modules with Module Name... Trunk Information Module was replaced by... For more about this, see... Module 623 Trunk Information Module on page 5-70. Chapter 3, Structure Code Layouts.
This old Module Number... 902
Trunk Information Module (623).
903
Calling Party Category
No Module. This information was moved into fields in the base structure code layouts.
E-40
Issue 27
May 2004
Index
Index
Numerics
15 Digit DN Feature, E-1E-40 deleted AMASE tables for, E-33 deleted modules for, E-39 impact on AMA documentation, E-3 impact on AMASE Tables, E-11E-35 impact on modules, E-36E-40 impact on structure code layouts, E-4E-10 modified AMASE tables for, E-31 new AMASE tables for, E-13 new modules for, E-37 3G-1X IP Service Option code, 34-9 3G-1X Low Speed Packet Data Service feature definition, B-68 5ESS DCS PRI, B-62 7- Digit AMA Block Sequence Number feature, 47-1 47-5
A
About this document, 1-lxvii availability, 1-lxxix conventions used, 1-lxxix how to use, 1-lxxix prerequisite skills and knowledge, 1-lxxviii reason for reissue, 1-lxviii, B-10 ADSS records, 25-7 AM 759 assert replacement of, B-60 AMA, 57-1 AMA Antenna Face Information for TDMA and Analog, B-132 AMA changes for, B-134 AMA Antenna Face Information for TDMA and Analog feature, 30-1 AMA block sequence number defined, 47-2 AMA Containing Incoming Automatic Number Identifi-
cation (AMANI) feature, 17-1 capabilities, 17-2 CPN incoming calls module2 fields, 17-3 CPNAD feature and AMANI feature interactions, 17-4 treatment of call forwarding calls, 17-4 treatment of call waiting calls, 17-4 treatment of special cellular networking calls, 174 AMA Enhancements, B-135 AMA changes for, B-137 AMA Enhancements of Home Zone Service Phase II and KTF Intelligent Network Service feature, 57-1 AMA event defined, 34-6 AMA Linking Functionality feature AMA changes for, B-47 availability, B-47 further information on, B-47 how it works, B-47 AMA record fields for AMA Antenna Face Information for TDMA and Analog, 30-3 AMA Record Generation for Redirecting Number feature AMA changes for, B-73 and the Redirecting Party Number (RDPN), B-73 description, B-73 further information on, B-73 AMASE Table 12 Service Feature, E-19, E-22, E-24 AMASE Table 471, 20-3 Analog Fax Support for CDMA feature AMA changes for, B-95, B-107 and the CDMA Circuit Mode Data Services feature, B-94, B-106 availability, 25-2, B-94, B-106 documentation, 25-2, B-95, B-107 feature description, 25-2, B-94, B-106 how it works, 25-2, B-94, B-106 Analog/digital usage billing feature auxiliary digital module fields, 16-4 benefits, 16-2 ANSI-41 Billing Module feature, 38-138-10 AMA changes for, B-128 ANSI-41 Billing Module with Service Type feature AMA impact, B-78 and the ANSI-41 BIlling Module feature, B-77 definition, B-77 further information, B-77
Issue 27
May 2004
IN-1
000-111-222
use of terms Service Type and Service ID, B-77 ANSI-41 Rev C Call Transfer feature AMA changes for, B-92, B-104 availability, B-91, B-103 documentation, B-91, B-103 feature description, B-91, B-103 Antenna face information. See AMA Antenna Face Information for TDMA and Analog Feature. Append Module 331 to 1336 AMA Record feature AMA changes for, B-71 description, B-71 further information on, B-71 Authentication Indicator in AMA feature feature description, B-98 Automatic Number Identification (ANI) feature. See AMA Containing Incoming Automatic Number Identification (AMANI) feature AUTOPLEX AMA Tape IBM Label Y2K Compliance feature AMA changes for, B-98, B-109 feature description, B-98, B-109
B
Billing levels. See LSA128 feature Billing Number field MIN in, 33-4 BIN Module, 37-10
C
Call Waiting Call Back, B-132, B-134 AMA changes for, B-134 Calling Name Presentation feature, 32-132-5 AMA impact of, 32-4 modules used, 32-4 Calling Name Presentation for TDMA feature (Phase 1) AMA changes for, B-119 Calling number identification presentation (CNIP) feature. See Calling number identification presentation and restriction (CNIPR) capabilities Calling number identification presentation and restric-
tion (CNIPR) capabilities CPN incoming calls (module1, and module2) module fields, 18-3, 32-4 CPN outgoing calls module fields, 18-3 CPNAD feature and AMANI feature interactions, 18-8 criteria for appending the CPN incoming calls (module1, or module2) modules to AMA records, 18-3 criteria for appending the CPN outgoing calls module to AMA records, 18-3 ecp form fields, 18-6 Calling number identification restriction (CNIR) feature. See Calling number identification presentation and restriction (CNIPR) capabilities CDMA Circuit IP Services feature 45-145-9 optional feature document for, 45-2 CDMA Circuit-Mode Data Service See Circuit-Mode Data Service CDMA Full IMSI feature, 39-139-6 AMA impact of, 39-4 optional feature document for, 39-1, 43-1 CDMA Meter Pulse feature AMA changes for, B-81, B-82 availability, B-81 description, B-81 further information, B-81 CDMA Network Directed System Selection feature AMA changes for, B-59 availability, B-59 definition, B-59 how it works, B-59 CDMA Packet-Mode Data Services feature AMA changes for, B-67, B-126 See also Packet-Mode Data Service, B-67 CDMA Private Network and User Zone feature, 24-2, 24-5 AMA changes for, B-127 Cell Origination Request Time Stamps feature AMA changes for, B-42 feature description, B-41 for further information, B-41 how it works, B-41 Changeable No Answer Timer feature AMA impact, B-79 definition, B-78 for further information, B-78 Charge Class Population in AMA feature, B-48 AMA changes for, B-48
IN-2
Issue 27
May 2004
Index
availability, B-48 dependency on 15 Digit DN AMA record structures, B-48 how it works, B-48 use of charging class, B-48 charging class, B-48 Circuit Data IWF Indicator in AMA feature AMA changes for, B-93, B-105 and the CDMA Circuit-Mode Data Services feature, B-92, B-104 documentation on, B-92, B-104 feature description, B-92, B-104 Circuit Mode Data Services feature used by Analog Fax Support for CDMA feature, B-94, B-106 used by Circuit Data IWF Indicator in AMA feature, B-92, B-104 Circuit-Mode Data Service, 25-125-22, 40-20, B132 ADSS records for, 25-7 AMA changes for, B-132 AMA impact, 25-7, 34-4 definition, 25-2 how it works, 25-3, 34-11 interworking function (IWF), 25-3 mobile data path leg, 25-4 PSTN data path leg, 25-4 CNAP. See Calling Name Presentation feature CNIPR capabilities. See Calling number identification presentation and restriction (CNIPR) capabilities Conditional Call Forwarding Split (CCF Split), B-139 Connect Resource Operations (Terminations) feature, B-55 AMA changes for, B-58 availability, B-57 dependency on 15 Digit DN AMA record structures, B-57 how it works, B-55 CPN Acceptance/Delivery (CPNAD) feature definition of, 18-2 CPN Acceptance/Delivery (CPNAD) feature. See Calling number identification presentation and restriction (CNIPR) capabilities CPN incoming calls module-1, 18-4 CPN incoming calls module-2, 18-4 CPNAD See CPN Acceptance/Delivery (CPNAD) feature, 18-2 Customized ESN Format in AMA Record feature, 53153-7, B-33
AMA changes for, B-33 AMA impacts, 53-3 description, 53-2 feature dependencies, 53-5 feature interactions, 53-6 related documentation, 53-7 service feature code for, 53-3 use of 2-step decimal format, 53-2
D
DCCH Non-Public Network Charging Area AMA Capability (NPNI), B-138 AMA changes for, B-138 Digit Information Module, 22-3, 33-7, 33-9, 39-5, 435 storing the MIN in, 33-6 with ANSI-41 DMH Redirection Indicator, 38-8 with Far End Release Cause Values for ISUP and R2 in the AMA Record feature, 52-3, 54-8 with Speech Handler Trunk Information in AMA feature, 49-3 Digit Information Module 1, 36-12, 38-7 Digital Audio Tape, B-139 Digital Event Module, 23-423-5, 54-5 Digital Radio Module, D-1 Donor Switch defined, 36-4 DRM number, D-1
E
Enhanced Kill Call, B-132 AMA changes for, B-133 Enhancement to Far End Release Cause Values in AMA Records feature, 52-1 AMA changes for, B-32 AMA impacts, 52-3 feature description, 52-2, B-31 module generation criteria, 52-4 use of Digits Recorded field, 52-4, 52-5 Event Descriptions defined, 34-8
Issue 27
May 2004
IN-3
000-111-222
Event Type defined, 34-6
I
IAMA, B-38 IBM Tape Label, Y2K change for, B-98, B-109 ICOS feature, 41-2 immediate billing record, 25-7 Increase AMA Record Storage with DAT feature AMA changes for, B-85 AMA impact, B-85 definition, B-84 Initial cell-based billing feature cell information module fields, 21-3 criteria for appending the cell information module to AMA records, 21-3 Intermediate AMA for LDC feature AMA changes for, B-39 feature description, B-38 further information, B-38 Intermediate IAMA for LDC feature how it works, B-38 Inter-MSC LSA (IMLSA) feature, 19-8 International Mobile Station Identity compared to MIN and DN, 43-2 makeup of, 43-2 Internet access calls, B-92, B-104 distinguishing from other calls, B-92, B-104 Inter-Working Function, 25-325-5, 40-340-5 Inter-Working Function and the mobile data path leg, 25-4, 40-4 Inter-Working Function and the PSTN data path leg, 25-4, 40-4 IP Billing feature 44-144-7 AMA impact of, 44-4, B-65, B-80 definition of, B-64, B-80 further information on, B-65, B-80 optional feature document for, 44-2, 44-3 IS53 Preferred Language feature AMA changes for, B-93, B-105 availability, B-93, B-105 documentation, B-93, B-105 feature description, B-93, B-105 Phase 2, B-93, B-105 IS-826 Locally-Allowed Specific Digit String Trigger feature, 50-150-8 AMA changes for, B-22 AMA impact, 50-5
F
Far End Release Cause Values for ISUP and R2 in the AMA Record feature, 52-1 AMA changes for, B-72 AMA impacts, 52-3 description, 52-2, B-72 further information on, B-72 module generation criteria for, 52-3, 54-8 fax AMA changes to support, B-95, B-107 Analog Fax Support for CDMA feature, B-94 availability, B-94 dependency on the CDMA Circuit Mode Data Services feature, B-94, B-106 feature description, B-94, B-106 for further information, B-95, B-107 new CDMA Assigned Service Options for, B-94, B-106 feature description, 57-2 Flexible Alerting feature, 37-137-12 AMA changes for, B-123 definition, 37-4
G
Global Locator Service, B-135 and the Mobile Inactive Trigger feature, B-96, B107 codes as changed by Mobile Inactive Trigger feature, B-136 feature description, B-136 further information about, B-96, B-108
H
HDR1 field, on IBM Tape Label, B-98, B-109
IN-4
Issue 27
May 2004
Index
feature dependency, 50-7 feature description, 50-2, B-22, B-23 further information, 50-1 module generation criteria for, 50-5 IS-826 Prepaid Base feature, 48-148-5 AMA changes for, B-41 AMA impacts, 48-3 feature description, 48-2, B-40 for further information, 48-1 IS-848 Billing Indicator, 50-4 IS-848 Charge Information, 50-4, 50-5
LSA128 feature, 19-219-10
M
Measurement Data in Call Records feature feature description, B-43 further information, B-43 Metered Billing (MB), B-138 AMA changes for, B-138 MIN in Billing Number field, 33-4 mobile data path leg, 25-4, 40-4 Mobile Directory Number (MDN) defined, 36-4 Mobile Identification Number (MIN), 43-2 Mobile Inactive Trigger feature AMA changes for, B-97, B-108 and the Global Locator Service feature, B-96, B107 availability, B-95 feature description, B-96, B-107 further information about, B-96, B-108 value of service feature codes for, B-136 Mobile Loop Back Test, B-135 AMA changes for, B-136 mobile security indicator, B-60 Mobile Station Identifier (MSID) defined, 36-4 Mobility defined, 36-4 Module 334, 54-5 Module Generation Criteria for CPN Incoming Calls See changes for Append Specific AMA Modules for Structure Code x2351, 18-4 Module Generation Criteria for Wireless Number Portability KTFWNPT, 36-9 Multiple voice coding AMA changes for, B-138 Multiple voice coding feature, 23-123-6, B-138 benefits, 23-2 digital event module, 23-423-5 expanded AMA functionality, 23-423-5 feature description, 23-223-3
J
Jurisdiction Information Parameter (JIP) , 36-12 defined, 36-4
K
KTF Home Zone Service Phase 2 feature AMA changes for, B-25 how it works, B-24
L
LAES, 42-5 LAES feature 42-142-6 AMA changes for, B-83 AMA impact, 42-4 description, 42-2 further information, 42-1, B-83 module generation criteria for, 42-5 Limited Service Area 128 (LSA128), B-139 Link Sequence Number, B-47 Location portability, 36-2 Location Routing Number (LRN) defined, 36-4 logical radio number, D-1
Issue 27
May 2004
IN-5
000-111-222
N
No Charge Calls in AMA Record feature, 31-131-4 AMA changes for, B-112 feature description, 31-2 No Charge Calls in AMA Record for Brazil Optional Feature, 31-1 Non-Ported Number defined, 36-4 North American Numbering Plan (NANP), 43-2 Number Portability SCP defined, 36-4 Number Portability Trigger defined, 36-4
Private numbering plan (PNP) non-dialable digits in HLR return results feature capabilities, 22-2 PSTN data path leg, 25-4, 40-4
R
R2 and ISUP Charge Indication in AMA feature, B-49 AMA changes for, B-50 availability, B-49 dependency on 15 Digit DN AMA record structures, B-49 how it works, B-49 Radio Information Module, 28-5 Recipient Switch defined, 36-5 Redirecting Party Number definition, B-73 Remote Feature Control feature AMA changes for, B-53 availability, B-52 definition of, B-52 how it works, B-52
O
Origination call, PDP leg no ADSS record for, 25-7 Over the Air Activation feature AMA changes for, B-117
P
Packet-Mode Data Service definition, 34-2, B-125 payphone, B-81 payphone provider billing of, B-81 PDP leg no ADSS records for, 25-7 Personal Communications Services (PCS) Minicell, B-140 physical radio number vs logical radio number, D-1 Ported Block defined, 36-5 Primary Rate Access defined, 46-2 Primary Rate Interface defined, 46-2
S
Selectable Mode Vocoder on PHV feature, 54-1, 5410, 55-1 56-1 56-5 AMA changes for, B-23 AMA impacts, 54-3, 55-3, 56-3 AMA storage requirements, 54-2 further information on, 54-1, 55-1, 56-1 how it works, 54-2, 55-2, 56-2, B-23 use of Digits Recorded field, 54-7 Separation of MSID-MDN feature AMA changes for, B-121 Service ID versus Service Type, B-77 Service Options defined, 34-8 Service portability, 36-2 service provider portability, 36-2 Service Type
IN-6
Issue 27
May 2004
Index
versus Service ID, B-77 Seven Digit AMA Block Sequence Number feature description, B-28, B-37 Seven Digit AMA Block Sequence Number feature, 47-147-5 AMA changes for, B-28, B-38 AMA impact, 47-4 feature description, 47-2 further information, 47-1 hardware required, 47-3 how it works, 47-3 software changes for, 47-3 Short Message Service, B-135 AMA changes for, B-135 Silent administration of LSA (SALSA) feature, 19-3, 19-11 SKT PrePaid Service feature, B-58 AMA changes for, B-59 availability, B-58 dependency on 15 Digit DN AMA record structures, B-58 Special features field definition changes for automatic roamer greeting, 15-3 for dynamic routing, 12-3 for message recording service (MRS) usage, 13313-8 for voice channel segment, C-4 Specific Called Party Digit String Trigger feature, 50150-8 AMA changes for, B-29 AMA impact, 50-3 feature dependency, 50-7 feature description, 50-2 further information, 50-1 how it works, B-28 module generation criteria for, 50-3 Speech Handler Trunk Information in AMA feature, 49-149-5, 57-1 AMA changes for, B-27 AMA impact, 49-3, 57-3 feature description, 49-2 how it works, B-27 module generation criteria for, 49-3, 57-3 Subscriber number resetting to ANI or MIN, 33-5 Subscriber PIN Access (SPINA), B-140 Support New Service Option of 13K Service feature description, B-40 Support New Service Option of 13K Service feature AMA changes for, B-40
Support of ISUP Release Cause Values 21, 28, 34, 42, 102, 111, and Local Release Cause Values in AMA Records feature AMA changes for, B-34 feature description, B-34 for further information, B-34 surveillance techniques, 41-2 Switch identification module, 28-4, 28-8
T
Tandem Trunk Switching and ADSS records, 25-7 TDMA Channel Usage Tracking Tool feature, 51-1 51-8 AMA changes for, B-30 AMA impacts, 51-4 feature description, 51-2, B-29 further information, 51-3, B-29 TDMA Circuit-Mode Data Service, 40-2 AMA impact, 40-6 TDMA Circuit-Mode Data Services feature AMA changes for, B-63, B-79 further information on, B-63, B-79 TDMA Flexent cells radio number for, D-1 TDMA IMSI feature 43-143-6 AMA changes for, B-51, B-66, B-84 AMA impact, B-51, B-66, B-84 AMA impact of, 43-4, 45-5 further information, B-50, B-66, B-84 to, B-11 Trunk Information Module Changes for Append Specific AMA Modules for Structure Code x2351, 28-7 See changes for Append Specific AMA Modules to Structure Code x2351, 28-7 Trunk information Module See changes for Append Specific AMA Modules to Structure Code x2351, 28-7 TSI Bridging feature 41-141-8 AMA changes for, B-82 AMA impact, 41-6, B-82 description, 41-2 further information, 41-1, B-82
Issue 27
May 2004
IN-7
000-111-222
module generation criteria for, 41-6 Two-step decimal format, 53-2 Type of Technology field, 20-3
U
Use of CPN Incoming Calls Module-2 See x2351 for Append Specific AMA Modules to Structure Code x2351, 17-3 User Interactive Services feature AMA changes for, B-45 availability, B-44 dependency on 15 Digit DN AMA record structures, B-44 User Interactive SMS feature, B-44 User Zone definition, 24-3 User Zone Capability, 24-124-16 User Zone for Analog, 24-7 User Zone for CDMA, 24-12 User Zone for TDMA, 24-7
wireless payphone, B-81 Wireline Feature Transparency, B-135 AMA changes for, B-136 Wireline feature transparency benefits, 29-3 expanded AMA functionality, 29-4 feature description, 29-229-3
V
Voice Privacy use of AMASE Table 471, 20-3 Voice privacy feature capabilities, 20-2
W
WIN-Based Flexible Alerting feature AMA changes for, B-42 AMA for, B-42 feature description, B-42 for further information, B-42 Wireless Number Portability, 36-136-14 Wireless Number Portability Module 36-936-11 Wireless number portability module, B-20
IN-8
Issue 27
May 2004

Flexent /autoplex Wireless Networks Executive Cellular Processor (ECP) Release 22.0

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Flexent /autoplex Wireless Networks Executive Cellular Processor (ECP) Release 22.0

Загружено:

Авторское право:

Доступные форматы

Flexent/AUTOPLEX Wireless Networks Executive Cellular Processor (ECP) Release 22.

0 Automatic Message Accounting Formats Description Volume 2

Lucent TechnologiesProprietary See notice on first page

About This Document

Dynamic Routing Feature

12-1 12-1 12-1 12-2 12-2 12-2 12-2 12-2 12-3

Issue 27 May 2004

Message Recording Service Feature

Lucent TechnologiesProprietary See notice on first page

Abbreviated Dialing with AMA Feature

Automatic Roamer Greeting Feature

Analog/Digital Usage Billing Feature

16-1 16-1 16-1 16-2

Introduction For Further Information Feature Description

Lucent TechnologiesProprietary See notice on first page

AMA Containing Incoming Automatic Number Identification (AMANI) Feature

Calling Number Identification Presentation and Restriction Capability Feature 18-1

Lucent TechnologiesProprietary See notice on first page

Lucent TechnologiesProprietary See notice on first page

Voice Privacy Feature

20-1 20-1 20-1 20-2

Introduction For Further Information Feature Description

Lucent TechnologiesProprietary See notice on first page

Initial Cell-Based Billing Feature

Multiple Voice Coding Feature

User Zone Capability

24-1 24-1 24-2

24-2 24-2 24-3 24-3 24-3 24-3 24-3

Lucent TechnologiesProprietary See notice on first page

Lucent TechnologiesProprietary See notice on first page

CDMA Circuit-Mode Data Services Feature

Lucent TechnologiesProprietary See notice on first page

25-21 25-22 25-22 25-22 25-22

Virtual Systems AMA Event Recording Feature

Metered Billing Feature

Lucent TechnologiesProprietary See notice on first page

27-4 27-4 27-4 27-4 27-5 27-6 27-9

AMA Enhancements Feature

Lucent TechnologiesProprietary See notice on first page

Wireline Feature Transparency Feature

AMA Antenna Face Information for TDMA and Analog Feature

Lucent TechnologiesProprietary See notice on first page

31-1 31-1 31-1 31-2 31-2 31-2 31-3 31-3 31-4

Calling Name Presentation and Restriction Feature

MIN-MDN Separation Feature

33-1 33-1 33-1 33-2 33-2 33-2

Lucent TechnologiesProprietary See notice on first page

Lucent TechnologiesProprietary See notice on first page

Lucent TechnologiesProprietary See notice on first page

Wireless Number Portability Feature

Lucent TechnologiesProprietary See notice on first page

Flexible Alerting Feature

Lucent TechnologiesProprietary See notice on first page

Lucent TechnologiesProprietary See notice on first page

38-8 38-8 38-8 38-9 38-10

CDMA Full IMSI Feature

39-4 39-5 39-5 39-5 39-5 39-5 39-6 39-6

TDMA Circuit-Mode Data Services Feature

Lucent TechnologiesProprietary See notice on first page

Lucent TechnologiesProprietary See notice on first page

Feature Dependencies Hardware Requirements Feature Interactions

40-21 40-21 40-21