More than one bit. QPSK is an example

Amplitude Modulation

6 More than one bit. QPSK is an example

For simplicity in the following discussion, we assume one bit per signaling ele.

ment unless otherwise stated. The discussion is not materially affected by this sim plification.

Recall from Figure 2.15 that the reception of digital data involves sampling the incoming signal once per bit time to determine the binary value. One of the diffi culties encountered in such a process is that various transmission impairments will corrupt the signal so that occasional errors will occur. This problem is compounded by a timing difficulty: In order for the receiver to sample the incoming bits properly, it must know the arrival time and duration of each bit that it receives.

Suppose that the sender simply transmits a stream of data bits. The sender has a clock that governs the timing of the transmitted bits. For example, if data are tc be transmitted at one million bits per second (1 Mbps), then one bit will be trans.

mitted every 1110~ = 1 microsecond (ps), as measured by the sender's clock. Typi.

cally, the receiver will attempt to sample the medium at the center of each bit-time.

The receiver will time its samples at intervals of one bit-time. In our example, the sampling would occur once every 1 ps. If the receiver times its samples based on its

5.1 / A S Y N C H R O N O U S A N D S Y N C H R O N O U S TRANSMISSION 141 own clock, then there will be a problem if the transmitter's and receiver's clocks are not precisely aligned. If there is a drift of 1 percent (the receiver's clock is 1 percent faster or slower than the transmitter's clock), then the first sampling will be 0.01 of a bit-time (0.01 ps) away from the center of the bit (center of bit is .5 ps from beginning and end of bit). After 50 or more samples, the receiver may be in error because it is sampling in the wrong bit-time (50 X .01 = .5 ps). For smaller timing differ- ences, the error would occur later, but, eventually, the receiver will be out of step with the transmitter if the transmitter sends a sufficiently long stream of bits and if no steps are taken to synchronize the transmitter and receiver.

Asynchronous Transmission

Two approaches are common for achieving the desired synchronization. The first is called, oddly enough, asynchronous transmission. The strategy with this scheme is to avoid the timing problem by not sending long, uninterrupted streams of bits.

Instead, data are transmitted one character at a time, where each character is five to eight bits in length.' Timing or synchronization must only be maintained within each character; the receiver has the opportunity to resynchronize at the beginning of each new character.

The technique is easily explained with reference to Figure 5.1. When no char- acter is being transmitted, the line between transmitter and receiver is in an idle state. The definition of idle is equivalent to the signaling element for binary 1. Thus, for NRZ-L signaling (see Figure 4.2), which is common for asynchronous transmission, idle would be the presence of a negative voltage on the line. The beginning of a character is signaled by a start-bit with a value of binary 0. This is followed by the five to eight bits that actually make up the character. The bits of the character are transmitted beginning with the least significant bit. For example, for ASCII characters, the first bit transmitted is the bit labeled bl in Table 2.1. Usually, this is followed by a parity bit, which therefore is in the most significant bit position. The parity bit is set by the transmitter such that the total number of ones in the character, including the parity bit, is even (even parity) or odd (odd parity), depending on the convention being used. This bit is used by the receiver for error detection, as discussed in Chapter 6. The final element is a stop, which is a binary 1. A minimum length for the stop is specified, and this is usually 1, 1.5, or 2 times the duration of an ordinary bit. No maximum value is specified. Because the stop is the same as the idle state, the transmitter will continue to transmit the stop signal until it is ready to send the next character.

If a steady stream of characters is sent, the interval between two characters is uniform and equal to the stop element. For example, if the stop is one bit-time and the ASCII characters ABC are sent (with even parity bit), the pattern is 01000001010010000101011000011111

. . .

111.~ The start bit (0) starts the timing sequence for the next nine elements, which are the &bit ASCII code and the stop

The number of bits that comprise a character depends on the code used. We have already seen one common example, the ASCII code, which uses seven bits per character (Table 4-1). Another common code is the Extended Binary Coded Decimal Interchange Code (EBCDIC), which is an 8-bit character code used on all IBM machines except for their personal computers.

In the text, the transmission is shown from left (first bit transmitted) to right (last bit transmitted).

