401-601-009

Lucent Technologies - ProprietaryThis document contains proprietary information of

Lucent Technologies and is not to be disclosed or used except inaccordance with applicable agreements

Copyright 2005 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

Flexent/AUTOPLEX Wireless NetworksAutonomous and Enhanced Registrationand Related FeaturesOptional Feature Description

Release 24, Software Update 24-0002

401-601-009Issue 10

August 2005

Copyright 2005 Lucent Technologies. 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.

Mandatory Customer Information

Interference information: Part 15 of FCC rulesNOTE: 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 documentation, 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 the customer to 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

All trademarks and service marks specified herein are owned by their respective companies.

Autonomous and Enhanced Registration and Related Features

Contents 401-601-009, Issue 10

August 2005 Lucent Technologies Proprietary Page iiiSee notice on first page

Contents Page

1. Introduction 1

Benefits 1

Reason for Reissue 2

Availability 2

To Obtain Technical Support, Documentation, and Training or Submit Feedback 2

2. Prerequisites 3

HLR Configuration 3

Software Requirements 3

Hardware Requirements 3

3. Feature Description 3

Autonomous Registration (AR) for CDMA 4

Geographic-Based and Time-Based AR (Analog, TDMA, CDMA) 5

Registration Terms 6

Mobile Registration Specifications 6

AR Overload Algorithm (Analog) 6

AR Limitations 7

Setting Registration Boundaries Through Staggered regid Values (Analog) 9

Enhanced Registration (ER) & Interim Standards 12

Autonomous Registration Improvements (Analog Only) 13

What ARI Does 13

ARI & Call Processing 17

No Paging Inactive Mobiles (NPIM) 18

Power Down in System with No VLR 19

Introduction 19

Functionality 19

Benefits 19

How the feature operates 1919

19

19

19

19

18

17

13

13

12

9

7

6

6

6

5

4

3

3

3

3

3

2

2

2

1

1

Contents Page


Page iv Lucent Technologies Proprietary August 2005See notice on first page

4. Feature Interactions 21

Mutually Exclusive FAFs (MAS) 22

5. Subscriber Perspective 22


6. Service Provider Perspective 22

FoCC and Optional Features (Analog) 22


7. System Interaction 23

System Interaction - AR 23

AR - Cellular Geographic Service Area (cgsa) Form 24

Series II Cell (cell2) Form 25

AR - Executive Cellular Processor (ecp) Form 27

AR - Cellular Network (net) Form 29

AR - Network Neighbor (nnbr) Form 30

AR for CDMA Forms 30

AR - Cellular Geographic Service Area (cgsa) Form 31

AR - Series II Cell (cell2) Form 33

AR - Series II Cell Equipage Setup (ceqsu2) Form 36

System Interaction - ER in DCCH Forms (TDMA) 36

ER - Cellular Geographic Service Area (cgsa) Form 37

ER - Series II Cell (cell2) Form 38

ER - Series II Cell Equipage Setup (ceqsu2) Form 41


sub form 42

References 42

8. Feature Implementation 42

General Implementation/Activation 43

Setting the Time-Based Registration Interval 4343

43

42

42

42

41

41

38

37

36

36

33

31

30

30

29

27

25

24

23

23

23

22

22

22

22

22

21


August 2005 Lucent Technologies Proprietary Page vSee notice on first page

Contents Page

Adjusting the System Clock 44

Implementing/Activating AR 44

Activate/Deactivate AR (Analog, CDMA, TDMA) 44

Implementing Geographic-Based AR (CDMA,TDMA) 45

AR over ACC Forward Control Channel (Analog, TDMA) 45

Reducing FoCC Activity 45

AR over Digital Control Channel (TDMA) 46

AR over CDMA Paging Channel (CDMA) 47

Other AR Implementation Concerns 47

Implementing/Activating ER 50

ER over the ACC Forward Control Channel (TDMA) 50

ER over the Digital Control Channel (TDMA) 50

ER over the Digital Control Channel (DCCH) - Deregistration 50

ER on the CDMA Paging Channel 50

Resource Usage & AR/ER Implementation 52

Implementing the Power Down in System with No VLR feature 52

Activating the feature 52

9. Monitoring Registrations 53

Service Measurements (SM) for AR/ER (Analog, CDMA, TDMA) 53

Analog Control Channel AR/ER Service Measurements (Analog) 56

Feature Activation Files (FAFs) 57

No Paging for Inactive Mobiles feature 57

Power Down in System with No VLR feature 58

10. Supplemental Information 58

Abbreviations 58

References 61

11. Appendix A - History of Revisions 61

Introduction 61

Issue 9 6161

61

61

61

58

58

58

57

57

56

53

53

52

52

52

50

50

50

50

50

47

47

46

45

45

45

44

44

44

Contents Page


Page vi Lucent Technologies Proprietary August 2005See notice on first page

12. Appendix B - Registration Features and Technologies 62

13. Appendix C - Registration Terms 63

14. Appendix D - Setting AR Parameters 65

Other database Fields 66

15. Appendix E - ARmon Support Tool 7171

66

65

63

62

Figure Page

401-601-009, Issue 10

August 2005 Lucent Technologies Proprietary Page viiSee notice on first page

A. Example of Registration Flow 4B. Example FoCC Occupancy for Series II Paging Load and AR Rates 8C. Example Cell Site Offset Configuration for a System with a Single MSC 10D. Example Cell Site Offset Configuration for a System with Three MSCs 10E. Multiple Registrations Event Flow at the HLR 15F. Multiple Registrations Event Flow at the VLR 16G. Example of cgsa Form (Screen 3) ECP Release 17.0 24H. Example of cell2 Form (Screen 9) ECP Release 17.0 25I. Example of ecp Form (Screen 1) ECP Release 17.0 27J. Example of ecp Form (Screen 15) ECP Release 17.0 28K. Example of net Form (Screen 1) ECP Release 17.0 29L. Example of nnbr Form (Screen 1) ECP Release 17.0 30M. Example of cgsa Form (Screen 1) ECP Release 17.0 31N. Example of cgsa Form (Screen 2) ECP Release 17.0 32O. Example of cell2 Form (Screen 1) ECP Release 17.0 33P. Example of cell2 Form (Screen 9) ECP Release 17.0 34Q. Example of ceqsu2 Form (Screen 1) ECP Release 17.0 36R. Example of cgsa Form (Screen 1) ECP Release 17.0 37S. Example of cell2 Form (Screen 1) ECP Release 17.0 38T. Example of cell2 Form (Screen 9) ECP Release 17.0 39U. Example of cell2 Form (Screen 10) ECP Release 17.0 40V. Example of ceqsu2 Form (Screen 1) ECP Release 17.0 4141

40393837363433323130292827252416151010

84

Figure Page

401-601-009, Issue 10

Page viii Lucent Technologies Proprietary August 2005See notice on first page

Table Page

401-601-009, Issue 10

August 2005 Lucent Technologies Proprietary Page ixSee notice on first page

1. ARI Registration Cancelled Messages 142. ARI Call Processing Scenarios 173. Zone Timer Value with Minutes 354. Related RC/V Forms 415. Related fields in the sub form 426. Typical Registration Traffic for an MSC with 100,000 Home Subscribers 447. AR/ER Service Measurements Counts 538. Other Related Service Measurements Counts 579. Registration Features and Respective Technologies 6210. cell Form Parameters for AR 6511. cgsa Form Parameters for AR 6612. net Form Parameters for AR 6713. net Form Paging Flag Summary for AR 6714. nnbr Form Parameters for AR 6815. ecp form Parameters for AR 6916. cgsa form Parameter for ER 6917. cell2 Form Parameters for ER 7018. ceqsu2 Form Parameter for ER 7070

7069696867676665625753444241351714

Table Page

401-601-009, Issue 10

Page x Lucent Technologies Proprietary August 2005See notice on first page

401-601-009, Issue 10

August 2005 Lucent Technologies Proprietary Page 1See notice on first page

1. Introduction

Registration allows a mobile to send its location information to the current serving Mobile Switching Center (MSC) for validation purposes and provides other pertinent call processing information. All mobiles have the capability to register, as described in the EIA-553 mobile specifications. Registration is also an important capability for Multiple Systems call delivery as described in 401-661-010, Multiple Systems Description and Implementation Guidelines.

Registrations can be solicited from homing mobiles only, roaming mobiles only, or both. Homing mobiles (from a cell site perspective) are defined as mobiles with the same System Identification (SID) stored in their memory as that of the serving system. Roaming mobiles are defined as mobiles with a different SID stored in their memory.

With the No Paging Inactive Mobile (NPIM) feature on, mobiles that are not subscribed to the Mobile Activity Supervision (MAS) feature can receive secondary treatment immediately without paging the mobiles for incoming calls to a mobile that is marked inactive. If no secondary treatment exists, the No Page Response announcement is played. To operate the NPIM feature, the Enhanced Registration feature must be active in the system.

