Micro-cell Base Station Extension

Extend the Maximum Distance Limitation of an Ericsson 882 M Micro-cell Base Station from 1.25 to 20 Miles

Problem
The Ericsson 882M Micro-cell provides the RF coverage needed at an airport. However, to cover the entire airport complex you need to extend over 1.25 miles to a remote Micro-cell base station (MCBS). The alternative would be separate Micro-cell control nodes (MCCN), but the traffic expected would not justify the cost. Cell enhancers cannot provide the quality of service needed for this application.

Solution
Coastcom's analog Micro-cell equipment can be configured to support analog 882M Micro-cell transceivers, MCC, and MLOC with remote alarm capability. The equipment consists of two D/I Mux III special T1 multiplexers with dual 4-Wire TO channel cards, a TTU channel card, SDM, and CEL1 SDCU data link(s). Installing MCBS and co-locating Coastcom equipment establishes a remote MCBS to an existing NCCN up to 50 miles awayremote MCBS, reducing hardware and T1 deployment costs significantly.

How Does It Work?
The CEL1 SDCU is a special data card that interfaces to the MDIO bus in the MCCN Ericsson control equipment. The 4-Wire TO channel cards connect the VF paths to the D/I Mux III at the remote Micro-cell location. These extend through the D/I Mux III at the control node, connecting to the MBLT at the MTSO. The TTU interfaces to the TDI card in the MCCN, connecting all local voice channels and the STC/STR data link. Typical configurations of 6 to 14 voice channels are connected to the MCCN over a single T1 facility, using microwave, fiber optics, or a T1 through the LEC. At the remote MCBS, the SDM channel card can be used as an option to support remote alarms support ofand extend the TW port of the IOIM to the MCBS. This provides access to the MTSO for control purposes.

Figure c9. Conventional Configuration for MCCN/MCBS

Figure c10. Remote Extension for Drop-and-Insert Configuration

What Actually Occurs?
The remote MCBS behaves similarly to the local MCBS in that it supports both hand-off and hand-over functions. The MCC and MLOC perform the same functions in the Micro-cell, but are remotely attached to an MCCN at the control node cell site. The CEL1 SDCU receives data from the MDIO and transfers them to the CEL1 SDCU in the Micro-cell. The CEL1 SDCU, in turn, passes the data to an MDCU bus cable connected to the MCBS radio rack.

The 4-wire voice connections from the transceivers bypass the MCCN, using dual channel 4-Wire TO cards in the D/I Mux III, to send data directly to the MTSO.

Each external alarm contact closure at the Micro-cell switches a ground condition to the alarm unit. This activation extends over the SDM link to the control node cell where the alarm unit activates an IOIM contact by providing a dry contact closure. IOIM thereby supports external alarm activation at both the remote Micro-cell and the local control node. Each external alarm -- and even the D/I Mux III equipment -- can be uniquely named within the IOIM alarm table to help with troubleshooting.

How Do You Set It Up?
As many as 19 analog voice channels can be located at the remote Micro-cell over a single T1 facility. Digital bandwidth allocation is limited to one DS0 (64 Kbps) for each MVC (analog voice channel), four DS0s (256 Kbps) for each CEL1 SDCU and one DS0 for the SDM alarm/TW port feature. At the MCCN, the D/I Mux III is set up in drop-and-insert mode at the MCCN, and it distributes the Mobile Bothway Line Trunk (MBLT) voice channels to the TDI, extending the other channels to the remote Micro-cell. The D/I Mux III at the remote MCBS is set up in channel bank mode, terminating all voice channels and the CEL1 SDCU data channel. The MCCN supports multiple remote Micro-cells. The MCC, MLOC, and MVC programming in the MTSO is similar to a conventional installation. An alarm unit terminates up to 16 remote alarms and interfaces to an SDM channel card in the D/I Mux III. The alarm unit at the control node provides the contact closure(s) to the IOIM should alarms be activated at the remote Micro-cell.

What Information Do You Need?

1. How many MVC voice channels do you need at the local and remote Micro-cell locations?

2. What is the distance between the local and remote Micro-cell sites, and what medium is used between the MTSO and cell sites (microwave, fiber, or local phone company T1)?

3. How many sectors are you planning to deploy at the Micro-cell?

Remote Micro-cell Base Stations

