Ericsson LBI-38965 System And Installation Manual
  1. Manuals
  2. Brands
  3. Ericsson Manuals
  4. Cell Phone
  5. LBI-38965
  6. System and installation manual
Ericsson LBI-38965 System And Installation Manual

Ericsson LBI-38965 System And Installation Manual

Sony ericsson cell phone installation manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
LBI-38965
Mobile Communications
EDACS BCU/CAL
Billing Correlation Unit/
Centralized Activity Logger
System and Installation Manual

Advertisement

Table of Contents
loading

Related Manuals for Ericsson LBI-38965

Summary of Contents for Ericsson LBI-38965

  • Page 1 LBI-38965 Mobile Communications EDACS BCU/CAL Billing Correlation Unit/ Centralized Activity Logger System and Installation Manual...

  • Page 2: Table Of Contents

    LBI-38965 1. INTRODUCTION ... 1.1. BCU FUNCTIONAL DESCRIPTION... 1.2. CAL FUNCTIONAL DESCRIPTION ... 2. PHYSICAL DESCRIPTION AND COMPATIBILITY... 2.1. PHYSICAL SPECIFICATIONS ... 2.2. BCU/CAL ARCHITECTURE... 2.3. COMPATIBILITY ... 3. SPECIFICATIONS... 10 3.1. COMMON BCU AND CAL OPERATIONAL SPECIFICATIONS ... 10 3.1.1.
  • Page 3 4.2.2.3. Proper System Shutdown ... 30 4.2.3. Software Upgrades ... 31 4.3. CAL TERMINAL SERVER CONFIGURATION... 31 APPENDIX A EDACS BILLING (CDR) FORMAT... A-1 APPENDIX B PHYSICAL CONFIGURATION DETAILS ... B-1 APPENDIX C FAULT TOLERANCE... C-1 TABLE OF CONTENTS (Cont.) LBI-38965...

  • Page 4: Introduction

    LBI-38965 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.

  • Page 5: Bcu Functional Description

    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: Console calls. Conventional site calls. Local interconnect calls. Non-EDG data calls. LBI-38965...

  • Page 6: Physical Description And Compatibility

    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.

  • Page 7: Bcu/Cal Architecture

    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 From CAM Platform Ethernet SCSI Formation TVME712/M Transition...
  • Page 8 LBI-38965 The BCU/CAL is based on a VMEbus computing platform with the following components: 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)

  • Page 9: Compatibility

    The User Interface “stats” command will not provide information regarding queued, denied, system busy, and convert-to-callee channel events. CAL-Specific Activity records and site monitoring will not reflect queued, denied, system busy, and convert-to-callee channel events. The site monitor will not provide current control channel indication. LBI-38965...

  • Page 10: Specifications

    LBI-38965 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).

  • Page 11: Billing Architecture

    The CDR format is compatible with Cincinnati Bell Information System’s (CBIS) Cellware billing software. System DAT (Optional) Area StarGate To other IMCs Figure 3 - Billing Architecture System Console Terminal Area LBI-38965 System...

  • Page 12: Rf Channel Usage (Air Time)

    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.

  • Page 13: Time Synchronization

    BCU configuration "database" can be maintained without using BCS to configure each unit manually. Specifies system parameters, default pseudo hang times, and billing modes. Specifies the pseudo hang time associated with each LID. Specifies the pseudo hang time and the group billing mode associated with each GID. LBI-38965 Contents...

  • Page 14: Operator Functions

    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.

  • Page 15: Call Processing

    There are two types of suffix segments. The first is an additional site segment, which identifies the sites and channels used in a multisite call. The second type of suffix is a PSTN phone number field, which is appended to a mobile-originated interconnect call record and contains the digits dialed by the caller. LBI-38965 Each CDR contains the following...

  • Page 16: Cal Operational Specifications

    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.

  • Page 17: Cal Operation Overview

    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.

  • Page 18: Installation

    LBI-38965 4.1. HARDWARE INSTALLATION 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.

  • Page 19: Software Installation

    LOADER.SX - “Bootstrap” loader for the BCU/CAL application. BC_A.SX - First segment of the BCU/CAL executable image. BC_B.SX - Second segment of the BCU/CAL executable image. Product configuration files to be modified by the BCU/CAL end user. Table 1 - BCU/CAL Installation Diskettes Contents LBI-38965...

  • Page 20: User Configuration Files

    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.
  • Page 21 EXPORTS.DAT file. gateway gateway_ip Table 4 - ROUTES.DAT File Parameters Meaning # Example of a host route # Example of a network route 147.117.32.3 # Example of `parsing LBI-38965...
  • Page 22 LBI-38965 Export entries are specified in the following form: directory client_ip Parameter directory Directory structure(s) to be exported. Must be a fully specified, valid directory on the BCU/CAL system disk (volume 1.2). Note that directories are case-sensitive. Specifying the BCU/CAL root directory (1.2/) indicates that the entire volume may be mounted by the host specified by client_ip.
  • Page 23 System Manager and the BCU/CAL. Table 6 - CAL.DAT File Parameters Meaning # System Manager Password for the site # IP address of the terminal server # TCP port number LBI-38965...

  • Page 24: Initial Installation

    LBI-38965 4.2.2. Initial Installation The following section discusses software installation on a new BCU/CAL. An example of the expected terminal display during this sequence is also provided. This example is annotated with comments indicating user activity/procedures during the installation, as well as general information regarding the process.
  • Page 25 Copying BC_A.SX to 01.02/loads/BC_A.SX... * Done! 1200330 bytes copied. <LOADER> Floppy disk has been unmounted. <LOADER> USER ATTENTION REQUIRED. Remove the current installation floppy diskette. Insert the next installation disk (if any). Strike <RETURN> to continue. into the BCU/CAL floppy disk drive. LBI-38965...
  • Page 26 LBI-38965 USER ACTION: Remove Installation Diskette 2. Insert Installation Diskette 3. Press the Enter key. <LOADER> Floppy disk has been mounted. Scanning floppy disk for BCU/CAL installation files... Copying BC_B.SX to 01.02/loads/BC_B.SX... * <LOADER> Floppy disk has been unmounted. <LOADER> USER ATTENTION REQUIRED.

  • Page 27: First-Time Configuration

    Copyright (c) Integrated Systems, Inc., 1992. Welcome to pSOSystem... pSH+> 4 13:55:09 1994 Table 7 - Default System Accounts Access Level Anything. This account is the “super-user.” Can access any BCS commands for system configuration. Most restricted, particularly for the BCS commands. LBI-38965...
  • Page 28 LBI-38965 USER INFORMATION: Enter “ls” to observe the root level directory files and subdirectories which were created during the software installation process. pSH+> ls BITMAP.SYS backup FLIST.SYS LOADER.SX activity cnfg USER INFORMATION: The following example shows the configuration files for the unit. The .BIN files were created during the software installation process.

  • Page 29: System Disk Booting

    <OS> Hard disk has been unmounted. <OS> Transferring program control to LOADER module... <LOADER> Installing BCU/CAL: DATE: May 4, 1994 TIME: 1:56:58 pm <LOADER> Processing file 01.02/cnfg/IP.DAT. Setting IP address: Assigning host name: bcu01 Setting subnet mask: 0xFFFFF000 147.117.37.226 (0x937525E2) LBI-38965...

  • Page 30: Proper System Shutdown

    LBI-38965 <LOADER> Loading file 01.02/loads/BC_A.SX from the hard disk... * <LOADER> First load complete. 393126 bytes loaded. <LOADER> Loading file 01.02/loads/BC_B.SX from the hard disk... * <LOADER> Second load complete. 55692 bytes loaded. <LOADER> Application load complete. 448818 bytes loaded.

  • Page 31: Software Upgrades

    Define the IP address and subnet mask of the terminal server. The IP address, terminal_server_ip, must reflect the associated address defined in the CAL.DAT file. The subnet mask, subnet_mask, should be the same as defined for the BCU/CAL in the IP.DAT configuration file. Server>> set server ip terminal_server_ip Server>> set server subnet mask subnet_mask LBI-38965...
  • Page 32 LBI-38965 For each site defined in the CAL.DAT file, configure the associated port on the terminal server as follows: Server>> change port Server>> change port Server>> change port Server>> change port Server>> change service PORT_< port_no > <TCP port_no > port port_no telnet disabled Server>>...
  • Page 33 Do not use this switch to reset the terminal server. Cycle power or issue the “Initialize server” command from the server configuration port to restart the terminal server. NOTE Ericsson GE Mobile Communications Inc. Mountain View Road Lynchburg Virginia 24502 LBI-38965 Printed in U.S.A.

  • Page 35: Appendix Aedacs Billing (Cdr) Format

    LBI-38965 APPENDIX A EDACS BILLING (CDR) FORMAT...
  • Page 36 LBI-38965 This appendix defines the EDACS call detail record (CDR) format for the collection of system resource usage data in a multisite trunked radio system. The document is intended for use primarily by air time billing software developers who use this record format as input, as well as for developers of equipment and software to collect and archive call detail data from EDACS.
  • Page 37 Figure A.1 - Call Detail Record, Single-Site Call 13 +n. Additional Site n a. No. b. Channel Map x+1 x+2 x+3 x+4 x+5 x+6 x+7 Figure A.2 - Call Detail Record, Additional Site Field 5. Start Time a. Hour b. Minute c. Second b. Channel Map LBI-38965...
  • Page 38 LBI-38965 5.4. CALCULATING THE NUMBER OF BYTES IN A CDR Note that the final linefeed character which terminates the record is not shown in these diagrams. The actual number of bytes in a CDR is calculated by adding 2 to the offset of the final byte. For example, a group call involving 4 sites contains 3 additional site fields, beginning at offset 70 and ending at offset 93 (from the formulae above).
  • Page 39 **** Invalid Call Type **** Group, Clear Voice, System All Call, TX Trunked 42-44 66-68 **** Invalid Call Type **** Table A.2 - Call Types Description LBI-38965 Valid with Rec. Type 00, 01 00, 01, 04 00, 04 00, 04...
  • Page 40 LBI-38965 Call Type Decimal Group, Digital Voice, System All Call, TX Trunked 46-48 70-72 **** Invalid Call Type **** Group, Clear Voice, Update, System All Call, TX Trunked 4A-4C 74-76 **** Invalid Call Type **** Group, Digital Voice, Update, System All Call, TX Trunked...
  • Page 41 System All Call (*Modifies meaning of bits 3 and 4) Jessica Jessica Special Call Reserved Reserved Reserved Bill Caller (*TX Trunked) Bill Callee (*MSG Trunked) Normal Emergency (*Update Call) Clear Voice Digital Voice or Data Individual Call Group Call ICall II Reserved LBI-38965...
  • Page 42 LBI-38965 7. CDR FILE TOPICS CDR files are located in the 1.2/cdr directory. All closed CDR files are named tdddhhmm.CDR, where = Day of the year the record was created (001 to 366). = Hour of the day the record was created (00 to 23).

  • Page 43: Appendix Bphysical Configuration Details

    LBI-38965 APPENDIX B PHYSICAL CONFIGURATION DETAILS...
  • Page 44 LBI-38965 This appendix contains information about jumper settings and cable pinouts for the BCU/CAL. 1. JUMPER SETTINGS Jumper settings for the BCU/CAL components are shown on the pages listed below: Figure B.1 TVME 147SA1 Single-Board Computer ... B-3 B.2 TVME 712/M Transition Module... B-4 B.3 TVME 147P2 Adapter Board ...
  • Page 45 System Controller 2 * AM27C040 Figure B.1 - TVME 147SA1 Single-Board Computer Factory Factory LBI-38965 Serial Port 4 J8 J9...
  • Page 46 LBI-38965 Terminators Removed Figure B.2 - TVME 712/M Transition Module (Terminators Installed) Figure B.3 - TVME 147P2 Adapter Board...
  • Page 47 LBI-38965 Figure B.4 - fv5310 Main Board...
  • Page 48 LBI-38965 PORT 0: DTE WITH DCE PROVIDING RX AND TX CLOCKS *IMC/CAM INTERFACE Figure B.5 - fv5310 Mezzanine Card...
  • Page 49 SCSI Connector (Terminators Removed) (Factory Set) Figure B.6 - Maxtor MXT-1240S Hard Disk Motor start on power-up Parity SCSI ID = 2 LBI-38965...
  • Page 50 LBI-38965 SCSI ID = 1 (Terminators Removed) TEAC FD235HS-711 Figure B.7 - Teac FD235HS-711 Floppy Disk SCSI Connector Reserved Self-Test Figure B.8 - Archive/Maynard 4324NP DAT Factory Set Jumpers (Terminators Removed) SCSI Conn. DDS Pass-Through (Compression Off) Parity On SCSI Mode (SCSI-1)
  • Page 51 RCV-N TSET-P TSET-N RSET-P RSET-N RTS-P RTS-N CTS-P CTS-N DCEREADY-P DCEREADY-N DTEREADY-P DTEREADY-N LBI-38965 Function Transmit Data Receive Data Transmit Clock Receive Clock Request To Send Clear To Send DCE Ready DTE Ready Function Transmit Data Receive Data Transmit Clock...
  • Page 52 LBI-38965 VME P2 Connector A-18 C-19 A-17 C-17 C-18 C-24 C-20 A-22 A-20 A-24 A-19 A-21 C-22 A-23 C-21 C-23 VME P2 Connector A-26 C-27 A-25 C-25 C-26 C-32 C-28 A-30 A-28 A-32 A-27 A-29 C-30 A-31 C-29 C-31 B-10 Table B.3 - WANServer Port 2...
  • Page 53 M/W BCU/CAL Port 0 Signal Name XMT-P XMT-N RCV-P RCV-N TSET-P TSET-N RSET-P RSET-N RTS-P RTS-N CTS-P CTS-N DCEREADY-P DCEREADY-N DTEREADY-P DTEREADY-N LBI-38965 Function Transmit Data Receive Data Transmit Clock Receive Clock Request To Send Clear To Send DCE Ready DTE Ready B-11...
  • Page 54 LBI-38965 WIRING TABLE F RO M (ITE M 1) TO ( IT EM 2) SIGN AL RJ12- 1 D B25-6 DT R RJ12- 2 D B25-3 T XD RJ12- 3 G ND D B25-7 RJ12- 3 D B25-7 G ND...
  • Page 55 J 1 2 J 1 3 42 0 3 8 40 G 1 TER M IN A L SE RV ER 2 Figure B.10 - CAL 32-Port Configuration LBI-38965 J 1 6 J 1 5 J 1 4 J 1 5...
  • Page 56 LBI-38965 EG E P T . N O . 19 C852 327G 1 CO NT RO L IN T ER FAC E B O A RD J 14 T O T ER M IN AL SER VE R 1 T R AN S CEIV ER...

  • Page 57: Appendix Cfault Tolerance

    LBI-38965 APPENDIX C FAULT TOLERANCE...
  • Page 58 LBI-38965 Figure C.1 shows the architecture for a fault tolerant EDACS billing system. Console Terminal Console Terminal 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.

Table of Contents