Ericsson LBI-38965B installation manual Billing Architecture BCU Operation Overview

Page 13

SPECIFICATIONS

LBI-38965

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.

RF	RF
System	System

RF	RF
System	System

Console

TerminalDownlink



DAT (Optional)				MIM		MIM

	BCU	C	Area
	BCU	A	IMC
		A
		M
		M
		High-Speed
		HDLC Link
	Ethernet
	TCP/IP WAN

Console

Terminal

DAT (Optional)

BCU

MIM

MIM

CArea

AIMC

M

StarGate

Customer

Billing

Mainframe

To other IMCs

The dotted lines enclose one optional setup for a StarGate (multi-node) billing architecture.

Figure 3 - Billing Architecture

3.2.3. BCU Operation Overview

Each RF system sends all call information to the IMC via the downlink. This is true for single-channel autonomous trunking (SCAT), Conventional Network Interface (CNI), basic EDACS, and RF systems operating in failsoft mode.

All call activity information messages received by the IMC are collected by the Central Activity Module (CAM), where each call message is time stamped. These messages, called raw activity records (RARs), are then passed via the high-speed serial link to the BCU/CAL. The BCU examines each RAR and uses the time stamp values to determine the length of each call. The actual billing algorithm is quite complex and depends on the BCU's keeping a memory ofoutstanding calls. The output of the billing algorithm is stored to a regular disk file as a series of call detail records (CDR).

The CDR format is compatible with Cincinnati Bell Information System’s (CBIS) Cellware billing software.

13

Image 13

Contents Ericssonz LBI-38965 Table of Contents Table of Contents BCU/CAL Architecture IntroductionCAL Functional Description BCU Functional DescriptionCall Types Supported Introduction Physical Description and Compatibility Physical SpecificationsTVME147 CPU BCU/CAL ArchitectureCPU Backwards Compatibility CompatibilityCommon BCU and CAL Operational Specifications SpecificationsBCU Operational Specifications Billing Architecture BCU Operation Overview Billing ArchitectureRF Channel Usage Air Time Group Billing ModeConversations Grouping CallsFile Name ContentsOperator Functions Default DataDatabase Elements Unit DataCall Processing CDR Processing ErrorsCDR Processing Call Processing CDR OutputSystem Manager Interface CAL Operational SpecificationsProtocol Supported CAL Operation Overview Additional Product Features Network File SystemHardware Installation InstallationDistribution Media Software InstallationUsage Installation DisketteParameter ROUTES.DAT Configuration FileIP.DAT File Parameters MeaningDirectory clientip EXPORTS.DAT File Parameters EXPORTS.DAT Configuration FileCAL.DAT File Parameters CAL.DAT Configuration FilePrerequisites Initial InstallationInstallation Installation User Information Login Default System AccountsPassword Access LevelUser Information Entering bcs invokes the BCS program PrerequisiteSystem Disk Booting Proper System Shutdown Software UpgradesUser Information Invoke the BCS program # access CAL Terminal Server ConfigurationExample Configuration TipsThis page intentionally left blank Appendix a Edacs Billing CDR Format Billing by Conversation OverviewBilling for Multiple Sites Record EncodingSINGLE-SITE Calls Record LayoutMULTIPLE-SITE Calls CDR Radix-64 DigitTable A.1 Call Detail Record Field Descriptions MOBILE-TO-LAND Telephone Interconnect CallsCall Type Hex Decimal Call Type DefinitionsTable A.2 Call Types DescriptionDescription Valid with Rec. Type A0-FF Table A.3 Call Type Bit Field Definitions Call Type Bit FieldsCDR 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 Cable Pinouts Connector DB-25F Signal NameTable B.1 WANServer Port FunctionTable B.2 WANServer Port Table B.3 WANServer Port Table B.4 WANServer Port DB-25M Connector M/W BCU/CAL Port Signal Name Table B.5 BCU/CAL Hdlc Loopback Cable SpecificationFigure B.9 CAL Terminal Server to Distribution Panel Cable Figure B.10 CAL 32-Port Configuration Computer Terminal Appendix C Fault Tolerance Redundant Operation Figure C.1 Edacs Billing Fault Tolerant Architecture