Sony Ericsson LBI-38965 - Manuals

Sony Ericsson LBI-38965 – Manual in PDF format online.

Manuals:

Manual

Manual Sony Ericsson LBI-38965

Summary

Page 2 - TABLE OF CONTENTS

LBI-38965 2 TABLE OF CONTENTS 1. INTRODUCTION ............................................................................................................................................................. 4 1.1. BCU FUNCTIONAL DESCRIPTION .................................................................

Page 4 - utilize resources and utilities common to both.; A r e a

LBI-38965 4 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 ActivityLogger (BCU/CAL). A block diagram...

Page 6 - PHYSICAL DESCRIPTION AND COMPATIBILITY; General Specifications; Operating Temperature:

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

Page 7 - WANServer

LBI-38965 7 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. Figure 2 - BCU/CAL Architecture TVME712/M Transition Module Communications Module Hard Disk Floppy Disk From CAM Tape Drive SCSI A...

Page 9 - IMC Software V4.01 and later; Backwards Compatibility

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

Page 10 - COMMON BCU AND CAL OPERATIONAL SPECIFICATIONS

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

Page 11 - serial communications link using HDLC protocol.; Figure 3 - Billing Architecture

LBI-38965 11 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. Figure 3 - Billing Architecture 3.2.3. BCU Operation Overview Each RF system sends all call informa...

Page 16 - Figure 4 - CAL Architecture; C e n tr a l iz e d

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

Page 17 - Network File System

LBI-38965 17 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, adownload request is sent...

Page 18 - CAUTION; and the information necessary is provided in Appendix B.

LBI-38965 18 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 onwill damage the boards. This section describes the physical installation of the BCU/CAL. Other configuration is per...

Page 19 - Installation; Product configuration files to be modified by the BCU/CAL end user.

LBI-38965 19 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 attachthe MAU to the network. If the BCU/CAL is being conn...

Page 21 - # Example of a host route; Configuration Tips

LBI-38965 21 Network routes are specified in the following form: type destination_ip gateway gateway_ip Table 4 - ROUTES.DAT File Parameters Parameter Meaning type Keyword for the type of route being added, either host or network. destination_ip IP address of the destination host or network, in Inte...

Page 22 - Export entries are specified in the following form:; directory

LBI-38965 22 Export entries are specified in the following form: directory client_ip Table 5 - EXPORTS.DAT File Parameters Parameter Meaning directory Directory structure(s) to be exported. Must be a fully specified, valid directory on the BCU/CALsystem disk (volume 1.2). Note that directories are c...

Page 23 - # System Manager Password for the site

LBI-38965 23 Table 6 - CAL.DAT File Parameters Parameter Meaning SITE.ss.PASSWD Specifies the System Manager password to be used for logins to/from this site.system_manager_password must match the associated value programmed on the SystemManager for the site specified by ss. SITE.ss.IP Defines the I...

Page 24 - PREREQUISITES; Verify that the BCU/CAL unit does not have power currently applied.

LBI-38965 24 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 duringthe installation, as w...

Page 25 - INSTALLATION; Insert; Installation Diskette 1

LBI-38965 25 INSTALLATION 1. Insert Installation Diskette 1 into the BCU/CAL floppy disk drive. 2. Apply unit power, and observe the user console. The remainder of the installation is provided by way of example.Actual observed output may be slightly different. If the BCU/CAL hard disk drive has neve...

Page 26 - USER ACTION: Remove Installation Diskette 4. Press the Enter key.

LBI-38965 26 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... * Done! 169977 bytes copied. <LOADER> Flop...

Page 28 - PREREQUISITE; Obtain the IMC slot number of the NIM and PIM modules, if any.

LBI-38965 28 USER INFORMATION: Enter “ls” to observe the root level directory files and subdirectories which were createdduring the software installation process. pSH+> lsBITMAP.SYS backup etc mnt var FLIST.SYS bin export rar LOADER.SX cdr loads tmp activity cnfg log usr USER INFORMATION: The fol...

Page 30 - USER INFORMATION: Invoke the BCS program.

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

Page 33 - command to each port on the server by only changing port_no.; NOTE

