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

Page 11

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

Terminal

Downlink

Console Terminal

DAT (Optional)

BCU

High-Speed

HDLC Link

Ethernet

TCP/IP WAN

C

A

M

MIM

MIM

Area

IMC

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.

If activity logging is enabled, the BCU first archives a copy of each RAR received. The BCU then 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 of outstanding calls. The output of the billing algorithm is stored to a regular disk file as a series of call detail records (CDR). Activity logging of RARs is a diagnostic capability not required for normal BCU functionality. RAR activity logging consumes disk space and can result in degraded system throughput. Although the feature is provided, its use is strongly discouraged for most users.

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

11

Image 11

Contents System and Installation Manual LBI-38965 Table of ContentsTable of Contents BCU/CAL Architecture IntroductionCall Types Supported BCU Functional DescriptionCAL Functional Description Physical Description and Compatibility Physical SpecificationsTVME147 CPU BCU/CAL ArchitectureCPU Backwards Compatibility CompatibilityBCU Operational Specifications SpecificationsCommon BCU and CAL Operational Specifications Billing Architecture BCU Operation Overview Billing ArchitectureGrouping Calls Group Billing ModeRF Channel Usage Air Time ConversationsFile Name Contents Unit Data Default DataOperator Functions Database ElementsCall Processing CDR Output CDR Processing ErrorsCall Processing CDR ProcessingProtocol Supported CAL Operational SpecificationsSystem Manager Interface CAL Operation Overview Additional Product Features Network File SystemHardware Installation InstallationInstallation Contents Diskette Software InstallationParameter Meaning File Name UsageParameter EXPORTS.DAT Configuration FileDirectory Clientip EXPORTS.DAT File Parameters CAL.DAT Configuration FileSITE01 CAL.DAT File ParametersPrerequisites Initial InstallationInstallation Return Login Password Access Level First-Time ConfigurationDefault System Accounts User Information Entering bcs invokes the BCS program PrerequisiteSystem Disk Booting User Information Invoke the BCS program Proper System ShutdownSoftware Upgrades CAL Terminal Server ConfigurationExample Configuration Tips Page Appendix a Edacs Billing CDR Format Record Encoding OverviewBilling by Conversation Billing for Multiple SitesMOBILE-TO-LAND Telephone Interconnect Calls Record LayoutSINGLE-SITE Calls MULTIPLE-SITE CallsName Size Format Range/Values Description Table A.1 Call Detail Record Field DescriptionsCall Type Description Valid with Hex Decimal Rec. Type Call Type DefinitionsTable A.2 Call Types A0-FF Table A.3 Call Type Bit Field Definitions Call Type Bit FieldsCDR File Topics 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 Table B.2 WANServer Port DB-25F Signal Name Function ConnectorCable Pinouts Table B.1 WANServer PortTable B.4 WANServer Port Table B.3 WANServer PortDB-25M Connector Signal Name Function BCU/CAL Port Table B.5 BCU/CAL Hdlc Loopback Cable SpecificationFigure B.9 CAL Terminal Server to Distribution Panel Cable A14 INM AC H106 Computer Terminal Appendix C Fault Tolerance Redundant Operation Figure C.1 Edacs Billing Fault Tolerant Architecture