The Power Down in System with No Visitor Location Register (VLR) feature allows the MSC to send the Mobile Station Inactive (MSINACT) message to the Home Location Register (HLR) if a power down registration is detected in a Lucent Technologies MSC and there is no VLR for that mobile. Currently, if a power down registration from a mobile is received in a Lucent Technologies MSC and there is no VLR associated with that mobile, then no MSINACT message is sent to the HLR.

Benefits

The Autonomous Registration (AR) feature facilitates the mobile registration process through pre-call validation of the mobile. Call time registrations are not relied upon. AR provides the ability to automatically page and deliver subscriber calls to the system they are roaming in (when combined with Multiple Systems). AR also supports reduction of the load on paging channels (elimination of the need to do flood paging) through updates of the mobile location in the home systems subscriber (sub) record. As a result, the system pages the mobile at the MSC where it was last seen. The reduction in unnecessary paging traffic also contributes to reduced call failures and blockages.

The Enhanced Registration (ER) feature gives the MSC a more accurate view of the subscribers location and activity status. Applications of this capability can allow the MSC to provide immediate secondary treatment (such as call forwarding, voice mail, messaging) when the mobile is known to be inactive. Features based on the ER capability also help the MSC to improve paging channel efficiency by paging only in the precise location area in which the mobile is known to be active.

401-601-009, Issue 10

Page 2 Lucent Technologies Proprietary August 2005See notice on first page

Because the NPIM feature provides immediate secondary treatment to subscribers for an incoming call to a mobile that is marked inactive, this feature is particularly beneficial to customers who are not subscribed to the MAS feature.

The Power Down in System with No VLR feature allows the MSC to send the MSINACT message to the HLR if a power down registration is detected in a Lucent Technologies MSC and there is no VLR for that mobile. Providing this capability will help to preserve paging channel resources by not paging the mobile at its last seen MSC (MSC where the mobile was last registered). Lucent Technologies assigns a unique Feature Identifier (FID) to each feature. The FID of the Power Down in System with No VLR feature is FID 12182.0.

Reason for Reissue

This document is being reissued to include information on the Power Down in System with No VLR feature. See Power Down in System with No VLR on page 19 for a description of this feature.

Availability

The Autonomous Registration Improvements (ARI) feature is available in Executive Cellular Processor (ECP) Release 17.1. or later.

The NPIM feature is available in ECP Release 14.0 and Software Update (SU) 00-0001.

The Power Down in System with No VLR feature is available in ECP Release 24.0 with SU 24-0002. The Power Down in System with No VLR feature is available in all markets.

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 at the following URL:

https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/customer.support/customer.support_toc.pdf

That document explains how to

contact Lucent Technologies to obtain technical support

register as an authorized user of the Lucent Technologies Wireless Networks Advanced Mobile Phone Service/Personal Communications Services (AMPS/PCS) customer technical support web site

401-601-009, Issue 10


access the most current AMPS/PCS and related 5ESS Digital Cellular Switch (DCS) documentation on the web site

order system and product documentation from Lucent Technologies

order Lucent Technologies training products or register for classroom training courses

submit comments and feedback about Lucent Technologies documentation and training

2. Prerequisites

HLR Configuration

The Power Down in System with No VLR feature is supported by the Integrated Home Location Register (IHLR) configuration.

Software Requirements

The Power Down in System with No VLR feature requires ECP Release 24.0 with SU 24-0002.

Hardware Requirements

There are no additional hardware requirements.

3. Feature Description

AR can occur on Analog, Code Division Multiple Access (CDMA), or Time Division Multiple Access (TDMA) technologies. ER can occur only on CDMA or TDMA. Table 9 on page 62 lists the Registration features and shows to which technology they belong. Also, the technology appears in parentheses in the heading for each feature.

Overhead messages that request registration information are sent from the cell sites to mobiles over the Analog Control Channel (ACC), Forward Control Channel, (FoCC), or the Digital Control Channel (DCCH) Broadcast Control Channel (BCCH). The mobiles then send their registrations over the ACC Reverse Control Channel (RCC) or the DCCH Random Access Channel (RACH) and receive a confirmation message from the cell site over the FoCC or the BCCH (see Figure A on page 4). The registration information is then sent to the MSC where it acts as a stimulus for modification and creation of entries in the Subscriber and Feature Information (sub) and Visitor Location Register (vlr) databases.

401-601-009, Issue 10


Figure A. Example of Registration Flow

The sub and vlr databases facilitate call deliveries and originations throughout the Feature Transparency Network/Extended Feature Transparency Network (FTN/EFTN). Mobiles register only when powered up and idle, not in the middle of a call or during a handoff. For information on how registration is used to update the sub and vlr databases, refer to 401-661-010, Multiple Systems Description and Implementation Guidelines.

Autonomous Registration (AR) for CDMA

AR for CDMA feature allows a CDMA mobile to register under the following conditions:

Power up

Power down

Travel into a new zone

Change of parameters (such as whether the mobile is using slotted or non-slotted paging and what its preferred paging slot cycle is)

When a system-controlled time interval has elapsed.

A CDMA mobile is also implicitly registered whenever it initiates a call or responds to a page. If the mobile registers in its home system, the home system sets the last seen data entry in the HLR to point to itself, and directs the system where the mobile was previously last seen (if any) to delete that mobiles information from its VLR. If a roamer registers in a visited system, the visited system informs the home system of the mobiles current statusthat is, whether the mobile is active or inactive.

UPDATES HOME/VISITEDLOCATION REGISTERS

REGISTRATION INFORMATION

REGISTRATION

4

CELL SITE

2

CONFIRMATION3

MSC

1 REQUEST FORREGISTRATION

401-601-009, Issue 10


In addition, the visited system obtains subscriber data about the registering roamer from the home system and creates a VLR entry to store this information with the dynamic data generated from the AR message. Included in this subscriber data is a field that indicates whether the mobile is allowed to use the CDMA technology.

Although the AR for CDMA feature supports zone-based registrationthat is, registration triggered by the mobiles movement into a different zonezone location data for the mobile is not maintained in the subscriber database by this feature. That functionality is provided by the MAS feature. (Refer to 401-612-112, Mobile Activity Supervision.)

To maintain a mobiles intersystem registration status, CDMA Paging Channel (CDMA-PC) registrations are processed by the MSC as ARs. The types of registrations include:

periodic

power up

Zone ID/Location Area1

parameter

When these registrations are processed, the following values are stored in the subscribers data record:

the slot cycle index

the last accessed technology type

the Zone ID of the setup face on which the registration was received

NOTE:This data pertains to only the serving MSC. It is not relevant to the mobiles intersystem registration status.

Geographic-Based and Time-Based AR (Analog, TDMA, CDMA)

Two AR implementation scenarios may be used in any Flexent/AUTOPLEX wireless networks: geographic-based AR and time-based AR.

In either AR scenario, mobiles register when they cross market boundaries and detect a different SID from the cell message sent over the FoCC. Registrations can be solicited from roamers only, homers only, or both. Geographic boundaries can also be established between MSCs in a Multiple System arrangement where those MSCs broadcast the same SID. This is accomplished by a registration that is forced when the boundary is crossed. Boundaries around a cell, or group of cells, can also be established if it is important to know when a mobile travels to a DCS where call delivery is not supported. This involves the use of the Selective Paging (SP) optional feature

1. Only CDMA uses the term Zone ID. It is equivalent to Location Area.

401-601-009, Issue 10


discussed in FoCC and Optional Features (Analog) on page 22. The section, Feature Implementation on page 42 describes the modifications necessary to implement geographic-based registration.1

In addition, time-based AR triggers a registration from a mobile when the time equivalent to the registration interval has passed. These intervals are set by the cellular service provider.

Time-based AR offers an additional benefit over geographic registration through periodic registration intervals. The frequency of ARs, the type of subscribers registering (roamers/homers), and the predefined registration boundaries may be varied using time-based AR. Time-based registration ensures that a stack-of-four mobile registers again in the same MSC, and it reduces the amount of time that a mobile may be lost due to MSC border (between two MSCs) cell AR issues (refer to Service Provider Perspective on page 22 for further discussion). Parameters to implement time-based AR are described under Feature Implementation on page 42.

Registration Terms

In Appendix B, registration terms are defined for AR over the FoCC as an example of the registration process. Some of these terms are actual translatable parameters. Their recommended settings are described under Feature Implementation on page 42.

Mobile Registration Specifications

After a mobile registers, it receives a confirmation message from the cell site. After confirmation is received, the mobile calculates and stores the value of its next registration (nxtreg) as the sum of the current regid value plus regincr.2 The mobile monitors the value of regid. When regid becomes greater than or equal to the value of its next registration (nxtreg), the mobile registers.

NOTE:These parameters do not apply to CDMA.

AR Overload Algorithm (Analog)

