Sony Ericsson LBI-38965 installation manual BCU Functional Description, CAL Functional Description

Page 5

LBI-38965

1.1. BCU FUNCTIONAL DESCRIPTION

The main function of the BCU is to generate call detail records (CDRs) to be 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 messages which indicate channel assignment and channel drop events to calculate air time, and then generates the CDR.

Call Types Supported

All EDACS call types except for the following are supported by the BCU:

1.Console calls.

2.Conventional site calls.

3.Local interconnect calls.

4.Non-EDG data calls.

1.2.CAL FUNCTIONAL DESCRIPTION

EDACS system administrators require both site monitor and activity download capabilities. These functions are normally supported by the System Manager in conjunction with the Site Controller at each Radio Frequency (RF) System. The CAL provides this capability for EDACS not equipped with a Site Controller.

1.Site Monitor

Provides the system operator at a System Manager terminal with a real-time display of the calls in progress on the RF channels at the selected trunked system.

2.Activity Download

Call activity and system status information are collected by the CAL and buffered in internal memory. Once an operator-defined buffer content threshold is exceeded, the CAL initiates a download of buffer contents to the System Manager. The downloaded information is used to prepare traffic reports on system usage.

In existing EDACS networks, the System Manager communicates with Site Controllers at RF systems using modems and dial-up or leased line connections, routed through a DECServer terminal server. A communications session is set up via a DECServer port between the System Manager and the Site Controller. The System Manager associates the DECServer physical port number with the Site Controller's identity.

Since the IMC is already connected to all the sites, it has centrally available much of the data that individual site controllers normally output to the system manager⎯for all the sites. The CAL connects to the IMC and demultiplexes incoming call activity information messages⎯the same messages that the BCU uses for billing⎯into activity download data and site monitor data to send to a system manager using site controller protocol.

The CAL uses two Internet Protocol (IP) terminal servers on the local area network (LAN) to communicate with the System Manager's DECServer(s). Up to 32 RS-232 asynchronous serial connections are available, 16 per terminal server. One System Manager DECServer port and one IP terminal server port are required per EDACS system being monitored by CAL.

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.Non-EDG data calls.

5

Page 4 Page 6
Image 5
Page 4 Page 6
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 ArchitectureRF Channel Usage Air Time Group Billing ModeConversations Grouping CallsFile Name Contents Operator Functions Default DataDatabase Elements Unit DataCall Processing CDR Processing ErrorsCDR Processing Call Processing CDR OutputProtocol 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 Billing by Conversation OverviewBilling for Multiple Sites Record EncodingSINGLE-SITE Calls Record LayoutMULTIPLE-SITE Calls MOBILE-TO-LAND Telephone Interconnect 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 Cable Pinouts DB-25F Signal Name Function ConnectorTable B.1 WANServer Port Table B.2 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
Top Page Image Contents