Straex800 CBTS Lpa (010619)

BTS System Description
STRAEX-800 Compact-BTS System (Standard)

Summary
This document describes compact BTS system. Compact BTS system is BTS of Starex-800 Standard, a personal communication system adopting CDMA digital mobile communication technology.
Table of Contents 1. General...............................................................................................................................1 1.1 Overview.......................................................................................................................1 1.2 Specification.................................................................................................................2 2. Architecture.........................................................................................................................5 2.1 H/W Configuration........................................................................................................5 2.2 S/W Configuration.......................................................................................................11 3. Functions...........................................................................................................................13 3.1 Main functions of BTS ................................................................................................13 3.2 H/W Configuration and Function.................................................................................15 3.3 Configuration and Functions of S/W...........................................................................34 3.4 Call Control ................................................................................................................41 3.5 Handoff Control Function............................................................................................50 3.6 Authentication ............................................................................................................56 3.7 Location Registration Function...................................................................................62 4. Lower Subsystem Description...........................................................................................65 4.1 ECMS.........................................................................................................................65 4.2 RCCS.........................................................................................................................74 5. Structural and Environmental Conditions..........................................................................81 5.1 Structural Features.....................................................................................................81 5.2 Environmental Conditions...........................................................................................81 6. Abbreviations ....................................................................................................................82
Issue 1. 04/00
LGIC Confidential and Proprietary
1. General
1.1 Overview
Compact BTS(C-BTS) is located between MS and BSC in the STAREX-800, a personal communication system adopting CDMA digital mobile communication technology, and it controls calls for MS and performs maintenance function. In other words, C-BTS guides MS to recognize BTS at first and sends necessary data. It allocates traffic channel upon call request and opens call path. BTS is designed to be extended to 4 FA in terms of capacity extension and maximum 48 BTS can be accommodated on one BSC. Main functions of C-BTS are as follows; Call control and Cal resource management Loading Configuration and operating information processing Fault handling Statistics, overload measurement and control Radio signal processing, radio ling test and TPTL Packet routing and transmitting Inventory Remote Control
Issue 1.04/00
1.2 Specification
1.2.1 General Specifications
Item C-BTS Types Traffic Channels Capacity per Sector Specification Up to 4FA/3Sectors More than 13Chs/Sector/FA 13K QCELP Vocoder Traffic Handling Capacity per Sector More than 9.0 Erlang/Sector/FA BP=2% No. of Channel Elements per Board Environmental Requirements Rack Size No. of Receiver Antenna Frequency Band Operating Temperature Limits Relative Humidity Limits 0 ~ 50oC 5 ~ 95% 750Wx650Dx1,886H (mm) 2EA/Sector Downlink (MS BTS) : Uplink (BTS MS) : 20 Channel Elements
824~849MHZ 869~894MHZ
Issue 1.04/00
1.2.2 RF Specifications 1.2.2.1 Receiver Specifications

Parameter Operation Band Diversity Frequency Transition RF Interface Noise Figure Sensitivity Dynamic Range 824 ~ 849 MHz Dual Diversity on Rx Straight Transition of license Block operation 50 nominal impedance 5dB (Max) FER is 1.0% or less with 95% confidence. FER is 1.0% or less with 95% confidence. -117dBm per RF Input port not less than -65dBm/ 23MHz in AWGN and Eb/No of 10dB 1dB Conducted Spurious Emissions Less than -80dBm in 30kHz RBW, RX Band. Less than -60dBm in 30kHz RBW, TX Band. Less than -47dBm in 30kHz RBW, all other frequencies. IS-97-A Description Comments
Issue 1.04/00
1.2.2.2 Transceiver Specifications

Parameter Operation Band Frequency Transition Frequency Tolerance Pilot Time Tolerance Pilot Channel to 869 ~ 894MHz Straight Transition of license Block operation Within 5 x 10-8 of the FA ( 0.05ppm) 10s Code The time error between the Pilot Channel and all code channels comprising the Forward CDMA is within 50ns Pilot Channel to Code The phase differences between the Pilot Channel and all code channels sharing the same Forward CDMA shall not exceed 0.05radian Waveform Quality is greater than 0.912 (excess power < 0.4dB) Total Power Code Domain Power within +2dB and -4dB of nominal power 27dB or more below the total power in each inactive channel Conducted Emission Spurious -45dBc 750kHz @30kHz RBW -60dBc 1.98MHz@ 30kHz RBW -13dBm 3.125MHz@ 100kHz RBW IS-97A Channel Phase Tolerance Description Comments
Channel Time Tolerance
Issue 1.04/00
2. Architecture
2.1 H/W Configuration
Standard BTS is composed of 5 blocks - ECP, BTR, RCB, LPA, FEC. The configuration and the mounting diagram of standard BTS(4FA/3sector) is as follows;
SBCR
6U FECU
BLANK (0.5U)
SBCR
FECU
L P A U / D L P A U / D
FECU
BLANK (0.5U) L L P P A A U U / / D D
FECU
L P A U / D L P A U / D
8.5U
LPA-D
,,
BLANK PANNEL(1U)
BLANK PANNEL(1U)
2U 6U
FAN(500005) RCB(6U) (3rd ~ 4th) RCB(6U)

P S U / I
FAN(2U)
RCBB-S M MM MM MM MM M R CCCCCCCCCCC PPPPPPPPPPP AAAAAAAAAAA 2 2 2 2 2 2 2 2 2 2 / 0 0 0 0 0 0 0 0 0 0S MMM MM MM MM M R CCCCCCCCCCC PPPPPPPPPPP AAAAAAAAAAA 2 2 2 2 2 2 2 2 2 2 / 0 0 0 0 0 0 0 0 0 0S BSBB-P P S U / G EEB CCA P PM AAA B A D A / D BB EE L L NN AA I I NN AA KK P S U / G R C P A / S R C P A / S B U D A / D B U D A / D
B T M A / C B T M A / C
B U D A / D B U D A / D
G P S M G P S M
P A C A / D P A C A / D
P S U / I
RCBB-S P S U / I P S U / I
6U
(1st ~ 2th) ECP(6U) B T R BLANK
6U 2U
C G P S
BLANK
FAN(400006)
FAN(400006)
Height:38U
Configuration & Mounting diagram of standard BTS
Issue 1.04/00
2.1.1 ECP (Enhanced Control Processor Block)

ECP block is mounted on the standard BTS and performs downloading, call control, alarm collection and maintenance functions. It also has trunk interface function between BTS and BSC and packet routing and interface function for the packet exchange. H/W is composed of ECPA (the master processor), BAMA (collecting alarms in BTS and performing maintenance function), ENIA (network of BTS), BADA (performing mobile simulation and diagnostic functions), BSBB (supplying power and physical channel), and LICD for trunk interface with BSC.
B S B B P S U / G E C P A E C P A B A M A B A E E D N N A I I / A A D P S U / G
Mounting Diagram of ECP
B U
S T IP / R IN G
P S T N
E N IA E N IA T A X I R S 4 2 2 B U S E C P A B A M A B A D A D
B S C
4 4
T 1 / E 1 T 1 / E 1
T A X I
T A X I
T A X I
R S -
S h e lf 4 2 2
R C
P A
R C
P A
B T M
B U
Structure of ECP
Issue 1.04/00
(1) ECPA : the master processor of BTS (2) BAMA : collects alarms in BTS and performs maintenance function (2) BADA : performs mobile simulation and diagnostic functions, makes diagnosis on BTS and measures Tx/Rx antenna VSWR (4) ENIA : network of BTS (5) LICD : trunk interface with BSC (6) BSBB : backboard of ECP block
2.1.2 BTR (BTS Timing Reference Block)

BTR is mounted on C-BTS and composed of BTMA which provides BTS system synchronization and clocks by using TOD received by GPS and synchronization signal, and CGPS which consists of GPS engine, power supply, OCXO and the controller. BTMA receives 10MHZ (sine wave), 1PPS (TTL) and TOD (Time of Day) from CGPS and broadcast TOC through IPC link in BTS. BTMA is operated in duplex and all signals between CGPS and BTMA are linked through the back plane. BTMA and CGPS use their own on-board power supply.
s p lit t e r
ECPA
B T M A B T M A
10M H Z C G P S C o n tro l CG PS
R S -4 2 2
M BU S BTM A BAM A R e m o te C o n tro l
T O D /1 0 M h z /1 P P S
Mounting Diagram of BTR Structure of BTR (1) BTMA : provides synchronization and clock for BTS system (2) CGPS : provides 10MHZ, 1PPS and TOD, and controls two GPS modules
Issue 1.04/00
2.1.3 RCB (Radio Channel Bank Block)

RCB block is mounted on standard BTS of C-BTS and performs CDMA channel modem function, channel distribution function, RF signal up/down conversion function and Tx power estimation function. H/W is composed of MCPA, RCPA, BUDA and PACA. MCPA is responsible for the overhead channel and traffic channel of BTS and RCPA is responsible for the maintenance of RCB block. BUDA functions as an up/down converter and PACA measures the power of the forward link.
R C P S U / I M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 M C P A 2 0 R C P A R C P A B U D A / D
B B B U D A / D B U D A / D B U D A / D B U D A / D B U D A / D P A C A / D P S U / I
Mounting Diagram of RCB
P a c k e t
S e r ia l
B U
0 M C
. . 9 . R C P A B
D P A C A D
P A 2 0
U D A ( 1 F A )
B U D A ( 2 F A )
R S -
4 8 5
A s y n c .T A X I / D
L P A U
E N
IA
Structure of RCB
Issue 1.04/00
(1) RCPA : RF device control, base-band digital combining of the forward link (2) MCPA20 : functions overhead channel and processes digital signal for CDMA channel (3) BUDA : frequency conversion of Tx/Rx signal, A/D Conversion (4) PACA : monitors transmitting output level change (5) RCBB : back board of RCB block
2.1.4 LPA-D (Linear Power Amplifier Block D)

LPA-D is mounted on standard C-BTS and composed of 6 units of LPAU-D. LPA-D amplifies the signal to enable remote MS to receive up converted CDMA signal. LPAU-D performs data interfacing with RCPA and informs the status of LPAU-D. It also performs several commands - enable/disable, status request or version request. Through a separate H/W line, it sends alarms (mount/dismount alarm, power on/off alarm) of LPAU-D to RCPA.
L P A U / D
L P A U / D
L P A U / D
L P A U / D
L P A U / D
L P A U / D
Mounting Diagram of LPA-D (1) LPAU-D : amplifies Rx signal
2.1.5 FECU (Front-End Block)

FECU is mounted on standard C-BTS and this is the from-end device of duplex type. FECU is composed of 3 units of FECU. 4 FA can be covered for receiving. Alarms of FECU are sent to BAMA in TTL signal format.
Issue 1.04/00
F E C U A lp h a
F E C U F E C B e t a G a m
U m
Mounting Diagram of FED (1) FECU : front-end module for compact BTS type
Issue 1.04/00
10
2.2 S/W Configuration

BTS S/W is composed of 2 subsystems ECMS and RCCS.
E ( R C
R C S )
S B (
P S V C S V C S
) M S C
E C ( E C
P M S )
C ( C
C C
P M S ) V L R
B
B T S
T S
S C
S C
S C
: : :
T r a f f ic S ig n a llin g C o n t r o l
S M
S T A R E X -
8 0 0
S S
<S/W Configuration of BTS and BSC>
2.2.1 ECMS (Enhanced BTS Call Control & Management) Subsystem

ECMS subsystem sets and releases mobile calls, and manages mobile call resources. ECMS also performs operation & maintenance functions downloading, status management, configuration and operation information change, fault handling, remote control, inventory, testing with BADA, overload control, statistics, etc.
Issue 1.04/00
11
2.2.2 RCCS (Rf & Channel Control) Subsystem

RCCS subsystem controls MCPA and BUDA, and processes digital signals and calls for J-STD-008 CDMA channel. It also performs operation & maintenance functions such as channel element downloading, device status management and statistics. It controls and manages all RF devices such as BUDA frequency synthesizer control, LPAU enable/disable, etc. RCCS measures AGC/RSSI level and performs RF power control such as Tx gain control for the whole sector.
Issue 1.04/00
12
3. Functions
3.1 Main functions of BTS
Main functions of BTS subsystem are as follows; 1) Call Control BTS subsystem sets and releases mobile-to-land, land-to-mobile or mobile-to-mobile calls in BTS by interworking with MS and BSC. It also supports softer, soft and hard hand-offs. Markov calls to set testing calls are also processed here. 2) Call Resource Management BTS subsystem disperses and selects the load of the channel element, which is necessary for call setting. When releasing a call, it withdraws the load of the channel element. It also reserves dedicated information for hand-off for a stable hand-off according to the frequency of hand-off occurrence. 3) Downloading BTS subsystem downloads necessary OS for each processor and the application code from the upper processor. If the version of OS or the application code is same, it does load but OS or the application is transferred from the flash memory, a nonvolatile memory. This finally prevents unnecessary loading time and reduces BTS initialization time. After downloading application code, ECP builds database regarding its status, configuration and operation with PLD data directly transferred from BSM. Then it sends configuration information necessary for initialization to the lower processor, RCP. 4) Configuration and Status BTS subsystem manages processor status, device status, configuration information and operation information for the operation and maintenance of BTS. ECP interworks with RCP, a sub-processor, and upper BSC and BSM, and performs operation and maintenance functions for the whole BTS. 5) Fault and Alarm Handling BTS subsystem handles H/W faults power failure, processor fault, cable removal- and S/W faults which does not need H/W device to detect faults. RCP in BTS detects device faults and alarms in its management area and reports them to ECP. Then ECP reports them to the upper part with proper measures.
Issue 1.04/00
13
H/W faults are detected through BAMA and reported to ECP. 6) Testing Regarding the channel element (especially the traffic channel), BTS subsystem periodically tests the available resources on-line to improve reliability of the resource. With the test result, BTS decides whether the resource is going to be used or not. Test is also available upon operators request. There are two CE test CE H/W test and a test with BTS Markov calls. The operator can understand the call status in BTS with BADA. 7) Overload Control There are four levels - Normal, Minor, Major and Critical according to processor loading. BTS subsystem takes proper actions for each level such as origination prohibition, origination/termination prohibition. 8) Statistics and Measurement BTS subsystem collects various statistics call statistics, process statistics, paging statistics, CE (Channel Element) statistics, BTS performance statistics and CAI (Common Air Interface) statistics- and reports them. The statistics are collected every hour basically and reported to BSM. If necessary, the operator can set the time and cycle for the measurement. 9) Remote Control BTS subsystem separates or resets the shelf power, processor or device. perform the command. 10) Inventory This is to manage the history of each board. BTS subsystem manages history (CN application, repairing history or remarks) of a certain board and BTS. When the operator commands separation or reset on BSM, ECP identifies the subject (BAMA or RCP) and sends the message to the subject to
Issue 1.04/00
14
3.2 H/W Configuration and Function

3.2.1 H/W Configuration
o m
p a c t
B T S ( S t a n d a r d )
E C
E C
P
P A A A
B T R
B T M C G A
R C
M C R C B U
B
P A 2 0 P A D A A
L A P
L P A U
F E C
F E C
U
U
B A M B A D E N IA
P S
P A C
L IC
R C
B B
B S B B
Issue 1.04/00
15
3.2.2 Functions for Each H/W Unit