To protect the RCC from congestion of AR messages, an AR overload algorithm is automatically executed in the Series II cell site. The threshold for execution of AR overload is determined from the value arrccovr (see Table 10 on page 65).

When time-based AR is implemented and AR overload controls are in effect, the following actions occur:

1. Roamer registrations are temporarily turned off.

2. Registration interval for homers is increased until the load is reduced sufficiently.

1. Geographic registration is equivalent to time-based registration where the cell sites registration clock is never incremented.

2. If the mobile does not receive a confirmation, it selects a random number between 1 and 10 and attempts to re-register after this number of intervals.

401-601-009, Issue 10


3. Registration interval is slowly readjusted back to its original value after the overload conditions disappear.

4. Roamers are again allowed to register.

When only geographic-based AR is implemented, homer and roamer registrations are toggled on and off until the registration load is sufficiently reduced. If an AR overload condition exists, roamer registrations are turned off. If an overload condition persists, homer registrations are turned off and roamer registrations are turned back on. If necessary, both homer and roamer registrations are turned off. Registration for both homers and roamers resumes when the overload conditions have cleared.

For Series II cell sites, a service measurement shows the number of 6-second intervals where the number of ARs exceeded the translatable AR overload threshold (refer to Table 7 on page 53). If AR overload is in effect for any of the cell sites, consider either an increase in the threshold value (arrccovr) if it is less than 60, or a reduction in the number of resulting registrations in the system through a larger registration interval or a smaller the number of registration boundaries.

AR overload protection may be disabled through specification of values of arrccovr larger than any feasible load (for example, 90 ARs in 6 seconds). Consequently, when AR overload protection is disabled, it is possible for AR messages to flood the RCCs and block other messages.

AR Limitations

Forward Control Channel (FoCC) Limitations (Analog)

Registration confirmations are sent from the cell over the FoCC to the mobiles. This is in addition to voice channel assignments, directed retries, and pages [short/long Mobile Identification Number (MIN)]. Flood paging (especially with only long MIN) creates a large burden on the FoCCs since the Flexent/AUTOPLEX wireless network pages all mobiles, in all cells, within an MSC. For busy cells, the addition of AR message confirmations can exhaust the FoCC and cause other messages (such as pages) to be shed. A number of Service Measurements (SM) counts are available to evaluate the throughput and activity of the FoCC. (See the section Monitoring Registrations on page 53.)

Figure B on page 8 (for Series II cells) provides guidelines to determine the safest AR interval (in terms of minutes) based on number of pages and what percent are short MIN pages. If the desired AR interval is 30 minutes and the chart shows that a 60-minute interval is the safest, other changes may be required to reduce the paging load in the system. A change from flood paging to smart paging (paging based on the last known location of the mobile) can reduce the paging load in a multi-MSC configuration. The System-Wide Short MIN Paging and SP optional features also reduces the size of the paging message and the number of pages. (See Service Provider Perspective on page 22.)

401-601-009, Issue 10


Figure B. Example FoCC Occupancy for Series II Paging Load and AR Rates

Reverse Control Channel (RCC) Limitations (Analog)

AR messages are sent over the RCC to the cell site and onto the Cell Site Node (CSN) via data link. These messages are then bundled at the CSNs and distributed evenly among the CDNs (Call Processing/Database Nodes) via a round-robin type process. One limitation in this process is the capacity of the RCC.

AR messages compete with origination messages, page responses, and other messages for capacity on the RCC. Estimates show that approximately 5 percent of the RCC is used for originations and messages other than AR messages. Allocation of 80 percent of the RCC for AR messages ensures that other messages are not blocked.

The total capacity of the cell sites RCC would be filled with approximately 78 AR messages in a 6-second interval. Therefore, 60 AR messages in 6 seconds would fill 80 percent of the capacity of the RCC. The cell form parameter arrccovr determines the number of registrations that can be received in 6-second intervals before AR overload is executed. Setting the value of arrccovr to 60 ensures that AR messages

Forward Control Channel OccupancyFor Series II Paging Load and AR Rates

0 10 20 30 40 50 60 70 80 90 100Percentage of Short MIN Paging

30

40

50

60

70

80

90

Max

imum

Num

ber P

ages

(x10

00) P

er Ho

ur

FOCC Message Shedding may occurwhen above selected AR line

AR is OFF 60 Min AR 30 Min AR 15 Min AR

401-601-009, Issue 10


occupy only 80 percent of the RCC before AR overload is executed. This overload situation can be prevented through selection of appropriate registration intervals and registration boundaries. See Figure H on page 25.

Setting Registration Boundaries Through Staggered regid Values (Analog)

The values of regid for cells within a given MSC are a function of time. Mobiles register after detection of a change of, for example, 5,000 units1 in the parameter regid during travel between cell sites that broadcast the same SID. A difference in the regid value by 5,000 (that is, creating offsets of 5,000) from one cell site to the next, registration boundaries are created. The variation in the value of regid causes the mobiles to detect an increase or decrease in the parameter and to register as a result. The recommended minimum offset value is 5,000.

The parameters ofstl and ofstm, when added together, provide the total offset of the regid value for each cell site. The parameter ofstl is specified on a cell basis to create variations in regid values among cell sites within a single MSC. Using this information, registration boundaries can be created by laying out a pattern of ofstl values among the cells.

Figure C on page 10 and Figure D on page 10 show possible configurations for two different systems. In the first example, assume that the value of ofstm is equal to 0. This means that the total offset for each of the cell sites is equivalent to the value of ofstl.

1. The difference between any two cell (adjacent or not) offsets needs to be only greater than the value of regincr. For example, if regincr is 180, cell and MSC offsets must be in multiples of 180 (or greater) so that the mobile recognizes the offset as the change in time it needs to re-register. A safe number to use is 5,000 because the maximum value of regincr is 4,095; thus, changes would not be required to cell or MSC offsets if a change were made to regincr.

401-601-009, Issue 10


Figure C. Example Cell Site Offset Configuration for a System with a Single MSC

Figure D. Example Cell Site Offset Configuration for a System with Three MSCs

B

B

B

B

B

B

B

B

B

B

B

B

B

B

B

B

B

B

B

AC

AC

A

C

A

C

A

C

A

CA

C

CA

CA

A = 5,000

B = 0

C = 10,000

CELL OFFSET

CELL OFFSET

CELL OFFSET

B

B

B

C

A

C

A

A

D

F

D

FB

B

B

B

B

B

B

B

B

B

B

B

B

B

B

AC

AC

A

C

A

C

C

E E

E

E

E

E

E

E

E

E

E

E

E

E

E

E

E

ED

F

D

F

DD

D

D

DFF

F

F

F

E

J

G

J

GJ

G

H

H

H

B

C

CA A

J

G

J

GJ

GJ

G

JG

JGH

H

H

H

H

H

H

H

H

H

H

H

H

H

H

H

MSC 1 MSC 2 MSC 3

MSC OFFSET = 0CELL OFFSET A = 5,000CELL OFFSET B = 0CELL OFFSET C = 10,000

MSC OFFSET = 15,000CELL OFFSET D = 5,000CELL OFFSET E = 0CELL OFFSET F = 10,000

MSC OFFSET = 30,000CELL OFFSET G = 5,000CELL OFFSET H = 0CELL OFFSET J = 10,000

401-601-009, Issue 10


NOTE:It is possible for individual cell sites to have different registration intervals through various regincr and ridincr values. The ridincr values for all cell sites must be identical for the offset values to be guaranteed to force mobile registrations. It is therefore recommended that only regincr vary if different registration intervals are desired.

In Figure C on page 10, the border cells (cells marked A and C) have been given ofstl values of 5,000 and 10,000, respectively. The interior cells (cells marked B) have ofstl values of 0. If a mobile drives into an A cell and then drives into a B cell, it detects the difference in regid of greater than 5,000 and registers after entrance into the B cell. Similarly, if the mobile travels in either direction between cells marked B and C or between cells marked A and C, the mobile registers after entrance into the second of the two types of cells.

These registration boundaries are helpful in that they induce stack-of-four mobiles to register. If a stack-of-four mobile registers in System #1, leaves System #1 and returns to System #1, the mobile does not re-register until time equivalent to the registration interval has passed. If the registration interval for System #1 is 30 minutes and the mobile leaves the system 5 minutes after registering and returns 5 minutes later, the mobile waits for 20 minutes before registering. By the setting of registration offsets, the mobile registers as soon as it enters the second cell in System #1 or in 20 minutes, whichever comes first.

There may be interior cells that should be offset as well. For example, if one of System #1s interior or B cells includes an airport and if the system has a long registration interval (such as 24 hours), it may be wise to make that an A type cell with a registration offset of 5,000. If a stack-of-four mobile leaves and returns within 24 hours, the offset forces it to register as soon as it leaves the airport cell. The ofstl parameter has a maximum value of 1,048,575. Therefore, 200 different offset values that vary by at least 5,000 can be used within a given system or SID area. The goal of establishing offsets is to guarantee that no two cell offsets (MSC + cell) are equal in a single MSC or multi-MSC configuration.

