Ericsson LBI-38965 manual

Mobile Communications EDACS   BCU/CAL Billing Correlation Unit/ Centralized Activity Logger System and Installation Manual LBI-38965[...]

LBI-38965 2 TABLE OF CONTENTS 1. INTRODUCTION ............................................................................................................................................................. 4 1.1. BCU FUNCTIONAL DESCRIPTION ................................................................................................................[...]

LBI-38965 3 TABLE OF CONTENTS (Cont.) 3.3. CAL OPERATIONAL SPECIFICATIONS ............................................................................................................ 16 3.3.1. System Manager Interface ............................................................................................................................. 16 3.3[...]

LBI-38965 4 1. INTRODUCTION This manual contains installation instructions, physical and functional descrip tions, specifications, and usage information for the Enhanced Digital Access Comm unications 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 wor[...]

LBI-38965 5 1.1. BCU FUNCTIONAL DESCRIPTION The main function of the BCU is to generate call d etail records (CDRs) to b e transferred to an external billing system f o r invoice gen eration. To accomplish this, th e B CU scans an in put stream of activity messages supplied by the IMC, archives these messag es in their raw form , uses those message[...]

LBI-38965 6 2. PHYSICAL DESCRIPTION AND COMPATIBILITY This section outlines the specifications, d epicts the physical architecture, and provides compatibility inform atio n for the BCU/CAL. Softw are for the BCU and the CA L are merged into on e software packag e. Feature encryption allow s or disallows BCU or CAL functionality. The two products ca[...]

LBI-38965 7 2.2. BCU/CAL ARCHITECTURE The BCU/CAL 's internal arch itecture is show n in Figure 2. The individual com ponents and their prim ary function s are outlined below. Figure 2 - BCU/CAL Architecture TVME712/M Transition Module Communications Module Hard Disk Floppy Disk From CAM Tape Drive SCSI Appl. SW HDLC RS-232 Ethernet LAN P2 Ada[...]

LBI-38965 8 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 vi a an on-board sm all computer sy stems interf ace (SCSI) with a connector o[...]

LBI-38965 9 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 Softw are version requirem[...]