3.2.2.1 ECP (Enhanced Control Processor Block) (1) ECPA (Enhanced Control Processor circuit board Assembly) ECPA is mounted on ECP block of BTS and duplexed. ECPA functions as the master processor of BTS downloading from the upper part, loading to the lower processor, controlling MS calls and managing BTS status. It has packet routing function for the packet exchange in BTS and provides the packet node and path. The block diagram and main functions of ECPA are as follows;
B
M C 6 8 3 6 0
B u f f e r S R A M
S C
R X ( 8 )
P a c k e t
T X ( 8 )
F I F O
2 T 1 / E 1
( F
L I C r a m
D e r , L I U )
M P a c k e t F I F O
T M
L A
- T
u r n
I F
A M
6 8
0 3 0
F P a c k e t I / F ( C P U S la v e ) I F O
E N I A
R S R
O A
M M F I F O
E X T
? ? ?
L A
M
P O R T
B u s
h e lf
u s
I n te r n a l B u s O th e r S id e
S h e lf
B u s
E C
P A
B lo c k
ia g r a m
ECPA has mainly two kinds of functions ECP function and NMM-P function. ECP function is composed of 68030 local processor function, shelf bus master function, duplexing function, packet bus slave node function and M-Bus interface function. NMM-P function is composed of 68360 local processor function, network master function, trunk interface function, packet bus slave node function and M-Bus interface function.
Issue 1.04/00
16
Local processor function is composed of the local resource (RAM, ROM) and I/O (MC68901) centered on MC68030, and has the actual ability to perform and control the program. Shelf bus master function is composed of 8Bit parallel bus and used for the communication with BAMA and BADA. Duplexing function is composed of command channel and data channel, and the function is implemented in the warm standby method. Packet bus slave node function provides IPC data channel of ECP and this is duplexed. M-Bus interface function is the maintenance bus and operated by BAMA, M-Bus Master. And BAMA can initialize ECP H/W remotely. NMM-P function is composed of local resource (RAM, ROM) centered on MC68360 and has local processor function performing and controlling the program. Network master function is the master of the packet bus that is operated in 8 bit full duplex bus. It allows transmitting and receiving of total 10 nodes and has maintenance function. Packet bus slave node function provides NMM-P with IPC data channel. M-Bus interface function is composed of BAMA (M-Bus master) and RS-485 interface. ECP functions MC68030 core IPC slave node Duplexing Shelf bus master M-Bus interface
NMM-P functions 68360 core IPC slave node M-Bus interface Network master
(2) BAMA (BTS Alarm collection & Maintenance board Assembly) BAMA is located in ECP block of C-BTS and its main functions are collecting and reporting alarms in BTS, remote control, BSM accessing through PSTN (modem) and BTS maintenance. The block diagram and main functions of BAMA are as follows;
Issue 1.04/00
17
D R A M (4 M ) 1 M x 3 2 B it
B o o te r F la s h ( 5 1 2 K ) 5 1 2 K x 8 B it
A p p lic a t io n F la s h ( 5 1 2 K ) 5 1 2 K x 8 B it
T im e K e e p e r(2 K ) 2 K x 8 B it
CPU M C68360
IP C RS232 RS422 56K M O DEM M CU M DP DAA RS485 N IM 2
S h e lf B U S SRAM (6 4 K x 8 ) A r b it e r
R e m ote C trl FPG A
A la rm FPG Ax2
RS422
B u ffe r
B u ffe r
A la r m B u ffe r (A B M )
EDU ( O u t d o o r O n ly )
M -B U S
R .C (2 4 )
A la r m ( 1 8 0 )
D ebug P o rt
PSTN
BTM A
E N IA
ECPA
O th e r C ir c u it B o a r d
B A M A B lo c k D ia g r a m
Collecting and Reporting H/W alarms in BTS BAMA can receive maximum 180 BTS H/W alarms (Cable alarm: 158, Shelf alarm: 22) including reserved 16 pins and the collected alarms are sent to ECPA through IPC (RS-422/HDLC). Remote Control Power pack on/off is available through BAMA and the processor in each board can be restarted. Maximum 24 units can be restarted. The electric standard is TTL. When TTL is high, power pack is off or the board is reset. When TTL is low, the power pack is on or the board is running.
Issue 1.04/00
18
BSM Accessing through User I/F (PSTN) Modem BSM (Workstation or PC) can access to BAMA through PSTN. BSM can check the status of BTS, perform remote control and make a diagnosis on the boards of BTS. The protocol of the modem is V.90 and the maximum speed is 56Kbps. BTS Maintenance (by Maintenance Bus and EDU Communication) BAMA functions as master of the maintenance bus checking board status in BTS and managing boards. M-Bus is HDLC bus type configuring with a master and several slaves. Each slave performs CTS control so collision among slaves does not happen. The electric standard is RS485. S/W alarms and the status of EDU are communicated through a separate RS-422/HDLC.
(3) BADA (Base station Analyze & Diagnostic Assembly) BADA functions as mobile simulator and performs DM function of the mobile simulator. BADA in RF-matrix structure selects RF path routes and performs path testing. The block diagram and main functions of BADA are as follows; Checking the status of Tx/Rx parts of BTS Checks the status of BTS with Markov calls. Measuring Tx antenna VSWR Measures Tx antenna VSWR features of BTS by measuring power of the forward port and reverse port of the antenna coupler. Measuring Rx antenna VSWR Measures Rx antenna VSWR features of BTS by measuring and comparing the adjust during call setting with forward port and reverse port of the antenna coupler or comparing with measuring Tx power of the mobile simulator.
Issue 1.04/00
19
M O S im
B I L E u l a t o r C O A X IA L
R M B
F A T L O
R C
I X K
C C
O O
A A
R F S I G N A L X I A L 1 8 E A X I A L 1 2 E A
F
F O F( D O
R
C
R RI
O
R O U
N
P
T
L E
- E
N R )
N
A
S I M P L E X D E U CP L T E I XO
+ 5 V 5 V
P R P O L A Y E W
O G
W U E R
S _ P W R _ S W S _ P R E _ S W
CONTROL & STATUS
M S _ P O W TE XR D _ M S R X M S _ P R O G _ D E _N M S
L P AR OT
S P _ S T S * E I _O S TN S *
A O
D N
L E D
D T
R R
: 7 ) * D *C *
E O
S L
S R
D E
C O D I N G G T OI S W T E R R O B E T P
-
P E N
L E D I S
D P
L E D
F A IL
C A ( 0 T X D _ M CP A S R X D _ M CP D S C W R
M F A IL F ( 0 : *7 ) O
A IL * P E N
M B W U S E R T T L T R X T O P T O
IT C T T L 1 2 L I MN -E B U S T R X R S 4 2 2
& A NN A K S W L
&
F A IL
H B
C A OM N AT R O L
L IN P S I N M U W S H N H
L E D
T T L
_ R E S E T *
T R
B ( B A D A
C C
D B o n t r o l
a u g h t e r
E X T E R N A L R F RX A N C - U N I T E X T E R N I V E R U N I T C O N T R O L T R X R S 4 2 2
o a r d )
V E O N P O V E R M O N P O ( 9 P
T O R R S Y2 3 2 I T O R R T S I O N T I T OT R L E E R T ( O P E N D R A IN ) I N )
SHELF ADDRESS BUS & S HELF DATA BUS

T B D
B E C O D I N G & R E G I S T E R B A
A N
D K
A &
C P
O O
N W
R O E R
B A D A
B lo c k
ia g r a m
(4) ENIA (Enhanced Network Interface circuit board Assembly) ENIA is mounted on ECP block of BTS and duplexed. As a network management processor, ENIA has network management function and packet routing function for the exchange of the packet in BTS, and provides packet node and path. ENIA is also responsible for TAXI Link I/F and Trunk I/F functions. The block diagram and main functions of ENIA are as follows;
Issue 1.04/00
20
R X (8 ) T X (8 ) M C 68360 (2 5 M H z )
F IF O TAXI I/ F P a c k e t I/ F (C P U S L A V E ) F IF O TAXI I/ F
ECPA
R O M
RCPA
D R AM F IF O TAXI I/ F Packet C o n tr o l
FLASH
M B u s I/F
BAM A
L IC D 4 T 1 /E 1 (F ra m e r ,L IU )
B r id g e
BSC
M -B u s
F IF O TAXI I/F
RCPA
E N IA B lo c k D ia g r a m
There are mainly two functions - 68360 local processor function of ENIA and NMM-P function. NMM-P function is composed of network master function, trunk interface function, TAXI interface function, packet bus slave node function and M-Bus interface function. NMM-P function has a local processor function performing and controlling the program with local resource (RAM and ROM) centered on MC68360. The network master function is the master of the packet bus that is operated in 8 bit full duplex bus. It allows total 10 nodes to transmit/receive and performs maintenance function. Trunk interface function converts parallel data into serial data and sends to LICD board which functions trunk interface. This function also controls LICD board. TAXI interface function sends data with high speed of 80 Mbps with using TAXI transmitter/receiver of AMD. TAXI link is implemented in cross duplexed. Packet bus slave node function provides IPC data channel to NMM-P. interface function is composed of BAMA (M-Bus master) and HDLC bus. M-Bus interface function is a maintenance bus and operated by BAMA (M-Bus master). It initializes H/W of ENIA remotely. M-Bus
Issue 1.04/00
21
NMM-P functions - 68360 local processor - IPC slave node - M-Bus interface - Network master - Trunk interface - TAXI interface
(5) LICD (Line Interface Control Daughter board) LICD is a trunk interface daughter board which is mounted in BSBB back plane of BTS. LICD has 4 units of T1/E1 trunk link lines to transmit/receive T1/E1 packet between ENIA of BTS and CITA of BSC. The built-in framer of LICD selects T1 and E1. Four units of links should be used as T1 or E1. The following is the block diagram of LICD.
C o n tro l FPG A
C o n t r o l S ig n a l
C o n t r o l S ig n a l
M C68360
B u ffe r
C o n tro l D a ta B u s
FRAM ER X 4
E C P A /E N IA
R S -4 2 2
L IU X 4
TR TR TR TR
A A A A
N N N N
S S S S
E1
RELAY
E1
BSC
OSC
L IC D
O THER BTS
L IC D B lo c k D ia g r a m
(6) BSBB (BTS Standard Back Board) BSBB is the back board of ECP block mounted on C-BTS. Based on 2 units of power board (LCP-A), 2 units of ECPA, 1 unit of BAMA, 1 unit of BADA and 2 units of ENIA, BSBB is designed in a way that maximum 4 units can be mounted. Also the trunk interface function is mounted on the back of BSBB in daughter card (LICD : Line Interface Control Daughter board) type. Each card has the capacity of 4 E1/T1. BSBB is a multiple board (14 floors) PBA and the size is appropriate to be mounted on the standard shelf of CBTS. The dimension is 294.5mm x 254.0mm x 3.2mm and te design allows BSBB to accommodate board of ECP block in standard C-BTS. To minimize crosstalk between signals and the reflection effect of the signal line end, BSBB is designed in a way
Issue 1.04/00
22
that layers and TTL signals have 50 Ohm of pattern impedance and the differential signals have 110 Ohm of pattern impedance. 3.2.2.2 BTR (BTS Timing Reference Block) (1) BTMA(BTS Timing Management circuit board Assembly) BTMA receives 10MHZ(TTL), 1PPS(TTL) and TOD(Time of Day) from CGPS and broadcasts TOD through IPC link in BTS. BTMA is operated in duplex and the signals between CGPS and BTMA are linked through back plane. BTMA uses on-board power supply. The block diagram and main functions of BTMA are as follows;
A [ 2 : 1 3 ] D A [ 1 8 : 2 1 ]
[ 0 :A 3 [ 1 0 ] : 1 8D ] [ 2 4 A: 3[ 10 ]: 1 8 D ] [ 2 4 : 3 1 ] s h F l a s h o r y M e m o o t e r - ( A p p l i c b i t ) 4 M b i t K B y t e5 1 2 K B
R S 4 8 5 t o B A M
- B
A [ 0 : D2 [1 0] : 3 1 ] M 6 8 E M ( 3 . 3 V ) C 3 6
C
a i n M e m o F r yl a M e D R A M B ( 1 6 M b i t x 2 E ( A -o 4 t Me 30 2 b i t ) - 4 M B y 5 1 2 M
r y a t i o ) y t e
R S 2 3 2 C
e b u p o r t
v e P o n r t t o
g
r y
S 1 ( R A S 1 ) C S 0 C S 2
T T L
I 2 C
I n
F
C S 5
R M G
/ E V
F R O G P S
1 0 M h z [ T T L ] 1 P P S [ T T L ] T O D [ T T L ] ( S
a u l t & e d u n d a n c y a n g e m e n t B lo c k S Y S _ C L K /
P
[ T T
E
L ]
N / F F o BT A M
/ P A
c n
W
t r l
R e d u n d a n t s i g n oa lt h o e r t { T T L ]
s i d e
T
Y
i m i n g B lo c k
S _ C L K
e n E V E N
E N _ S E C ) 4
_ S E C
P O R T [ P - E C L ] T oR C P A
R S 4 2 2 ( T X ) R S 4 2 2 ( T X ) R ( R S 4 X 4 X 2 ) 2 ) 2
A T B T o
L o E L E
I N C I N C P
K P K A A
L C
R ( R
B T M
Main Functions Clock generation - SYS_CLOCK/EVEN_SEC - p-ECL interface GPS interface - TOD / Control / Alarm / 1 PPS / 10 MHZ - TTL interface
B lo c k
ia g r a m
Issue 1.04/00
23
MBUS interface - Power on/off - RS485 interface IPC - Interface with NIM2 ASIC - RS422 Serial Interface
Interactions Interface between BTMA and CGPS is as follows;
Clock Interface : provides 1PPS and 10Mhz (from CGPS) TOD, Control TTL Interface : provided to BTMA through back plane Alarm Interface : Receives GPS H/W alarms (Open / Power fail / Function fail) from CGPS and provides them to BAMA.
(2) CGPS (Compact BTSs Global Positioning System) CGPS provides 10 Mhz (TTL), 1 PPS (TTL) and TOD (Time of Day - TTL) to BTMA. All signals between CGPS and BTMA are linked through back plane and CGPS uses own on-board power supply. The block diagram and main functions of CGPS are as follows; CGPS provides following functions with visual information from GPS satellite.
10 Mhz, 1PPS, TOD generation Control port, Alarm interface Redundancy control Fault monitoring
CGPS has external interface input/output through back plane and internal interface with the connection between CGPS and BTMA.
External Interface
- 10 Mhz (sine wave-50 ohm-SMB) --- 3 port - 1 PPS (TTL,50 ohm-SMB) - TOD (RS232C-9 pin D-sub) - ANT (TNC Female) - PWR --- 1 port --- 1 port
- Control (RS232C-9 pin D-sub) --- 1 port --- 2 port --- 2 port
Internal Interface
- 10 Mhz (TTL-50 ohm) ---- 2 port - 1 PPS (TTL,50 ohm) --- 2 port
Issue 1.04/00
24
- TOD (TTL,50 ohm) --- 1 port - Control (TTL,50 ohm) --- 1 port
1 0 M h z / S in e w a v e / S M B
1 P P S /T T L /S M B
T O D [ R S 2 3 2 C ] / 9 P in D - S u b
CG PS
C o n t r o l [ R S 2 3 2 C ] /9 P in D - S u b
A N T /T N C
P o w e r/2 0 ~ 6 0 D C
C G P S B lo c k D ia g r a m
3.2.2.3 RCB (Radio Channel Bank Block) (1) RCPA (Radio & Channel Processing board Assembly) RCPA performs base-band digital combining of the forward link and parity checking and generation of the backward link. RCPA also distributes the timing of the digital shelf and the standard frequency. Lastly, it also controls RF devices. RCPA consists of Core Control Module (CCM) interfacing with CPU (i960), ESCC in charge of monitor interfacing through RS-232, memory controller controlling memory, HDLC in charge of duplexing the board, and peripheral controller in charge of interfacing of peripheral devices of the board. 6 units of CSM (Cell Site Modem) ASIC corresponding to CDMA code channel or ECM ASIC control are equivalent here. The block diagram and main functions of RCPA are as follows.
Issue 1.04/00
25
P r o c e s s o r C o re R e g io n B o o t & C o n t r o l R e g io n
A d d r & D ata
CH ANNEL PRO CESSOR i9 6 0 C F - 4 0 (IN C L U D IN G D M A )
In t e r r u p t S ig n a l
C o n t ro l
B u s & In t C o n tr o l & S t a t u s M o d u le & M o n i t o r in g P o r t & P h e r ip h e r a l C o n tro l
P h e r ip h e r a l R e g io n
CSM In t e r r u p t s S ta tu s
1 F P G A M e rg e : S IM
T im in g & 6 S e cto r C D M A D a ta C o n tr o l/In te r fa c e
H O T l in k T r a n s c e iv e r pECL & C lo c k B u f
F ro m /T o R C B T X D a ta R X D a ta T im in g S ig .
M e m o ry & D u p le x R e g io n
Ca che C o n t o lle r ( 0 - w a it P / B u r s t )
F L A S H M e m o ry (B a c k u p m e m o ry )
EPROM ( B o o t & Jig )

32 1M x 32 D R A M B a n k ( w / P a r it y ) & 25 6K B C a ch e 32 In t e r -b u s B u f & F IF O 16
16
S P I In te rfa c e M o d u le
pECL T r a n c e iv e r
B U D A /P V M A C o n t ro l b u s
S h e lf & H P A In te r fa c e M o d u le
S h e lf & H P A A la r m /O p e n /R e s e t
B o a r d D u p le x e L in k (H D LC )
P a c k e t In te r fa c e M o d u le
B u f fe r
TAXI T r a n s c e iv e r
P a r a l le l P a c k e t b u s In t e rf a c e w ith M C P A T A X I In t e r fa c e w i t h E N IA
In t e r - R C P A D u p l e x B a c k u p P a t h RS232 f o r In v e n t o r y
S e r ia l EEPR O M
S IO
RS485 T r a n s c e iv e r
H P A In t e r fa c e
CPU BU S
F ro n t P a n e l
I/O B U S
RCPA Block Diagram Core Control Module (CCM) Interrupt Control DMA Control Timer Control port
ESCC RS-232 Monitor Interface
Memory Controller DRam, Cache RAM, Tag RAM Control Cache mode control between cache RAM and DRAM Flash Memory Control
HDLC NIM2- Board Duplex Peripheral Controller
Issue 1.04/00
26
CSM (Cell Site Modem) ASIC or ECM ASIC Modem Chip CDM - CDMA Date interface Control SDM Self states Detecting Module (Open/Fail) Packet interface between PIM and MCPA STM System Timing LPA SIO LPA Interface SIM BUDA, PACA Interface
(2) MCPA20 (Multi-Channel Processing board Assembly 20) MCPA20 is a board covering overhead channel (Pilot, Sync, paging and Access channel) and maximum 20 traffic channels. MCPA20 is composed of Core Control Module (CCM) interfacing with CPU (i960), ESCC in charge of monitor interfacing through RS-232, memory controller controlling memory and peripheral controller in charge of interfacing of peripheral devices in the board. The block diagram and main functions of MCPA20 are as follows.
P r o c e s s o r C o r e R e g io n B o o t & C o n t ro l R e g io n
A d d r & D a ta
20 units of CSM (Cell Site Modem) ASIC
corresponding to CDMA code channel or ECM ASIC control are equivalent here.
CH PRO i9 6 (IN C L U
AN NEL CES SO R 0 C F -4 0 D IN G D M A )
In t e r ru p t S ig n a l
C o n tro l
B u s & In t C o n tr o l & S t a tu s M o d u le & M o n it o r in g P o r t & P h e r ip h e r a l C o n tr o l
P h e r ip h e r a l R e g io n
CSM In t e r r u p t s S ta tu s
5 C S M G ro u p 1 (C S M 1 ~ 4 ) 2 3 4
M e m o r y & D u p le x R e g io n
Cache C o n to lle r ( 0 - w a it P / B u r s t )
F LA S H M e m o ry (B a c k u p m e m o ry ) D TM C D M A T X D a ta In t e r f a c e & T i m in g H O T li n k T r a n s m itt e r r pECL & C lo c k B u f
TX D ata
EPRO M (B o o t & Jig )

32 1M x 32 D R A M B a n k ( w / P a rit y ) & 256KB Cache 32 In t e r -b u s B u f & F IF O 16
T im in g S ig .
16
RD M C D M A R X D a ta In te rfa c e
H O T lin k R e c e iv e r
R X D a ta F ro m R C P A
B o a r d D u p le x e L in k (H D LC )
P a c k e t In te rfa c e M o d u le
B u ffe r
P a r a lle l P a c k e t b u s In t e r fa c e w ith R C P A
RS232
f o r In v e n t o r y
S e r ia l EEPRO M
CPU BUS
F ron t Pan e l
I/ O B U S
B a c k p la n e In te r fa c e
MCPA20 Block Diagram Main configuration of MCPA20 is as follows;
Issue 1.04/00
27
Core Control Module (CCM) Interrupt Control DMA Control Timer Control port
ESCC RS-232 Monitor Interface
Memory Controller Dram , Cache RAM, Tag RAM Control Cache mode control between cache RAM and DRAM Flash Memory Control
Peripheral Controller CSM (Cell Site Modem) ASIC or ECM ASIC DTM - Timing & CDMA Date interface Control Packet Interface between PIM and RCPA
(3) BUDA (Base station sector conversion & Up/Down converter Assembly) BUDA is mainly divided into shared part, Tx path and Rx path. The block diagram and main function of BUDA are as follows.
Issue 1.04/00
28
RX B
B P a th
IQ DEMO D HO T L INK TO RCPA
RX
ATT RX A
RF F ro n t b lo c k
IF B lo c k
IF A t t . B lo c k
AM P AGC Ci rcuit BPF AMP
FPGA
DA C
D e te c to r
D ig ita l In te r f a c e
Loc al O s c ila to r
REFIn put
TX
DAC From RCPA H OT LIN K FPGA DAC TX_O UT IQ MO DUL ATOR B LO CK C oup le r
TX IF B LO C K
BPF ATT AM P
TX I F Det ec tor & TX AG C CIRCUI T
T X O UT DETEC TI ON CIRCUIT
BUDA Block Diagram

Main Functions of Tx/Rx Frequency up conversion transforming baseband signal into IF/ RF signal. RF signal output control by gain control. Tx AGC (Automatic Gain Control): maintaining gains of receiving part regularly to keep its output. Rx AGC (Automatic Gain Control) IQ demodulator
BUDA (Baseband Up Down Conversion Assembly) can be explained by Tx and Rx block. Tx block A/D transformed in BUDD (Buda Digital Daughter board) into IF signal in IQ modulator. The signal is transmitted to LPA with frequency up conversion in RF block. Receiving part converts the signal input from FEU (Front End Unit) in RF block into IF frequency after lowNoise amplifying, and inputs it on IQ demodulator block to send BUDD. The converted signal into baseband is again D/A converted and sent to RCPA or MCPA. BUDA status reporting and PLL synthesizer frequency setting are processed in RCPA and digital interface block. (4) PACA (Power Adjust & Control Assembly) RF path, which can accommodate 2FA/3SECTOR, is mounted on PACA so that it uses Rx frequency functions by FA with controlling PLL synthesizer to process Muti FA signal. PACA monitoring final Tx output level change by converting the final output signal of the sending path to receiving RSSI electronic power. The block diagram of PACA and its main functions are as follows;
Issue 1.04/00
29
Sensing Tx output Temperature reading DC power fault detection 10MHz reference signal detection
PLL synthesizer part receives control signal of the decoding circuit and generates local signal for frequency down converting of RF signal into IF signal. PACA reports the present temperature of the board to PCPA. It receives final Tx output signal from front end and converts it into IF signal. Then it sorts signal and reports RSSI electronic power of interested signal to RCPA.
1FA ALPHA PATH 1FA BETA

1FA
BPF
1FA GAMMA LOCAL
PATH
PATH
ATT
GAMMA
AMP
PLL
AM P
PVPD-EL
4 WAY DIVIDER
1FA ALPHA LOCAL 1FA BETA LOCAL SAMPLE PORT
A/D CONVERTER
RCPA
THERMAL SENSOR
10MHz
4 WAY DIVIDER
EEPROM
PVPD-EL PLL 4 WAY DIVIDER
1FA ALPHA LOCAL 1FA BETA LOCAL 1FA GAMMA LOCAL SAMPLE PORT
2FA 2FA 2FA

CGPS
ALPHA BETA GAMMA
PATH PATH PATH
PACA Block Diagram
Issue 1.04/00
30
(5) RCBB (Radio & Channel Bank Backboard) RCBB is a back board of radio channel block accommodated in C-BTS. It is designed to support max. 3 sectors. RCBB is designed to mount 2 power packs (PSU-I), 10 MCPA20s, 2 RCPAs 2, 6 BUDAs and a PACA. RCBB is the 16-layered multi back board with appropriate size to be mounted on the standard shelf. The dimension is 599.5mm x 254.0mm x 3.3mm. RCBB is designed to accommodate standard boards in RCB block of C-BTS. Signal connecting boards in RCBB are; HOT-link signal for CDMA signal transmitting, network signal for packet transmitting, timing signal divided into open, fail signal, system clock, even sec and sync signal in each board, cable connecting signal to be connected with other shelves and other necessary signals.. The signals above are with specific impedance of 50 Ohm to minimize reflection and cross talk. For differential signal, it is with specific impedance of 100 Ohm. To avoid reflection of signal, termination resistance is mounted. In the mean time, pull-up resistance is mounted to stabilize the signal. 3.2.2.4 LPA (Linear Power Amplifier Block) (1) LPAU-D (Linear Power Amplifier Unit D) LPAU-D is mounted on standard C-BTS. 6 units of LPAU-D are needed for 4 FA / 3sectors. A RCPA controls total 6 units of LPAU-D and Combiner. LPAU-D interfaces with RCPA through combiner. The data interface method is multi-drop and it uses RS-485. Other H/W alarm signals use TTL level. LPAU-D receives commands - enable/disable, status request and version request - from RCPA and performs them. On status command, it reports LPAU-D status with data interface line (control pin #1 ~ #4). LPAU-D can be restarted by remote control signal being sent from RCPA.
Issue 1.04/00
31
The electric specification of LPAU-D is as follows;
Parameter Frequency Range RF Output Power Gain Variation over 30 ~ 47dBm Gain Variation over Operating Temperature IMD/Spurious @30W at LPAU-D output port DC Input **
Specification 869MHz to 894MHz 60Watts nominal 65 1.0dB 65 1.0dB for 0 to 60 C 31dBc/30kHz BW at 750kHz offset 45dBc/30kHz BW at 1980kHz offset Operating Range : 24 ~ 28V 30A Maximum at 27V ( 47.8dBm)
3.2.2.5 FEU (Front-End Block) (1) FECU (Front-End for Compact Unit) FECU is composed of a duplexer or receiving BPF (Band Pass Filter), sending BPF (BAND Pass Filter), sending channel filter, LNA (Low Noise Amplifier), a directional coupler and a large number of splitters. Main functions of FECU and the block diagram of FECU is as follows;
Receiving BPF (Band Pass Filter) of the duplexer filters receiving signal only of the bandwidth it needs. LNA (Low Noise Amplifier) supplies receiving signal to receiving port of BUDA for each FA after amplifying the signal as suitable one. LNA reports its own status to BAMA.
Issue 1.04/00
32
FECU
4W SP 4W SP
T X IN
PACA 1 PACA 2 PACA 3 PACA 4 PACA 5
TXF (2 5 M H z )
R X A S a m p le
4W SP
PACA 6 PACA 7 PACA 8 B A D A -A F W D T X S a m p le
RXF (2 5 M H z ) LN A D /C
RXA O UT1 RXA O UT2
ANT A (T X /R X )
B A D A -A R E V
D C /A la r m D C /A la r m B A D A -B F W D
RXB OUT1 RXB OUT2
LN A
R XF (2 5 M H z )
D /C
ANT B (R X B )
B A D A -B R E V
R X B S a m p le
<FECU Block Diagram>
Issue 1.04/00
33
3.3 Configuration and Functions of S/W

3.3.1 S/W Configuration Diagram S T A R E X - 8 0 0 S / W U n i t
o m ( 2 6
p a c t - B T S l o c k s )
B S C ( 5 1 B l o c k s )
M
E E E E E E E E E E E E E E M C R H
S
C C M C
C
R
C
M D
S
M M D M C M I M C C C L C
R M M R R R R P P A
C C D D P P
T C P D O D S C M M M N T F
T C K N
F A M T M S
3.3 2 S/W Block Functions

3.3.2.1 ECMS (Enhanced BTS Call Control & Management Subsystem) 1) EMC (Enhance BSP Main Control) Block EMC is the main function block of ECP and performs following functions. - Loading each block of ECP
Issue 1.04/00
34
- Loading PLD from BSM - Writing each block of ECP to Flash ROM - Managing common DB of ECP S/W 2) ECC (Enhanced BSP Call Control) Block ECC block processes BTS terminating/originating call setting, call controlling and call releasing, and main functions are as follows; - Setting and releasing terminating/originating calls of MS. - Authenticating terminating/originating call. - Collecting statistical data of call processing - Setting and releasing Markov call. 3) ERM (Enhanced BSP Resource Management) Block ERM block manages call processing resource and its main functions are as follows; - Initializing call processing resource in BTS for /Managing resource status - Allocating and releasing resource - communication channel, CDMA channel and frame offset. - Distributing resource equally. 4) EHC (Enhanced BSP Handoff Control) Block EHC block process handoff requests of BSC and main functions are as follows; - Identifying handoff type: soft handoff/hard handoff. - Processing softer/soft handoff: add/drop/swap. - Processing hard handoff: changing frequency/frame offset. 5) ETC (Enhanced BSP Transparent message Control) Block ETC block delivers/receives message to MS and main functions are as follows; - Processing registration message and delivering the result. - Processing order message. - Processing authentication message. - Processing data burst message. - Notification VMS. 6) EPM (Enhanced BSP Power Management) Block EPM block manages electric power and main functions are as follows; - PACA initial calibration - TPTL (Transmit Power Tracking Loop) calibration/traffic gain scaling - Effective radiated power limiting (LPA over power estimation)
Issue 1.04/00
35
- Blossoming/Wilting Sector 7) EDM (Enhanced BSP Device Management) Block EDM block performs supplementary function for BTS device OAM and main functions are as follows; - Remote H/W reset through BAMA. - Collecting and reporting Inventory. - Processing BAMA and BTMA keep-alive. - Gathering BAMA dismounting faults. - Delivering status message and control message of EDU 8) EOM (Enhanced BSP OAM Main Control) Block EOM block manages/controls blocks in ECP and main functions are as follows; - Running/stopping EMC sub-block. - Managing block status in ECP. 9) EDN (Enhanced BSP Downloading) Block EDN block downloads processors in BTS. The following is its main functions. - Downloading sub-processors - RCP, MCP - and MCP data. - Loading block. 10) EST (Enhanced BSP Status Management) Block EST manages status of all processors and devices in BTS and main functions are as follows; - Managing status of processors and devices - On-line and on-demand blocking/unblocking of over-head channel. 11) ECF (Enhanced BSP Configuration Management Block) ECF initializes ECP and processes ECP data and main functions are as follows; - Configuring and initializing ECP database. - Initializing RCP and CE. - Processing configuring/operating information. 12) EFA (Enhanced BSP Fault & Alarm Management) Block EFA processes BTS information and main functions are as follows; - Collecting and reporting H/W alarm from BAMA. - Collecting and reporting S/W alarm from RCP. - Collecting and reporting faults.
Issue 1.04/00
36
13) EMS (Enhanced BSP Measurement & Statistics) Block EMS processes various statistics in BTS and main functions are as follows; - Collecting and reporting statistics; on-demand, Hourly - Measuring and reporting processor load of ECP, handling overload; call restriction 14) ETM (Enhanced BSP Test Management) Block ETM block tests BTS and main functions are as follows; - Controlling BADA (Base station Test Unit) - BTS Markov call: on-line and on-demand - Channel element built-in test: on-line and on-demand - Measuring VSWR. - Mobile phone status output - TA (Temporal Analyzer) data output - Searcher/finger data output - Adjusting attenuator - Controlling sector selecting switch.
3.3.2.2 RCCS (RF & Channel Control Subsystem) 1) RMM (Rcpa Maintenance & Management) Block RMM block is composed of RCC_MainTask and RCC_StatusTask. RCC_MainTask performs initial update of DB by RCB configuration and channel DB conversion. If the updating is successful, RCC_MainTask generates RCC_MctTask of RDM block and RCC_LoaderTask of MCC block. Its physical configuration manages Channel DB and overhead channel DB is managed by FA and sector. RMM also controls channel element modem ASIC test and deletes/adds channel cards and blocks/unblocks channel cards and channel element. RCC_StatusTask periodically checks duplicate status of RCPA and reports the result to ECP. It automatically blocks/unblocks the overhead channel by estimating IPC path status from ECP. 2) RDM (Rcbu Device Management) Block RDM block manages fail/good status of STM in channel card and RCPA, and mounting/dismounting status of channel cards by periodic monitoring their status port (every 600 msec). It also initializes/controls/manages status of STM and CDM in RCPA. If STM initializing is successful, RDM block creates RCC_DnloadTasks in each channel card mounted to download codes. When faults or alarm occurs, the block reports it to ECP. RDM block also performs duplex switching function and simplex and duplex conversion function.
Issue 1.04/00
37
3) MCD (Multi-Channel Downloading) Block MCD Block is composed of RCC_LoaderTask and RCC_DnloadTask. RCC_LoaderTask loads channel code from ECP and RCC_DnloadTask downloads the channel code to channel card requesting channel configuration to ECP. At the same time, it also manages channel status. The max. 11 RCC_DnloadTasks are generated and RCC_KaTask is generated when channel status is normal. 4) MCM (Multi-Channel Maintenance) Block MCM Block is composed of RCC_StaticTask and RCC_KaTask. RCC_StaticTask reports on-demand and hourly perform measuring result of frame error rate in the traffic channel to ECP for each sector and this function. RCC_KaTask are generated max. 10 and they eschange KeepAlive message with channel card every 2 seconds. When the KeepAlive fault occurs, RCC_KaTask reloads the channel card after resetting it. 5) RDCB RDCB is a part of DevCtlTask, and performs PLL controlling and frequency tuning of BUDA and the PACA board, Tx Attenuation controlling of BUDA, LPA on/off controlling, and alarm recovering. As a supplementary function, it includes DebugTask module, which supports direct user control interface. 6) RDMB RDMB is a part of DevCtlTask. This unit senses mounting/dismounting and alarms of BUDA, PACA and LPA. RFC operates device status in 2 methods. The first one is the event driven status report method that updates status DB of RFC devices on special event occurring by periodical polling and reports the result to ECP. The second one is the cyclic status report method that updates status DB of current RFC devices periodically and reports the result to ECP. 7) RDIB RDIB is the unit, which configures the main RFC weekly program. It delivers relevant message to each task by initializing RFC, generating each task and communicating with RCC and ECP. It is a part of DevCtlTask and in charge of RFC device interfacing. RDIB is composed of I/O module, which adjusts Tx gain of BUDA, controls LPA, and inputs status of LPA on/off, and IIC module which runs PLL of UDCA through 3 wire buses. 8) RPMB RFC main task generates Eeprom task first among tasks of RPMB. RFC reads temperature data of 0 ~ 60 degree from PACA per 10 degree and calculates temperature data with the level of 1 degree through interpolation of 2 temperatures. If the interpolation successfully ends, RFC main task generates TrsPwrTask and WilbloTask. TrsPwrTask calculates initial Tx power value by referencing current temperature data after reading RSSI value from PACA, and continue to calculate current Tx power by using the weighted average by 50 ms. The current current Tx power is the basis of all power management. With the current Tx power value, WilbloTask in RPMB
Issue 1.04/00
38
performs wilting, blossoming, overhead power calibration, TPTL calibration, etc. 9) PACCB (Pilot/Sync and Access Channel Control Block) Pilot Channel is forward CDMA channel from BTS. It is used for initial synchronization in MS and provides frame synchronization when MS receives sync channel and standard pulse on demodulating. Sync channel is also forward channel from BTS and used at the system acquisition level. Once MS detects the system, sync channel doesnt need to be re-used until the power is on again. Access Channel is backward channel used when MS attempts to access to BTS and fixed to 4800 bps of information transmission rate. 10) PCCB (Paging Channel Control Block) S/W Paging Channel is from BTS. When MS receives system information, command or paging information for the entire or certain MS, or access request by MS, it processes these by receiving reply messages. 11) TCCB (Traffic Channel Control Block) S/W The following figure shows block configuration of TCCB. Main functions are as follows; - Performing required processing for call allocation - Encoding signal received from SVC (Selector/Vocoder) to transmit to MS - Transmitting data sent from MS to SVC - Detecting signal sent from MS - Sending/receiving necessary message for ECP/call allocation
Issue 1.04/00
39
P a c k e t R o u te r (fr o m /to S V C ,E C P )
.Call allocation .All blocks control and management .Data exchange with ECP .SVC control data processing
T X B lo c k
.Sending SVC data to OTA .Sending Time_sync packet to the main block
M A IN B lo c k
R X B lo c k
.Sending MS data to SVC .Sending Time_sync packetto SVC
SEARCH B lo c k
.Multipath signal detecting
M O D E M D riv e r ( A I R in t e r f a c e )
12) KERNEL Block - Initialization - Diagnostic - I/O interface - Low-level driver - Utilities and Libraries
Issue 1.04/00
40
3.4 Call Control