Figure D on page 10 shows an example of the offset configuration for a system that has three MSCs. In addition to the border cells being offset from the interior cells, the three subsystems within the SID area have been offset from each other. The MSC offset is located in the cgsa form. If all Cellular Geographic Service Areas (CGSAs) should be one registration area, all cgsa forms should contain the same offset value. If the SP feature is being used and a DCS area coincides with a CGSA, a different offset value for the CGSA can be used to create a registration boundary for that DCS and its group of cells.

This system has its offsets configured in such a way that a mobile is forced to register when travel occurs between any two MSCs. The total offsets varying from 0 to 40,000 have been laid out to ensure this. As stated earlier, additional offsets may be provided for interior cells as needed.

401-601-009, Issue 10


For a system that has two MSCs, the offsets shown for MSCs #1 and #2 in Figure D on page 10 are sufficient.

The records in the roam form must be changed to reflect the home Extended System Identifier (ESID) of the particular NPA-NXXs that now are networked (if this has not already been done). For every new ESID specified in a roam record, there must be a record in the Network Neighbor (nnbr) database. The nnbr form defines the VLR expiration time for mobiles from this ESID, the data link to be used, and the validation, call delivery, and handoff types allowed between this ESID and all serving system DCSs.

Enhanced Registration (ER) & Interim Standards

The ER feature enables the MSC to keep track of IS-136 mobile unit activities in the following ways:

Mobile unit power uppower up registrations are stimulated when a mobile is turned on. (These registrations are equivalent to those available for IS-54B compliant mobiles.)

Mobile unit power downpower down registrations are stimulated when a mobile is turned off. (These registrations are equivalent to those available for IS-54B compliant mobiles.)

Location area identificationthese registrations are stimulated when a mobile moves into a cell/sector that is broadcasting a different value (Location Area Identity (LOCAID) on the ACC; RNUM on the DCCH) that is not part of the current list stored in the mobiles semipermanent memory.

ACC-to-DCCHadditional registration capability available only on the DCCH. This capability allows a mobile to register on the DCCH if the mobile was previously served by an ACC.

De-registrationfuture registration capability available only on the DCCH. This capability lets a mobile generate a deregistration in its former system (including private and residential systems) before it registers in a new system.

New system registrationsfuture registration capability that allows a mobile to register whenever it enters a private/residential system.

ER can be activated independently from geographic-based or time-based AR. However, it is recommended that AR and ER be considered together when evaluating the overall impact on system resources.

For ER over the DCCH, separate activation/deactivation is provided for the three currently available types of ERs (power up, power down, and location area change). The default is off. In addition, a new capability to activate/deactivate deregistration on the DCCH is provided.

401-601-009, Issue 10


Autonomous Registration Improvements (Analog Only)

Autonomous Registration Improvements (ARI) resolve registrations from a roaming mobile subscriber in multiple, inter-vendor cellular systems.1 When an MSC detects a roamer that is not registered in its service area, it sends a registration notification message to the mobiles home HLR. A nearby system could simultaneously detect the roamer and initiate its own registration notification to the same home HLR. Because inter-vendor messages and the transactions that result are processed as they are received, the HLR responds to the first registration as soon as possible.

The first reporting MSC becomes the serving VLR. Receipt of a registration notification shortly after the initial registration for that mobile implies that the mobiles presence has been simultaneously detected by two MSCs. This could create multiple registrations. If each incoming registration is accepted and each previous registration is cancelled, the roaming mobile might be placed in a service area that cannot provide strong enough radio signals to maintain service. This condition is referred to as registration glare. Registration glare creates constant re-registration and switching between MSCs which could overload the system and reduce subscriber services. The ARI feature addresses this difficulty.

What ARI Does

