Pan American Wireless Infrastructure Division

Ft. Lauderdale Center for Excellence

CDMA Network Operations

Prepared & Presented by Antonio Shappley

PWID Training: CDMA Foreword

Motorola Confidential Proprietary

3 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Foreword

Foreword

The objective for this course is to present the SuperCell CDMA system network operations in detail, in order to prepare Motorola Personnel for placing a CDMA system in operation. It is recommended that students take the following courses (available from TED) in preparation for this course:
- GNL180: IS-95 Implementation & Operation - GNL190: CDMA Call Processing - CNL070: SC9600 Overview (CDMA)

Most of this manual presents Motorola Condential Proprietary information, so care must be taken by the student to comply with POPI regulations at all times. This course was prepared by Antonio Shappley of the Training & Certications department, based out of Ft. Lauderdale, Florida. Some material for this course has been taken from other groups documentation- please see the Acknowledgements section for the names of these groups and/or individuals.

4 of 259

Motorola Confidential Proprietary

Table of Contents:
Foreword 4 Introduction to CDMA Theory & IS-95 Standard 7 An Introduction to the SuperCell System 37 The Tandem MM Platform & UNIX OS 73 The OMC-R and UNO Platforms 111 The Transcoder Platform 131 The SS7 Sub-System: MM and MSC 163 The SC9600 BTS 181 Output from Work Sessions 193 CDMA Call Processing 207 Tricks, Tips & Tools for Unix and CDMA 237

Motorola Confidential Proprietary

5 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Page Intentionally left blank.

6 of 259

Motorola Confidential Proprietary

PWID Training: CDMA

Introduction to CDMA Theory & IS-95 Standard

Motorola Confidential Proprietary

7 of 259

Objectives:
To present a basic introduction of the CDMA technology and the IS-95 standard, as it pertains to Motorolas SuperCell product.

8 of 259

Motorola Confidential Proprietary

Table of Contents:
Fundamental Statements................................................................................................ Why CDMA?................................................................................................................... Fundamental Comparisons............................................................................................ CDMA Basic Concepts ................................................................................................... Digital Voice Coding Concepts....................................................................................... Basic Digital Signaling Concepts- Isomorphism & Spreading Sequences .................. Multiple Conversations on One Channel? .................................................................... Forward CDMA channels .............................................................................................. Reverse Link Channels................................................................................................... IS-95 Forward Link Encoder ......................................................................................... IS-95 Reverse Link Encoder .......................................................................................... CDMA Call Processing Overview .................................................................................. CDMA Handoffs............................................................................................................. 11 13 15 17 19 21 23 25 27 29 31 33 35

Motorola Confidential Proprietary

9 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

What is CDMA?

Code Division Multiple Access:

Digital technology for secure transmission of data. CDMA is used in a Cellular Radio environment:
BTS

Forward Link MS Reverse Link MS MS

CDMA Channel Bandwidth (Either Forward or Reverse Channel): .27 Mhz 1.23 Mhz

.27 Mhz

Many users may occupy a physical CDMA channel at one time. Mobile Stations are dual or tri-mode (CDMA, AMPS, NAMPS).
10 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Fundamental Statements CDMA- Code Division Multiple Access:

CDMA technology was developed originally by the government in order to provide a secure communications path which was also resistant to the effects of jamming by enemy signals. CDMA spreads the digital data which represents the signal to be delivered over a wide frequency spectrum, thus lessening the negative effect of a narrow bandwidth jamming signal at a particular frequency. The CDMA technology was rst proposed for use in a cellular environment by a company called QualComm, based in San Diego, California. QualComm owns many patents on the CDMA technology for cellular- Motorola has made licensing agreements with QualComm in order to build CDMA equipment. CDMA is dened by an Interim Standard of the CTIA: IS-95. The rst physical CDMA channel will require 1.77 Mhz (1.23 Mhz at 3dB point, 270 Khz guard band on each end). This is the equivalent of 59 AMPS channels. Note that if CDMA is being deployed at 800 MHz (the AMPS band), then 59 AMPS channels must be cleared from use in the area in which CDMA is being deployed. Each additional carrier requires a separation from other CDMA carriers of 200 kHz. Recommended center frequency AMPS channels for the A-Bands rst CDMA carrier are 283 (Primary CDMA channel), and for the B band its 384 (Primary). Multiple logical channels reside in a single physical channel. A Forward CDMA channel carries trafc from the Base Site to the Mobile Station. A Reverse CDMA channel carries trafc from the Mobile Station to the Base Site. A CDMA channel (either Forward, or Reverse) will be utilized by multiple Mobile Stations. Special digital codes are used to keep the conversations apart. CDMA Mobiles are being built by Oki, QualComm, Motorola and other companies. Most of these mobiles are either dual mode (CDMA/AMPS), or tri-mode (CDMA/ AMPS/NAMPS).

NOTES:

Motorola Confidential Proprietary

11 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Why CDMA? ??????????

Provides more capacity than any other system, digital or analog. Secure system. Make-before-break handoffs. Adapts to varying load conditions. Mobiles utilize less transmit power:
- Raising battery life - Lowering health risks

Utilizes additive multipath.

12 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Why CDMA? Before embarking on a study of CDMA technology and Motorolas CDMA product, it is convenient to study the reasons why CDMA is receiving so much attention in the cellular world today.
Current analog system (TACS, AMPS, NAMPS, etc.) are rapidly reaching their saturation point. Although in theory analog systems could expand without bounds by introducing microcells and more powerful computers, the cost of this expansion is prohibitive. A new system is required which will provide more capacity than these analog systems- CDMA (in theory) provides up to 10 times the capacity of AMPS systems. CDMA provides the highest level of security of any digital or analog system currently on the market. By encoding the signal to be transmitted with digital sequences which are extremely hard (if not impossible) to reproduce by eavesdroppers, a fraud-proof system can be achieved. This is very attractive to cellular operators, since fraud is very common in current analog cellular technology. CDMA is currently the only system to provide make-before-break handoffs. This means that the signal is not interrupted while the mobile station starts functioning with another base station. The perceived voice quality is improved in CDMA (over any other system) due to this feature. A CDMA cell site can automatically change its output power, and thus change the cells coverage area. This change in output power is inversely related to the amount of trafc covered in a cell- thus, a cell which is handling much trafc will shrink its coverage area, and other cells around it will pick up some of the trafc in the remaining area. It is critical that all CDMA mobiles use only the power necessary to achieve a good signal at the base site. As a result, CDMA mobiles utilize very little power on averagethus, CDMA mobiles will have longer batter life than their analog or digital counterparts. This feature of CDMA also results in lowered health risks. The CDMA technology utilizes a concept called additive multipath, in which timedelayed versions of the same signal are combined in a way such that the nal signal is always stronger than any of the separate paths. Thus, CDMA will provide a better quality of service due to this feature.

NOTES:

Motorola Confidential Proprietary

13 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Comparison of Cellular Technologies:

1.23

FDMA: physical channel = 30 kHz, 1 user at one time. TDMA: physical channel = 30 kHz, 3 users (3 logical channels), each at a given time-slot. CDMA: physical channel = 1.23 MHz, N users, each with a given code which keeps the conversations separate. CDMA can utilize FDMA concepts by employing multiple CDMA channels.
14 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Fundamental Comparisons FDMA (AMPS, N-AMPS, TACS):

An FDMA AMPS channel separation (separation between center frequencies) is 30 Khz, while NAMPS channel separation is 10 Khz, and TACS is 25 Khz. One channel (i.e. one frequency) may be utilized by only one user at a time. Channels are assigned to conversations on-demand; there is a hard limit on the number of simultaneous conversations allowed.

TDMA (GSM, PDC, IS-54):

Each conversation is assigned a given amount of time (a time slot) on a single FDMA channel. In GSM, up to 8 users may utilize a single FDMA channel (200 Khz channel separation) simultaneously, while PDC and IS-54 both place up to 3 users per AMPS channel (30 Khz). Channels are assigned on-demand; thus the hard limit still exists.

CDMA:
Physical channels consists of a relatively large bandwidth (1.23 Mhz). Multiple conversations (logical channels) are supported on the same physical channel. Special digital codes called Walsh codes and special pseudo-random noise sequences called Pn codes are utilized to keep conversations apart on the same physical channel. A hard limit does not exist, since the system is limited by the noise level on a CDMA channel. To enable more conversations, the overall quality of all the conversations may be slightly diminished for a short period of time. FDMA concepts may be utilized in a CDMA system by providing multiple CDMA carriers, each occupying 1.23 Mhz of bandwidth. Frequency planning must be employed in order to take advantage of the multiple carriers.

NOTES:

Motorola Confidential Proprietary

15 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Concept: The International Party:

Each conversation shares the same spectrum. Every pair speaks a different language. If noise level increases, all guests must raise their volume. Guests may go to another room if the noise is too high. One guest speaking too loudly can ruin all other conversations.

16 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Basic Concepts CDMA- Similar to an International Cocktail Party:

Couples speak different languages (French, German, Spanish, English, etc.). Thus, we see that linguistic diversity is used to enable different conversations at once in the same airspace. If the total volume is too high in the room, some couples may opt for going to another room and continuing their conversation there. Thus, we see that spacial diversity may also be utilized to enable more conversations. A single person who raises his or her voice level will cause the other couples in the room to have more difculty in understanding each other. These other couples may be forced to increase their volume as well. This process quickly results in having an unacceptably high level of noise in the room. A load rock-and-roll band (or any kind of music, for that matter), would cause the total noise in the room to increase as well. This will again cause couples to raise their volume in order to be heard, and could result in the same situation as above. Couples who are in close proximity do not need to use a high volume level in order to be heard, thus these couples do not contribute as much to the noise level in the room as do other couples who are farther apart.

Conclusions from the International Party which apply to CDMA:

Existing noise oor must be low (i.e. rock-and-roll band must play with low volume). This means that the existing radio spectrum must be clear from interference (microwave operators at 1.9 GHz, and regular AMPS spectrum at 800 MHz are two examples of interference contributing to the noise oor). Power control is crucial in CDMA. Mobiles that are close to the BTS must use a smaller transmit power than mobiles that are farther away. It is crucial that all mobiles be transmitting the lowest possible power at all times, since each mobile contributes to the general noise oor perceived by all other mobiles that are operating at the same CDMA frequency. The concept of using different languages at the party is parallel to using digital codes in CDMA. By multiplying the digital stream of data (which represents the conversation) by a much longer sequence of digital data which has been specially selected, the original data can be combined non-destructively with other conversations on the same physical channel. NOTES:

Motorola Confidential Proprietary

17 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Digital Voice Coding Concepts

A/D

QCELP Encoder

QCELP Decoder

D/A

Digital voice coding concepts called vocoding used in CDMA. Encoder takes digital samples of analog voice waveform as input, outputs stream of digital codes. Decoder does the inverse. Objectives:
- Minimize amount of data transmitted - Maintain acceptable voice quality - Keep equipment affordable

QCELP: QualComm Code-Excited Linear Predictive Coding. Vocoder is variable-rate: .8, 2, 4, 8.6 and 13 Kbps.

18 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Digital Voice Coding Concepts The human voice produces analog waveforms. These waveforms are picked up by a microphone, and transmitted as electrical impulses to a circuit which performs analog to digital conversion. The manipulations performed on the resulting digital stream are performed by a device called the vocoder. Some points regarding the device are as follows:
Conversion from a digitally sampled waveform (call Pulsed Code Modulation or PCM) to a compressed digital format is called encoding. Conversion from a compressed digital format back to PCM is called decoding. The CDMA vocoder functions on the basis of modeling the human voice tract as a linear predictive lter. The lter uses a pitch generator and a white noise generator as inputs, and determines the set of parameters (called lter coefcients) for the lter in order to best represent the 20 ms of speech being encoded. The result is data which represents parameters to be fed to the decoder in order to reproduce the speech. The number of bits transmitted to represent the parameters can be modied- thus modifying the resolution of the lter parameters. It is logical to deduce that as higher voice quality is desired, more bits will be needed to reproduce the lter parameters more faithfully at the decoder. The CDMA SuperCell vocoder is a variable rate vocoder, supporting rates of .8, 2, 4, 8.6 and 13 Kbps. The 13 Kbps rate is not part of the IS-95 standard, rather it is an effort (by Motorola) to provide an option for high quality voice. In addition, several companies (including Motorola) have been working on an enhanced 8 Kbps vocoder which reportedly provides very good audio quality. The vocoder switches the encoding rate based on the perceived energy of the signal being encoded. That is, if the person is listening (not speaking at all), a slower vocoding rate will be utilized in order to send fewer bits over the transmission medium. One of the side-effects of this is that background noise is diminished during a conversation with a low voice activity factor (many silences in the conversation, or one party speaks most of the time). The technology for the CDMA vocoder is called QCELP, for QualComm Code Excited Linear Prediction.

NOTES:

Motorola Confidential Proprietary

19 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Digital Signaling Concepts- Work Sheet

Fill-in rst two rows with zeros and ones:

X-OR the rst two rows, place result in third. Copy third row above into rst row below, second row above into the second row below. X-OR the two sequences.

Increase the ratio of bits in the scrambling code to the bits in the data sequence up to 4:1:

Introduce errors, de-code as above.

When scrambling code has more bits than the data being scrambled, resulting sequence has wider BW.

20 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Basic Digital Signaling Concepts- Isomorphism & Spreading Sequences The work sheet on the previous page will help in understanding two basic principles: isomorphism and signal spreading.
An X-OR of two binary sequences will yield another binary sequence, which when XORed by either of the rst will result in the remaining sequence. This property is called isomorphism. For binary sequences, both modula-2 multiplication and X-OR operations exhibit this behavior. If one of the X-ORed sequences is made longer (i.e. one sequence is multiplied by several bits of the other sequence), then the resulting sequence will have the same amount of bits as the longer sequence. When a binary sequence which is running at a slow speed is X-ORed by another binary sequence which is running at a higher speed, the result is a binary sequence which runs at the higher speed. Translating this into the frequency domain, the slower binary sequence occupies a smaller bandwidth, while the faster binary sequence occupies a larger bandwidth. By X-ORing a slow sequence by a fast sequence, the slow sequence is spread to a larger bandwidth. In order to recuperate the original (slower) sequence, the resulting fast sequence is XORed by the same fast sequence used to spread the slower sequence, then the result is integrated (averaged) across every <N> bits to produce the original (slower) sequence. Note that we must use the exact same spreading sequence! In CDMA, the slower sequence is the data which we want to transmit (which has been digitally manipulated to insure more resistance to fading and interference), while the faster (spreading) sequence is called the Pseudo-random noise code (Pn code). The resulting fast sequence is used to modulate the RF carrier. Note that the Pn code must be carefully selected, since we want a good balance of ones and zeros (imagine how bad the spreading would be if the Pn code were all zeros!). Also note that, since there is a processing gain (in the work sheet, the gain is 4:1), the resulting signal is more resistant to fading.

NOTES:

Motorola Confidential Proprietary

21 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Multiple Conversations on One Channel?

Most denitely!
Physical RF carrier of 1.23 Mhz transmits multiple conversations. Multiple CDMA carriers may exist, each with many virtual channels on it.

How?
Spreading sequence runs at 1.2288 Mcps, while data runs at 9600 bps... 128 chips per bit. Up to 63 bits can be damaged, and original bit can still be recovered! Digital properties of orthogonality and auto-correlation used to determine Pn sequences and Walsh codes. Different Pn code offsets used between BTSs, to keep conversations from interfering.

22 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Multiple Conversations on One Channel? The concept of having multiple conversations multiplexed on one physical channel at the same time is one of the main differences between CDMA and any other system. Understanding how this is achieved is beyond this section (more to follow in another section). However, the following is presented to give the reader some clues:
Special digital codes called Walsh codes multiply the data to be sent in order to increase the probability of de-coding the conversation after all other conversations have been multiplexed on the same channel. Walsh codes are orthogonal, which implies that the multiplication of a Walsh code with another Walsh code will not produce another Walsh code. Pn codes are specially selected so that a time-displaced version of the code multiplied by the same Pn code with another time-displacement will result in zero. Pn code offset is a term that is utilized often in CDMA, since each CDMA BTS will transmit with a different time-offset of the same Pn code. Since multiplication of the codes will result in zero, CDMA cell sites can use the same CDMA carrier even though the sites are next to each other! The CDMA system changes the Pn code being used very rapidly in order to provide resistance to fraud. Due to the time-orthogonal nature of the forward link, all cell sites transmitting the same CDMA carrier must change their Pn code at exactly the same time. In order to do this, each cell site needs an absolute time reference, which is taken from Global Positioning System satellites orbiting the earth.

NOTES:

Motorola Confidential Proprietary

23 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Forward Link Channels:

Forward CDMA Channel (1.23 MHz)

Paging Paging Trafc Trafc Sync Trafc Trafc Pilot Channel * * * Channel Channel * * * Channel Channel Channel * * * Channel Channel 1 7 1 23 24 55

W0

W1

W7

W8

W31

W32
Trafc Channel N

W33

W63

Wn = Walsh code channel.

CDMA Strau Data

Power Control

Walsh codes used to separate conversations on Forward link. 64 Walsh codes, each assigned as illustrated above. Pilot Channel used by MS to acquire CDMA system. Sync Channel used by MS to acquire synchronization and system parameters. Paging Channels used to broadcast pages and order messages to MS. Trafc Channels carry CDMA STRAU frames, along with Power Control Bits.

24 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Forward CDMA channels

Logical channels inside the forward CDMA link are identied through the use of timeorthogonal codes called Walsh codes. Walsh codes are binary sequences of 64 bits in length. The fact that they are orthogonal implies that one code multiplied by another will not result in another of the 64 codes. This property of orthogonality only holds true when the Walsh codes are not displaced with respect to one another- this is why Walsh codes are used to separate conversations only on the Forward link. Assignment of the 64 possible Walsh codes is as follows: Walsh 0 is the Pilot Channel. Walsh 1-7 are the Paging Channels. Walsh 32 is the Synch Channel. All other Walsh codes (55 in all) identify trafc channels.

The Pilot Channel allows the mobile stations to identify the cell site or sector which the mobile stations are listening to, and it provides a coherent phase reference so that the mobile station can de-modulate the other channels correctly. The Pilot Channel does not transmit any data, it only transmits the carrier modulated by Walsh code zero (which is made up of all zeros). The Synch Channel constantly transmits a single message containing information needed by the MS in order to synchronize with the CDMA infrastructure, and to be notied of certain data such as system and network identication numbers. The trafc channels carry the users encoded data bits, which are in data packets called STRAU frames, along with power control information (one bit every 1.25 ms)- a 1 means lower power by 1 dB, a 0 means raise the power by 1 dB).

NOTES:

Motorola Confidential Proprietary

25 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Reverse Link Channels:

Reverse CDMA Channel (1.23 MHz)

Access

Access

Trafc *** *** *** ***

Trafc Channel M

Channel * * * Channel Channel 1 N 1

Addressed by Long Pn Code Offsets

Reverse Link modulation is different- channels are separated by different offsets of a long digital code sequence. Certain offsets set aside for use as Access Channels. IS-95 provides for maximum of 30 Access Channels per Paging Channel. Access Channel used by MS to communicate with the BTS when MS is NOT on a trafc channel.

26 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

Reverse Link Channels CDMA Reverse Link Channel Structure

Modulation on the reverse link is different than for the forward link- time offsets of the Pn long code are used to keep conversations separate, and Walsh codes are used to represent the data being sent. The Pn Long Code is a 42 bit code, so there are 242-1 possible time shifts of the Pn Long Code. Thus there are 242-1 codes available which may identify separate conversations. Access Channels are used whenever the mobile is not on the Trafc Channel and must communicate with the Base Site. Access Channels are used for the following: Call Originations Responses to Page Responses to Order messages from BTS Mobile Registrations

There are a maximum of 30 Pn Long Code offsets per paging channel (for a maximum of 210 offsets) which are reserved for Access Channels. Those Pn Long Code offsets which are not used for access channels may be used as trafc channels.

NOTES:

Motorola Confidential Proprietary

27 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

IS-95 Forward Link Encoder

28 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

IS-95 Forward Link Encoder

At the top of the encoder diagram is the Pilot channel. Note that Walsh code 0 (which is composed of all zeros) is used to spread a digital sequence which is all zeros, and then the result (which will be all zeros) is sent to the quadrature spreader and then used to modulate the carrier. A convolutional encoder will scramble the bits to be sent, and at the same time will produce more bits at the output than those presented at the input. The encoder loads <length> bits into registers, and then performs operations (such as ORs and ANDs) on the bits. The results of the operations are then sent as output. The rate of the convolutional encoder in IS-95 can be either 1/2 (meaning that two bits are output for every bit of input), or 1/3 (meaning that three bits are output for every bit of input). Symbol repetition basically repeats each symbol a given amount of times. This is done in order to insure proper delivery at the other end. The Block Interleaver will shufe large blocks of bits around such that spurious errors can be recovered through CRC error correction. The Sync channel data runs at 1200 bps, always repeating the same message (which contains information on the system time, long code state, etc.). This information is sent to a 1/2 rate convolutional encoder, and then to a 2x block interleaver. This information stream is spread by Walsh code 32 and then sent to the quadrature spreader. The Paging channel data is run through a convolutional encoder, symbol repeater, block interleaver, and then the information is scrambled through the use of a Pn long code. The receiving side knows the long code and the mask used, so it can de-scramble the information. The Paging channel may transmit at any of several rates: Motorola is currently using 4800 bps. The Trafc channel will transmit data from the vocoder at a variable rate (which will be determined by the vocoder). This data is sent through a convolutional encoder, symbol repeater, and block interleaver. The rate of symbol repetition will depend on the rate of the data coming from the vocoder- the end result is always a data stream of 19.2 ksps (symbols per second). This stream is scrambled with a long code, using a long code mask which is based on the users mobile id number. The Trafc channel also carries power control bits- these bits are pushed onto the stream of data bits (called blank-and-burst).

NOTES:

Motorola Confidential Proprietary

29 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

IS-95 Reverse Link Encoder

Access channels and Trafc channels on reverse link. Convolutional encoder is rate 1/3 (as opposed to rate 1/2 on fwd link). Modulation is through a Orthogonal Modulator. Interference is minimized at lower bit rates by Data Burst Randomizer. Signal is scrambled with long code.

30 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

IS-95 Reverse Link Encoder

The Reverse Link is composed of two types of channels: Access channels, and Trafc channels. Access channels use a data rate of 4800 bps, while Trafc channels have variable rate. Data is output by the IS-95 variable-rate vocoder at either .8, 2.0, 4.0, or 8.6 kbps. This data stream is fed to a Cyclic Redundancy Code generator, which will add data for reconstructing erroneous bits. This is done only for the 4 and 8.6 kbps rates, since the other rates will be repeated so often that data integrity can be provided through repetition. After CRC, 8 more bits are added to each frame for encoding purposes- this brings the speed up to 1.2, 2.4, 4.8, or 9.6 kbps. Then the data stream is fed to a convolutional encoder of length 9 bits, and rate 1/3 (meaning that 3 bits will be output for each bit of input). The resulting data stream is fed to a block interleaver, and then to an orthogonal modulator. Orthogonal modulation takes 6 bits of input (which in binary can specify 64 different possibilities), and looks up the corresponding Walsh code. For example, if 6 bits of input are 101100 (56 decimal), then Walsh code 56 will be sent in place of the 6 bits. Since Walsh codes are time orthogonal, its very easy to detect when one Walsh code ends, and another begins by simply comparing each 64 bits with all of the Walsh codes until a perfect match is found. The data burst randomizer will blank out data from the stream to be sent, based on the data rate of the information bits. More bits are blanked out for the lower information data rates, since at lower rates the data is repeated more often. This has the effect of lowering interference on the reverse link when lower data rates are used. The resulting data stream is then scrambled with a long code (which has been modied with a mask based on the mobile id), and then sent to a quadrature spreader.

NOTES:

Motorola Confidential Proprietary

31 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Call Processing Overview

MS Power Up MS Initialization State MS Idle State MS Access State MS Control on Tch State

MS has selected and acquired the System.

MS monitors the Paging chnl.

MS is directed to Trafc chnl.

Call Processing specied by states and events.

- MS may be in any particular state. - Event will cause transition to another state.

Event will be signaled by arrival of message from device in CDMA network. State transitions usually involve performing an action. MS may be in any of the following CP states:
Initialization State Idle State System Access State Control on the Trafc Channel State

32 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Call Processing Overview The process of setting up and tearing down CDMA calls is called Call Processing. Several denitions are presented in order to facilitate the discussion of call processing (CP):
A device can be in any of several call processing states. The more general states are as follows: Initialization State. This is the rst main state, to which an MS will always revert upon critical problems in any of the other states, and to which an MS will transition upon power-up. In this state, rst the system to use is determined (whether CDMA or another technology such as AMPS). If CDMA is to be used, the MS then acquires the Pilot channel, and the Sync Channel. From the Sync channel, the MS is able to synchronize its internal timing mechanisms to that of the CDMA infrastructure. Idle State. From within this state, the MS can initiate registration messages, initiate or receive a call, receive informational messages and orders, and initiate a message transmission. The Pilot channels from different cell sites are constantly being scanned to determine the strongest cell site, and an Idle State handoff may also be performed so that the MS is always listening to the strongest Pilot channel. System Access State. In this state, the MS sends messages to the BTS over any of the Reverse Channel Access channels (of which there are a maximum of 210), and receives messages from the BTS over the Paging channel(s). Control on the Trafc Channel State. The MS is on the trafc channel in this state (presumably transmitting digital data which represents either voice or telemetry being sent from the MS). Power control data is sent to and from the mobile in this state, hand-off orders and trafc data are also sent in this state. An event may cause a transition from one CP state to another. Events will usually be messages sent over communication links to devices which see the physical event taking place (such as a perceived signal quality drop at a transceiver). A state transition will usually involve performing some pre-dened action (such as turning on a busy signal at the MS speaker, or sending an acknowledgment message over the access channel).

NOTES:

Motorola Confidential Proprietary

33 of 259

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Handoffs
MSC

CBSC XC MM

BTS

BTS

BTS

MS

Soft Handoff.
- One CDMA BTS to another CDMA BTS. - Both BTSs under same CBSC. - Same CDMA carrier.

Softer Handoff
- One CDMA sector to another. - Both sectors on same BTS. - Both sectors using same CDMA carrier.

Hard Handoff
- CDMA-CDMA, BTSs under different CBSCs. - CDMA to analog system.

Lists of pilot channels are kept at the MS:

- Active Pilots - Candidate Pilots - Neighbor Pilots
34 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97 Introduction to CDMA Theory & IS-95 Standard

CDMA Handoffs Handoffs are the process of getting a mobile handset to talk to another BTS, or to another sector of the same BTS. The following is information on the different types of handoffs available in CDMA:
Soft Handoff. This is an attractive feature of CDMA, where the conversation or data ow is not interrupted due to the hand-off. Soft handoff can currently be performed when an MS goes from one CDMA BTS to another, where both are under the control of the same centralized controller. Also, the source and target BTSs must both be utilizing the same CDMA carrier frequency. In the near future, soft handoff will be extended so that it applies when the BTSs are not under the same centralized controller. Softer Handoff. This is the same as Soft Handoff, except that it applies only when a CDMA handset goes from one sector to another under the same CDMA BTS, at the same CDMA carrier frequency. Hard Handoff. This occurs under two different circumstances- when a CDMA handset hands-off from a CDMA BTS to an Analog BTS, or when a CDMA handset hands-off between CDMA BTSs which are utilizing different CDMA carrier frequencies. Conversation is interrupted for a brief instance in hard hand-off. The MS is constantly scanning all possible offsets of the Pn code (it takes 26.6 ms per scan cycle), and keeps three lists of Pilot Channels: The Active Set. This is a list of Pilot Channels which are actively used by the MS to transmit digital data. CDMA (IS-95) provides for up to three members in this active set at once. That is, a CDMA handset may be talking over at most three different sectors or cell sites at once. The Candidate Set. This is a list of Pilot channels which are not strong enough to be in the active set, but are strong enough to be candidates for hand-off. Neighbor Set. These are candidates which are very weak, but still visible at the MS. Remaining Set. These are all other Pilot Channels (from the 512 channels that are available in a single CDMA carrier) that are not members of any of the above three sets.

NOTES:

Motorola Confidential Proprietary

35 of 259

Conclusions:
CDMA stands for Code Division Multiple Access. Physical channels: 1.23 MHz in BW, support many logical channels simultaneously. Forward link transmits from BTS to MS, while reverse link transmits from MS to BTS. CDMA is like an International Party, each pair of guests are conversing in a different language. QCELP is the digital variable rate vocoder used. Pseudo-random noise codes carefully selected, making it very difcult to break CDMA. Walsh codes separate conversations on forward link. There are 64 Walsh codes in all. Short Pn code time offsets identify sectors and cells. Long Pn code time offsets identify conversations on reverse link. Soft handoffs are from BTS to BTS (same controller, same carrier). Softer handoffs are from sector to sector (same BTS), while hard HO are from CDMA to analog or from one CDMA carrier to another.

36 of 259

Motorola Confidential Propretary

PWID Training: CDMA

An Introduction to the SuperCell System

Motorola Confidential Proprietary

37 of 259

Objectives:
To present an introduction to Motorolas SuperCell product for CDMA technology in order to provide the student with a basic understanding of the SuperCell product.

38 of 259

Motorola Confidential Proprietary

Table of Contents:
CDMA Network Architecture......................................................................................... CDMA Functional Partitioning ..................................................................................... CDMA System Cardinality ............................................................................................. Basic System Inter-Connections .................................................................................... CDMA CBSC Overview.................................................................................................. Logical Paths through the CBSC................................................................................... The CDMA Tandem Platform ........................................................................................ The CDMA Transcoder .................................................................................................. The CDMA Transcoder Cards ....................................................................................... Transcoder Connectivity................................................................................................. The CDMA BTS ............................................................................................................. The CDMA SC9600 BTS Devices.................................................................................. CDMA Software Overview ............................................................................................. CDMA System Database Creation................................................................................. CDMA Software Installation & Initialization ............................................................... CDMA Customer Interfaces........................................................................................... 41 43 45 47 49 51 53 55 57 59 61 63 65 67 69 71

Motorola Confidential Proprietary

39 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Network Architecture

MSC PSTN

CBSC LMF XC MM

UNO (AP)

OMC-R

BTS

BTS

BTS

LMF voice & control

LMF

Base Site System (BSS)

control / signalling

The Supercell System

MS PSTN MSC MM CBSC Public Switched Telephone Network Mobile Switching Center Mobility Manager Centralized Base Station Controller MS OMC-R Operations & Maintenance Center - Radio XC Transcoder BTS Base Transceiver Station LMF Local Maintenance Facility UNO/AP UNO Platform (Application Processor)

PSTN- provides path to & from land subscribers. MSC- interfaces PSTN to Supercell. CBSC- provides management of real-time cellular radio functions. BTS- provides air interface to MS. LMF used for calibration, on-site maintenance. OMC-R/UNO- provide customer presentation.

40 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Network Architecture This diagram is simplied, so as to present only the major black boxes which implement CDMA. Here are short descriptions for each of the boxes in order to provide a basis for more in-depth discussion:
PSTN - Public Switched Telephone Network, responsible for providing paths to and from land-based telephone subscribers. MSC- Mobile Switching Center, responsible for interfacing the SuperCell CDMA system to the PSTN. The MSC may be provided by Motorola (an EMX2500), or by another vendor. The MSC routes calls to/from the PSTN to the CBSC, and maintains subscriber records and billing. The MSC is NOT considered a part of the SuperCell architecture, although an MSC is necessary to provide cellular service. CBSC- Centralized Base Station Controller. The CBSC is the combination of the MM with the XC and a Router Frame which contains routers, dsus and optionally a XCPC. MM- Mobility Manager. This is a Tandem Computers Integrity-UX box, which is responsible for specialized radio channel management features, managing channel allocation, certain types of handoffs, and is the managing agent for all the managed devices in the SC network (BTS, XC). XC- Transcoder. This box performs transcoding of digital data from PCM to a CDMA format, and it concentrates span lines from many BTSs to the MSC. OMC-R- Operations & Maintenance Center, Radio. This is a Tandem Computers Integrity-UX box, responsible for statistics & alarm collection, and conguration management of one or more CBSCs. UNO- Unied Network Operations Processor. This is a SUN SPARCStation 20, which provides a graphical user interface for managing and providing status of the SC network equipment. BTS- Base Transceiver Station. This entity provides the RF interface to the Mobile Stations. LMF- Local Maintenance Facility. This is a portable PC which is used to perform on-site maintenance of several SC devices, including calibration of the BTS.

NOTES:

Motorola Confidential Proprietary

41 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Functional Partitioning
Billing Records Number Translation Subscriber Database Hard Handoff A+ Interface to CBSC PSTN, IS-41 OMC-R Alarm Management Performance Data Planning Data Storage & Reports Graphical User Interface UNO MSC

Centralized BSS O&M Centralized Conguration Management Code and Data Storage Command Line Interface Event Log/CDL Log Conguration Database A+ Interface to MSC Handoff Arbitration BTS Fault Mngmnt. Channel Allocation Page Distribution BTS Init. & Download

QCELP Transcoding Switching Function Mobile Event Detect. Signalling on the TCH Paging Distribution Soft handoff handling

CBSC Mobility Manager XC

BTS Trafc Channels Power Control Signal Quality Measurements Signalling on page & access channels Softer Handoff GLI MCC Message Routing Site O&M

42 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Functional Partitioning

The MSC has a limited role in Supercell (as compared to analog). It is limited to maintaining billing records, the subscriber database, providing the A+ interface, and dialed digit translations, as well as some functionality for hard handoffs. The OMC-R is the operations & maintenance center for all CBSCs under its control. The OMC-R is the central repository for code and data in the system. Software for SuperCell releases is stored on the OMC-R, and propagated to each CBSC when a software upgrade is performed. In addition, the OMC-R contains the database which species how the CBSCs are congured. The OMC-R also collects Call Detail Logs and statistics for later analysis. The UNO (Unied Network Operations Platform) is the customer presentation platform. This platform presents a user-friendly graphical interface through which the customer may obtain status of the network elements, and the customer may also manage the network through the use of alarms, reports, and CLI (command-line interface) commands. The CBSC is comprised of the MM, XC, DSUs and Routers. The MM is one of the active brains of the system. The MM performs handoff arbitration, device fault management, channel allocation, page distribution, BTS initialization and code download, as well as the collection of alarms and statistics for later relaying to the OMC-R. The XC (Transcoder) performs switching of timeslots and conversion of PCM (PulseCode Modulation) to QCELP (QualComm Code Excited Linear Prediction). In addition, the XC takes care of signaling information while the mobile is on a trafc channel. The XC handles soft handoffs for mobiles under base sites controlled by the XC. The XC also distributes pages to mobiles, and routes control data from the MM to the base sites. The XC may also provide echo cancelling. The BTS (Base Transceiver Site) is composed (among others) of the GLI (Group Line Interface) and the MCC (Multiple Channel Card). The GLI routes messages to/from the CBSC, and it performs site operations & maintenance. The MCC cards handle trafc channels, power control, signaling, quality measurements and softer handoff.

NOTES:

Motorola Confidential Proprietary

43 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA System Cardinality:

PSTN MSC

MSC Other Cellular Network (Analog, CDMA, etc.).

UNO (AP)

OMC-R

CBSC XC MM

CBSC BTS BTS BTS XC MM

CBSC BTS BTS BTS XC MM

BTS

BTS

BTS