LBI-38965 10 3. SPECIFICATIONS 3.1. COMMON BCU AND CAL OPERATIONAL SPECIFICATIONS 3.1.1. EDACS System Interface The BCU/CA L interfaces to EDACS v ia a full duplex port supporting hi gh-level data link con trol (HDLC) protocol. The BCU/CAL w ill adap t to the data transmission rate to wh ich the Central Activity Module (CAM) is set to operate (64K [...]

LBI-38965 11 3.2.2. Billing Architecture The EDACS billing system architecture is sho w n 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 all call information to the IMC via the do w nlink. T his is tr[...]

LBI-38965 12 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 w orking RF channels is assigned in response to a request from a subscriber unit (mobile radio, data term inal, etc.). Each chann el assignment even t results in air time, w hich is defined as the perio d of[...]

LBI-38965 13 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 ?[...]

LBI-38965 14 The thre e configuration files can b e created by running BCS o n 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 sam e configuration values. Changes speci fic to the target must be made either by running BCS on the target o r by making [...]

LBI-38965 15 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 maintain ed by the sy stem. A conversation is a collection of calls detailed by RARs that have been correlated based u pon call participants and caller pseudo hang time. Each CDR c[...]

LBI-38965 16 3.3. CAL OPERATIONAL SPECIFICATIONS This section outlines the sp ecifications that are unique to the CAL personality. Ref er to Figure 4 for the CAL architecture. 3.3.1. System Manager Interface The CA L interfaces to the Sys tem Manager' s DECServer(s) via on e or two termin al servers capable of supportin g up to 32 independen t[...]

LBI-38965 17 3.3.3. CAL Operation Overview As new RA Rs enter the system , they are dispatched to an appropriate site h andler which ref o rm ats and queues the data. When the nu mber of activity records queued exceeds a threshold valu e obtained from the Sy stem Manager at startu p, a download request is sent to the System Manager. A t any point, [...]

LBI-38965 18 4. INSTALLATION 4.1. HARDWARE INSTALLATION CAUTION Turn off the power before removing or installing VMEbus boards. Removing or reinstalling the bo ards while the po wer is on will damage the boards. This section describ es the phy sical installation o f the B C U/CAL. Other configuration is performed during manufacture, and the informa[...]

LBI-38965 19 If the B CU/CAL is being connected to a netw o rk, plug a MAU (either coaxial or twisted pair) into the 15-pin female connector labeled "ETHERNET" on the TVME-712/M transition m odule on the rear of the BCU/C AL enclosure and attach the MA U to the netw ork. If the BCU/CAL is being connected to a 10BASE- 15 (T hick Ethern et)[...]

LBI-38965 20 The following tab le sum marizes the co nfiguration files contained on Installation Diskette 4. These files are provided in template form , and should be m odified to suit customer- specific requiremen ts. T he files are in MS-DOS format, and may be edited with any ASCII text editor. Table 2 - BCU/CAL Configuration Diskette File Name U[...]

LBI-38965 21 Network routes are specified in the following form: type destination_ip gateway gateway_ip Table 4 - ROUTES.DAT File Parameters Parameter Meaning type Keyword for the type of route being added, either host or network . destination_ip IP address of the destination host or network, in Internet dotted-decimal notation. gateway Keyword ind[...]

LBI-38965 22 Export entries are specified in the following form: directory client_ip Table 5 - EXPORTS.DAT File Parameters Parameter Meaning directory Directory structure(s) to be exported. Must be a fully specified, valid directory on the BCU/CAL system disk (volume 1.2). Note that directories are case-sensitive. Specify ing the BCU/CA L root dire[...]

LBI-38965 23 Table 6 - CAL.DAT File Parameters Parameter Meaning SITE. ss .PASSWD Specifies the System Manager passw ord to be used for logins to /from this site. system_manager_passw ord m ust match the associated value prog rammed on th e System Manager for the site specified by ss . SITE. ss .IP Defines the Internet IP address, in dotted-decimal[...]

LBI-38965 24 4.2.2. Initial Installation The followin g section discusses softw are installation on a new BCU/CAL. An ex ample of the expected term inal display during this sequence is also pro vided. This example is annotated with comm ents indicating user activity/procedures during the installation, as well as general information regarding the pr[...]

LBI-38965 25 INSTALLATION 1. Insert Installation Diskette 1 into the BCU/CAL floppy disk drive. 2. Apply unit pow er, and observe th e user console. The rem ainder of the instal lation is provided by way of example. Actual observed output may be slightly different. If the B C U/CAL hard disk drive has never been formatted (i.e., system integrator i[...]

LBI-38965 26 USER ACTION: Remove Installation Diskette 2. Insert Installation Diskette 3. Press the Enter key. <LOADER> Floppy disk has been mounted. Scanning floppy disk for BCU/CAL installation files... Copying BC_B.SX to 01.02/loads/BC_B.SX... * Done! 169977 bytes copied. <LOADER> Floppy disk has been unmounted. <LOADER> USER A[...]

LBI-38965 27 ************************************************************** * Welcome to the EDACS BCU/CAL. * * * * Copyright (C) Ericsson GE Mobile Communications * * Mountain View Road * * Lynchburg, Virginia 24502 * * 1993,1994 * ************************************************************** System boot complete: Wed May 4 13:55:09 1994 Login: U[...]

LBI-38965 28 USER INFORMATION: Enter “ls” to observe the root lev el directory files a nd subdirectories w hich w ere created during the software installation process. pSH+> ls BITMAP.SYS backup etc mnt var FLIST.SYS bin export rar LOADER.SX cdr loads tmp activity cnfg log usr USER INFORMATION: The following exam ple shows the configuration [...]

LBI-38965 29 Offload time = 00:00:00 Tape logging = Off CDR archive(s) lifetime = 7 IMC time synchronization = Off RAR activity logging = Off RAR maximum file records = 10000 System ID = 0 Node ID = 0 NIM slot = 0 PIM slot = 0 USER ACTION: To define the IMC NIM slot, execute the following com mand. This exam ple assumes that the NIM occupies slot 3[...]

LBI-38965 30 <LOADER> Loading file 01.02/loads/BC_A.SX from the hard disk... * <LOADER> First load complete. 393126 bytes loaded. <LOADER> Loading file 01.02/loads/BC_B.SX from the hard disk... * <LOADER> Second load complete. 55692 bytes loaded. <LOADER> Application load complete. 448818 bytes loaded. <LOADER> H[...]

LBI-38965 31 4.2.3. Software Upgrades Softw are upgrades are similar to th e initial installation procedu re discussed above. Each time the BC U/CAL boots, it will check to determ ine w hether a floppy diskette is installed. If a diskette is present, it w ill be scanned to check w hether any BCU/CAL installation files are present. If applicable fil[...]

LBI-38965 32 For each site defined in the CAL.DAT file, configure the associated port on the terminal server as follows: Server>> change port port_no access remote Server>> change port port_no type softcopy Server>> change port port_no autobaud disabled Server>> change port port_no speed 19200 Server>> change service P[...]

LBI-38965 33 Configuration Tips If all 16 ports of a term inal server are needed for Sy stem Manag er interface, first conf igure 15 of them using a “dumb” termin al connected to port 1. Port 1 (con figuration port) m ay then be re- assigned to a remote port, accessible via a teln et connection. T elnet into the terminal server on the OVERRIDE [...]

[...]

LBI-38965 A-1 APPENDIX A EDACS BILLING (CDR) FORMAT[...]

LBI-38965 A-2 This appendix defines the EDA CS call detail record (CDR) format f o r the collection of system reso urce usage data in a multisite trunked radio system . T h e d ocument is intended for use primarily by air tim e billing so ftw ar e develop ers who use this record form at as input, as well as f o r developers of equ ipment and soft w[...]

LBI-38965 A-3 5. RECORD LAYOUT 5.1. SINGLE-SITE CALLS The followin g diagram show s the layout of the fields in a basic CDR for a single- site call. The top row sh ows the field name and num b er, the middle row shows the subfield nam e and letter, if ap plicab le, and the b otto m row shows the byte offset within the record. 1. Record Type 2. Node[...]

LBI-38965 A-4 5.4. CALCULATING THE NUMBER OF BYTES IN A CDR Note that th e final linefeed character w hich termin ates the record is not shown in these diagrams. The actual n umber of bytes in a CDR is calculated by adding 2 to the offset of the final byte. For example, a group call involving 4 sites contains 3 additional site fields, beginning at [...]

LBI-38965 A-5 6. CALL TYPE DEFINITIONS Table A.2 contains the ty pical values of the call ty pe (CDR field 6). Note that many call types are invalid, and most call types are valid only in conjunction with particular record types (CDR field 1). An “invalid call ty p e” simply indicates that these values are not generated with this version of BCU[...]

LBI-38965 A-6 Table A.2 - Call Types (Cont.) Call Type Description Valid with Hex Decimal Rec. Type 45 69 Group, Digital Voice, System All Call, TX Trunked 00 46-48 70-72 **** Invalid Call Type **** 49 73 Group, Clear Voice, Update, System All Call, TX Trunked 00 4A-4C 74-76 **** Invalid Call Type **** 4D 77 Group, Digital Voice, Update, System All[...]

LBI-38965 A-7 Call Type Bit Fields The call ty pe values h ave been selected so that individu al attributes of the call type m ay be associated w ith single- or double-bit fields w ithin the call ty pe 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 sho[...]

LBI-38965 A-8 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). hh = Hour of the day the record was created (00 to 23). mm = Minute of the hour the record was created (00 to 59). The maxim um num ber of call records wh ic[...]

LBI-38965 B-1 APPENDIX B PHYSICAL CONFIGURATION DETAILS[...]

LBI-38965 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 ..................................................................... B-3 B.2 TVME 712/M Transi[...]

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.1 - TVME 147SA1 Single-Board Computer[...]

LBI-38965 B-4 Terminators Removed Figure B.2 - TVME 712/M Transition Module (Terminators Installed) Figure B.3 - TVME 147P2 Adapter Board[...]

LBI-38965 B-5 Figure B.4 - fv5310 Main Board[...]

LBI-38965 B-6 Figure B.5 - fv5310 Mezzanine Card PORT 0: DTE WITH DCE PROVIDING RX AND TX CLOCKS *IMC/CAM INTERFACE[...]

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[...]

LBI-38965 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 RD2 RD1 PWR (Terminators Removed) SCSI Connector ON SCSI ID = 3 Self-Test Reserved DDS Pass-Through (Compression Off) Parity On SCSI Mode (SCSI-1) OFF Figure B.[...]

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 Table B.2 - WANServer Port 1 VME P2 Connector DB-25F Connector Signal Name Function A-02 02 XMT-P Transmit Data C-03 14 XMT-N A-01 03 RCV-P Receive Data C-01 16 RCV-N C-02 15 TSET-P Tr[...]

LBI-38965 B-10 Table B.3 - WANServer Port 2 Table B.4 - WANServer Port 3 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-17 16 RCV-N C-18 15 TSET-P Transmit Clock C-24 12 TSET-N C-20 17 RSET-P Receive Clock A-22 09 RSET-N A-20 04 RTS-P Request To Send A-24 19 RTS-N A-19 0[...]

LBI-38965 B-11 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 12 TSET-N 17 17 RSET-P Receive Clock 09 09 RSET-N 04 05 RTS-P Request To Send 19 1[...]

LBI-38965 B-12 2 3 9X PI N 1 PI N 13 PI N 14 PI N 25 5 1 PI N 1 TBD .7 5 NOT ES: 1 . F ABRI CATE CABL E T O L ENGT H I NDI CATED. NOTE CO NNECTO R O RI ENTAT I O N CAREF ULL Y. WIRI NG TAB L E FR O M ( I TEM 1) R J 1 2- 1 R J 1 2- 2 R J 1 2- 3 R J 1 2- 3 R J 1 2- 4 R J 1 2- 5 D B 25 - 6 D B 25 - 4 TO ( I T EM 2) D B 2 5- 6 D B 2 5- 3 D B 2 5- 7 D B[...]

LBI-38965 B-13 J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 J11 J12 J13 J14 J15 J16 420 3 8 40 G 1 TER M I N A L S E R V ER 1 420384 0 G1 TER M I N A L S E RV ER 2 1 J33 P O R T 1 PO R T 2 P O R T 3 P O R T 4 PORT 5 PO R T 6 POR T 7 PO R T 8 POR T 9 P O R T 1 0 P O R T 1 1 P O R T 1 2 P O R T 1 3 PO RT 1 4 P O R T 1 5 P O R T 1 6 J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 J[...]

LBI-38965 B-14 Co mpu t e r Te rm i n a l ASCI I Ke y b o a r d A7 P 2 A 7 IN M A C H 3 5 3 -2 A7P1 PORT 1/ CONSOLE SE RI AL POR T 3 SE R I AL PO R T 2 SERI AL POR T 4 SC SI I N TER F AC E ETH ERN E T P R I N T E R J 3 PORT 2 DB 25 F J2 PORT 1 DB2 5F J4 P O RT 3 DB25 F J1 P OR T 0 DB 25 F TO T ER MI N AL SERVER 1 T RAN SCEI V ER A6 P1 A6 2 203710G [...]

LBI-38965 C-1 APPENDIX C FAULT TOLERANCE[...]

LBI-38965 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.1 - EDACS Billing Fault Tolerant Architecture Redundant MIM processors are added to each RF Sy stem inter[...]