Ericsson LBI-38965B manuale d’uso

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. Any repairs, alterations or substitution[...]

LBI-38965 3 TABLE OF CONTENTS Page 1. INTRODUCTION ................................................................ ..................................................................................... 5 1.1. BCU FUNCTIONAL DESCRIPTION ................................................................................................ ............. 6 1[...]

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). A block diagram of the BCU/CAL is shown below. The [...]

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

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

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. Feature encryption allows o r disallows B CU or CAL[...]

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

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 microprocessor • Supports BCU/CAL application processing • Interfaces to hard disk, floppy disk, and tape drive via a n on-board small computer system[...]

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 Software V3.01 and later (CAL only) The S[...]

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. The BCU/CAL will adapt t o the data transmission rate to which the Central Activity Module (CAM) is set to oper[...]

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 all call information t o the IMC via the downlink. [...]

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 event results in air time, which is defined as the [...]

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.) • Site number or c[...]

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. Changes specific to the target must be made either b y running BCS o n the targe[...]

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. A conversation is a collection of calls detailed b y RARs that have been correlated based upon call participants and caller pseudo hang ti[...]

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

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. At any po[...]

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. Other configuration is performed during manufacture, and the informat[...]

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. If the BCU/CAL is being connected to a 10BASE-15 (Thick Ether[...]

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 - Second 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. Specified as 8 hexadecimal digits, in upper case. 4.2.1.1.2. ROUTES.DAT Configuration File T[...]

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. Network routes may be manually added and deleted using the route command discussed i n the User Interface Manual (LBI-38[...]

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., preceded with a # character) and thus have no effect whe[...]

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. I n general, beginning TCP port definition at 5000 is saf[...]

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. If the unit is only licensed for the BCU feature, the file CAL.DAT ma[...]

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.SX... * Done! 1200330 bytes copied. <LOADER> Floppy disk has been unmounted. <LOA[...]

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 from the hard disk...* <LOADER> First load comp[...]

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 o f system access security. The following table define[...]

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. PREREQUISITE 1. Obtain the IMC slot number of the NIM and PIM modules, if any. 2. If not al[...]

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. BCS> show system /nim /pim NIM slot = 32 PIM slot = 16 USER ACTION: Exit BCS, which returns the operato[...]

INSTALLATION LBI-38965 33 ************************************************************** * 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 Log[...]

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. These can b e retrieved b y the operator in the event of problems with a new software inst[...]

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 #Terminal server IP address SITE.02.PORT 5002 #TCP port[...]

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.S.A. This page intentionally left blank[...]

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

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

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. A mobile-to-land call never involves multiple sites, so the PSTN Telephone Number field is never [...]

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 n Site Number Channel Map 8 2 6 Decimal Hex 01 - 32 000000 - FFFFFF Information on the site of Origin (field 13) and any additional sites participating in the call[...]

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, Clear Voice, Special Call, Bill Caller 00 22-23 34-35 **** Invalid Call Type **** 24 3 6 Individual, Digital Voice, Special Call, Bill Caller 00, 01 2[...]

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 **** Invalid Call Type **** 64 1 00 Individual, Digital Voice, Jessica, Bill Caller 01 65-6F 101-111 **** Invalid Call Type **** 70 1 12 Individual, Clear Voice,[...]

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. (The call type byte is the 8-bit value represented b y the ASCII encoded, 2-digit hexadecimal number in the CDR call type fiel[...]

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). mm = Minute of the hour the record was created (00 to 59). The maximum number o[...]

[...]

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

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.6 - Maxtor MXT-1240S Hard Disk[...]

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

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 03 RCV-P Receive Data C-01 16 RCV-N C-02 15 TSET-P [...]

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-09 16 RCV-N C-10 15 TSET-P Transmit Clock C-16 12 TSET-N C-12 17 RSET-P Receive Clock A-14 09 RSET-N A-12 04 RTS-P Request To Send A-16 19 RTS-N A-11[...]

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

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-25 16 RCV-N C-26 15 TSET-P Transmit Clock C-32 12 TSET-N C-28 17 RSET-P Receive Clock A-30 09 RSET-N A-28 04 RTS-P Request To Send A-32 19 RTS-N A-27[...]

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 12 TSET-N 17 17 RSET-P Receive Clock 09 09 RSET-N 0[...]

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. NOTE CONNEC T OR O R IENT AT I O N CARE F UL LY. WIRING TAB L E FR O M (ITEM 1 ) R J12 - 1 R J12 - 2 R J12 - 3 R J12 - 3 R J12 - 4 R J12 - 5 D B25 -6 D B25 -4 TO (IT E M 2) DB25-6 DB25-3 DB25-[...]

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 R T 3 P O R T 4 POR T 5 PO R T 6 PORT 7 PORT 8 PO R 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 14 P O R T 1 5 P O R T 1 6 J1 J2 J3 J4 J[...]

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 TE R F AC E ETHER NE T P R I N T E R J3 PORT 2 DB 2 5 F J2 POR T 1 DB25 F J4 PO RT 3 DB25 F J1 PO RT 0 DB25 F TO TE R MI NAL SE RVE R 1 T RAN SCE IVER[...]

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