CDMA system can be grown to cover large areas. MSC may have multiple CBSCs connected to it. OMC-R will typically control from 1 to 5 CBSCs. CBSC will typically control from 1 to 90 BTSs. Numbers depend on load distribution, software release, and hardware release.
Motorola Confidential Proprietary

44 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA System Cardinality This diagram gives a sense of how devices are inter-connected to cover a large area with CDMA.
The maximum number of sub-tending devices that can be connected to a parent device will depend upon several factors- including the following: The call processing load seen by the sub-tending devices. The release of software and hardware in the devices. The amount of equipment in each of the sub-tending devices (MCC cards, etc.). One MSC may have multiple CBSCs connected to it. The Supercell PDC project in Japan had at one point a single MSC with 7 CBSCs connected to it. One OMC-R may have several CBSCs connected to it. Again, the maximum will depend on the load that the OMC-R is capable of handling. Typical for the Supercell PDC project was to have 3 to 5 CBSCs on one OMC-R. One MM may have several transcoder frames connected to it. The transcoder is expanded with more frames when trafc conditions require the expansion. Each transcoder can handle several BTSs- maximum number will depend on the conditions mentioned above. The Release 4 XC system limits are 50 KBHCA, 200 BTS links, 350 E1/T1 Span lines, 2000 PCM Voice Circuits. The MM in Release 4 will handle 35 KBHCA.

NOTES:

Motorola Confidential Proprietary

45 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Basic System Inter-Connections

MSC CBSC
RS-232 PCM over T1 or E1

OMC-R
UNO

Transcoder
Network Interface

TCP/IP over Ethernet Mobility Manager

Control Bridge TCP/IP over Token Ring

XCDR

Switching Matrix

Network Interface

T1 or E1

A+ over SS7/C7.

BTS

BTS BTS Cluster

BTS

SCAP over LAP-D @ 64 Kbps

Legend:

Traffic Channels. Each T1 Link Control & Data carries 4 TCH. Traffic is QCELP STRAU frames. Traffic

Co-located MM and MSC. Ethernet carries data for OMC-R to AP, MM to OMC-R and MM to XC connections. E1 or T1 span lines carry trafc and control data for the BTS<->XC link. Redundancy for most links is available (for extra $$).

46 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Basic System Inter-Connections This diagram illustrates the basic connections between the network elements which make up a CDMA SuperCell system.
The diagram represents a situation where the MSC is co-located with the CBSC, since the SS7 links are directly connected between the CBSC and the MSC. When the two entities are not co-located, it is necessary to transport the SS7 links through the XC and over a T1 or E1 span line to the MSC. In order to do this, two additional DSUs are needed for the V.35 lines from the MM to be placed on T1 links to the XC. All CDMA systems so far have co-located MSC and CBSCs. Redundancy is present in the system, but not represented in the diagram. There are at least two SS7 links to the MSC, exactly two TCP/IP links between the MM and the XC, and two TCP/IP links between the MM and the OMC-R. Redundancy for the AP was not deemed necessary, so there is only one TCP/IP link over Ethernet between an AP and the OMC-R. A+ over SS7 is used to communicate control data from the MM to the MSC. A+ is an Open Interface, meaning that the information necessary to comply with the interface is freely available, so that any switch manufacturer may build a switch that can talk A+. SCAP (SuperCell Application Protocol) is a set of messages and message formats designed by Motorola for communication with the BTSs. This is a Motorola Proprietary interface, so companies outside of Motorola cannot build Base Sites compatible with this standard. SCAP is sent over a LAPD transport, using one channel of a T1 or E1 carrier. Trafc Channels to the Base Sites are multiplexed 4 to 1 on the T1 time slots. Each Trafc Channel uses 16 kbps of QCELP (QualComm Code Excited Linear Prediction) data. This data represents the speech over the trafc channel- two of these channels (forward and backward) make up a two-way conversation.

NOTES:

Motorola Confidential Proprietary

47 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA CBSC Overview

MM Frame

Router Frame

Transcoder Frame

DSUs Router Router

XC-PC:

E A - 600 mm B - 762 mm C - 457 mm D - 600 mm E - 2,162 mm F - 1,819 mm C min. 457 mm Frame Clearance F B
MM 612 Kg DSU/ 100 Kg Transcod-

A
250 Kg

D min. 600 mm Frame Clear-

CBSC controls all BTSs under it. Code & data download, initialization, fault management, callsetup, call-teardown, soft/hard handoff, statistics collection, concentration of span lines. Routers convert TCP/IP/Ethernet to TCP/IP/TokenRing. DSUs convert V.35 to DS0 for SS7 links to remote MSC. XC-PC used to download code & data to XC.
48 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA CBSC Overview The CBSC (Centralized Base Site Controller) is a component of the SC9600 system responsible for controlling all the Base Sites that have been assigned to it, in addition to concentrating conversations from several BTSs over T1 or E1 span lines to an MSC.
A CBSC is responsible for downloading and initializing the devices in the BTS which must have code and/or data on them. The CBSC is responsible for performing Fault Management of the BTSs- meaning that if a device in a BTS goes OOS (Out of Service), then the CBSC will attempt to take corrective action. The OMC-R contains all the code and data required by the CBSC, but the OMC-R is not crucial to the CBSCs functionality. In fact, should the OMC-R not be present, the CBSC will continue to perform correctly in order to implement the CDMA call processing features. The XC (Transcoder) is a child of the MM, meaning that the MM performs some management of the XC, and performs some Fault Management on the XC in addition to device downloading. However, downloading and management by the MM are currently limited to the FEP cards- all other cards in the XC are managed by the OMP GPROC. Unfortunately, at the present time not all of the devices in the XC can be downloaded by the MM- so, a special PC called the XC-PC must be used to download the XC. The XC-PC talks to the XCs OMP GRPOC through the ber-optic token-ring LAN. Note that the service is interrupted to download the XC, since the MM is taken off of the LAN at download time. The Routers (or Bridges) serve to convert from TCP/IP over Ethernet on the MM side to TCP/IP over Token-Ring on the XC side. This is because neither the MM nor the XC currently support each others formats. The DSUs are necessary in order to convert the V.35 data paths from the MM to T1 spans to the XC when the MM and the MSC are NOT co-located.

NOTES:

Motorola Confidential Proprietary

49 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Logical Paths through CBSC

OMC-R MSC

WAN
terrestrial circuit 56 Kb PCM MM-OMC using TCP/IP

CBSC
DSU
A+ interface over E1

MM I/O Cage Tandem Processor

XC
XCDR XCDR XCDR Control

Router TCP/IP VirtualCircuits

TCH 16 Kb QCELP

SCAP link 56 Kb digital

BTS

BTS

...

BTS

MSC, OMC-R both at remote sites. TCP/IP WAN used for OMC-R<->MM connection, SS7 links nailed through XC over E1 span to MSC. MM instructs XC to set-up connections.

50 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Logical Paths through the CBSC This diagram presents the logical paths for control and trafc data through the CBSC.
Note that the case presented is for a remotely located CBSC. Both the MSC and the OMC-R are removed from the CBSC. This case has not occurred yet, but there is the possibility that future customers will choose this option. A WAN (Wide-Area-Network) is established between the MM and the OMC-R when they are not co-located. This WAN is composed of DSUs and dedicated T1 lines which transport TCP/IP data. The A+ data for communicating between the MSC and the MM is transported through nailed circuits in the XC, such that a T1 or E1 to the MSC from the Transcoder will carry both channel trafc (conversations in PCM format) and control data (A+ messages over a 56 kbps or 64 kbps channel). One of the functions of the Transcoder is to concentrate conversations from many T1 or E1 lines from several BTSs to a few T1 or E1 lines to the MSC. When the MSC is not colocated, this cuts down considerably on the operators cost. Note that XC stands for Transcoder (which is the whole frame), while XCDR stands for Transcoder Board, which is the device responsible for converting between PCM on the land side (to/from the MSC) to the CDMA Air Interface side (which uses QCELP STRAU data frames). Logical paths are established in the XC at the request of the MM. The XC manages its own resources in order to establish the appropriate paths as requested by the MM. In release 4, when handling a mobile-to-mobile call, the XC transcodes both conversations from QCELP to PCM, and then from PCM to QCELP again. However, in a future release, mobile-to-mobile calls under the same CBSC will by-pass the transocding step- thus providing better voice quality for M-M calls.

NOTES:

Motorola Confidential Proprietary

51 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA Tandem Platform

Air intake Processor Card Cage I/O Controller Card Cage

Memory Modules (2) CPU Modules (3) IOP ModSDCC(Single DC Converter)

System Disks or Tape Modules (up to 9)

SP Modules
IO Cards (will vary from OMC-R to MM)

Fan Modules(3) Air intake (front only)

DCC(DC Converter) Modules (6)

1829 mm

Bulk Power Supply Module (4)

Fan Modules(3) Air Exhaust

762 mm

Fault Tolerant Tandem Integrity UX (Unix). Doubly-redundant hardware. RISC-based technology (MM uses MIPS R4400 CPUs at 175 MHz, with 128 Mbytes of fast local memory, 16 Mbytes of global memory). Mirrored disk storage system (running Veritas software).
52 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA Tandem Platform Both the OMC-R and the MM are built on a computing platform provided by Tandem Computers, Inc.
The Tandem box utilizes redundant hardware such that a single failure in the box will not cause functionality to be interrupted. For example, should a FAN go bad, the other fans will speed up to compensate for the failure. The Tandem platform will post alarms when devices fail such that operator action may be performed. Only one CPU out of three may fail at any time (two CPUs must be sane for the system to operate correctly). All other systems are doubly redundant. The box runs a specialized version of UNIX called Non-Stop UX, which has been customized by both Tandem and Motorola in order to provide more robustness in the Operating System. The disk storage system is also doubly redundant and mirrored, such that any failure on a drive will not cause data to be lost. A software suite called Veritas implements this feature. The MM and OMC-R are different in that the OMC-R does not need V.35 interface hardware for the SS7 links, nor does it need as much processing power as the MM. On the other hand, the MM does not need as much disk space as the OMC-R, since the OMC-R is the central repository for the code and data in the SuperCell system. The platform runs on -48 Vdc power.

NOTES:

Motorola Confidential Proprietary

53 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA Transcoder Frame

Top Interconnect Panel Daughter Daughter Cards (29 max.) LANX, KSWX, CLKX Full Size Cards (29 max.) GPROC, GCLK, XCDR, KSW MSI Circuit Breaker Housing

Full

Size

1800 mm
Power Supplies (3)

Fan

Fan Modules

Daughter Cards (29 max.) Daughter Full Size Cards (29 max.) Full Size Power Supply Bds. (2)

Alarm Bds. (2)

Power Supplies (3) Fan Fan Modules

800 mm

Concentrates & converts data formats between MSC, MM, and BTSs. Optional Echo Cancelling. Gets involved in soft and softer handoffs. Can be expanded to multiple cages for more capacity if necessary.

54 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA Transcoder The CDMA Transcoder frame is presented in the diagram.
The CDMA XC design was carried over from the GSM project- much of the hardware and software is core between the two technologies. The XCs main functions are: To concentrate trafc from spans to many BTSs to few spans to the MSC. Thus cutting down on the cost to the customer for rented spans. To convert from PCM (pulse-code modulation) to QCELP (QualComm Excited Linear Prediction), which is the format that represents voice trafc in CDMA. Optional echo cancelling. Shares responsibility in hand-off arbitration, along with the MM. The XC has two main shelves, the upper and the lower. Each main shelf has a bay for half-size cards, and a bay for full-size cards. The XC initially may be congured with only one shelf, and can be congured to have up to 13 shelves (this is the LAN constraint- other constraints would limit this number further).

NOTES:

Motorola Confidential Proprietary

55 of 259

L28

BTC 0
U28 U27 U26

RMT KSWX A4 RMT KSWX A3 RMT KSWX A2 RMT KSWX A1 RMT KSWX A0 EXP KSWX A2 EXP KSWX A1 EXP KSWX A0 LANX A

56 of 259
L27

KSW A XCDR 0 XCDR 1

U25 U24 U23 U22 U21 U20 U19 U18 U17

L26 L25

GPROC 0 GPROC 1 GPROC 2 GPROC 3 GPROC 4 GPROC 5 GPROC 6 GPROC 7

L24

XCDR 2 XCDR 3 XCDR 4 XCDR 5 XCDR 6

PWID Center for Excellence

L23 L22 L21 L20 L19 L18 L17

LANX B

XCDR 7 XCDR 8 XCDR 9 XCDR 10 XCDR 11 XCDR 12 XCDR 13 XCDR 14 XCDR 15

MSI 0 MSI 1 MSI 2 MSI 3 MSI 4 MSI 5 MSI 6 MSI 7 MSI 8

L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6

U16 U15 U14 U13 U12 U11 U10 U9

Revision 0, 4/24/97

The CDMA Transcoder Cards

GPROC- generic processors. Function depends on software downloaded. Functions are: FEP, OMP, CPP, Shelf. GCLK- Global Clock. Provides timing for XC. MSIMultiple Serial Interface. Terminates two T1 or E1 span lines. XCDR- Performs transcoding of digital signal, optional echo cancelling. KSW- Kilo-Switch card. Provides switching of TDM channels. Half-size cards: KSWX- extends TDM bus to other shelves. LANX- extends token-ring ber optic network. CLKX- distributes clock signal.
EXP KSWX B0 XCDR 16 XCDR 17 XCDR 18
L5

Motorola Confidential Proprietary

MSI 9 MSI 10 MSI 11 GCLK A
L3

U8 U7 U6 U5 U4 U3

EXP KSWX B1 CLKX A0 EXP KSWX B2 CLKX A1 RMTKSWX B0 CLKX A2 RMTKSWX B1 CLKX B0 RMTKSWX B2 CLKX B1 RMTKSWX B3 GCLK B
U2 L1 L0

An Introduction to the SuperCell System

CLKX B2 RMTKSWX B4 KSW B BTC 1

U1

LOCAL KSWX A U0 LOCAL KSWX B

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA Transcoder Cards

The full-size cards are: GPROCs (generic processors). Based on 25 MHz MC68030 CPU, 16 Mbytes RAM, 1Mbyte EPROM, Dual redundant 16 Mbps Token Ring LAN, dual redundant TDM highways (32 channels @ 64Kbps). GCLK (clock reference card), used as a single clock reference for the entire XC (there is a redundant GCLK card in case the primary fails). MSI (Multiple Serial Interface). This card terminates two E1 or T1 span lines. The XCDR cards- perform transcoding and optional echo cancelling. The BTC (bus terminator card). KSW (Kiloport SWitch) cards. This is a TDM switching matrix which supports 4096 input ports and 1024 output ports (each port at 64 kbps or 56 kbps). Half size cards extend the clock circuits and KSW bus between shelves, and interface the XCs internal bus with the token-ring LAN. They are the LANX (extends token ring lan to multiple cages), the KSWX (extends TDM highway to multiple cages and multiple KSW cards), and the CLKX (extends clock reference to multiple cages). The GPROC cards may take on three different roles: Front-End Processor (FEP GPROC). This processor routes control trafc between the XC devices, BTSs, and the MM. It converts between LAPD and TCP/IP so the MM can talk to the BTSs. Operations & Management Processor (OMP GPROC). This processor is the master GPROC for the XC subsystem- it performs operations and maintenance (O&M), fault management, and device state management for all the devices in the XC. The OMP also has an RS-232 interface for management and debugging of the XC. Call Processing Processor (CPP GPROC). This device carries out orders dictated by the MM for channel allocations and call processing functionality.

NOTES:

Motorola Confidential Proprietary

57 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Transcoder Connectivity
To MSC E1 MSI
c7sl circuit PCM A+ To MM

GCLK

MSI

FEP
LANX

KSW

XCDR
QCELP trafc

XCDR
mxldl csldl

CPP

Token Ring LAN Bridge To MM

MSI

MSI

OMP

E1 BTS

E1 BTS
To OMC-R

Connections from MM to XCs CPP and OMP GPROCs are called mxldl. Connections from MM to BTS are called csldl. Voice paths to BTSs are called trafc, while voice paths to MSC are called circuit. A+ path through XC is called c7sl- C7 Signalling Link. The KSW card provides switching of all TDM trafc between the XCs cards- including nailed circuits such as csldl, mxldl, and c7sl.

58 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Transcoder Connectivity This diagram illustrates connections made through the XC in order to provide the XCs functionality.
This diagram is for a remotely located MSC, since the A+ links are being nailed through the XC. E1 (or T1) links are always terminated on MSI cards- each card can terminate two links. The MM establishes TCP/IP Virtual Circuits in order to communicate with the CPP GPROC, the OMP GPROC, the FEP GPROC, and to each of the BTSs. Inside the XC, the FEP converts the TCP/IP packets to LAPD packets, and forwards those packets to the appropriate device. In the XCs internal conguration database, the nailed connections made for MM to BTS control paths are called CSLDL for Cell Site LapD Link, while the connections made for MM to CPP and OMP GPROCs are called MXLDL for MM to XC LapD Link. The nailed connections made for MM to MSC (A+) paths are called C7SL for C7 Signalling Link. The KSW card provides switching of TDM slots over a dual (in/out) TDM highway to which the XCDR, MSI, FEP, CPP, and OMP GPROCs have access. Thus any port on the IN path may be connected to any port on the OUT path by the KSW. The OMP GPROC also provides an RS-232 interface which is used to input XC MMI commands to perform Recent Change commands in order to change the XCs conguration, or to perform debugging and/or status commands on the XC. This interface is also available at the OMC-R via a dial-up modem (when the OMC-R is not co-located), or through a dedicated RS-232 line to the OMC-R.

NOTES:

Motorola Confidential Proprietary

59 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA SC9600 BTS

Linear Power Amplier Frame RF Modem Frame Site Interface Frame

A A - 2400 mm B - 600 mm C - 1350 mm

min. 150 mm Air Flow LPA SIF Frame Frame 400 Kg RFM Frame

360 Kg 320 Kg min. 600 mm Front Access

SC9600 BTS is composed of three Frames:

- RF Modem Frame. Converts between a terrestial interface (CDMA Strau Data over LAPD link) to CDMA Air Interface (layer 1). - Site Interface Frame. Interfaces the sites antennas with the LPA frame(s), and the RFMF(s). - Linear Power Amplier Frame. Contains up to three linear power ampliers, each capable of amplifying multiple CDMA carriers. - Redundancy is provided for critical elements.

All cabling is through the top of the frames.

60 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA BTS The CDMA BTS is composed of three frames:

The Site Interface Frame (SIF) The RF Modem Frame (RFMF or sometimes just MF) The Linear Power Amplier Frame (LPA)

The BTS provides the interface between the CDMA infrastructure equipment and the air interface.
A SC9600 CDMA system must have at least one of each of the three shelves mentioned above. Other congurations (such as SuperCell 4850) may not necessarily be under that constraint. An SC9600 BTS may have multiple RFMF and LPA frames, but only one SIF is needed at a BTS. Antenna congurations supported are Omni-Receive, Omni-Transmit (Omni-Omni), and 3 sector transmit/receive. The frames work with +27 Vdc power. Maintenance may be performed locally at the BTS through the use of an LMF (Local Maintenance Facility), which is a customized portable PC. Direct dial-up modems are usually connected to the site in order to enable the OMC-R to interface with the BTS when specialized site Operations & Maintenance must be performed. This step is usually only necessary when the site has lost its T1 or E1 link to the CBSC. Redundancy is provided for critical devices in the BTS, such that failure of a single device will not cause a service-affecting outage at the site. However, some device failures (such as a Multiple Channel Card outage) will result in lower capacity at the site. Physical interfaces for the BTS are presented at the top of the frames, thus allowing for easy access to the cabling (this is a general SuperCell design philosophy).

NOTES:

Motorola Confidential Proprietary

61 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA SC9600 BTS Devices

RF interface Digital interface Other interface

Tx/Rx Antenna Systems

GPS and Loran Antennas RF MODEM FRAME Preselectors modem AMRs LMF (opt) RS232 BBXs GLIs CSMs & LFR MCCs RF Rx Channels
AMR Bus for CDMA

To/From CBSC Span Lines

SITE INTERFACE FRAME Dir.Couplers Multicouplers Frame Power RFDS Filters RGLI

BTS Control

XCVR RF Outputs

SCAP TCP/IP

Ethernet RF Tx Channels

LINEAR POWER AMPLIFIER FRAME LPA Modules Frame Power LCIs

LMF

RFMF contains:
GLI cards: terminate T1|E1, provide site O&M. GPS & Loran cards (CSM & LFR): system clock. BBX cards handle the RF/Baseband conversion. BDC cards handle Pilot Channel and Signal Spreading on the Tx path, antenna diversity on the Rx path. - Preselectors, AMRs: RF and alarm functions.

SIF contains lters for the Rx path, multicouplers to allow multiple RFMFs at one site, and directional couplers to patch in an RFDS test station.
62 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

The CDMA SC9600 BTS Devices The RF Modem Frame Contains the GLI card (Group-Line Interface), which terminates the T1 or E1 spans from the CBSC, and also performs site O&M (Operations & Maintenance) for the BTS. It also houses equipment for GPS (Global Positioning System) signal acquisition, in addition to a Loran system in case GPS fails. In addition, the frame houses the MCC (Multiple Channel Cards), which perform the complicated Layer 1 and Layer 2 functions of the IS-95 standard. These functions include forward power management, signaling on the trafc channel, and trafc channel management. The RFMF houses the BDC card. The BDC card combines the forward baseband signals from each of the MCC cards and performs the direct-sequence spreading of the signal. In addition, the RFMF also houses the BBX card. The BBX card receives signal from the BDC card, and is responsible for the CDMA RF functions (up-conversion, downconversion, etc.).

The Site Interface Frame Provides the RF interface to the propagation medium (air). Consists of RF lters, directional couplers, an RFDS (Radio Frequency Diagnostic Subsystem), multicouplers (to support more than one RFMF), and antennas.

The Linear Power Amplier Frame Provides power amplication for transmit signals from the BTS. Houses up to three Linear Power Ampliers (LPAs), each capable of amplifying multiple CDMA carriers from multiple RF Modem Frames.

NOTES:

Motorola Confidential Proprietary

63 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Software Overview

OMC-R

OMC-R OMC-R

Runs Unix, Informix, SC9600. Contains the MIB for SuperCell. Provides a CLI environment. Unix K-shell programming. Provides a debugger, tracer, and system kernel analyzer. Also provides X-Windows. Transcoder

MM Same as OMC-R, but no MIB or X-Windows. DB in the form of CDFs.

LMF

Runs VRTX OS. Has its own DB, which is downloaded from a PC.

Runs Solaris UNIX. OS is pre-installed. LMF application is loaded by operator.

Provides a CLI-ish interface through RS232 cable. Provides a monitor and message lter utility

CDMA uses UNIX on MM, OMC-R, AP, and LMF. Most interfacing will occur through CLI environment, although emergencies will require UNIX knowledge, and knowledge of debuggers available in each platform.
64 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Software Overview Properly congured and running software is crucial in acheiving a functional CDMA system.
CDMA utilizes UNIX on many of its platforms (MM, OMC-R, LMF, AP/UNO). Unfortunately, a careless operator with root access can cause serious damage to the software on any of the platforms, rendering the platform unusable. Care must be taken to only allow knowledgeable and responsible operators to have root privileges. Even non-root users have the potential of affecting the performance of a platform- by starting up too many processes at once, for example. Note that the database is stored on the OMC-R as an Informix MIB (Managed Information Base), while on the MM the database is in the form of ASCII les called CDFs, and on the XC the database is a separate entity. These three databases must be in agreement on those items which are shared among them. The LMF (Local Maintenance Facility) is a portable PC which runs Suns Solaris for Portables Operating System. This PC is pre-loaded with the Sun OS from the factory, but must be loaded with the proper LMF Application Software (distributed with the SuperCell software releases) by the operator (usually an RF Cellular Field Engineer). In addition, this PC must have the proper CDF (conguration data les) for the cell-sites which are to be optimized with the LMF.

NOTES:

Motorola Confidential Proprietary

65 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA System Database Creation

OMC-R Transcoder Frame

Establish Requirements

OMC-R

Run CLI scripts produced in Step 3 on the OMC-R, run MMI scripts produced in Step 3 on Transcoder. Run CSSS and Congurator

Run CDMA Conguration Manager

Export the MIB to a Tape, Download the XC database object to a diskette.

Customers requirements (# of subscribers, area to be covered, etc) must be determined. Run the CDMA Static System Simulator (CSSS) to determine the cell site placement and conguration to cover the required area properly. Run the CDMA Congurator to determine the number of resources needed for this CDMA system (#MSI cards, #XCDR cards, etc.). Run the CDMA Conguration Manager tool to generate CLI and MMI scripts. Scripts used to generate a MIB on the OMC-R and a XC database object on the XC.
66 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA System Database Creation In order to get the CDMA equipment to function properly, the equipment databases must be populated correctly. These databases specify how the CDMA system has been equipped. The following steps are given to provide an overview of the system database generation (or sysgen, for short) process:
First the Motorola personnel must dialog with the Customer in order to determine the requirements for the CDMA system. Among those requirements are: coverage area, estimated erlangs (subscriber loading), and the total number of subscribers to be served. Then Motorola personnel (usually Systems Engineers) must input that data into a software package called the CDMA Static System Simulator (or CSSS). The CSSS is a collection of programs which will help determine an adequate placement for BTSs in order to cover the area specied. NOTE: The CSSS algorithms are being incorporated into Motorolas NetPlan software. The CSSS will soon be replaced by NetPlan! Contact NetPlan project management for a release date. Another software package called the CDMA Congurator is run to determine the amount of hardware which will be necessary to comply with the customer requirements. Any additional parameters that are needed are lled in by the Systems Engineer, usually with the help of the CDMA Motorola Recommended Parameters document. A set of ASCII les are then created which are the minimal amount of information necessary to specify the CDMA network elements. These les are fed to a program called the CDMA Conguration Manager. This program produces CLI script les and MMI script les. The CLI script les are run on an OMC-R (or equivalent- such as a development machine which sort of emulates the OMC-R) in order to produce an Informix MIB. The MIB is exported to a cartridge tape, which is then ready to ship to the site. The MMI script les can be run on-site on the XC, or in a lab on the XC, in order to produce an XC database object. If a lab was used, a diskette containing the database object is shipped to the site.

NOTES:

Motorola Confidential Proprietary

67 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Software Installation & Initialization

OMC-R

#1
OMC-R

#2 #5

#4
Transcoder Frame

#3
BTS

#2
OMC-R

MM

#4

1st: Obtain installation tapes. Install software on OMC-R, MM, AP, and XC platforms. 2nd: Obtain System Database Tape & Floppies, install MIB on OMC-R, XC Database on XC. 3rd: Generate CDF les on OMC-R, propagate them to the MM. 4rd: Perform a software INIT command on MM and OMC-R. 5th: MM will automatically download those BTSs which need new code & data downloads. 6th: BTS will start providing service as soon as possible.
68 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Software Installation & Initialization The previous diagram illustrates the abbreviated steps necessary to load a new software release onto the Supercell system.
This is not intended to replace the Software Installation Procedures (which should be present with the new load to be installed), its just presented as an overview of the typical installation process. The Release Notes that accompany a release, along with the Installation Procedures will specify which network elements, and which software packages will need to be installed as part of the release. There are major releases, and point-xes. Major releases may cause all the software in the system to be upgraded, along with some hardware components as well. Minor releases usually require only a subset of the software to be upgraded. The software release media is usually shipped to the site. At times the software will be FTPed to the Area Ofce, where tapes are made and then physically transported to the site. The same can be said about the site-specic database (both the MIB and the XC database image). Once the software is loaded on the OMC-R, it can be installed from the OMC-R directly to the sub-tending MMs through the ethernet interface. Another option is to install the software directly onto the MMs. Yet another option (which is usually done on commercial systems) is to perform a Brain Transplant on the MMs, which involves swapping out half of the MMs hard drives for new drives with the new release preinstalled on them. A process called CDF Gen is then performed on the OMC-R in order to create new CDF les for the MM. The CDF les are transferred to the MM via the ethernet LAN. The system software is then re-initialized (by performing a CLI INIT command). This causes all the devices under an MM to be re-loaded if the load identier in the CDF le for the device has changed. The BTSs will start providing service as soon as possible (as soon as the minimal amount of devices required have been downloaded and initialized by the MM).

NOTES:

Motorola Confidential Proprietary

69 of 259

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

Customer Interfaces to CDMA

UNO
External Network Ethernet Bridges and Routing Equipment X - Terminals Remote MMI Terminals OMC-R OMC-R RS-232

Console Terminal

UNO

Ethernet

Ethernet Redundant Ethernets

X - Terminals Local MMI Terminals Transcoder Frame Transcoder Frame

XC-PC RS-232 OMC-R Console Terminal MM MM RS-232 OMC-R

Main customer interface through UNO platform. UNO provides GSD (Geographical System Display), an Alarm Manager, and a Status Display. The UNO can be remote, or local to the OMC-R. Other devices have more rustic interfaces (CLI, MMI)

70 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

An Introduction to the SuperCell System

CDMA Customer Interfaces Several interfaces are in place so that the customer may interface with the CDMA system.
MMI stands for Man-Machine-Interface. Note that MSC interfaces are not presented, since the MSC is not considered part of SC9600. The MSC would have its normal User Interfaces- in the case of an EMX switch, these would be the Switch Terminals and (optionally) the CAT terminals which are connected to a SwitchMate box. The main interface is provided through the UNO boxes, which are server platforms for one or more X-Terminals. At either the UNO or the X-Terminals the customer will be able to bring up graphical user interfaces (GUIs) which will detail the state of the Radio Network Devices. The customer may also view statistics reports and perform system maintenance from any of the X-Terminals or AP boxes. The UNO provides software packages which allow the operator to manage the SC9600 network, such as the Status Display Tool, the Geographical Systems Display, and the Alarm Manager. Other interfaces are less user-friendly, such as the console terminals of the OMC-R, and the MMs, as well as the XC-PC interface to the Transcoder. SC9600 commands may be performed at the console terminals, or through UNIX telnet sessions connected to the MM or the OMC-R platforms. The software which parses and starts execution of SC9600 commands is called the CLI- for Command-Line Interface. The XC has a CLI-like environment which may be accessed over an RS-232 serial line which is connected to the OMP GPROC. This is a non-user-friendly environment, and is usually used only by XC specialists. An UNO cluster may be remotely located, by using bridges and routers and to carry high speed serial lines over dedicated T1 or E1 spans. However, this option has not yet been used by any CDMA customer to date.

NOTES:

Motorola Confidential Proprietary

71 of 259

Conclusions:
SuperCell CDMA product is a distributed environment for providing cellular telecomunications. SuperCell system consists of CBSC, BTS, OMC-R, and UNO platforms. CBSC handles switching and control functions in the BSS network, along with transcoding of QCELP into PCM (and vice versa). CBSC is composed of MM and XC, along with other equipment for O&M. BTS handles air interface for CDMA. MSC is responsible for PSTN interface to SuperCell, billing and subscriber database functions. Several CBSCs may be connected to a single MSC, while several BTSs may be connected to a CBSC. UNIX is widely used in the SuperCell network. MM, OMC-R are Tandem platforms, running Unix. XC provides switching matrix, transcoding functions. Proper software installation and conguration is crucial to SuperCell.

72 of 259

Motorola Confidential Propretary

PWID Training: CDMA

The Tandem MM Platform & UNIX OS

Motorola Confidential Proprietary

73 of 259

Objectives:
Present the MM platform in detail- its specialized hardware as well as the SuperCell software running on the platform, in order to equip the student with the necessary skills to operate the MM. Present the basics on the UNIX operating system, in order to give the student a working understanding of UNIX.

74 of 259

Motorola Confidential Proprietary

Table of Contents:
The MM Architecture and Interfaces ............................................................................ 77 MM Hardware Architecture........................................................................................... 79 MM Physical Conguration........................................................................................... 81 MM Functions ................................................................................................................ 83 The UNIX OS- Theory & Denitions ............................................................................ 85 Supercell File System Structure..................................................................................... 87 MM File System Theory & Operation ........................................................................... 89 Unix: Basic Communications ........................................................................................ 91 The Unix Korn Shell....................................................................................................... 93 Supercell MM Software Overview ................................................................................. 95 Supercell MM Software Architecture ............................................................................ 97 MM Platform Initialization ............................................................................................ 99 Supercell Initialization: SCSIIM ................................................................................. 101 The Supercell Process Set ............................................................................................ 103 Supercell Process Set- Continued ................................................................................ 105 MM Software Installation ............................................................................................ 107 MM Operations- Tools & Tricks .................................................................................. 109

Motorola Confidential Proprietary

75 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Architecture and Interfaces

MM SS7 UNIX SVR4 Operating System Disk Cntrls Supercell Application SW UNIX Utilities

SS7 Sync. Cntrls

TCP/IP Enet Cntrls Enet Cntrls

To MSC (through DSUs)

SCAP over TCP/IP (Ethernet & Token Ring)

MM is a fault-tolerant UNIX box built by Tandem Computers. At least two instances of every critical device. The Operating System is UNIX SVR4. Supercell application software interfaces with UNIX to perform Supercell functions. MM interfaces with MSC, BTSs, OMC-R, XC, and its local console terminal. MSC interface is through SS7 stack running on MMs SYNC cards. BTS/XC, OMC-R interfaces are through TCP/IP stacks running over MMs ethernet cards. Local console terminal is through an RS-232 serial line to the MMs I/O processor.
76 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

The MM Architecture and Interfaces The Mobility Manager (MM) is a computer platform which Motorola purchases from Tandem Computers, Inc. The following points concern this platform:
The platform is fully hardware fault tolerant, meaning that any single device failure will not cause a system-wide (or catastrophic) failure. All devices except the CPUs are doubly redundant, while the CPUs are triple-modularredundant (which means that 2 out of 3 CPUs must be in agreement). The ethernet cards and Synch cards are active/standby, while the disk (SCSI) controllers are active/active. An active/standby redundancy scheme means that one card will always perform all the work, while the other will only come into service when the rst card fails. An active/active scheme requires both devices to perform the same work at the same time- An external entity will watch both cards, in order to detect failures. The defective card will be removed, and all work will continue to be performed on the remaining good card. A software/hardware system called midas is responsible for the watching. The operating system is UNIX SVR4 (POSIX compliant). The OS is the core software component in the MM- it interfaces with the system hardware (such as ethernet controllers, sync cards, and SCSI disk controllers), and provides an environment in which the Motorola software can interface with the rest of the real world. The software for receiving and sending information over SS7 and ethernet interfaces resides in the hardware (rom/ram) for the interface (Async cards, ethernet cards), in the Operating System (OS) itself, and in the Motorola Software as well. The Motorola Software makes software calls to the OS in order to send and receive information from the communications stack (such as a TCP/IP stack, or an SS7 stack). A standard VT100 terminal at 19200 baud (8 bits, no parity) may be connected to the MM in order to function as a console terminal. From this terminal, an operator will be able to access the MM when all other access methods (TCP/IP) are not available. From this terminal, the MM may also be reset should all other recovery attempts fail.

NOTES:

Motorola Confidential Proprietary

77 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Hardware Architecture
CPU A CPU B CPU C

MEM A

MEM B

IOP 0

Service Processors MMI Port

IOP 1

VME bus MIRRORED DISKS

Disk Controller

VME bus

Disk Controller SYNC (2) Controllers 4 LAN (4) Controllers Ethernet LAN 2 pair MSC Control Channels

3x MIPS R4400 CPUs. 175 Mhz internal, 75 Mhz external clock speeds. 128 Mb memory. 16 Mb external (shared) memory. 2x I/O highways (I/O Processors control trafc). 2x SCSI busses, and disk drives. 2x SYNC controllers (for SS7 links). 2x ethernet controllers (for FEP/OMC links).
78 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Hardware Architecture The MM platform was especially built for Motorola by Tandem Computers for handling the demanding real-time environment of cellular call processing, while providing the reliability necessary for the cellular environment. The following are points concerning the MM platform:
There are three CPUs, two of which must be in agreement at all times. Each CPU has 128 Mb of on-board memory (fast NVRAM). The CPUs are MIPS R4400 series, running at 150 Mhz internal clock speed, 75 Mhz external bus speed. Each CPU resides on its own card. A CPU may be pulled out, but upon re-inserting the CPU, the Tandem box will automatically start a process called re-integration. This will bring the CPU up to speed with the other two CPUs, and will be done very slowly so as to not affect the other two CPUs. Watch the le /var/adm/messages for indications as to when the CPU reintegration is nished. There are two global memory cards, each with 16 Mb of memory. This global memory may be accessed by all three CPUs, while the CPU local memory can be accessed only by the local CPU. Information which must be seen by all three CPUs is placed in this memory. Access to global memory is slower than access to local memory (as is to be expected). I/O processors provide a bus for communication to the I/O devices in the computer. Thus bus is called VME bus, and it allows access to the Ethernet, Sync, and SCSI bus controllers by the CPUs. The disk controllers each control a SCSI chain of devices, which include the hard disk drives, cartridge tape drive, and an optional DAT tape drive. A software suite called Veritas provides low-level formatting and access to the disk volumes, in order to handle active/active redundancy. The Sync controllers are also called V.35 controllers (V.35 is the name of the communications standard provided by the controllers). The Sync controllers provide four ports each, labelled 0 through 3. These ports are used for connections to the MSC (through DSUs). The ethernet controllers provide one ethernet port each. There are four ethernet cards in the MM- two for active/standby connections to the XC (FEP GPROCs), and two for active/standby connections to the OMC-R.

NOTES:

Motorola Confidential Proprietary

79 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Physical Conguration
151 152 161 162 163 164 165 166 167 168

} }