The ARI feature includes the capability to detect multiple registrations of a mobile for multiple registration notification within a 3-second time interval. It then processes the registration request based on the signal strength arbitration. Multiple registration can occur if an MSC within the domain of a VLR overhears a registration or origination that occurs within the domain of a neighboring VLR. If multiple registration occurs, the HLR sends registration cancellation notification to one of the VLRs concerned. The registration cancellation message is sent to the appropriate VLR, based on whose signal is stronger (called signal strength arbitration algorithm performed by the HLR if the MSC is Flexent/AUTOPLEX, or by the VLR if the MSC is not Flexent/AUTOPLEX. Performance of the signal strength arbitration at the HLR for Flexent/AUTOPLEX reduces message traffic and delay.

During signal strength arbitration, the cell site and the MSC perform as follows:

1. Cell site sends raw signal strength during call origination (MGORIG).

2. Cell site sends raw signal strength during page response (MGPGRSP).

3. Cell site sends raw signal strength during autonomous registration (MGCAUTREG).

4. MSC call processing, upon receiving the raw signal strength from the cell site, converts the raw signal strength into the scaled values provided in IS-41 standards.

1. Autonomous Registration Improvements is also known as Multiple Registration.

401-601-009, Issue 10


5. MSC verifies the threshold limit of the signal strength. If the signal strength is below the threshold, MSC call processing does not use the raw signal strength information sent by the cell site. Instead, the MSC marks the information as 0, in accordance with the IS-41 scaled values.

After the serving MSC distinguishes whose signal is stronger (its own or the signal from the detecting MSC), it sends one of the messages shown in Table 1 on page 14.

Once a mobile (a roamer in the VLR or a homer in the HLR) is registered in a serving MSC, additional autonomous registrations, call originations, or page responses cause this MSC to record the registration time and the signal strength. This data is saved for future reference or for possible signal strength arbitration.

Figure E on page 15 and Figure F on page 16 illustrate these multiple registration events from the HLR and VLR perspectives.

Table 1. ARI Registration Cancelled Messages

This message is sent From To And this is the result

RegCanc Response Serving MSC (VLR)

HLR VLR is deleted

RegCanc Denied (with a new denied reason of Multiple Access)

Serving MSC (VLR)

HLR VLR is not deleted

RegCanc Out of Sequence

HLR MSC doing signal arbitration

MSC responds by sending OP_SEQ_ERR message to HLR so that HLR is aware that the cancellation request cannot be done

401-601-009, Issue 10


Figure E. Multiple Registrations Event Flow at the HLR

RegNotreceived

RegNot Invokereceived fromnetwork MSC

Store RegNot signal,channel and

system accessparameters in

temporary memory

RegNotReceived under

3 seconds?

Store Time Stampof RegNot event

in temporarymemory

Mobilealreadyvisiting?

Set up RegCancto Serving VLR

with Normal Parameters

YesA

No

No

Yes Obtain the signalvalue of the VLR

at the time ofregistration

Signal Arbitration

VLRsignal value

higher?B

Yes

Send RegCancto serving VLRand set timer

Wait for Responseor Timeout

No

RegCanctimeout RegCanc_RR

Change last seenpointer in CCF tonew serving VLR

A

Send RegNot_RRwith authorizationdenied-multipleaccess to requesting MSC

Copy latestRegNot timestamp into CCF

Send RegNot_RRwith authorization

accepted

End

B

401-601-009, Issue 10


Figure F. Multiple Registrations Event Flow at the VLR

MSC detectsroamer

Is this anauthorizedroamer?

Is it alreadyregistered?

Normal internalprocessing

Normal non-network visitor

processing

Store recvdsignal strengthfrom cell in

temp memory

Format RegNot msg

for HLR

Set RegNotresponse

timer

Send RegNot to HLR

Wait for responseor time-out

No

Yes

No

Yes

RegNotresponse

Returnauth serv?

Createservice

VLR

Move recvdsignal strength

to VLR

End

RegNot re-sponse timeout

Performcustomerpreferredtreatment

End

Createno-service

VLR

No

Yes

B

Format RegCanc responseof operationssequence error

Delete VLR

FormatRegCancresponse of

accepted

FormatRegCanc

response ofdeny multiple

access

Send RegCanc

response_RRto HLR

End

A

Localsignal

stronger?

Retrievestored signalstrength from

VLR

RegCancin progress or

no VLR?

Yes

No

B

Multipleaccess?

ANo

Yes

Yes

No

RegCancRecvd

401-601-009, Issue 10


ARI & Call Processing

Table 2 on page 17 presents various call processing scenarios that can involve the ARI feature.

Table 2. ARI Call Processing Scenarios

When this happens... This is the result

An IS-41 networked MSC detects a roaming mobile the MSC sends a Registration Notification INVOKE message with the ReceivedSignalQuality to the HLR associated with the mobile

A HLR associated with the roaming mobile receives a Registration Notification INVOKE message from a VLR, and no multiple access is attempted

the HLR updates the last seen pointer and sends the Registration Cancellation Notice to the serving VLR.

A HLR associated with the roaming mobile receives a Registration Notification INVOKE message from a VLR, and there is multiple access (2 accesses within 3 seconds), and this access is not desired

(Background Information: When the HLR receives the first Registration Notification message, it sends the response to the requesting system immediately. It starts the 3-second timer for any possible multiple registrations. The HLR distinguishes whether a Registration Notification message is part of a multiple access, based on its internal algorithm. The HLR distinguishes whether the access is desirable or not based on the internal algorithm for the received signal strength for an access.)

the HLR sends the Registration Notification ReturnResult message to the requesting VLR with the Authorization Denied set to multiple access.

A HLR associated with the roaming mobile receives a Registration Notification INVOKE message from a VLR, and if there is multiple access and the access is acceptable,

the HLR sends a Registration Cancellation INVOKE message to the serving VLR. The Registration Cancellation INVOKE message does not contain access information because the signal arbitration is done at the HLR.

The serving VLR receives a Registration Cancellation INVOKE message and access information from the HLR

the VLR checks to see whether it received a multiple access that matches the registration event.

The serving VLR performs a signal strength arbitration if it received an access matching the registration event. Based on the results of the arbitration, the VLR does one of the following:

- If the serving VLR signal is stronger, it sends the Registration Cancellation ReturnResult message to the HLR, with an indication that it denies the cancellation request. A CancellationDenied parameter is included, set to Multiple Access, along with the local access information.

- If the serving VLR signal is weaker, it removes the mobiles record. It sends a Registration Cancellation ReturnResult to the HLR associates with roaming mobile.

The HLR receives the Registration Cancellation ReturnResult from the serving VLR without the cancellation denied parameter set

the HLR clears the pointer to the previously visited VLR. It sends a Registration Notification ReturnResult to the requesting VLR.

401-601-009, Issue 10


No Paging Inactive Mobiles (NPIM)

Through provisioning of immediate secondary treatment to an incoming call on a mobile that is marked inactive, the NPIM feature benefits customers who are not subscribed to the MAS feature. Without this feature, after an inactive mobile is paged twice, then the secondary treatment is provided. However, with this feature, the inactive mobile receives secondary treatment immediately, and if secondary treatment is not applicable, then the No Page Response announcement is received. This feature can be activated only if the ER feature is active.

The HLR receives the Registration Cancellation ReturnResult from the serving VLR with the cancellation denied parameter set to multiple access,

the HLR sends a Registration Notification Return Result to the requesting VLR with the Authorization Denied parameter set to multiple access. The Registration Notification ReturnResult does not include the access information parameter.

The neighbor MSC receives a Registration Notification ReturnResult message from the HLR associated with the roaming mobile, and if the authorization denied parameter was received and it indicated a multiple access,

the neighbor MSC removes the record of the mobile in its VLR.

A neighboring VLR sends a Registration Notification message for a mobile to the HLR

the HLR compares the time interval between the Registration Notification and the previous registration time stamp stored in the HLR. If the time stamp was less than 3 seconds, the HLR compares the signal strength received in the Registration Notification message with the stored signal strength in the HLR.

- If the stored (HLR) signal strength is stronger, the HLR sends the Registration Cancelled message to the VLR.

- If the VLR signal strength is stronger, the HLR updates the last seen pointer to the VLR.

If the time stamp was greater than 3 seconds, the HLR updates the last seen pointer to the VLR.

The HLR receives autonomous registration or Register Notification from a VLR because a dual-mode mobile registered in TDMA/CDMA (not in the analog control channel)

the HLR stores the time stamp and a value in the signal quality field, indicating the signal quality that the mobile registered on TDMA/CDMA (not in analog).

The HLR receives an autonomous registration from a mobile that is being serviced by a VLR

the HLR compares the signal strength with the signal strength stored for the previous registration if the registration happened within the last 3 seconds. It sends a Registration Cancelled message to the VLR if the HLR received a stronger signal strength.

If the time interval between the registration is greater than 3 seconds, it sends a Registration Cancelled message to the serving VLR and assigns itself as the serving system.

Table 2. ARI Call Processing Scenarios

When this happens... This is the result

401-601-009, Issue 10


Power Down in System with No VLR

Introduction

The following information describes the functionality, benefits, and operation of the Power Down in System with No VLR feature.

Functionality

The Power Down in System with No VLR feature allows the MSC to send the MSINACT Invoke message to the HLR if a power down registration is detected and no VLR exists for the mobile. Additionally, this feature enhances the functionality of handling the MSINACT Invoke message at the HLR. The enhancements will check if the MSINACT Invoke message was received from the last seen MSC and the type of deregistration. Based on these checks the mobile is marked active/inactive, the Registration Cancellation (REGCANC) Invoke messages are sent out and the MSINACT Return Result (MSINACT RR) or MSINACT Return Error (MSINACT RE) message is sent back

Benefits

The Power Down in System with No VLR feature will help to preserve paging channel resources by not paging the mobile at its last seen MSC (MSC where the mobile was last registered).

How the feature operates

The Power Down in System with No VLR feature handles the power down registration from a mobile roaming into a Lucent Technologies MSC and the MSC does not have a VLR associated with the roaming mobile. The feature functionality is divided into the following three parts.

Sending the MSINACT to HLR

When the roaming mobile powers down, the Lucent Technologies MSC will send a MSINACT Invoke message to the HLR even if the VLR does not exist. The Mobile Switching Center Identification (MSCID) parameter is added to the MSINACT Invoke message if the HLR is a Lucent Technologies IHLR. The MSCID will be used by the IHLR to determine which is the Last Seen Pointer (LSP) MSC when the network is using Global Title Translations (GTT) routing.

Processing the MSINACT at IHLR

The Power Down in System with No VLR feature handles not only the MSINACT Invoke due to power down in system with no VLR, but also to handles all MSINACT Invoke messages at the IHLR. Prior to this feature, the current functionality accepts MSINACT Invoke messages only from the LSP MSC. It does not handle MSINACT messages routed using GTT and does not take into consideration the deregistration type received in the MSINACT message. With this feature, the IHLR will process the MSINACT messages from the non-LSP MSC, process the messages routed using GTT as well as process the "deregistration type" parameter included in the MSINACT message.

401-601-009, Issue 10


Determining Deregistration Type:

When the Lucent Technologies IHLR receives MSINACT Invoke from a non-LSP MSC, it shall first determine the Deregistration Type according to one of the following scenarios.

If the Deregistration Type is Deregister Due to Mobile Station power down then the following steps shall be performed:

1. Send MSINACT RR to acknowledge the MSINACT Invoke.

2. Send REGCANC to both the LSP MSC and to the MSC that sends the MSINACT Invoke message.

3. Update to indicate that the mobile is inactive.

4. Update the Recent Change/Verify (RC/V) sub form Mobile Inactive Reason field to 5, which represents Power Down (PD) in system with no VLR.

5. LSP updated to point to the MSC sending the MSINACT message.

6. Update the Short Message Service Message Waiting Indicator (SMS_MWI) indicator based on SMS_MWI value from the REGCANC RR from the LSP MSC.

If the Deregistration Type is not included or the Deregistration Type is not Deregister Due to Mobile Station power down then the following steps shall be performed:

1. Send MSINACT RE to acknowledge the MSINACT Invoke.

2. Send REGCANC only to the MSC that sends the MSINACT Invoke message.

3. Ignore the SMS_MWI value from the REGCANC RR.

Processing the REGCANC RR message

Upon receipt of the REGCANC RR at the IHLR, before updating the SMS_MWI flag, a check will be performed to see if the REGCANC RR was received from the LSP MSC. Only the REGCANC RR from the LSP MSC will be accepted, then the SMS_MWI flag will be updated if required. If the "ignore REGCANC RR" field is set, the REGCANC RR would be discarded and the SMS_MWI flag will not be updated.

401-601-009, Issue 10


4. Feature Interactions

Both AR and ER each have their own Feature Activation File (FAF) entries. Although the AR and ER features may be implemented independently, the AR feature must be active in the Feature FAF for ER to operate.

A number of other features are dependent on the AR feature being active or can be used in the implementation of AR.

The Non-AR Capable Flood Paging (NARCFP) feature is designed to provide a way to page mobiles that do not autonomously register. Refer to 401-612-067, Non-AR Capable Flood Paging (NARCFP), for additional information and implementation procedures.

The SP feature pages mobiles only when their home DCS supports call delivery with the DCS they are visiting.

The System-Wide Short MIN Paging (SWSMP) feature pages home subscribers with a short MIN, rather than with a long MIN, reducing the paging work load for the FoCC. Refer to 401-612-076, System-Wide Short MIN Paging (SWSMP).

The Automatic Roamer Greeting (ARG) feature initiates a call and plays a recorded announcement after the detection of a roamer AR. Refer to 401-612-003, Automatic Roamer Greeting.

The Multiple Units with Same Directory Number (MUSDN) feature allows a subscriber to have up to three mobile units with the same directory number. The mobile unit that is determined to be active (either because of autonomously registering or from making a call) is the one tracked by the system and the one to which calls are delivered. Refer to 401-612-072, Multiple Units with Same Directory Number (MUSDN), for additional information.

The CDMA AR feature is dependent on AR over the TDMA DCCH. It is also dependent on ER over both the ACC and TDMA DCCH. CDMA AE also interacts with the following features:

Message Waiting Indicator (MWI)Whenever a registration message (other than a power down registration) is processed, the MWI feature checks to determine whether the message waiting indicator is set in the HLR/VLR and notifies the mobile. Refer to 401-601-019, Voice Mail Interfaces and Message Waiting Indicator.

Mobile Activity Supervision (MAS)This feature builds on the functionality added by the CDMA AR feature. CDMA AR must be in effect for the MAS feature to operate for CDMA mobiles. Refer to 401-612-112, Mobile Activity Supervision.

The NPIM feature is dependent on the AR and ER features.

The Power Down in System with No VLR feature does not interact with other features.

401-601-009, Issue 10


Mutually Exclusive FAFs (MAS)

If the MAS feature is on in the system, then the NPIM feature cannot be activated.

5. Subscriber Perspective

For most subscribers, registration is transparent. A stack-of-four mobile does not register when crossing an SID boundary if it has already registered within that systems AR/ER interval. Many mobiles may not register as instructed. This provides the opportunity for the last known location of the mobile to become incorrect. Since mobiles are probably being paged based on the last known location, calls can be missed. This situation is not detectable by MSC software and can only rely on subscriber feedback. When this occurs, the mobile can be exclusively flood paged in the systems identified on the net form flood page list, through the use of the NARCFP feature, or through a value of y (yes) in the Flood Page FTN? field of the sub form.


The Power Down in System with No VLR feature is transparent to subscribers. However, when cloned (fraud) mobiles power down in an MSC, due to this feature sending the MSINACT Invoke to the HLR, the mobile would be marked Inactive and no Authentication is done before marking this mobile inactive. Due to the mobile being marked inactive, the original mobile will not receive any terminating calls until the next time based authentication or call origination from the original mobile.

6. Service Provider Perspective

FoCC and Optional Features (Analog)

Evaluation of the FoCC and current paging load is recommended prior to implementing AR/ER. When turning on AR/ER, it is expected that flood paging would be turned off, and thus offset the increase in FoCC messaging caused by AR/ER. If excessive message traffic on the FoCCs already exists, other optional features are available to help reduce paging traffic. These features are:

System-Wide Short MIN Paging (SWSMP): This feature pages all home mobiles with a short MIN (does not include the area code) and all roamers with a long MIN. A short MIN requires half the FoCC resource of the long MIN. The use of this feature can reduce the paging load by as much as 50 percent.

Selective Paging (SP): This feature pages only cells associated with a DCS that allows call delivery with the mobiles home DCS. This feature was designed to not page mobiles in cases where call delivery was not supported, but may also help to reduce the amount of page requests that a cell has to process.

401-601-009, Issue 10



The Power Down in System with No VLR feature will be controlled by its FAF. Activation of this feature will:

preserve paging channel resources

reduce message traffic between the CDN and CSN

reduce message traffic between the CDN and Data Link Node (DLN)

save real time usage of the CDN

7. System Interaction

The following RC/V screens highlight the required fields for implementation of AR and ER.

System Interaction - AR

In addition to the pre-existing fields for AR over the ACC, FoCC, and DCCH, AR includes fields for registration periodicity (cgsa and cell2 forms) and for whether home mobiles and roamer mobiles should register on the DCCH (cell2 form). In the case of registration periodicity, a plus mark (+) before the field number on the RC/V form indicates that this field has overriding parameters. This means the field is defined at a system level (cgsa form) but can be redefined at the lower cell level (cell2 form).

Parameters for these forms are included as Appendix C.

401-601-009, Issue 10


AR - Cellular Geographic Service Area (cgsa) Form

An example of the cgsa form is shown in Figure G on page 24.

Figure G. Example of cgsa Form (Screen 3) ECP Release 17.0

Offset of Registration ID for Cells in CGSA (ofstm parameter)This field contains a value that, when added to the ofstl parameter (Offset of Registration ID for This Cell) value on the cell2 form, provides the total offset of the regid parameter for a given cell site. Refer to Setting Registration Boundaries Through Staggered regid Values (Analog) on page 9 for suggestions on populating this field.

NOTE:The existing per-CGSA fields Turn-off Home Mobile Registration in CGSA and Turn-off Roamer Mobile Registration in CGSA that can disable AR on the ACC for all cells in the CGSA do not apply to AR on the DCCH. No equivalent per-CGSA control of AR exists on the DCCH.

Registration Periodicity (min)This field activates periodic registration and defines the registration interval on the DCCH when assigned a non-null value. This field accepts values from 1 to 511, which is approximately equivalent in minutes to a range from just over a minute to 8.5 hours. A suggested registration interval for most systems is 30 minutes. This field has overriding parameters and also appears on the cell2 form.

AUTOPLEX Cellular CELLULAR GEOGRAPHIC SERVICE AREA (cgsa) Screen 3 of 8 System List of Switches Offset of Registration ID for Cells in CGSA...... 23) 0 in this CGSA Turn-off Home Mobile Registration in CGSA........ 24) n 40) [1] __ Turn-off Roamer Mobile Registration in CGSA...... 25) n [2] __ Registration Periodicity (min)...................+26) ___ [3] __ Carrier Access Selection Active.................. 27) n [4] __ Dynamic Routing Feature Active................... 28) n [5] __ Allow Service if Authentication Fails............ 29) y [6] __ ACC RAND Broadcast Frequency.....................+30) 10 [7] __ [8] __ Electronics Industry Association [9] __ Standard Dialing Plan Active..................... 32) n [10] __ Adjunct Data: CR - Use data from.............. 34) n [11] __ - Default treatment.......... 35) d [12] __ PASA - Use data from.............. 36) n [13] __ - Default treatment.......... 37) d [14] __

