Summary of the content on the page No. 1
LBI-38965B
System and Installation
Manual
EDACS BCU/CAL
Billing Correlation Unit/
Centralized Activity Logger
ericssonz
Summary of the content on the page No. 2
LBI-38965 NOTICE! This manual covers Ericsson and General Electric products manufactured and sold by Ericsson Inc. NOTICE! Repairs to this equipment should be made only by an authorized service technician or facility designated by the supplier. Any repairs, alterations or substitution of recommended parts made by the user to this equipment not approved by the manufacturer could void the user’s authority to operate the equipment in addition to the manufacturer’s warranty. NOTICE! The software con
Summary of the content on the page No. 3
LBI-38965 TABLE OF CONTENTS Page 1. INTRODUCTION..................................................................................................................................................... 5 1.1. BCU FUNCTIONAL DESCRIPTION ............................................................................................................. 6 1.2. CAL FUNCTIONAL DESCRIPTION ............................................................................................................. 6 2. PHYSI
Summary of the content on the page No. 4
LBI-38965 TABLE OF CONTENTS (Cont.) Page 4. INSTALLATION ....................................................................................................................................................20 4.1. HARDWARE INSTALLATION....................................................................................................................20 4.2. SOFTWARE INSTALLATION .....................................................................................................................
Summary of the content on the page No. 5
INTRODUCTION LBI-38965 1. INTRODUCTION This manual contains installation instructions, physical and functional descriptions, specifications, and usage information for the Enhanced Digital Access Communications System (EDACS) Billing Correlation Unit and the Centralized Activity Logger (BCU/CAL). A block diagram of the BCU/CAL is shown below. The BCU/CAL works as a subsystem attached to an Ericsson Private Radio Systems (PRS) Integrated Multisite and Console Controller (IMC) and can be set to o
Summary of the content on the page No. 6
LBI-38965 INTRODUCTION 1.1. BCU FUNCTIONAL DESCRIPTION The main function of the BCU is to generate call detail records (CDRs) to be transferred to an external billing system for invoice generation. To accomplish this, the BCU scans an input stream of activity messages supplied by the IMC, archives these messages in their raw form, uses those messages which indicate channel assignment and channel drop events to calculate air time, and then generates the CDR. Call Types Supported All EDACS call
Summary of the content on the page No. 7
INTRODUCTION LBI-38965 Call Types Supported All EDACS call types except for the following are supported by the CAL: 1. Console calls. 2. Conventional site calls. 3. Local interconnect calls. 4. System all calls. NOTE Non-EDG data calls are only supported if radios are “wide-area enabled” on the site. 7
Summary of the content on the page No. 8
LBI-38965 PHYSICAL DESCRIPTION AND COMPATIBILITY 2. PHYSICAL DESCRIPTION AND COMPATIBILITY This section outlines the specifications, depicts the physical architecture, and provides compatibility information for the BCU/CAL. Software for the BCU and the CAL are merged into one software package. Feature encryption allows or disallows BCU or CAL functionality. The two products can also run on the same hardware platform with minor additions for CAL. 2.1. PHYSICAL SPECIFICATIONS General Specifica
Summary of the content on the page No. 9
PHYSICAL DESCRIPTION AND COMPATIBILITY LBI-38965 2.2. BCU/CAL ARCHITECTURE The BCU/CAL's internal architecture is shown in Figure 2. The individual components and their primary functions are outlined below. VMEbus Backplane P2 Adapter Board RS-232 Appl. SW HDLC Common VME From CAM Platform Ethernet LAN SCSI Formation TVME712/M Transition TVME147 CPU Module WANServer Communications Module Tape Drive Floppy Administrative Terminal Disk Hard Disk To System Manager Terminal Servers (CAL Only) Figu
Summary of the content on the page No. 10
LBI-38965 PHYSICAL DESCRIPTION AND COMPATIBILITY The BCU/CAL is based on a VMEbus computing platform with the following components: CPU Technico TVME 147 single-board computer based on a 68030 microprocessor • Supports BCU/CAL application processing • Interfaces to hard disk, floppy disk, and tape drive via an on-board small computer systems interface (SCSI) with a connector on the transition module • Interfaces to the console terminal via an RS-232 serial port with a connector on the transition
Summary of the content on the page No. 11
PHYSICAL DESCRIPTION AND COMPATIBILITY LBI-38965 2.3. COMPATIBILITY The BCU/CAL software is compatible with the following IMC and System Manager versions: • IMC Software V4.01 and later • IMC CAM Controller Board (P/N 19D903299P3) • Networks/Data VME Controller ROM V1.03 • MicroVax System Manager Software V3.01 and later (CAL only) The System Manager Software version requirement applies only to the CAL feature. The BCU feature operates independent of the System Manager. Thus, the BCU is “comp
Summary of the content on the page No. 12
LBI-38965 SPECIFICATIONS 3. SPECIFICATIONS 3.1. COMMON BCU AND CAL OPERATIONAL SPECIFICATIONS 3.1.1. EDACS System Interface The BCU/CAL interfaces to EDACS via a full duplex port supporting high-level data link control (HDLC) protocol. The BCU/CAL will adapt to the data transmission rate to which the Central Activity Module (CAM) is set to operate (64K or 360K, selectable via CAM dip switches). BCU/CAL Input Data Each raw activity record (RAR) contains the following information: 1. Day and ti
Summary of the content on the page No. 13
SPECIFICATIONS LBI-38965 3.2.2. Billing Architecture The EDACS billing system architecture is shown in Figure 3. Each IMC is connected to a BCU/CAL via a high-speed serial communications link using HDLC protocol. RF RF RF RF System System System System Console Console Terminal Terminal Downlink MIM MIM DAT (Optional) MIM MIM DAT (Optional) C Area Area C BCU A BCU IMC A IMC M M High-Speed HDLC Link Ethernet TCP/IP WAN StarGate Customer Billing Mainframe To other IMCs The dotted lines enclose
Summary of the content on the page No. 14
LBI-38965 SPECIFICATIONS 3.2.3.1. RF Channel Usage (Air Time) The basic unit of RF channel usage for billing purposes is a channel assignment. One or more working RF channels is assigned in response to a request from a subscriber unit (mobile radio, data terminal, etc.). Each channel assignment event results in air time, which is defined as the period of time during which the RF channel or group of channels is in use, repeating the signal from a subscriber unit. If the system is operating in
Summary of the content on the page No. 15
SPECIFICATIONS LBI-38965 Channel assignment and channel drop messages contain the following information: • Date and time of event to the nearest tenth of a second • Type of event (i.e., assignment or drop) • Call type (individual clear voice, group clear voice, individual digital voice, group digital voice, data, etc.) • Site number or console number • Channel number • Caller ID • Callee ID 3.2.3.5. Time Synchronization The time of channel event value is derived from the IMC's internal clock.
Summary of the content on the page No. 16
LBI-38965 SPECIFICATIONS The three configuration files can be created by running BCS on a BCU/CAL used as a master. Then, these files can be copied to the appropriate directory (1.2/cnfg) on a target BCU, and the target will assume the same configuration values. Changes specific to the target must be made either by running BCS on the target or by making the changes on the master, copying the configuration files to the target, then reversing the changes to restore the master to its baseline conf
Summary of the content on the page No. 17
SPECIFICATIONS LBI-38965 3.2.3.10. Call Processing This section contains specifications on the BCU's call processing capability. CDR Processing A record of each conversation is maintained by the system. A conversation is a collection of calls detailed by RARs that have been correlated based upon call participants and caller pseudo hang time. Each CDR contains the following information: 1. Caller billing ID (BID) 2. Callee BID or GID (group ID) 3. Call type (individual, group, Digital Voice, d
Summary of the content on the page No. 18
LBI-38965 SPECIFICATIONS 3.3. CAL OPERATIONAL SPECIFICATIONS This section outlines the specifications that are unique to the CAL personality. Refer to Figure 4 for the CAL architecture. NOTE Before linking a CAL to a System Manager, consult the EDACS VAX/VMS System Manager’s User’s Manual (LBI-38984) to assure that the proper System Manager configuration has been chosen to handle the number of sites to be monitored. Failure to install a properly sized System Manager may result in the loss of l
Summary of the content on the page No. 19
SPECIFICATIONS LBI-38965 3.3.3. CAL Operation Overview As new RARs enter the system, they are dispatched to an appropriate site handler which reformats and queues the data. When the number of activity records queued exceeds a threshold value obtained from the System Manager at startup, a download request is sent to the System Manager. At any point, the System Manager may log in to the site object and request it to purge its queue of activity messages, start/stop download of activity messages,
Summary of the content on the page No. 20
LBI-38965 INSTALLATION 4. INSTALLATION 4.1. HARDWARE INSTALLATION CAUTION Turn off the power before removing or installing VMEbus boards. Removing or reinstalling the boards while the power is on will damage the boards. This section describes the physical installation of the BCU/CAL. Other configuration is performed during manufacture, and the information necessary is provided in Appendix B. Follow these steps to connect a BCU/CAL to an IMC for the first time (except where indicated otherwis