Call control function of STAREX-800 BTS processes originating/terminating call of MS, various events and call releasing by interworking with BTS channel element and CCP of BSC. Originating/terminating call processing procedure is briefly explained here in.
3.4.1 Originating call processing procedure

1) When the subscriber inputs termination number and presses the SEND key, MS transmits origination message that requests level 2 reply message for BTS origination service through AC (Access Channel). (imsi : Mobile Address, svc_opt : Service Option, dgt : Called Digits)
M S
m s_org_m sg
C E
E C P
C SB
C C P
m s_ o rg _ m s g bs_ac k_order
M o b O rg _ B 2 C ( im s i , e s n , s v c _ o p t , d g t )
2) ECP, which received origination message through AC, searches message and then sends MobOrg_B2C to CCP notifying originating call occurrence. CCP is the control processor of BSC. At this point, ECP sends base station acknowledge order message through paging channel originating to MS which confirms message receiving. 3) CCP, which received origination message (MobOrg_B2C) the origianting call setting message, allocates available vocoder by referring to 1st and 2nd frame off-set information delivered and allocated by BTS. CCP transmits setup message which includes call setting information such as called party BCD number (digit information dialed by the terminal user) to the switching system. When CCP allocates the vocoder resource, it allocates minimum load resource and does not allocate same frame offset at the same vocoder card.
Issue 1.04/00
41
M S
C E
EC P
C SB
C C P
A ssgn R eq_M 2C ( c ic )
M SC
A ssgnR eq_C 2B ( fr a m e o f fs e t) A ssgnR sp _B2C N u ll T r a f f ic c h_assg n_m sg P r e a m b le N u ll T r a f f ic v s _ m o b _ a c q _ c tl tc _ a c k _ c tl s e l_ lk _ o n b s_ ac k _ o rd er m s_ ac k_ ord er so _ req u est so_connect s o _ c o m p le t e T c L in k A c t _ S 2 C tc _ m o b _ m s g tc _ a s s g n _ a c k pc_ch_assgn pc _c h _assg n _ac k T im r S y n c . T im e S y n c . V s T c L in k _ C 2 S A ssgnR spAck_C2B
A s s g n C m p l_ C 2 M
4) MSC receives assignment request message (AssgnReq_M2C) which requests configuration of wireless channel resource connecting. 5) When CCP receives the assignment request message, it requests wireless channel allocation such as TC (Traffic Channel) or code CH by transmitting the assignment request message (AssgnReq_C2B) including allocated frame off-set information to ECP, 6) ECP selects usable TC with using received frame offset information and sends it to CCP by using assignment response message (AssgnRsp_B2C) with allocating code CH. 7) CCP, which received reply message for the resource allocation request from ECP, notifies the confirmation with AssgnAck_C2B message. 8) ECP, which received final AssgnAck_C2B, notifies allocation to TC/PC and receives allocation confirmation from each of them. 9) The allocated TC starts transmitting null data. PC transmits channel assignment message, which includes allocated code CH and frame offset, to MS through PC of CAI for wireless traffic channel setting.
Issue 1.04/00
42
10) MS, which received channel assignment message, synchronizes to the forward traffic with included information, and transmits preamble data through the backward traffic channel after sensing null data reception. The data is used for the backward communication channel synchronization of TC in BTS. 11) Aligning with 7~10 procedure, CCP requests TC link setting to SBP by using VsTcLink_C2S, which includes TC address and frame offset value allocated and notified by BTS. 12) The vocoder in SVCS of allocated BSC and BTS call channel complete TC link setting by delivering time synchronization message to each other. In this case, the time synchronization is not needed due to packet system of STAREX-1900 using CINU. 13)The call channel sends sel_lk_on message, which notifies link setting between the vocoder and call channel to ECP, and also sends vs_mob_acq_ctl message, which notifies gaining of the backward call to SVCS and receives reply message. 14) SVCS transmits the base station acknowledge order message to check whether link setting is properly set or not by the set link. In this case, if BTS gains the backward call channel, SVCS transmits the message requesting level 2 reply. 15) MS transmits the mobile station acknowledge order message as a reply for the base station acknowledge order message. Then MS-SVC takes service option negotiation procedure. 16) When call channel setting is completed, SBP reports it to CCP through TcLinkAck_S2C. CCP notifies the allocation completion of the wireless channel resource by transmitting the assignment complete message to MSC.
M S
C E
EC P
C SB
C C P
A le r t i n g _ M 2 C A le r t in g _ C 2 S
PC X (V L R )
R in g B a c k T o n e ( in _ b a n d ) C o n n e c t_ M 2 C M obC onn_C2S C o n n e ctA ck _ C 2 M
17) During termination setting procedure, originating MSC receives the notification receiver is ringing and notifies it to CCP by alerting message. In this case, the progress indicating information elements (option
Issue 1.04/00
43
information elements) displays whether call progress information is transmitted as in-band by tone or displayed by outer message. If the information element does not exist, it is regarded as in-band provisionally. 18) CCP transmits the alerting message to SVCS and the originating MS receives the ring back tone sent from the switching system by in-band. 19) If a call receives subscribers reply, the ring back tone is stopped and MSC connects the wire line to the terminating side and then configures the communication path by transmitting connect message to CCP. 20) When CCP receives the connect message, it transmits MobConn_C2S message to SVCS. In this case, CCP notifies by-pass Mode (M-To-M) or transcoding mode (Mobile-to-Land) to SBP for vocoding mode. The vocoder operates as by-pass mode, in case the vocoding mode is mobile-to-mobile call.
3.4.2 Terminating Call Processing Procedure

