Instruction/ maintenance manual of the product LBI-38965B Ericsson
Go to page of 64
LBI-38965B System and Installation Manual EDACS BCU/CAL Billing Correlation Unit/ Centralized Activity Logger.
LBI-38965 2 Copyright August 1994, Ericsson Mobile Communications Inc. 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.
LBI-38965 3 TABLE OF CONTENTS Page 1. INTRODUCTION ................................................................ ..................................................................................... 5 1.1. BCU FUNCTIONAL DESCRIPTION ...............
LBI-38965 4 TABLE OF CONTENTS (Cont.) Page 4. INSTALLATION ................................................................................................ .................................................... 20 4.1. HARDWARE INSTALLATION ............
INTRODUCTION LBI-38965 5 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).
LBI-38965 INTRODUCTION 6 1.1. BCU FUNCTIONAL DESCRIPTION The main function of the BCU i s to generate call detail records (CDRs) to b e transferred to an external billing system for invoice generation.
INTRODUCTION LBI-38965 7 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. Non-EDG data calls are only supported if radios are “wide-area enabled” on the site .
LBI-38965 PHYSICAL DESCRIPTION AND COMPATIBILITY 8 2. PHYSICAL DESCRIPTION AND COMPATIBILITY This section outlines the specifications, depicts the physical architecture, and provides compatibility information for t h e BCU/CAL. Software for the BCU and the CAL are merged into one software package.
PHYSICAL DESCRIPTION AND COMPATIBILITY LBI-38965 9 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. Figure 2 - BCU/CAL Architecture TVME712/M Transition Module Communications Module Hard Disk Floppy Disk From CAM Tape Drive SCSI Appl.
LBI-38965 PHYSICAL DESCRIPTION AND COMPATIBILITY 10 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 micr.
PHYSICAL DESCRIPTION AND COMPATIBILITY LBI-38965 11 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.
LBI-38965 SPECIFICATIONS 12 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.
SPECIFICATIONS LBI-38965 13 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. Figure 3 - Billing Architecture 3.2.
LBI-38965 SPECIFICATIONS 14 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.
SPECIFICATIONS LBI-38965 15 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.
LBI-38965 SPECIFICATIONS 16 The three configuration files can be created b y running BCS o n a BCU/CAL used a s a master. Then, these files can b e copied to the appropriate directory (1.2/cnfg) on a target BCU, and the target will assume the same configuration values.
SPECIFICATIONS LBI-38965 17 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 b y the system.
LBI-38965 SPECIFICATIONS 18 3.3. CAL OPERATIONAL SPECIFICATIONS This section outlines the specifications that are unique to the CAL personality. Refer to Figure 4 for the CA L architecture.
SPECIFICATIONS LBI-38965 19 3.3.3. CAL Operation Overview As new RARs enter the system, they are dispatched to an appropriate site handler which reformats and que ues 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 20 4. INSTALLATION 4.1. HARDWARE INSTALLATION 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 o f the BCU/CAL.
INSTALLATION LBI-38965 21 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 t o the network.
LBI-38965 INSTALLATION 22 The table below summarizes the contents of the distribution disks. Table 1 - BCU/CAL Installation Diskettes Installation Diskette Contents 1 LOADER.SX - “Bootstrap” loader for the BCU/CAL application. 2 BC_A.SX - First segment of the BCU/CAL executable image.
INSTALLATION LBI-38965 23 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.
LBI-38965 INSTALLATION 24 Configuration Tips Network routes should be entered in a logical order. That is, if there are multiple gateways between the BCU/CAL an d a destination, the most direct route(s) should be specified first.
INSTALLATION LBI-38965 25 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.
LBI-38965 INSTALLATION 26 Configuration Tips The TCP port number selection can be o f significance i f 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.
INSTALLATION LBI-38965 27 d. I f 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 fo r which the CAL feature is to provide service.
LBI-38965 INSTALLATION 28 USER ACTION: Remove Installation Diskette 1. Insert Installation Diskette 2. Press the Enter key. <LOADER> Floppy disk has been mounted. Scanning floppy disk for BCU/CAL installation files... Copying BC_A.SX to 01.02/loads/BC_A.
INSTALLATION LBI-38965 29 USER ACTION: Remove Installation Diskette 4. Press the Enter key. <LOADER> Processing file 01.02/cnfg/IP.DAT. Setting IP address: 147.117.37.226 (0x937525E2) Assigning host name: bcu01 Setting subnet mask: 0xFFFFF000 <LOADER> Loading file 01.
LBI-38965 INSTALLATION 30 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.
INSTALLATION LBI-38965 31 These parameters are defined using the BCU/CAL Configuration Service (BCS) program. BCS is discussed i n detail i n LBI-38967. The following example is provided for reference to get the BCU set up and running as quickly as possible.
LBI-38965 INSTALLATION 32 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.
INSTALLATION LBI-38965 33 ************************************************************** * Welcome to the EDACS BCU/CAL. * * * * Copyright (C) Ericsson Private Radio Systems * * Mountain View Road * *.
LBI-38965 INSTALLATION 34 Note that previous software loads and user configuration files are not destroyed when a n upgrade o r configuration change is installed. The BCU/CAL archives up to 3 of the last installations i n the "1.2/backup" directory.
INSTALLATION LBI-38965 35 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.
LBI-38965 INSTALLATION Ericsson Inc. Private Radio Systems Mountain View Road Lynchburg, Virginia 24502 1-800-528-7711 (Outside USA, 804-528-7711) Printed in U.
EDACS BILLING FORMAT LBI-38965 A-1 APPENDIX A EDACS BILLING (CDR) FORMAT.
LBI-38965 EDACS BILLING FORMAT A-2 This appendix defines the EDACS call detail record (CDR) format for the collection o f system resource usage data i n a multisite trunked radio system.
EDACS BILLING FORMAT LBI-38965 A-3 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 t o 49 opqrstuvwx 50 to 59 yz#$ 60 to 63 5.
LBI-38965 EDACS BILLING FORMAT A-4 5.3. MOBILE-TO-LAND TELEPHONE INTERCONNECT CALLS A CDR for a mobile-to-land telephone interconnect call will have a n additional field beginning at byte offset 70. This field contains the digits dialed b y the caller.
EDACS BILLING FORMAT LBI-38965 A-5 Table A.1 - Call Detail Record Field Descriptions (Cont.) No. Name Size Format Range/Values Description 13. 13+n a. b.
LBI-38965 EDACS BILLING FORMAT A-6 Table A.2 - Call Types (Cont.) Call Type Description Valid with Hex Decimal Rec. Type 20 3 2 Individual, Clear Voice, Special Call, Bill Caller 00, 01 21 3 3 Group, .
EDACS BILLING FORMAT LBI-38965 A-7 Table A.2 - Call Types (Cont.) Call Type Description Valid with Hex Decimal Rec. Type 60 9 6 Individual, Clear Voice, Jessica, Bill Caller 01 61-63 97-99 **** Invali.
LBI-38965 EDACS BILLING FORMAT A-8 Call Type Bit Fields The call type values have been selected s o that individual attributes o f the call type may be associated with single- or double-bit fields within the call type byte.
EDACS BILLING FORMAT LBI-38965 A-9 7. CDR FILE TOPICS CDR files are located in the 1.2/cdr directory. All closed CDR files are named t dddhhmm. CDR, where ddd = Day of the year the record was created (001 to 366). h h = Hour of the day the record was created (00 to 23).
.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-1 APPENDIX B PHYSICAL CONFIGURATION DETAILS.
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-2 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 Page B.1 TVME 147SA1 Single-Board Computer .
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-3 J1 J2 2 * AM27C040 U22 U30 Factory Set P1 P2 J5 J6 J3 System Controller Factory Set Serial Port 4 J8 J9 J7 Figure B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-4 Terminators Removed Figure B.2 - TVME 712/M Transition Module (Terminators Installed) Figure B.3 - TVME 147P2 Adapter Board.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-5 Figure B.4 - fv5310 Main Board.
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-6 Figure B.5 - fv5310 Mezzanine Card.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-7 J6 J7 J5 0 1 2 3 4 0 1 2 3 4 SCSI Connector RN2 RN1 (Terminators Removed) Parity SCSI ID = 2 (Factory Set) Motor start on power-up Figure B.
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-8 Pwr SCSI Conn. Factory Set Jumpers RA2 RA1 TEAC FD235HS-711 ID2 ID1 ID0 SCSI ID = 1 (Terminators Removed) Figure B.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-9 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 B-10 Table B.2 - WANServer Port 1 VME P2 Connector DB-25F Connector Signal Name Function A-10 02 XMT-P Transmit Data C-11 14 XMT-N A-09 03 RCV-P Receive Data C.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-11 Table B.3 - WANServer Port 2 VME P2 Connector DB-25F Connector Signal Name Function A-18 02 XMT-P Transmit Data C-19 14 XMT-N A-17 03 RCV-P Receive Data C.
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-12 Table B.4 - WANServer Port 3 VME P2 Connector DB-25F Connector Signal Name Function A-26 02 XMT-P Transmit Data C-27 14 XMT-N A-25 03 RCV-P Receive Data C.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-13 Table B.5 - BCU/CAL HDLC Loopback Cable Specification DB-25M Connector M/W BCU/CAL Port 1 DB-25M Connector M/W BCU/CAL Port 0 Signal Name Function 02 03 X.
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-14 2 3 9X PIN 1 PIN 1 3 PIN 1 4 PIN 2 5 5 1 PI N 1 TBD .75 NO TE S: 1. F ABR IC ATE CA BL E TO LE N GTH INDICATED.
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-15 J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 J11 J12 J13 J14 J15 J16 42 0 3840G1 TER M I N A L SE RV ER 1 4 203840G1 TERMI N AL SE RV ER 2 1 J33 P O R T 1 PO R T 2 P O .
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-16 Compu t e r Te r m in a l ASC II Ke y bo a r d A7P2 A 7 INMAC H 353 -2 A7P 1 PORT 1 /CONSOLE SERIAL POR T 3 SER IA L PO RT 2 SE RI A L P ORT 4 SC S I I N .
FAULT TOLERANCE LBI-38965 C-1 APPENDIX C FAULT TOLERANCE.
LBI-38965 FAULT TOLERANCE C-2 Figure C.1 shows the architecture for a fault tolerant EDACS billing system. RF System Console Terminal MIM (Primary) MIM BCU BCU C A M C A M AREA IMC Console Terminal To StarGate Primary Downlink Backup Downlink (Backup) Figure C.
An important point after buying a device Ericsson LBI-38965B (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Ericsson LBI-38965B yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Ericsson LBI-38965B - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Ericsson LBI-38965B you will learn all the available features of the product, as well as information on its operation. The information that you get Ericsson LBI-38965B will certainly help you make a decision on the purchase.
If you already are a holder of Ericsson LBI-38965B, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Ericsson LBI-38965B.
However, one of the most important roles played by the user manual is to help in solving problems with Ericsson LBI-38965B. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Ericsson LBI-38965B along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