Remain --- - beginning of the next character and then samples the input signal at one-bit intervals for seven intervals. It then looks for the next 1-to-0 transition, which will occur no sooner than one more bit-time.

The timing requirements for this scheme are modest. For example, ASCII characters are typically sent as &bit units, including the parity bit. If the receiver is 5 percent slower or faster than the transmitter, the sampling of the eighth information bit will be displaced by 45 percent and still be correctly sampled. Figure 5.lc shows the effects of a timing error of sufficient magnitude to cause an error in reception. In this example we assume a data rate of 10,000 bits per second (10 kbps);

therefore, each bit is of 0.1 millisecond (ms), or 100 ks, duration. Assume that the receiver is off by 7 percent, or 7 ks per bit-time. Thus, the receiver samples the incoming character every 93 ks (based on the transmitter's clock). As can be seen, the last sample is erroneous.

An error such as this actually results in two errors. First, the last sampled bit is incorrectly received. Second, the bit count may now be out of alignment. If bit 7 is a 1 and bit 8 is a 0, bit 8 could be mistaken for a start bit. This condition is termed

t t t t t t f t t

1 2 3 4 5 6 7 8

5.1 / ASYNCHRONOUS A N D S Y N C H R O N O U S TlUNSMISSION 143 a framing error, as the character plus start and stop bits are sometimes referred to as a frame. A framing error can also occur if some noise condition causes the false appearance of a start bit during the idle state.

Asynchronous transmission is simple and cheap but requires an overhead of two to three bits per character. For example, for an 8-bit code, using a 1-bit-long stop bit, two out of every ten bits convey no information but are there merely for synchronization; thus the overhead is 20%. Of course, the percentage overhead could be reduced by sending larger blocks of bits between the start and stop bits.

However, as Figure 5.lc indicates, the larger the block of bits, the greater the cumu- lative timing error. To achieve greater efficiency, a different form of synchronization, known as synchronous transmission, is used.

Synchronous Transmission

With synchronous transmission, a block of bits is transmitted in a steady stream without start and stop codes. The block may be many bits in length. To prevent timing drift between transmitter and receiver, their clocks must somehow be synchro- nized. One possibility is to provide a separate clock line between transmitter and receiver. One side (transmitter or receiver) pulses the line regularly with one short pulse per bit-time. The other side uses these regular pulses as a clock. This technique works well over short distances, but over longer distances the clock pulses are subject to the same impairments as the data signal, and timing errors can occur. The other alternative is to embed the clocking information in the data signal; for digital signals, this can be accomplished with Manchester or Differential Manchester encoding. For analog signals, a number of techniques can be used; for example, the carrier frequency itself can be used to synchronize the receiver based on the phase of the carrier.

With synchronous transmission, there is another level of synchronization required, so as to allow the receiver to determine the beginning and end of a block of data; to achieve this, each block begins with apreamble bit pattern and generally ends with a postamble bit pattern. In addition, other bits are added to the block that convey control information used in the data link control procedures discussed in Chapter 6. The data plus preamble, postamble, and control information are called a frame. The exact format of the frame depends on which data link control proce- dure is being used.

Figure 5.2 shows, in general terms. a typical frame format for synchronous transmission. Typically, the frame starts with a preamble called a flag, which is eight bit-long. The same flag is used as a postamble. The receiver looks for the occurrence of the flag pattern to signal the start of a frame. This is followed by some number of control fields, then a data field (variable length for most protocols), more control fields, and finally the flag is repeated.

FIGURE 5.2 Synchronous frame format.

144 <:HAPTE,N. 5 / T H E DATA COMMUNICATIONS INTERFACE

For sizable blocks of data, synchronous transmission is far more efficient than asynchronous. Asynchronous transmission requires 20 percent or more overhead.

The control information, preamble, and postamble in synchronous transmission are typically less than 100 bits. For example, one of the more common schemes, HDLC, contains 48 bits of control, preamble, and postamble. Thus, for a 1000-character block of data, each frame consists of 48 bits of overhead and 1000 X 8 = 8,000 bits of data, for a percentage overhead of only 4818048 X 100% = 0.6%.

Two characteristics that distinguish various data link configurations are topology and whether the link is half duplex or full duplex.

The topology of a data link refers to the physical arrangement of stations on a transmission medium. If there are only two stations, (e.g., a terminal and a computer or two computers), the link is point-to-point. If there are more than two stations, then it is a multipoint topology. Traditionally, a multipoint link has been used in the case of a computer (primary station) and a set of terminals (secondary stations). In today's environments, the multipoint topology is found in local area networks.

Traditional multipoint topologies are made possible when the terminals are only transmitting a fraction of the time. Figure 5.3 illustrates the advantages of the multipoint configuration. If each terminal has a point-to-point link to its computer, then the computer must have one I10 port for each terminal. Also, there is a sepa-

T T

Computer T Termmals

(primary) T ' (secondaries)

T T (a) Point-to-point

(b) Multipoint Computer

FIGIJRE 5-3 Traditional computerlterminal configurations.

I I I I I I

T T T T T T

rate transmission line from the computer to each terminal. In a multipoint configuration, the computer needs only a single 110 port, thereby saving hardware costs.

Only a single transmission line is needed, which also saves costs.

Data exchanges over a transmission line can be classified as full duplex or half duplex. With half-duplex transmission, only one of two stations on a point-to-point link may transmit at a time. This mode is also referred to as two-way alternate, suggestive of the fact that two stations must alternate in transmitting; this can be compared to a one-lane, two-way bridge. This form of transmission is often used for terminal-to-computer interaction. While a user is entering and transmitting data, the computer is prevented from sending data, which would appear on the terminal screen and cause confusion.

For full-duplex transmission, two stations can simultaneously send and receive data from each other. Thus, this mode is known as two-way simultaneous and may be compared to a two-lane, two-way bridge. For computer-to-computer data exchange, this form of transmission is more efficient than half-duplex transmission.

With digital signaling, which requires guided transmission, full-duplex operation usually requires two separate transmission paths (e.g., two twisted pairs), while half duplex requires only one. For analog signaling, it depends on frequency; if a station transmits and receives on the same frequency, it must operate in half-duplex mode for wireless transmission, although it may operate in full-duplex mode for guided transmission using two separate transmission lines. If a station transmits on one frequency and receives on another, it may operate in full-duplex mode for wireless transmission and in full-duplex mode with a single line for guided transmission.

Most digital data-processing devices have limited data-transmission capability. Typ- ically, they generate a simple digital signal, such as NRZ-L, and the distance across which they can transmit data is limited. Consequently, it is rare for such a device (terminal, computer) to attach directly to a transmission or networking facility. The more common situation is depicted in Figure 5.4. The devices we are discussing, which include terminals and computers, are generically referred to as data terminal equipment (DTE). A DTE makes use of the transmission system through the medi- ation of data circuit-terminating equipment (DCE). An example of the latter is a modem.

On one side, the DCE is responsible for transmitting and receiving bits, one at a time, over a transmission medium or network. On the other side, the DCE must interact with the DTE. In general, this requires both data and control information to be exchanged. This is done over a set of wires referred to as interchange circuits.

For this scheme to work, a high degree of cooperation is required. The two DCEs that exchange signals over the transmission line or network must understand each

Signal and control lines

transmission line

Data terminal Data circuit-terminating equipment (DTE) equipment (DCE)

(a) Generic interface to transmission medium

(b) Typical configuration

FIGURE 5.4 Data communications interfacing.

other. That is, the receiver of each must use the same encoding scheme (e.g., Man- chester, PSK) and data rate as the transmitter of the other. In addition, each DTE- DCE pair must be designed to interact cooperatively. To ease the burden on data- processing equipment manufacturers and users, standards have been developed that specify the exact nature of the interface between the DTE and the DCE. Such an interface has four important characteristics:

Mechanical Electrical Functional Procedural

The mechanical characteristics pertain to the actual physical connection of the DTE to the DCE. Typically, the signal and control interchange circuits are bundled into a cable with a terminator plug, male or female, at each end. The DTE and DCE must present plugs of opposite genders at one end of the cable, effecting the physical connection; this is analogous to the way residential electrical power is produced.

Power is provided via a socket or wall outlet, and the device to be attached must have the appropriate male plug (two-pronged, two-pronged polarized, or three- pronged) to match the socket.

The electrical characteristics have to do with the voltage levels and timing of voltage changes. Both DTE and DCE must use the same code (e.g., NRZ-L), must use the same voltage levels to mean the same things, and must use the same dura-

tion of signal elements. These characteristics determine the data rates and distances that can be achieved.

Functional characteristics specify the functions that are performed by assign- ing meanings to each of the interchange circuits. Functions can be classified into the broad categories of data, control, timing, and electrical ground.

Procedural characteristics specify the sequence of events for transmitting data, based on the functional characteristics of the interface. The examples that follow should clarify this point.

A variety of standards for interfacing exists; this section presents two of the most important: V.241EIA-232-E, and the ISDN Physical Interface.

The most widely used interface is one that is specified in the ITU-T standard, V.24.

In fact, this standard specifies only the functional and procedural aspects of the interface; V.24 references other standards for the electrical and mechanical aspects.

In the United States, there is a corresponding specification, virtually identical, that covers all four aspects: EIA-232. The correspondence is as follows:

Mechanical: I S 0 2110 Electrical: V.28

c Functional: V.24 Procedural: V.24

EIA-232 was first issued by the Electronic Industries Association in 1962, as RS-232. It is currently in its fifth revision EIA-232-E, issued in 1991. The current V.24 and V.28 specifications were issued in 1993. This interface is used to connect DTE devices to voice-grade modems for use on public analog telecommunications systems. It is also widely used for many other interconnection applications.

Mechanical Specification

The mechanical specification for EIA-232-E is illustrated in Figure 5.5. It calls for a 25-pin connector, defined in I S 0 2110, with a specific arrangement of leads. This connector is the terminating plug or socket on a cable running from a DTE (e.g., terminal) or DCE (e.g., modem). Thus, in theory, a 25-wire cable could be used to connect the DTE to the DCE. In practice, far fewer interchange circuits are used in most applications.

Electrical Specification

The electrical specification defines the signaling between DTE and DCE. Digital signaling is used on all interchange circuits. Depending on the function of the interchange circuit, the electrical values are interpreted either as binary or as control signals. The convention specifies that, with respect to a common ground, a voltage more negative than -3 volts is interpreted as binary 1 and a voltage more positive than f 3 volts is interpreted as binary 0; this is the NRZ-L code illustrated in Figure 4.2. The interface is rated at a signal rate of <20 kbps and a distance of <15 meters.

148 ^CHAT9GER⁵/ THE 13ATA CBMMUNlCATIBPJS INTERFACE

Shield Received Clear to Signal Reserved Unassigned Secondary

data send ground for testing clear to send

FIGURE 5.5 Pin assignments for V.241EIA-232.

Transmitter signal element

timing

Greater distances and data rates are possible with good design, but it is prudent to assume that these limits apply in practice as well as in theory.

The same voltage levels apply to control signals; a voltage more negative than -3 volts is interpreted as an OFF condition and a voltage more positive than +3 volts is interpreted as an ON condition.

Functional Specification

Secondary Secondary Local DTE Ring Transmit signal transmitted received loopback ready indicator element timing

data data

Receiver signal element

timing

'Table 5.1 summarizes the functional specification of the interchange circuits, and Figure 5.5 illustrates the placement of these circuits on the plug. The circuits can be grouped into the categories of data, control, timing, and ground. There is one data circuit in each direction, so full-duplex operation is possible. In addition, there are two secondary data circuits that are useful when the device operates in a half-duplex fashion. In the case of half-duplex operation, data exchange between two DTEs (via their DCEs and the intervening communications link) is only conducted in one direction at a time. However, there may be a need to send a halt or flow-control message to a transmitting device; to accommodate this, the communication link is equipped with a reverse channel, usually at a much lower data rate than the primary channel. At the DTE-DCE interface, the reverse channel is carried on a separate pair of data circuits.

Dans le document Data Communications 3 3 (Page 152-179)