LBI-38965B System and Installation Manual EDACS BCU/CAL Billing Correlation Unit/ Centralized Activity Logger ericssonz
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.
LBI-38965 TABLE OF CONTENTS Page 1. INTRODUCTION..................................................................................................................................................... 5 1.1. BCU FUNCTIONAL DESCRIPTION ............................................................................................................. 6 1.2. CAL FUNCTIONAL DESCRIPTION ............................................................................................................. 6 2.
LBI-38965 TABLE OF CONTENTS (Cont.) Page 4. INSTALLATION ....................................................................................................................................................20 4.1. HARDWARE INSTALLATION....................................................................................................................20 4.2. SOFTWARE INSTALLATION .....................................................................................................................21 4.2.1.
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.
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.
INTRODUCTION LBI-38965 Call Types Supported All EDACS call types except for the following are supported by the CAL: 1. 2. 3. 4. Console calls. Conventional site calls. Local interconnect calls. System all calls. NOTE Non-EDG data calls are only supported if radios are “wide-area enabled” on the site.
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 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.
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 module
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.
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. 2. 3. 4. 5. 6. 7. 8.
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.
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.
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.
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 configuration.
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. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.
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.
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.
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. manufacture, and the information necessary is provided in Appendix B.
INSTALLATION LBI-38965 If the BCU/CAL is being connected to a network, plug a MAU (either coaxial or twisted pair) into the 15-pin female connector labeled "ETHERNET" on the TVME-712/M transition module on the rear of the BCU/CAL enclosure and attach the MAU to the network. If the BCU/CAL is being connected to a 10BASE-15 (Thick Ethernet) network, no MAU is required. Attach the transceiver cable directly to the 15-pin connector on the transition module.
LBI-38965 INSTALLATION The table below summarizes the contents of the distribution disks. Table 1 - BCU/CAL Installation Diskettes Installation Contents Diskette 1 LOADER.SX - “Bootstrap” loader for the BCU/CAL application. 2 BC_A.SX - First segment of the BCU/CAL executable image. 3 BC_B.SX - Second segment of the BCU/CAL executable image. 4 Product configuration files to be modified by the BCU/CAL end user.
INSTALLATION LBI-38965 Table 3 - IP.DAT File Parameters Parameter Meaning IP_ADDRESS IP address of the BCU/CAL, in Internet dotted-decimal notation. HOST_NAME Host name of the BCU/CAL, up to 32 characters long. SUBNET_MASK IP subnet mask for the BCU/CAL. Specified as 8 hexadecimal digits, in upper case. 4.2.1.1.2. ROUTES.DAT Configuration File The ROUTES.DAT configuration file specifies network routing paths to be established at system boot.
LBI-38965 INSTALLATION Configuration Tips Network routes should be entered in a logical order. That is, if there are multiple gateways between the BCU/CAL and a destination, the most direct route(s) should be specified first. Network routes may be manually added and deleted using the route command discussed in the User Interface Manual (LBI-38967).
INSTALLATION LBI-38965 4.2.1.1.4. CAL.DAT Configuration File The CAL.DAT is a mandatory file for execution of the CAL software feature. It defines the interface parameters between the BCU/CAL and the System Manager. The template file defines 32 example sites, which are commented out (i.e., preceded with a # character) and thus have no effect when the file is processed. Entries must be provided for each site interface the CAL will be supporting. The information contained in the CAL.
LBI-38965 INSTALLATION Configuration Tips The TCP port number selection can be of significance if the BCU/CAL is attached to a large or TCP protocol intensive network. If you are unsure of TCP port usage on your network, consult you network administrator prior to assigning these values. In general, beginning TCP port definition at 5000 is safe for most applications. A convenient rule of thumb is to start at 5000, with the lower digits of the port reflecting the associated site number.
INSTALLATION LBI-38965 d. If the BCU/CAL has been purchased with the CAL software feature, the file CAL.DAT on Installation Diskette 4 must be modified. This modification should define each site interface to the System Manager for which the CAL feature is to provide service. If the unit is only licensed for the BCU feature, the file CAL.DAT may be left unmodified from that supplied with the release distribution. e. Reboot the BCU/CAL. INSTALLATION 1.
LBI-38965 INSTALLATION USER ACTION: Remove Installation Diskette 1. Insert Installation Diskette 2. Press the Enter key. Floppy disk has been mounted. Scanning floppy disk for BCU/CAL installation files... Copying BC_A.SX to 01.02/loads/BC_A.SX... * Done! 1200330 bytes copied. Floppy disk has been unmounted. USER ATTENTION REQUIRED. Remove the current installation floppy diskette. Insert the next installation disk (if any). Strike to continue.
INSTALLATION LBI-38965 USER ACTION: Remove Installation Diskette 4. Press the Enter key. Processing file 01.02/cnfg/IP.DAT. Setting IP address: 147.117.37.226 (0x937525E2) Assigning host name: bcu01 Setting subnet mask: 0xFFFFF000 Loading file 01.02/loads/BC_A.SX from the hard disk...* First load complete. 393126 bytes loaded. Loading file 01.02/loads/BC_B.SX from the hard disk... * Second load complete. 55692 bytes loaded.
LBI-38965 INSTALLATION 4.2.2.1. First-Time Configuration The following section describes the minimal set of system initializations that a user must perform to set up a BCU/CAL. When the BCU/CAL software is first installed, three user accounts are initialized. Each account has a varying level of system access security. The following table defines the initial accounts and their passwords, arranged in decreasing levels of access. The login name and password are case-sensitive.
INSTALLATION LBI-38965 These parameters are defined using the BCU/CAL Configuration Service (BCS) program. BCS is discussed in detail in LBI-38967. The following example is provided for reference to get the BCU set up and running as quickly as possible. PREREQUISITE 1. 2. Obtain the IMC slot number of the NIM and PIM modules, if any. If not already logged into the BCU/CAL, log in under the "root" account as previously discussed. Enter the following commands at the indicated prompts.
LBI-38965 INSTALLATION USER ACTION: If either of the previous commands were executed, you can verify them by entering the following command. The previous two steps may be repeated in case the values were incorrectly entered by the operator. BCS> show system /nim /pim NIM slot = 32 PIM slot = 16 USER ACTION: Exit BCS, which returns the operator the pSH+> prompt. BCS> exit pSH+> 4.2.2.2.
INSTALLATION LBI-38965 ************************************************************** * Welcome to the EDACS BCU/CAL. * * * * Copyright (C) Ericsson Private Radio Systems * * Mountain View Road * * Lynchburg, Virginia 24502 * * 1993,1994 * ************************************************************** System boot complete: Wed May 4 13:58:50 Login: 4.2.2.3. Proper System Shutdown The BCU/CAL must be shut down in an orderly fashion prior to a system reboot.
LBI-38965 INSTALLATION Note that previous software loads and user configuration files are not destroyed when an upgrade or configuration change is installed. The BCU/CAL archives up to 3 of the last installations in the "1.2/backup" directory. These can be retrieved by the operator in the event of problems with a new software installation, or errors in the end user modified configuration files. 4.3.
INSTALLATION LBI-38965 EXAMPLE: Assume that the file CAL.DAT has the following two site entries: System Manger site 2 is connected to port 3 on the distribution panel, and System Manager site 10 is connected to port 6 on the distribution panel. SITE.02.PASSWD SITE.02.IP SITE.02.PORT SITE02 147.117.37.10 5002 #Terminal server IP address #TCP port_no used for site 2 SITE.10.PASSWD SITE.10.IP SITE.10.PORT SITE10 147.117.37.
LBI-38965 INSTALLATION This page intentionally left blank Ericsson Inc. Private Radio Systems Mountain View Road Lynchburg, Virginia 24502 1-800-528-7711 (Outside USA, 804-528-7711) Printed in U.S.A.
EDACS BILLING FORMAT LBI-38965 APPENDIX A EDACS BILLING (CDR) FORMAT A-1
LBI-38965 EDACS BILLING FORMAT This appendix defines the EDACS call detail record (CDR) format for the collection of system resource usage data in a multisite trunked radio system. The document is intended for use primarily by air time billing software developers who use this record format as input, as well as for developers of equipment and software to collect and archive call detail data from EDACS. 1.
EDACS BILLING FORMAT LBI-38965 The following table defines the ASCII characters used in the CDR radix-64 sequence number field, and their associated decimal values. CDR Radix-64 Digit Decimal Equivalent 0123456789 0 to 9 ABCDEFGHIJ 10 to 19 KLMNOPQRST 20 to 29 UVWXYZabcd 30 to 39 efghijklmn 40 to 49 opqrstuvwx 50 to 59 yz#$ 60 to 63 5. RECORD LAYOUT 5.1. SINGLE-SITE CALLS The following diagram shows the layout of the fields in a basic CDR for a single-site call.
LBI-38965 EDACS BILLING FORMAT 5.3. MOBILE-TO-LAND TELEPHONE INTERCONNECT CALLS A CDR for a mobile-to-land telephone interconnect call will have an additional field beginning at byte offset 70. This field contains the digits dialed by the caller. A mobile-to-land call never involves multiple sites, so the PSTN Telephone Number field is never combined with the Additional Site fields described in the preceding section. 14. PSTN Telephone No.
EDACS BILLING FORMAT LBI-38965 Table A.1 - Call Detail Record Field Descriptions (Cont.) No. 13. 13+n a. b. Name Site of Origin / Additional Site n Site Number Channel Map Size 8 14. PSTN Telephone No. 32 2 6 Format Decimal Hex Range/Values 01 - 32 000000 - FFFFFF Dialed Digits Description Information on the site of Origin (field 13) and any additional sites participating in the call. Site number (site 32 represents a remote node). A hexadecimal bitmap, where bit 0 = channel 1.
LBI-38965 EDACS BILLING FORMAT Table A.2 - Call Types (Cont.) Call Type Hex Description Valid with Decimal Rec.
EDACS BILLING FORMAT LBI-38965 Table A.2 - Call Types (Cont.) Call Type Hex Description Valid with Decimal Rec.
LBI-38965 EDACS BILLING FORMAT Call Type Bit Fields The call type values have been selected so that individual attributes of the call type may be associated with single- or double-bit fields within the call type byte. (The call type byte is the 8-bit value represented by the ASCII encoded, 2-digit hexadecimal number in the CDR call type field.) Table A.3 shows these bit fields and their meaning. Table A.
EDACS BILLING FORMAT LBI-38965 7. CDR FILE TOPICS CDR files are located in the 1.2/cdr directory. All closed CDR files are named tdddhhmm.CDR, where ddd hh mm = Day of the year the record was created (001 to 366). = Hour of the day the record was created (00 to 23). = Minute of the hour the record was created (00 to 59). The maximum number of call records which will be written to a single CDR file is controlled by the “bcs” utility.
PHYSICAL CONFIGURATION DETAILS LBI-38965 APPENDIX B PHYSICAL CONFIGURATION DETAILS B-1
LBI-38965 PHYSICAL CONFIGURATION DETAILS This appendix contains information about jumper settings and cable pinouts for the BCU/CAL. 1. JUMPER SETTINGS Jumper settings for the BCU/CAL components are shown on the pages listed below. Figure B.1 B.2 B.3 B.4 B.5 B.6 B.7 B.8 B-2 Page TVME 147SA1 Single-Board Computer ................................................................. B-3 TVME 712/M Transition Module ...........................................................................
PHYSICAL CONFIGURATION DETAILS LBI-38965 P1 P2 J7 Serial Port 4 J5 J8 J9 Factory Set System Controller J3 J6 2 * AM27C040 Factory Set U22 J1 U30 J2 Figure B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS Terminators Removed Figure B.2 - TVME 712/M Transition Module (Terminators Installed) Figure B.
PHYSICAL CONFIGURATION DETAILS LBI-38965 Figure B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS Figure B.
PHYSICAL CONFIGURATION DETAILS LBI-38965 SCSI Connector J6 RN1 RN2 (Terminators Removed) J7 4 3 2 1 0 4 3 2 1 0 Motor start on power-up Parity SCSI ID = 2 (Factory Set) J5 Figure B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS TEAC FD235HS-711 Factory Set Jumpers Pwr ID2 (Terminators Removed) RA2 ID1 SCSI ID = 1 ID0 RA1 SCSI Conn. Figure B.7 - Teac FD235HS-711 Floppy Disk SCSI Connector RD2 RD1 JP4 JP6 Reserved Self-Test DDS Pass-Through (Compression Off) Parity On SCSI Mode (SCSI-1) OFF SW1 (Terminators Removed) 8 7 6 5 4 PWR 2 1 SCSI ID = 3 Figure B.
PHYSICAL CONFIGURATION DETAILS LBI-38965 2. CABLE PINOUTS BCU/CAL Internal Wiring - VME P2 Backplane connector (of WANServer card) to DB-25 connectors on backplate Table B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS Table B.
PHYSICAL CONFIGURATION DETAILS LBI-38965 Table B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS Table B.
PHYSICAL CONFIGURATION DETAILS LBI-38965 Table B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS WIRING TABLE FROM (ITEM 1) RJ12-1 RJ12-2 RJ12-3 RJ12-3 RJ12-4 RJ12-5 DB25-6 DB25-4 TO (ITEM 2) DB25-6 DB25-3 DB25-7 DB25-7 DB25-2 DB25-20 DB25-8 DB25-5 SIGNAL WIRE WIRE COLOR DTR TXD GND GND RXD DSR DCD RTS/CTS ITEM 5 ITEM 5 ITEM 5 ITEM 5 ITEM 5 ITEM 5 ITEM 4 ITEM 4 WHITE BLACK RED GREEN YELLOW BLUE WHITE WHITE 2 3 TBD 9X PIN 1 PIN 14 PIN 13 PIN 25 .75 PIN 1 5 1 G1 NOTES: 1. FABRICATE CABLE TO LENGTH INDICATED. NOTE CONNECTOR ORIENTATION CAREFULLY.
A14 INMAC H1060-1 1 J1 J2 J3 J4 J5 J6 J7 J8 J9 A12 2203810G1 A12 2203810G 1 A12 2203810G1 PORT 32 P ORT 31 PORT 30 PORT 29 PORT 16 PORT 15 PORT 14 P ORT 13 A12 2203810G1 A12 2203810G1 A12 2203810G1 A12 2203810G1 J15 A12 2203810G1 A12 2203810G1 J1 4 PORT 12 A12 2203810G1 J13 PORT 28 J33 PORT 11 J1 0 J11 J12 PORT 27 A12 2203810G1 A14 INMAC H1060-1 A12 2203810G1 A12 2203810G1 PORT 10 J9 PORT 26 J8 A12 2203810G1 A12 2203810G1 J7 PORT 9 J6 P OR T 25 J5 A12 2203810G1
LBI-38965 PHYSICAL CONFIGURATION DETAILS EGE PT. NO. 19C852327G1 CONTROL INTERFACE BOARD J14 J15 J1 A6P2 A6 2203710G1 J2 J3 BCU/CAL REAR PANEL J4 I/O PANEL / TRANSITION MODULE J5 J2 PORT 1 DB25F SCSI INTERFACE TRANSCEIVER SERIAL PORT 2 TO TERMINAL SERVER 1 ETHERNET J4 PORT 3 DB25F SERIAL PORT 4 J3 PORT 2 DB25F PRINTER Figure B.
FAULT TOLERANCE LBI-38965 APPENDIX C FAULT TOLERANCE C-1
LBI-38965 FAULT TOLERANCE Figure C.1 shows the architecture for a fault tolerant EDACS billing system. RF System Primary Downlink Console Terminal Backup Downlink MIM (Backup) MIM (Primary) C A M BCU AREA C A M IMC BCU Console Terminal To StarGate Figure C.1 - EDACS Billing Fault Tolerant Architecture Redundant MIM processors are added to each RF System interface within the IMC. A duplicate CAM is added, which connects to the redundant BCU/CAL and tape drive.