Ericsson LBI-38965B Redundant Operation, Figure C.1 Edacs Billing Fault Tolerant Architecture

Page 64

LBI-38965

FAULT TOLERANCE

Figure C.1 shows the architecture for a fault tolerant EDACS billing system.

	RF
	System
Console	Primary	Backup
Console	Downlink	Downlink
Terminal

BCU

BCU

Console

Terminal

	MIM		MIM
	MIM		(Backup)
	(Primary)		(Backup)

C

A

M

AREA

CIMC

A M

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.

REDUNDANT OPERATION

The primary and redundant MIM processors operate in a hot standby configuration, i.e., once primary unit failure is detected, the backup becomes the active processor with minimal disruption to calls in progress. The redundant CAM, BCU/CAL and tape drive are operated as on-line mirror duplicates. This eliminates any changeover operation; in the event of failure of one BCU/CAL, or its associated components; the remaining unit continues to operate and process call activity.

C-2

Image 64

Contents Ericssonz LBI-38965 Table of Contents Table of Contents Introduction BCU/CAL ArchitectureCAL Functional Description BCU Functional DescriptionCall Types Supported Introduction Physical Specifications Physical Description and CompatibilityBCU/CAL Architecture TVME147 CPUCPU Compatibility Backwards CompatibilityCommon BCU and CAL Operational Specifications SpecificationsBCU Operational Specifications Billing Architecture Billing Architecture BCU Operation OverviewGroup Billing Mode RF Channel Usage Air TimeConversations Grouping CallsContents File NameDefault Data Operator FunctionsDatabase Elements Unit DataCDR Processing Errors Call ProcessingCDR Processing Call Processing CDR OutputSystem Manager Interface CAL Operational SpecificationsProtocol Supported Additional Product Features Network File System CAL Operation OverviewInstallation Hardware InstallationSoftware Installation Distribution MediaInstallation Diskette UsageROUTES.DAT Configuration File ParameterIP.DAT File Parameters MeaningEXPORTS.DAT Configuration File Directory clientip EXPORTS.DAT File ParametersCAL.DAT Configuration File CAL.DAT File ParametersInitial Installation PrerequisitesInstallation Installation User Information Default System Accounts LoginPassword Access LevelPrerequisite User Information Entering bcs invokes the BCS programSystem Disk Booting Proper System Shutdown Software UpgradesUser Information Invoke the BCS program CAL Terminal Server Configuration # accessConfiguration Tips ExampleThis page intentionally left blank Appendix a Edacs Billing CDR Format Overview Billing by ConversationBilling for Multiple Sites Record EncodingRecord Layout SINGLE-SITE CallsMULTIPLE-SITE Calls CDR Radix-64 DigitMOBILE-TO-LAND Telephone Interconnect Calls Table A.1 Call Detail Record Field DescriptionsCall Type Definitions Call Type Hex DecimalTable A.2 Call Types DescriptionDescription Valid with Rec. Type A0-FF Call Type Bit Fields Table A.3 Call Type Bit Field DefinitionsCDR File Topics Page Appendix B Physical Configuration Details Jumper Settings Figure B.1 Tvme 147SA1 Single-Board Computer Figure B.2 Tvme 712/M Transition Module Figure B.4 fv5310 Main Board Figure B.5 fv5310 Mezzanine Card Scsi Connector Pwr Connector DB-25F Signal Name Cable PinoutsTable B.1 WANServer Port FunctionTable B.2 WANServer Port Table B.3 WANServer Port Table B.4 WANServer Port Table B.5 BCU/CAL Hdlc Loopback Cable Specification DB-25M Connector M/W BCU/CAL Port Signal NameFigure B.9 CAL Terminal Server to Distribution Panel Cable Figure B.10 CAL 32-Port Configuration Computer Terminal Appendix C Fault Tolerance Figure C.1 Edacs Billing Fault Tolerant Architecture Redundant Operation