1) MSC switching system transmits the paging request message to the relevant CCP for terminating call setting and runs the paging timer.
M S
C E
EC P
C SB
C C P
P a g in g _ M 2 C
M SC
G e n P a g in g _ C 2 B p age_m sg p age_m ob _rsp p ag e_ m o b _ rsp P ageM obR sp_B2C P ageR sp _C 2 M A ssg nR eq_ M 2C pc_page_m ob
2) When CCP receives the paging request message, it transmits the paging request message to the corresponding ECP. In this case, the first paging request uses the zone list paging method is used for the second paging request and the system paging method is used for the second paging request. 3) When ECP receives the paging request message, it transmits the paging request message including MS address through PC (Paging Channel). 4) MS replies to the page request by transmitting the page response message to AC (Access Channel).
Issue 1.04/00
44
5) When ECP receives the page response message, it searches the message and then transmits the PageMobRsp_B2C message to CCP to notify the reply of MS. 6) When CCP receives the PageMobRsp_B2C massage, the reply message of receiving call, it delivers the page response message to the switching system by allocating usable vocoder resource referring to frame off-set information delivered and allocated by BTS. If CCP finds that the call is the test one of BSM by referring the service option of paging reply call, it performs the test call process procedure without delivering it to the switching system.
M S
C E
EC P
C SB
C C P
PC X (V L R )
A ssgn R eq_M 2C ( c ic )
A ssgnR eq_C 2B A ssgnR sp _B2C N u ll T r a f f ic c h_assg n_m sg P r e a m b le N u ll T r a f f ic v s _ m o b _ a c q _ c tl tc _ a c k _ c tl s e l_ lk _ o n b s_ ac k _ o rd er m s_ ac k_ ord er so _ req u est so_connect s o _ c o m p le t e T c L in k A c t _ S 2 C tc _ m o b _ m s g tc _ a s s g n _ a c k pc_ch_assgn pc _c h _assg n _ac k T im r S y n c . T im e S y n c . V s T c L in k _ C 2 S A ssgnR spAck_C2B
A s s g n C m p l_ C 2 M
7) MSC transmits the assignment request message requesting wireless channel resource allocation to CCP. 8) When CCP receives the assignment request message, it requests the wireless channel allocation such as TC (Traffic Channel) and code CH, by transmitting the assignment request message including frame off-set value usable in the allocated vocoder to ECP. 9) ECP selects the usable TC with received the frame off-set value, allocates code CH and transmits to CCP by using the assignment response message. 10) When CCP receives AssgnRsp_B2C, it confirms ECP by AssgnAck_C2B.
Issue 1.04/00
45
11) When ECP receives the final AssgnAck_C2B, it notifies allocation to TC and PC and checks the allocation in each. 12) The allocated TC starts the null data transmitting and PC transmits the channel assignment message including code CH and frame off-set to MS through PC of CAI for wireless traffic channel setting. 13) When MS receives the channel assignment message, it synchronizes to the forward traffic channel with included information, and transmits the preamble data through the backward traffic channel by sensing null data reception. The data is used for the synchronization of TC in BTC to the backward communication channel. 14) Aligning with 10~13 procedure, CCP requests TC link setting to SBP by using the VsTcLink_C2S message including the TC address and the frame off-set value. 15) The vocoder in SVCS of allocated BTS and the BTS call channel complete TC link setting by delivering time synchronization message to each other. In this case, the time synchronization is not needed due to packet system of STAREX-1900 using CINU. 16) The call channel transmits the sel_lk_on message, which notifies link setting between the vocoder and call channel to ECP, and sends the vs_mob_acq_ctl message, which notifies gaining of the backward call, to SVCS and receives the reply message about them. 17) SVCS transmits the base station acknowledge order message to check whether link setting is properly set or not by the set link. In this case, if BTS gains backward call channel, SVCS transmits the message requesting level 2 reply. 18) MS transmits the mobile station acknowledge order message as reply of the base station acknowledge order message. Then, MS-SVC takes service option negotiation procedure. 19) When call channel setting is completed, SBP reports it to CCP through TcLinkAck_S2C. CCP notifies the allocation completion of the wireless channel resource by transmitting the assignment complete message to MSC.
Issue 1.04/00
46
M S
C E
E C P
C SB
A le r t in g _ C 2 S
C C P
M SC
a le r t I n f o ( r in g _ o n ) m s_ac k _o rder A le r t A c k _ S 2 C c onnect order M obC onn_S2C A le r t in g _ C 2 M C o n n ec t_ C 2 M C o n n e ctA ck_M 2 C C onnAck_C2S
20) SVCS transmits the alert info to notify ringing to MS and MS replies to the alert message by transmitting the mobile station acknowledgement message to SCVS. 21) CCP sends alert message to MSC to notify ringing of the terminating side during the terminating setting procedure. 22) On receiving of receivers reply to the call, the connect order message which needs confirm reply is transmitted by MS. 23) When CCP receives reply to the call from the receiving MS, it transmits the connect message which notifies reply of receiving side to MSC. 24) When MSC receives the connect message, it transmits the connect acknowledge message as reply of receiving and CCP transmits the ConnAck_C2S message to SVCS. In this case, CCP notifies by-pass Mode (MTo-M) or transcoding mode (Mobile-to-Land) to SBP for vocoding mode. The vocoder operates as by-pass mode, in case the vocoding mode is mobile-to-mobile call.
Issue 1.04/00
47
3.4.3 Call Releasing Procedure