LBI-38965 33 Configuration Tips If all 16 ports of a terminal server are needed for System Manager interface, first configure 15 of them using a “dumb” terminal connected to port 1. Port 1 (configuration port) may then be re-assigned to a remote port, accessible via a telnetconnection. Telnet into t...

Page 35 - APPENDIX A

LBI-38965 A-1 APPENDIX A EDACS BILLING (CDR) FORMAT

Page 36 - Decimal Equivalent; ABCDEFGHIJ

LBI-38965 A-2 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 usethis record format as input, as well as for de...

Page 38 - CALCULATING THE NUMBER OF BYTES IN A CDR; Table A.1 contains detailed descriptions of each of the CDR fields.; Table A.1 - Call Detail Record Field Descriptions

LBI-38965 A-4 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 co...

Page 39 - CALL TYPE DEFINITIONS; particular call type.; Call Type; Individual, Digital Voice or Data, Bill Caller

LBI-38965 A-5 6. CALL TYPE DEFINITIONS Table A.2 contains the typical values of the call type (CDR field 6). Note that many call types are invalid, and most call types are valid only in conjunction with particular record types (CDR field 1). An “invalid call type” simply indicates thatthese values a...

Page 40 - Reserved Types

LBI-38965 A-6 Table A.2 - Call Types (Cont.) Call Type Description Valid with Hex Decimal Rec. Type 45 69 Group, Digital Voice, System All Call, TX Trunked 00 46-48 70-72 **** Invalid Call Type **** 49 73 Group, Clear Voice, Update, System All Call, TX Trunked 00 4A-4C 74-76 **** Invalid Call Type *...

Page 49 - SCSI Connector; Parity

LBI-38965 B-7 J6 J7 J5 0 1 2 3 4 0 1 2 3 4 SCSI Connector RN2 RN1 (Terminators Removed) Parity SCSI ID = 2 (Factory Set) Motor start on power-up Figure B.6 - Maxtor MXT-1240S Hard Disk

Page 50 - Pwr; Factory Set Jumpers; PWR; Reserved; OFF

LBI-38965 B-8 Pwr SCSI Conn. Factory Set Jumpers RA2 RA1 TEAC FD235HS-711 ID2 ID1 ID0 SCSI ID = 1 (Terminators Removed) Figure B.7 - Teac FD235HS-711 Floppy Disk 1 2 3 4 5 6 7 8 SW1 JP6 JP4 RD2RD1 PWR (Terminators Removed) SCSI Connector ON SCSI ID = 3 Self-Test Reserved DDS Pass-Through (Compressio...

Page 54 - Figure B.9 - CAL Terminal Server to Distribution Panel Cable

LBI-38965 B-12 2 3 9 X P I N 1 P I N 1 3 P IN 1 4 P IN 2 5 5 1 P IN 1 T B D .7 5 N O T E S : 1 . F A B R I C A T E C A B L E T O L E N G T H I N D I C A T E D . N O T E C O N N E C T O R O R I E N T A T IO N C A R E F U L L Y . W IR IN G TA BL E F RO M (I T E M 1 ) R J 1 2- 1 R J 1 2- 2 R J 1 2- 3 R...

Page 56 - A S C II K e yb oa r d

LBI-38965 B-14 C om p u ter T er m in al A S C II K e yb oa r d A 7 P 2 A 7 IN M A C H 3 5 3 -2 A 7 P 1 PO RT 1 /CONSO L E S E R IAL POR T 3 SER IAL PO R T 2 SER IA L P O R T 4 SC SI I N T E R F A C E ETH E R N E T P R IN T E R J 3 P O R T 2D B 2 5 F J 2 P O R T 1D B 2 5 F J 4 P OR T 3D B 2 5F J 1 P...

Page 58 - Figure C.1 - EDACS Billing Fault Tolerant Architecture; connects to the redundant BCU/CAL and tape drive.; REDUNDANT OPERATION

LBI-38965 C-2 Figure C.1 shows the architecture for a fault tolerant EDACS billing system. RF System ConsoleTerminal MIM (Primary) MIM BCU BCU CAM CAM AREA IMC Console Terminal To StarGate Primary Downlink Backup Downlink (Backup) Figure C.1 - EDACS Billing Fault Tolerant Architecture Redundant MIM ...