ページ1に含まれる内容の要旨
LBI-38965
Mobile Communications
EDACS BCU/CAL
Billing Correlation Unit/
Centralized Activity Logger
System and Installation Manual
ページ2に含まれる内容の要旨
LBI-38965 TABLE OF CONTENTS 1. INTRODUCTION ............................................................................................................................................................. 4 1.1. BCU FUNCTIONAL DESCRIPTION.................................................................................................................... 5 1.2. CAL FUNCTIONAL DESCRIPTION ...............................................................................................................
ページ3に含まれる内容の要旨
LBI-38965 TABLE OF CONTENTS (Cont.) 3.3. CAL OPERATIONAL SPECIFICATIONS............................................................................................................ 16 3.3.1. System Manager Interface ............................................................................................................................. 16 3.3.2. Protocol Supported................................................................................................................................
ページ4に含まれる内容の要旨
LBI-38965 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 BCU/CAL works as a subsystem attached to an Ericsson GE Integrated Multisite and Console Controller (IMC) and can be set to operate as a BCU, a CAL, or both. Each
ページ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
ページ6に含まれる内容の要旨
LBI-38965 2. PHYSICAL DESCRIPTION AND COMPATIBILITY This section outlines the specifications, depicts the physical architecture, and provides compatibility information for the BCU/CAL. Software for the BCU and the CAL are merged into one software package. Feature encryption allows or disallows BCU or CAL functionality. The two products can also run on the same hardware platform with minor additions for CAL. 2.1. PHYSICAL SPECIFICATIONS General Specifications BCU/CAL: ELMA VME System 12 7-slo
ページ7に含まれる内容の要旨
LBI-38965 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. VMEbus Backplane P2 Adapter Board RS-232 Appl. SW HDLC Common VME From CAM Platform Ethernet LAN SCSI Formation TVME712/M Transition TVME147 CPU Module WANServer Communications Module Tape Drive Floppy Administrative Terminal Disk Hard Disk To System Manager Terminal Servers (CAL Only) Figure 2 - BCU/CAL Architecture 7
ページ8に含まれる内容の要旨
LBI-38965 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 an on-board small computer systems interface (SCSI) with a connector on the transition module • Interfaces to the console terminal via an RS-232 serial port with a connector on the transition module • Network physical connection i
ページ9に含まれる内容の要旨
LBI-38965 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 System Manager Software version requirement applies only to the CAL feature. The BCU feature operates independent of the System Manager. Thus, the BCU is “compatible” with any System Manager softwar
ページ10に含まれる内容の要旨
LBI-38965 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 to the data transmission rate to which the Central Activity Module (CAM) is set to operate (64K or 360K, selectable via CAM dip switches). BCU/CAL Input Data Each raw activity record (RAR) contains the following information: 1. Day and time of event ac
ページ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 RF RF System System System System Console Console Terminal Terminal Downlink MIM DAT (Optional) MIM MIM MIM DAT (Optional) C Area Area C BCU BCU A IMC A IMC M M High-Speed HDLC Link Ethernet TCP/IP WAN StarGate Customer Billing Mainframe To other IMCs The dotted lines enclose one optional set
ページ12に含まれる内容の要旨
LBI-38965 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 period of time during which the RF channel or group of channels is in use, repeating the signal from a subscriber unit. If the system is operating in transmission t
ページ13に含まれる内容の要旨
LBI-38965 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 console number • Channel number • Caller ID • Callee ID 3.2.3.5. Time Synchronization The time of channel event value is derived from the IMC's internal clock. This is slaved
ページ14に含まれる内容の要旨
LBI-38965 The three configuration files can be created by running BCS on a BCU/CAL used as a master. Then, these files can be 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 by running BCS on the target or by making the changes on the master, copying the configuration files to the target, then reversing the changes to restore the master to its baseline configuration. NOTE
ページ15に含まれる内容の要旨
LBI-38965 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 by the system. A conversation is a collection of calls detailed by RARs that have been correlated based upon call participants and caller pseudo hang time. Each CDR contains the following information: 1. Caller billing ID (BID) 2. Callee BID or GID (group ID) 3. Call type (individual, group, Digital Voice, data, interconne
ページ16に含まれる内容の要旨
LBI-38965 3.3. CAL OPERATIONAL SPECIFICATIONS This section outlines the specifications that are unique to the CAL personality. Refer to Figure 4 for the CAL architecture. 3.3.1. System Manager Interface The CAL interfaces to the System Manager's DECServer(s) via one or two terminal servers capable of supporting up to 32 independent asynchronous RS-232 serial connections. The ports on the CAL's terminal servers are connected to the ports on the System Manager's DECServers via RS-232 cables. 3
ページ17に含まれる内容の要旨
LBI-38965 3.3.3. CAL Operation Overview As new RARs enter the system, they are dispatched to an appropriate site handler which reformats and queues 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 point, the System Manager may log in to the site object and request it to purge its queue of activity messages, start/stop download of activity messages, or start/stop t
ページ18に含まれる内容の要旨
LBI-38965 4. INSTALLATION 4.1. HARDWARE INSTALLATION CAUTION 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 of the BCU/CAL. Other configuration is performed during manufacture, and the information necessary is provided in Appendix B. Follow these steps to connect a BCU/CAL to an IMC for the first time (except where indicated otherwise, these step
ページ19に含まれる内容の要旨
LBI-38965 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 to the network. If the BCU/CAL is being connected to a 10BASE-15 (Thick Ethernet) network, no MAU is required. Attach the transceiver cable directly to the 15-pin connector on the transition module. If CAL is to be enabled for this installation, then c
ページ20に含まれる内容の要旨
LBI-38965 The following table summarizes the configuration files contained on Installation Diskette 4. These files are provided in template form, and should be modified to suit customer-specific requirements. The files are in MS-DOS format, and may be edited with any ASCII text editor. Table 2 - BCU/CAL Configuration Diskette File Name Usage IP.DAT Defines the IP address, subnet mask, and host name of the BCU/CAL. ROUTES.DAT Defines network routing paths between the BCU/CAL and other hosts on