Locate a Number of Micro-cell Base Stations (MCBS) 20 Miles or More from a Micro-cell Control Node (MCCN)

Problem
Use of a Micro-cell provides the RF coverage needed at the downtown business center. However, there are four major buildings that need coverage using the LEC, resulting in distances of many miles to each remote MCBS. An alternative would be four separate Micro-cell control node (MCCN) systems, but the traffic expected would not justify the cost. Cell enhancers cannot provide the voice transmission quality needed to support this application.

Solution
Coastcom's analog Micro-cell equipment can be configured to support analog 882M Micro-cell transceivers, MCC, and MLOC with remote alarm capability. The equipment consists of D/I Mux III T1 multiplexers with dual 4-Wire TO channel cards, TTU channel cards, SDM, and CEL1 SDCU data link(s). By co-locating Coastcom equipment, remote MCBSes can be established up to 50 miles from an existing MCCN. Savings in hardware and T1 facilities can reduce deployment costs significantly.

How Does It Work?
The CEL1 SDCU is a special data card interface to MDIO bus that interfaces to the MDIO bus in the MCCN control equipment. Each MCBS has a dedicated CEL1 SDCU link back to the MCCN using 256 Kbps or four DS0s. The 4-Wire TO channel cards connect the VF paths at the remote Micro-cell locations to channels or DS0s through the TTU interfaces at the control node. These T1s support either an MBLT to the MTSO or connect to the TDI interface and derive voice channels through the MCCN. Typical configurations of 6 to 14 voice channels per MCBS connect to the MCCN over a single T1 facility, using microwave, fiber optics, or a T1 through the LEC. Each D/I Mux III can be configured individually as channel bank, dual channel bank, or drop-and-insert, enabling many different MCBS network topologies. Similarly, the SDM channel card can support remote alarms and extend the TW port of the IOIM to the Micro-cell location, providing access to the MTSO for control purposes.

Figure c11. Locating Multiple Micro-cell Base Stations (MCBS) Over 20 Miles from a Micro-cell Control Node (MCCN)

What Actually Occurs?
The remote MCBS behaves similarly to the local MCBS in that it supports both hand-off and hand-over functions. The MCC and MLOC perform the same functions in the micro cell, but are remotely attached to an MCCN at the control node cell site. The CEL1 SDCU receives data from the MDIO and transfers data transfer from the MDIO to the CEL1 SDCU in the micro cell. The CEL1 SDCU, in turn, passes the data to a MDCU bus cable connected to the MCBS radio rack.

The 4-wire voice connections from the transceivers use dual-channel 4-Wire TO cards in the D/I Mux III to pass signals back to the MTSO, bypassing the MCCN completely.

Each external alarm contact closure at the micro cell switches a ground condition to the alarm unit. This extends over the SDM link to the control node cell where the alarm unit activates an IOIM contact by providing a dry contact closure. The IOIM thereby supports external alarm activation at both the remote micro cell and the local control node. Each external alarm, and even the D/I Mux III equipment, can be uniquely named within the IOIM alarm table to aid troubleshooting.

How Do You Set It Up?
Up to 19 analog voice channels can be located at the remote Micro-cell over a single T1 facility. Digital bandwidth allocation is limited to one DS0 (64 Kbps) for each MVC (analog voice channel), four DS0s (256 Kbps) for each CEL1 SDCU, and one DS0 for the SDM alarm/TW port feature.

At the MCCN location, the D/I Mux III, which is set to drop-and-insert mode, distributes the Mobile Bothway Line Trunk (MBLT) voice channels to the TDI and extends the other channels to the remote Micro-cell.

The D/I Mux III at the remote MCBS is set to channel bank mode, terminating all voice channels and the CEL1 SDCU data channel. The MCCN can support multiple remote Micro-cells. The MCC, MLOC, and MVC programming in the MTSO is similar to a conventional installation. Up to 16 remote alarms are terminated by an alarm unit that interfaces to an SDM channel card in the D/I Mux III. The alarm unit at the control node provides the contact closure(s) to the IOIM should alarms be activated at the remote micro cell.

What Information Do You Need?

1. How many MVC voice channels do you need at the local and remote Micro-cell locations?

2. What is the distance between the local and remote Micro-cell sites, and what medium is used between the MTSO and the cell sites (microwave, fiber, or local phone company T1)?

3. How many sectors are you planning to deploy at the Micro-cell?

