GTE Omni Si Database Technical Practices Issue 1 Manual
Have a look at the manual GTE Omni Si Database Technical Practices Issue 1 Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 3 GTE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
TL-130500-1001 l Dial tone is transmitted to the subscriber until the first digit is dialed or timeout occurs. In addition to transmitting dial tone to the originating subscriber, the system checks the subscriber’s class of service. Data base class-of-service tables (resident in system CPU RAM) define to the system exactly what features are assigned to the originator’s lineReception of34.2.8 The subscriber recognizes dial tone as a signal to begin DTMF Digitsdialing the desired number. The CPU prepares to accumulate and interpret the dialed digits. After the first digit is dialed, the CPU removes dial tone from the subscriber. The CPU then writes the address of the special information memory location that contains quiet code into the subscriber’s control memory, thereby disconnecting the subscriber from dial tone (Figure 34.5). The sequence of receiving digits is as follows: e The subscriber commences to key in the number to be called on the touch pad of the DTMF telephone. Each number keyed generates a dual-tone frequency output on the telephone’s tip and ring input connection into the associated line interface card. l The dual-tone frequency from the telephone tip and ring is converted to digital and is applied to a sample gate output on the line interface card. l The Channel Memory card produces binary-coded outputs which are decoded by the PCMFS card into a discrete equipment interface select output. This discrete output from the PCMFS card enables this line interface card sample gate for approximately 1 microsecond, during which time the dual-tone frequency appears on the PCM bus. The output of the line interface card becomes a series of l-microsecond-wide digital pulses whose amplitudes vary in step with the dual-tone frequency inputs from the telephone. l This output is routed through the time-switch Nntwork, and then is applied to the DTMF receiver. l The fast-scan routine (executed every 10 milliseconds) sequentially samples for digit collection on all DTMF receiver channels (time slot) that have been made busy by a request-for-service. o The DTMF receiver output is then applied to the MPB85 card and the MPB85 card transfers up to eight sense-point status inputs onto the CPU bus where is it finally applied to the CPU. During this digit collection routine, the CPU accumulates the dialed digits via the MPB85 card and executes a digit store routine (Figure 34.6). SVR 5210 8187s-333
TL-130500-1001 l During a digit store routine, the CPU stores each digit in a scratch pad area of the CPU memory. The digits are stored in the digit store scratch pad only long enough for the CPU to identify the station being called (dialed). Then, this information is transferred to call store for the duration of the call. (The word format for digit stores and call stores is described in TL- 130200-l 001.) Reception Of34.2.9 The subscriber recognizes dial tone as a signal to begin DP Digitsdialing the desired number. The CPU prepares to accumulate and interpret the dialed digits and, after the first digit is dialed, the CPU removes dial tone from the subscriber. The CPU then writes the address of the special information memory location that contains quiet code into the subscriber’s control memory thus, disconnecting the subscriber from dial tone. The sequence for receiving digits is as follows: l The subscriber commences to rotary dial the number being called. As the rotary dial returns to the home position, it makes and breaks the tip and ring connection into the associated line interface card. Each make and break of the tip and ring connection creates one DP (Dial Pulse) into the line interface card. Dialing a one creates one pulse; dialing a nine creates nine pulses. l Each tip and ring pulse received by the associated line interface card enables and disables a sense point output from a circuit on the line interface card. The dialed pulses cause the sense point output to vary at an 8 to 12 pulses per second rate.Note: The line interface card sense point used for DP digits is the same sense point used to input request-for-service from a DP telephone (i.e., current flow detected). l Each time a line interface card is enabled, the level on the sense point output from the line interface card is applied to the FB-17215-A MPB85 (Multi-Processor Buffer) card. Each sense point is enabled (read) for a period of 1 microsecond. l As well as executing the fast-scan routine every 10 milliseconds, which samples the DP digits, the CPU also routinely executes the DP digit collection routine for those DP telephone channels that have requested service and received dial tone. During the DP digit collection routine, the CPU counts the pulses and interdigital pauses read from the MPB85 card and routinely transmits the accumulated DP digits to the system CPU via the MPB85 card. s-334 8187SVR 5210
Ringing and Ringback SW 521034.2.10 After the CPU has received all the dialed digits, it will determine who is being called or how the call is to be routed. It also checks the subscriber’s class of service (line record code data base tables) to determine if the subscriber is allowed to make the kind of call dialed. If the call is allowed, for instance station-to-station, the CPU determines whether or not the called telephone is busy, sends a ringback (or busy) signal tone to the originating subscriber, and then rings (if not busy) the telephone being called (Figure 34.7). The follows explaines the call processs:l As the CPU routinely addresses the MPB85 card, it reads the sense points of equipment interface cards through the MPB85 card. The sense-point bits indicate the status of the equipment connected to the interface card being scanned. o If the telephone being called is busy (off-hook), the CPU writes into the control memory of the originating subscriber’s time slot the special information memory address that contains 8187s-335 TL-130500-1001 TIME INTERDIGITQUIET, DTMF TONES SWITCH NO. 4 CHANNEL CONTROL - ACONTROL - I3PAD INFORMATION ;;aim 3C: FO : ; 9z2vx78 f D8 f ;///////;i??zy W//A 78: Da I %w//A78 ; 07 ;78; -- I IeY/A40 IFO i80 1 08 : y///Av/4 wd 80) D8 ; wd80 ; 07 ;80 ; -- I 44 IF0241 Ia#x4 w88 kO>Dd m88 kO>Dd w 88 ; 37 f IWm 88 j,‘;;, i 1d, ckt.4 I 50 f A3 I !& Figure 34.5Interdigit and DTMF Tonesl By routinely executing a call store and the associated digit store routines, the system CPU accumulates the dialed DP digits by storing the digits in a scratch pad area of system CPU memory. The digits are stored only long enough for the CPU to identify the station being called (dialed). (The word format for digit stores and call stores is described in TL-130200- 1001.)
TL-130500-1001S-336TIME LAST DIGIT DIALED, DTMF RECEIVER RELEASED !WITCH NO. 5 CHANNEL CONTROL-ACONTROL - BPAD INFORMATION ;wdAo i&I>D8! I& A0 137,071!///////IpriczZ///Iw IN54 A0 !-- I Imd I&Co ’ dial I I tone, ; m,Da lquietliterm 1 1md F8 jga”ti;i Irn Figure’34.6Last Digit Dialed, DTMF Receiver Released Jthe busy signal tone. This action connects the originating subscriber to the busy signal tone. l If the telephone being called is not busy, the CPU enters the time slot assignment routine, and assigns a time slot to the telephone being called by writing the hardware identification number of that telephone into the channel memory of the new time slot (Figure 34.8). o The CPU now sends a control bit to the equipment interface card of the telephone being called, causing the telephone to ring. @ The CPU now writes into the control memory of the originating subscriber’s time slot the special information memory address that contains the ringback signal tone. Answering34.211 When the subscriber being called answers the a Calltelephone, the system CPU detects the off-hook action. The system then stops ringing the telephone. The system CPU also writes into the control memory of the originating subscriber’s time slot; the information memory address of the subscriber (called the subscriber’s time slot). Then the CPU writes into the control memory of the called subscriber’s time slot; the information memory address of the 8187SVR 5210
TL-1305QO-1001SVR 5210TIME SWITCHCALLED TELEPHONE (GROUP A, PCMUS 2, CIRCUIT 6) ASSIGNED TIME SLOT NO. 6 CHANNELCONTROL -ACONTROL - BPAD INFORMATION ;miM 3C: FOf ;m 70 f D8 ! mpz3 IsmA 78 I Da I78 ; 07 I78; --I V////A40 I~0>261 I w//A 80 I Da I y///h4 80 I Da Iaof 07 I y///A80 I PCMI V///AV////AI m/HI;w//9’ lineI44 I24 iaa I Da I wmd aa I Da I ; ckr.6 I ~Y////~ aa I 37 I kvTz/A :vm% 1//////A IV/h y/maa 1 Pm’ linei , C0I dial II tone, I 7559 Da j$& p?4 Fa :g,“g Imr( Figure 34.7Called Telephone Assigned Time SlotTIME SWITCHORIGINATING TELEPHONE RINGBACK, CALLED TELEPHONE RINGS No.7CHANNELCONTROL-ACONTROL - B IwA Figure 34.8Ringback Sent to Originating Caller 8187s-337
TL-130500-1001 originating subscriber’s time slot. This action cross-connects the two time slots so that each is listening to the other.Conversation34.2.12 When the time switch is arranged as shown in Figure 34.9, the two parties can talk to each other, and the two time slots are in a stable call condition. The time switch (under control of the INCKS card) cycles through a regular scanning routine and looks at all of the system time slots, one at a time. During each look. four tasks are executed: l Channel memory is read to obtain the hardware identification number (26) of the originating equipment and assigned to this time slot. A data sample is then taken from the equipment and placed into the time slot information memory (PCM) voice circuit. l Control memory of the originating equipment time slot is read to obtain the address in memory (88) that the time switch reads next. It is the information memory address (of some other time slot) to which the call originator wants to listen. * Information memory of the distant end time slot is read to obtain a data sample (PCM voice circuit 4). The data sample from the distant end time slot is sent to the originating equipment (26) time slot. Based on the exchange of data samples, the two parties are able to conduct conversation. The call remains “stable” until a change in call status occurs (e.g., one party hangs up or a hookswitch flashes). l The fourth task involves writing data into channel memory or control memory. The time switch allocates the last part of its look at each time slot so that the CPU can write data into channel memory or control memory. This is only done when the status of a call is to be changed. (For example, when a time slot is assigned, the CPU must write a hardware identity number into channel memory.) Termination34.2.13 The telephones are placed on-hook when the of Callconversation has ended, and the following occurs: l As part of the slow-scan routine, the CPU detects a change in status of the sense-point status bits related to the station equipment. l The CPU then writes idle data (FO) into channel memory of each time slot (when that time slot is scanned) and then writes the special information memory address of quiet tone (D8) into the control memory of each time slot (Figure 34.10). S-338 8187SVR 5210
SW 52108187TL-130500-1001 TIME SWITCHCALLED STATION ANSWERS, CONVERSATION N0.8 CHANNELCONTROL - ACONTROL - 8PAD INFORMATION ;mqim;m3c I78 f D8 ; p?zqFO 1 v////5 78; D8 1’ 07I f9zvz?i V///d 40; 26 : I z-w/A80 :~8>8d 7a /m/5/~ 78;-- ;80 b8>881 IM88 1~8,801 I %?//A %V/A AO: D8 1#WZ///180 )07>371 m 88; 37 I W//A 1’///////1 AO; 07 ;3 DmFigure 34.9 Conversation TIME CALLTERMINATED SWITCHNO. 9 CHANNEL CONTROL -ACONTROL - BPAD INFORMATION i22zyi2zYx44;w4q+zq3c I78 i D8 i78; D8 ;78 ; 07 I yvk-4FO ’ W//AW//AI W//Ay////578 1-- f40 126>~0I80 k38>~sl Iwd80 188>~4 1ma80 ;37>07[ p//A w5%l80 ;--i w AO; D8 tI///////:AO; 07 ;3 ImaFigure 34.10 Call Terminated s-339
TL-130500-1001 THIS PAGE IS INTENTIONALLY LEFT BLANK. s-3408/87SW 5210
Software Description Executive Class Software Operating System ROM Debugger Boot ROM SVR 5210TL-130500-1001 35.0 The software components used to provide the data system call and interconnect features are divided into the following categories: 0 Executive class software l Packet device handler software e Data call-processing software l Administration, control, and maintenance software Software categories are implemented by using the techniques of compile time switching designed into the program code. All of the code is memory resident. The CHASM high-level language is used on all cards, except the ADMP-C card processor. The ADMP-C card processor is programmed in the language “C”. 35.1Executive class software is the core software that operates the processor based cards used for providing data features for all APMs, SPMs, NICs, UCBs/DCPs, and ADMPs. This software class contains the OS (Operating System), NETLINK, ROMs debugger, and diagnostics software. The executive class software performs the following tasks: 0 Initiating and terminating data processes. l Queuing and de-queuing messages. l Sending and receiving messages to/from other cards. l Allocating and deallocating buffer space. l Providing for software debugging. 0 Carrying out the low-level MPP (Mini-Packet Protocol) link protocol. 35.2 The operating system is a compile time configurable software component that services multiple timed and/or event-driven tasks on two priority levels. It operates on single andiordual 6502 compatible processor systems. The operating system also services the real-time clock and maintains an ;ight-bitmultiple scale timer for each task running under its control. 35.3 The ROM debugger executes commands that provide the following: * Read/modify memory l Halt processing * Single step l Breakpoint software l Dump error logs 35.4 Boot ROMs reside ,311 all RAM-resident cards for the purpose of downloading their code and tables. This download is performed at system initialization, system reconfiguration, and device installation. A common boot ROM is used for the APM, SPM, and UCB/DCP cards. It resides on the A processor. A boot PROM is used on the ADMP-C processor. aia7s-341
TL-130500-1001Netlink35.5 The NETLINK is the software component that provides intercomponent communications across the packet transport system and central packet link. It resides, in various forms, on the APM, SPM, UCWDCP, NIC and ADMP cards. NETLINKconsists of three layers: 0 Layer 1 (Physical Layer). This layer provides the software interface with the packet line interfaces and the packet transport system hardware. 0 Layer 2 (Mini-Packet Protocol Layer). This layer implements the link layer protocol. This guarantees sequenced, error-free delivery of nontransparent control mini-packet traffic on each logical link. It also guarantees sequenced, error-free delivery on nontransparent user mini-packet data traffic. @ Layer 3 (Message Layer). This layer controls the mini-packet protocol layer and provides an interface to all higher level software components for sending and receiving X.25 packets and data control messages (APM and SPM only). SuperlinMADMP35.6 SUPERLINK resides on the ADMP and serves as an interface to transfer messages from NETLINK between the ADMP application tasks on the ADMP-C processor and NETLINK orlthe ADMP-A processor. Messages are transferred via inbound and outbound message transfer lists in the common data area. The inbound message transfer list is for messages from the C processor to the A processor, and the outbound message lists is for messages going in the other direction. ADMP PECLINK35.7 The ADMP-based PECLINK component receives ADMP-bound messages sent over the PEC bus, validates message ntegrity, processes assurance responses, and adds all other valid messages to the PEC-to-ADMP message queue. These messages are then retrieved and processed by the ADMP application tasks. Unknown commands are ignored by the ADMP application task. The PEG-bound messages from the ADMP application tasks are retrieved from the ADMP-to-PEC message queue and sent to the FZC again via the PEC bus. PECLINK will act as a black box for all PEC-bound messages, with the exception of he print event and device event messages, SVR 5210