Page 3 - TABLE OF CONTENTS; Page
LBI-38965 3 TABLE OF CONTENTS Page 1. INTRODUCTION..................................................................................................................................................... 5 1.1. BCU FUNCTIONAL DESCRIPTION .....................................................................
Page 5 - INTRODUCTION; utilize resources and utilities common to both.
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 theCentralized Activity Logger (BCU/CAL). A ...
Page 6 - Call Types Supported; NOTE
LBI-38965 INTRODUCTION 6 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 ...
Page 7 - Conventional site calls.
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 . ...
Page 8 - PHYSICAL DESCRIPTION AND COMPATIBILITY; General Specifications; Operating Temperature:
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 the BCU/CAL. Software for the BCU and the CAL are merged into one software package. Fea...
Page 9 - Module; WANServer
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...
Page 11 - IMC Software V4.01 and later; Backwards Compatibility
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.03 • MicroVax System Manager...
Page 13 - SPECIFICATIONS; serial communications link using HDLC protocol.; Figure 3 - Billing Architecture
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.3. BCU Operation Overview Each RF system sends a...
Page 14 - Grouping Calls
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.). Each channel assignment e...
Page 15 - File Name; Specifies the pseudo hang time associated with each LID.
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 dig...
Page 16 - Default Data
LBI-38965 SPECIFICATIONS 16 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...
Page 17 - CDR Processing
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 by the system. A conversation is a collection of calls detailed by RARs that have been correlated based upon ...
Page 18 - Figure 4 - CAL Architecture; Centralized
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 CAL architecture. Before linking a CAL to a System Manager, consult the EDACS VAX/VMS System Manager’s User’s Manual (LBI-38984)t...
Page 19 - Network File System
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 queues the data. When the number of activity records queued exceeds a threshold value obtained from the System Manager at startup, adownload ...
Page 20 - INSTALLATION; on will damage the boards.; CAUTION
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 of the BCU/CAL. Other configuration ...
Page 21 - The red LEDs on the BCU/CAL are not illuminated.
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 attachthe MAU to the network. If the BCU/CAL ...
Page 22 - Installation; Product configuration files to be modified by the BCU/CAL end user.
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. 3 BC_B.SX - Se...
Page 23 - Parameter; Network routes are specified in the following form:; type
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. Specified as 8 hexadecimal digits, in uppe...
Page 24 - these parameters in mind when adjusting ROUTES.DAT contents.; directory
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 and a destination, the most direct route(s) should be specified first. Network routes may be manually added and deleted using the route comman...
Page 25 - unique for every site defined.
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.e., precede...
Page 26 - PREREQUISITES; Verify that the BCU/CAL unit does not have power currently applied.
LBI-38965 INSTALLATION 26 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 thesevalues. In general...
Page 27 - Insert; Installation Diskette 1
INSTALLATION LBI-38965 27 d. If the BCU/CAL has been purchased with the CAL software feature, the file CAL.DAT on InstallationDiskette 4 must be modified. This modification should define each site interface to the System Manager forwhich the CAL feature is to provide service. If the unit is only lic...
Page 29 - USER ACTION: Remove Installation Diskette 4. Press the Enter key.; USER INFORMATION
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.02/loads/BC_A.SX fro...
Page 30 - Table 7 - Default System Accounts
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. Each account has a varying level of s...
Page 31 - PREREQUISITE; Obtain the IMC slot number of the NIM and PIM modules, if any.
INSTALLATION LBI-38965 31 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. Obtain the IMC slot number ...
Page 33 - USER INFORMATION: Invoke the BCS program.
INSTALLATION LBI-38965 33 *************************************************************** Welcome to the EDACS BCU/CAL. ** ** Copyright (C) Ericsson Private Radio Systems ** Mountain View Road ** Lynchburg, Virginia 24502 ** 1993,1994 *************************************************************** S...
Page 34 - port_no access remote
LBI-38965 INSTALLATION 34 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 beretrieved by the operator in the ...
Page 35 - #Terminal server IP address; Configuration Tips; command to each port on the server by only changing port_no.
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.02.PASSWD SITE02 SITE.02.IP 147.117.37.10 #Term...
Page 36 - This page intentionally left blank
LBI-38965 INSTALLATION Ericsson Inc.Private Radio SystemsMountain View RoadLynchburg, Virginia 245021-800-528-7711 (Outside USA, 804-528-7711) Printed in U.S.A. This page intentionally left blank
Page 37 - EDACS BILLING FORMAT; APPENDIX A
EDACS BILLING FORMAT LBI-38965 A-1 APPENDIX A EDACS BILLING (CDR) FORMAT
Page 38 - BILLING BY CONVERSATION
LBI-38965 EDACS BILLING FORMAT A-2 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 usethis record format as inp...
Page 39 - Decimal Equivalent; ABCDEFGHIJ
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...
Page 40 - Table A.1 contains detailed descriptions of each of the CDR fields.; Table A.1 - Call Detail Record Field Descriptions
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 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 sit...
Page 41 - CALL TYPE DEFINITIONS; particular call type.; Call Type; Individual, Digital Voice or Data, Bill 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. Site of Origin /Additional Site nSite NumberChannel Map 8 26 DecimalHex 01 - 32000000 - FFFFFF Information on the site of Origin (field 13) and any ...
Page 43 - Individual, Digital Voice, Jessica Special Call, Bill Caller 01
EDACS BILLING FORMAT LBI-38965 A-7 Table A.2 - Call Types (Cont.) Call Type Description Valid with Hex Decimal Rec. Type 60 96 Individual, Clear Voice, Jessica, Bill Caller 01 61-63 97-99 **** Invalid Call Type **** 64 100 Individual, Digital Voice, Jessica, Bill Caller 01 65-6F 101-111 **** Invalid...
Page 44 - Call Type Bit Fields
LBI-38965 EDACS BILLING FORMAT A-8 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-dig...
Page 45 - ddd
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 tdddhhmm.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). mm = Minute of the hour the rec...
Page 47 - PHYSICAL CONFIGURATION DETAILS; APPENDIX B
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-1 APPENDIX B PHYSICAL CONFIGURATION DETAILS
Page 48 - Figure
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 .................
Page 49 - System Controller
PHYSICAL CONFIGURATION DETAILS LBI-38965 B-3 J1 J2 2 * AM27C040 U22 U30 FactorySet P1 P2 J5 J6 J3 System Controller FactorySet Serial Port 4 J8 J9 J7 Figure B.1 - TVME 147SA1 Single-Board Computer
Page 53 - SCSI Connector; Parity
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.6 - Maxtor MXT-1240S Hard Disk
Page 54 - Pwr; Factory Set Jumpers; PWR; OFF
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.7 - Teac FD235HS-711 Floppy Disk 1 2 3 4 5 6 7 8 SW1 JP6 JP4 RD2RD1 PWR (Terminators Removed) SCSI Connector ON SCSI ID = 3 Self-Test Reserv...
Page 55 - Connector
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.1 - WANServer Port 0 VME P2 Connector DB-25F Connector Signal Name Function A-02 02 XMT-P Transmit Data C-03 14 XMT-N A-01 0...
Page 59 - Signal Name
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 XMT-P Transmit Data 14 16 XMT-N 03 02 RCV-P Receive Data 16 14 RCV-N 15 15 TSET-P Transmit Clock 12 1...
Page 60 - Figure B.9 - CAL Terminal Server to Distribution Panel Cable
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-14 2 3 9X PIN 1 PIN 13 PIN 14 PIN 25 5 1 PIN 1 TBD .75 NOTES: 1. FABRICATE CABLE TO LENGTH INDICATED. NOTE CONNECTOR ORIENTAT IO N CAREFULLY. WIRING TABL E FRO M (ITEM 1) RJ12- 1 RJ12- 2 RJ12- 3 RJ12- 3 RJ12- 4 RJ12- 5 DB25- 6 DB25- 4 TO ( IT EM 2) DB25-6 D...
Page 62 - ASCII Keyboard
LBI-38965 PHYSICAL CONFIGURATION DETAILS B-16 Computer Terminal ASCII Keyboard A7P2 A 7 INM A C H 353 -2 A7P1 P O RT 1 /C O NS O L E SE R IAL PO R T 3 SER IA L PO R T 2 S E RIA L P O RT 4 SC S I I N T E R F AC E ETH E R N E T P R IN T E R J3 PORT 2DB25F J2 PORT 1DB25F J4 PORT 3DB25F J1 PORT 0DB25F T...
Page 63 - FAULT TOLERANCE; APPENDIX C
FAULT TOLERANCE LBI-38965 C-1 APPENDIX C FAULT TOLERANCE
Page 64 - Figure C.1 - EDACS Billing Fault Tolerant Architecture; connects to the redundant BCU/CAL and tape drive.; REDUNDANT OPERATION
LBI-38965 FAULT TOLERANCE C-2 Figure C.1 shows the architecture for a fault tolerant EDACS billing system. RF System ConsoleTerminal MIM (Primary) MIM BCU BCU CAM CAM AREA IMC Console Terminal To StarGate Primary Downlink Backup Downlink (Backup) Figure C.1 - EDACS Billing Fault Tolerant Architectur...