Analog Macro-cell Hook-Up

Connect a Micro-cell Base Station to an Existing Analog Macro-cell Site and Install as a Remote Sector Up to 50 Miles Away

Problem
The Micro-cell meets the limited space and RF coverage available at the conference center. A macro-cell site is in place five miles away, but cell enhancers do not have the quality needed to support this application within the allocated budget. The traffic expected could not justify the cost of a full Micro-cell control node and Micro-cell base station combination.

Solution
Coastcom's analog Micro-cell equipment can be configured to support a remote sector of the local macro-cell site. Analog Micro-cell transceivers with MCC and MLOC functionality operate from the existing EMRP/EMDM control at a donor cell site. The equipment consists of D/I Mux III T1 multiplexers equipped with dual 4-Wire TO channel cards and one or more CEL1 SDCU data link. By installing the remote MCBS and co-locating the Coastcom equipment, an MCBS can be established as a remote sector up to 50 miles from an existing macro cell site. Savings in hardware and T1 facilities can reduce deployment costs significantly.

How Does It Work?
The CEL1 SDCU is a special data card that interfaces to the MDIO bus in the EMRP/EMDM control equipment. The MCBS has a dedicated CEL1 SDCU link that uses 256 Kbps or four DS0s. The 4-Wire TO channel cards connect the VF paths at the remote Micro-cell location to MBLT channels or DS0s, using the D/I Mux III at the donor cell site. Additional savings on T1 facility costs can be realized by cross-connecting spare voice channels on the D4 at the donor to the 4-Wire TO channel cards on the D/I Mux III. Typical configurations of 6 to 14 voice channels per MCBS can be connected over a single T1 facility. The SDM channel card support of remote alarms and extends the TW port of the IOIM to the Micro-cell location, providing access to the MTSO.

Figure 12. Remote Sector - Ericsson GE 882M

What Actually Occurs?
Each remote MCBS behaves like a remote sector to the donor macro cell site, supporting both hand-off and hand-over functions. The MCC and MLOC perform the same functions, but are connected remotely to an EMDM at the donor site. The CEL1 SDCU CEL1 SDCU data linkreceives data from the MDIO and transfers data transmission to the CEL1 SDCU in the MCBS. The CEL1 SDCU, in turn, passes the data to a MDCU bus cable, connected to the MCBS radio rack.

The 4-Wire voice connections for the transceivers use dual channel 4-Wire TO cardsdual 4-Wire TO in the D/I Mux III and connect directly to the MTSO, using the D/I Mux III at the donor.

Each external alarm contact closure at the Micro-cell switches a ground condition to the alarm unit. This activation extends over the SDM link to the control node cell where the alarm unit activates an IOIM contact by providing a dry contact closure. The IOIM thereby supports external alarm activation at the remote as well as the local control node. Each external alarm and even the D/I Mux III equipment can be uniquely named within the IOIM to aid troubleshooting.

How Do You Set It Up?
From 6 to 14 analog voice channels can be remotely located at each base station, operating over a single T1 facility. Digital bandwidth allocation is limited to one DS0 (64 Kbps) for each MVC (analog voice channel), four DS0s (256 Kbps) for each CEL1 SDCU and one DS0 for the SDM alarm/TW port feature. At the donor cell, the D/I Mux III is set to drop-and-insert mode and distributes the MBLT voice channels, using the D/I Mux III and over the T1 facility to the MCBS. The D/I Mux III at the remote MCBS is set to channel bank mode, terminating all voice channels and the CEL1 SDCU data channel. The MCC, MLOC, and MVC programming in the MTSO is similar to a sectorized cell site and necessitates no special programming. An optional alarm unit terminates up to 16 remote alarms, connecting via an SDM channel card in the D/I Mux III. Should alarms be activated at the base station, the alarm unit at the donor provides the contact closure(s) to the IOIM.

What Information Do You Need?

1. How many MVC voice channels do you have at the donor and remote locations?

2. What is the distance between the donor and remote site, and what medium is used between the MTSO and cell sites (microwave, fiber, or local phone
   company T1)?

3. How many sectors are you planning to deploy at each?

4. Are you using compact or non-compact hardware, and what contingency requirements do you have at the donor (redundant EMDM/EMRPs, STRs, power)?

5. What configuration best serves your needs -- dedicated T1 for the host, or a shared configuration, using spare voice channels at the donor?