401-601-009, Issue 10


Series II Cell (cell2) Form

An example of the cell2 form is shown in Figure H on page 25.

Figure H. Example of cell2 Form (Screen 9) ECP Release 17.0

Should Home Mobiles Register (field for the DCCH)This field indicates whether a home mobile is allowed to register on the DCCH. The values for this field are y (yes) or n (no), with a default of n.

Offset of Registration ID for This Cell (ofstl parameter) This field contains a value that, when added to the ofstm parameter (Offset of Registration ID for Cells in CGSA) value on the cgsa form, identifies the offset of the regid parameter for this particular cell site. For suggestions on how to populate this field, refer to Setting Registration Boundaries Through Staggered regid Values (Analog) on page 9.

NOTE:The existing Maximum Interval Between Mobile Registrations, Time Interval to Increment Registration ID (sec), and Transmission Rate for Registration Message fields on the cell2 form now apply to only AR on the ACC.

AUTOPLEXCellular SERIES 2 CELL (cell2) Screen 9 of 21 System Cell ___

Autonomous Registration ACC DCCH CDMA Should Home Mobiles Register.......................... 167) n 168) n 169) n Should Roamer Mobiles Register (FSID Indicator) ...... 170) n 171) n +172) n Offset of Registration ID for This Cell.........+173) 0 Maximum Interval Between Mobile Registrations... 174) 2000 Time Interval to Increment Registration ID (sec) 175) 0 Transmission Rate for Registration Message 176) 10 AR Overload Threshold (Max. # of ARs in 6 sec).. 177) 60 TDMA DCCH Registration Periodicity (min)........+178) ___ CDMA Time-Based Registration Period.............+179) __ CDMA Parameter Change Registration...............180) n Enhanced Registration ACC DCCH CDMA Power-Up/Power-Down Registration...................... 181) n 182) n 183) n Location Area/Zone ID Registration.................... 184) n 185) n 186) 0 CDMA Zone ID Registration Timer..................187) 0 TDMA DCCH Deregistration.........................188) n

Sub-MSC Paging Area..............................189) 0

401-601-009, Issue 10