3.4.3.1 Call Releasing on Originating Side
M S
C E
EC P
CSB
CC P
M SC
R e le a se O rd e r R e le a se O rd e r R e le a s e M s g R e le a s e A c k M sg R ele a se _ S 2 C R e lC o m p _ C 2 S R e le a s e _ C 2 M R elease_ C 2 B c c _ c a ll_ re l R elease_ C 2 B R elC o m p _ M 2 C
1) MS starts call releasing with transmitting the release order message through the backward traffic channel. 2) SVCS of CSB (CDMA Selector Bank) stops call connecting, transmits the release order message to MS through the forward traffic channel as a reply to the release order message of MS, and notifies call releasing by MS to CCP. 3) CCP transmits RelComp_C2S, the reply for the release message, to SBP, and the release message to MSC to start call releasing process. Then it sends release message to ECP, and runs the call releasing timer. 4) MSC releases the call resource and transmits the release complete message to CCP. When CCP receives the message, it stops the call releasing timer. 5) When the entire release complete messages are received by MSC and ECP, CCP releases wireless call resource. If the receiving is not completed, it performs the call releasing procedure two times more and then withdraws the resource.
Issue 1.04/00
48
BTS System Description 3.4.3.2 Call Releasing by Network
M S
C E
E C P
C SB
C C P
PC X
R e le a s e _ C 2 M R e le a s e _ S 2 C R e le a s e O r d e r R e le a s e M s g R e le a s e O r d e r R e le a s e A c k M s g R e lC o m p _ C 2 S c c _ c a l l_ r e l R e le a s e _ C 2 B R e le a s e _ C 2 B R e lC o m p _ M 2 C
1) MSC transmits the release message to CCP to release the call and runs the call releasing timer. 2) When CCP receives the release message regarding call releasing occurrence from MSC, it transmits the release complete message to MSC and transmits the release message to SVCS. 3) When SVCS receives the release message, it starts call recovery by transmitting the release order message to MS through the forward traffic channel. 4) When MS receives the release order message, it transmits the message to the backward traffic channel as a reply. 5) When MSC receives the release complete message from CCP, it releases wire resource. 6) When CCP receives the release complete message of call recovery starting by MS from SVCS, it transmits the Release_C2B message to ECP and releases wireless resource.
Issue 1.04/00
49
3.5 Handoff Control Function

The handoff control function of STAREX-800 BTS interfaces with BSC to support all types of handoffs provided by STAREX-800 system. The type of handoff is decided by CCP, and it assigns or draws back TC according to this. MS measures the pilot strength of PN offset in the neighbor list and transmits PSMM (Pilot Strength Measurement Message) to CCP. CCP determines softer handoff, soft handoff, hard handoff, etc., based on PSMM (Pilot Strength Measurement Message) transmitted from MS. ECP receives handoff request differently and handles each differently according to the types of handoff. ECP, as to the softer handoff handling, receives a request from TCE (Traffic Channel Element) and assigns one more walsh code only. In case of handling soft handoff and hard handoff, ECP receives a request from CCP and assigns a new TCE. That ECP assigns resources in performing soft handoff is different somewhat from a normal common call. In case of a common call, it consults as to the frame offset decided by CCP up to three times maximum to distribute load as to the frame offset. But, in case of a soft handoff, ECP assigns the corresponding frame offset without consulting as to the frame offset designated by CCP. However, in case ECP could not allocate the corresponding frame offset, it mishandles soft handoff. And, it makes CCP to perform hard handoff.
3.5.1 Softer Handoff

Softer handoff is made with three procedures, that is, add cell, drop cell, swap cell.
3.5.1.1 Add Cell 1) If, of the pilot offset list that MS has, the strength of the pilot included in the neighbor set is in excess of T_ADD, then MS sends pilot strength measurement message (PSMM) to SVC (Selector Vocoder Card). 2) After SVC receives PSMM, the result is softer handoff, it transmits tc_sftr_ho_ctrl_msg which orders add pilot to the corresponding TCE. 3) TCE sends softer handoff request message that requests resources allocation from ECP for the handoff requested. 4) ECP assigns resources for handoff, and reports it to TCE. ECP which received softer handoff requset of TCE assigns code channel to use to the corresponding handoff, and sets up forward TX gain, and sends channel assign message in which assign_type is HA_SOFTER_HO to TCE, and then activates timer. 5) After ECP receives Call_status_Message from TCE in SFTR_HO_W_4_TC_SETUP status, if receiving Call_status_Message from TCE in SFTR_HO_W_4_OTA_TX status, then it releases timer to finish add pilot
Issue 1.04/00
50
BTS System Description (add sector) procedure of the softer handoff flow. 3.5.1.2 Drop Cell 1) If, of the pilot offset list which Mobile has, the strength of the pilot included in the active set falls below T_DROP, Mobile activates handoff drop timer, and even after the termination of timer, if the strength of the pilot is still below T_DROP, then it sends PSMM to SVC. 2) SVC, which received PSMM judges that pilot, was dropped, and it sends handoff direction message to Mobile. 3) Mobile performs handoff flow, and sends handoff completion message, and SVC which received the message sends a message that requests a release of the sector of the corresponding pilot to TCE. 4) TCE sends handoff completion message to ECP. 5) If ECP receives CC_HO_CMPL_MSG reporting handoff completion from TCE during the softer handoff, then it draws back code channel being used for handoff.
M S
TC
EC P
P I L O T S T R E N G T H M E A S U R E M E N T M E S S A G E ( C A I)
S B P /S V C
PSM M _S2C
C C P
tc _ s f t r _ h o _ c t l v s _ a c k _ c tl
H o ffA sgn_ C 2 S (S O F T E R _ A D D )
AD D PRO CEDURE
s o f te r _ h o _ r q s t_ c tl tc _ m o b _ a s g n vs_ sftr_ h o _ rsp _ c tl tc _ a c k _ c tl H A N D O F F D IR E C T IO N M E S S A G E (C A I) H A N D O F F C O M P L E T IO N M E S S A G E (C A I) H O f f C m p l_ S 2 C ( S O F T E R A D D )
P IL O T S T R E N G T H M E A S U R E M E N T M E S S A G E ( C A I) P SM M _S2C H o f fA s g n _ C 2 S ( S O F T E R _ D R O P ) H A N D O F F D I R E C T I O N M E S S A G E ( C A I) H A N D O F F C O M P L E T I O N M E S S A G E ( C A I)
DRO P PRO CEDURE
tc _ s o f t e r _ h o _ c o m p l e t e _ c tl vs_ ac k_ c tl cc_ho_cm pl H O f f C m p l_ S 2 C ( S O F T E R _ D R O P )
SOFTER HANDOFF SCENARIO (ADD, DROP)
Issue 1.04/00
51
BTS System Description 3.5.1.3 Swap Cell 1) If of the pilot offset list that Mobile has, the strength of the pilot included in the neighbor set is in excess of T_ADD, and at the same time, the strength of the pilot offset included in the active set falls below T_DROP, then it activates handoff drop timer, and if the strength of the pilot is still below T_DROP even after the termination of the timer, Mobile sends PSMM to SVC through TCE. 2) SVC compares the pilot chosen as a candidate and the pilot to be dropped, and if they are softer handoff, then it sends a message that orders swap pilot to the corresponding TCE. 3) TCE sends CC_SFTR_SWAP_RQST_MSG that requests TC swap from ECP for the handoff requested. 4) If ECP receives swap request message from TCE, it releases the code channel assigned to the sector to be dropped included in the message from TCE, and performs the flow such as drop pilot procedure; for example, the regulation of forward TX gain, etc. 5) ECP assigns the code channel to use and forward TX gain to the sector to be added, and after sending channel assign message that orders softer handoff preparation to TCE, it activates the timer. 6) After receiving Call_status_Message from TCE in SFTR_HO_W_4_TC_SETUP status, if ECP receives Call_status_Message from TCE in SFTR_HO_W_4_OTA_TX status, it releases the timer to finish add pilot (Add Sector) procedure of the softer handoff flow.
M S
TC
P I L O T S T R E N G T H M E A S U R E M E N T M E S S A G E ( C A I)
EC P
S B P /S V C
PSM M _S2C
C C P
t c _ s ftr _ h o _ s w a p _ c t l
H o f fA s g n _ C 2 S ( S O F T E R _ S W A P )
SW AP SUC C ESS PR O C E D UR E
s o fte r _ h o _ rq s t_ c t l tc _ m o b _ a s g n
v s_ a c k _ c tl
v s _ s ftr _ s w a p _ r s p _ c t l(s u c c e s s ) t c _ a c k _ c tl H A N D O F F D IR E C T I O N M E S S A G E (C A I ) H A N D O F F C O M P L E T IO N M E S S A G E ( C A I ) H O ff C m p l_ S 2 C ( S O F T E R _ S W A P )
s f t r _ h o _ r q s t _ c tl
t c _ s f t r _ s w a p _ r e j e c t( c a u s e )
v s _ s ft r _ s w a p _ r s p - c t l( F a il , c a u s e )
S W A P F A IL P R O C E D U R E
tc _ a c k _ c tl
H O ff F a il_ S 2 C ( c a u s e )
SOFTER HANDOFF SCENARIO (SWAP)
Issue 1.04/00
52
3.5.2 Soft Handoff

Soft handoff is made with three procedures, that is, add cell, drop cell, swap cell. 3.5.2.1 Add Cell (BTS to perform HandOff) 1) If, of the pilot offset list that MS has, the strength of the pilot included in the neighbor set is in excess of T_ADD, then MS sends pilot strength measurement message (PSMM).
2) SVC receives PSMM of MS and reports it to CCP, and CCP, in case of a soft handoff, sends CC_HANDOFF_REQUEST_MSG_ID to ECP to request a HandOff. 3) ECP that received handoff request message from CCP checks whether base_id is appropriate and searches whether joblk identical with the Mobile included in the message received from CCP was assigned. 4) It assigns joblk to set job_state to CP_CALL_ACTIVE, and assigns traffic channel and code channel. 5) It transmits assign message to TCE. (MA_SOFT_HO) 6) After reporting assign items for handoff to CCP, it activates the timer for handoff. 7) After ho_state receives CALL_STATUS Message from TCE in SFT_HO_W_4_TC_SETUP status, ECP, if receiving CALL_STATUS_MESSAGE in SFT_HO_W_4_OTA_TX_ON status, releases the timer to finish add pilot (Add Cell) procedure of the soft handoff flow. 3.5.2.2 Drop Cell (Cell on Busy) 1) If of the pilot offset list that MS has, the strength of the pilot included in the activation group falls below T_DROP value, then MS transmits PSMM to SVC. 2) CCP analyzes the PSMM message, and in case the pilot offset value is another BTS value controlled by itself, it orders soft handoff drop to SVC. 3) SVC uses handoff direction message to order activation group correction to MS. 4) MS uses handoff complete message to report that the activation group was corrected. 5) SVC requests a channel release from TC included in the pilot offset in which the strength of the pilot is T_DROP. 6) TC that received channel release order releases channel and reports it to SVC and ECP.
Issue 1.04/00
53
7) BSC SVC reports the completion of soft handoff drop procedure to CCP.
SE R V IN G M S TC ECP T C
TA RG ET ECP S B P /S V C
PSM M _S2C tc _ m o b _ as g n (so ft) tc _ asgn_ a c k t c _ s o f t_ h o _ i n _ p r o g r e s s _ c tl vs_ ac k _ c tl T im e _ S y n c Tim e _ S ync H o ffR e q_ C 2 B (FR E F E R A B L E _ A L L O C ) H o ffA sg n_ B 2 C (N O _ C E L L _ E R R O R ) H o ffA sgn_ C 2 S (SO F T_ A D D )
C CP
P IL O T S T R E N G T H M E A S U R E M E N T M E S S A G E ( C A I)
A D D P R O CED UR E
H A N D O F F D IR E C T IO N M E S S A G E ( C A I) vs_ m o b _ ac q_ c tl tc _ a c k _ c t l s e l_ lk _ o n H A N D O F F C O M P L E T I O N M E S S A G E ( C A I) H o ffC m p l_ S 2 C (S O F T _ A D D ) P IL O T S T R E N G T H M E A S U R E M E N T M E S S A G E ( C A I)
P SM M _S2C H o ffA sgn_ C 2 S(S O F T _ D R O P )
H A N D O F F D IR E C T IO N M E S S A G E ( C A I) H A N D O F F C O M P L E T IO N M E S S A G E ( C A I) tc _ r e le a s e _ c tl vs_ ac k _ c tl c c _ c all_ re l tc _ s o f t _ h o _ c o m p l e t e _ c tl vs _ ac k _ c tl c c_ho _cm pl H O ffC m pl_ S 2 C (S O F T_ D R O P )
DR O P PR O C ED U RE
SOFT HANDOFF SCENARIO (ADD, DROP)

3.5.2.3 Swap Cell SWAP procedure is a procedure in which ADD and DROP are performed simultaneously, and if, of the pilot offset list that MS has, the strength of the pilot offset included in the neighbor set is in excess of T_ADD value and at the same time the strength of the pilot offset included in the activation group falls below T_DROP value for a certain period, it transmits PSMM. 1) BSC CCP analyzes PSMM message and requests wireless channel assignment from BTS in which it is judged as a soft handoff SWAP to be added. CCPs handoff judgement inspects whether the value of the received pilot offset corresponds to BTS being serviced. If the result is another BTS, BTS, which is included in it, is inter-BTS soft, and if it is included in another BSC, it handles it as inter-BSC soft handoff or hard handoff according to the types of BSC. 2) BTS assigns the channel requested by, and reports it to CCP.
Issue 1.04/00
54
BTS System Description 3) BSC CCP that received channel assignment report from BTS orders soft handoff SWAP to SVCS. 4) BSC SVCS sets channel element and traffic channel link of a new BTS, and uses EHDM to order activation group correction to MS (A new group is added, and one of the existing groups is deleted). 5) MS uses HCM to report activation group correction to BSC SVCS through BTS. 6) BSC SVCS requests a channel release from the BTS channel element included in the pilot offset deleted from the activation group. 7) It releases the channel of BTS channel element being used and reports its history to the corresponding BTS and BSC SVCS. At this time, BTS draws back released call channel resources. 8) SVCS reports the successful completion of soft handoff SWAP cell procedure to CCP. 9) Exceptions: Exceptions are applied in case BTS could not assign traffic channel, code channel or onward power and in case a call is released at MS, etc. (But, DROP procedure is performed normally.)
Issue 1.04/00
55
3.6 Authentication
Authentication procedure is the information exchange procedure between BTS and MS that confirms the identity and qualifications of the calling party to confirm whether the service was allowed to the subscriber and protect an illegal call, before the service open to the subscriber. In addition, it is to protect the voice and data sensitive to security.
3.6.1 Authentication upon Origination

Authentication upon origination is a procedure when MS is approached to the network for an originating call. 1) By inputting RAND, ESN, IMSI_S1, SSD_A received through the access parameter message, MS transmits AUTHR, RANDC (RAND higher 8 bit), presently memorized COUNT value generated by performing an authentication signature procedure to BTS through the origination message. 2) Authentication center compares AUTHR and COUNT of the received message with AUTHR and COUNT values of its own for verification. 3) If the result conforms to each other, it allows an originating call and sends parameter update order message to MS to increase call history counter. 4) If the result is different, it rejects an originating call and performs unique challenge response procedure or SSD update procedure.
3.6.2 Authentication upon Termination