Air intake

SPC

SPC Ether- SCSI SCSI Ether- SS7 or net 0 1 0 net SPC 0 1 Bypass

Ether- SS7 Ethernet 1 net 2 3

DC PWR (75
Fan Modules(3) Air intake (front only)

I/O Controller Card Shelf

I/O Processor 0

Bulk Power Supply Module

1 gig Disk

Processor Card Shelf

c0d3 c0d0 201 211 c0d1 c0d4 (tape) 202 212 c0d2 203 c1d5 213 c1d6 221 c1d0 222 c1d1 223

I/O Processor 1 1 gig Disk 1 gig Disk

Fan Modules(3) Air Exhaust (bottom, front and rear)

1 gig Disk

Storage Device Bay

Each member of 2x set of cards on different power supply. Most cards hot-swappable by using the cfdown and cfonline commands. Optional DAT tape drive may be used. LEDs on the cards indicate card status (red is BAD!). cfstatus command may be used to show card status.
80 of 259 Motorola Confidential Proprietary

Memory A

Memory B

CPU-A

CPU-C

CPU-B

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Physical Conguration The diagram illustrates the physical position of the cards on the MM. These positions are dictated by the MM Hardware Installation document. The following points concern the MMs hardware:
All removable devices may be queried for status by using the following command (partial output is shown as an example):
# cfstatus Component ______________ enet1 scsi1 State _______________________ online online Cabinet __________ system system IOP/Controller ____________________ iop0 iop0 DCC CRU _______ DCC3 DCC3

All removable devices may be placed out of service with the cfdown command. Beware of using this command! A careless operator can bring the MM down through careless use of this command. See the cfdown manual page for more information. All removable devices may be placed into service through the cfonline command. The command will need the name of the controller for the device to be specied with a -c argument. Example:
# cfonline -c scsi0 disk0

Notice that the slot numbers on the top of the I/O controller card shelf correspond to the numbers on the back of the frame. The cnstall command must be used if the device is shown as Absent through a cfstatus command. The cnstall is used as follows (in the example, we are installing ethernet card 0, which is in slot 161). See the man page for cnstall for more details.
# cfinstall -i iop0 -s ioc0 -c enet0

Notice that the disk drive identiers are given in the diagram for the storage device bay. These devices are then accessed at the low level by addressing the les in the directory / dev/dsk/. For example, the 1 gig drive in the upper left hand corner would be addressed as /dev/dsk/sc0d0. All cards have LED indicators on them- red is not a good color! (this means the card is ofine). An important point to make about the SS7 cards: port 0 of the SS7 card is actually the bottom-most port on the card! (Not the top, as one would suppose).

NOTES:

Motorola Confidential Proprietary

81 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Functions
MSC CBSC Ethernet DSU Transcoder A+ DSU A+ Mobility Manager

RS-

OMC-R

Token

Bridg

TCP/IP Ethernet

LAPD and TCHs BTS BTS BTS BTS Cluster

Call Control and Channel Allocation. Control point for handoff operations. Builds partial call detail records. Performs Operations & Maintenance actions (under the instruction of OMC-R). Provides initialization, fault management and event processing for itself and devices it controls. Runs Tests, Audits, and Diagnostics (TAD) programs periodically. Provides control of software releases and data versions on its sub-tending devices (except most XC boards). Collects statistics for later transmission to OMC. Provides Command Line Interface (CLI) for interaction with operator.
82 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Functions The MM (Mobility Manager) is the brains of the SuperCell Real-Time operations. Functions which require access to database information, or complex functions which must be performed quickly are delegated to the MM. The following functions are delegated to the MM:
Basic call control and channel allocation functions. This includes allocating trafc channel elements in the BTS which is servicing an MS, as well as assigning Walsh codes for the conversation. Control point for handoff operations. For handoffs between two channels that are both under control of the same MM, the MM can control the entire handoff. For inter-CBSC handoffs, the source MM will provide overall control, but the process will also involve the MSC and the MM that controls the destination channel. Collect the cellular data needed for call detail records. This data is forwarded to the MSC, where it will be combined with the land-network information. Producing the completed call records is then a function of the MSC. Acts as an agent for operations and maintenance actions. It is important to note that the MM does not need the OMC-R in order to perform call processing tasks. However, the MM acts as a slave to the OMC-R when provisioning or changes are done to the cellular network. Provides a system conguration database that is consistent with the data stored at the OMC-R. The MMs version can support the real-time demands of call processing. The MMs version of the database is stored in les called cdfs. Provides high level fault management and event processing for itself and subtending devices. This is done through a software sub-system called scdevom. Provides system level diagnostics and test control in cooperation with the OMC-R. Provides control for distribution of software and data base downloads. Controls initialization of MM and all subtending subsystems. Collects performance measurement information for later processing and display at the OMC-R and UNO platforms. Provides local user interface through a Command Line Interface (CLI).

NOTES:

Motorola Confidential Proprietary

83 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

The UNIX OS- Theory & Denitions

MM SS7 UNIX SVR4 Operating System Disk Cntrls Supercell Application SW UNIX Utilities

SS7 Sync. Cntrls

TCP/IP Enet Cntrls Enet Cntrls

To MSC (through DSUs)

SCAP over TCP/IP (Ethernet & Token Ring)

Operating System: set of computer instructions which provide software interfaces to hardware. UNIX: powerful multi-tasking OS. UNIX allocates slices of time to each stream of commands (process). SVR4 allows several scheduling classes:
- System. - Real-Time. - Time Scheduling.

84 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

The UNIX OS- Theory & Denitions It is important to understand some of the theory behind the UNIX OS in order to better understand the operation of the MM. The following statements are provided to this purpose:
An operating system (OS) is a set of software instructions which run on a computers CPU in order to provide interfaces to the computers hardware. The interfaces are used by application programs. The OS will generally provide an environment in which a users program can access data residing in the computers devices, as well as data which is arriving on a telecommunications link. The UNIX OS was invented by AT&T in 1969- it is a powerful OS, and very popular for such applications as telephony, scientic studies, modeling, simulation, and many others. The combination of instructions for a user program, along with memory in which to perform operations is called a Unix Process. The function of assigning time to a process in an ordered manner is called scheduling. The Unix OS provides a process called the scheduler which has the capacity to remove a process from the CPU and put another process in its place. This is called preempting. A process of higher priority may pre-empt another process of lower priority. Unix SVR4 provides different scheduling classes and priorities as follows: System Class: Processes in this class are guaranteed to run any time they need to. This is the highest priority class, any process in this class may pre-empt any other process at any time. The Unix system scheduler process is an example of this type of process. Real-Time Class: Processes in this class run until they give up the CPU of their own accord, or until an optional time quantum is exceeded (the time quantum is assigned by the process itself at the beginning of its execution). This class is usually only used by time-critical applications. Inside this class, a process may be of priority from 0 to 59, 59 being the highest priority. Time Scheduling Class: Processes are run in a non-deterministic manner (i.e. the process does not know when its going to be pre-empted). The time quantum is assigned by the unix scheduler based on a scheduling algorithm for this class. The algorithm takes into account several factors, including recent CPU consumption, and process priority (which may be from -20 to +20).

NOTES:

Motorola Confidential Proprietary

85 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Unix & Supercell File System Structure

/screl

SC-1.2.1.0.0 active release

(additional releases) install

1.2.1.0.0-Release.lst 1.2.1.0.0-Release.rds bin 1.2.1.0.0-README (slm scripts) loadable data bin bts (MM/OMC (MM/OMC data les) executables) [soft links] (conguration data) (cdf Files)

(slm scripts) loadable

fep

mm

omc

xc

(platform code and data les)

MM utilizes Unixs hierarchical le system. MM has following le systems: / (root), /var, /home, / usr, and /screl. Code & data les for Supercell stored in /screl. Software Load Management is used in Supercell. MM may have several releases of software in /screl. The README le for a release will have information on software release (including size data).

86 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell File System Structure The MM utilizes the Unix hierarchical le system structure. Hierarchical means that the structure is similar to that of the management in most companies, with one entity as the top or head, several entities report to the head, and so on. In Unix, a directory is a place-holder for other directories and/or les. The following points refer to the le systems used by the MM:
The MM has several le systems (which are independent of each other), each of these le systems has its own space assigned to it. The following are le systems on the MM: / (root). This is the top directory, under which all other le systems are mounted. Mounting a le system is the process of making that le system available for use as a sub-directory of the root le system. (More on this later). /usr. This lesystem contains several les and sub-directories which contain software libraries and binary les for the proper operation of the MM platform. Programs such as cat, and crash reside in this le system. /var. This lesystem contains les and directories which contain system message les, and other les which specify the behavior of certain Unix programs running on the MM. The /var/adm/messages le is a very important log le to which many processes will output messages. /screl. All the Supercell software for the MM and its sub-tending devices resides in this le system, as well as log les and data les for Supercell. The le system is organized as seen in the previous slide. A Supercell software sub-system called SLM manages the information in this le system. /home. All the user accounts reside in this le system. Default users are scadm, lmf, and a7adm- these are created during a software installation of the MM. An MM may have several Supercell releases on it at the same time. The actual number will vary, depending on the release size, and the capacity of the /screl lesystem. At press time, the MM could hold a maximum of six full releases of Supercell software at once. The README le for a release will have information such as release dependencies (version of A7 software required, whether or not a full XC reset is required, etc.), and release size information.

NOTES:

Motorola Confidential Proprietary

87 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM File System Theory & Operation

Disk 0: sub-disk sc0d0-s1 sub-disk sc0d0-s2

Plex: test-0

Disk 1: sub-disk sd0d1-s1 sub-disk sd0d1-s2

}
Plex: test-1

Volume: test

Veritas System

File systems must be mounted for use. Veritas le system manages mirrored disks so all information resides on two disks. Basic unit in Veritas is sub-disk, which resides on a physical disk. One or more sub-disks make up a plex. One or more plexes make up a volume. volprint command prints status of veritas. volplex command re-integrates a bad plex.

88 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM File System Theory & Operation

All le systems other than root are attached to the root le system through a process called mounting. This process allows the le system to be accessed as if it were a directory under root. The command mount is used as follows to do this:
mount -F <type> [-o <mount options>] <device to mount> <mount_point>

The le system type will be vxfs for most le systems on the MM. Mount options (the -o option) are usually not used. The device to mount will be the full pathname to the volume to be mounted, this will usually be /dev/vol/<lesystem name>. The mount point is the full path to a directory under which the le system will be accessed. It is important to note that if the directory contains any information in it before the mount, the information will be hidden after the mount command. The mount command (with no options) will print information on the le systems mounted, as in the following example:
/ on /dev/vol/root read/write/setuid on Mon Apr 29 13:37:27 1996 /usr on /dev/vol/usr read/write/log/setuid on Mon Apr 29 13:37:43 1996 /var on /dev/vol/var read/write/log/setuid on Mon Apr 29 13:37:45 1996 /screl on /dev/vol/screl read/write/log/setuid on Mon Apr 29 13:40:16 1996 /home on /dev/vol/home read/write/log/setuid on Mon Apr 29 13:40:19 1996

The Veritas system uses the concept of a sub-disk as the lowest unit of le storage. A sub-disk will be directly associated to a particular area on a physical disk. The next unit is the plex, which is composed of one or more sub-disks. A plex is usually composed of sub-disks which are all on the same physical disk. The top-most unit is the volume, which is composed of one or more plexes. The veritas command volprint will print information such as the following:
TYPE sd sd plex plex vol NAME sc0d1s3-m3 sc1d0s3-m3 screl-0 screl-1 screl ASSOC screl-0 screl-1 screl screl fsgen KSTATE ENABLED ENABLED ENABLED LENGTH COMMENT 1375176 1375176 1375176 1375176 1375176

The veritas command volplex can be used to re-integrated a FAILED volume, although usually this command is performed automatically by the MM when a failed volume is detected. The following is an example volplex command (see the man page for volplex for more details):
volplex -U gen -o iosize=16k -o slow=200 -- att screl screl-1

NOTES:

Motorola Confidential Proprietary

89 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell: Inter-Process Communications

Other Application Shared Memory Segments

Application

Shared Mem.Msg Allocator Send IPC Message Queues for Other Process IPC Message API Queue Shared Memory Segment API Shared Memory Segment Named Pipe (FIFO)

ScapComm NecaComm/ API AplusComm IPC Msg. Handler Poll(2) Interface TCP/IP SS7 / J7 Ethernet Driver Protocol Protocol Stack Stack

T i m e r

Application Operating System Services

IPC Msg. Tickle

SS7 / J7 TCP/IP Messages Messages

SC processes receive communications through:

Shared Memory. Messages. Pipes. Signals.

Shared Memory segments are set up by a process called scsiim. Use the ipcs command to check IPC status.

90 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Unix: Basic Communications Unix processes often need to be told of events that have occurred in the system, or they need to talk to other processes in the system. The OS provides several ways for a process to receive indications from the outside world- following are some points concerning Inter-Process Communications (IPC):
A process may receive or send a signal, which causes a pre-dened routine to be executed upon reception of that signal. All possible signals are dened in the le /usr/ include/sys/signal.h. The key sequence cntrl-C produces a signal 2 (SIGINT), while other key combinations can produce SIGTERM (signal 15). These signals generally have the effect of causing a process to stop execution and exit. Care must be taken when using the kill command (this command causes signals to be delivered to processes). A process may receive or send a message from/to another process. The receiving process may pick the message up from a queue (which is provided by the OS), and perform some operation based on the data received. A process may receive or send data through a pipe, which is a special type of le to which other processes may write data. Reception of data on that pipe is usually detected by performing a poll() system call to the OS. The poll() system call will wake up only if data is received. Thus, the process will go to sleep until data is received over the pipe. A process may receive or send data through shared memory. Shared memory is used extensively in Supercell to hold data which must be accessed by more than one process at a time. Shared memory is created by a process called SCSIIM (more on this process later). However, in order for a process to be notied that a change has occurred in shared memory, another method of IPC is used (such as a pipe, signal, or message). The Supercell processes will sit in a poll() system call until something happens. The poll() system call is listening to several sources, among which may be pipes for Event Messages (special data which is placed in shared memory queues), pipes for A+ messages arriving over SS7 links, and pipes for SCAP messages arriving over TCP/IP links to the XC FEPs. The ipcs command may be used to check the status of the shared memory segments.

NOTES:

Motorola Confidential Proprietary

91 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

The Unix Korn Shell

Wow! Ksh is great!

OMC-R

A shell is an environment presented to user upon login into platform. Korn Shell (or Ksh) is one of the most popular shells, and is used by the Supercell product. Knowledge of Ksh is important! Example Constructs: for and if-then-else. Ksh also provides le name expansion, testing, substitution, etc. From inside a Ksh session, a CLI session is started. The CLI session is really a Ksh session with more commands available. Good reference material exists for Ksh- highly recommended!

92 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

The Unix Korn Shell In order to interact properly with unix-based computers, an operator needs to know a unix shell. There are several shells available (such as C Shell, B Shell, and Korn Shell), but the MM uses only Korn Shell (or Ksh). The following points are given concerning the Ksh:
When a user logs into the MM, a Ksh session is started. This session allows the user to interact with the computer, offering the ability to start programs, status programs, and even build complex programming language constructs to get jobs done. An example construct is the for loop. For example, if a user wants to create several directories called cdfdir1, cdfdir2, cdfdir3, and cdfdir4 the user can write the following at the ksh prompt:
# # > > for name in 1 2 3 4 do mkdir cdfdir${name} done

Another example construct is the if-then-else test clause. This can be used to perform some action based on a condition which must evaluate to true. The following is an example where if argument #2 to a function is not writable, the le is made writable, / tmp/newFile is written over it, and then the le is made not writable. Otherwise, the le / tmp/newFile is simply written over it.
if [ ! -w $2 ] then chmod +w $2 cp /tmp/newFile $2 chmod -w $2 else cp /tmp/newFile $2 fi

Once the operator has logged in, a CLI session is started simply by starting a program called CLI from inside the ksh session. A CLI session is really nothing more than a ksh session which has been customized so that the prompts are presented with sequence numbers, and the PATH environment variable has been modied so that access to Unix commands is restricted (note: simply type export PATH=$UPATH to get around this). Excellent reference books on Ksh abound- one of them (highly recommended) is The Kornshell Command and Programming Language by Bolsky and Korn, published by Prentice Hall.

NOTES:

Motorola Confidential Proprietary

93 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell MM Software Overview

MM SS7 UNIX SVR4 Operating System Disk Cntrls Supercell Application SW UNIX Utilities

SS7 Sync. Cntrls

TCP/IP Enet Cntrls Enet Cntrls

To MSC (through DSUs)

SCAP over TCP/IP (Ethernet & Token Ring)

Supercell software running on MM:

Supercell System Initializer- SCSIIM. SS7 process set. Software Load Management- SLM. Supercell Device Operations- SCDEVOM. Volume Data Transfer- VDT. Performance Measurement- PM. Call Processing- CP, CLCP, CPMO. Event Management- SCEVMGR. Command-Line Interface- CLI. Gateway- MM_GW.

94 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell MM Software Overview The following are the main software sub-systems involved in Supercell, along with brief explanations of the functions covered by the sub-systems:
The SCSIIM sub-system is responsible for establishing the Supercell application process set. The process is started during the MM platforms normal startup sequence (as part of a Unix re-boot or platform cold start). The SS7 software sub-system is responsible for establishing SS7 connections over the MMs V.35 cards to the MSC. This sub-system consists of several processes which perform different functions related to the SS7 links (monitoring, sending/receiving data over the links, routing, etc.). The Software Load Management sub-system (SLM) manages the software releases for the MM and its sub-tending devices. Commands such as INSTALL, DEINSTALL, and ACTIVATE are handled by SLM. The Supercell Fault Management sub-system (SCDEVOM) manages the MMs subtending devices, taking the appropriate actions should a device go out of service. It is also responsible for loading and initializing the devices. The Volume Data Transfer sub-system (VDT) is responsible for establishing TCP/IP connections to devices and transferring data to and/or from the devices. Code and data for devices needing download is sent through the VDT sub-system. The Performance Management sub-system (PM) is responsible for collecting statistics pegs and counts, and forwarding this information to the OMC-R. Information such as MCC element usage and call completion ratios is collected by the PM sub-system. The Call Processing sub-system is responsible for the call processing activities on the MM. It consists of Connection-Oriented Call Processing (CP, for short), Connection-less Call Processing (CLCP), and Call Processing Maintenance and Operations (CPMO). The Event Management sub-system is responsible for propagating alarms and event reports to all the proper destinations. The Command-Line Interface sub-system (CLI) is responsible for the basic user interface functions at the MM. The Gateway sub-system (MM_GW) is responsible for establishing and monitoring a TCP/IP connection with the OMC-R.

NOTES:

Motorola Confidential Proprietary

95 of 259

96 of 259

PWID Center for Excellence

Supercell MM Software Architecture

CLI Session scsiim UNIX Shell Spooler

dgen pm_collect SW Load Info scdb CDF Access DB Updates DB Access Real Time Database (RTOs) R/W Application Segment VDT Control & Buffering DB Access

Command Event Reports mmgw

Motorola Confidential Proprietary

J7NodeControl DB Access Resource Allocation callproc1

Event Reports Event Manager

Shared CDF

sc_devom

Resource Allocation VDT Cntl

Data Dnld File Disk CDF Access Code/Data Files and Uploads SW Load Control mmslm TCP/IP VDT

Paging Cntl & Call Assign. Trace Cntl

Revision 0, 4/24/97

TCP/IP -w- OMC Log Security Events Alarms sec_mgmt L o UNIX Trigger g

clcp

API VDT Segments Cntl cpmo Trace Uploads

C D F s

L o a d s

TCP/IP

J7/SS7

The Tandem MM Platform & UNIX OS

API

DGM&S J7/SS7 Pkg.

UNIX Operating System

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell MM Software Architecture The purpose of the previous page is to present the whole picture of the Supercell MM software. The following points are presented on the overall architecture:
The UNIX OS is bottom-most layer of software, all access to physical devices by the Supercell processes must be made through UNIX. The operator must also use UNIX when equipping new cards on the MM, for installation of the MM software, as well as for general operations of the platform (cleaning up les, etc.). A software entity called the Application Programming Interface (API) lives between the OS and the Supercell processes. In reality, the API consists of a software library which is linked in to the Supercell processes, along with a lot of shared memory which is established by the SCSIIM process. The software applications use the API in order to perform common tasks (such as sending and receiving messages, publishing alarms and event reports, setting/clearing timers, etc.). At the top left corner of the previous page (when viewed in landscape mode) is the SCSIIM process. This process is the rst Supercell process brought up by Unix. In turn, this process sets up the shared memory environment and starts bringing up all the other processes in the diagram. Once SCSIIM has nished bringing all the processes up, it just listens for processes that die, and performs the appropriate action. So, SCSIIM is the mother of all Supercell processes. These processes have a great deal of debugging information built into them- when a problem is suspected in a particular area (such as Call Processing), the debugging messages for CP can be activated by using a program call dbapi. Some of the processes in the diagram show up for the rst time; sec_mgmt, which stands for Security Management sends an alarm when someone has exceeded the maximum amount of failed login attempts. The dgen process produces data les to be downloaded to the MMs sub-tending devices (such as MCC cards). The pm_collect program is the Performance Measurement process. Note that all the processes are ovals, while squares are either shared memory, or entities such as UNIX or the API.

NOTES:

Motorola Confidential Proprietary

97 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Platform Initialization:
Reset I/O Init UNIX Load

Daemons

File Systems

Startup Scripts

Login Prompt

Power up, I/O Subsystem Initialization- I/O cards are recognized and initialized. Unix loaded from the boot partition, all cards and storage units are recognized, memory initialized. Start system daemons. Check, Mount File Systems.. Run startup scripts. The /etc/inittab le is master, then /etc/rc<N>.d scripts are executed. Present login prompt at console. User may then login, and supercell processes should be coming up at this time.

98 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Platform Initialization
The MM will go through its start-up sequence at these times: When the MM is powered up (both switches on the backs of the Service Processors are in the on position), or when the MM is reset through a hostreset host command at the console, or when the MM is reset through a cntrl-CORE key sequence at the console, or when the MM reboots itself due to a PANIC condition. As a general note: The MMs console is the ONLY location where information on the MM reboot can be seen in real-time. So, it is important that the console be monitored during a reboot in case any anomalies should occur. First the MM will do an I/O initialization, where all the card hardware is recognized. Messages such as the following will be seen at the console:
Cabinet configuration: Central Office Identified Interphase Ethernet Controller in iop 0, slot 0 Identified Interphase Ethernet Controller in iop 1, slot 0

Then the Unix OS is loaded from the boot partition. In order to access the boot partition, the command mkbootdisk may be used. The boot partition is special- it can only be accessed through the mkbootdisk command (it is not normally mounted). Messages such as the following will be output when Unix is loaded:
loading file disk(1,0,5)unix 2349616+390992+1116272 text entry:0x80031000, start: 0x80031000, end:0x8026ea2f data start:0x8026ea30, end:0x802ce17f bss start:0x802ce180, end:0x803de9ef

System daemons are then started. A daemon is a process that runs in the background, usually elding asynchronous requests. Examples are the rpcd (Remote Procedure Call Daemon), and the inetd (internet services deamon). The init process is started, which then reads the /etc/inittab le and starts processes specied in that le for the run level in which the machine is coming up. The /etc/inittab le has a value called inittdefault, which sets the run level of the machine to 4 for Supercell. At run level 4, a script called /sbin/bcheckrc checks several sub-systems in the MM- including the le systems. The init process then runs the script /sbin/rc4, which in turn will run all the scripts in /etc/rc4.d. It is useful to look at the scripts in /etc/rc4.d, since they perform such tasks as conguring the ethernet cards, mounting le systems, removing les in /tmp, and resetting the SS7 cards. Towards the end of the /etc/inittab le, entries for a process called ttymon will enable a login prompt to be presented at the console and at any tty session. NOTES:

Motorola Confidential Proprietary

99 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell Initialization: SCSIIM

Unix Stuff Unix Init Supercell Stuff SCSIIM /etc/inittab /sc/scsiim/scsiim.logle /screl/active/data/scsiim_cdf.mm1 CLI INIT

SCSIIM:
- starts from the unix init program. - establishes Supercell system on MM and OMC. - reads specications for Supercell system from / screl/active/data/scsiim_cdf.mm1. - outputs indications to /sc/scsiim/scsiim.logle. - brings up Supercell processes, monitors them for process death.

Several types of INITs (done at CLI):

- INIT Level 1 (re-boots the Tandem platform) - INIT Level 2 (re-starts only the Supercell Processes) - Both above may specify Force mode to be either Yes or No, for re-reading the MM database les.

100 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell Initialization: SCSIIM