AR Overload Threshold (Max. # of ARs in 6 sec)

This field indicates the maximum number of registrations that can be received by the cell site in 6 seconds before AR overload is executed. This threshold helps to prevent the RCC from congestion by ARs from mobiles. The default of 60, which indicates that 60 ARs can be received in 6 seconds, ensures that AR messages occupy only 80 percent of the RCC before AR overload is executed.

TDMA DCCH Registration Periodicity (min)This field activates periodic registration and defines the registration interval on the DCCH when assigned a non-null value. This field accepts values from 1 to 511, which is approximately equivalent in minutes to a range from a little over a minute to 8.5 hours. A suggested registration interval for most systems is 30 minutes. This field has overriding parameters and also appears on the cgsa form. Therefore, if no value is entered, the value from the cgsa form is used.

401-601-009, Issue 10


AR - Executive Cellular Processor (ecp) Form

An example of the ecp form is shown in Figure I on page 27.

Figure I. Example of ecp Form (Screen 1) ECP Release 17.0

Read Control FillerThis field indicates whether the mobile unit must read the control filler word before accessing the RCC. Values for this field are y (yes) or n (no). This field should be set to y when implementing AR. Table 15 on page 69 describes the parameters.

AUTOPLEX Cellular EXECUTIVE CELLULAR PROCESSOR (ecp) Screen 1 of 41System

Executive Cellular Processor Identification............*1) 1 Read Control Filler.................................... 2) n Overload Control for Mobile Originations (S2 ONLY)..... 3) 5 Overload Location Request Limit........................ 4) 6 Service Measurements - Level of Reports................ 5) 1 - Reporting Period................ 6) 0 Message Routing Scheme................................. 7) a System Controlled Dynamic Power Change - Cell Site..... 8) n - Mobile........ 9) y Apply Busy Tone Indicator to Interworked SS7 Calls.... 10) y Frequency of ISUP Trunk Circuit Audits (sec).......... 11) 60 SCP System Identifier................................. 12) _____ SCP Switch Number..................................... 13) ___ Overload Call Origination Limit....................... 14) 10 CDN Removal Stable Call Threshold..................... 15) 5 Max Loop Counts: Origination Request.. 16) 2 IN Trigger.... 17) 2 Connect Resource..... 18) 2 Reset Timer... 19) 3

401-601-009, Issue 10


Figure J. Example of ecp Form (Screen 15) ECP Release 17.0

FTN/EFTN No Service VLR Expiration Time (min)In the ecp form (Figure J on page 28) indicates how often (in minutes) a no-service VLR for FTN/EFTN neighbors are deleted. A no-service VLR is created when a call origination is attempted or an AR is received and no subscriber record is found, a serial number mismatch occurs, or the home system indicates that service should be denied. The recommended value is 30 (minutes).

TIA No Service VLR Expiration Time (min)This field indicates how often a no-service VLR for a Telecommunications Industries Association (TIA)/IS-41 neighbor is deleted (in minutes).

AUTOPLEX Cellular EXECUTIVE CELLULAR PROCESSOR (ecp) Screen 15 of 41System

ESID of Roamer Administrative MSC (RAM) ID: DCS................................................ 259) __ ECP................................................ 260) __ System............................................. 261) _____ Additional paging interval time (sec)................. 262) 0 Call Forwarding (CF) effective in..................... 263) cgsa Message Recording Service (MRS) effective in.......... 264) cgsa Disallow Roamer Access Number in Home FTN............. 265) n Call Delivery Primary Dialing Class................... 266) ___ Call Delivery Secondary Dialing Class................. 267) ___ FTN/EFTN No Service VLR expiration time (min)......... 268) 30 TIA No Service VLR expiration time (min).............. 269) _____ Automatic Roamer Greeting Expiration Time (hr)........ 270) 0 Turn Off Subscriber Pre-Call Announcement (SPANC)..... 271) n Maximum Attempts for ISUP Call Forwarding............. 272) _ Enable Enhanced 911 for this ECP...................... 273) n

401-601-009, Issue 10


AR - Cellular Network (net) Form

An example of the net form is shown in Figure K on page 29.

Figure K. Example of net Form (Screen 1) ECP Release 17.0

Multiple System Flood PagingThis field indicates whether flood paging of all mobiles in an FTN will occur. See Table 12 on page 67 for descriptions of the parameters.

Multiple System Compatible Flood PagingThis field indicates whether flood paging will be immediate. See Table 12 on page 67 for descriptions of the parameters.

AUTOPLEX Cellular CELLULAR NETWORK (net) Screen 1 of 20 System

Cellular Network Entity Number.................*1) 1

Cellular Networking Feature Active............. 2) n Maximum Inter-Switch Trunks Allowed Per Call... 3) 0

Multiple System Flood Paging................... 4) _ Multiple System Compatible Flood Paging........ 5) _ Technology to Page............................. 6) last Final Technology to Page....................... 7) multiple Are Local DCSs in Different FTNs............... 8) _ FTN of Multiple-MSC FTN........................ 9) __ Sub-MSC Paging Status.......................... 10) off Sub-MSC Paging Initial Paging Type............. 11) n Sub-MSC Paging Final Paging Type............... 12) n Sub-MSC Paging Pre-Paging Force Direct Page.... 13) n Print TI message for SMP Pre-Paging Mismatches. 14) n

401-601-009, Issue 10


AR - Network Neighbor (nnbr) Form

An example of the nnbr form is shown in Figure L on page 30.

Figure L. Example of nnbr Form (Screen 1) ECP Release 17.0

Unit of Expiration TimeThis field indicates the unit of time for expiration of records in the vlr database for roamers homed on a system with this ESID. Values that may be entered in this field are minutes (m), hours (h), days (d), or weeks (w). The recommended value is h.

See Table 15 on page 69 for descriptions of parameters.

AR for CDMA Forms

In the following RC/V forms, a plus mark (+) before the field number indicates that the field is defined at a system level (ECP or CGSA) and can be redefined, if required, at a lower level (cell or physical face). These fields are referred to as having overriding parameters. The value of fields with overriding parameters are displayed on a lower level form (for example, cell2) only if the technician has specifically overridden a higher level value via that form. In such a case, the values shown on the higher level form no longer apply for that particular cell. When a value has not been overridden, a blank appears on the lower level form.

AUTOPLEX Cellular Network Neighbor (nnbr) Screen 1 of 6 System Extended System Identifier: Switch.................*1) __ (optional) : ECP ...................*2) __ : System ................*3) _____ Message Default Values: Inter-vendor Msg Method...... 4) 1 Suppress Route Request....... 19) n Originating Major Class...... 5) 2 High End Timer Units......... 20) d Unit of Expiration Time...... 6) d High End Timer Value......... 21) 0 Expiration Time (in units)... 7) 0 Override Timer Units......... 22) d Timeout Treatment Indicator.. 8) r Override Timer Value......... 23) 0 Multiple System Networking... 9) n SystemMyType................. 24) 0 TIA Authorization Period.... 10) a SystemAccessType............. 26) n RTA Allowed................. 11) n Suppress RedirectionRequest.. 27) n Translation Type (MIN)...... 12) ___ Translation Type (IMSI)..... 13) ___ CDMA Multiple Pilots Handoff 14) n CDMA OTAPA Allowed.......... 15) n Extend Registration Timer....... 28) n CNIR Authorization REGNOTRR.. 16)n ANSI-41 Compliant Leg Support... 29) n REVC Route Request RR........ 17)n Non-Compliant Leg No Answer Time 30) 0

401-601-009, Issue 10


AR - Cellular Geographic Service Area (cgsa) Form

An example of the cgsa form is shown in Figure M on page 31.

Figure M. Example of cgsa Form (Screen 1) ECP Release 17.0

CDMA Registration Zone IDThis field specifies the CDMA registration zone identification that applies to all cells in this CGSA. Zone ID is equivalent to Location Area. The values accepted for this field are 0 to 4095, with a default of 0. This field has overriding parameters and also appears on the cell2 and ceqsu2 forms.

AUTOPLEX Cellular CELLULAR GEOGRAPHIC SERVICE AREA (cgsa) Screen 1 of 8 System Cellular Geographic Service Area...............*1) __ ACC Location Area ID...........................+2) 0 DCCH Virtual Mobile Location Area..............+3) 0 CDMA Registration Zone ID......................+4) 0 Maximum Number of Access Channels to Scan...... 5) 21 Use New Access Channel Range................... 6) n Maximum Number of Paging Channels to Scan...... 7) 21 New Starting Access Channel Number............. 8) 0 System Identification.......................... 9) _____ - Alternate SID for AMA...................... 10) _____ CDMA System Identification.................... 11) _____

401-601-009, Issue 10


Figure N. Example of cgsa Form (Screen 2) ECP Release 17.0

CDMA Time-Based Registration PeriodThis field enables time-based registration and defines the time-based registration interval. Values for this field are 29 to 85. This field has overriding parameters and also appears on the cell2 form. If both the cgsa and cell2 values are blank, CDMA time-based registration is disabled.

AUTOPLEX Cellular CELLULAR GEOGRAPHIC SERVICE AREA (cgsa) Screen 2 of 8 System

DCCH Alphanumeric SID (ASID).................. 12) _______________ DCCH ASID active.............................. 13) n System Operator Code.......................... 14) ____ IS-136 Emergency Routing Number............... 15) _______________ Roamer Major Class of Service - Originations.. 16) 1 - Terminations.. 17) 1 Roamer Service Authorization.................. 18) y Serial Number Checking........................ 19) y Roamer Service List Check..................... 20) y Fraudulent Mobile Serial Number Checking...... 21) y CDMA Time-Based Registration Period.......... +22) __