Authentication upon termination is a procedure when MS is approached to the network for a terminating call. 1) By inputting RAND, ESN, IMSI_S1, SSD_A received through the access parameter message, MS transmits AUTHR, RANDC (RAND higher 8 bit), presently memorized COUNT value generated by performing an authentication signature procedure to BTS through the page response message. 2) Authentication center compares AUTHR and COUNT of the received message with AUTHR and COUNT values of its own for verification. 3) If the result conforms to each other, it allows an originating call and sends parameter update order message to MS to increase call history counter.
Issue 1.04/00
56
4) If the result is different, it rejects an originating call and performs unique challenge response procedure or SSD update procedure.
O r ig in a tin g S id e M S
m s _ o rg _ m s g b s _ a c k _ o rd e r a u th _ c h a ll _ m s g c h a ll_ r s p _ m s g
T e r m in a tin g S id e C C P M SC
(V L R )
C E
A C
EC P
M o b O rg _ B 2 C a u th _ c h a ll
C SB
C C P
< ID L E > P a g in g _ M 2 C
C SB
PageM obR eq_C 2B
EC P
C E
M S
page_m sg p a g e _rs p _ m s g
m s _ o rg _ m s g
< I D L E >L 3 i n f o _ C 2 M ( a u t h s )
( i m s i , e s n , s v c _ o p t , d g t ,a u t h s ) ( T 3 0 3 ) ,( T 3 2 3 0 ) A u th R e q _ M 2 C A u th C h a ll_ C 2 B (R A N D U ) [T 3 2 3 0 ] P C c h a l l_ r s p C h a llR s p _ B 2 C A u th R s p _ C 2 M A C (A U T H U )
S e tu p _ C 2 M
( im s i, e s n ,s c i, c e llid _ lis t ,s o ) L 3 in f o [ P a g e R s p _ C 2 M ] ( c e ll id , s c m , im s i, a u th ) A u th R e q _ M 2 C (ra n d u ) A u th R s p _ C 2 M (a u th u ) S e tu p _ C 2 M C a ll C o n f _ M 2 C A ssgnR eq_M 2C ( c ic ,t r a n s c o d e r m o d e )
( im s i,e s n , s c i,s o )
p c_ p age_ m o b p a ge_ rs p P C A C a u th _ c h a l l c h a l l_ r s p PC A C
P ageM o bR sp _B 2 C (i m s i,e s n ) A u th C h a l l_ C 2 B C h a llR s p _ B 2 C
[ T 3 0 3 ] C a l lP r o c _ M 2 C A ss g n R e q _ C 2 B (fro ) A s s g n R s p _ B 2 C ( f r o ,t c ) n u ll tr a ff ic TC PC tc _ m o b _ as g n tc _ as g n _ a ck T c L in k R e q _ C 2 S T im e _ S y nc T C T im e _ S y n c s e l _ lk _ o n v s _ m o b _ a c q _ c tl tc _ a c k _ c t l b s _ a ck _ o rd er m s _ a c k _o rd e r so _ re q ue s t so_connect so _ c o m p le te T c L in k A c t_ S 2 C A s s g n C m p l_ C 2 M ( v e , t c ,f r o ,s e r v i c e _ o p t ) A s s g n A c k _ C 2 B (f r o )
a u th _ c h a l l_ m s g c h a ll_ r s p _ m s g
A ssgn R eq _ M 2C ( c ic ,t r a n s c o d e r m o d e )
A s s g n R e q _ C 2 B (f ro ) A s s g n R s p _ B 2 C ( f r o ,t c ) A s s g n A c k _ C 2 B (f ro ) tc _ m o b _ a s g n
p c_ ch_ asgn ch_ asgn_ m sg ( c d m a c h ,c o d e c h ,f r o ) p c _ c h _ a s g n _ a c k P r e a m b le
T c L in k R eq _ C 2 S ( v e , tc ,f r o ,s e r v ic e _ o p t)
tc _ as g n _ a ck T C n u ll tra f fi c pc_ch_asgn p c _ c h _ a s g n _ a c kP C c h _ a s g n _ m s g ( c d m a c h ,c o d e c h , f r o ) p re a m b le T im e _ S y nc T C tr a ff i c T im e _ S y nc v s _ m o b _ a c q _ c tl s e l_ lk _ o n t c _ a c k _ c tl b s _ ac k _ o rd er m s _ a c k _ o rd e r so _ re q u e s t so_connect a le r t_ In fo ( rin g o n ) m s _ a ck _ o rd e r c o n ne c t_ o rd e r
( c ic , c e ll_ i d )
A s s g n C m p l_ C 2 M ( c ic , c e ll _ id )
T c L in k A c t_ S 2 C
so _ resp o n se
s o _ c o m p le te
( tr a n _ m o d e ) (tra n _ m o d e )
M ob C o nn_ C 2 S A le r tin g _ C 2 S
A le r tin g _ C 2 S
R in g B a c k T o n e ( in _ b a n d )
A le r tin g _ M 2 C C o n n ec t_ M 2 C C o n n e c tA c k _ C 2 M
A le r t i n g _ C 2 M C o n n e ct_ C 2 M
A le r ti n g _ S 2 C M o b C o nn_ S 2 C
C o n n e c t A c k _ M 2 C( T 3 1 3 )
[T 313]
C O N V E R S A T I O N
Mobile-To-Mobile Authentication SCENARIO
3.6.3 Authentication upon Location Registration

It is an authentication procedure when MS is approached to the network for location registration. After comparing the AUTHR value generated by performing authentication procedure by MS and COUNT value presently memorized at MS with the AUTHR, COUNT of BTS authentication center, location registration is allowed only in case they conform to each other.
1) By inputting RAND, ESN, IMSI_S1, SSD_A received through the access parameter message, MS performs an authentication signature procedure to create AUTHR and transmits it with RANDC (RAND higher 8 bit) and COUNT, attached to the registration message.
Issue 1.04/00
57
2) Authentication center compares AUTHR and COUNT of the received message with AUTHR and COUNT values of its own for verification.
3) If the result is identical, authentication is allowed, and if different, it rejects its registration and starts unique challenge response procedure or SSD update procedure.
M S
R e g is t r a t i o n
C E
M obR eg_M sg
EC P
SV C
C C P
M S C /A C
M o b R e g _ B 2 C (T y p e ) R eg R e q _ C 2 M (T y p e)
U D T R eg_M 2C ( A c c e p t / R e je c t ) M o b O rd er_ C 2 B (A c ce p t) M o b _ O rd e r(A c c e p t) O rd e r_ M sg (R e g A c c e p )
Location Registration Authentication SCENARIO
3.6.4 Unique Challenge Update Procedure

Unique challenge update procedure is a procedure that requests an authentication directly from the authentication center as to a specific MS. Since it can be executed anytime whenever an authentication center is necessary, a delivery to MS should be possible through the paging or traffic channel.
1) Authentication center creates 24 bit random number RANDU and delivers it to MS to request an authentication, attached to the authentication challenge message.
2) If receiving authentication challenge message, MS reads RANDU value in the message and performs an authentication signature procedure with ESN, IMSI, SSD_A values to transmit AUTHU to the authentication center, attached to authentication challenge response message.
3) Authentication center uses SSD_A to perform an authentication signature procedure in the same way to create
Issue 1.04/00
58
BTS System Description AUTHU and compares it with the value ascended from MS.
4) If the result is identical, it allows an authentication and if wrong, it does not allow any more access as to MS or starts SSD update procedure.
M S
A u t h _ C h a ll_ M s g
C E
EC P
SV C
A u t h _ C h a ll_ C 2 B
C C P
M S C /A C
A u t h _ C h a ll_ M 2 C
A u t h _ C h a ll_ R s p _ M s g
O rd e r_ M sg
M o b _ O rd e r_ B 2 C A u th _ R e q _ C 2 M
Unique Challenge Update Procedure SCENARIO(Paging CH)
M S
C E
EC P
SV C
A u t h _ C h a ll _ C 2 S
C C P
M S C /A C
A u t h _ C h a ll_ M 2 C
A u t h _ C h a ll_ R s p _ M s g
O rd e r_ M sg
M o b _ O rd e r_ S2 C
A u th _ R e q _ C 2 M
Unique Challenge Update Procedure SCENARIO(Traffic CH)
3.6.5 SSD Update Procedure

SSD update procedure is a procedure that updates SSD (Shared Secret Data) of the authentication center and MS, and it can be executed anytime whenever the authentication center is necessary through the paging or traffic channel.
1) The authentication center creates 56 bit random number RANDSSD and delivers it to MS through SSD update message to request SSD update.
2) After MS receives a message, MS reads RANDSSD and creates SSD_A_NEW and SSD_B_NEW as in ESN, A-Key. And then it creates random number RANDBS to confirm the lawfulness of the network having requested
Issue 1.04/00
59
BTS System Description SSD update and a new SSD value and transmits it BTS through access or reverse traffic channel, attached to BS challenge order message.
3) The authentication center performs an authentication signature procedure to RANDBS of BS challenge order message received, SSD_A_NEW created, ESN, IMSI_S1 of the corresponding MS to create AUTHRBS and transmits BS challenge confirmation order message to MS through paging or forward traffic channel.
4) If AUTHBS of BS challenge conformation order message is successfully verified, MS updates SSD by SSD_A_NEW, SSD_B_NEW and transmits BS challenge confirmation order message to BTS, and if unsuccessful, it transmits SSD update reject order to BTS.
M S
S s d _ U p d a te _ M sg O rd e r_ M sg
C E
S sd _ U p d a te _ M sg
EC P
SVC
S sd _ U p d a te _ C 2 B
C C P
M S C /A C
S sd _ U p d a te _ M 2 C
O rd e r_ M sg
B S _ C h a ll_ B 2 C B S _ C h a ll_ C 2 M B S _ C h a ll_ R s p _ M 2 C
O rd e r_ M sg O rd e r_ M sg
M o b _ O rd e r
B S _ C h a ll_ R s p _ C 2 B
O rd e r_ M sg
S sd _ U p d a te _ R sp _ B 2 C
S sd _ U p d a te _ R sp _ C 2 M
SSD Update Procedure SCENARIO (Paging CH)
M S
S sd _ U p d a te _ M sg O rd er_ M sg
C E
EC P
S s d _ U p d a te _ M sg
SV C
S sd _ U p d a te _ C 2 S
C C P
M S C /A C
S sd _ U p d a te_ M 2 C
O rd e r_ M s g
B S _ C h a ll_ S 2 C
B S _ C h a ll_ C 2 M B S _ C h a ll_ R s p _ M 2 C
O rd e r_ M sg O rd e r_ M sg
M o b _ O rd er
B S _ C h a ll_ R s p _ C 2 S
O rd e r_ M sg
S s d _ U p d a te _ R sp _ S 2 C
S sd _ U p d a te _ R sp _ C 2 M
Issue 1.04/00
60
SSD Update Procedure SCENARIO (Traffic CH)
Issue 1.04/00
61
3.7 Location Registration Function

Location registration is an essential function that is requested to handle efficiently the paging function for setting up of a terminated call to MS (Mobile Station) in the mobile communications system. It is a procedure in which MS reports its location, status, ID (IMSI, ESN), slot cycle index and other different features to BTS. Especially, in case MS is operated in slot mode, by providing SLOT_CYCLE_INDEX parameter to BTS, it reports to BTS that MS supervises any type of slot to enable BTS to page the corresponding slot, and by reporting its location and status to the system through BTS it enables MS to efficiently page MS when the system sets up MS terminated call. Since an excessive location registration receives location registration from many MSs, rather leading to a loading to the access channel and network, thus making it inefficient, location registration parameter should be set by the value optimized through a lot of tests.
M S
1) Pow er up, T im e r b a se d , D ista n c e B a se d , Z o n e b a se d , P a r a m e te r c h a n g e re g .
I n it_ R e g _ M s g
CE
M o b R e g_ M sg
ECP
SV C
M o b R e g _ B 2 C (T y p e )
CCP
M SC/ VLR
R e gR e q _ C 2 M (T y p e ) R e g _ N o t if i c a t i o n U D T R e g_ M 2 C (A c c e p t / R e je c t ) R e g _ N o t i f ic a t i o n _ A c k
HLR
b s_ a c k _ o rd e r b s_ a c k _ o rd e r
R e g is t
M o b O r d e r _ C 2 B ( A c c e p t /R e je c t ) M o b _ O r d e r( A c c e p t / R e g R e je c t ) O r d e r _ M s g ( R e g A c c e p t / R e g R e je c t )
2) P o w e r d o w n in N o T r a f fic sta te
R e g _ U p d a te _ M s g M o b R e g U p t_ M s g b s_ a c k _ o rd er M o b R e g _ B 2 C (ty p e ) R e g R eq _ C 2 M (T y p e ) R e g _ N o t if i c a t i o n R e g _ N o t if i c a t i o n _ A c k
3) P o w e r d o w n in T ra ffic sta te
R e g_ U p d a te _ M sg
R e le a s e _ R e q ( P o w e r - d o w n ) R e le a s e _ M s g R e le a s e _ A c k c c _ c a l l_ r e l R e lC o m p _ C 2 S R e g _ N o t if ic a tio n _ A c k V s M o b R e l_ S 2 C R e lC o m p _ C 2 M ( c a u s e :p o w e r - d o w n )
U p d a te
R e g _ N o t i f ic a t i o n (p o w e r-d o w n )
Registration Scenario (by mobile)
Issue 1.04/00
62
M S
4) O rd e r R e g ist By M SC
O rd e r_ M sg (R e g _ R e q u e st_ O rd e r) R e g is tr a tio n _ M s g
CE
ECP
M o b _ O rd e r(O rd e re d _ R e g ) R e g is t ra tio n _ M s g
SVC
M o b O rd e r_ C 2 B (O rde red _R e g)
CCP
M SC / VLR U D TR eg_M 2C
(O rd e r e d R e g )
HLR
R e gR e q _ B 2C
R e g R e q _ C 2 M (T y p e ) R e g _ N o t i f ic a t i o n U D TR eg_M 2C ( A c c e p t / R e je c t ) R e g _ N o t if i c a t i o n _ A c k
O rd e r_ M s g (A c c e p t/ R e je c t ) m s_ o rg _ m sg o r p a ge _ rsp _ m sg
M o b_ O rd e r
M o b O rd e r _ C 2 B (A c c e p t/ R e je c t)
5) Im p li c i t R e g istra tio n
m s_ o rg_ m sg o r p a g e _ rs p B s_ A c k _ O rde r
M ob O rg_ B 2 C or P ageM o b R sp _ B 2 C
S e tu p _ C 2 M
R e g _ N o t if ic a tio n ( I m p lic it ) R e g _ N o tif ic a t io n _ A c k
B s_A ck _O rd er
6) T ra ffic C h a n n e l R e g istra tio n (B y C C P ) 7) T ra ffic C h a n n e l R e g istra tio n (B y M S C )

(rese rv e d )
H O ffP rfm _ C 2 M
R e g _ N o t if ic a tio n R e g _ N o t i f i c a t io n _ A c k
M o bR eg_M 2C M s _ R e g is te r e d M s _ R e g is t e r e d M obR eg_C 2S
O rd e r_ M sg (sta tu s_ re q ) S ta tu s _ M sg
S ta t u s _ R e q _ O r d e r ST A T U S_M SG
S ta t u s R e q _ C 2 S
S tatu sR e q _ M 2 C C o n v e rs a t io n S t a t e w it h H a nd off ST A T U S_ C 2 M U D TR eg_M 2C ( M s R e g is t t e r e d )
ST A T U S_S2C
R e g _ N o t if i c a t i o n R e g _ N o t i f i c a t io n _ A c k
M s _ R e g is te r e d
M s _ R e g is t e re d
S tatu sR eg _ C 2 S
Registration SCENARIO (BY MSC, Implicit)
3.7.1 Power-up Registration, Timer Based, Distance Based, Zone Based, Parameter Change Registration
If the registered message transmitted from MS is delivered to ECP through ACCESS CH., ECP transmits the registered message to CCP and sends BS_ACK_ORDER to MS. If HLR receives the registered message, it performs a registration, and delivers its result (ACCEPT OR REJECT) to VLR to be delivered to MS.
3.7.2 Power-down Registration in No Traffic State