SCSIIM is the rst Supercell process to be started up by the MM platform, after a Unix reboot. The scsiim process reads from the le /screl/active/data/scsiim_cdf.mm1, which species how the MM platforms Supercell software is to be congured. The shared memory conguration (size, name, type, etc.) is included in this le, along with information on environment variables which must be established for the processes, and information on the processes themselves. The following is an excerpt from the cdf le:
PROC = { // monitorApi - monitor proc growth & shared memory usage ... ActionOnDeath = Restart, (NOTE: some output deleted due to space). Name = monitorApi, Path = /screl/active/bin/monitorApi, Priority = 20, Args = /screl/active/data/scsiim_cdf.omc -dbg ERROUT /sc/processes/ monitorApi.err -dbg ALL 0 -dbg OUTPUT /sc/processes/monitorApi.out, },

The scsiim process will place information on whats going on in the le /sc/scsiim/ scsiim.logle. The following is an excerpt from the le:
Fri Mar 29 00:24:18 1996 omc PID: 1710 scsiim: Attempting to spawn process: SyslogdRefresh Fri Mar 29 00:24:18 1996 omc PID: 1710 scsiim: Non-lockstep process: SyslogdRefresh instantiated. Pid: 1779

The CLI command called INIT is used to re-initialize an MM. The commands format is as follows:
cli prompt> INIT MM-1 [Level=1|2] [Force=Y|N]

The Level may be either 1 or 2. If the level is 1, the MM platform will be re-booted via a unix fastshutdown command. This will cause all processes (including unix processes) to be shutdown and re-started. If the level is 2, only the Supercell software will be restarted. In any case, a Force parameter may be specied to Y (or Yes) if the user wants to re-read the entire MM database from the CDF les residing on the hard drive. Normally this step is done only if corruption is suspected in the data. After bringing up all the processes, scsiim will monitor the processes and perform the appropriate action should a process die. The action will be specied in the scsiim_cdf.mm1 le. The /sc/scsiim/scsiim.logle le is very important, especially during a platform initialization. A good operator will keep an eye on the le through a tail -f command.

NOTES:

Motorola Confidential Proprietary

101 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell Process Set

popper MonitorAPI scemlogd mmgw scevmgr SCSIIM sec_mgmt vdt_1, 2

SCSIIM sequences supercell process initialization. popper starts up SS7 process set. Similar to scsiim, but only controls SS7 process set. Most processes started by scsiim output indications to les in /sc/processes/<processName>. MonitorAPI monitors consumption of certain resources on MM (and OMC). scemlogd manages ring buffer and set of les containing last messages sent and/or received. mmgw establishes and manages link to OMC. scevmgr sends events to all interested parties. sec_mgmt posts alarm on excessive failed logins. vdt_1, vdt_2 establish virtual connections for data transfers on demand.
102 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

The Supercell Process Set

The SCSIIM process will sequence the start-up of all the Supercell processes. It is important to watch the initialization sequence carefully, since several processes are of type Mandatory, meaning that if the process cannot initialize properly, the rest of the initialization will be terminated, and SCSIIM will attempt to re-initialize the whole platform again. SCSIIM has protection against innite roll-overs, and will generally do only 2 reinitializations when a mandatory process fails to initialize. After the second attempt, scsiim will bring all remaining Supercell processes down, and will wait for the operator to x the situation. After xing the situation, the operator must re-initialize scsiim manually. The initialization sequence proceeds in a clockwise manner in the diagram on the previous page. Several short-lived processes have been omitted for simplicity. The rst process is popper- this process will eventually start all the SS7 process set. Initialization messages for the SS7 processes will be output to the screen (more on this later). The SS7 process set has its own scsiim equivalent which monitors and re-starts any process which should die. Most of the processes started by scsiim will output indications to les in /sc/processes/ <processName>. Any core dump les (which are les produced by the OS when a process dies prematurely) are also kept in these directories. The MonitorAPI process monitors the consumption of platform resources such as lesystem size, memory consumed by processes, and shared memory usage. This information is kept in /sc/processes/MonitorAPI.?, where ? is a number from 0-4. The scemlogd process keeps log les of the most recent message activity in the system. The les are /sc/processes/scemlogd.log.?, where ? is a number from 0-2. The mmgw process reads the /screl/active/data/aec/ENTITIES le in order to establish a TCP/IP connection with the OMC-R. The scevmgr process is next- it will allow other processes to send events to all interested parties, including the OMC-R through the mmgw process. The sec_mgmt process will post an alarm when a user exceeds a certain amount of login attempts. The vdt processes (vdt_1 and vdt_2) will establish TCP/IP virtual circuits to devices needing download. This will be done on an as-needed basis, usually through a request from the sc_devom process (more on this later).

NOTES:

Motorola Confidential Proprietary

103 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell Process Set- Cont.

mm_slm dgen scdb sc_devom pm_collect SCSIIM mmtadadm cpmo fepMon scfm_poke clcp callproc1

mm_slm checks consistency of release directory, handles requests for release management. dgen generates data images for download on demand. scdb parses CDF les, establishes MMs DB, handles DB-related requests. sc_devom manages devices under MM, including initialization and fault management. pm_collect collects statistics information from devices in network, transfers les to OMC-R. mmtadadm manages periodic tests, diagnostics. cpmo handles requests for call traces, call teardown, call prole records. callproc1 handles most call processing tasks. clcp handles paging, re-paging, class0 msgs.
104 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

Supercell Process Set- Continued

The mm_slm process checks the /screl/release/*.lst and *.rds les for consistency with the release directory structure. It is important to note that if there is an inconsistency in the software release, mm_slm will cause the MMs initialization sequence to be halted. The dgen process will generate download les for devices in the network in an ondemand basis. The les will be downloaded to the devices using the vdt processes. This download process is managed by sc_devom. The scdb process parses all the CDFs (Conguration Data Files), in order to create a real-time database in shared memory which contains data on all the elements in the Supercell network. The process then handles requests for recent change on the data (when network elements are moved, added, or modied). It is important to note that if a CDF le contains errors, the scdb process will fail to initialize and that will cause the MMs initialization sequence to halt. The sc_devom process handles all the operations & management of the Supercell devices under control of the MM. All data downloads, initializations, code downloads, and fault recovery actions are coordinated by sc_devom. This process listens to a particular TCP/IP connection to the FEPs over which all asynchronous state change event notications are sent by the devices under the MM, and it takes appropriate action upon receipt of those messages. The pm_collect process initiates data uploads from several Supercell devices for collection of performance measurements. This data is then transferred to the OMC-R through a unix ftp command. The mmtadadm process periodically spawns tests, audits, and diagnostics on the devices under the MM, and publishes alarms should a device fail a test. The cpmo process establishes several data structures in shared memory for reference by the other CP processes, and it is also responsible for forwarding requests for call traces, call teardowns, and call prole record upload to the callproc1 process. The callproc1 process handles call set up, handovers, teardowns, disconnects, registrations, and also generates call detail records and statistics information. The clcp process handles all connection-less oriented message trafc. The scfm_poke process is an optional process which will cause the CLI command ENABLE CBSC UNC to be performed at the end of the initialization. The fepMon process monitors the FEPs for connectivity to the MM.

NOTES:

Motorola Confidential Proprietary

105 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Software Installation
MM

OMC-R

Installation document has the nal word! First, boot platform from tape device. Next, run sysinstall program. Boot from disk, install required packages, optional packages. Install IPMs, if necessary. Run Motorola Installation script.
passwords for root, scadm, a7adm, lmf accounts. Timezone information Ethernet conguration (addresses, gateways, etc.) SC9600 release software SS7 installation, card setup, Point Code Setup Activate SC9600 software

Re-boot platform, MM should initialize the Supercell release software.

106 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Software Installation An overview of the software installation process is presented here, along with tricks & tips for future reference. Please note that the Supercell Software Installation Document is the authority on software installations.
A full software installation on the MM will typically take about 3 hours to perform (if the hard drives are not re-formatted). Please note that it should be necessary to do this procedure only when initially installing software (on a just-out-of-the-box platform). A scratch installation should not be performed as a catch all for problems that cannot be solved. The problem should be isolated rst- a scratch install is the LAST RESORT for debugging a problem (rarely will a scratch software installation solve the problem anyway). The platform is rst booted from the boot tape (which should be supplied with the Tandem box). After booting from tape, a # prompt will be presented, at which the user must enter sysinstall. Note: the sysinstall command is actually a script which may be modied if necessary. After the sysinstall, the machine is re-booted (this time from the newly loaded disk drives), and the required and optional packages are loaded onto the platform. If any IPMs (updates to the OS) are needed, then these are loaded at this time. The Motorola installation scripts are then run. These scripts allow an operator to install the platform with a minimum of manual steps required. However, the scripts are somewhat sensitive to values which are incorrectly entered, and to interruption of the script ow. The scripts are all ksh scripts which reside in /usr/sc.install. The main script is called MakeSC9600, and it in turn invokes functions which are contained in the le InstallFunctions.ksh. As the scripts are run, a le called FunctionsDone is populated with the names of the functions which have been performed successfully. Should it ever be necessary to perform one of those functions again, the functions name must be deleted from the FunctionsDone le. Thus, the next time MakeSC9600 is invoked, it will start at the rst function called in the MakeSC9600 script which does not have an entry in the FunctionsDone le. The MakeSC9600 script will prompt the operator for the values of several parameters, and will install the SS7 software, Supercell software, and congure the ethernet cards and SS7 cards, along with Point Codes for SS7 communication and account passwords for the a7adm, scadm, lmf, and root accounts. Timezone information will also be requested from the operator. Please note that the Software Installation Document (available in the CIG library) is the authority on installs. NOTES:

Motorola Confidential Proprietary

107 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Operations- Tools & Tricks

!#?&@^!

OMC-R

MM
Problems may occur with any of a number of systems on MM. Most problems are due to incorrectly congured software parameters. When SS7 links wont align:
- Use a7 terminal handlers displ-slk; command. - Use SS7 network analyzer. - Double-check route to MSC (check DSUs).

When the Supercell processes wont initialize:

- Check scsiim.logle. - Check output and error les. - Turn up DBG levels using dbapi, or in scsiim_cdf.mm1.

108 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Tandem MM Platform & UNIX OS

MM Operations- Tools & Tricks Problems may occur on the MM which require user intervention- usually these problems will occur the rst time the MM is to be placed into service, or when new software has been loaded on the platform. The source of these problems is almost always incorrectly congured software. The following is information which will help in debugging problems:
Become familiar with the tools available for use on the MM. Also become familiar with the location of log les for such sub-systems as the SS7 system. The SS7 links from the MM to the MSC must be aligned properly in order for the MM to initialize all the devices in the Supercell network. See also the chapter on SS7- it has much information on point codes and debugging link problems. A common problem in link alignment is incorrectly set point codes. Check point codes by using the a7 terminal handler- login as a7adm, and run start_term. Then enter: displ-opc; and displospc;. Link status may be checked by entering displ-slk;. As a last resort, all point code and link information may be removed by performing the following commands:
# cd /usr/a7 # find . -name \*.254 -exec rm -f {} \;

Beware of the above, since you will have to re-provision the SS7 links once all the *.254 les are removed. The links are re-provisioned through entering commands at the a7 terminal handler. Another common problem is that the DSUs that service the MM-MSC link are faulty or incorrectly congured- verify the connections, and re-seat and re-power the DSUs as a possible debugging step. When the Supercell processes wont initialize correctly, the rst step is to look at the /sc/ scsiim/scsiim.logle le, and determine which process is causing a problem. Then proceed to look at that processs .err and .out les in /sc/processes. This should point to the problem. If mm_slm refuses to initialize, it is almost always because of a defective or incorrectly loaded software release. If scdb refuses to initialize, it is almost always due to bad CDF les. Try to get CDF les which have been produced from a clean MIB. The debug levels of processes may be modied in order to display more information. The Supercell process dbapi is capable of doing this through the mDbg command, and it can display information of debug levels through the S <processName> DbgStatus command. Debug levels may also be changed through modifying the scsiim_cdf.mm1 le, specically the Args eld for the processes.

NOTES:

Motorola Confidential Proprietary

109 of 259

Conclusions:
The MM is a Unix-based platform which has been customized to work in the Supercell environment. MM is a fully hardware redundant platform- availability across single hardware failures insured. The MMs main functions are call processing, operations & maintenance- other functions include statistics collection, test & audits, implementation of recent change to the Supercell network. The Unix OS is a powerful Operating System which allows multiple streams of execution to run simultaneously on the cpu. The MM utilizes the Veritas software to manage disk drives and le systems for redundancy. Supercell software is composed of several processes, each of which implement particular functions. SCSIIM starts up all the Supercell processes, and restarts them should they die (according to spec.). MM Software installation is done through the use of Ksh functions- MakeSC9600 is the main script. Several tools and tricks may be used to analyze failures on the MM- among them are dbapi and the a7 term handler.

110 of 259

Motorola Confidential Propretary

PWID Training: CDMA

The OMC-R and UNO Platforms

Motorola Confidential Proprietary

111 of 259

Objectives:
To present the OMC-R platform utilized in Supercell CDMA in detail- including architecture (software and hardware), theory, and operations. To present an overview of the UNO platform (more information on UNO is available through a TEM videotape).

112 of 259

Motorola Confidential Proprietary

Table of Contents:
OMC-R Architecture and Interfaces ........................................................................... OMC-R Physical Conguration................................................................................... The OMC-R Supercell Software Architecture............................................................. Platform Software Initialization .................................................................................. Informix & the MIB ..................................................................................................... OMC-R Operations....................................................................................................... Supercell Device Provisioning Hierarchy ................................................................... The UNO Platform ....................................................................................................... 115 117 119 121 123 125 127 129

Motorola Confidential Proprietary

113 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

OMC-R Architecture and Interfaces

OMC-R Informix UNIX SVR4 Operating System Async. Cntrls Disk Cntrls Supercell Application SW UNIX Utilities TCP/IP Enet Cntrls Enet Cntrls

To XCs, Modems, etc.

SCAP over TCP/IP (Ethernet & Token Ring)

The OMC-R is the same fault-tolerant UNIX box as that used for the MM, with some exceptions. The OMC-R connects to the MM and to the UNO platform via TCP/IP over Ethernet. The OMC-R has an RS-232 connection to each XC in the system, in order to perform O&M specic to the XCs. A modem with an external line may be connected for remote access.

114 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

OMC-R Architecture and Interfaces The OMC-R is very similar to the MM, in that the same base platform is utilized. However, there are some important differences and attributes of the OMCR which the following points address:
The OMC-Rs CPUs are not as fast and have less on-board (local) memory than the MM: The CPUs runs= at 50 Mhz, while there is 64Mb of local RAM. There is still 16Mb of global RAM on the OMC-R. Asynchronous cards are used on the OMC-R in order to communicate with printers, modems, and RS-232 lines (such as the XC OMP GPROC connections). The OMC-R requires more disk space because of its role in life. (Current conguration as of this writing has 3 logical drives of 2 gig each for a total of 6 gigabytes). The SS7 software suite does not run on the OMC-R (there is no need for this). Informix is used extensively on the OMC-R in order to provide a Managed Information Base (MIB), which contains much information on the sub-tending CBSCs. The OMC-R connects to the MM and the UNO platforms by using TCP/IP over Ethernet. The Ethernet connections are through coaxial cable, commonly called 10Base2. Ethernet transceivers (also called MAUs) must be used by every device connected to the ethernet 10Base2 network. In order to perform operations & maintenance which is specic to the Transcoder subsystem, the OMC-R is connected via serial lines to the XCs in the system. These connections may have to be done via modems if the XCs are not co-located with the OMC-R (however, most sites have co-located XCs and OMC-R). The OMC-R may also have a modem with a direct outside line connected to it, in order to allow remote access to the OMC-R (and remote dial-out as well). In order to provide the above mentioned connections, the OMC-R has two Async cards, each capable of eight serial connections (RS-232).

NOTES:

Motorola Confidential Proprietary

115 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

OMC-R Physical Conguration

151 152 161 162 163 164 165 166 167 168

} }
DC PWR (75
Fan Modules(3)

Air intake

SPC

SPC Ether- SCSI SCSI Ether-Async Ether-Async Etheror net net 0 1 0 1 net net SPC 0 2 3 1 Bypass

I/O Controller Card Shelf

I/O Processor 0

Bulk Power Supply Module

2 gig Disk

Processor Card Shelf

2 gig disk c0d3 c0d0 201 211 c0d1 c0d4 (tape) 202 212 c0d2 203 c1d5 213 2 gig disk c1d6 221 c1d0 222 c1d1 223 2 gig Disk

Fan Modules(3) Air Exhaust (bottom, front and rear)

Memory A

Memory B

Air intake (front only)

I/O Processor 1 2 gig Disk

CPU-A

2 gig Disk

Storage Device Bay

Very similar to MM, except for I/O cards and Storage Device Bay. Total disk space is greater, due to requirements for storage of CDLs and other data. Async cards replace the SS7 cards on the MM. The OMC-Rs lesystems are markedly different from the MM.

116 of 259

Motorola Confidential Proprietary

CPU-C

CPU-B

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

OMC-R Physical Conguration The OMC-R and the MM have much in common- the physical cabinet is the same, but the I/O cards and the Storage Device Bay are different. The following points are given with respect to the OMC-R physical conguration:
With the exception of the Async cards (which replace the SS7 cards), the I/O cage layout is identical to that of the MM. The Async cards are used for serial connections to devices in the Supercell network, and to modems for outside access. The OMC-R uses more disk drives since the requirements for storage are greater- Call Detail Logs (CDLs) are stored at the OMC-R, as well as information from statistics collection from devices in the Supercell network. The following is the result from a volprint -v command on an OMC-R running release 2.4:
TYPE vol vol vol vol vol vol vol vol vol vol vol vol vol vol NAME boot cdl home mibrdbs miniroot rdbspace root sc screl swap swap1 swap2 usr var ASSOC gen fsgen fsgen gen fsgen gen fsgen fsgen fsgen gen gen gen fsgen fsgen KSTATE ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED LENGTH COMMENT 40000 2011144 342724 204800 20000 163840 131072 2230511 1212416 65536 393216 262144 512000 140000

The cdl lesystem is used to hold Call Detail Logs. The mibrdbs data space (notice that it is not a lesystem) is used by the Informix engine to hold data for the Supercell Managed Information Base (MIB). The rdbspace is also used by Informix, but this space holds other Informix data bases (not the MIB). The sc lesystem holds performance management (PM) data (including statistics), as well as some CDL logs and other logs for Supercell processes. The swap volumes are for adding more virtual memory to the OMC-R. The volprint -s command may be used by the curious (or otherwise interested) parties to nd out where the above mentioned volumes reside (on which disks).

NOTES:

Motorola Confidential Proprietary

117 of 259

118 of 259

PWID Center for Excellence

The OMC-R Supercell Software Architecture

scsiim UNIX Shell

CLI Session Spooler sdc omcmib

Applications - Alarm Mgr - PM Database.

omc_slm

Command omcgw
Motorola Confidential Proprietary

Event Reports Alarms & State Chng Event Rpts Database Access

Event Reports Security Alarms sec_mgmt ted XC Alarms API Segments UNIX Trigger RS-232 / XC MMI

Revision 0, 4/24/97

scevmgr

pm_rqst Log Events L o g s D B L o a d s P MD a t a ASCII PM Data

CDL Log

TCP/IP -w- OMC

File Transfer (Bulk via FTP)

API

The OMC-R and UNO Platforms

UNIX Operating System

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

The OMC-R Supercell Software Architecture The OMC-Rs Supercell software architecture is different from that of the MM. The following points are made on the architecture:
The API again serves as the interface between the OS and the application software. It is the same API as in the MM, and provides the same services. Event reports, alarms, CDLs, and PM statistics are stored on the OMC-Rs disk drives, and may be browsed (or viewed) by using CLI commands on the OMC-R, or by using the more user-friendly interfaces provided by the UNO platform. The OMC-R receives information from each of the MMs that are connected to it through the omcgw process. This process has TCP/IP connections to each of the MMs through the Ethernet network. As of release 2.4, an OMC-R and the MMs that are connected to it must be on the same release- this is due to the format of the messages that are sent between the omcgw and mmgw processes- if a release changes the format (or adds or deletes messages), then both platforms must be on the same release. However, as of release 2.6, a new feature will be added which will allow the OMC-R and the MM to talk to each other across different releases. The scevmgr process performs much the same job as it does on the MM, which is to route event messages and alarms to their proper destinations. Destinations usually include any CLI sessions which have registered for events or alarms. The scevmgr on the OMC-R also keeps a log of all the events in the system, which may be browsed by using the BROWSE CLI command. The omcmib process interfaces with the Informix software and with the rest of the Supercell software in order to implement commands which add, modify, or delete devices in the MIB. The pm_rqst process requests on a periodic basis for statistics information to be downloaded from the MMs through an FTP protocol transfer. The ted process is the Transcoder Event Daemon- it uses the RS-232 links to the XCs in order to present XC alarms to the Event Management system (scevmgr, sdc, UNO, etc.).

NOTES:

Motorola Confidential Proprietary

119 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

Platform Software Initialization

Unix Stuff Unix Init Informix SCSIIM Supercell Stuff

CLI INIT

/etc/inittab /sc/scsiim/scsiim.logle /screl/active/data/scsiim_cdf.omc

Unix Init process is initialized during the Unix startup sequence. Script /etc/rc4.d/fast/S97informix initializes Informix. SCSIIM is started by the Init process, and starts-up all the Supercell processes. SCSIIM will then idle until CLI INIT command is performed, or until a process dies. Uppon process death, the appropriate action will be performed.
120 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

Platform Software Initialization The OMC-R goes through a similar initialization process as that of the MM. The Unix side of affairs is identical, except for the additional volumes and lesystems that must be checked, and the fact that the OMC-R has async card, but no SS7 cards. The following points concern the software initialization of the OMC-R:
The Unix Init process will read from the /etc/inittab, running in run-state four. The runstate four will cause the /sbin/rc4 script to be run, which in turn will run the scripts in / etc/rc4.d/fast directory. Among the scripts in the /etc/rc4.d/fast directory is a script called S97informix, which will initialize the Informix database system (more on this later). The informix database system must be up and running in order for the Supercell software to initialize correctly (the omcmib process will not come up if the Informix system is not up). The SCSIIM process is started by the Unix Init process, and the SCSIIM process proceeds to establish shared memory and environment variables as specied in the / screl/active/data/scsiim_cdf.omc le. The SCSIIM process then starts bringing up the processes specied in the scsiim_cdf.omc le. The output le for scsiim is /sc/scsiim/scsiim.logle (just as in the MM), and the output les for the processes brought up by scsiim are in /sc/processes as well. Once SCSIIM has brought up all the Supercell processes specied in the scsiim_cdf.omc le, SCSIIM will pause and wait for a CLI INIT command to be performed, or for a process to die. Should a process die, SCSIIM will perform the action specied in the scsiim_cdf.omc le (which could be restart, re-init the platform, or do nothing at all).

NOTES:

Motorola Confidential Proprietary

121 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

Informix & the MIB

S97informix Unix Init tbinit dbexport tbmonitor dbimport sqlturbo dbaccess /usr/informix/etc/tbcong sqlturbo Informix Utilities tbmode

Installation scripts initialize disk space for root db space. tbspaces command used for mibrdbs db space. MIB must be loaded at installation time, or empty MIB must be created and populated via CLI commands. dbimport utility used to load MIB into OMC-R, dbexport utility used to export a MIB. tbmonitor utility used to get status of databases, user information, and other statistics on informix system. dbaccess utility used to access information in a db through SQL commands. tbmode utility used to force checkpoint, or to change mode of informix online engine.
122 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

Informix & the MIB

Informix is brought up through the Unix Init program, when the /etc/rc4.d/fast/ S97informix script is executed by the /sbin/rc4 script. The S97informix script will setup some environment variables, and then execute a tbinit process. The tbinit process is in charge of starting up the Informix software subsystem, including the initialization of the shared memory used for informix. An ipcs command at the OMC-R should show at least one shared memory segment owned by user informix. The sqlturbo processes are brought up by the processes needing access to the informix database information. There are two processes on the OMC-R which access information in the MIB: omcmib, and mmi_ping. As part of the OMC-R installation, the installation scripts will initialized the disk space to be used for the root db space (root db space is always required), and the tbspaces informix utility will be used to create a new db space which is the mibrdbs space created on disk by the installation scripts. Information on this space is kept in the root db space. At installation time, the installation scripts will ask for a mib to be imported. The command used to import a mib is called dbimport. It expects a directory to be specied in which a set of les exists. These les are the result of a previous dbexport command done a properly congured MIB (usually Systems Engineering is responsible for providing a good MIB). The les are ASCII les which contain the data for each of the tables in the MIB, in addition to a le which contains Structured Query Language (SQL) commands which create the database structure and tables. The tbmonitor Informix utility is a menu-driven program which allows an operator to status the informix system, including information on users, databases, and certain actions (such as forcing a checkpoint) may be performed as well. The tbmode utility is used to change the mode of operation of the informix engine. The dbaccess Informix utility is a menu-driven program which allows an operator to enter SQL commands in order to display or modify data in the database. If a MIB is to be created from CLI commands, this utility must be used to rst create an empty MIB. See http://scwww.cig.mot.com/SC/test/cdma_foa/FOA/OMCR/emptymib.creation and http://scwww.cig.mot.com/SC/test/cdma_foa/FOA/OMCR/device.states (on the WWWuse Netscape or Mosaic) for information on how to create an empty MIB, and how to set the proper device states.

NOTES:

Motorola Confidential Proprietary

123 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

OMC-R Operations

OMC-R

OMC-R

OMC-R is a management point for CDMA network. However, functions are migrating to UNO platform. CLI environment on OMC-R may be used to perform any of the following:
- Status queries on system devices. - Add, delete, or modify system devices or system parameters. - Display statistics information (PM reports). - Browse through alarms and event reports. - Select certain alarms or event reports to be displayed in real-time. - Load, enable, disable system devices. - Handle system alarms through the Alarm Manager application.

124 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

OMC-R Operations
Many operations may be performed on the OMC-R in order to manage the CDMA network. It should be noted that much effort is being placed by Motorola to make the UNO platform be the management interface to the CDMA network. However, it will always be possible to perform network management of CDMA through the OMC-R since some customers may not opt for buying the UNO platform. The CLI environment is used on the OMC-R in order to manage the CDMA network. One function which may be performed is that of getting status of the different devices in the network under the OMC-R is shown below. The display command may be used to display the status and the parameters on practically any device in the system (see System Commands Reference manuals for more information).
cli> display omcr allstatus

Operations which effect changes on the CDMA network may be performed at the OMCRs CLI session. The add and delete commands are used to provision or remove devices in the CDMA network. More on provisioning on the next slide. The PM reports may be viewed by using the dbaccess menu-driven program (in absence of the UNO platform). The SQL command select * from <tableName> may be used inside the dbaccess program, where <tableName> is replaced by a table describe in the Performance Analysis manual published by TED. However, it is highly recommended that a UNO platform be used for viewing statistics, or an alternative software package such as PM Sum be used (check out http://www.rochellepark.pamd.cig.mot.com/ software.html). The command BROWSE CDLLOG is used to browse through CDLs, while BROWSE EVTLOG is used to browse through event reports. Both commands accept many options, including start and end information for the period of time desired, and desire attributes of the records to be displayed. At a CLI session, the command ENABLE EVENTS is used to enable events and alarms to be displayed at the CLI session. In addition the SUBSCRIBE EVENTS command may be used to set lters so that only the desired alarms and events are displayed. A process called the Alarm Manager may be started at an X-terminal connected to the OMC-R in order to manage alarms through a GUI. The commands CUTOVER, LOAD, ENABLE, and DISABLE are used to manage devices in the CDMA network.

NOTES:

Motorola Confidential Proprietary

125 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

Supercell Device Provisioning Hierarchy

LEGEND: Required Assoc. when Provisioned Optional Assoc. when Provisioned Non-Parental Assoc. enforced when deleting MMI Add/Del MMI MSC Add/Del XASECT XASECT Add/Del XCSECT XCSECT XCLINK
(OMP)

OMC Add/Del OMCR MM CBSC Add/Del CBSC -C

FEP(R) Add/Del FEP NCON BTS SPAN

MSI

Add/Del MSI Add/Del MSCSPAN MSC SPAN C7LINK

Add/Del BTSSPAN BTSDS0 SRCHAN

Add/Del BTS RFDS RGLI

BTS

-C

Add/Del CSM

Add/Del C7LINK

SECTOR -C

CSM TERCKT XCLINK

(CPP)

BTSLINK Add/Del BTSLINK

Add/Del TERCKT

Add/Del XCLINK

CARRIER Add/Del CARRIER

Add/Del MDM

MDM

GLI Add/Del GLI BBX(R) Add/Del BBX Add/Del MCC MCCCE

LPA LCI Add/Del LPA

BDC TCHwc MCC

PCH Add/Del PCH SCH Add/Del SCH ACH Add/Del ACH

Devices shown include physical (MSI, LPA, etc.) and logical (SCH, CBSC) devices. Devices usually provisioned through CLI commands on off-line MIB. Small changes can be done on-line.
126 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

Supercell Device Provisioning Hierarchy The device hierarchy is presented here because the OMC-R is the central repository for the information, and it also is responsible for carrying out the necessary actions when the hierarchy is changed. The following regards the hierarchy:
The hierarchy follows (with two exceptions during deletion) a parent-child approach. None of the devices are allowed to be provisioned in the database unless the proper parent-child relationship exists. For example, it is not possible to add a BTSSPAN without specifying a valid MSI through which the span information will ow. In general, the devices will be provisioned in an off-line manner, usually by a Systems Engineer who can utilize an OMC-R (or an OMC-R simulator) which is not in commercial service in order to generate a MIB. However, many times changes to devices in the CDMA network will be done through CLI commands at the OMC-R. The OMCR is responsible for updating the physical device, verifying that the update was performed, and then updating the MIB. Procedures for adding/deleting devices from the CDMA network are found in the Cellular System Administration manual, published by TED (manual number as of this writing: 68P09226A21-O). The following are the expansions to some abbreviations which may be confusing:
NCON XASECT XCSECT BTSDS0 SRCHAN MDM MCCCE TCHwc ACH PCH SCH Nailed Connection External Analog Sector External CDMA Sector BTS Digital Signaling 0 (this is a timeslot on a T1/E1 spanline) Sub-Rate Channels (each BTSDS0 has four of these, each at 16 Kbps) Modem Cage (this is where the GLI, MCC, BDC, and BBX cards reside) Multiple Channel Card Channel Element (each MCC-8 has 8 of these) Traffic Channel Walsh Code Access Channel Paging Channel Signaling Channel

Many of the devices have associated parameters which may be set as part of the provisioning operations. Check with Systems Engineering personnel for the latest recommended parameters document. There is a BSS Sysgen tool available which facilitates the generation of MIBs- contact PWID System Engineering Software Tools Group for the latest version of this tool.

NOTES:

Motorola Confidential Proprietary

127 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

The UNO Platform

UNO

OMC-R

OMC-R
UNO- Universal Network Operation platform.
- Connects to OMC-R through a TCP/IP over ethernet connection. - Is a Sun Sparc20 with cdrom drive, several hard drives for large storage capacity. - Is the preferred platform for CDMA management.

UNO Provides:
- Alarm Manager, Status Display, Geographical Display GUIs. - Data Analysis (analysis of PM data) - On-line documentation (using WorldView)

An open interface is used- other devices can be managed.

128 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The OMC-R and UNO Platforms

The UNO Platform Much emphasis is being placed on moving management of the CDMA network to the UNO platform (indeed, much has already been done). The following points concern release 2.4 of the UNO platform:
UNO stands for Universal Network Operation platform. The idea behind UNO is to integrate all devices in a cellular network under one platform which will be the Operator Interface to the devices. What used to be the Applications Processor has turned into UNO. The UNO connects to the OMC-R through a TCP/IP connection over ethernet. However, a protocol called CMIP is used at both the OMC-R and the UNO platform for transferring data and commands related to Events, Control, and database access. CMIP stands for Common Management Interface Protocol, and is an open interface developed by Sun Microsystems for the management of devices in a network. The commands are generic enough so that any device that needs to be managed may build a CMIP agent which is capable of translating general CMIP commands into their corresponding native language commands (for example, the OMC-Rs native language would be CLI commands, while the SwitchMates native language would be CAT terminal commands). The UNO platform currently provides all customer documentation through an Interleaf viewer called WorldView, an Alarm Manager GUI, a Status Display GUI, a Geographical System Display, and data analysis tools (for analyzing PM data). More information on the UNO platform is available through a TEM (Technical Enrichment Matrix). TEM libraries are accessible at Arlington Heights, Ft. Lauderdale and (I think) Ft. Worth facilities.

NOTES:

Motorola Confidential Proprietary

129 of 259

Conclusions:
The OMC-R is the same platform as the MM, with some modications due to its different role in life. The OMC-R software architecture is also similar to the MM- however, the process set brought up by SCSIIM is very different. Informix plays a large role on the OMC-R. Informix is brought up by Unix, and used by the Supercell processes in order to access data in the MIB. All network management functions for Supercell may be performed at the OMC-R. These include changes to the network, as well as status queries, device state transitions, and statistics display. When adding or deleting devices in Supercell, the Supercell device hierarchy governs the relationships which must exist between devices. The UNO platform is the preferred platform for managing the Supercell network, since its graphical capabilities and user-friendly interfaces make it a more attractive alternative than the OMC-Rs CLI interface.

130 of 259

Motorola Confidential Propretary

PWID Training: CDMA

The Transcoder Platform

Motorola Confidential Proprietary

131 of 259

Objectives:
To present the Transcoder platform utilized in Supercell CDMA in detail- including architecture, theory, and operations.

132 of 259

Motorola Confidential Proprietary

Table of Contents:
The Transcoder Architecture ....................................................................................... Clock Signals in the XC ............................................................................................... TDM Bus and KSW Card............................................................................................. The GPROCs................................................................................................................. The Token Ring............................................................................................................. The MCAP and SBUS Buses ....................................................................................... MSI Connections .......................................................................................................... XC Troubleshooting- Preparation & Denitions ........................................................ XC Troubleshooting- First Steps.................................................................................. XC Troubleshooting- Device States ............................................................................. XC Sudden Trouble- Token Ring ................................................................................. XC Troubleshooting- Defective Token Ring ................................................................ More XC Troubleshooting Notes ................................................................................. Loading Software into the XC...................................................................................... 135 137 139 141 143 145 147 149 151 153 155 157 159 163

Motorola Confidential Proprietary

133 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The Transcoder Architecture

To half-size boards and AMR card To MM via Router with GPROC 2.048 Mbps (To DSU/MSC) or BTS) 2 span-lines per MSI Serial Bus Token Ring LAN Ethernet LAN MCAP Bus

To MM with GPROC-II

KSW

GPROC

GPROC II

MSI

XCDR

TDM Bus

BTSs, MSC data transported through TDM bus. All buses are redundant. GPROC-II will dispose of router (future). MCAP provides asynchronous communication between GPROCs and peripheral boards. Token Ring LAN allows MM to communicate with GPROCs, GPROCs to communicate with each other. Serial Bus allows status and control of half-size cards and AMR card by GPROCs.
134 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The Transcoder Architecture Knowledge of the XCs architecture will help in troubleshooting problems with the XC. The following points are made regarding the XCs architecture:
The backbone for all the PCM, QCELP, SCAP, and A+ data owing through the XC is the TDM highway. There is a TDM bus for inbound data, and another for outbound data (inbound/outbound from the perspective of the KSW). The TDM buses are redundant (so there are four in all). Trafc on the TDM bus is managed by the KSW card. Remember the following denitions: PCM is digitally coded voice data (at 64kbps) between the MSC and the XC. PCM is usually transported through a T1 or E1 span line. QCELP is digitally coded voice data (at 16Kbps) between the XC and the BTS. QCELP occupies one/fourth of a 64Kbps channel on a T1 or E1 span line. SCAP is digital control data between the MM and the BTS. SCAP is transported from the MM with TCP/IP over Ethernet, and then the FEP changes TCP/IP packets into LAP-D. The LAP-D packets are then packed into a 64Kbps channel on a T1 or E1 span line which goes to the GLI at the BTS site. A+ is digital control data between the MM and the MSC. When the MSC and the MM are not co-located, this data is usually transported through a nailed connection using a 64Kbps channel of a T1 or E1 span line. All buses in the XC are 2n redundant. Redundancy in the XC cards is highly recommended, and if implemented, will be 2n for the KSW, 2n for GPROCs, and n+1 for the FEP. This diagram is simplied- the LANX cards are not shown, XC is single cage. In the future, the GPROC-II card will allow the router to be eliminated, since the GPROC-II card will have a TCP/IP over Ethernet interface. The MCAP bus allows the GPROCs to talk to other non-GPROC boards for purposes of initialization, collection of alarms, download of rmware, and connection/disconnection messages to the KSW board. The Token-Ring LAN allows GPROCs to talk to GPROCs in other shelves, in addition to connecting the MM with the XC. The Serial Bus allows GPROCs to talk to half-size cards and the AMR board for purposes of initializing and obtaining status.

NOTES:

Motorola Confidential Proprietary

135 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

Clock Signals in the XC

kswx 0 kswx 1 clkx 3 clkx 6 GCLK3 GCLK5 Clock signal A kswx 0 kswx 1 MCAP Bus A

MCAP Bus B KSW, GPROC MSI, or XCDR KSW, GPROC MSI, or XCDR

cage 0

kswx 0 kswx 1

cage 2

kswx 0 kswx 1

MCAP Bus A

MCAP Bus A

MCAP Bus B KSW, GPROC MSI, or XCDR KSW, GPROC MSI, or XCDR

MCAP Bus B

cage 1

cage 3

All cards synced to clock in GCLK card in cage 0. Four-cage XC shown. CLKx cards with ber-optics are used to extend clock to other cages. gclk5 feeds clock to clkx6, which sends clock to kswx1 in cages 0, 1, 2, and 3. gclk3 feeds clock to clkx3, which distributes clock to kswx0 in cages 0, 1, 2, and 3. kswx1 cards feed clock to the MCAP bus A in each cage, while kswx0 card feeds clocks to the MCAP bus B in each cage.
136 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

Clock Signals in the XC

In order to maintain synchronization inside the XC and between the XC and the MSC, the same reference clock signal must be distributed to all cards in the XC. Typically, the MSC serves as the master clock reference, and the XC database has dened two MSC spans as reference signals for the XC GCLK cards. These cards then phase lock the timing signal to that of the spans, and hence the XC is synchronized with the MSC. Cards called CLKx (Clock Extenders) allow the timing signal to be extended to multiple frames. A single frame XC could have a GCLK provide the timing directly to the MCAP bus in that frame, but as soon as a KSWx board is placed in the XC, a CLKx will be necessary in order to distribute the clock to the frame. Fiber optics are used to interconnect the CLKx boards. The timing sub-system in the XC is fully redundant. The GCLK card in slot 5 distributes the timing reference to the CLKx card in (half-size bay) slot 6. The CLKx card then distributes via ber optic cable the signal to the KSWx boards in slot 1 of every cage. The KSWx boards in slot 1 of each cage will then feed the signal to the MCAP Bus A. The other side is identical, with the exception of the slot numbers. The GCLKs card in slot 3 distributes the timing reference to the CLKx card in (half-size bay) slot 3. The CLKx card then distributes via ber optic cable the signal to the KSWx boards in slot 0 of every cage. The KSWx boards in slot 0 of each cage will then feed the signal to the MCAP Bus B.

NOTES:

Motorola Confidential Proprietary

137 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

TDM Bus and KSW Card

copy data x from to KSW timeslot 150 to from KSW timeslot 400 timeslot=1023 timeslot=400 timeslot=150

KSW

timeslot=0

MCAP bus
x y x

TDM bus
x y x y

timeslot=0 timeslot=150 timeslot=400 timeslot=1023

from KSW
46

102

4kb

ps

to KSW
tim eslo ts

copy data y from to KSW timeslot 400 to from KSW timeslot 150

All switching of data is performed in KSW card. 1024 timeslots @ 64kbps for total of 65Mbps capacity in each TDM bus. Multiple KSWs may be inter-connected to increase capacity. KSW performs sub-rate switching at 16Kbps, packing 4 channels of 16Kbps each onto a single TDM channel. XC has two separate TDM highways, 0 and 1.
138 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

TDM Bus and KSW Card

The KSW card is responsible for managing data on the TDM highway. A TDM highway is composed of two buses, each capable of 1024 TDM channels at 64Kbps rate. There is an inbound TDM bus (inbound to the KSW card), and an outbound TDM bus. The KSW card receives orders from the OMP GPROC over the MCAP bus when a connection is to be made or broken. Using KSWx cards, a TDM highway may be extended to other cages. Up to a maximum of four KSW cards may be congured on one TDM highway. Each of the KSW cards will be able to select from all of the timeslots on the inbound lane of the TDM highway, but will be able to place trafc only on its outbound lane (1024 ports). Thus, a XC with two KSW cards will be able to switch between 2048 input ports and 1024 output ports, with three cards it will be 3072-1024, and with four cards, 4096-1024. The KSW card contains hardware which is capable of sub-rate switching data on the TDM highway, which means that any two bits from any inbound TDM channel may be placed in any (multiple of two bits) location on a channel of the outbound TDM lane. A 64Kbps timeslot will send 8 bits at a time- this is divided by four to achieve the 16Kbps rate, which results in 2 bits at a time for every 16Kbps sub-rate channel. The XC platform has two separate TDM highways, 0 and 1. There are two entirely different hardware paths for these highways in order to provide true redundancy.

NOTES:

Motorola Confidential Proprietary

139 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The GPROCs
OMP EXE DLS C P MCA DLS P P LAP D route r SM

FEP1

CA

TBUS 0 0

MMI

RS232

terminal

MCAP Bus

LAN

token ring (TCP/IP)

CPF 1

token ring (Motorola protocol) xc pc

MM
FEP2 LAN EXE DLS C P MCA DLS P P r CP MMI

RS232 terminal

TBUS 1 0
LAP D

route

MCAP Bus

FEP GPROC routes messages between MM and OMP, CPP. OMP GPROC uses MCAP, TDM, SBUS buses, manages KSW cards, device states in XC. CPF GPROC uses MCAP, TDM buses, performs call processing functions. Shelf GPROC provides OMP access to other cages.
140 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The GPROCs
The GPROCs perform a variety of jobs, depending on the software which is loaded on the processor. All GPROCs are capable of interfacing with 32 64Kbps serial paths via the TDM switch highway, a 16 Mbps token ring LAN, the Motorola Cellular Advanced Processor (MCAP) bus, and four additional RS-232 serial interfaces (one of which is available on the front panel). The GPROCs are powered by 24 MHz Motorola 68030 processors with 16 Mb of RAM, 32 Kb of non-volatile RAM, and 1 Mb of ash rom. The simplest type of GPROC is the Shelf GPROC, which only runs the processes which manage the buses of the cage in which it sits. Shelf GPROCs are necessary in order to allow access by the OMP and CPF GPROCs to shelves which have no OMP or CPF GPROC. Processes running on the Shelf GPROC include the MMI (Man Machine Interface) which provides a command interpreter, the MCAP DLSP (Motorola Cellular Advanced Processor Bus Data Link Service Process), which handles messages being sent to and from the peripheral boards (XCDR, MSI, GCLK, etc.), and the TTY DLSP which manages the serial bus for communications to the half-size cards and the AMR card in that cage. The OMP GPROC has all the Shelf GPROC processes, plus a process called Central Authority (CA) and another called Switch Manager (SM). CA keeps track of XC device states and does whatever necessary to change their state (sending/receiving conguration messages, orders, and code load over the MCAP bus). SM manages timeslot connections in the KSW (ordering the KSW through the MCAP bus to make or break connections on the TDM highway). The CPF GPROC has all the Shelf GPROC processes, plus a process called Call Processing (CP). The CP process terminates call processing SCAP messages sent by the MM through the FEP GPROC (which then places the SCAP message into a LAP-D format on the TDM bus for consumption by the CPF GPROC). The CP process makes and breaks call connections by sending messages to the SM process on the OMP GPROC via the token-ring bus. The FEP GPROC runs the LAN software, the LAPD software, and the router software. The LAN process on the FEP interfaces with the token ring in order to communicate with other FEPs and with the MM. The LAPD software talks through the TDM bus in order to exchange LAPD messages with the BTS devices (through the CSLDL links) and with the OMP and CPF GPROCs (through the MXLDL links). The router process switches messages going through the FEP to their proper destination.

NOTES:

Motorola Confidential Proprietary

141 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The Token Ring

through backplane LANX OMP FEP 1 slot 20 cage 0 slot 25

MM

LANX CPF 2 FEP 3 slot 20 cage 2 ethernet (over coax) xc pc LANX router shelf gproc FEP 4 slot 20 cage 3 LANX CPF 1 FEP 2 slot 21 cage 1 slot 25

ber optic token ring

LANx provides token ring access for all GPROCs in a cage. Token ring is 16 Mbps IEEE 802.5 standard. Token ring provides comm. link between non-FEP GPROCs, between FEPs, between MM and FEPs. FEPs use different language (TCP/IP) than other GPROCs (Motorola Proprietary), but both use IEEE 802.5 transport.
142 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The Token Ring

A ber optic token ring network is used in order to achieve high-speed communications between the MM and the FEPs, between FEPs, and between all non-FEP GPROCs in the XC. The LANX card interfaces all GPROCs in a XC cage with the token ring. The token ring is a 16Mbps bi-directional communications path, governed by the IEEE 802.5 standard. All GPROCs (including the FEP GPROC, before the FEP software is loaded on it by the MM) speak the same proprietary Motorola protocol over the token ring. The XC-PC also speaks this language, and uses the language in order to download software to the XC GPROC cards. Once the FEP software is running on the FEP GPROCs, the FEPs start talking TCP/IP to the MM over the same token ring network. However, the TCP/IP packets are being picked up by the Router and sent over the TCP/IP over Ethernet network to the MM. All other IEEE 802.5 packets (which include those used by all other GPROCs in the XC) are ignored by the MMs router.

NOTES:

Motorola Confidential Proprietary

143 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The MCAP and SBUS buses

MCAP: KSW initialization, download, and connect/disconnect messages: MCAP: MSI, XCDR, GCLK initialization and download messages only: SBUS: Initialization and status messages for half-size and AMR boards:
cage 1 cage 0 ber optic token ring MSI XCDR GCLK MSI XCDR LANX CPF GPROC MCAP SBUS SBUS KSWX AMR KSWX CLKX LANX KSW

MCAP KSW OMP GPROC

GPROCs talk to MSIs, XCDRs, and KSW boards through MCAP bus. Information sent over MCAP bus:
Initialization orders for the boards. Collection of alarms from boards. Download of rmware to boards. Connection/Disconnection messages to KSW card.

SBUS used to initialize and status half-size cards (LANX, CLKX, KSWX) and AMR card. MCAP and SBUS buses are local to their cages. Token ring used to communicate between cages.
144 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

The MCAP and SBUS Buses

The MCAP bus provides a path for the GPROC (the OMP GPROC) to communicate with the peripheral boards (full-size boards other than the GPROCs). The MCAP bus is used to communicate with the KSW, MSI, and XCDR boards. The OMP GPROC will need to communicate with the peripheral boards for any of the following functions: Initialization of the boards (during an XC initialization, or during an attempt to recover from a fault). Collection of alarms from the boards. Alarms are stored in the 32 Kb of non-volatile RAM on the OMP GPROC. Download of software to the boards. This is done during an XC initialization, or during an attempt to recover from a fault. Connection/Disconnection messages to the KSW board(s) for the TDM highways. The serial bus (SBUS) is used to initialize and status half-size boards and the AMR (Alarm Monitoring and Reporting) card. An example of a serial bus message would be a GPROC poll message to an AMR asking, What is the status of the fans and power converters?, or a GPROC diagnostic message to a LANX asking it for some kind of response to show that it is alive. The MCAP bus is local to a cage. If an OMP GPROC in cage 0 wants to send a message to a KSW card in cage 1, the OMP GPROC will send a message over the token ring to the MCAP bus administrator GPROC (usually the CPF GPROC, or maybe a shelf GPROC). This GPROC in cage 1 will relay the request over the local MCAP bus to the KSW card. The SBUS is also local to a cage. If an OMP GPROC wants to status a LANX card in another cage, the same scenario above is repeated (except the SBUS is used in the remote cage, instead of the MCAP bus).

NOTES:

Motorola Confidential Proprietary

145 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

MSI Connections
span cable to IDF XC Frame Top View- BIB Interfaces TOP of XC frame UPPER MS0 BIB card MS3 MS1 MS0 MS2 MS2 BIB 2 7,9,11 M M S S I I slot 13 MS3 BIB 3 6,8,10 MS2 BIB 2 7,9,11 MS3 BIB 3 6,8,10 MS0 BIB 0 13,15, 17 MS1 BIB 1 12,14, 16 MS0 BIB 0 13,15, 17 MS1 BIB 1 12,14, 16

through backplane

M S I slot 17

Lower XC Shelf(0)

Upper XC Shelf(1)

slot 15

MSI Cards support either 2 T1 or 2 E1 span lines. Three MSI cards interface through XC backplane to a BIB card. BIB provides isolation of XC from T1 or E1 line. MSI board connects via backplane to TDM highways. MSI board under control of OMP GPROC through MCAP bus. Cable pin-out for span cable to IDF on next page.
146 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

MSI Connections
Each MSI card is capable of supporting either 2 T1 or 2 E1 span lines. The MSI provides normal clock recovery, span line build out, elastic buffering and jitter attenuation, insertion and alarms and loopbacks for remote diagnostic capability. The MSI uses a Motorola MC68302 Integrated Multiprotocol Processor (IMP) to perform data processing and control functions. The T1 or E1 span lines are connected via the XC backplane to a connector which connects a ribbon cable to the top of the XC frame. At the top of the XC, a BIB (Balanced-Line Interconnect Board) provides isolation and impedance matching of the T1 or E1 to the XC signal path. A BIB board may be used for North American T1, Japanese T1, and European E1 (120 ohm - 3V), while a T43IB board must be used to interface with European E1 at 75 ohm & 2.37 V. Each BIB supports up to 6 span lines (thus each BIB supports 3 MSI cards). The MSI slot numbers which each BIB supports are given in the diagram. The following table gives the PIN wiring for the 37-pin D-connector at each of the BIBs:
Pins 1,20 2,21 4,23 5,24 7,26 8,27 10,29 11,30 13,32 14,33 16,35 17,36 Signal Span Tx t/r Rx t/r Tx t/r Rx t/r Tx t/r Rx t/r Tx t/r Rx t/r Tx t/r Rx t/r Tx t/r Rx t/r 1 1 2 2 3 3 4 4 5 5 6 6 Color white/blue,blue/white white/orange,orange/white white/green, green/white white/brown,brown/white white/gray,gray/white red/blue,blue/red red/orange, orange/red red/green,green/red red/gray, gray/red black/blue, blue/black black/blue,blue/black black/orange, orange/black

The MSI board is under control and status of the OMP GPROC through the MCAP bus. NOTES:

Motorola Confidential Proprietary

147 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- Prep & Denitions

Transcoder Frame

Preparing for trouble:

- Empty non-volatile RAM. - Verify that date is correct.

Types of trouble:
Sudden. Redundancy Activated. Activity-Induced. New CBSC. Occasional Voice Loss.

148 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- Preparation & Denitions Troubleshooting of the XC is like troubleshooting any other complex systemknowledge of the systems architecture is required, along with knowledge of the tools and methods available for analysis of problems, along with some imagination on the part of the trouble-shooter.
All XCs should be prepared for trouble before the trouble is ever encountered. All the non-FEP GPROCs should have their non-volatile RAM cleared by issuing the swfm clear fatal and swfm clear nonfatal, mmi commands. Fatal SWFM messages are placed in the non-volatile RAM until this space lls up- thus it is important that the memory be cleared. It is difcult to correlate the events happening in the XC to outside real-world events if the XCs time is not correct- use the chg_time command to place the proper time on the XC. There are several different types of trouble the XC may run into (indeed, almost any type of trouble for any network element will fall into one of these categories): Type Sudden (During normal operation, there is a sudden loss of voice or links) Redundancy activated (FEP, KSW, Clock redundancy) Activity-induced (During BTS expansion, BSC SW upgrade, or BTS reparenting) New BSC Affects service: Yes Cause This is usually due to hardware failure and lack of software redundancy in current releases. Immediate action may be required. This is usually due to hardware failure. Replacement of a board may be required. Most of the time, the trouble encountered is due to the new software, new hardware introduced (expansion boards), or new databases. There are many possible factors. Hardware, databases are all new. Maybe the most difcult to analyze, but there is time available to troubleshoot. If the number of no voice calls is very small, with no particular dependence on TERCKT and TCH used, then it may be a software bug.

No

Yes

Yes

Occasional no voice

Some

NOTES:

Motorola Confidential Proprietary

149 of 259

150 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

XC Troubleshooting- First Steps

L28

BTC 0 KSW A XCDR 0 XCDR 1 XCDR 2 XCDR 3 XCDR 4 XCDR 5 XCDR 6 GPROC 0 GPROC 1 GPROC 2 GPROC 3 GPROC 4 GPROC 5 GPROC 6 GPROC 7 XCDR 7 XCDR 8 XCDR 9 XCDR 10 XCDR 11 XCDR 12 XCDR 13 XCDR 14 XCDR 15 XCDR 16 XCDR 17 XCDR 18 GCLK A MSI 0 MSI 1 MSI 2 MSI 3 MSI 4 MSI 5 MSI 6 MSI 7 MSI 8 MSI 9 MSI 10 MSI 11

U28 U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4

RMT KSWX A4 RMT KSWX A3 RMT KSWX A2 RMT KSWX A1 RMT KSWX A0 EXP KSWX A2 EXP KSWX A1 EXP KSWX A0 LANX A LANX B

Determination of GPROC state is the rst step! GPROCs should all be in GPROC RAM state. GPROC in slot 20 will be the OMP GPROC. FEPs should all be in FEP INS state. Check status of equipment through mmi command disp_equipment.

L27 L26 L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6

Revision 0, 4/24/97

EXPKSWX B0 EXPKSWX B1 CLKX A0 EXPKSWX B2

The Transcoder Platform

KSWX B0 CLKX A1 RMT KSWX B1 CLKX A2 RMT KSWX B2 CLKX B0 RMT KSWX B3 CLKX B1 RMT CLKX B2 RMT KSWX B4 LOCAL KSWX A U0 LOCAL KSWX B

L5

L3

U3

GCLK B
U2

L1 L0

KSW B BTC 1

U1

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- First Steps

The rst step in debugging ANY Transcoder problem is to determine what state the GPROCs are in. Use the following table to do this: If LED is... Green steady on or blinking Green steady Green slow blinking Green fast blinking Green steady Red only Red and green blinking fast and Prompt is... Cust BSS MMI-0xxx ->, control-n gives ROM:emon_0xxx % Cust BSS MMI-0xxx ->, chg_level, control-n gives RAM:emon_0xxx % RT> only RT>, esc/return gives F> RT>, esc/return gives F> None Garbage, RAM:emon_0xxx % or ROM:emon_0xxx % then State is... GPROC ROM GPROC RAM FEP, OOS ROM FEP, OOS RAM FEP, INS Dead EEPROM programming in progress

The prompt is presented when an RS-232 terminal at 9600 baud, 8 bits, no parity is connected to the DB-25 pin connector on the front of the GPROC. There are two access levels possible using the RS-232 terminal. One is called the Customer Prompt and will be Cust BSS MMI-0xxx ->. The other is called the emon prompt and will be RxM:emon_0xxx%. When inside the customer prompt, a chg_level command will allow access to the emon prompt by pressing cntrl-n. In CDMA the password required is 5cardstud. The OMP, CPFs, and shelf GPROC cards should be in GPROC RAM state, while the FEPs should be in the FEP INS state. If any of the GPROCs are not in their proper state, then start looking for token ring failure problems (more on this later). If the GPROCs are all in the RAM, then the following command may be used to display the status of the devices. All devices should be either unlocked busy, unlocked enabled, or equipped busy:
Cust BSS MMI-0115-> disp_equipment bsc status location

NOTES:

Motorola Confidential Proprietary

151 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- Device States

UNEQUIP
Not Equipped

EQUIP

Locked Enabled

ENABLE DISABLE

Locked Disabled

UNEQUIP UNLOCK

UNLOCK FAILURE LOCK

UNLOCK

UNLOCK FAILURE

LOCK

Unlocked Busy

ACTIVE STANDBY

Unlocked Enabled

ENABLE DISABLE

Unlocked Disabled

DISABLE

LOCK

ENABLE FAILURE

Operational Transition:

Administrative Transition:

Above diagram illustrates valid states most XC devices may be in. Valid states are:
- Not Equipped - Locked Enabled/Disabled - Unlocked Busy/Enabled/Disabled

See results of disp_equipment bsc status location mmi command.

152 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- Device States

Three commands are used at the XC OMP MMI in order to manage devices: EQUIP, LOCK, and UNLOCK. The following are descriptions of the different XC device states: Not Equipped- device does not have an entry in the XC database. Locked- device is equipped, but is not allowed to go into service. Two sub-states exist: disabled or enabled- the XCs CA process automatically transitions between these states, depending on whether or not the device can be placed into service. Unlocked Busy- device is equipped, and is being used (active). Unlocked Enabled- device is equipped, and is ready to go into service if necessary (but is not currently being used). Unlocked Disabled- device is equipped, but an attempt to place it into service has failed. CA will continue to attempt to place device in service. The following command may be used at the OMP GPROC in order to display the state of all devices in the XC:
- disp_equip 0 location status NAME ID 1 2 3 | DEVICES PARENT(S)/ ADDITIONAL INFO | C/S | Admin OP ============================================================================= GPROC 0 0 0 | .................................. | 0/20 | Unlocked Busy GPROC 1 0 0 | .................................. | 0/21 | Unlocked Busy GPROC 2 0 0 | .................................. | 0/25 | Unlocked Busy GPROC 3 0 0 | .................................. | 0/23 | Unlocked Busy OMP 0 0 0 | GPROC 0 0 0 ..................... | 0/20 | Unlocked Busy MSI 0 0 0 | .................................. | 0/6 | Unlocked Busy MMS 0 0 0 | MSI 0 0 0 ..................... | 0/6 | Unlocked Busy MMS 0 1 0 | MSI 0 0 0 ..................... | 0/6 | Unlocked Busy GCLK 0 0 0 | .................................. | 0/5 | Unlocked Busy KSW 0 0 0 | .................................. | 0/27 | Unlocked Busy CAGE 0 0 0 | TDM HWY 0 ......................... | ----- | Unlocked Busy CAB 0 0 0 | .................................. | ----- | Unlocked Enabled SITE 0 0 0 | .................................. | ----- | Unlocked Busy XCDR 0 0 0 | .................................. | 0/26 | Unlocked Disabled CSLDL 0 0 0 | MMS 0 0 0[ 1]-FEP 0 0 0[ 3] | ----- | Unlocked Busy CSLDL 1 0 0 | MMS 0 0 0[ 2]-FEP 0 0 0[ 4] | ----- | Unlocked Busy CSLDL 2 0 0 | MMS 0 0 0[ 3]-FEP 0 0 0[ 5] | ----- | Unlocked Busy MXLDL 0 0 0 | GPROC 0 0 0[ 2]-FEP 0 0 0[ 1] | ----- | Unlocked Busy MXLDL 1 0 0 | GPROC 1 0 0[ 2]-FEP 0 0 0[ 2] | ----- | Unlocked Busy FEP 0 0 0 | GPROC 2 0 0 ..................... | 0/25 | Unlocked Busy CPF 1 0 0 | GPROC 1 0 0 ..................... | 0/21 | Equipped Busy CPF 2 0 0 | GPROC 3 0 0 ..................... | 0/23 | Equipped Busy

NOTES:

Motorola Confidential Proprietary

153 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Sudden Trouble- Token Ring

through backplane LANX OMP FEP 3 FEP 1 FEPs wait for poll, but when it does not come, they drop to OOS slot 25 cage 0 LANX BAD TOKEN RING, POLL DOES NOT ethernet REACH DESTINATION!!! (over coax) POLL

MM

FEP 4 FEP 2 FEPs wait for poll, but when it does not come, they drop to OOS LANX slot 25 cage 1

router token ring died, so usually only one LED on token ring card is lit.

FEP 7 FEP 5 FEPs wait for poll, but when it does not come, they drop to OOS slot 25 cage 2 FEP 8 FEP 6 FEPs wait for poll, but when it does not come, they drop to OOS slot 25 cage 3 LANX

ber optic token ring

First sign of trouble- MXLDL or XCLINK alarm. Token Ring Failure: FEPs, OMP are OOS RAM, other GPROCs are in ROM. MM normally polls FEPs. If FEPs dont see the poll, they drop to OOS.
154 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Sudden Trouble- Token Ring

The rst sign of trouble with the XC is usually an MXLDL or XCLINK alarm observed at the OMC-R. This alarm is an indication that something is wrong, and the rst step (as always) should be to determine what state the GPROCs (including FEPs) are in. The following is a table detailing the different sudden trouble types, and their usual symptoms: Trouble type Token ring failure (The important thing to remember about the token ring failure is that it will affect all GPROCs: FEPs, OMP, CPF, and shelf GPROCs.) Symptoms

FEPs will drop to OOS RAM or go red LED. Since the token ring is down, there is no messaging between the MM and FEPs, so the FEPs die due to lack of polls from the MM. (WARNING: This could also be an indication of an MM or router problem) CPF or shelf GPROCs will all reboot, and will be found in ROM. Since the token ring is down, there is no messaging between the OMP and other GPROCs, so the non-OMP GPROCs (CPF and shelf) will die from lack of OMP polls. OMP is in RAM as it should be, but if you check the emon prompt, you will see errors, indicating that the token ring is in beacon mode, and that links have been dropped. OMP GPROC failure OMP, CPF and shelf GPROCs have all rebooted and appear to be rebooting/initializing. FEPs still INS CPF or shelf GPROC fail- 1 CPF or 1 shelf GPROC seems to have rebooted and ure automatically recovered. FEPs still INS The MM pings the FEPs periodically over the TCP/IP network. If the FEPs do not see this message from the MM over a period of time, the FEPs will go OOS RAM. Please note that the ping from the MM may not be getting to the FEPs due to several reasons: defective router, defective LANX card, or a defective LAN ber optic cable. The last reason is less likely in a non-lab environment.

NOTES:

Motorola Confidential Proprietary

155 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- Defective Token Ring

RX 0-R Router TX 0-2E RX TX 0/20 2/20 All boards pictured are LANXs. Location x/y = cage x, slot y 1-3E RX TX 1/20 3/20 1/20 3/20 Router RX TX 0/20 TX RX RX TX 1-3E RX TX 0-2E RX TX 2/20

TX RX RX TX

1-R

Normal Fiber Optic Cabling- 4 cages

RX TX 0/20 TX RX RX TX 1-3E RX TX 1/20 3/20 1-R RX TX 2/20 0-R Router RX TX

#1: Is it the Router?

RX TX 0/20 TX RX RX TX RX TX 1/20 3/20 2/20

Router

#2: Is Cage 0 Ok?

#3: Are router, cage 0 Ok?

Use problem isolation techniques

- reset all GPROCs and KSWs between iterations - observe for link established message at OMP

Once problem isolated:

- replace defective device - reset all GPROCs and KSWs one last time - observe for XC init complete message at OMP

156 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

XC Troubleshooting- Defective Token Ring

When a defective token ring is suspected, the GPROCs and KSWs should be reset (by toggling the switches on their front panels). A defective token ring will result in the lack of a link established message at the OMP GPROC, and all GPROCs will reboot with a fatal SWFM message with a no good lan available message. Use problem isolation techniques by utilizing a spare ber optic cable to short out certain sections of the ber optic network, as seen in the diagram. Between each iteration, reset all the GPROCs and KSW cards, and check to see if the link established message appears. If the link established appears for case #1, then the router must be checked, and possibly replaced. However, replacing the router requires some programming as well- so replacement should be the last alternative (more on this later). If the message does not appear, then continue with case #2 (since it could be a bad router OR a bad component in the XC). If the link established message appears for case #2, then you can assume that the token ring path for cage 0 is okay. If not, then consider replacing the LANX card for cage 0. If the link established message appears for case #3, then you can assume that the router is okay. If not, then you can assume that the router is defective, and the router must be checked. Continue in the above manner until the culprit has been found. Note: removing and inserting ber optic cables is a delicate operation, which when done properly will pose no mechanical resistance. If you nd that the plug does not slide into the socket easily, then make sure that the bumps on the side of the bayonet plug are sliding into the grooves on the socket connector. Note: Replacing a LANX will require a torx screwdriver. There is a rotary switch on the LANX card indicating the cage ID of the parent cage- make sure this switch is set properly if any cards are replaced.

NOTES:

Motorola Confidential Proprietary

157 of 259

158 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

More XC Troubleshooting Notes

L28 L27 L26 L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6

BTC 0 KSW A XCDR 0 XCDR 1 XCDR 2 XCDR 3 XCDR 4 XCDR 5 XCDR 6 GPROC 0 GPROC 1 GPROC 2 GPROC 3 GPROC 4 GPROC 5 GPROC 6 GPROC 7 XCDR 7 XCDR 8 XCDR 9 XCDR 10 XCDR 11 XCDR 12 XCDR 13 XCDR 14 XCDR 15 XCDR 16 XCDR 17 XCDR 18 GCLK A MSI 0 MSI 1 MSI 2 MSI 3 MSI 4 MSI 5 MSI 6 MSI 7 MSI 8 MSI 9 MSI 10 MSI 11

U28 U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4

RMT KSWX A4 RMT KSWX A3 RMT KSWX A2 RMT KSWX A1 RMT KSWX A0 EXP KSWX A2 EXP KSWX A1 EXP KSWX A0 LANX A LANX B

OMP GPROC failure- FEPs stay INS. CPF, Shelf GPROC failure- GPROC reboots. FEP Redundancy- analyze data, replace FEP. GCLK Redundancy- replace bad board.

Revision 0, 4/24/97

EXPKSWX B0 EXPKSWX B1 CLKX A0EXPKSWX B2

The Transcoder Platform

CLKX A1 RMT KSWX B0 CLKX A2 RMT KSWX B1 CLKX B0 RMT KSWX B2 KSWX B3 CLKX B1RMT CLKX B2RMT KSWX B4 LOCAL KSWX A U0 LOCAL KSWX B

L5

L3

U3

GCLK B
U2

L1 L0

KSW B BTC 1

U1

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

More XC Troubleshooting Notes

If an OMP GPROC is in GPROC ROM state, then reset the entire XC to recover. If the OMP still does not initialize (no XC init complete message observed), then read the OMP error messages at a terminal which has logging capability by entering the following commands repeatedly, until no messages are left:
RAM:emon_0115% swfm read nonfatal RAM:emon_0115% swfm read fatal

In order to replace an OMP GPROC, switch the reset switch to disabled, replace the board, and reset all GPROCs and KSW cards. Wait for the XC Initialization Complete message, and then do an ENABLE CBSC command at the MM. If a CPF or Shelf GPROC is rebooting of its own accord, monitor the GPROC via a terminal from its serial port. At the OMP, place another serial terminal to its serial port, with logging enabled in order to log errors that may appear. At the faulty GPROC, read the swfm error indications (by entering the above two commands repeatedly). The output should be analyzed by XC support personnel- call MCSC in order to get an XC support person on-line. If a CPF or Shelf GPROC needs replacement, rst lock the device by entering the following at the OMP GPROC:
Cust BSS MMI-0115-> lock_device bsc GPROC <id> 0 0

Then disable the GPROC, replace it with a new one, and unlock the GPROC with the following command at the OMP GPROC:
Cust BSS MMI-0115-> unlock_device bsc GPROC <id> 0 0

Monitor the new GPROC, and make sure it initializes correctly. If a FEP fails, the redundant FEP will be enabled automatically, and it will take over the links that were on the failed FEP. In order to collect information from the failed FEP for analysis, connect a serial port to a computer which can log output to a le, and perform the following command at the FEPSCOPE prompt:
F> execlist system

The document for all fepscope commands is in the Arlington Heights network in /usr/ test/supcell/ife/frame/fepscope. The following commands may be used to check the status of the GCLK boards:
Cust BSS MMI-0115-> disp_dev_stat bsc GCLK 0 0 0 Cust BSS MMI-0115-> disp_dev_stat bsc GCLK 1 0 0

The master GCLK will be unlocked-busy, and have its green LED lit. Look at the event log in the OMP GPROC (use swfm read command) to check for bad GCLK. NOTES:

Motorola Confidential Proprietary

159 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

Loading Software into the XC

Transcoder Frame

Use XC-PC, placing PC on the Token-Ring LAN. Release and database les on PC (or database to be created by MMI commands). Reset XC with LANLOAD program running on XCPC- XC will be downloaded. Sysgen will be needed to build database from scratch.
- Script used on PC connected to OMP GPROC serial port.

Take PC off Token-Ring LAN, reset XC, enable CBSC.

160 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The Transcoder Platform

Loading Software into the XC

The XC software load is done through the token ring LAN, using the XC-PC. Generally, the XC-PC is kept off the LAN with the XC in order to avoid placing a single-point-offailure into the network. So, the ber optic LAN will need to be modied such that the PC is placed into the LAN. The XC-PC will have a software program call lanload loaded on its hard disk. In addition, the XC-PC needs to have all the les which compose the XC software release loaded into a directory on the PCs hard drive. This will usually be a sub-directory of c:\xc. In addition, if an XC database is to be loaded (as opposed to building one right on the XC through OMP MMI commands), the database object (a le with a .002 extension) must be copied into the XC software release directory. If this is a software upgrade, you want to upload the current XC database by performing the following: Place PC on the LAN (PCs Rx to LANx Tx, PCs Tx to LANx Rx). Start up lanload program in the XC release directory: lanload -f Reset the XC (reset OMP GPROC< followed by all other GPROCs and KSW cards) Observe that Link Established messages appear at the XC-PC (if not, XC will reboot). Wait for XC Initialization Complete message. Type u at the lanload prompt on the PC. Respond to prompts to upload object 2 from GPROC 0115. Download the code objects to the XC by re-setting the XC while the XC-PC is in the lanload program. Code objects will be downloaded to the OMP GPROC, and it will crossload other GPROCs and cards in the XC. If a database object was included in the XC-PCs XC release directory, at some point the XC will observe the Cust BSS MMI0115 -> prompt. Go to the emon prompt by typing chg_le, followed by a cntrl-N. This will complete the XC initialization and the XC will come into service. If you do not have a database object, the XC will say that a sysgen is needed, and you must type sysgen on. After changing security levels, run a script with commands to congure the devices on a PC connected to the OMP GPROC. Type sysgen off, then reset the XC. Observe the initialization sequence at the OMP GPROC by putting it in emon monitor mode (control-n, or change_level followed by control-n).

NOTES:

Motorola Confidential Proprietary

161 of 259

Conclusions:
The Transcoder is fully hardware redundant. GPROCs talk to other full-size cards in a shelf through the MCAP bus. GPROCs talk to full-size cards in other shelves through the token ring LAN. The TDM bus handles all data trafc to/from the MSC, BTSs, and between FEPs and other GPROCs. The SBUS allows a GPROC to communicate with half-size cards, and with AMR card. MSIs handle two T1 or E1 interfaces. Troubleshooting an XC requires knowledge of XC sub-systems and internal XC connectivity. Sudden Trouble on an XC is usually indicated by XCLINK or MXLDL alarms. The lock_device and unlock_device commands are used to disable/enable devices in the XC. The XC-PC is used with a program called lanload in order to download an XCs software.

162 of 259

Motorola Confidential Propretary

PWID Training: CDMA

The SS7 Sub-System: MM and MSC

Motorola Confidential Proprietary

163 of 259

Objectives:
To present the SS7 sub-system, with an emphasis on operation and debugging typical problems.

164 of 259

Motorola Confidential Proprietary

Table of Contents:
SS7 Denitions ............................................................................................................. Point Codes, A7 Terminal Handler .............................................................................. More on SS7 Links ....................................................................................................... The MSC & SS7- creating the SS7 sub-system ........................................................... SS7 Commands at the EMX......................................................................................... Sample Status Commands for SS7 on EMX2500 ....................................................... Debugging SS7 Link Problems .................................................................................... SS7 Denitions ............................................................................................................. Point Codes, A7 Terminal Handler .............................................................................. More on SS7 Links ....................................................................................................... The MSC & SS7- creating the SS7 sub-system ........................................................... SS7 Commands at the EMX......................................................................................... Sample Status Commands for SS7 on EMX2500 ....................................................... Debugging SS7 Link Problems .................................................................................... 167 169 171 173 175 177 179 167 169 171 173 175 177 179

Motorola Confidential Proprietary

165 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

SS7 Denitions
NETWORK
SCP AIN SCP SCP SCP AIN

Cluster

SSP End Ofce

STP

STP

CCSSO End Ofce

STP

STP MSC

STP

STP

SP
End Ofce

Signaling Point Codes Signal Point Area/Netwrk 0 to 255 0 to 7

EMX

Zone 0 to 7

C7 Point Cd.

Network ID 1 to 254

Cluster ID 0 to 255

Member ID SS7 Point Cd. 0 to 255

Member

SS7- transports telephony signaling information. Point Codes- used to identify network elements. STP- Signalling Transfer Point DPC- Destination Point Code OPC- Origination Point Code SCP- Signaling Control Point

166 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

SS7 Denitions
Common Channel Signalling System Number 7 (SS7) is an internationally standardized signaling system for telephony applications. SS7 denes a set of messages and ows which handle call control (setup, tear-down, billing, etc.). It also denes a communications protocol which implements management functionality for the SS7 links. STP is a Signaling Transfer Point, and can be thought of as a switch capable of routing trafc to other points in the network. SCP is a Signaling Control Point. The signaling control point usually originates SS7 messages, and/or is the sink for many SS7 messages in the system. The SCP is usually where a database will reside (for example, the 800-number database for the PSTN). Links which connect any two points in an SS7 network are called linksets. The linkset can be composed of one to sixteen links of 56 Kbps or 64 Kbps. Each linkset is identied by its Signaling Link Code (SLC) in order to route messages. A Destination Point Code (DPC) is a three octet number which uniquely identies the node that an SS7 message is destined to. An Originating Point Code (OPC) is a three octet number which uniquely identies the node that an SS7 message came from. Nodes in the SS7 network also have NODENAMEs, which are associated with point codes such that the nodename may be used to route messages to particular point codes.

NOTES:

Motorola Confidential Proprietary

167 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

Point Codes, A7 Terminal Handler

V.35 SS7 Link, 56/64 Kbps

EMX2500 OPC: 250-150-001 DPC: 251-151-001

MM DPC: 250-150-001 OPC: 251-151-001 S7Dpc: 104186 S7Opc: 104443

A7 Terminal Handler allows operator interface to SS7 sub-system on MM. SS7 parameters congured on MM through port_commands le. OPC & DPC are dened relative to the platform. CDF le on MM must match DPC & OPC information on MSC & MMs SS7 sub-system.

168 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

Point Codes, A7 Terminal Handler

The SS7 package on the MM includes an MMI (Man-Machine Interface) which allows an operator to perform actions on the SS7 software stack. The interface is called the A7 Terminal Handler. The SS7 links and link parameters may be modied through this interface, as well as other operations such as obtaining status of links, and setting point codes. The SS7 links must be provisioned as part of an initial MM install. Usually, a le called / usr/a7/conf/port_commands contains A7 Terminal Handler commands for provisioning the links. The rst line will have the MMs point code, while all other point codes are for the MSC. The point codes in the /screl/active/loadable/cbsc-1.cdf MUST MATCH those used by the MSC and in the SS7 software package. In the CDF les, the point codes are decimal representations of the hexadecimal point codes entered into the MSC and the A7 term handler, when the rst and third octets are swapped. For example, a point code of 251151-001 will be converted into hex: FB.97.1, then read from left to right: 1.97.FB, and convert this to decimal: 104443. This would be the number used in the CDF le. All the commands available from the A7 terminal handler (which is started as follows:)
a7termhandler -node A7 -logicalname a7th -destname PM ALW-MON:NAME=string; ALW-PRINT[:ID=string]; ALW-SNAPSHOT[:FILE=string]; BKUP-APPL:FROM=string,TO=string; BKUP-NODE; DISPL-BKUP; DISPL-MON[:PRT=YES/NO]; DISPL-PSTATUS; DISPL-PURGE; DISPL-QSTATUS; INH-MON; INH-PRINT; RST-APPL:FROM=string,TO=string; RST-NODE:SOURCE={PRIMARY/SECONDARY/TERTIARY},[CHGLOG=YES/NO]; RTRV-ALARM[:DATE=ALL]; RTRV-ERROR[:DATE=ALL]; RTRV-ILLOG[:DATE=ALL]; RTRV-INFO[:DATE=ALL]; SCH-BKUP:DAYS=number; SCH-PURGE:DAYS=number; STOP-NODE; ACTV-LSET:LSET=identifier; ACTV-SLK:SLK=identifier; ALW-MEAS:ID=MTPXMT/MTPRCV; ALW-RSET:RSET=identifier; CHG-CPC:SSN=number,ADD/DEL=number; CHG-REMSSN:PC=number,ADD/DEL=number; CHG-REPCPC:SSN=number,PC=number; CHG-RSET:RSET=identifier,ADD/DEL=identifier,PRIORITY=number; CHG-RSET:RSET=identifer,LOADSHR=YES/NO; CHG-TIMER:TIMER=identifier,TVAL=numberM/S/MS; CRTE-CPC:SSN=number,PC=number; CRTE-LSET:LSET=identifier,PC=number; CRTE-OSPC:PC=number; CRTE-REMSSN:PC=number,SSN=number; CRTE-REPCPC:SSN=number,PC=number; CRTE-RSET:RSET=identifier,PC=number,RTES=identifier,LOADSHR=YES/NO; CRTE-SLK:SLK=identifier,LSET=identifier,SLC=number,SPEED=number,PORT=number; DEACT-LSET:LSET=identifier; DEACT-SLK:SLK=identifier; DISPL-CPC; DISPL-LSET; DISPL-OSPC; DISPL-REMSSN; DISPL-RSET; DISPL-SLK; DISPL-SSN; DISPL-TIMER; DLT-CPC:SSN=number; DLT-LSET:LSET=identifier; DLT-OSPC; DLT-REMSSN:PC=number; DLT-REPCPC:SSN=number; DLT-RSET:RSET=identifier; DLT-SLK:SLK=identifier; INH-MEAS:ID=MTPXMT/MTPRCV; INH-RSET:RSET=identifier; RTRV-MEAS:ID=SCCP/MTP,TIME=00:00;

NOTES:

Motorola Confidential Proprietary

169 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

More on SS7 Links

Hmm... Im gathering info as fast as I can!

OMC-R

Example port_commands le for MM. Looking at SS7 logs on the MM

- Turning logging on/off. - Log le: /usr/a7/Logs/Monitor.log

Gathering information when problems arise

Turn logging on for aprox. 5 minutes. Run get.tandem.data script. Turn logging off. Send information to Motorola.

170 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

More on SS7 Links

An example port_commands le with all the commands to provision links on the MM follows. Please note that port 0 on the SS7 card is actually the bottom-most port!
CRTE-OSPC:PC=251-151-003; CRTE-LSET:LSET=LSET1,PC=250-150-50,TYPE=F; CRTE-RSET:RSET=RSET1,PC=250-150-50,RTES=LSET1; CRTE-SLK:SLK=SLK00,LSET=LSET1,SLC=0,SPEED=64K,PORT=0; CRTE-SLK:SLK=SLK01,LSET=LSET1,SLC=2,SPEED=64K,PORT=1; CRTE-SLK:SLK=SLK02,LSET=LSET1,SLC=4,SPEED=64K,PORT=2; CRTE-SLK:SLK=SLK03,LSET=LSET1,SLC=6,SPEED=64K,PORT=3; CRTE-SLK:SLK=SLK04,LSET=LSET1,SLC=1,SPEED=64K,PORT=4; CRTE-SLK:SLK=SLK05,LSET=LSET1,SLC=3,SPEED=64K,PORT=5; CRTE-SLK:SLK=SLK06,LSET=LSET1,SLC=5,SPEED=64K,PORT=6; CRTE-SLK:SLK=SLK07,LSET=LSET1,SLC=7,SPEED=64K,PORT=7; ALW-RSET:RSET=RSET1; CRTE-CPC:PC=250-150-50,SSN=254; CRTE-REMSSN:PC=250-150-50,SSN=254; ACTV-SLK:SLK=SLK00; ACTV-SLK:SLK=SLK01; ACTV-SLK:SLK=SLK02; ACTV-SLK:SLK=SLK03; ACTV-SLK:SLK=SLK04; ACTV-SLK:SLK=SLK05; ACTV-SLK:SLK=SLK06; ACTV-SLK:SLK=SLK07; CHG-SLK:SLK=SLK00,SLT=NO; CHG-SLK:SLK=SLK01,SLT=NO; CHG-SLK:SLK=SLK02,SLT=NO; CHG-SLK:SLK=SLK03,SLT=NO; CHG-SLK:SLK=SLK04,SLT=NO; CHG-SLK:SLK=SLK05,SLT=NO; CHG-SLK:SLK=SLK06,SLT=NO; CHG-SLK:SLK=SLK07,SLT=NO;

A useful logle for the SS7 sub-system is /usr/a7/Logs/Monitor.log. However, logging must be enabled if very useful information is expected (otherwise, only the basics are logged). Logging is turned on for the SS7 sub-system with the following command:
/usr/a7/bin/monitor -ln A7.SCCP -m 15

Logging is turned off with the following command. Please note that logging should not be turned on for commercial systems during busy hours.
/usr/a7/bin/monitor -ln A7.SCCP -m 0

A script called get.tandem.data is run in order to analyze and collect information for the SS7 sub-system, for later analysis by Tandem in order to debug problems with the SS7 software and/or hardware. This script will be included in /usr/a7/bin in later releases of the software, but is available now in /home/hilton0/perez/supercell/notes/ tandem/get.tandem.data in the Arlington Heights Sun network. NOTES:

Motorola Confidential Proprietary

171 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

The MSC & SS7- creating the SS7 Sub-System

Call Proc Mgr. Ext. Equip Processors Enable Build Mode Link Ext. Mgr. (LNKEXT) Make CBSC Node Disable Build Mode Common Chan. Mgr. (CCM) Common Chan. Dist. (CCD) (0-1) Common Chan. Link. (CCLK) (0-31) EMX2500 CCS Equip A+ Link Set Link Parameters Add link to Linkset Add linkset to routeset Enable Route Refresh Procs Activate links, linksets Set Timers

On the left, EMX2500 Common Channel Signaling Processors. On the right, steps necessary for creation of SS7 Database.

172 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

The MSC & SS7- creating the SS7 sub-system

The Link Extension Manager processor (LNKEXT) provides tandem message transport between SS7 subsystem and the rest of the switch. The LNKEXT allows the SS7 subsystem to pass call processing signalling message to the line trunk manager processors for call setup and trunk circuit maintenance functions, and for the LTMs to send messages to the SS7 system. The Common Channel Manager processor (CCM) provides management of the SS7 network. It is necessary to remove/restore this component when changes are made to the SS7 network since its memory holds information on the network. The CCM routes messages between the LNKEXT and CCD processors and contains an interface to the Trafc Metering and Measurement (TM&M) subsystem. The Common Channel Distributor processor (CCD) provides message formatting and routing to and from the links. The CCD is responsible for Link Selection for outgoing messages. It also determines if an incoming message is destined for this EMX, and routes the message accordingly. The Common Channel Link processor (CCLK) implements the link layer protocol. It provides the physical link through either RS449, V.35, or RS232 (depending on the implementation). The CCLK will normally be connected via V.35 to the MM, through a board in the rear of the CCS frame which will have either a DTE or a DCE Winchestertype connector for the cable to the DSU. Although the CCLK may have 2 physical ports, this is only possible for bit rates below 19.2 Kbps- since our links are 56 Kbps, we end up using only one link per CCLK. The equipage of the processors is usually done only once. There is information available in the Arlington Heights FOA groups home page on the SS7 subsystem. Moses Kunamalla has written a document which describes the commands necessary to build the database. Making the CBSC node involves creating sub-system names and indexes for the EMX and the CBSC. One or more A+ links are then equipped, and their parameters (including speed, time-outs, format, and others) are set. The A+ link is then added to a linkset. Then the linkset is added to a routeset, and the route is enabled. The processors for the CC subsystem are then reset, the links and linksets are then activated. Then the proper timers are set for the links. The CCLK processors will begin trying to align the links (the orange light will alternate on/off with a period of aprox. 3 seconds). When the links are aligned, the orange light on the CCLK will stay on.

NOTES:

Motorola Confidential Proprietary

173 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

SS7 Commands at the EMX

Im building a database, building a database, building a database, ha, ha, ha, ha!

EMX2500

Excerpt from commands used to build the SS7 subsystem on the EMX. Voice Trunks and CICs must be added as well.

174 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

SS7 Commands at the EMX

The following is an excerpt from a list of commands which are input at the MSC in order to congure the SS7 links. Commands such as these normally must be performed when the MSC is rst installed, and when any changes are performed to the SS7 network.
The following information is assumed in this setup: Local Node: EMX1 250-150-001 CBSC Node: CBSC1 251-151-001 Local node subsystem: EMXSS CBSC node subsytem: CBSCSS Initial number of A+ links is one (using link id 0) Initial number of voice spans is one with 23 circuits (span 16, ckts 385-407) Voice trunk group is 700 Links configured are V.35 DTE at 64Kbps external clocking from DSU with NRZ !Commands !Network Assignment !Enable Build Mode BUILD CCS NETWORK E Y CHANGE CCS NODE CBSC1 Y N 001 151 251 Y !Establish CBSC Node ASSIGN SUBSYS INDEX EMX1 10 ASSIGN SUBSYS INDEX CBSC1 10 Y CHANGE SCCP SSNAME EMXSS Y N EMX1 254 Y CHANGE SCCP SSNAME CBSCSS Y N CBSC1 254 Y CHANGE SCCP SSSTAT CBSCSS Y A N Y CHANGE SCCP SSSTAT EMXSS Y A N Y CHANGE SCCP SUBSYS EMXSS Y EMX N CHANGE CCS USERPA SCCP YONDMX N PA Y BUILD CCS NETWORK D !Disable Build Mode STATUS CCS PROCS ; !Verify Processors are in Service CHANGE CCS LINK 0 EQ Y !Equip A+ link CHANGE CCS LINKPA 0 1 1 4 4 NRZ !Establish Link Parameters CHANGE CCS LINKPA 0 2 N 256 N Y CHANGE CCS LINKPA 0 3 50 29 64 80 60 100 110 90 130 140 120 160 Y CHANGE CCS LINKPA 0 4 D S Y CHANGE CCS LINKPA 0 5 400 400 4 Y CHANGE CCS LINKSE LSCBSC Y AS CBSC1 ; ; F 1 0 1 0 Q Y Y !Add Link to Linkset CHANGE CCS RSMAST 4 LSCBSC 1 Q Y !Add Linkset to Routeset CHANGE CCS DPCRS EMX1 E Y !Enable Route CHANGE CCS DPCRS CBSC1 4 E D Y Y A Y Y REMOVE LNKEXT PROC A B !Refresh Processors RESTORE LNKEXT PROC A I ; REMOV LNKEXT PROC B B ; RESTORE LNKEXT PROC B I REMOV CCM PROC A B ; RESTOR CCM PROC A I ; REMOV CCM PROC B B RESTOR CCM PROC B I ; REMOV CCD PROC A B ; RESTOR CCD PROC A I REMOV CCD PROC B B ; RESTOR CCD PROC B I ; REMOV CCLK PROC 0 B RESTOR CCLK PROC 0 I DEACTIVATE CCS LINKSE LSCBSC !Activate Links and Linksets ACTIVATE CCS LINKSE LSCBSC ; DEACTIVATE CCS LINK 0 ; ACTIVATE CC LINK 0 Y !Set Timers CHANGE CCS TIMERS MTP 1 1 0 Y MTP 2 1 0 Y MTP 3 1 0 Y MTP 4 1 0 Y MTP 5 1 0 Y CHANGE CCS TIMERS MTP 6 1 0 Y MTP 8 1 0 Y MTP 10 30 0 Y MTP 11 30 0 Y CHANGE CCS TIMERS MTP 12 1 0 Y MTP 13 1 0 Y MTP 14 3 0 Y MTP 15 3 0 Y CHANGE CCS TIMERS MTP 16 2 0 Y MTP 17 1 0 Y MTP 18 30 0 Y MTP 20 100 0 Y CHANGE CCS TIMERS MTP 21 100 0 Y MTP 98 60 0 Y MTP 99 60 0 Y CHANGE CCS TIMERS SCCP 0 180 0 Y SCCP 1 300 0 Y SCCP 2 1320 0 Y SCCP 3 20 0 Y CHANGE CCS TIMERS SCCP 5 30 0 Y SCCP 9 30 0 Y SCCP 10 30 0 Y !Add Voice Trunks CHANGE MTN T1THRS 16 EQ 1 3 15 20 30 3 10 20 30 35 ;;;;;;;;;;;;; C CHANGE MTN T1THRS 16 ;;;;;;;;;;; 100 30 100 4 10 12 N Y Y Y N Y Y C CHANGE MTN TRKCKT 385-407 EQ M CHANGE MTN TRKGRP 700 EQ 0 0 0 0 0 0 Y CHANGE CP TRKGRP 700 ; ; 0 M 0 N N N BSS ALL Y CHANGE CP CKTTBL 385-407 CC7TRK 0 0 Y M CHANGE CP TRUNK 385 700 TWOWAY N 1 Y CHANGE CP CIC 385 ADD 385 CBSC1 Y DISPLAY BSS BSSRTE !Check to see if the BSS route is correct DISPLAY BSS CELRTE !For Hard-Handoffs checkt the cell route table

NOTES:

Motorola Confidential Proprietary

175 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

Sample Status Commands for SS7 on EMX

MM

These SS7 links wont align!! What do I do?

OMC-R

Display point code and sub-system name information. Display link parameter information. Display linkset information. Status the links.

176 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

Sample Status Commands for SS7 on EMX2500

To display point code and node name information:
DISP SCCP SSSTAT DISPLAY SCCP SSSTATUS DATE: 1/11/96 TIME: 16:02:19 SUBSYSTEM NAME : EMXSS SS SS SEND SS NAME NODE NAME POINT CODE NO. TRAF ASSIGNMENT REPL REPL LOCATION ------ ----------- ----------- --- ---- ---------- ---- ------------EMXSS HKEMX 250-150-001 254 YES ASSIGNED NO SUBSYSTEM NAME : BSSSS SS SS SEND SS NAME NODE NAME POINT CODE NO. TRAF ASSIGNMENT REPL REPL LOCATION ------ ----------- ----------- --- ---- ---------- ---- ------------BSSSS HKMM1 251-151-001 254 YES ASSIGNED NO

To display link parameter information:

>DISP CCS LINKPA LINK# : 0 PARAMETER GROUP : 1 DISPLAY CCS LINKPARMS FOR LINK: 0 DATE: 1/11/96 TIME: 16:07:22 CURRENT PARAMETERS : PHYSICAL CHANNEL INTERFACE BAUD RATE CLOCKING SIG ENCODE -------------------------------------RS449/V.35 DCE 64KB internal NRZ

To display linkset information (its important that SLC be the same as for the MM):
DISP CCS LINKSE LINK SET : LS001 CCS LINKSET : LS001 ASSIGN ADJACENT STATUS NODE ====== =========== AS HKMM1 LINKS IN LINK SET ======== 0 2 4 6 LINK PRIORITY ======== 1 1 1 1 3 2 1 0 DATE: 1/11/96 TIME: 16:10:00 LS ACT LINKS TYPE ALLOWED ==== ========= A 4

SRTM COMP ======= Issue 1 SLC ===

COMBINED LINK SET ======== ********

Status links:
STAT CCS LINK N 0-2 CCS LINK STATUS DATE: 3/19/96 SERVICE BLOCKED INHIBIT LINK # STATUS STATUS STATUS LINK SET ------------------------------------0 AOS UB UI LS001 1 NE UB UI ******** 2 AOS UB UI LS001 TIME: 12:34:23 CHANNEL STATUS -------------in service in service in service

Other interesting commands:

>DISP >STAT >LIST >LIST CCS DPCRS -> To find information on the destination point code SCCP SUBSYS -> Shows status of the EMX CCS subsystem CCS NODE ; ; -> Lists all the node names and their pointcodes SCCP SSNAME ; ; -> Lists the SS Name, Node Name, Point Code and SS Number.

NOTES:

Motorola Confidential Proprietary

177 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

Debugging SS7 Link Problems

T1 Spans- connected through DSX V.35, to SS7 Board 0, port 0 DTE/DCE Interface Board

V.35 56/64 Kbps EMX2500 OPC: 250-150-001 DPC: 251-151-001 MM DPC: 250-150-001 OPC: 251-151-001 S7Dpc: 104186 S7Opc: 104443

DSUs- provide Timing, link isolation.

Trace signal path- make sure there is a physical connection. Check SLC number assignments, point codes.
- Use a7 terminal handlers displ-slk;, displ-ospc, displ-dpc commands. - Use MSCs DISP CCS LINKSE, DISP SCCP SSSTAT commands.

Check DSU programming. Check link speed assignment. Re-seat DSUs. Replace cables. Replace DSUs.

178 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SS7 Sub-System: MM and MSC

Debugging SS7 Link Problems

One way to avoid problems altogether (and to make them easier to nd when they do appear) is to label all components correctly. All DSX (Digital Cross-Connect) jacks should be labeled properly, as well as all cables. The V.35 connections are present on the MMs SS7 card. It is important to note that SS7 card 0 (in slot 165) will have port 0 on the bottom. Port 0 is usually the rst to be congured- this port will be dened with SLC of 0 as well (see the port_commands le). The SLC on the MSC must be the same for this link! (use the DISPL CCS LINKSE command). The DSUs provide link isolation, timing for the link, and also they provide a means to monitor the links through the Digital Cross Connect (DSX). An SS7 LinkSet Monitor (such as the Wandel & Goltermann PA-41, or the HP 37900) may be connected to the monitor ports on the DSX. The DSUs should be checked if the links dont align. A loop-back may be performed at the DSX in order to isolate the faulty DSU. For example, if the link aligns at the EMX when the EMXs DSUs T1 connection is looped-back, then the MMs DSU is suspect. The proper settings for the DSUs are documented in the Arlington Heights FOA group page, under FOA/DSU. Note that when two DSUs are connected back-to-back (as in the diagram on the previous page), one of them must be setup as a DCE in order to provide timing on the link. A common source of problems is improper link speed specication on one of the components. Note that the link speed is specied in various places: on the EMX (DISP CCS LINKPA), in the MMs SS7 software (a7 term handler: displ-slk;), in the MMs cbsc-X.cdf le (check for C7LinkSpeed), and in the DSUs as well. All of these speed denitions must be the same for the link to align. Yet another problem which may cause link alignment failure is the point code settings on the MM and MSC. Again, the operator must make certain that the point codes have been set the same in the MSC (use DISP SCCP SSSTAT), in the MMs SS7 software (use a7 term handler: displ-ospc; and displ-dpc commands), and in the MMs cbsc-X.cdf le (check for S7Dpc, S7Opc). As part of the troubleshooting procedures, the DSUs should be re-seated. If problems persists after all the data checks out okay (point codes, link speeds, link parameters, etc.), then the DSUs should be replaced. The cables could also be replaced as a debugging step. Also, an SS7 linkset analyzer (if available) can prove to be an excellent debugging tool (most analyzers can emulate link alignment). NOTES:

Motorola Confidential Proprietary

179 of 259

Conclusions:
The SS7 communications protocol is used for communication between MM and MSC. Point codes must be dened correctly on MM and on MSC. The a7 terminal handler is used on MM to display, change, and status the SS7 sub-system on the MM. Several commands must be run on both the MM and the MSC in order to provision the SS7 links correctly. Any of a number of components in the SS7 path may be incorrectly congured or damaged. Debugging and problem isolation is used to nd the culprit for faulty SS7 links.

180 of 259

Motorola Confidential Propretary

PWID Training: CDMA

The SC9600 BTS

Motorola Confidential Proprietary

181 of 259

Objectives:
To present the SC9600 bts utilized in Supercell CDMA in detail- including architecture, hardware, and operations. To present briey the other BTS alternatives for CDMA.

182 of 259

Motorola Confidential Proprietary

Table of Contents:
The SC9600 BTS Architecture..................................................................................... BTS Operations ............................................................................................................ More BTS Operations Notes ........................................................................................ Other BTSs for CDMA ................................................................................................. 185 187 189 191

Motorola Confidential Proprietary

183 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

The SC9600 BTS Architecture

Rx
1a

Rxd
1b

...

Rxd
3b 2 1

Tx
2 3 3

Dir. Coupler

...

Dir. Coupler
6

...
1a 1b 3b 2

Cell Site Filter 1

1a 1b

...
2

...3a

3b

RFDS
(not in CDMA Trial yet)
RS485 RGLI

To other 6 RF Modem Frames

...

Multicoupler
3 3

...

Alarms

SITE INTERFACE FRAME

LPA
1 2 3

Preselector
6 6

Preselector / Splitter

LPA FRAME
LCI

Preselector I/O
3 3 3 3 3 3 3 3

Tx Combiner
3 3 3 3

To MIOs of other CCP shelves

Timing and Synchronization

Clk/Sync

MIO Rx
1a

MIO Tx
3b 3 ... R

From MIOs of other CCP shelves

... 3a 1b
BBX

1 3

RS485

LFR
RS232 R Clk/Sync P

GPS

1a,b I,Q 4

...3a,b I,Q ...

BDC
1a,b..3a,b I,Q 12 Rx/Rxd
Clk/Sync

CSM
AMR BUS (RS485)

Customer Alarms
P R

12

Tx 1

MCC MCC Bus GLI

...
R

20

AMR

Ethernet

(SCAP/TCP/IP)

AMR BUS (RS485)

ISB = primary = redundant To other GLIs in same frame T1

CCP Shelf
To LMF P R To other GLIs in other RF Modem Frames

MSIO
Note: CDMA Trial will not use RFDS 3-sector system shown, Assumes Tx & Rx non-shared antennas Trial system will use omni xmit & rcv (i.e.: 2 rcv, 1 xmit antenna) In Trial System, MIO Tx outputs will be routed directly to (NAMPS) LPAs T1/E1 To/From CBSC

T1/E1 To/From other BTS

184 of 259

Motorola Confidential Proprietary

AMR BUS (RS485)

RF MODEM FRAME
Ethernet

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

The SC9600 BTS Architecture In this diagram we present the internal connectivity of the BTS, including RF and Baseband signal ow.
Note the demarcations for each of the frames: SIF frame on the top, LPA frame in the middle right, RF Modem Frame on the bottom. The SIF frame presents all the RF interfaces to the RFMF on the Rx path. Note that the RFDS uses the directional coupler in order to test Tx and Rx paths at the BTS. The RFDS is not currently available for CDMA. From the Multicouplers, the Rx RF signal is fed to the RFMF. The RF signal is delivered to the BBX cards (one per CDMA sector). The BBX cards perform all the up-conversion and down-conversion. The baseband signals from the receive antennas are then fed to the BDC card, which will perform antenna diversity functions to select the best signal, and it will remove the Pn offset for the particular cell or sector. The resulting signal is forwarded to the MCC cards. The MCC cards will be directed by the MM to listen for particular coded conversations on the reverse link (Rx path), and the de-coded conversation will be sent to the XC via the GLI and MSIO cards through a T1 or E1 interface. On the transmit path, the information to be sent will be received from the XC through the T1 or E1 interface, through the MSIO and GLI cards, and picked up from the MCC bus by the MCC card which has been assigned to the particular conversation being transmitted. The MCC card will code the conversation so that it can be mixed with all other conversations and still be de-coded by the mobile (Spread-Spectrum spreading with a particular Walsh code), and the resulting signal will be sent to the BDC. The BDC will combine all signals being transmitted from all MCC cards, and place the Pn offset for the cell or sector on the combined digital signal. This signal is then fed to the BBX. The BBX will up-convert the digital signal to RF, and send the resulting RF signal to the LPA frame where it will be amplied and sent to the SIF for transmission on the Tx antennas.

NOTES:

Motorola Confidential Proprietary

185 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

BTS Operations
Linear Power Amplier Frame RF Modem Frame Site Interface Frame

Optimization- See guide by TED. LMF is a Unix-based platform.

- Presents a CLI interface. - Allows opeator to download code, data to BTS devices. - Allows operator to optimize BTS through automated scripts (see notes on Ksh on page 92). - Use Ethernet tips & tricks on page 244 when LMF cant ping the GLI.

GLI has an MMI interface at which commands may be entered for troubleshooting.

186 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

BTS Operations Very good material is available from TED on installing the BTS, and on optimizing the BTS- therefore we will not go into these topics. However, the following points are presented on the LMF and on the BTS devices:
The LMF is a unix-based (Sun Solaris) laptop. Many of the tips & tricks for Unix may be used on the LMF. In particular, many times the LMF cannot login to the BTS. When this occurs, try to ping the GLI (look in the /etc/hosts le to nd the GLIs address). If the GLI has no address in the /etc/hosts table on the LMF, then lookup the GLIs address by connecting an MMI cable to its front-panel RS-232 port to the LMFs serial port. Press <esc><return> to obtain the RT> prompt. At this prompt, enter cong, and this should print the IP address of the GLI. Enter this IP address into the /etc/hosts le on the LMF. Then the LMF should be able to ping the GLI, and the LMF application should initialize okay. When problems are suspected at the GLI (E1 link coming in/out of service, for example), connect a terminal to the MMI port of the GLI, and enter the following commands (make sure to capture the output from the commands in a le on the terminal):
RT> RT> RT> RT> RT> RT> RT> RT> RT> RT> RT? printf on <ret> status <ret> <esc> <esc> crashp 80 80 80 rd_path 1 (notice the output when you see .... rd_link X (get X from last command) config scap_addr dpll <esc><ret> lapd_stat 0 <ret><esc><ret> dmsg 50<ret) printf off

Link ID=X .... )

Another usefull troubleshooting command for the GLI is:

RT> lstat <ret><esc>

This command shows all the device the GLI sees on the LAN. The GLI will be able to communicate with the device if the Conn eld says CONN, and the State eld is OK. The ping command may be used at the GLI in order to see if the GLI can see the MM: ping 128 0 0 0 0. The dmsg command will print the last <n> messages. After a ping, you should see a message type 3600 (ping), followed by a message type 3602 (ping response). NOTES:

Motorola Confidential Proprietary

187 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

More BTS Operations Notes

Linear Power Amplier Frame RF Modem Frame Site Interface Frame

Resetting a GLI remotely (used when comm link to MM is down). Checking span line information (use span_view command at GLIs MMI). Changing GLIs IP address.

188 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

More BTS Operations Notes

Resetting the GLI: Dial into the BTS through a cu command at the OMC-R, or through a ProComm (or similar) package on a PC with a modem. A CONNECT mesage will be seen, followed by several numbers (ignore the numbers). Type the <esc> key, followed by <return> key to get the RT scope prompt (RT>). Use the status command to get the status of the GLI. If GLI has cage control, enter sndtype 16387 <ret> <esc>(16387d = 4003h = SCAP message for OOS_RAM). If not, enter send 0 0 128 48 255 16387 <ret><esc>. The '128 48 255 is the decimal representation of the SCAP address for the GLI, the GLI in the bottem cage = 48 and in the top cage = 47. Now check the status of the LAN connections with the lstat command. Notice that a column labeled CTL is decoded as follows: B - INS_STANDBY, A INS_ACTIVE, 3 - OOSROM, 4 - OOSRAM. If the GLI state is OOSROM, do the following:
RT> cmd; set 40004ecc A number will be displayed, after RT> ping 0 0 128 48 255 (this RT> cmd; set 40004ecc A number will be displayed, after displayed the first time followed this number type: 4003. <ret> will reboot the GLI) this number type the original number that was by .<ret>

To check span conguration at the GLI, try this command (example output shown):
RT>span_view Span Type = T1_3 Span Rate = 56 Span A Type = T1 long haul Span B Type = T1 long haul Lapd slot for Span A = 0 Lapd slot for Span B = 0

To change the GLIs IP address from 128.0.0.2 to 136.182.108.51:

> > > > > > > > > > > > RT>cmd RC>set.b 04000006 04000006 04000007 04000007 04000008 04000008 04000009 04000009 0400000A RC>go 04000006 80 ? 88 08 00 ? b6 36 00 ? 6c AC 02 ? 33 B3 00 ? .

NOTES:

Motorola Confidential Proprietary

189 of 259

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

Other BTSs for CDMA

SC600 SC4850
Naming Conventions:
- Four digits used, rst omitted when no narrowband channels included. - When four digits used, rst two digits indicate # of narrow-band transceivers. - Third digit will be 2 for CDMA-only, 5 for mixed.

SC2450

SC4850
- 48 NAMPS channels, 1.9 GHz, 108 CDMA chnls.

SC600
- No NAMPS channels, 36 CDMA chnls.

SC2450
- 24 AMPS/NAMPS channels, 800/900 MHz, 108 CDMA chnls.
190 of 259 Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

The SC9600 BTS

Other BTSs for CDMA

The naming convention for BTSs in CDMA is dened as follows. A series is a BTS type which can have several options. A series is identied with four digits. Those series which do not include narrow band transceivers have only three digits (i.e. SC 600). A series which includes narrow band transcievers has four digits (i.e. SC9600). The third digit with be a 2 if a CDMA-only BTS, 5 if its a mixed CDMA-analog BTS. The fourth digit will be used if necessary in the future for major product variations. The SC4850 BTS for CDMA is a 1.9 GHz-only system, capable of providing CDMA and NAMPS air interfaces. Input voltage is +27 VDC. Dimensions are 2100mm height, 800mm width, 600mm depth. Maximum weight is 430 kg (950lbs). Capacity is 48 analog (NAMPS) transceivers, and 2 CDMA carriers of 3 sectors each. Using 18 CDMA channels per sector (practical maximum determined through eld trials), this gives 108 CDMA channels. The SC2450 BTS (currently called the SC2400) provides AMPS/NAMPS/CDMA air interfaces at 800 or 900 MHz ranges. Input voltage is +27 VDC. Dimensions are 2100mm height, 800mm width, 600mm depth. Maximum weight is 636 kg (1400lbs). Capacity is 24 analog (AMPS or NAMPS) channels, and 2 CDMA carriers of 3 sectors each, giving 108 CDMA channels. The SC600 BTS is a CDMA-only BTS designed for easy instllation outdoors. It is a selfcontained, convection-cooled unit. An SC600 can support one Omni site with 36 CDMA channels (maximum). The SC600 can be expanded with other SC600 units (stacked on top of each other) to provide a maximum of 108 CDMA channels. With the exception of the SC600, all BTSs will have (sometime in the future) an option for a Radio Frequency Diagnostic System (RFDS), which is being developed in Ft. Worth.

NOTES:

Motorola Confidential Proprietary

191 of 259

Conclusions:
The SC9600 is a three-frame BTS, composed of the RF Modem Frame, LPA Frame, and Site Interface Frame. The BBX is the demarcation point for the RF path. The GLI handles T1/E1 termination, acts as the sites controller. The BTS is designed such that fault tolerance is provided for those elements which could malfunction in time. The LMF allows an operator to login to the GLI, and use a CLI to input enable/disable commands and other commands to optimize the site. The GLI uses Motorolas EXEC environment, which presents a prompt at which several commands may be input for debugging/maintenance functions. The GLI may be reset remotely via a modem to the site.

192 of 259

Motorola Confidential Propretary

PWID Training: CDMA

Output from Work Sessions

Motorola Confidential Proprietary

193 of 259

Objectives:
Present example ows from initializations, in order to familiarize the reader with the sequence of events.

194 of 259

Motorola Confidential Proprietary

Table of Contents:
Sample Output: Unix Initialization ............................................................................. Sample Output: Unix Initialization (Continued), SCSIIM Initialization .................. Sample Output: SCSIIM Initialization (Continued)................................................... Sample Output: Enable CBSC..................................................................................... Sample Output: Enable CBSC (Continued)................................................................ Sample Output: Enable CBSC (Continued)................................................................ Sample Output: Enable CBSC (Continued), BTS Enable.......................................... Sample Output: BTS Enable........................................................................................ Sample Output: BTS Enable........................................................................................ 196 198 199 200 201 202 203 204 205

Motorola Confidential Proprietary

195 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

Sample Output: Unix Initialization

Cabinet configuration: Central Office Identified Interphase Ethernet Controller in Identified Interphase Ethernet Controller in Identified Interphase SCSI controller in iop Identified Interphase SCSI controller in iop Identified Interphase SCSI controller in iop Identified Interphase SCSI controller in iop Identified Interphase Ethernet Controller in Identified Interphase Ethernet Controller in Identified Interphase Ethernet Controller in Identified Interphase Ethernet Controller in Identified Interphase Ethernet Controller in Identified Interphase Ethernet Controller in slot0: initialization succeeded slot1: initialization succeeded slot1: disk0 disk3 tape4 online slot2: initialization succeeded slot2: tape0 disk1 disk5 online slot3: initialization succeeded slot5: initialization succeeded slot7: initialization succeeded iop 0, slot iop 1, slot 0, slot 1 1, slot 1 0, slot 2 1, slot 2 iop 0, slot iop 1, slot iop 0, slot iop 1, slot iop 0, slot iop 1, slot 0 0

3 3 5 5 7 7

CPU Proms - t7437A14 - Fri Nov 05 13:23:02 CDT 1993 Hit space within 10 seconds to interrupt rcboot sequence: Initiating rcboot could not load disk(1,0,6) could not load disk(2,1,6) loading file disk(1,0,5)unix 2349616+390992+1116272 text entry:0x80031000, start: 0x80031000, end:0x8026ea2f data start:0x8026ea30, end:0x802ce17f bss start:0x802ce180, end:0x803de9ef CPU: MIPS/R4400 Processor Chip Revision: 5.0 FPU: MIPS/R4400 Floating Point Coprocessor Revision: 0.0 consattr=19200,8,n,1,n 2boot_end=135266304 red_zone_end=138412031 Iop0: IOP is present (inserted) Iop1: IOP is present (inserted) cpu: cpua,cpub,cpuc 64MB local memory tmrc: tmrca,tmrcc[Primary] 16MB (base 0xa8000000) iop: iop0,iop1 mlsetup: initializing memory Delay multiplier = 27, cnt = 59 mlsetup: reintegration diagnostic save area, size 4096 bytes, at a8fff000 Event log driver initialized NonStop-UX SVR4.0 -- Seq: 4 -- root -- Tue Mar 19 23:28:32 GMT 1996 UNIX(R) System V Release 4.0 AT&T Version B32 Total real memory = 82837504 (20224 pages) Root on dev 5/0 Swap on dev 5/0, 32768K bytes total real memory = 82837504 total available memory = 76259328 Identified Interphase Ethernet Controller in iop 0, slot 0 Identified Interphase Ethernet Controller in iop 1, slot 0 Identified Interphase SCSI controller in iop 0, slot 1 Identified Interphase SCSI controller in iop 1, slot 1 Identified Interphase SCSI controller in iop 0, slot 2 Identified Interphase SCSI controller in iop 1, slot 2 Identified Interphase Ethernet Controller in iop 0, slot 3 Identified Interphase Ethernet Controller in iop 1, slot 3 Identified Macrolink async board, serial #390 in iop 0, slot 4 Identified Macrolink async board, serial #390 in iop 1, slot 4 Identified Interphase Ethernet Controller in iop 0, slot 5 Identified Interphase Ethernet Controller in iop 1, slot 5 Identified Interphase Ethernet Controller in iop 0, slot 7 Identified Interphase Ethernet Controller in iop 1, slot 7 Jaguar Version (077-34-01N) Date 01271992 with 126 Kbytes ram. Port0: Single Ended Port1: None

196 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

scsi0: initialization succeeded

Revision 0, 4/24/97

Output from Work Sessions

Sample Output: Unix Initialization (continued)

scsi0 unit0: unit online scsi0 unit3: unit online scsi0 unit4: unit online Async0: Initialization Completed Jaguar Version (077-34-01N) Date 01271992 with 126 Kbytes ram. Port0: Single Ended Port1: None scsi1: initialization succeeded scsi1 unit0: unit online scsi1 unit1: unit online scsi1 unit5: unit online OSI/TCP Application Facility Release 1.0 IO subsystem initialization complete. Volume Manager started Starting root volume... Done log replay in progress replay complete - marking super block as CLEAN Switching to root volume fsgen/volume: Volume cdl: log read from plex cdl-0 failed: No such device or address fsgen/volume: Volume cdl: log read from plex cdl-1 failed: No such device or address fsgen/volume: Volume cdl: No valid logs were found fsgen/volume: Volume cdl: Cannot reconcile logs, volume not started Node: rpomcr Checking for new unix kernel keepalive daemon started System V STREAMS TCP Release 1.0 (c) 1983,1984,1985,1986,1987,1988,1989 AT&T. (c) 1986,1987,1988,1989 Sun Microsystems. (c) 1987,1988,1989 Lachman Associates, Inc. (LAI). All Rights Reserved. adding daemon /usr/sbin/rpcbind (pid 92) respawn /etc/keepalive.d/rpcbind adding daemon /usr/sbin/inetd (pid 93) respawn /etc/keepalive.d/inetd adding daemon /usr/bin/ism/configd (pid 99) respawn /etc/keepalive.d/configd adding daemon /usr/bin/ism/evlogd (pid 98) respawn /etc/keepalive.d/evlogd adding daemon /usr/sbin/sproute (pid 120) respawn /etc/keepalive.d/sproute adding daemon /usr/mds/midas (pid 149) respawn /etc/mdsinit adding daemon /usr/sbin/syslogd (pid 154) respawn /etc/keepalive.d/syslog The system is going into fast multi-user mode. Please wait. vxfs mount: warning: <> mounted as </sc> vxfs mount: warning: <> mounted as </screl> vxfs mount: warning: <> mounted as </home> /sbin/spawndaemon: daemon /usr/sbin/sproute is already executing /sbin/spawndaemon: daemon /usr/sbin/inetd is already executing adding daemon /usr/sbin/tp0d (pid 238) respawn /etc/keepalive.d/tp0d K: tp0open called Mar 19 23:38:28 1996: MIDAS: Boot has occurred. Async0: Ready /sbin/mvcload: Option -i board information: Firmware part number: 450146 Firmware revision: 4.0 Board address: 0x0 Number of lines: 16 Printer port available: YES Amount of FIFO memory: 66K (0x10800) Nvram message: PN221200RB1#390

NOTES:

Motorola Confidential Proprietary

197 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

The system is ready. Sample Output: Unix Initialization (Continued), SCSIIM Initialization Beginning background state 4 processing Checking for system core dump. Saving the system core dump (if present) will be done in the background. 298 keepalive daemon restarted

rpomcr Welcome to the Tandem S2 UNIX System Console Login: could not find daemon /sbin/vold (pid=0) to delete. Wed Mar 20 21:41:59 1996 rpmm1 PID: 316 scsiim: scsiim process started at time: Wed Mar 20 21:41:59 1996 Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: initLevel=2 scsiim: initForced=0 Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: This platform is an MM, with platform number: 1 Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: Warning: CDF file has no RESOURCES::MutexLocks field. Defaulting to creating 150 locks and 10 buckets Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: Warning: Preserve item in CDF file is empty or not present. Defaulting to false. Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: Warning: Preserve item in CDF file is empty or not present. Defaulting to false. Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: Type for shared memory segment SC_DEVOM_CDF has been specified as MMAP Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: Warning: Preserve item in CDF file is empty or not present. Defaulting to false. Wed Mar 20 21:42:00 1996 rpmm1 PID: 316 scsiim: Warning: Preserve item in CDF file is empty or not present. Defaulting to false. Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: SyslogdRefresh Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: SyslogdRefresh instantiated. Pid: 2618 Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: popper Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: popper instantiated. Pid: 2619 Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: MonitorAPI Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: MonitorAPI instantiated. Pid: 2620 Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: scemlogd Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: scemlogd instantiated. Pid: 2621 Wed Mar 20 21:42:02 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: mmgw Wed Mar 20 21:42:03 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: mmgw instantiated. Pid: 2622 Wed Mar 20 21:42:03 1996 rpmm1 PID: 316 scsiim: Pausing for an additional 10 seconds after mmgw Wed Mar 20 21:42:03 1996 rpmm1 PID: 316 scsiim: Pausing for an additional 10 seconds after mmgw Wed Mar 20 21:42:13 1996 rpmm1 PID: 316 scsiim: Pausing for an additional 1 seconds after mmgw Wed Mar 20 21:42:14 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: scevmgr Wed Mar 20 21:42:14 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: scevmgr instantiated. Pid: 2727 Wed Mar 20 21:42:14 1996 rpmm1 PID: 316 scsiim: Pausing for an additional 3 seconds after scevmgr Wed Mar 20 21:42:17 1996 rpmm1 PID: 316 scsiim: Pausing for an additional 1 seconds after scevmgr Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: sec_mgmt Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: sec_mgmt instantiated. Pid: 2766 Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: vdt_1 Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: vdt_1 instantiated. Pid: 2767 Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: vdt_2 Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: vdt_2 instantiated. Pid: 2768 Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: mm_slm Wed Mar 20 21:42:18 1996 rpmm1 PID: 316 scsiim: Checking lockstep for process: mm_slm Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: lockstep process: mm_slm brought up successfully. Pid: 2769 Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: dgen Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: dgen instantiated. Pid: 2773 Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: dd Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: dd instantiated. Pid: 2774 Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: scdb Wed Mar 20 21:42:23 1996 rpmm1 PID: 316 scsiim: Checking lockstep for process: scdb Wed Mar 20 21:42:39 1996 rpmm1 PID: 316 scsiim: lockstep process: scdb brought up successfully. Pid: 2775 Wed Mar 20 21:42:39 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: sc_devom Wed Mar 20 21:42:39 1996 rpmm1 PID: 316 scsiim: Checking lockstep for process: sc_devom Wed Mar 20 21:43:14 1996 rpmm1 PID: 316 scsiim: lockstep process: sc_devom brought up successfully. Pid: 2780 Wed Mar 20 21:43:14 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: mmtadadm Wed Mar 20 21:43:14 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: mmtadadm instantiated. Pid: 2782 Wed Mar 20 21:43:14 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: cpmo Wed Mar 20 21:43:14 1996 rpmm1 PID: 316 scsiim: Checking lockstep for process: cpmo Wed Mar 20 21:43:20 1996 rpmm1 PID: 316 scsiim: lockstep process: cpmo brought up successfully. Pid: 2783 Wed Mar 20 21:43:20 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: callproc1 Wed Mar 20 21:43:20 1996 rpmm1 PID: 316 scsiim: Non-lockstep process: callproc1 instantiated. Pid:

198 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

2785

Revision 0, 4/24/97

Output from Work Sessions

Sample Output: SCSIIM Initialization (Continued)

Wed Mar 20 21:43:20 Wed Mar 20 21:43:20 Wed Mar 20 21:43:20 Wed Mar 20 21:43:20 Wed Mar 20 21:43:20 as specified in CDF Wed Mar 20 21:43:20 indication. 1996 rpmm1 1996 rpmm1 1996 rpmm1 1996 rpmm1 1996 rpmm1 file. 1996 rpmm1 PID: 316 scsiim: Attempting to spawn process: clcp PID: 316 scsiim: Non-lockstep process: clcp instantiated. Pid: 2786 PID: 316 scsiim: Attempting to spawn process: fepMon PID: 316 scsiim: Non-lockstep process: fepMon instantiated. Pid: 2787 PID: 316 scsiim: scsiim has finished attempting to bring up processes PID: 316 scsiim: scsiim of pid: 316 is pausing, waiting for INIT

NOTES:

Motorola Confidential Proprietary

199 of 259

PWID Center for Excellence

rpmm1-010012 > enable cbsc-1 unc Sample Output: Enable CBSC

Revision 0, 4/24/97

Output from Work Sessions

010012-00003 COMMAND ACCEPTED CLICMD-5179 96-03-16 16:58:03 rpmm1 MM-1 M010012.00003 000062/000062 INFO:1 Command Received and Accepted COMMAND=ENABLE cbsc-1 unc CBSC-1 96-03-16 16:58:03 rpmm1 MM-1 M010012.00003 000063/000063 INFO:3 Command in Progress STATUS=STARTED CBSC-1 96-03-16 16:58:03 rpmm1 MM-1 M010012.00003 000064/000064 STCHG:1 State Change Event OLDSTATE=OOS_MANUAL PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=START CBSC-1 96-03-16 16:58:03 rpmm1 MM-1 M010012.00003 000065/000065 STCHG:1 State Change Event OLDSTATE=INS PROCEDURE=INITIALIZE NEWSTATE=OOS_AUTOMATIC ACTION=FINISH CBSC-1 96-03-16 16:58:03 rpmm1 MM-1 M010012.00003 000066/000066 INFO:5 Command Failed REASON_CODE=Primary FEPs Not INS rpmm1-010012 > enable fepr-1-1-1 unc 010012-00004 COMMAND ACCEPTED CLICMD-5180 96-03-16 16:58:13 rpmm1 MM-1 M010012.00004 000067/000067 INFO:1 Command Received and Accepted COMMAND=ENABLE fepr-1-1-1 unc FEPR-1-1-1 96-03-16 16:58:13 rpmm1 MM-1 M010012.00004 000068/000068 INFO:3 Command in Progress STATUS=STARTED FEPR-1-1-1 96-03-16 16:58:13 rpmm1 MM-1 M010012.00004 000069/000069 STCHG:1 State Change Event OLDSTATE=OOS_MANUAL PROCEDURE=NONE NEWSTATE=OOS_PARENT ACTION=NOCHANGE FEPR-1-1-1 96-03-16 16:58:13 rpmm1 MM-1 M010012.00004 000070/000070 INFO:5 Command Failed REASON_CODE=Parent Device In Improper State rpmm1-010012 > status cbsc-1 010012-00005 COMMAND ACCEPTED CBSC-1 96-03-16 16:58:21 rpmm1 MM-1 D010012.00005 000071/000071 INFO:3 Command in Progress STATUS=STARTED CBSC-1 072 INFO:2 Device Status Response TELSTATE=OOS_AUTOMATIC PROCEDURE=NONE PHYSTATE=NONE rpmm1-010012 > load fep1 -1-1-2 010012-00006 COMMAND ACCEPTED CLICMD-5182 96-03-16 16:58:31 rpmm1 MM-1 M010012.00006 000073/000073 INFO:1 Command Received and Accepted COMMAND=LOAD fep-1-1-2 FEP-1-1-2 96-03-16 16:58:31 rpmm1 MM-1 M010012.00006 000074/000074 INFO:3 Command in Progress STATUS=QUEUED FEP-1-1-2 96-03-16 16:58:31 rpmm1 MM-1 M010012.00006 000075/000075 PROC:1 Procedural State Change Event PROCEDURE=QUEUED_TO_DOWNLOAD TELSTATE=OOS_MANUAL ACTION=START FEP-1-1-2 96-03-16 16:58:31 rpmm1 MM-1 M010012.00006 000076/000076 INFO:3 Command in Progress STATUS=STARTED FEP-1-1-2 96-03-16 16:58:31 rpmm1 MM-1 M010012.00006 000077/000077 PROC:1 Procedural State Change Event PROCEDURE=QUEUED_TO_DOWNLOAD TELSTATE=OOS_MANUAL ACTION=FINISH 96-03-16 16:58:21 rpmm1 MM-1 D010012.00005 000072/000

200 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

Sample Output: Enable CBSC (Continued)

FEP-1-1-2 96-03-16 16:58:31 rpmm1 MM-1 M010012.00006 000078/000078 PROC:1 Procedural State Change Event PROCEDURE=DOWNLOAD ACTION=START TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:01:31 rpmm1 MM-1 M010012.00006 000079/000079 PROC:1 Procedural State Change Event PROCEDURE=DOWNLOAD ACTION=FINISH TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:01:31 rpmm1 MM-1 M010012.00006 000080/000080 INFO:4 Command Successfully Completed REASON_CODE=No Reason rpmm1-010012 > enable cbsc-1 unc 010012-00007 COMMAND ACCEPTED CLICMD-5200 96-03-16 17:03:00 rpmm1 MM-1 M010012.00007 000081/000081 INFO:1 Command Received and Accepted COMMAND=ENABLE cbsc-1 unc CBSC-1 96-03-16 17:03:00 rpmm1 MM-1 M010012.00007 000082/000082 INFO:3 Command in Progress STATUS=STARTED CBSC-1 96-03-16 17:03:00 rpmm1 MM-1 M010012.00007 000083/000083 STCHG:1 State Change Event OLDSTATE=OOS_AUTOMATIC PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=START FEP-1-1-2 96-03-16 17:03:00 rpmm1 MM-1 M010012.00007 000084/000084 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:03:00 rpmm1 MM-1 M010012.00007 000086/000086 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=CANCELLED TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:03:00 rpmm1 MM-1 M010012.00007 000087/000087 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=START TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:03:11 rpmm1 MM-1 M010012.00007 000090/000090 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=FINISH TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:03:11 rpmm1 MM-1 M010012.00007 000091/000091 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_AUTOMATIC FEP-1-1-2 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000092/000092 STCHG:1 State Change Event OLDSTATE=OOS_AUTOMATIC PROCEDURE=NONE NEWSTATE=INS_ACTIVE ACTION=NOCHANGE XCLINK-1-1-2-1 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000093/000093 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=FINISH CPP-1-1-1 PROC:1 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000094/000094 Procedural State Change Event

NOTES:

Motorola Confidential Proprietary

201 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT Sample Output: Enable CBSC (Continued) CPP-1-1-1 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000096/000096 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=FINISH XCLINK-1-1-2-2 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000097/000097 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=FINISH FEP-1-1-2 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000098/000098 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS_ACTIVE FEPR-1-1-1 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000099/000099 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT FEPR-1-1-1 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000102/000102 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=CANCELLED TELSTATE=OOS_PARENT FEPR-1-1-1 96-03-16 17:03:12 rpmm1 MM-1 M010012.00007 000103/000103 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=START TELSTATE=OOS_PARENT FEPR-1-1-1 96-03-16 17:03:23 rpmm1 MM-1 M010012.00007 000105/000105 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=FINISH TELSTATE=OOS_PARENT FEPR-1-1-1 96-03-16 17:03:23 rpmm1 MM-1 M010012.00007 000106/000106 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT FEPR-1-1-1 96-03-16 17:03:24 rpmm1 MM-1 M010012.00007 000107/000107 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=NONE NEWSTATE=INS_STANDBY ACTION=NOCHANGE XCLINK-1-1-1-1 96-03-16 17:03:24 rpmm1 MM-1 M010012.00007 000108/000108 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=FINISH FEPR-1-1-1 96-03-16 17:03:24 rpmm1 MM-1 M010012.00007 000109/000109 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS_STANDBY MSC-1 96-03-16 17:03:30 rpmm1 MM-1 M010012.00007 000111/000111 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT C7LINK-1-1-1 96-03-16 17:03:30 rpmm1 MM-1 M010012.00007 000113/000113 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=FINISH MSC-1 96-03-16 17:03:30 rpmm1 MM-1 M010012.00007 000114/000114 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=NONE NEWSTATE=INS ACTION=NOCHANGE rpmm1-010005 > enable bts-52 unc 010005-00014 COMMAND ACCEPTED CLICMD-2340 96-03-20 20:40:26 rpmm1 MM-1 M010005.00014 000231/000231 INFO:1 Command Received and Accepted COMMAND=ENABLE bts-52 unc BTS-52 96-03-20 20:40:26 rpmm1 MM-1 M010005.00014 000232/000232 INFO:3 Command in Progress STATUS=STARTED BTS-52 PROC:1 96-03-20 20:40:26 rpmm1 MM-1 M010005.00014 000233/000233 Procedural State Change Event

202 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_MANUAL Sample Output: Enable CBSC (Continued), BTS Enable

BTSLINK-52-1 96-03-20 20:40:26 rpmm1 MM-1 M010005.00014 000235/000235 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT BTSLINK-52-1 96-03-20 20:40:26 rpmm1 MM-1 M010005.00014 000236/000236 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=NONE NEWSTATE=INS ACTION=NOCHANGE BTSLINK-52-1 96-03-20 20:40:26 rpmm1 MM-1 M010005.00014 000237/000237 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS MGLI-52-1 96-03-20 20:40:41 rpmm1 MM-1 M010005.00014 000238/000238 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_MANUAL MGLI-52-1 96-03-20 20:40:41 rpmm1 MM-1 M010005.00014 000240/000240 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=CANCELLED TELSTATE=OOS_MANUAL MGLI-52-1 96-03-20 20:40:41 rpmm1 MM-1 M010005.00014 000241/000241 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=START TELSTATE=OOS_MANUAL MGLI-52-1 96-03-20 20:40:51 rpmm1 MM-1 M010005.00014 000243/000243 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=FINISH TELSTATE=OOS_MANUAL MGLI-52-1 96-03-20 20:40:51 rpmm1 MM-1 M010005.00014 000244/000244 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_MANUAL MGLI-52-1 96-03-20 20:40:56 rpmm1 MM-1 M010005.00014 000245/000245 STCHG:1 State Change Event OLDSTATE=OOS_MANUAL PROCEDURE=NONE NEWSTATE=INS_ACTIVE ACTION=NOCHANGE CSM-52-1 96-03-20 20:41:04 rpmm1 MM-1 M010005.00014 000246/000246 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT LCI-52-1 96-03-20 20:44:56 rpmm1 MM-1 M010005.00012 000250/000250 PROC:1 Procedural State Change Event PROCEDURE=DOWNLOAD ACTION=FINISH TELSTATE=OOS_AUTOMATIC CSM-52-1 96-03-20 20:45:53 rpmm1 MM-1 M010005.00014 000251/000251 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=INS_ACTIVE ACTION=START CSM-52-1 96-03-20 20:45:53 rpmm1 MM-1 M010005.00014 000252/000252 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS_ACTIVE LCI-52-1 96-03-20 20:45:54 rpmm1 MM-1 M010005.00014 000253/000253 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_AUTOMATIC

NOTES:

Motorola Confidential Proprietary

203 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

Sample Output: BTS Enable

LCI-52-1 96-03-20 20:46:04 rpmm1 MM-1 M010005.00014 000255/000255 STCHG:1 State Change Event OLDSTATE=OOS_AUTOMATIC PROCEDURE=NONE NEWSTATE=INS_ACTIVE ACTION=FINISH LCI-52-1 96-03-20 20:46:04 rpmm1 MM-1 M010005.00014 000256/000256 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS_ACTIVE BDC-52-1 96-03-20 20:46:04 rpmm1 MM-1 M010005.00014 000257/000257 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT BDC-52-1 96-03-20 20:46:04 rpmm1 MM-1 M010005.00014 000259/000259 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=CANCELLED TELSTATE=OOS_PARENT BDC-52-1 96-03-20 20:46:04 rpmm1 MM-1 M010005.00014 000260/000260 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=START TELSTATE=OOS_PARENT BDC-52-1 96-03-20 20:46:16 rpmm1 MM-1 M010005.00014 000261/000261 PROC:1 Procedural State Change Event PROCEDURE=DATALOAD ACTION=FINISH TELSTATE=OOS_PARENT BDC-52-1 96-03-20 20:46:16 rpmm1 MM-1 M010005.00014 000262/000262 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT BDC-52-1 96-03-20 20:46:17 rpmm1 MM-1 M010005.00014 000263/000263 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=NONE NEWSTATE=INS_ACTIVE ACTION=NOCHANGE BDC-52-1 96-03-20 20:46:17 rpmm1 MM-1 M010005.00014 000264/000264 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS_ACTIVE BBX-52-1 96-03-20 20:46:17 rpmm1 MM-1 M010005.00014 000265/000265 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=START TELSTATE=OOS_PARENT BBX-52-1 96-03-20 20:46:22 rpmm1 MM-1 M010005.00014 000267/000267 STCHG:1 State Change Event OLDSTATE=OOS_PARENT PROCEDURE=INITIALIZE NEWSTATE=OOS_AUTOMATIC ACTION=FINISH MGLI-52-1 96-03-20 20:46:22 rpmm1 MM-1 M010005.00014 000268/000268 PROC:1 Procedural State Change Event PROCEDURE=INITIALIZE ACTION=FINISH TELSTATE=INS_ACTIVE BTS-52 96-03-20 20:46:22 rpmm1 MM-1 M010005.00014 000269/000269 STCHG:1 State Change Event OLDSTATE=OOS_MANUAL PROCEDURE=INITIALIZE NEWSTATE=INS ACTION=FINISH

BTS-52 96-03-20 20:46:22 rpmm1 MM-1 M010005.00014 000270/000270 INFO:4 Command Successfully Completed REASON_CODE=No Reason rpmm1-010005 > rpmm1-010005 >

204 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

Page intentionally BTS Enable for notes). Sample Output: left blank (use

NOTES:

Motorola Confidential Proprietary

205 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Output from Work Sessions

206 of 259

Motorola Confidential Proprietary

PWID Training: CDMA

CDMA Call Processing

Motorola Confidential Proprietary

207 of 259

Objectives:
To present CDMA call processing in detail, from the perspective of actual message ow through the various devices in the network.

208 of 259

Motorola Confidential Proprietary

Table of Contents:
Call Processing Functionality Split ............................................................................. 211 Observing CDMA Call Processing at the MM ............................................................ 213 Call Processing Flows- General................................................................................... 215 Call Flow: Mobile Termination.....................................................................................223 Call Flow: Mobile Registration.....................................................................................226 Hand-Offs in CDMA .................................................................................................... 229 Call Flow: Soft Hand-Off Add Success ........................................................................230 Looking at SCAP and A+ Messages ............................................................................ 235

Motorola Confidential Proprietary

209 of 259

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Call Processing Functionality Split

PSTN Interface Handoff Arbitration Feature Control Tone Insertion Number Translation Billing Subscriber Data Base Trunk Management

MSC
E1- 30 PCM A+/SS7 Resource Allocation (TCH) Dynamic Equipment Sharing Handoff Control Call Model Access Threshold Priority Access

CBSC
SCAP/LAP-D

Signal Quality Measurements Layer 2 Protocols Power Change Management Handoff Measurements C/I & MRI Reporting MAHO integration

E1- 29 DS0s x 4 tch/DS0 = 116 tch/E1

BTS
IS-95 Air Interface Spec. MS

Functions in Real Time category left at BTS. Background functions at CBSC. High volume transactions were left at cell site due to bandwidth demands. Review of interfaces used:
SCAP/LAP-D over DS0 for control of BTS. STRAU over DS0 for trafc channels of BTS. A+/SS7 over V.35 or DS0 for MSC, CBSC control. PCM over DS0 for trafc channels to/from MSC.

210 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Call Processing Functionality Split

Supercell takes much functionality away from the MSC, as compared to the functionality assigned to the MSC in typical analog systems. The CGM (Cell Group Manager) on an EMX acting as an MSC no longer performs any work. (However, the EMX will not initialize properly if the CGM is not in place, so the EMX still has the CGM present). The MSC holds the subscriber database, performs hand-off arbitration on inter-cbsc and inter-system hand-offs (hard hand-offs), provides the interface to the PSTN (both trafc and signaling trunks), performs number translations, and is the central repository for billing information. The CBSC is responsible for allocating resources in the system which are needed for performing call processing. These resources include MCCCE (Channel elements in an MCC), and connections through the XCs KSW card for timeslots coming from MCCCEs to the proper XCDR card which will have a TERCKT assigned to it. The MM handles hand-offs for BTSs that it controls, and it acts as the controlling agent for hard hand-offs which originate in its BTSs. In addition, it implements call processing features such as Access Threshold and Priority Access. The MM also handles dynamic equipment sharing- allocating free devices from a pool of available resources. The BTS handles the more time-critical functions which could not be handled by the CBSC due to delays in transmission and processing at the CBSC. These functions include power control, hand-off measurements, and signal quality measurements, among others. Reviewing the interfaces: IS-95 Air Interface is used over an RF carrier from the BTS. SCAP (Supercell Application Protocol) is used over a LAP-D transport for control information at 64 Kbps to the BTS. E1s are used (in the International Market) for transport of trafc channels to the BTS. Each E1 has 30 channels at 64 Kbps each, out of which 1 is used for the LAPD control link. The remaining 29 channels can each carry 4 trafc channels encoded with CDMA STRAU frames, giving 116 channels per E1 to a BTS. A+ is used over SS7 for transport of control data between MSC and MM. Usually this link will have physical resources dedicated solely for it (V.35 cables, when MM and MSC are co-located). In that case, each E1 between the XC and the MSC can carry 30 channels of PCM-encoded data.

NOTES:

Motorola Confidential Proprietary

211 of 259

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Observing CDMA CP at the MM scapdbg: ---------------------------- 96 Mar 22 ------------------------------------------ CDMA Ch Required --> 03:04:08.243 BTS: 52 ESN: 9f038ca4 Dialed: 992-0071 --- Complete L3 Info --> 0x0039 03:04:08.248 <-- Connect Conrmed --- 0x0039 03:04:08.345 --- Setup --> 0x0039 03:04:08.347 <-- Call Proceeding --- 0x0039 03:04:08.416 <-- Assignment Request --- 0x0039 03:04:08.479
MM

OMC-R

Utility called scapdbg used to look at message ow on MM. Utility presents ladder diagram of message ows, based on information from DBG output les. Getting scapdbg: http://scwww.cig.mot.com/SC/test/ cdma_foa/public_html Turning on DBG statements for SCAP for callproc1 and clcp: dbapi mDbg command. Looking more closely at SCAP messages: The SCAP denition document.

212 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Observing CDMA Call Processing at the MM

CDMA call processing may be observed at the MM through the use of a tool called scapdbg. This tool is not a comprehensive call analysis tool, but will sufce in giving the operator a general idea about call processing & device O&M activity. The tool was created by members of the Arlington Heights FOA group, along with some members of the development comunity. This tool is generally used when trying to debug problems with call processing when the system is rst being tested. Once a system is commercial, the call processing problems in the system tend to be due to bad coverage in certain areas, or due to high trafc volume. These problems are analyzed using another set of tools (more on this later). The tool presents a ladder diagram of messages going between the MM, XC, and MSC devices. The tool may be obtained through the Arlington Heights FOA group home page on the WWW at: http://scwww.cig.mot.com/SC/test/cdma_foa/public_html. In order for the scapdbg program to present the ladder diagram, the DBG attributes for the processes to be studied must be set to ScapTrace 3 by performing the following command from inside the dbapi debugger:
dbapi> mDbg callproc1 ScapTrace 3

Typically, the callproc1 and clcp processes will be modied as in the above command when an operator wants to trace call processing; while sc_devom, sc_vdt1 and sc_vdt2 will be modied when the operator wants to trace code downloads and device operations & maintenance. scapdbg usage:
scapdbg v11.3 Usage: scapdbg -cesxlhvdtTEB <ESN in hex> <BTS in decimal> -c Show detailed cause -e Show errors -s Show ESN, dialed digits and Markov -h Show handoff info -x Show XC connections -l Separate calls -b Ring bell between calls (off by default) -v Verbose (shows all the above) -d Use when decoding sc_devom or vdt -t Suppress Trouble Notifications -T Show only Trouble Notifications -E Only show calls with a particular ESN -B Only show sc_devom messages for a particular BTS

The SCAP denition document (available through the CIG library) is the reference document for SCAP messages of all types. NOTES:

Motorola Confidential Proprietary

213 of 259

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Call Processing Flows- General

MSC

CBSC XC MM

BTS

BTS

BTS

MS

Call Flows illustrate messages through system. Successful Mobile Origination. Successful Mobile Termination. Successful Mobile Registration. Errors can occur at any step in a ow. Timers are set up so that expected responses must arrive in a given time frame.

214 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Call Processing Flows- General

The next few pages illustrate the ow of messages which go through the CDMA network elements in order to perform different types of CDMA functions. Although this material is somewhat tedious, it is important to follow the ow in order to get an idea as to what happens during phone calls. An example mobile origination, as output from the scapdbg tool is as follows:
---------------------------- 96 Mar 22 ------------------------------------------- CDMA Ch Required --> 12:15:54.825 BTS: 52 ESN: 9f03733f Dialed: 001-305-999-9999 --- Complete L3 Info --> 0x019e 12:15:54.829 <-- Connect Confirmed --- 0x019e 12:15:54.928 --- Setup --> 0x019e 12:15:54.929 <-- Call Proceeding --- 0x019e 12:15:55.000 <-- Assignment Request --- 0x019e 12:15:55.060 <-- CDMA XC Ch Assigned --- 0x19f 12:15:55.062 CIC=78 MSC Span=2 TS=14 MSI=2 Span=A TS=2 Grp=2 CPP=1 BTS=52 MCC=1 CEP=1 Channel=1 PN=110 WC=18 ESN=9f03733f --- CDMA XC Assmnt Success--> 0x19f 12:15:56.565 --- Assignment Complete --> 0x019e 12:15:56.566 --- CDMA HO Recognized --> 0x19c 12:15:57.665 HOCause: Soft HO Add 1 - TAdd Event UplinkFER: 0 ActvPNs [Ec/Io] [Phase]: 110 [-5.0dB] [0] ttdrop timer not expired CandPNs [Ec/Io] [Phase]: 310 [-12.0dB] [19840] <-- CDMA XC HO Direction --- 0x19c 12:15:57.668 HOCause: Softer HO - Add 1 SrchWinN: 8 (60 chips) TAdd: 24 (-12.0dB) SrchWinA: 5 (20 chips) TDrop: 26 (-13.0dB) SrchWinR: 9 (80 chips) TTdrop: 4 (6 sec) NghbrMaxAge: 3 TComp: 4 (2.0dB) FwdPwrThresh: 2 (erasures) PN: 310 WC: 8 BTS=52 MCC=2 CEP=1 CHNL=1 --- CDMA HO Successful --> 0x19c 12:15:58.525 <-- CDMA Update Parameters--- 0x19c 12:15:58.527 Neighbor list: 10 20 210 30 40 410 60 160 No. of neighbors: 8 < LOTS of Hand-Offs (deleted for space constraints) > --- CDMA XC Radio Ch Rlsd --> 0x19c CDMA call processing cause: normal --<-<---<-- CDMA Release Radio Ch --- 0x19c BTS=52 MCC=2 CEP=1 Ch=1 CDMA call processing cause: normal <-<-- CDMA XC Rls Radio Ch --- 0x19d CDMA call processing cause: normal <-12:17:04.304 release Release Release Complete Clear Cmd Clear Comp release Release --> ------> 0x019b 0x019b 0x019b 0x019b 12:17:04.306 12:17:04.385 12:17:04.389 12:17:04.391 12:17:04.393

--- 0x019c 12:17:04.395 12:17:04.397

release SCCP Disconnect Req --- 0x019b 12:17:04.464

NOTES:

Motorola Confidential Proprietary

215 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [1] Origination Message [MSID(MIN,ESN),AUTH_MODE=0, SLOT_CYCLE_INDEX,SCM, service option 1, 2, 8002, or 8003 hex, dialed digits] [2] Base Station Ack Order

[5] LAPD: Channel Required [6] LAN: Channel Required

[4] CHI: Channel Required [Location area, Antenna Pair, Origination message]

[10] SS7: SCCP Connection Request + Complete Layer 3 Information Message (CM Service Request) [Cell Identifier,CM Service Type, Ciphering Key Sequence Number=111, Classmark Information Type 2,Mobile Identity (MID), Mobile Identity (ESN)] [If SCM in IS-95 Origination message indicates mobile is slotted mode, the Slot Cycle Index element is included in the CM Service Request.] [12] SS7: SCCP Connection Confirm [14] SS7: Setup [Called Party BCD Number] [16] SS7: Call Proceeding [19] SS7: Assignment Request [Channel Type, Layer 3 Header Info, Circuit Identity Code] [20] TC marked busy; MCC TCH and WC allocated [21] LAN: XC Channel Assigned [CDMA TCH information,encryption mode=0,frame offset=0,antenna pair, MIN,public long code mask,Circuit Identity Code, source XCVR routing info(TCH MCC),source XCVR routing info(PG MCC), ESN,CODEC mode,traffic channel code,call mode,service option]
Motorola Confidential Proprietary 216 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination (Continued)

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [22] LAPD: XC Channel Assigned ****************************************************************** XCDR is operating in default service option mode - no dim and burst operation - PCM silent tone generated toward MSC - IS-95 Null TCH Data generated toward MCC The XCDR and MCC are not yet connected thru the KSW ***************************************************************** [24] MCAP: Traffic Channel BTS Link Request [XCDR Channel,CL2=Clear Layer 2,B0=1] [25] MCAP: Port connection instructions [26] PCM silent tone [27] STRAU Speech frames containing IS-95 Null TCH data XCDR generated Null TCH data [29] PCM silent tone Generated by XCDR [28] STRAU Idle frames [30] MCAP: Traffic Channel State Change [XCDR channel,New_State=MCC_idle, Invalid_Speech, or Valid_Speech] **************************************************** XCDR and TCH MCC have acheived STRAU frame synchronization **************************************************** [32] LAPD: Channel Assigned [CDMA TCH information,encryption mode=0,frame offset=0,antenna pair, MIN,public long code mask,source XCVR routing info,ESN,call reference number] [33] LAPD: Channel Assigned [34] CHI: Channel Assigned [36] IS-95 frames

Motorola Confidential Proprietary

217 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination (Continued)

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [37] CHI: Target Channel Designation [CDMA TCH information,encryption mode=0, frame offset=0,MIN] [38] CHI: Target Channel Designation [40] Channel Assignment Message [ADDR_TYPE=0,ADDRESS(MIN), ASSIGN_MODE=0, FREQ_INCL=1,CODE_CHAN, CDMA_FREQ,FRAME_OFFSET=0, ENCRYPT_MODE=0] Upon detection of two consec. good frames on Fwd. TCH, MS starts to tx TCH Preamble. [43] IS-95 frames TCH Preamble *********************** MCC is in default service option mode: - IS-95 traffic from MS formatted as QCELP and sent to xcdr in STRAU Speech frames - STRAU traffic from XCDR formatted as QCELP and is expected in STRAU [44] STRAU Speech frames Speech frames Full-rate, inner & outer CRC indicators not equal to*********************** 00 [47] CHI: Suspend TCH Assignment [MIN] ******************************* TCH MCC has acquired the MS *******************************
Motorola Confidential Proprietary 218 of 259

[46] PCM silent tone generated in XCDR

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination (Continued)

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [48] CHI: Suspend TCH Assignment [50] MCAP: Traffic Channel State Change [XCDR channel,New_State=Invalid Speech] *********************************************** XCDR has detected TCH acquisition of the MS *********************************************** [52] MCAP: Layer 3 Message Request [XCDR Channel,Magic Number,ackr=1,Base Station Acknowledgment Order] [53] Base Station Acknowledgement Order [ack_req] [54] Mobile Station Ack Order [56] STRAU Speech frames Eighth-rate, inner & outer CRC = 00 [58] MCAP: Layer 3 Message Confirm [XCDR Channel, Magic Number] [59] MCAP: Traffic Channel State Change [XCDR channel,New_State=Valid Speech ] [61] MCAP: Layer 3 Message Request [XCDR Channel,Magic Number,ackr=1,Service Option Response Order] [ack_req,service option 1, 8002 or 8003 hex] [62] Service Option Response Order [63] Mobile Station Ack Order [55] IS-95 frames Null TCH Data

[57] PCM silent tone generated by XCDR

Motorola Confidential Proprietary

219 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination (Continued)

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [64] IS-95 frames QCELP, if SO=1 Markov data, if SO=8002 hex Data, if SO=8003 hex [65] MCAP: Layer 3 Message Confirm [XCDR Channel, Magic Number] [66] MCAP: Service Option Change Request [Service Option (1-QCELP, 8002 hex-markov, 4-m-m data trial), Codec Mode] The XCDR will start operating in the requested service option mode. SO 1: - Valid STRAU Speech frames from MCC will be transcoded into PCM and sent to the MSC - Traffic from the MSC will be transcoded from PCM into QCELP in STRAU speech frames - Dim and Burst operation will be used for downlink signalling SO 8002 hex: - Variable rate Markov data will be originated in the transcoder and sent to the MCC in STRAU Markov frames - Data received from the MCC in STRAU Markov frames will be treated as received variable rate Markov data - PCM silent tone or equivelent will be sent toward the MSC - Received PCM from the MSC will be discarded SO 8003 hex: - Synchronization with remote transcoder will be attempted (and will not be successful until MSC connects local and remote circuits) - Valid data traffic from the MCC will be sent to remote transcoder - Framed traffic from remote transcoder will be sent to MCC in STRAU Data frames - If no framed data traffic from remote transcoder, send IS-95 Null TCH Data to MCC in STRAU Data frames [67] STRAU frames If SO = 1: STRAU Speech frames containing PCM->QCELP transcoded silent tone If SO = 8002: STRAU Markov frames containing XCDR generated Markov data If SO = 8003: STRAU Data frames containing XCDR generated IS-95 Null TCH Data

Motorola Confidential Proprietary

220 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination (Continued)

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [68] STRAU frames If still receiving STRAU Speech frames downlink, continue STRAU Speech frames containing QCELP uplink If STRAU Data frames received downlink, send STRAU Data frames containing IS-95 traffic uplink If STRAU Markov frames received downlink, send STRAU Markov frames containing IS-95 traffic uplink

[69] LAPD: XC Assignment Successful [call reference number] [70] LAN: XC Assignment Successful [71] SS7: Assignment Complete [Channel Number] [73] SS7: Alerting

[74] PCM ringback tone

Motorola Confidential Proprietary

221 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Origination (Last Slide)

MSC MM FEP GPROC XCDR KSW GLI PG-ACC TCH MS [75] STRAU Frames If SO=1: STRAU Speech frames containing PCM->QCELP transcoded ringback tone If SO=8002: STRAU Markov frames containing XCDR generated markov data If SO=8003: STRAU Data frames containing XCDR generated IS-95 Null TCH Data

[77] SS7: Connect

******************** Called has Party Answered If SO=1, a PCM connection is now established between the called and calling parties If SO=8002, PCM received from the MSC is discarded by the XCDR, the XCDR sends PCM silent tone or equivelent to the MSC, the XCDR transmits markov data in STRAU Markov frames to the MCC, the XCDR receives STRAU Markov frames from the MCC If SO=8003, the local and remote transcoders achieve frame synchronization, and a data connection is now established between the called and calling parties ******************** [78] Through connected If SO=1: PCM (voice) If SO=8002 hex: dont care If SO=8003 hex: rate adapted data frames

[79] STRAU Frames If SO=1: STRAU Speech frames containing PCM->QCELP transcoded voice If SO=8002 hex: STRAU Markov frames containing XCDR generated markov data If SO=8003 hex: STRAU Data frames containing transcoder bypassed data

[80] MCAP: Synched to remote xcdr circuit SO 8003 hex only: Indicates to GPROC that frames from the remote transcoder are being received by the local transcoder from the MSC direction. [81] SS7: Connect Acknowledge

Motorola Confidential Proprietary

222 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Termination

MSC MM FEP GPROC XCDR KSW GLI TCH MS [1] Release Order [normal release or power down indication] [2] IS-95 frames [3] STRAU Speech frames Null TCH Data Eighth-rate, inner & outer CRC=0 [5] MCAP: Layer 3 Message Indication [XCDR Channel,Release Order message]

[4] PCM

[6] Use fast repeat to send Release to MS

[8] MCAP: Layer 3 Message Request [XCDR Channel,Magic Number,Fast_repeat_flag=use fast rep., ACKR=no ack req.,Release Order message] [no reason given] [9] Release Order [no reason given]

[10] MS stops tx

[11] TCH loses MS [12] MCAP: Layer 3 Message Confirm [XCDR Channel,Magic Number] [Note that in fast repeat case, L3 Msg Confirm and State Change Indication may reverse order.] [13] STRAU Traffic frames (bad quality) ********************************************************** XCDR detects loss of the MS on the Reverse Traffic Channel ********************************************************** [14] MCAP: Traffic Channel State Change Indication [XCDR Channel,New_State= bad quality traffic frames] [16] MCAP: Traffic Channel BTS Link Request [XCDR Channel,CL2=clear layer 2,B0-B2=inactive link] [17] XCDR is now in service optionless state

Motorola Confidential Proprietary

223 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Termination (Continued)

MSC MM FEP GPROC XCDR KSW GLI TCH MS [18] STRAU Speech frames containing IS-95 Null Traffic Channel Data [19] PCM Silent tone or equivalent [20] PCM [21] MCAP: Port connection instructions [22] All TCH MCCs in call are disconnected from XCDR

[23] STRAU Speech frames containing IS-95 Null Traffic Channel Data [24] KSW idle pattern [25] KSW idle pattern on BTS links into XCDR [26] IS-95 frames [27] LAPD: XC Radio Channel Released Null TCH Data [cause=normal release] [28] LAN: XC Radio Channel Released [30] SS7: Release [cause layer 3=normal clearing] [31] SS7: Release Complete [35] SS7: Clear Command [Layer 3 Header Information, cause=call control] [37] SS7: Clear Complete [39] Idle TC

Motorola Confidential Proprietary

224 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Termination (Last Slide)

MSC MM FEP GPROC XCDR KSW GLI TCH MS [41] Release all TCHs associated with call [42] LAN: Release Radio Channel [detailed cause]

[43] SS7: SCCP RLSD [44] SS7: SCCP RLC [45] LAPD: Release Radio Channel [46] CHI: Release Radio Channel [47] TCH stops dl tx [48] CHI: Radio Channel Released [49] LAPD: Radio Channel Released [50] LAN: Radio Channel Released [51] Stop MmCpT3 [52] Deallocate TCH MCC and associated Walsh Code

Motorola Confidential Proprietary

225 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Registration

MSC MM FEP GLI PG-ACC [1] Registration [ACK_REQ, MSID, REG_TYPE, SLOT_CYCLE_INDEX, SCM] MS

[2] BTS Ack Order [ACK_SEQ,VALID_ACK] This message is sent using quick repeats. [3] CHI: Location Registration Request [ MIN, Location Area, ESN Registration Type, SCM, Slot Cycle Index ] [4] LAPD: Location Registration Request [5] LAN: Location Registration Request

[7] SS7: SCCP Connection Request + Complete Layer 3 Information (Location Updating Request) [Location Area Identification, Mobile Id (MID), Mobile Id (ESN)] [If the SCM indicates that the mobile is slotted mode, the Slot Cycle Index element is included]

Motorola Confidential Proprietary

226 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Mobile Registration (Last Slide)

MSC MM FEP GLI PG-ACC MS [8] SS7 SCCP Connection Refused + Location Updating Accept [Location Area Identification]

[10] LAN: Location Registration Accepted [MIN] [If the MS is operating in slotted mode, the Slot Cycle Index element is included] [11] LAPD: Location Registration Accepted [12] CHI: Location Registration Accepted [13] Registration Accepted Order Sent using quick repeats. If L2 info for the MS id still exists, include an ack to the Registration message in the Registration Accepted Order.

Motorola Confidential Proprietary

227 of 259

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Hand-Offs in CDMA
MSC

CBSC XC MM

BTS

BTS

BTS

MS

Mobile Assisted Hand-Offs (MAHO) used in CDMA. TAdd, TComp, TDrop, and TTDrop- four of several parameters governing HOs. The XC, MM, and MS are involved in HOs. XC detects need to HO indications sent by MS, selects the best 20ms frames from two or more BTSs. MM determines resources to use for the HO, sends instructions to XC and MSC to perform HO.

228 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Hand-Offs in CDMA
HO detection processing takes place in the MS, the XC, and the MM. The MS has parameters which dene which Pilots will be in the Active Set, and in the Candidate Set (the two most important sets). Some of these parameters are: TAdd- Threshold above which a pilots signal strength must rise in order for the MS to transmit a pilot strength measurement message. The pilot strength measurement message is the mobiles response to the infrastructure indicating that the MS has seen a strong Pilot. TComp- Threshold above which a candidate set pilot strength must rise above an active set pilot to cause the MS to transmit a pilot strength measurement message. TDrop- Pilot signal strength threshold below which a pilot will be dropped from its list (either Active, or Candidate list). Pilot must stay under the threshold for TTDrop time or more in order to be dropped from its list. The XC will detect the need to handoff (by detecting the pilot strength measurement from the MS), perform handoff preprocessing and identify hand-off events. The XC also selects the best 20ms frame of STRAU data to transcode, from the 2 or 3 available frames. The MM will determine the handoff type, perform target selection and perform channel allocation (Walsh codes, available MCCCE, XCDR circuits, etc.). The following is a section of the output from the scapdbg script for a hand-off:
--- CDMA HO Recognized --> 0x19c 12:15:57.665 HOCause: Soft HO Add 1 - TAdd Event UplinkFER: 0 ActvPNs [Ec/Io] [Phase]: 110 [-5.0dB] [0] ttdrop timer not expired CandPNs [Ec/Io] [Phase]: 310 [-12.0dB] [19840] <-- CDMA XC HO Direction --- 0x19c 12:15:57.668 HOCause: Softer HO - Add 1 SrchWinN: 8 (60 chips) TAdd: 24 (-12.0dB) SrchWinA: 5 (20 chips) TDrop: 26 (-13.0dB) SrchWinR: 9 (80 chips) TTdrop: 4 (6 sec) NghbrMaxAge: 3 TComp: 4 (2.0dB) FwdPwrThresh: 2 (erasures) PN: 310 WC: 8 BTS=52 MCC=2 CEP=1 CHNL=1 --- CDMA HO Successful --> 0x19c 12:15:58.525 <-- CDMA Update Parameters--- 0x19c 12:15:58.527 Neighbor list: 10 20 210 30 40 410 60 160 No. of neighbors: 8

The following pages illustrate message ow through the CDMA system under different hand-off situations.

NOTES:

Motorola Confidential Proprietary

229 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Soft Hand-Off Add Success

MM XC KSW XCDR ADD_TCH ALL_TCH MS [1] RF: Pilot Strength Measurement Message [Pilot strengths, Pilot phases, reference pilot strength & phase]

[2] SCAP: CDMA Handoff Recognized [Cause field = soft handoff add, XC starts timer XcHoT7.] [3] Channel Hunt Process

[MM recognizes "add", finds available TCH in target cell]

[4] SCAP: CDMA XC Handoff Direction [Soft handoff "add" decision, new set of active pilots, etc.]

[5] MCAP: KSW Connection Request [Route downlink QCELP to new target, time align uplink.]

[6] MCAP: CDMA TCH BTS Link Request [Connect XCDR to new TCH.]

Motorola Confidential Proprietary

230 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Soft Hand-Off Add Success (continued)

MM XC KSW XCDR ADD_TCH ALL_TCH MS [7] SCAP: CDMA Handoff Channel Assigned [The target MCC programs its searchers, setpoint, forward power, and "keys" PA.]

[8] SCAP: CDMA Forward Channel Transmission Indication [Target MCC is now simulcasting on downlink.]

[9] RF: Extended Handoff Direction Message [HDM_SEQ, search windows, T_ADD, T_DROP, T_TDROP, T_COMP.] [Pilots and Walsh codes of active TCHs.] [Start timer XcHoT1.] [10] RF: Handoff Completion Message [Pilots involved in active set and HDM_SEQ.] [XC clears timers XcHoT7 and XcHoT1.]

[11] RF: Base Station Acknowledgment Order [12] SCAP: CDMA Handoff State Change [Number of forward links and receivers assigned to the call]

[13] SCAP: CDMA Handoff Successful [MM clears timer]

Motorola Confidential Proprietary

231 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Call Flow: Soft Hand-Off Add Success (Last Slide)

MM XC KSW XCDR ADD_TCH ALL_TCH MS The following messages are sent as required

[14] SCAP: CDMA Update Parameters Message [15] RF: In-Traffic System Parameters Message [16] RF: Mobile Station Acknowledgment Order [17] RF: Neighbor List Update Message [18] RF: Mobile Station Acknowledgment Order [19] RF: Power Control Parameters Message [20] RF: Mobile Station Acknowledgment Order

Motorola Confidential Proprietary

232 of 259

PWID Center for Excellence

Revision 0, 5/23/96

CDMA Call Processing

Page intentionally left blank.

Motorola Confidential Proprietary

233 of 259

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Looking at SCAP & A+ Messages

file: ../AplusComm.C func: ServiceInbound() AplusMsg is: ---------SCCP HEADER(6 bytes)-------Message Type: 0x1201 Ref Number: 0x00000000 ------A+ BSSMAP HEADER(2 bytes)-----Message Discrimination: 0x00 Length Indicator: 0x07 ---------BODY(7 bytes)----------------------Message Type: 0x34 01 00 37 04 01 07 ------------HEADER(20 bytes)-----Header Version: 0x0 Data Version: 0x0 Hop Count: 0x2 Channel ID: 0x1 Data Length: 0x48 Message Type: 0x12 Dest Address: sys(0x80) subsys(0xffff) grp(0xff) dev(0xff) elem(0xff) Response Type: 0x0 Source Address: sys(0x81) subsys(0x0001) grp(0x80) dev(0x42) elem(0x22) -------------BODY(bytes)---------0x00 0x22 0x00 0x00 0x00 0x0a 0x42 0xc6 0xd5 0x80 0x00 0x0b 0x39 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00 0x01 0x01 0x00 0x00 0x17 0x00 0x34 0x00 0x18 0x00 0x1c 0x00 0x0f 0x1a 0x00 0x00 0x24 0x06 0x01 0x9e 0x00 0x00 0x10 0x06 0x01 0x01 0x00 0x00 0x21 0x18 0x13 0x01 0x08 0x01 0x05 0x04 0x03 0x80 0x87 0xaa 0x6c 0x06 0x80 0x84 0xa7 0xaa 0xaa 0x0a 0x70 0x01 0x00 MSC

CBSC

XC

BTS

BTS

MS

SCAP document provides full denition of all messages for control of the BTSs and the XC. A+ document provides full denition of all A+ messages for communication to the MSC. DBG output les will contain all the messages as seen above when Trace 3 is turned on.

234 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

CDMA Call Processing

Looking at SCAP and A+ Messages At times it could be necessary to go down to the bits-and-bytes level in order to debug a particular problem, or just to get more information on whats going on with the CDMA network elements.
The messages must be captured rst, by using the dbapi debugger and turning on the DBG statements for Trace at level 3 for processes to be studied. In general, turning on Trace for callproc1, clcp, cpmo, and sc_devom will give most messages of interest. The SCAP ICD document denes all the messages and message formats for all messages going over the BTSLINKs, and the XCLINKs. This document can be found in the Arlington Heights Supercell Library, which has an on-line copy in the AH Sun network at /usr/test/scdocrel/COM/GEN/ICD/003. The A+ ICD document denes all the messages and formats for messages going over the A+ links from the MM to the MSC. This document can also be found in the Arlington Heights Supercell Library (on-line path is not available at time of writing, but reader can try the Arlington Heights Web page: http://www.sc.cig.mot.com/SC/library/ index.html for more information.

NOTES:

Motorola Confidential Proprietary

235 of 259

Conclusions:
Call Processing in CDMA is carried out at all points in the network. However, the MM is the work horse. Call Processing message ow may be observed at the MM by using the scapdbg program. DBG statements must be turned on for ScapTrace at level 3 for the above program to work. Call Processing ows help understand what is going on in the system when a call is placed. Hand-Offs are considered part of call processing. Hand-Offs are handled mostly by the MM, although the MS, XC are always involved. The MSC is involved for Hard Hand-Offs. Several parameters govern the behavior of Hand-Offs. These parameters are editable. The SCAP and A+ ICD documents are the authorities on messages going over the BTSLINKs, XCLINKs, and over the A+ link.

236 of 259

Motorola Confidential Propretary

PWID Training: CDMA

Tricks, Tips & Tools for Unix and CDMA

Motorola Confidential Proprietary

237 of 259

Objectives:
To present various tricks & tips on general topics related to Supercell and Unix. To present a brief overview of the tools available for CDMA data analysis (statistics and drive test data).

238 of 259

Motorola Confidential Proprietary

Table of Contents:
On-Site Access to Outside World.................................................................................. Setting up a Dial-In Modem......................................................................................... Ethernet Conguration ................................................................................................ Other Unix Tricks: Find, dps, high priority session................................................ More Tricks & Tips: ftp, telnet, anonymous ftp, etc.................................................... Tricks & Tips: tar, compression utilities, framemaker batch les .............................. Tools for Analysis of CDMA Data ............................................................................... 241 243 245 247 249 251 253

Motorola Confidential Proprietary

239 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

On-Site Access to Outside World

For accessing the external world, hardware needed:

- Portable PC with an ethernet card (preferably PCMCIA- very convenient). - PC Modem (at least 14.4 baud). - Direct-connect telephone lines to the site. - Activated SecureID card (at least one).

Software needed (two options):

- Obtain Linux for PCs (vendor, the Internet, or through Motorola WWW), or- Obtain Connection Kit (through Motorola WWW- soon) for Windows.

Second option will be easier, but rst option allows Unix OS on your portable PC!

240 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

On-Site Access to Outside World It is very useful that the CBSC site be equipped to communicate with the outside world, specically with the Motorola internal network. An operator can never guess exactly when a particular le will be necessary, or some information which is on the Motorola WWW is crucial to the proper functioning of a new release. Access to email, phone lists, etc. will also be provided with a link to Motorola. The following are points are given on establishing a link.
Hardware requirements: A portable PC with an Ethernet PCMCIA card and a modem. A combo card (28.8 Modem, Ethernet 10BaseT and 10Base2) PCMCIA Ethernet card such as 3Coms Etherlink III Combo card is recommended. In addition, direct-connect lines to the outside world for exclusive use by modems should be installed at the CBSC site. This usually must be arranged with the customer, since the customer will <usually> have another MSC at the site (assuming that most customers install CDMA in the same physical facilities as their existing analog or digital telephony equipment). At least one activated SecureID card is essential in order to access the Motorola network. Contact ITS at the CIG help desk ([email protected]) in order to get information on activating a SecureID card, or contact your local support person for information on how to obtain a new card. There are two approaches to obtaining the software necessary for the portable PC to access the Motorola network- one is through the Linux OS (which is a version of Unix available on the internet for free), or through a Connection Kit which will allow PCs with Windows to login to the Motorola network and use such utilities as ftp, telnet, and Netscape. Linux is more complicated to install, but at the same time it provides a full version of Unix which the operator might nd interesting to play around (hack) with. Linux includes PPP (Point-to-Point protocol), which is necessary to create a link with Motorola through a dial-up modem. Linux also has ftp, telnet, and Netscape applications available. Linux is available through the WWW (search for Linux Distributions), or it may be purchased on CDROM through Walnut Creek CDROM(1-800-786-9907). A bare-bones version of Linux is available on the Motorola WWW at http: The Connection Kit will be available on the Motorola WWW soon (look for notication on the cdmaprod mailing list). NOTES:

Motorola Confidential Proprietary

241 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Setting up a Dial-In Modem

Remote Support Site

MTSO

Imperative at times to allow outside access of OMCR (and thus, MM and XC as well) to qualied Motorola personnel. Access must be restricted!!!! Additional hardware needed: at least 9600 baud modem (1) with RS-232 connection. One RJ-48 to RS-232 cable. Procedure Overview:
- Connect modem to power supply, telco, async card. - Add a port (software command for port monitor). - Add a service to the port (software command for port monitor). - Dial in, and get a prompt!

242 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Setting up a Dial-In Modem At times it is critical for outside support personnel to be able to login to the OMC-R in order to debug problems with Supercell equipment such as the OMC-R, MM, or XC. The following are notes and procedures for setting up access for the outside world.
First of all, it is critical that this be done only when absolutely necessary, and that access to the system be monitored such that only authorized personnel have access. In addition, the account through which the remote personnel will login must be protected by a good password, and the modem should actually be turned off when not in use in order to avoid un-authorized access. The hardware needed: One modem with RS-232 port (at least 9600 baud). The modems used in the SC9600 BTSs may be used on the OMC-R, provided there is a +27 VDC power supply. Most of the time a BTS will be co-located with the OMCR, so the BTS modem could be used temporarily. The modem must be connected to a telephone line with direct access to the outside world (PSTN). One RJ-47 to RS-232 cable. The cable used for connecting the OMC-R console terminal to the IOP card may be used (its better to use a spare cable, if there is a spare available). This cable is connected from the rst available terminal on the rst async card in the back of the OMC-R. Add a port monitor process (ttymon), using the sacadm command. An example is the following:
# sacadm -a -p ttymon1 -t ttymon -c /usr/lib/saf/ttymon -v `ttyadm -V` -n 1000

Please note that the word following the -p argument is the tagname of the port monitor being added. This tagname will be used in the following command, which must be executed next (all one line):
# pmadm -a -p ttymon1 -i root -s 0 -f u -m `ttyadm -p tty0login: -h -d /dev/term/ a0 -l 9600 -s /usr/bin/login` -v `ttyadm -V`

The above command will tie the port monitor process (established with the sacadm command) of tagname ttymon1 with a login service. Note that the -d argument must be replaced with the actual device number (a0 is the topmost connection on async card 1, a7 is the bottom-most). The 9600 entry is the speed of the modem, while the tty0login: is the prompt presented upon login.

NOTES:

Motorola Confidential Proprietary

243 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Ethernet Conguration
OMCLAN-1-omc OMCLAN-2-omc OMCLAN-1-mm1 enet0 (slot 161) 198.175.180.10 enet0 (slot 161) 198.175.180.11 OMCLAN-2-mm1 enet1 (slot 164) 198.175.181.10 IFELAN-2 enet1 (slot 164) 198.175.181.11 OMC-R enet2 (slot 166) 198.175.182.01 enet3 (slot 168) 198.175.183.01 IFELAN-1 MM-1 FEP-1 198.175.182.01 enet2 (slot 166) 198.175.183.01 enet3 (slot 168) ... Bridge Bridge FEP-2 FEP-x

MMI LAN-1 MMI LAN-2

OMCLAN-1-mm<n>

enet0 (slot 161) 198.175.180.1n OMCLAN-2-mm<n> enet1 (slot 164) 198.175.181.1n MM-n 198.175.182.01 198.175.183.01 IFELAN-1 FEP-1 Bridge Bridge IFELAN-2 enet2 (slot 166) enet3 (slot 168) FEP-2 FEP-x

Ethernet sub-system rst established by adding the cards with a cnstall (on Tandem). Several les govern ethernet conguration: /etc/inet/ strcf, /etc/inet/rc.inet, and /etc/hosts. The /etc/rc4.d/fast/S69inet script starts and stops the ethernet stack. The ifcong command allows management of network interfaces to unix. The netstat command displays status and conguration (routes, etc.) for network interfaces.

244 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Ethernet Conguration The commands and comments given here apply to the MM and OMC-R platforms specically, but most Unix-based platforms will be very similar.
The ethernet cards are installed as part of the MakeSC9600 script. The following command will install the rst ethernet card on the MM or OMC:
cfinstall -i iop1 -c enet0 -s ioc0

The les that congure the ethernet sub-system are: /etc/inet/strcf. This le congures the TCP/IP system, including the ethernet cards. An example command in this le for ethernet card 0 is as follows:
cenet ip /dev/enet enet 0 # S2 eagle enet

/etc/inet/rc.inet. This le performs the ifcong les for each ethernet card, giving each card an identify on the network, and the le also sets up a route for trafc. Example cong lines in this le are as follows:
/usr/sbin/ifconfig enet3 vulcan5 up -trailers netmask 0xffffff80 broadcast 136.182.112.255 /usr/sbin/ifconfig enet0 OMCLAN-1-mm1 up -trailers /usr/sbin/route add default 136.182.112.254 1

/etc/hosts. This le contains name to IP address translations. The vulcan5 and OMCLAN-1-mm1 names given in the above command must have entries in this le with proper IP addresses. The script /etc/rc4.d/fast/S69inet can be used to stop and start the ethernet services (just invoke the script with either a stop or start argument). The ifcong command may be used as follows to print information on ethernet:
vulcan5:/etc/inet > ifconfig enet0 enet0: flags=4023<UP,BROADCAST,NOTRAILERS,MULTICAST> inet 198.175.180.11 netmask ffffff00 broadcast 198.175.180.255

The netstat command may be used as follows to print information on ethernet:

vulcan5:/etc/inet > netstat -ir Name Mtu Network Address spsl1 296 192.150.151 SP_HOST spsl0 296 192.150.151 SP_HOST lo0 2048 loopback localhost enet2 1496 198.175.182 IFELAN-1 enet0 1496 198.175.180 OMCLAN-1-mm1 enet3 1496 136.182.112 vulcan5 enet1 1496 198.175.181 OMCLAN-2-mm1 Ipkts 1201495 1211464 2857 1366502 365109 160374 0 Ierrs 0 0 0 0 0 0 0 Opkts 1213658 1223859 2857 1847960 491086 150622 0 Oerrs 0 0 0 0 0 0 0 Collis 0 0 0 12 205 274 0

NOTES:

Motorola Confidential Proprietary

245 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Other Unix Tricks

MM

These tricks are really making me smart!

OMC-R

The nd command.
- Useful for performing operations on les which match certain parameters.

The dps command.

- Useful for checking process consumption of memory, CPU resources.

High-priority console.
- Necessary to enable access to MM when MM is under stress.

246 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Other Unix Tricks: Find, dps, high priority session

The Unix nd command is very convenient for performing operations on les that comply with a desired attribute. For example, to remove all les with the extension 254, the following nd command may be performed:
# find . -name \*.254 -exec rm -f {} \; -print

The above command will nd les starting in the current working directory, and will executed the command rm -f on the les which end in a 254 extension. The command to be executed may be any command which may be executed by the Unix shell. The brackets {} will be substituted with the le name, while the escaped-semicolon \; signals the end of the command. The -print directive will print those les which were removed. In order to nd out which processes are consuming the most time and memory resources in the system, a command called dps may be used. Command usage:
Usage: dps [-T] [-r] [t [n]] Where -T specifies to print time-of-day for each report, -r specifies relative time reporting (default is absolute), and t specifies time (no default) between n samples (default 1). Example: dps 5 2 Reports two 5 second samples with respect to absolute time.

On very RARE occasions, an MM may lock-up (no response from the MM tty sessions). Usually this is due to a run-away Supercell process which is running in the Real-Time priority class. In order to provide a means to debug the situation, it is recommended that the operator establish a high-priority tty session at the console of the MM through the following command (after logging into the console as root):
# priocntl -e -c RT -p 59 -t 1000 ksh

In addition, the following command will list all processes currently running in the RT class:
# priocntl -d -i class RT

Check to make sure that the shell running at the console window is among the list resulting from the above command with the following (which prints the shells process ID):
# echo $$

NOTES:

Motorola Confidential Proprietary

247 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Still More Tricks & Tips

MM

Wow! Im really becoming a power user!

OMC-R

IP addresses, and NameServers. Using FTP, TELNET. Using PWIDs anonymous FTP server.

248 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

More Tricks & Tips: ftp, telnet, anonymous ftp, etc.

Computer platforms which have a TCP/IP communications stack are identied on the Internet with numbers called IP addresses, such as 160.4.22.1 (this is the IP address of the le server in Ft. Lauderdale). Names may also be used, but you must have a Name Server which is capable of translating the name into an IP address (or the name must be in the /etc/hosts le of your local platform). Most name servers have a program called nslookup which allows you to nd out the IP address of the Name Server, and of the machine you are looking for. For example, to nd the address of the anonymous FTP server in Rolling Meadows:
segws005 $ nslookup ftp.rollingmdws Name Server: segfs001.ftlauderdale.pamd.cig.mot.com Address: 160.4.22.1 Non-authoritative answer: Name: ftp.rollingmdws.pamd.cig.mot.com Address: 160.4.64.1

Anonymous FTP means that the user may enter anonymous as the user id for the remote system, and the password is usually the users email address. Many anonymous ftp sites exist all over the internet for different types of stuff. FTP stands for File Transfer Protocol, and is used to transfer les from one system to another. If you have the IP address of the platform, you can start an FTP session, and transfer les to your local platform. Inside FTP, you should set the bin mode (so that les get transferred in binary mode), and you should enter the hash command (so that you can see the progress of a transfer). Other commands are available, such as lcd (for changing the local directory), cd (for changing the remote directory), get (which gets a le from the remote system, and put (which puts a le into the remote system from the local system). Telnet is used to setup a session on a remote unix session. Again, an IP address is needed by the telnet command in order to login to the remote system. When a connection is established with the remote system, a login prompt is presented, and the user must enter a username and password to gain access to the remote system. One trick that is used is to enter the command DISPLAY=<LOCAL_IP>; export DISPLAY on the remote system, and xhost+ on the local system, and then start a program that uses Xwindows. The program will be displayed on the local system, but will actually be running on the remote system.

NOTES:

Motorola Confidential Proprietary

249 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

And Still More Tips!

MM

Okay! Im learning as fast as I can!

OMC-R

The tar command. Compression Utilities. Framemaker batch les.

250 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Tricks & Tips: tar, compression utilities, framemaker batch les

The tar command is used to place all the les in one or more directories into one at le which can then be compressed and transferred using ftp. To make a tarle called / tmp/scap.tar which contains all the les and sub-directories under /usr/test/scap:
segws005 $ cd /usr/test segws005 $ tar -cvf /tmp/scap.tar scap

Notice that we made /usr/test the current working directory before doing the tar. We could have specied /usr/test/scap as the directory to tar, but then when you un-tar the tar le, the command would attempt to create /usr/test/scap, and many times the user will not have the access privileges to do that. To un-tar a tarle:
segws005 $ tar -xvf /tmp/scap.tar

Usually a tar le will be created in order to transfer the information over a link to a local system. It is convenient to compress this information so that the transfer does not take as long. Several compression utilities exist for Unix. The most common is compress, and its counter-part, uncompress. These programs create a le with a .Z extension.
segws005 $ compress /tmp/scap.tar segws005 $ ls -la /tmp/scap.tar* -rw-r--r-1 ashapple engr 1329 May 23 10:36 /tmp/scap.tar.Z

Another set of programs are the gzip and gunzip utilities- these are made by the famous GNU programmers, and is shareware (freely available on the Web). These are more efcient than compress/uncompress, and are generally available for many platforms (however, check to make sure both platforms have this utility before using it). Much documentation is now being done in Motorola using Framemaker (a powerful document processing software package). When Framemaker versions change, the user must convert the les to the new version. A script which will do this for all the les in a given directory (except those ending with a .ps or .backup extension) is as follows:
#! /bin/ksh find . ! -name \*.ps -type f -print > /tmp/files.frame find . -name \*.backup -exec rm {} \; > /tmp/frame.script for file in `cat /tmp/files.frame` do echo Open $file >> /tmp/frame.script #echo Update $file >> /tmp/frame.script echo Save $file >> /tmp/frame.script echo Quit $file >> /tmp/frame.script done echo Quit >> /tmp/frame.script cat /tmp/frame.script fmbatch -v /tmp/frame.script rm /tmp/files.frame rm /tmp/frame.script find . -name \*.backup -exec rm {} \;

NOTES:

Motorola Confidential Proprietary

251 of 259

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Tools for Analysis of CDMA Data

OMC-R

How do I analyze this systems performance?

OMC-R

Data collected through:

- PM reports stored at OMC-R. - Drive tests (using Safeco, LCC, or Motorola CAMPS). - SMAP platform- used at CBSC to collect forward link information.

Data analyzed through:

- UNO platform GUI, reports. - XFreq, pm_sum programs. - Automatic Overnight Analysis program.

Sources of information given for the above.

252 of 259

Motorola Confidential Proprietary

PWID Center for Excellence

Revision 0, 4/24/97

Tricks, Tips & Tools for Unix and CDMA

Tools for Analysis of CDMA Data There are several tools available for analysis of data from a CDMA system. The following points are presented concerning this:
Data is collected automatically by the system, and stored at the OMC-R platform. This data is analyzed by programs running on the UNO platform which present the data in a user-friendly manner. The tables and the reports which may be generated from them are specied in the Performance Analysis manual from TED- part # 68P09226A23-2. Data collected from the system will be due to use of the system- the data will include records on calls which failed with given CFCs. This data is usually of much interest to the operator, in that call failures will need to be analyzed. A software program called Xfreq by Allan Shedlo (see http:// www.rochellepark.pamd.cig.mot.com/~ashedlo/) will present a graphical interface to the data, while another software program (also by Allan) called pm_sum will generate useful reports on the Performance Management data for purposes of analyzing network problems. Data may also be collected through drive tests. Drive tests will usually be conducted using Safeco equipment, although recently another company called LCC is producing CDMA drive test equipment, and Motorola has produced a product called CAMPS for drive testing. The CAMPS web page is: http://scwww.cig.mot.com/SC/mgmt/tools/ CDMA/Test_Tools/CAMPS/index.html. The data collected from drive testing is analyzed using a software program called AOA (Automatic Overnight Analysis). The name is somewhat of a misnomer, since it usually doesnt take all night to analyze the drive test data. The AOA home page is: http:// www.fwrdc.rtsg.mot.com/TPD/Projects/AOA/product.html. Every two weeks there is a conference call held by a group of engineers and managers who are involved with the analysis of CDMA network performance. Jay Moore is heading up this group- the group currently has representatives from all the major markets (Antonio Shappley is representing PWID). The notes from the meetings and other notes or questions are sent to a mailing list: [email protected]. Send email to [email protected] with a line which states subscribe cdmadata (in the body) in order to become a member of this mailing list. Another tool used to collect data from the system during operation and/or drive tests is SMAP. TED publishes an operators guide (68P09226A14). The project manager for SMAP is John Bernas- 847-632-3557. NOTES:

Motorola Confidential Proprietary

253 of 259

Conclusions:
Having on-site access to the outside world from the MTSO can be a life-saver! Allowing access to the MTSO (MSC, CBSC, etc.) to remote engineers can also be a life-saver! Commands netstat -ir, and ifcong are used to nd status and conguration of communications subsystems. The nd command is convenient for performing operations on many les. The dps command works on MM and OMC-R to see which processes are using the most resources. A high-priority session must be established on the MM and OMC-R console. Ftp, telnet, anonymous ftp are used to access remote systems. The tar program can be used along with compression utilities to ship many les to other systems. Framemaker batch les can be used to bring many documents up to the latest frame release.

254 of 259

Motorola Confidential Propretary

References:
Many sources of information exist for CDMA. Following are most of the sources used by the author to put this course together, and to learn about the CDMA technology and the CDMA Supercell system in general. Supercell Library (http://www.sc.cig.mot.com/SC/library/index.html). Most documents in the library are available on-line in the Arlington Heights network under /usr/test/scdocrel. The PWID Rolling Meadows /users/CDMA directory. Under this directory are many usefull documents for CDMA, including the CDMA RF Guide. TEM (Technical Enrichment Matrix) Presentations (http://www.acpg.cig.mot.com/w3/APD/ TSG/TEM/tem.html). TEM video tape libraries are in Ft. Worth and in Arlington Heights. In Arlington Heights, call Jennifer at 632-4133. Of particular interest to CDMA are: Supercell Software Architecture, by Paul Steinberg et.al., Supercell Applications Processor, by Chris Sheneel, and the SC600 Overview, by Craig Reilly et.al. Some presentations will soon be available at Ft. Lauderdale- contact Felix Garcia about this (954-489-2051). The PWID Core Tools home page (http://www-home.pamd.cig.mot.com/group_pages/ groups_html/core_tools). Check out the CDMA BSS Sysgen Creator Guide (CBSC Database Tool), under Digital Database. The Arlington Heights FOA groups home page (http://www.sc.cig.mot.com/SC/test/ cdma_foa). Notes from FOA group members may be found under this link- including the CDMA Recommended Parameters document. Mobile Cellular Telecommunications, William C. Y. Lee. Available from McGraw-Hill. Purchasing line: 800-722-4726. Product Code: 0070380899. This is overall one of the best books on Cellular Technologies available. It covers analog and digital technologies, including CDMA. U.S. CDMA Commercial System Specication (The B1 Document), Motorola CIG. This document presents Motorolas CDMA to Motorola customers. Its a good overview of the Motorola CDMA product. Available from the Supercell library. SC9600 Architecture Document (The ARD Document), Motorola CIG. This document discuses the SC9600 equipment architecture in some detail. Also available at the CIG library. CDMA Call Processing System Functional Specication (The CP SFS Document). Also available from the Supercell Library. CDMA Hand-Off and Power Control System Functional Specication (HOPC Document). Also availabel from the Supercell Library. TED Courses GNL180 (CDMA: IS-95 Implementation & Operation), and GNL190 (CDMA Call Processing). These courses are given by Space 2000, usually by Dr. Simo, or by Dr.

255 of 259

Motorola Confidential Propretary

PWID Center for Excellence

Revision 0, 4/24/97

References

Nored. Both courses are highly recommended. The CDMA Command Reference Guides. Available from TED. Call George Reed (847632-2747) or Dora Lopez (847-435-7661). The CDMA SC9600 and SC4950 BTS Installation and Optomization Guides, Available from TED. The cdmadata, cdmaprod, and cdmadbcm mailing lists. Send email to [email protected], with the line subscribe <listname> in the body. You will be added to the mailing list, pending that the list is open. Approval of the subscription may be necessary for closed lists.

256 of 259

Motorola Confidential Proprietary

Acknowledgements:
Paul Steinberg and others- Supercell Software Overview TEM. Marilyn Escue- CDMA Call Processing TEM. Steve Wasilew- Introduction to SuperCell Digital Cellular Technology. Phil Tsubaki- XC Overview. Mike Jones from TED- Much documentation on CDMA- manuals, instructor notes, etc. Many, many others who helped out in one way or another- Thanks!

257 of 259

Motorola Confidential Propretary

PWID Center for Excellence

Revision 0, 4/24/97

Acknowledgements

Page intentionally left blank.

258 of 259

Motorola Confidential Proprietary

Last Page!
Please use this page for any notes you want to make.

259 of 259

Motorola Confidential Propretary