401-601-009, Issue 10


AR - Series II Cell (cell2) Form

An example of the cell2 form is shown in Figure O on page 33.

Figure O. Example of cell2 Form (Screen 1) ECP Release 17.0

CDMA Registration Zone IDThis field specifies the CDMA registration zone identification associated with this particular cell. Values accepted for this field are 0 to 4095, with a default of 0. A per-cell value takes precedence over the cgsa form value for this field, but if the cell2 field is null, the cgsa form value is used.

AUTOPLEX Cellular SERIES 2 CELL (cell2) Screen 1 of 21 System

Cell Site Number............................ *1) ___ ACC Location Area ID........................ +2) ____ DCCH Virtual Mobile Location Area........... +3) ____ CDMA Registration Zone ID............. +4) ____ VZID/CID Cell ID............................ 5) ____ Cellular Geographic Service Area............ 6) 1 Switch Identification....................... 7) 1 Virtual Switch Identification............... 8) __ CDMA Switch Identification.................. 9) __ CDMA Virtual Switch Identification.......... 10) __ Cell Site Status............................ 12) g Location Equipped Antenna Faces............. 13) 0 Wait for Overhead Message................... 14) n

401-601-009, Issue 10


The form shown in Figure P on page 34 is used to enable/disable registration of CDMA-capable roaming mobiles. Values for this field are y (yes) or n (no), with a default value of n.

Figure P. Example of cell2 Form (Screen 9) ECP Release 17.0

Should Home Mobiles RegisterThis field is used to enable/disable registration of CDMA-capable home mobiles. The values for this field are y (yes) and n (no). The default value is n.

CDMA Time-Based Registration PeriodThis field enables time-based registration and defines the time-based registration interval. Values for this field are 29 to 85. This field has overriding parameters and also appears on the cgsa form. If both the cell2 and cgsa values are blank, CDMA time-based registration is disabled.

Power-UP/Power-Down RegistrationThis field enables/disables the CDMA power up/power down registration parameter. Values are y (yes) or n (no), with n as the default.

AUTOPLEX Cellular SERIES 2 CELL (cell2) Screen 9 of 21 System Cell ___

Autonomous Registration ACC DCCH CDMA Should Home Mobiles Register.......................... 167) n 168) n 169) n Should Roamer Mobiles Register (FSID Indicator) ...... 170) n 171) n +172) n Offset of Registration ID for This Cell.........+173) 0 Maximum Interval Between Mobile Registrations... 174) 2000 Time Interval to Increment Registration ID (sec) 175) 0 Transmission Rate for Registration Message 176) 10 AR Overload Threshold (Max. # of ARs in 6 sec).. 177) 60 TDMA DCCH Registration Periodicity (min)........+178) ___ CDMA Time-Based Registration Period.............+179) __ CDMA Parameter Change Registration...............180) n Enhanced Registration ACC DCCH CDMA Power-Up/Power-Down Registration...................... 181) n 182) n 183) n Location Area/Zone ID Registration.................... 184) n 185) n 186) 0 CDMA Zone ID Registration Timer..................187) 0 TDMA DCCH Deregistration.........................188) n

401-601-009, Issue 10


Location Area/Zone ID RegistrationThis field enables/disables the CDMA zone-based registration parameter. Values are in the range of 0 through 7. This field controls the stored zone data in a mobile. This is done by specifying the number of total zones the mobile is allowed to keep in its zone list memory. A value of 0 indicates that the zone-based AR is disabled.

CDMA Zone ID Registration TimerThis field changes the zone_tmr variable from a one-minute hard coded value to a translatable parameter. This timer specifies the time-interval for the mobile to remove all except the last accessed zone ID from its memory. The CDMA Time-Based Registration Period is still used to tell the mobile how often it should register to the system. The accepted range for this field is 0 through 7. The default value is 0. The table below indicates the allowed values and the corresponding time in minutes.

Table 3. Zone Timer Value with Minutes

Zone Timer Value Minutes

0 1

1 2

2 5

3 10

4 20

5 30

6 40

7 60

401-601-009, Issue 10


AR - Series II Cell Equipage Setup (ceqsu2) Form

An example of the ceqsu2 form is shown in Figure Q on page 36.

Figure Q. Example of ceqsu2 Form (Screen 1) ECP Release 17.0

ACC Location Area IDThis field specifies the CDMA registration zone identification that applies to a setup face for each CDMA-equipped sector. The values accepted for this field are 0 to 4095. This field has overriding parameters and also appears on the cgsa and cell2 forms. If no value is entered, the value from the cell2 form is used. If there is no value on the cell2 form, the value from the cgsa form is used.

System Interaction - ER in DCCH Forms (TDMA)

In the RC/V forms that follow, a plus mark (+) before the field number indicates that the field is defined at a system level (ECP or CGSA) and can be redefined, if required, a lower level (cell or physical face). These fields are referred to as having overriding parameters. The value of fields with overriding parameters is displayed on a lower-level form (for example, cell2) only if the technician has specifically overridden a higher level value by using that form. In such a case, the values shown on the higher level form no longer apply for that particular cell. When a value has not been overridden, a blank appears on the lower level form.

AUTOPLEX Cellular SERIES 2 CELL EQUIPAGE SETUP (ceqsu2) Screen 1 of 5 System Cell Site Number......................................*1) ___ Setup Face............................................*2) _ ACC Location Area ID...........................+3) ____ DCCH Virtual Mobile Location Area.....................+4) ____ VZID/CID Zone ID...................................... 5) ___ Directional Setup Allowed............................. 6) _ Cell Sector Type...................................... 7) _ Color Codes - Digital................................. 8) _ - 1st TDMA Supervisory Digital............ 9) _ - 2nd TDMA Supervisory Digital........... 10) _ Control Mobile Attenuation Code...................... 11) 0 Paging - Setup Channel Number........................ 12) ____ - Attenuation Code............................ 13) 0

ACC RAND Broadcast Frequency.........................+14) __

401-601-009, Issue 10


ER - Cellular Geographic Service Area (cgsa) Form

An example of the cgsa form is shown in Figure R on page 37.

Figure R. Example of cgsa Form (Screen 1) ECP Release 17.0

DCCH Virtual Mobile Location Area (VMLA)This field indicates the VMLA of the setup face per CGSA for each DCCH-equipped CGSA. This field ensures that a valid mum is available if location area ER is activated on any DCCH-equipped cells in the CGSA. (The mum parameter is equivalent to the locaid parameter associated with the ACC Location Area ID field on this form.) The values accepted for the DCCH Virtual Mobile Location Area field are from 0 to 1023, with a default of 0. Both the DCCH Virtual Mobile Location Area and the ACC Location Area ID fields have overriding parameters and appear on the cell2 and ceqsu2 forms as well. Table 16 on page 69 describes the parameter locaid.

AUTOPLEX Cellular CELLULAR GEOGRAPHIC SERVICE AREA (cgsa) Screen 1 of 8 System Cellular Geographic Service Area...............*1) __ ACC Location Area ID...........................+2) 0 DCCH Virtual Mobile Location Area..............+3) 0 CDMA Registration Zone ID......................+4) 0 Maximum Number of Access Channels to Scan...... 5) 21 Use New Access Channel Range................... 6) n Maximum Number of Paging Channels to Scan...... 7) 21 New Starting Access Channel Number............. 8) 0 System Identification.......................... 9) _____ - Alternate SID for AMA...................... 10) _____

CDMA System Identification.................... 11) _____

401-601-009, Issue 10


ER - Series II Cell (cell2) Form

An example of the cell2 form is shown in Figure S on page 38.

Figure S. Example of cell2 Form (Screen 1) ECP Release 17.0

DCCH Virtual Mobile Location Area (same as VMLA)This field indicates the VMLA of the setup face per cell for each DCCH-equipped cell. Values range from 0 to 1023. If no value is entered, the value from the cgsa form is used. This field has overriding parameters and appears on the ceqsu2 form as well as on the cgsa form. Refer to the cgsa form description in the previous subsection for a more detailed description.

AUTOPLEX Cellular SERIES 2 CELL (cell2) Screen 1 of 21 System

Cell Site Number............................ *1) ___ ACC Location Area ID........................ +2) ____ DCCH Virtual Mobile Location Area...... +3) ____ CDMA Registration Zone ID................... +4) ____ VZID/CID Cell ID............................ 5) ____ Cellular Geographic Service Area............ 6) 1 Switch Identification....................... 7) 1 Virtual Switch Identification............... 8) __ CDMA Switch Identification.................. 9) __ CDMA Virtual Switch Identification.......... 10) __ Cell Site Status............................ 12) g Location Equipped Antenna Faces............. 13) 0

401-601-009, Issue 10


Figure T. Example of cell2 Form (Screen 9) ECP Release 17.0

Power-Up/Power-Down Registration (for DCCH)This field

Documents

401-601-009