The basic procedure is the same as 1) and because MS was already powered down, HLR updates the registered DATA and then reports it to VLR to terminate FLOW.
3.7.3 Power-down Registration in Traffic State

When MS was powered down in TRAFFIC status, if, after setting CAUSE being POWER_DOWN to RELEASE_ORDER, it sends it to SVC, and if after SVC sends RELEASE_MSG to CE, it receives ACK, then it transmits a message to the higher processor. HLR, after recognizing having been POWER_DOWN in TRAFFIC status and updating the registered data, reports it to VLR and then FLOW is terminated.
Issue 1.04/00
63
3.7.4 Ordered Registration by MSC

If MSC delivers ORDERED_REG_MSG to MS through BSC, then MS transmits the registered message to BTS through ACCESS CH and the remaining procedure is identical with <1>.
3.7.5 Implicit Registration

When MS transmitted Origination_Msg or Page_Response_Msg to BTS, it is automatically registered in HLR.
3.7.6 Traffic Channel Registration by CCP

When the zone of MS was changed after HandOff, if CCP reports it to MSC, VLR requests a registration to HLR. If HLR reports the result about the registration, SVC transmits MS Registered_Msg through TC and reports the result to MS.
3.7.7 Traffic Channel Registration by MSC

If MSC transmits Status_Request_Msg to MS through BTS in traffic status, then MS transmits Status_Msg to SVC through AC. If HLR performs a registration and reports its result to MSC/VLR, SVC transmits MS Registered_Msg through TC to report the result to MS.
Issue 1.04/00
64
4. Lower Subsystem Description

4.1 ECMS
4.1.1 Subsystem Overview
ECMS (Enhanced BTS Call Control & Management Subsystem) is a S/W subsystem of STAREX-800 BTS. It handles access, paging, traffic channels, and call control message and maintenance & repair message of of RCCS (Rf & Channel Control Subsystem) and gives and takes the message for RF control, and gives and takes CCMS (CCP), control message and maintenance & repair message. It defined ECMS function, architecture and block for the systematic development of ECP software, and divided ECMS into the function blocks, and defined the function about each block.
4.1.2. Subsystem Design Concept

ECMS, as in the subsystem configuration diagram below, is a subsystem in STAREX-800 BTS to support the works necessary for the operation and maintenance of the system such as call processing, handoff, resources management, power management, configuration, trouble and alarm, statistics, test, etc.
S S B P , S V C ( S V C S ) P C X C C P ( C C M S ) E C P ( E C M S ) C S M S B T S B S C H L R
C E R C P ( R C C S )
M S C
: : :
T r a f f i c S i g n a l l i n g C o n t r o l
B S M
Issue 1.04/00
65
4.1.3. Subsystem Architecture

4.1.3.1 Subsystem Configuration and Interworking
ECMS, as in the architectural diagram of ECMS software below, is interfaced with CCP and CE. It is comprised of the call processing control part such as ECC that controls a call, EHC that controls a handoff, ETC that handles the transparent message with MS, ERM that is responsible for the resources management, EPM that manages BTS power, etc. and the operation and maintenance processing part that is comprised of EMC that downloads BTS block, EQM that performs the status management of the lower block, EDN that handles BTS downloading, EST that handles the management, maintenance and repair of the BTS status, EFA that is in charge of the fault control,
S T A R
E E C C E E H C E T C P M R M
O
E E
p e r a t in g
D S N T E D M
S y s te m
E E E C F
F A T M S
C E O M E M
C
E E M E E E E M M E C R a H T P Sa a D C : E n h a n M : E n h a n n a g e m e n t C : E n h a n C : E n h a n M : E n h a n Tn a : g e E m n eh na tn n a g e m e n t N : E n h a n c e d c e d c c c c e e e e d d d d B S P B S P B B B B S S S S P P P P
&
M O C F a T M D a
C
C : M : F : A e: C g M : S : M : n a g e E E E E o E E E m n n n n n n n
E
h h h h t h h h e a a a ra o a a a n n n n nl n n n t c c c c c c c e e e e e e e d d d d d d d B B B B B B B S S S S S S S P P P P P P P M O C F T M D a A o a e e e in C M M n f ig u lt & s t M a s u v ic e o n tr o l a in c o n u r a t io n A la r m a n a g e m r e m e n t t r M M e & o a a n S l n a n a t ta
C a ll C o n tr o l R e s o u r c e H a n T r a n P o w S ta t D o w d s e u n
c e d
B S P
E E o f f C o n t r o l E p a r e n t m e s Es r E s E E lo a d in g M
Issue 1.04/00
66
BTS System Description ETM that is in charge of the test, EMS that is in charge of the measurement and statistics, and EDM that is in charge of OAM supplementary function.
4.1.3.2 S/W Block Functions
1) EMC (Enhanced BSP Main Control Block) It is a main block of ECP S/W. It is a function block downloaded by Booter ROM. As the major functions, it downloads lower block application other than itself from CCP and downloads PLD from BSM. In addition, it manages a common DB shared by each ECP function block. For the minimization of the time for ECP processor S/W downloading, after writing each block downloaded on the flash ROM, it checks the version from CCP upon re-initiation, and if they are identical, it reads each function block from the flash ROM to perform the cut-down of downloading time. Since, at ECP, another execution file by each function block is operated at one processor board, a manager is necessary to control DB that should be shared by each block. That is, information about common DB is necessary and a block that allocates its DB to the memory is necessary, so EMC is in charge of the function.
2) ECC (Enhanced BSP Call Control Block) ECC is a block related to the call processing of ECP to perform the basic call processing function.
The major examples are as follows: - Data initialization related to the call processing - Call related message processing - MS originated call processing - MS terminated call processing - Call release processing - Call processing monitoring function - Call related BTS user interface function 3) ERM (Enhanced BSP Resource Management Block) BRM is the resources management block of ECP and its major functions are as follows: - Call resources management related data initialization - Resources status related message processing - Call resources allocation - Call resources release
Issue 1.04/00
67
BTS System Description 4) EHC (Enhanced BSP Handoff Control Block) EHC is a block handoff call processing related block of ECP and the handoff function is to support all types of handoffs provided by STAREX-1900 system, interworking with BSC (Base-Station Controller), PCSC (PCS Mobile Service Switching Center). In view of ECP, the difference between the softer handoff and the soft handoff in their processing is as follows: ECP, in case of handling the softer handoff, receives a request TCE (Traffic Channel Element) and allocates one more walsh code only. In case of handling the soft handoff and hard handoff, ECP receives a request from CCP and allocates a new TCE. That, in performing soft handoff, ECP performs a resources allocation is different somewhat from the normal common call. Upon soft handoff, as to the frame offset designated by CCP, ECP allocates the corresponding frame offset. However, in case ECP can not allocate the corresponding frame offset, it fails in soft handoff. And, it makes CCP perform hard handoff.
5) ETC (Enhanced BSP Transparent message Control Block) ETC is a block that handles the transparent message with MS. It provides the procedures for the following supplementary function service by handling all the messages excepting the message related to the basic call processing. - Performs the function that handles the message received from the access channel. - Performs the function that handles the message received from CCP and sends it to the page channel. - Performs the function that handles the message received from CCP. - Performs the function that handles the message received from the access channel and sends it to CCP. - Provides the user command and function for debugging. 6) EPM (Enhanced BSP Power Management Block) EPM is the power management block of ECP and is operated as a power management task and initializes power management related data, and receives power management related message and calls the corresponding function to provide the power management function such as TPTL, PACA calibration, etc. Power management is a wide meaning of vocabulary including power estimation(TPTL), excess capacity estimation, sector breathing, sector wilting, effective radiated power limiting, forward link power control, hard handoff, soft handoff, softer handoff, etc. and it is an element performing the most important role in deciding the capacity of CDMA system. The major functions of EPM are as follows: - PACA Initial Calibration When RCP is initialized, it performs a calibration as to the overhead channel.
Issue 1.04/00
68
BTS System Description - PACA Periodic Calibration It receives a message from Config task of ECP to perform a calibration periodically. - PACA MMC Command Calibration It receives a message from BSM or performs a calibration through the user command of ECP. - LPA Over Power Estimation & Control It receives a report on the LPA status from RCP to control BTS according to this. - TPTL (Transmit Power Tracking Loop) It receives a report on TC Total Power RCP every 1.5 second from RCP to perform a calibration. - Excess Forward Link Capacity Estimation & Control It measures the load of forward link to control BTS according to this. - Traffic Channel Gain Scaling If Excess forward link capacity falls below gain scaling threshold, it performs gain scaling. - Excess Capacity Threshold Change It changes excess capacity threshold by user command. - PACA Measurement BSM Display It reports the present PACA status by the request of BSM. - Excess Forward Link Capacity Estimation & Control - Sector Wilting - Sector Breathing
7) EOM (Enhanced BSP OAM Main Control Block) EOM performs the function that manages and controls the status of the function block excepting EMC in ECMS subsystem. The major functions are as follows: - Executes the function block downloaded from CCP by EMC. - Status management of each function block - Function stop and re-execution of the corresponding block according to function block update during the service 8) EDN (Enhanced BSP Downloading Block) Each processor (ECP,RCP) board performs a downloading according to each board ID upon equip and reset by booter loader. In case of ECP, it downloads OS (all BTSs), application from CCP, and in case of other booters it downloads OS and application of each processor to load them in the memory and if the downloading ends, it activates OS, application of the corresponding processor. In case of ECP, it records OS, application code as to the lower processor on the data area of RAM and then if a loading request is received from the lower processor, then it performs a down-loading.
Issue 1.04/00
69
BTS System Description 9) ECF (Enhanced BSP Configuration Management Block) ECF function block initializes the internal data on the information about the configuration and operation according to the radio wave configuration such as H/W configuration and FA/Sector, etc. necessary in performing the function by the S/W Block in ECP. In addition, it performs the function that changes the related data as to the changes of the configuration and operation information during the service. The information about H/W configuration and FA/Sector configuration about all BTSs is included in the data commonly called PLD (Programmable Loading Data), and initializes the internal data in ECMS, based on PLD that EMC block downloaded from BSM.
10) EST (Enhanced BSP Status Management Block) EST function block is a block that performs the status management and control of all the processors and device in BTS. The processor and device in BTS are transited in their status by the reason of a fault in operation, etc., and EST block manages such status changes, and reports them to BSM or performs a control due to the changes. The major functions of EST are as follows: - Processor status management - Device status management - Processor re-initiation - Device re-initiation - Block/Unblock of Over-Head channel according to the change of the channel or RF resources status - Reporting the status of the channel resources to ERM, a resources management block
11) EFA (Enhanced BSP Fault & Alarm Management Block) EFA performs the function that collects and manages the faults occurred during the operation of BTS H/W and S/W and reports them to BSM. EFA manages and reports the faults in two types, that is, alarm and fault largely. Alarm collection path, in view of EFA block in ECMS, is divided into three types; that is, an alarm collected through BAMA, an alarm collected from RCP and an alarm that sets a random value as a threshold, and generates and releases an alarm according to the change of the threshold so that it may maintain the status about the fault in systems operation to inform the operator of the status. The alarm detected and managed by BAMA is As follows: - ECPA Open/Equip and Function Fail/Recover - BADA B'd Open/Equip and Function Fail/Recover - BTMA B'd Open/Equip and Function Fail/Recover - RCPA Open/Equip and Function Fail/Recover - Open/Equip about RCPA Shelf Power
Issue 1.04/00
70
BTS System Description - EDU Environment Alarm - Open/Equip by Each Sector/Path of LNA, Power Fail/Recover, and LNA Fail/Recover - Optical Repeater Alarm - GPS Power Fail, Open/Equip and Function Fail/Recover The alarm detected and managed by RCP is as follows: - MCPA Open/Equip and Function Fail/Recover - BUDA B'd Open/Equip and Function Fail/Recover - PACA B'd Open/Equip and Function Fail/Recover - LPA and RF Device Related Alarm
S/W alarm processing by threshold setting is as follows: CPU Time Over Load Alarm LPA Over Power Alarm Call Setup Rate Alarm Fault processing of EFM judges the following cases as a fault and reports a fault of BSM; that is, in case an automatic recovery is made as a continuous recognition to the operator is not necessary or time passes during the fault of BTS. In case a fault and an alarm were occurred, when the status change is necessary according to the kinds of the fault and alarm, it reports it to EST, a status management block, to change the status. In case of an alarm, EFM reports fault occurrence/recovery situation to BSM and manages this independently, but in case of a fault, it does not manage it. However, in case, as in CE fault, a fault occurs in a short period of 20msec or so often, it may bring about a system overload, so it performs an internal management for the purpose of filtering this. 12) EMS (Enhanced BSP Measurement & Statistics Block) EMS block performs mainly ECP overload status management and on-line , on-demand statistics processing. The overload status is divided into normal, minor, major, critical for reporting, and it performs originating call restriction, or terminating/originating call restriction according to the overload status. The statistics processing items are as follows: - BTS performance statistics - CE statistics - Wireless quality statistics - Paging statistics - Process statistics - CAI (Common Air Interface) statistics Statistics also is divided into on-line statistics that reports the statistics collection data of all items, and ondemand statistics that requests a statistics at need by fixing an item for processing.
Issue 1.04/00
71
13) ETM (Enhanced BSP Test Management Block) ETM function block enables a good call quality by testing a call resources such as the channel element of BTS and the radio resources such as the antenna that could affect a call quality, and by figuring out the status of the resources bad beforehand and isolating them. The test target of ETM includes BIT (Built In Test) test that measures whether H/W of the channel element is normal, Markov call test that uses BADA to set up an actual call and measures a call quality, and VSWR that uses BTS Markov call to test the status or features of the antenna, etc.
Test configuration for the channel is as follows: H/W function status test of the channel - On-line/On-demand test - Inhibit/Allow function - Test items . Modulator/Demodulator interface test . Encoder/Decoder test . Interleaver/Deinterleaver test Test configuration for Markov call is as follows: It measures a call quality by setting up an actual call and measuring forward/reserve FER. - On-line/On-demand test - Inhibit/Allow function - Test items . In case of on-line test, test of the overall CEs . In case of on-demand, test possible by designating in RCB/CHC/CE unit VSWR measurement test configuration is as follows: By setting up an actual call and measuring VSWR, it can check up the antenna status through the features of the antenna. - On-line/On-demand test - Inhibit/Allow function - Test items . By designating a specific FA at Multi-FA BTS, VSWR possible to be measured. 14) EDM (Enhanced BSP Device Management Block) EDM function block performs a supplementary OAM functions such as status management, Remote H/W Reset, Inventory function, etc. through the device and Keep-Alive in ECU shelf.
Issue 1.04/00
72
BTS System Description The major functions of EDM block are as follows: - Status management by BAMA,BTMA Keep-Alive - Remote H/W Reset function about B'd in ECU shelf via BAMA - Remote H/W Reset function such as B'd and LPA, etc. in RCB - Function of collecting the inventory of each PBA and reporting it to BSM - EDU related control, status message delivery function
Issue 1.04/00
73
4.2 RCCS
4.2.1 Subsystem Overview
RCCS (Rf & Channel Control Subsystem) subsystem is comprised of RCC (RCbu Control) part, RFC (RF Control) part, CMC (Channel Modem Control) part and KERNEL part largely. RCC performs the initialization, control, status management, maintenance and repair, and cord downloading of STM (System Timing Module), CDM (CDMA Data combine and align interface Module) in MCPA (Multi-Channel Processor board Assembly), CE (Channel Element), and RCPA (Rf & Channel control board Assembly) and performs various On-Line, OnDemand functions. RFC performs the functions such as the initialization, control, status management and maintenance and repair, etc. of BUDA(Broad band sector conversion & Up-Down conversion board Assembly), PACA, LPA, and MCC performs CDMA digital MODEM control function. In addition, KERNEL module provides packet routing function, board initialization, nucleus OS, and various utility functions by each module.
4.2.2 Subsystem Design Concept
E C P A ( E C P )
I A
L P A 1 L P A 1 L P A L P A L P L
l p - B e 1 - G 2 A 2 P A
t a A l p - B e t 2 - G a
C M
P C
A P
2 0 A
# 0 2 0
R R # 9
C C
P P
A A
A B
B B
D A 1 U D A 1 B U D A B U D A B U D B U
l p - B e 1 - G 2 A 2 D A
t A P l p - B e t 2 - G a a A C A
P -
B u s
S e r ia l-
B u s
The above picture is a configuration diagram of RCB (Radio Channel Bank Block) on which RCCS subsystem is mounted, and takes control of the subscriber of digital mobile communications, final CDMA digital channel control part performing air interface, and RF control part.
Issue 1.04/00
74
4.2.3 Subsystem Architecture
RM M B
R C C M a in T a s k
RDM B
RC C M CT Task
M CM B
R C C S ta tic T a s k
R C C S ta tu s T a s k
R C C D eb ug T ask
R CC KA Task 1
M CDB
R C C L o a de r T a sk
R C C K A T a sk 1 0
R C C D n lo a d T a s k 1
RDCB
R F C D e v C tl T a sk
R C C D n lo a d T a s k 1 0 R FC D e b u g T a sk
KNL
PACCB
P S C M a in T a sk
A C M a in T a s k
PCCB
P C Tx Task
TCCB
T C M a in T a s k
(N u c le u s P L U S & D riv e r (E C M ,C S M , H D L C , S IO ) & F a u lt/N M I H a n d le r & P a c k e t R o u te r & I/O & W a tc h d o g & D ia g n o s tic & U tility & L ib ra r y )
R D IB
R F C M a in T a s k
R F C D e v C tl T a s k
RDM B
R F C D e v C tl T a sk
RPM B
R FC E eprom Task
TC Tx Task R FC TrsP w r Task TC R x Task R F C W il b l o T a s k
TC S earch T ask
4.2.3.1 Configuration and Functions S/W in RCCM of RCPA is comprised of the blocks, as in the above picture, and several tasks is included in each block.
1) RMM (Rcpa Maintenance & Management) Block Function
Issue 1.04/00
75
BTS System Description RMM block is comprised of RCC_MainTask and RCC_StatusTask, and RCC_MainTask performs RCB configuration function and channel DB conversion to perform a DB initial update, when this function was successfully performed, it creates RCC_MctTask of the RDM Block and RCC_LoaderTask of the MCD block. Channel DB is managed by physical configuration, and in addition as to overhead channel DB, it is also managed by FA and sector. In addition, it performs channel MODEM ASIC test control function, and also performs channel element delete/add function and channel card and channel element block/unblock function. RCC_StatusTask checks the duplexing status of RCPA periodically to report it to ECP. And, it estimates IPC path status from ECP to perform the automatic block/unblock function of the overhead channel.
2) RDM (Rcbu Device Management) Block Function RDM block manages the fail/good status of STM and the open/equip status of the channel cards in channel card and RCPA periodically (every 600msec), detecting the status port, and performs the initialization, control, status management of STM and CDM in RCPA, and if STM initialization is successful, then it creates RCC_DnloadTasks to perform code downloading to each channel card equipped. And, it detects the fault and alarm of the devices periodically, and performs the function of reporting it to ECP upon a situation occurrence, and also performs overhead channel duplexing switch-over function and simplexing/duplexing change function. 3) MCD (Multi-Channel Downloading) Block Function MCD block is comprised of RCC_LoaderTask and RCC_DnloadTask, and RCC_LoaderTask downloads a channel code from ECP, and RCC_DnloadTask loads the channel code to the channel card, and requests channel configuration from ECP, and at the same time, channel status management is also made. At this point, RCC_DnloadTask is created up to 11EA maximumly, and if the channel status becomes normal, it creates RCC_KaTask. 4) MCM (Multi-Channel Maintenance) Block Function MCM block is comprised of RCC_StaticTask and RCC_KaTask. RCC_StaticTask performs the function of reporting the measurement result of frame error rate of the traffic channel to ECP by sector, and it performs the function by on-demand and hourly function. RCC_KaTask is created up to 10EA maximumly, and gives and takes KeepAlive Message with the channel card in a 2 second period, and in case KeepAlive fault occurs, it resets the corresponding channel card and then performs a reloading. 5) RDCB Function RDCB is a part of DevCtlTask to perform the function such as PLL control and frequency tuning of BUDA and PACA boards, Tx attenuation control of BUDA and On/Off control and alarm recovery of LPA. In addition, as a supplementary function, it includes DebugTask Module supporting a simple direct user control interface.
6) RDMB Function RDMB, a part of DevCtlTask, is an unit that performs the function such as alarm detection of BUDA, PACA,
Issue 1.04/00
76
BTS System Description LPA and alarm detection. RFC operates the status of the devices in two ways. The first is event driven status report method in which, when a specific event was happened by a periodical polling, it updates the status DB of RFC devices and reports it to ECP, and the second is cyclic status report method in which it updates the status DB of the present RFC devices periodically and reports it to ECP. 7) RDIB Function RDIB is an unit consisting of RFC main program and it delivers an appropriate message to each task through the initialization of RFC, the creation of each task and communication with RCC and ECP. In addition, it is a part of DevCtlTask and is also an unit in charge of the interface of RFC device. It is comprised of I/O module in charge of BUDA transmission profit adjustment, LPA On/Off control and status input, and IIC module that activates PLL of UDCA through 3 wire bus. 8) RPMB Function RFC main task creates EEPROM Task of the tasks of RPMB first of all. RFC reads the temperature data from 0C to 60C from PACA in 10C unit and seeks again the temperature data on the level of 1C through the interpolation between two temperatures. If the interpolation function is finished successfully, RFC main task creates TrsPwrTask and WilbloTask by turns. TrsPwrTask reads RSSI value from PACA and seeks the initial Tx power value by referring to the present temperature data, and through the use of a weighted average in 50ms unit, it continuously seeks on current Tx power. This current Tx power is a basis to all power management, and WilbloTask uses this value to perform the function such as wilting, blossoming, overhead power calibration, and TPTL calibration, etc.
9) PACCB (Pilot/Sync and Access Channel Control Block) Function Pilot channel does not control in a way of software. This block is divided into PSC_Main task that handles Sync Channel message and AC_Main task in charge of access channel. PSC_main task makes sync channel message per 80ms and repeats infinitely a routine that transmits continuously per 1200bps. AC_Main Task detects the message sent from MS and repeats a routine that performs demodulation and decoding infinitely. 10) PCCB (Paging Channel Control Block) Function Paging channel software receives a message from the higher and converts it to CAI format for transmission. For this, it is comprised of only one PC_TxTask and it performs a role of paging channel, as this task rounds infinite loop and calls each functional functions. Each function receives a message from the higher and it can be divided into a temporary storing part, a part that converts a message to the corresponding slot time in CAI format, and a part that performs encoding to write the message on asic. 11) TCCB(Traffic Channel Control Block) Function Blocks of TCCB are comprised as follows: - TC_MAIN
Issue 1.04/00
77
BTS System Description It performs all the works related to the channel assignment and call processing, and it is a block that performs a role of controlling all blocks of the traffic channel traffic. handles control data between the traffic channel and SVC. - TX It is a block that handles the data received from SVC (Selector/Vocoder), and the kind of Rx data includes time_sync packet and voice packet. It sends Time_sync packet to TC_MAIN block, and sends voice packet to OTA (Over-The-Air) after encoding. TX block is alive every 1.25ms to handle a call presently assigned or a call newly assigned. - RX It is a block that performs a role of sending the data sent to the backward channel by MS to SVC (Selector/Vocoder) after decoding. It determines a rate in 20ms frame unit. In addition, it sends time_sync packet as an answer to time_sync packet sent by SVC at the time of initial call setup, and performs a role of transmitting the control data that the traffic sends to SVC. - SEARCH It is a block that performs a role of detecting the signal transmitted to OTA (Over-The_Air) backward traffic channel sent by MS. It controls Searcher/Finger in MODEM to detect multipath signal. The major functions are as follows: - Performing a process necessary for call allocation - Transmitting the signal received from SVC (Selector/Vocoder) to MS after encoding - Transmitting the data sent from MS to SVC - Detecting a signal sent from MS - Tx/Rx of the message necessary for ECP and call allocation 12) KERNEL S/W The kernel architecture and major functions are as follows: Initialization Diagnostic I/O interface Low-level driver Utilities and Libraries - Initialization It performs an initialization of CHC (CHannel Card) hardware and software. Here, it performs a minimum initialization for a normal operation of CHC S/W, and an additional initialization at need can be made. The architecture is as follows: It handles time_sync packet from SVC (Selector/Vocoder), and gives and takes a message necessary for ECP and call assignment. In addition, it
Issue 1.04/00
78
D a ta B a se
ECM In it ia l HD LC
Bus c o n t r o lle r
P e r ip h e r a l c o n t r o lle r
D ig it a l C o m b in e r
S IO
- Diagnostic It performs restart, fault report, etc. upon necessity after detecting a fault of CHC hardware and software. The architecture is as follows:
D ia g n o s t ic ta sk
W atch d o g ta s k
S y s te m v ie w e r
F a u lt /N M I h a n d le r
F a u lt re p o rte r
System viewer: It has the function of showing the information such as task, timer, event group, etc. presently operated, a fault previously stored or debugging information to the user, and is provided in CLI (Command Line Interface) form. Diagnostic task: It checks whether a fault of the hardware occurred periodically, and in case of a fault occurrence, it stores the status, and calls fault reporter. It receives various diagnostic commands in message type, and reports the execution and result of the command. Watchdog task: It checks whether application tasks are falls in the infinite loop periodically, and when there is such a task, it stores the status, and calls fault reporter, and then performs restarting. Fault/NMI handler: It stores the status in case an exception occurs due to the malfunction of the software, and calls fault reporter and then performs restarting. Fault reporter: In case various exceptions occur, it corrects fault history, and reports the present fault information to BTS BSC or CHDM (CHannel Diagnostic Monitor).
Issue 1.04/00
79
BTS System Description - I/O interface It uses RS-232 (Serial port) or RS-422 (HDLC port) interface to execute the command input by the user, and performs the function of outputting the necessary information. The architecture is as follows:
u s e r p r in t a m essage
p r in t ta sk
se n d a ch a ra cte r o r m e ssa g e th ru S IO o r H D L C
u s e r in p u t a co m m an d
m o n it o r ta sk
in te r p r e t & e x e c u t e u ser com m and
- Low-level driver It provides HDLC (High-Level Data Link Control), CSM, ECM, CHDM driver, etc. to CHC S/W. The functions are as follows: HDLC :- initialization - packet tx and rx - error detection , correction, statistic CSM : - initialization - packet tx and rx ECM : - initialization - packet tx and rx CHDM : - initialization - packet tx and rx - Utilities and libraries It provides the basic and common functions requested for CHC S/W operation in function type. The functions are as follows: -. standard library functions (memcpy, memcmp, strcpy, strcmp, getopt, atol, ) -. Functions in a transformed type of standard library (datol, hatol, memclrw, memcpyw, ) -. fixed-length doubly-linked-list non-priority queue -. system time management (time_set, time_invalidate, time_get_coarse, time_get_sys, ) -. number-to-ASCII converter (byte2hex, word2hex, word2dec) -. pack/unpack of packet (pack32, unpack32, pack64, unpack64) -. CHDM report -. load complete message send -. nano seconds delay
Issue 1.04/00
80
5. Structural and Environmental Conditions

5.1 Structural Features
5.1.1 General Structural Features
(1) BTS is made of a module structure where an extension and the function change are easy, so a new function add and an accommodation of the technical development is easy. (2) The outer housing of BTS is attached with a port for grounding. (3) BTS is comprised of an unit having an enough shielding effect in consideration of the influence on the electronic wave.
5.1.2 Reliability and Availability

(1) The major parts of BTS hardware is made duplexed for the reliability of the system, and is designed in the structure of the module structure where operation and maintenance are easy. (2) BTS software is designed in a logical, physical function distribution structure and it insures a maximum service transparency suitable for the distribution system in a fault-tolerant structure. (3) System reliability is over 30 years as an average time between the downs (MTBF). (considering HW only) (4) Availability is below 4 hours as an average down handling time (MTTR).
5.2 Environmental Conditions

(1) Operating Temperature Limits : 0 ~ 50C (2) Relative Humidity Limits : 5 ~ 95%
Issue 1.04/00
81
6. Abbreviations
SBCR : Standard BTS Control Rack SBER : Standard BTS Extended Rack BTR : BTS Timing Reference Block ECP : Enhanced Control Processor Block RCB : Radio Channel Bank Block LPA : Linear Power Amplifier Block ECPA : Enhanced Control Processor circuit board Assembly ENIA : Enhanced Network Interface circuit board Assembly BAMA : BTS Alarm collection & Maintenance board Assembly LICD : Line Interface Control Daughter board BTMA : BTS Timing Management circuit board Assembly CGPS : Compact BTSs Global Positioning System MCPA20 : Multi-Channel Processing board Assembly 20 RCPA : Radio & Channel Processing board Assembly PACA : Power Adjust & Control Assembly BADA : Base station Analyze & Diagnostic Assembly BUDA : Base station sector conversion & Up/Down converter Assembly LPAU : Linear Power Amplifier Unit FECU : Front-End Compact Unit BSBB : BTS Standard Back Board RCBB : Radio & Channel Bank Backboard PSU-G : Power Supply Unit - G PSU-I : Power Supply Unit - I
Issue 1.04/00
82

Straex800 CBTS Lpa (010619)

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Straex800 CBTS Lpa (010619)

Diunggah oleh

Hak Cipta:

Format Tersedia

BTS System Description

STRAEX-800 Compact-BTS System (Standard)

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary

BTS System Description

1.2.2 RF Specifications 1.2.2.1 Receiver Specifications

LGIC Confidential and Proprietary

BTS System Description

1.2.2.2 Transceiver Specifications

Channel Time Tolerance

LGIC Confidential and Proprietary

BTS System Description

FAN(500005) RCB(6U) (3rd ~ 4th) RCB(6U)

(1st ~ 2th) ECP(6U) B T R BLANK

LGIC Confidential and Proprietary

BTS System Description

2.1.1 ECP (Enhanced Control Processor Block)

Mounting Diagram of ECP

LGIC Confidential and Proprietary

BTS System Description

2.1.2 BTR (BTS Timing Reference Block)

M BU S BTM A BAM A R e m o te C o n tro l

LGIC Confidential and Proprietary

BTS System Description

2.1.3 RCB (Radio Channel Bank Block)

Mounting Diagram of RCB

LGIC Confidential and Proprietary

BTS System Description

2.1.4 LPA-D (Linear Power Amplifier Block D)

Mounting Diagram of LPA-D (1) LPAU-D : amplifies Rx signal

2.1.5 FECU (Front-End Block)

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary

BTS System Description

2.2 S/W Configuration

<S/W Configuration of BTS and BSC>

2.2.1 ECMS (Enhanced BTS Call Control & Management) Subsystem

LGIC Confidential and Proprietary

BTS System Description

2.2.2 RCCS (Rf & Channel Control) Subsystem

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary

BTS System Description

3.2 H/W Configuration and Function

LGIC Confidential and Proprietary

BTS System Description

3.2.2 Functions for Each H/W Unit

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary

BTS System Description

IP C RS232 RS422 56K M O DEM M CU M DP DAA RS485 N IM 2

R e m ote C trl FPG A

LGIC Confidential and Proprietary

BTS System Description

LGIC Confidential and Proprietary