Content
Chapter V
OPERATION AND MAINTENANCE
5.1 Robot Information
Maybe you are interested!
-
Car body electrical practice - 8
zt2i3t4l5ee
zt2a3gs
zt2a3ge
zc2o3n4t5e6n7ts
If the voltage is out of specification, replace the wire or connector.
If the voltage is within specification, install the front fog light relay and follow step 5.
Step 5 Check the front fog light switch
- Remove the D4 connector of the fog light switch
- Use a multimeter to measure the resistance of the front fog light switch.
Measurement location
Condition
Standard
D4-3 (BFG) -D4-4 (LFG)
Light switchFront Fog OFF
>10kΩ
D4-3 (BFG) -D4-4 (LFG)
Front fog light switchON
<1 Ω
- Standard resistor
D4 connector is located on the combination switch assembly.
If the resistance is out of specification, replace the combination switch (the fog light switch is located in the combination switch).
If the resistance is within specification, follow step 6.
Step 6 Check wiring and connectors (front fog light relay-light selector switch)
- Disconnect connector D4 of the combination switch assembly
- Use a voltmeter to measure the voltage value of jack D4 on the wire side.
Measurement location
Control modecontrol
Standard
D4-3 (BFG) - (-) AQ
TAIL
11 to 14 V
D4 connector for the wiring of the combination switch assembly
If the voltage does not meet the standard, replace the wire or connector.
If the voltage is within standard, there may have been an error in the previous measurements.
Step 7 Check the front fog lights
- Remove the front fog light electrical connector.
- Supply battery voltage to the fog lamp terminals
Jack 8, B9 of front fog lamp on the electrical side
blind first.
Power supply location
Terms and Conditions
Battery positive terminal - Terminal 2Battery negative terminal - Terminal 1
Fog lightsbefore morning
- If the light does not come on, replace the bulb.
If the light is on, re-plug the jack and continue to step 8.
Step 8 Check wiring and connectors (relay and front fog lights)
- Disconnect the B8 and B9 connectors of the front fog lights.
- Use a voltmeter to measure voltage at the following locations:
Measurement location
Switch location
Terms and Conditions
B8-2 - (-) AQ
Electric lock ON TAIL size switchFog switch ON
11 to 14 V
B9-2 - (-) AQ
Electric lock ONTAIL size switch Fog switch ON
11 to 14 V
B8 and B9 connectors on the front fog lamp wiring side
Voltage is not up to standard, repair or replace the jack. If up to standard, there may have been an error in the measurement process.
2.2.4. Procedure for removing, installing and adjusting fog lights 1. Procedure for removing
- Remove the front inner ear pads
Use a screwdriver to remove the 3 screws and remove the front part of the front inner ear liner
-Remove the fog light assembly
+ Disconnect the connector.
+ Use a screwdriver to remove 3 screws to remove the fog light cover
2. Installation sequence
-Rotate the fog lamp bulb in the direction indicated by the arrow as shown in the figure and remove the fog lamp from the fog lamp assembly.
-Rotate the fog light bulb in the direction indicated by the arrow as shown in the figure and install the light into the fog light assembly.
- Use a screwdriver to install the fog light cover
-Install the electrical connector
Attention: Be careful not to damage the plastic thread on the lamp assembly.
- Install the front inner ear pads
Use a screwdriver to install the front inner bumper with 3 screws.
3. Prepare the vehicle to adjust the fog light convergence. Prepare the vehicle:
- Make sure there is no damage or deformation to the vehicle body around the fog lights.
- Add fuel to the fuel tank
- Add oil to standard level.
- Add engine coolant to standard level.
- Inflate the tire to standard pressure.
- Place spare tire, tools and jack in original design position
- Do not leave any load in the luggage compartment.
- Let a person weighing about 75 kg sit in the driver's seat.
4. Prepare to check the fog light convergence
a/ Prepare the vehicle status as follows:
- Place the car in a dark enough place to see the lines. The lines are the dividing line, below which the light from the fog lights can be seen but above which it cannot.
- Place the car perpendicular to the wall.
- Keep a distance of 7.62 m between the center of the fog lamp and the wall.
- Park the car on level ground.
- Press the car down a few times to stabilize the suspension.
Note: A distance of approximately 7.62 m is required between the vehicle (fog lamp center) and the wall to adjust the convergence correctly. If the distance of 7.62 m cannot be achieved, set the correct distance of 3 m to check and adjust the fog lamp convergence. (Since the target area varies with the distance, please follow the instructions as shown in the figure.)
b/ Prepare a piece of thick white paper about 2 m high and 4 m wide to use as a screen.
c/ Draw a vertical line through the center of the screen (line V).
d/ Set the screen as shown in the picture. Note:
- Keep the screen perpendicular to the ground.
- Align the V line on the screen with the center of the vehicle.
e/Draw the reference lines (H, V LH and V RH lines) on the screen as shown in the figure.HINT:
Mark the center of the fog lamp on the screen. If the center mark cannot be seen on the fog lamp, use the center of the fog lamp or the manufacturer's name mark on the fog lamp as the center mark.
H line (fog light height):
Draw a line across the screen so that it passes through the center mark. Line H should be at the same height as the center mark of the fog light bulb.
Line V LH, V RH (center mark position of left fog lamp LH and right fog lamp RH):
Draw two lines so that they intersect line H at the center marks.
5. Check the fog light convergence
a/ Cover the fog lamp or remove the connector of the other side fog lamp to prevent light from the unchecked fog lamp from affecting the fog lamp convergence test.
b/ Start the engine.
c/ Turn on the fog lights and make sure that the dividing line is outside the standard area as shown in the drawing.
6. Adjust the fog light convergence
Use a screwdriver to adjust the fog light to the standard area by turning the toe adjustment screw.
Note: If the screw is adjusted too far, loosen it and then tighten it again, so that the last rotation of the light adjustment screw is clockwise.
3. Self-study questions
1. Describe the operating principle of the lighting system with automatic headlight function
2. Describe the operating principle of the lighting system with the function of rotating headlights when turning
3. Draw diagram and connect lighting system on Hyundai Porter car
4. Draw diagram and connect lighting system on Honda Accord 1992
5. Draw the lighting circuit on a 1993 Toyota Lexus
LESSON 3 MAINTENANCE AND REPAIR OF SIGNAL SYSTEM
I. IMPLEMENTATION GOAL
After completing this lesson, students will be able to:
- Distinguish between types of signals on cars
- Correctly describe common symptoms and suspected areas causing damage.
- Connecting signal circuits ensures technical requirements
- Disassemble, install, check, maintain and repair the signal system to ensure technical requirements.
- Ensure safety in work and industrial hygiene
II. LESSON CONTENT
1. General description
The signal system equipped on cars aims to create signals to notify other vehicles participating in traffic about the vehicle's operating status such as: stopping, parking, braking, reversing, turning...
Signals are used either by light such as headlamps, brake lights, turn signals….. or by sound such as horns, reverse music….
Just like the lighting system. A signal system circuit usually consists of: battery, fuse, wire, relay, electrical load and control switch. Only some switches of the signal system are on the combination switch. The switches of other signals are usually located in different locations such as in the gearbox or brake pedal……
2. Maintenance and repair
2.1. Turn signals and hazard lights
The installation location of the turn signal is shown in Figure 3.1. The turn signal control switch is located in the combination switch under the steering wheel. Turning this switch to the right or left will make the turn signal turn right or left.
The hazard light switch is used when the vehicle has a problem while participating in traffic. When the hazard light switch is turned on, all the turn signals on the vehicle will light up at a certain frequency. The hazard light switch is usually placed separately from the turn signal switch (some old cars integrate the hazard and turn signal switches on the same combination switch cluster).
Figure 3.1 Turn signal switch Figure 3.2 Hazard switch
The part that generates the flashing frequency for the lights is called a turn signal relay. The turn signal relay usually has 3 terminals: B (positive power supply); E (negative power supply); L (providing the turn signal switch to distribute to the
lamp)
2.1.1. Circuit diagram
To generate the frequency for the turn signal, a turn signal relay is used in the turn signal circuit. The current from the turn signal relay will be sent to the turn signal switch assembly to distribute the current to the turn signal lights for the driver's purpose.
Figure 3.3. Schematic diagram of a turn signal circuit without a hazard switch
1. Battery; 2. Electric lock; 3. Turn signal relay; 4. Turn signal switch; 5. Turn signal lamp; 6. Turn signal lamp; 7. Hazard switch
Figure 3.4 Schematic diagram of turn signal circuit with hazard switch
1. Battery; 2. Combination switch cluster; 3. Turn signal;
4. Turn signal light; 5. Turn signal relay
Today's cars no longer use three-pin turn signal relays (B, L, E) but use eight-pin turn signal relays (figure 3.5) (pin number 8 is used for hazard lights).
For this type, the current supplying the turn signal lights is supplied directly from the turn signal relay to the lights.
div.maincontent .p { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; } div.maincontent p { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; } div.maincontent .s1 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 13pt; } div.maincontent .s2 { color: black; font-family:"Times New Roman", serif; font-style: italic; font-weight: normal; text-decoration: none; font-size: 14pt; } div.maincontent .s3 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; } div.maincontent .s4 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 13pt; } div.maincontent .s5 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 13pt; vertical-align: 1pt; } div.maincontent .s6 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 11pt; } div.maincontent .s7 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; vertical-align: -9pt; } div.maincontent .s8 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 11pt; } div.maincontent .s9 { color: #008000; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; } div.maincontent .s10 { color: black; font-family:"Times New Roman", serif; font-style: italic; font-weight: normal; te -
Qos Assurance Methods for Multimedia Communications
zt2i3t4l5ee
zt2a3gs
zt2a3ge
zc2o3n4t5e6n7ts
low. The EF PHB requires a sufficiently large number of output ports to provide low delay, low loss, and low jitter.
EF PHBs can be implemented if the output port's bandwidth is sufficiently large, combined with small buffer sizes and other network resources dedicated to EF packets, to allow the router's service rate for EF packets on an output port to exceed the arrival rate λ of packets at that port.
This means that packets with PHB EF are considered with a pre-allocated amount of output bandwidth and a priority that ensures minimum loss, minimum delay and minimum jitter before being put into operation.
PHB EF is suitable for channel simulation, leased line simulation, and real-time services such as voice, video without compromising on high loss, delay and jitter values.
Figure 2.10 Example of EF installation
Figure 2.10 shows an example of an EF PHB implementation. This is a simple priority queue scheduling technique. At the edges of the DS domain, EF packet traffic is prioritized according to the values agreed upon by the SLA. The EF queue in the figure needs to output packets at a rate higher than the packet arrival rate λ. To provide an EF PHB over an end-to-end DS domain, bandwidth at the output ports of the core routers needs to be allocated in advance to ensure the requirement μ > λ. This can be done by a pre-configured provisioning process. In the figure, EF packets are placed in the priority queue (the upper queue). With such a length, the queue can operate with μ > λ.
Since EF was primarily used for real-time services such as voice and video, and since real-time services use UDP instead of TCP, RED is generally
not suitable for EF queues because applications using UDP will not respond to random packet drop and RED will strip unnecessary packets.
2.2.4.2 Assured Forwarding (AF) PHB
PHB AF is defined by RFC 2597. The purpose of PHB AF is to deliver packets reliably and therefore delay and jitter are considered less important than packet loss. PHB AF is suitable for non-real-time services such as applications using TCP. PHB AF first defines four classes: AF1, AF2, AF3, AF4. For each of these AF classes, packets are then classified into three subclasses with three distinct priority levels.
Table 2.8 shows the four AF classes and 12 AF subclasses and the DSCP values for the 12 AF subclasses defined by RFC 2597. RFC 2597 also allows for more than three separate priority levels to be added for internal use. However, these separate priority levels will only have internal significance.
PHB Class
PHB Subclass
Package type
DSCP
AF4
AF41
Short
100010
AF42
Medium
100100
AF43
High
100110
AF3
AF31
Short
011010
AF32
Medium
011100
AF33
High
011110
AF2
AF21
Short
010010
AF22
Medium
010100
AF23
High
010110
AF1
AF11
Short
001010
AF12
Medium
001100
AF13
High
001110
Table 2.8 AF DSCPs
The AF PHB ensures that packets are forwarded with a high probability of delivery to the destination within the bounds of the rate agreed upon in an SLA. If AF traffic at an ingress port exceeds the pre-priority rate, which is considered non-compliant or “out of profile”, the excess packets will not be delivered to the destination with the same probability as the packets belonging to the defined traffic or “in profile” packets. When there is network congestion, the out of profile packets are dropped before the in profile packets are dropped.
When service levels are defined using AF classes, different quantity and quality between AF classes can be realized by allocating different amounts of bandwidth and buffer space to the four AF classes. Unlike
EF, most AF traffic is non-real-time traffic using TCP, and the RED queue management strategy is an AQM (Adaptive Queue Management) strategy suitable for use in AF PHBs. The four AF PHB layers can be implemented as four separate queues. The output port bandwidth is divided into four AF queues. For each AF queue, packets are marked with three “colors” corresponding to three separate priority levels.
In addition to the 32 DSCP 1 groups defined in Table 2.8, 21 DSCPs have been standardized as follows: one for PHB EF, 12 for PHB AF, and 8 for CSCP. There are 11 DSCP 1 groups still available for other standards.
2.2.5.Example of Differentiated Services
We will look at an example of the Differentiated Service model and mechanism of operation. The architecture of Differentiated Service consists of two basic sets of functions:
Edge functions: include packet classification and traffic conditioning. At the inbound edge of the network, incoming packets are marked. In particular, the DS field in the packet header is set to a certain value. For example, in Figure 2.12, packets sent from H1 to H3 are marked at R1, while packets from H2 to H4 are marked at R2. The labels on the received packets identify the service class to which they belong. Different traffic classes receive different services in the core network. The RFC definition uses the term behavior aggregate rather than the term traffic class. After being marked, a packet can be forwarded immediately into the network, delayed for a period of time before being forwarded, or dropped. We will see that there are many factors that affect how a packet is marked, and whether it is forwarded immediately, delayed, or dropped.
Figure 2.12 DiffServ Example
Core functionality: When a DS-marked packet arrives at a Diffservcapable router, the packet is forwarded to the next router based on
Per-hop behavior is associated with packet classes. Per-hop behavior affects router buffers and the bandwidth shared between competing classes. An important principle of the Differentiated Service architecture is that a router's per-hop behavior is based only on the packet's marking or the class to which it belongs. Therefore, if packets sent from H1 to H3 as shown in the figure receive the same marking as packets from H2 to H4, then the network routers treat the packets exactly the same, regardless of whether the packet originated from H1 or H2. For example, R3 does not distinguish between packets from h1 and H2 when forwarding packets to R4. Therefore, the Differentiated Service architecture avoids the need to maintain router state about separate source-destination pairs, which is important for network scalability.
Chapter Conclusion
Chapter 2 has presented and clarified two main models of deploying and installing quality of service in IP networks. While the traditional best-effort model has many disadvantages, later models such as IntServ and DiffServ have partly solved the problems that best-effort could not solve. IntServ follows the direction of ensuring quality of service for each separate flow, it is built similar to the circuit switching model with the use of the RSVP resource reservation protocol. IntSer is suitable for services that require fixed bandwidth that is not shared such as VoIP services, multicast TV services. However, IntSer has disadvantages such as using a lot of network resources, low scalability and lack of flexibility. DiffServ was born with the idea of solving the disadvantages of the IntServ model.
DiffServ follows the direction of ensuring quality based on the principle of hop-by-hop behavior based on the priority of marked packets. The policy for different types of traffic is decided by the administrator and can be changed according to reality, so it is very flexible. DiffServ makes better use of network resources, avoiding idle bandwidth and processing capacity on routers. In addition, the DifServ model can be deployed on many independent domains, so the ability to expand the network becomes easy.
Chapter 3: METHODS TO ENSURE QoS FOR MULTIMEDIA COMMUNICATIONS
In packet-switched networks, different packet flows often have to share the transmission medium all the way to the destination station. To ensure the fair and efficient allocation of bandwidth to flows, appropriate serving mechanisms are required at network nodes, especially at gateways or routers, where many different data flows often pass through. The scheduler is responsible for serving packets of the selected flow and deciding which packet will be served next. Here, a flow is understood as a set of packets belonging to the same priority class, or originating from the same source, or having the same source and destination addresses, etc.
In normal state when there is no congestion, packets will be sent as soon as they are delivered. In case of congestion, if QoS assurance methods are not applied, prolonged congestion can cause packet drops, affecting service quality. In some cases, congestion is prolonged and widespread in the network, which can easily lead to the network being "frozen", or many packets being dropped, seriously affecting service quality.
Therefore, in this chapter, in sections 3.2 and 3.3, we introduce some typical network traffic load monitoring techniques to predict and prevent congestion before it occurs through the measure of dropping (removing) packets early when there are signs of impending congestion.
3.1. DropTail method
DropTail is a simple, traditional queue management method based on FIFO mechanism. All incoming packets are placed in the queue, when the queue is full, the later packets are dropped.
Due to its simplicity and ease of implementation, DropTail has been used for many years on Internet router systems. However, this algorithm has the following disadvantages:
− Cannot avoid the phenomenon of “Lock out”: Occurs when 1 or several traffic streams monopolize the queue, making packets of other connections unable to pass through the router. This phenomenon greatly affects reliable transmission protocols such as TCP. According to the anti-congestion algorithm, when locked out, the TCP connection stream will reduce the window size and reduce the packet transmission speed exponentially.
− Can cause Global Synchronization: This is the result of a severe “Lock out” phenomenon. Some neighboring routers have their queues monopolized by a number of connections, causing a series of other TCP connections to be unable to pass through and simultaneously reducing the transmission speed. After those monopolized connections are temporarily suspended,
Once the queue is cleared, it takes a considerable amount of time for TCP connections to return to their original speed.
− Full Queue phenomenon: Data transmitted on the Internet often has an explosion, packets arriving at the router are often in clusters rather than in turn. Therefore, the operating mechanism of DropTail makes the queue easily full for a long period of time, leading to the average delay time of large packets. To avoid this phenomenon, with DropTail, the only way is to increase the router's buffer, this method is very expensive and ineffective.
− No QoS guarantee: With the DropTail mechanism, there is no way to prioritize important packets to be transmitted through the router earlier when all are in the queue. Meanwhile, with multimedia communication, ensuring connection and stable speed is extremely important and the DropTail algorithm cannot satisfy.
The problem of choosing the buffer size of the routers in the network is to “absorb” short bursts of traffic without causing too much queuing delay. This is necessary in bursty data transmission. The queue size determines the size of the packet bursts (traffic spikes) that we want to be able to transmit without being dropped at the routers.
In IP-based application networks, packet dropping is an important mechanism for indirectly reporting congestion to end stations. A solution that prevents router queues from filling up while reducing the packet drop rate is called dynamic queue management.
3.2. Random elimination method – RED
3.2.1 Overview
RED (Random Early Detection of congestion; Random Early Drop) is one of the first AQM algorithms proposed in 1993 by Sally Floyd and Van Jacobson, two scientists at the Lawrence Berkeley Laboratory of the University of California, USA. Due to its outstanding advantages compared to previous queue management algorithms, RED has been widely installed and deployed on the Internet.
The most fundamental point of their work is that the most effective place to detect congestion and react to it is at the gateway or router.
Source entities (senders) can also do this by estimating end-to-end delay, throughput variability, or the rate of packet retransmissions due to drop. However, the sender and receiver view of a particular connection cannot tell which gateways on the network are congested, and cannot distinguish between propagation delay and queuing delay. Only the gateway has a true view of the state of the queue, the link share of the connections passing through it at any given time, and the quality of service requirements of the
traffic flows. The RED gateway monitors the average queue length, which detects early signs of impending congestion (average queue length exceeding a predetermined threshold) and reacts appropriately in one of two ways:
− Drop incoming packets with a certain probability, to indirectly inform the source of congestion, the source needs to reduce the transmission rate to keep the queue from filling up, maintaining the ability to absorb incoming traffic spikes.
− Mark “congestion” with a certain probability in the ECN field in the header of TCP packets to notify the source (the receiving entity will copy this bit into the acknowledgement packet).
Figure 3. 1 RED algorithm
The main goal of RED is to avoid congestion by keeping the average queue size within a sufficiently small and stable region, which also means keeping the queuing delay sufficiently small and stable. Achieving this goal also helps: avoid global synchronization, not resist bursty traffic flows (i.e. flows with low average throughput but high volatility), and maintain an upper bound on the average queue size even in the absence of cooperation from transport layer protocols.
To achieve the above goals, RED gateways must do the following:
− The first is to detect congestion early and react appropriately to keep the average queue size small enough to keep the network operating in the low latency, high throughput region, while still allowing the queue size to fluctuate within a certain range to absorb short-term fluctuations. As discussed above, the gateway is the most appropriate place to detect congestion and is also the most appropriate place to decide which specific connection to report congestion to.
− The second thing is to notify the source of congestion. This is done by marking and notifying the source to reduce traffic. Normally the RED gateway will randomly drop packets. However, if congestion
If congestion is detected before the queue is full, it should be combined with packet marking to signal congestion. The RED gateway has two options: drop or mark; where marking is done by marking the ECN field of the packet with a certain probability, to signal the source to reduce the traffic entering the network.
− An important goal that RED gateways need to achieve is to avoid global synchronization and not to resist traffic flows that have a sudden characteristic. Global synchronization occurs when all connections simultaneously reduce their transmission window size, leading to a severe drop in throughput at the same time. On the other hand, Drop Tail or Random Drop strategies are very sensitive to sudden flows; that is, the gateway queue will often overflow when packets from these flows arrive. To avoid these two phenomena, gateways can use special algorithms to detect congestion and decide which connections will be notified of congestion at the gateway. The RED gateway randomly selects incoming packets to mark; with this method, the probability of marking a packet from a particular connection is proportional to the connection's shared bandwidth at the gateway.
− Another goal is to control the average queue size even without cooperation from the source entities. This can be done by dropping packets when the average size exceeds an upper threshold (instead of marking it). This approach is necessary in cases where most connections have transmission times that are less than the round-trip time, or where the source entities are not able to reduce traffic in response to marking or dropping packets (such as UDP flows).
3.2.2 Algorithm
This section describes the algorithm for RED gateways. RED gateways calculate the average queue size using a low-pass filter. This average queue size is compared with two thresholds: minth and maxth. When the average queue size is less than the lower threshold, no incoming packets are marked or dropped; when the average queue size is greater than the upper threshold, all incoming packets are dropped. When the average queue size is between minth and maxth, each incoming packet is marked or dropped with a probability pa, where pa is a function of the average queue size avg; the probability of marking or dropping a packet for a particular connection is proportional to the bandwidth share of that connection at the gateway. The general algorithm for a RED gateway is described as follows: [5]
For each packet arrival
Caculate the average queue size avg If minth ≤ avg < maxth
div.maincontent .s1 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 15pt; }
div.maincontent .s2 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 15pt; }
div.maincontent .p { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; }
div.maincontent p { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; }
div.maincontent .s3 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 14pt; }
div.maincontent .s4 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; }
div.maincontent .s5 { color: black; font-family:"Times New Roman", serif; font-style: italic; font-weight: normal; text-decoration: none; font-size: 14pt; }
div.maincontent .s6 { color: black; font-family:"Times New Roman", serif; font-style: italic; font-weight: bold; text-decoration: none; font-size: 14pt; }
div.maincontent .s7 { color: black; font-family:Wingdings; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; }
div.maincontent .s8 { color: black; font-family:Arial, sans-serif; font-style: italic; font-weight: bold; text-decoration: none; font-size: 15pt; }
div.maincontent .s9 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 14pt; }
div.maincontent .s10 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 9pt; vertical-align: 6pt; }
div.maincontent .s11 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 13pt; }
div.maincontent .s12 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 10pt; }
div.maincontent .s13 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-d -
Objective Test Questions Used in Teaching the Lesson "Equation of a Straight Line" -
Poverty Line Level According to Poverty Gap Index and Poverty Rate in Indonesia -
Tourism and Travel Services Business is a Conditional Business Line
5.2 Switchboard management operations
5.3 Switchboard maintenance

5.1 Robot Information
5.1.1 Overview of ManMachine information
In SPC switchboards that use processors to control the switchboard, peripheral devices for man-machine exchange are connected to the switchboard. Thanks to these devices, operators and maintenance staff can exchange information with the switchboard in Man Machine Language. Through this language, operators can manage information, process billing data, and perform system administration and operation requirements. System operation can be performed on-site or at the Operating Maintenance Center.
Robot language includes commands (Input), output messages (Output) and control messages.
Switchboard
control tasks, and how tasks such as testing and communicating with the system are performed. MML is the only tool for communication between people and the system. It needs to be designed for maximum efficiency and effectiveness.
OMC
Output (Screen, Printer, ...)
Input (Keyboard, mouse, communication commands...)
Figure 5.1 Structure of human-machine communication system
5.1.1.1 Structure of maintenance operation center
CC
OMC
OIC
MMI
VDU
PRT
DKU MTU STR
OAM
Figure 5.2 Structure of maintenance operations center
In there:
CC Center Control Central Control
OMC Operating Maintenance Center OMC Operating Maintenance Center
OIC Output / Input Controller Input / Output Controller
MMI Man Machine Interface
VDU Visual Display Unit
Chapter 5. Operation and maintenance
PRT Printer Printer
DKU Disk Unit Hard Disk Drive Unit
MTU Magnetic Tape Unit
STR Streamer Digital Data Tape Device Block
OAM Operating & Administrator Maintenance
* Functions of OMC: includes 3 main functions:
Management function: performs data storage of the system. To know the status of the object to be managed and the changes of the components in the system.
Monitoring function: Monitor all system activities to confirm whether the service to be provided is acceptable by testing.
Maintenance function: Includes tasks and functions to ensure the system works best under current conditions.
5.1.1.2 Characteristics of robot language
Based on a common language, usually English.
Easy to learn and easy to use to input commands and translate messages out
Contains full operational control commands to ensure system operation, maintenance, installation...
Open architecture to add new functionality without affecting existing
The command code will be function oriented (1 command per function).
Provides facilities for creating, deleting, and stopping active commands.
The word set used is the CCITT recommended Alphabetic character set.
5.1.2 Structure of Human-Machine Language
5.1.2.1 Command syntax
It is a set of rules for constructing commands in a grammatically correct language, it defines word sets, cipher keys, dividers and boundaries to make the written sentence clear.
* Basic components in syntax.
Identifier set: Is a set of letters starting from a group of letters, usually the initial information related to the command code and action of the job to be manipulated.
Example: DISSLNINFO:DN
Symbol name: Is a string of characters.
Counting numbers: Represented in different bases such as base 10, base 16.
Separator: Colon (:)
Indicator: the end of each command is a semicolon (;)
* Each command has a mandatory part and an optional parameter part.
Command code: To define the function to be performed, the actions to be performed on the system.
Parameters: After the command code is the parameter block.
Command code and parameter block are separated by a comma (:)
A command is terminated by a semicolon (;)
A parameter block consists of one or more parameters, the parameters are separated by the symbol (,)
Each parameter has a parameter name and parameter value separated by an equal sign (=).
* The format of a command and the structure of the command parameter block are described as follows.
Command code
,
:
=
;
Parameter block
Parameter name
Value
Some examples Example 1:
Figure 5.3 General command structure
Parameter Block Separator
REGSSVC:DN=850000,SSVC=ABS ;
Command end mark
Value of parameter Parameter
Example 2:
Command code
Parameter block
Cre Subd n=850075 el=000300317
2nd parameter Value of the parameter
First parameter Command code
* Types of newsletters
From SPC electronic switchboard systems, there are generally 4 types of messages output.
Command identification message (instruction): This message includes command number, time, date and communication device characteristics, this message is used to store the content of the
Chapter 5. Operation and maintenance
command has been issued.
Command response message (instruction): Includes information confirming the command initiation request and the command result.
System messages: These are system messages that automatically indicate events in system operations, or data and normal working status of important system function blocks. In addition, messages about warning status are also automatically issued.
Error message: The system will output an incorrect message when an incorrect command is entered into the system.
5.2 Switchboard management operations
5.2.1 Operation of switchboard equipment
Switchboard operation depends on the following factors:
Data stored in the switchboard
The program is stored in the processor.
Working status of hardware devices: such as distinguishing working and non-working status, status for testing.
Managing switchboard equipment means converting, setting up or deleting switchboard data.
For example, changing the outgoing trunk to a 2-way trunk, changing the service for the subscriber...
5.2.2 Subscriber line management
Including creating new subscriber numbers, converting subscriber lines, changing subscriber services, and setting up inactive subscribers.
Create new subscriber line.
Creating a new subscriber line requires entering an operation command into the switchboard system, which establishes a connection between the reserved directory number (DN) and the unallocated equipment address number (EN) with the appropriate attribute, distributing the billing set to the subscriber.
Move a subscription.
It involves changing the EN number assigned to the subscriber but leaving the DN, attributes and billing data unchanged, it is used for technical operations such as balancing voice traffic between circuits in different departments and interconnected parts of the switching network.
Change service for subscribers
Subscriber data can be changed by appropriate command according to DN and EN. Line service outage (suspension of subscriber operation)
When it is necessary to put the line out of service, it can be done by 2
way.
Service interruption (compression) includes: Opening the connection between EN and DN. Immediately
EN is available for other DNs. All calls to DN are transferred to the operator or the pre-recorded message of the subscriber's attributes is deleted from its file.
Out of service (delete): After deletion DN and EN become available for service again.
At the time of execution (compression) and (deletion) the content of the meter assigned to the line is output on the OMT.
5.2.3 Trunk line management
In the switchboard, the trunk data is stored in the switchboard memory as separate files. This file includes addresses obtained from local subscribers or incoming trunk lines. The trunk files define the trunk lines associated with the status of the trunks of the trunk group such as: Outgoing trunk, incoming trunk, 2-way depending on the type of signaling.
In the switchboard, the operator can redefine or change one or all of these functions by robot command.
5.2.4 System management
5.2.4.1 Fee data management
There are two sets of information stored in the fare file.
Data to calculate the cost of each call such as: Rate, area code... This data is provided to the call processing program in the form of a rate code, after analyzing the predetermined digits.
Billing content of each subscriber: Each subscriber has a separate billing set defined in the switchboard memory to record billing data for calls of this subscriber. Normally the operator cannot change the content in the billing set.
Normally, billing is done separately at the central computer used by the switchboards. To do this, the contents of the meter are periodically copied to a peripheral device suitable for the computer, such as a magnetic tape, or transmitted directly via the data line. The computer will bill each subscriber line based on the difference between the current and previous readings of the billing machine. In case of billing by item, the switchboard immediately records all the necessary information for each call, such as: Address of the called subscriber, call time... and then transfers this message to a suitable device when the call is terminated.
In addition, the content of the billing set is automatically printed out each time the operator creates a line, changes the DN, or temporarily suspends the operation of a number of subscribers.
5.2.4.2 Monitoring voice traffic and load
In SPC switching systems: Call monitoring and traffic measurement functions are fully integrated with the switching system in the switchboard, they are performed by the call processing program and more specialized voice test programs. They have the advantage of organizing frequent testing, monitoring the operation in a wider switchboard, and processing voice and updating results more reliably. On the other hand, the voice monitoring system outputs messages in a form that can be directly processed, enabling the operator to decide on timely and appropriate operational responses.
Chapter 5. Operation and maintenance
traffic balancing for subscriber switching blocks and trunk groups.
Monitoring modes: Depends on the object, and there are 2 types of monitoring
Regular monitoring: This monitoring method is to monitor the quality
Regular monitoring of services and traffic load in devices. Monitoring work is performed within the entire switchboard such as measuring the total number of outgoing and incoming calls, displaying basic parameters when the allowable values exceed the limit, an alert will be generated.
These monitoring tasks are performed automatically, and the operator can change how the results are displayed, such as defining which figures to display, requesting that the figures be transferred to tape, or setting alarm trigger thresholds for any parameter.
Real-time monitoring: Monitoring involves some hardware components of the PBX system such as subscriber lines, trunks, and switching elements. The data collected is often processed by a computer to optimize the PBX's resource usage, to locate problems in trunks, or to evaluate changes in the network.
These monitoring commands are initiated by the operator and define the parameters that need to be monitored, the list of parameters can be created, modified, looked up and canceled through the operation command, the operator can perform automatic test measurements.
At specific intervals, the data is processed in the switchboard and the processing results are displayed for use by the manager or transferred to the appropriate storage device for sending to the computing center for processing.
When the switchboard is under high load, the instant monitoring work is stopped but does not affect the regular monitoring work.
5.3 Switchboard maintenance
Maintenance aims to maintain the stable operation of the switchboard to ensure continuous service provision to customers. Maintenance work is classified as follows:
* Regular maintenance (repair):
The task of the SPC switchboard security program is to detect errors in the switchboard hardware and software. When an error occurs, the central controller will trigger warning messages.
Thus regular maintenance is performed after a fault is detected in the system. The purpose of this method is to restore the normal state to perform the required function.
Maintenance does not require frequent system checks (less maintenance activities are required) but results in unstable service quality.
* Periodic maintenance:
Routine maintenance involves a series of routine tasks to check any parts that are likely to be sources of failure and repair them before they fail. This method requires a large amount of work to be done.
* Control maintenance:
The development of today's equipment provides new methods of maintenance, the system can immediately report information related to the existence of abnormal and irregular controls.
Periodic test measurements can be replaced by methods of continuous monitoring of system functions and measures to check the continuity of operation of equipment and provide warning signals to the operator when the service quality falls below a pre-set limit.
5.3.1 Maintenance of subscriber lines and trunk lines
5.3.1.1 Subscriber line maintenance
Includes testing of a subscriber line or group of subscriber lines and related equipment using human-machine commands. Testing of subscriber lines and telephones is divided into four parts:
* Subscriber line monitoring.
When a subscriber line is in an abnormal state, it is detected by the call processing software and the subscriber line is isolated from the switchboard (Lockout) the subscriber line.
The system periodically checks the status of all lines. An alert is generated from the periodic line check system when the line is locked out beyond the threshold for the entire switchboard or a certain line connection.
The alarm threshold and time between checks can be changed by command from the operator, which provides indication to the cause and location of the fault.
* Periodic testing to detect and identify faulty lines.
Periodic testing is initiated by the operator's command, testing can be initiated immediately after a period of storage of information about the faulty line and the line that has not been tested because it is busy is printed out on request from the operator's command. The operator can enter a test order for all lines during the night and have the results the next morning.
* The operator is assisted in testing the subscriber line to determine the source and cause of the line failure. The operator uses the system control command to perform the test as follows:
Measure open circuit on the line.
+ Measure AC voltage between T and ground
+ Measure AC voltage between R and ground
+ Measure DC voltage between T and ground
+ Measure DC voltage between R and ground
+ Measure the insulation impedance Z between T and ground
+ Measure the insulation impedance Z between R and ground
+ Measure the insulation impedance Z between T and R
Measure loop resistance on the line.
+ Loop Current
Chapter 5. Operation and maintenance
+ Loop Resistor
Dial-up telephone measurement
+ On/off time for each dial pulse.
+ Number of pulses received for a digit to be dialed.
Measure the phone press key
+ Frequency and level for digits.
+ Test subscriber phone
By performing simple tests at the subscriber's machine independently of the workload in the switchboard, or after repairing the line or telephone, it is possible to check:
+ Signal on the line.
+ Line insulation resistance.
+ Loop current.
+ Transmit bell current, adjust bell.
5.3.1.2 Trunk line maintenance
In SPC switchboards trunk data is stored in switchboard memory as separate files in the form of trunk profiles, which define the type, and group of trunk lines (Outgoing trunk, Incoming trunk, 2-way trunk) corresponding to the associated signaling type.
When a problem occurs or after a certain period of time, maintenance is necessary. When defects occur with the modules, the system will output warning messages. If the system cannot fix it itself, the operator must
proceed
through human-machine interface commands. Thanks to
communication commands
The robot can change the trunk structure.
Trunk testing can also be performed automatically and the results are output in the form of messages. However, automatic testing does not provide enough information for diagnosis, to restore normal operation of the faulty trunk lines. Therefore, manual testing equipment is required, which is often used for space SPC switchboards.
5.3.2 Maintenance of switching network, control system
5.3.2.1 Switching network maintenance
Work includes: Performing call testing, call monitoring, testing switches, locating faults in the switching network.
5.3.2.2 Control system maintenance
In switchboards, the automatic diagnostic program is responsible for detecting errors in modules and units. Execute this program to identify the functional unit or printed circuit board that has a problem.
The control system determines all operations of the switchboard, so the processors are equipped with a pair of hot standby (ACT/SBY) operating units. When a hardware failure occurs, the system will trigger an alarm. The operator uses commands to locate the failed module and replace it with the same type.


![Qos Assurance Methods for Multimedia Communications
zt2i3t4l5ee
zt2a3gs
zt2a3ge
zc2o3n4t5e6n7ts
low. The EF PHB requires a sufficiently large number of output ports to provide low delay, low loss, and low jitter.
EF PHBs can be implemented if the output ports bandwidth is sufficiently large, combined with small buffer sizes and other network resources dedicated to EF packets, to allow the routers service rate for EF packets on an output port to exceed the arrival rate λ of packets at that port.
This means that packets with PHB EF are considered with a pre-allocated amount of output bandwidth and a priority that ensures minimum loss, minimum delay and minimum jitter before being put into operation.
PHB EF is suitable for channel simulation, leased line simulation, and real-time services such as voice, video without compromising on high loss, delay and jitter values.
Figure 2.10 Example of EF installation
Figure 2.10 shows an example of an EF PHB implementation. This is a simple priority queue scheduling technique. At the edges of the DS domain, EF packet traffic is prioritized according to the values agreed upon by the SLA. The EF queue in the figure needs to output packets at a rate higher than the packet arrival rate λ. To provide an EF PHB over an end-to-end DS domain, bandwidth at the output ports of the core routers needs to be allocated in advance to ensure the requirement μ > λ. This can be done by a pre-configured provisioning process. In the figure, EF packets are placed in the priority queue (the upper queue). With such a length, the queue can operate with μ > λ.
Since EF was primarily used for real-time services such as voice and video, and since real-time services use UDP instead of TCP, RED is generally
not suitable for EF queues because applications using UDP will not respond to random packet drop and RED will strip unnecessary packets.
2.2.4.2 Assured Forwarding (AF) PHB
PHB AF is defined by RFC 2597. The purpose of PHB AF is to deliver packets reliably and therefore delay and jitter are considered less important than packet loss. PHB AF is suitable for non-real-time services such as applications using TCP. PHB AF first defines four classes: AF1, AF2, AF3, AF4. For each of these AF classes, packets are then classified into three subclasses with three distinct priority levels.
Table 2.8 shows the four AF classes and 12 AF subclasses and the DSCP values for the 12 AF subclasses defined by RFC 2597. RFC 2597 also allows for more than three separate priority levels to be added for internal use. However, these separate priority levels will only have internal significance.
PHB Class
PHB Subclass
Package type
DSCP
AF4
AF41
Short
100010
AF42
Medium
100100
AF43
High
100110
AF3
AF31
Short
011010
AF32
Medium
011100
AF33
High
011110
AF2
AF21
Short
010010
AF22
Medium
010100
AF23
High
010110
AF1
AF11
Short
001010
AF12
Medium
001100
AF13
High
001110
Table 2.8 AF DSCPs
The AF PHB ensures that packets are forwarded with a high probability of delivery to the destination within the bounds of the rate agreed upon in an SLA. If AF traffic at an ingress port exceeds the pre-priority rate, which is considered non-compliant or “out of profile”, the excess packets will not be delivered to the destination with the same probability as the packets belonging to the defined traffic or “in profile” packets. When there is network congestion, the out of profile packets are dropped before the in profile packets are dropped.
When service levels are defined using AF classes, different quantity and quality between AF classes can be realized by allocating different amounts of bandwidth and buffer space to the four AF classes. Unlike
EF, most AF traffic is non-real-time traffic using TCP, and the RED queue management strategy is an AQM (Adaptive Queue Management) strategy suitable for use in AF PHBs. The four AF PHB layers can be implemented as four separate queues. The output port bandwidth is divided into four AF queues. For each AF queue, packets are marked with three “colors” corresponding to three separate priority levels.
In addition to the 32 DSCP 1 groups defined in Table 2.8, 21 DSCPs have been standardized as follows: one for PHB EF, 12 for PHB AF, and 8 for CSCP. There are 11 DSCP 1 groups still available for other standards.
2.2.5.Example of Differentiated Services
We will look at an example of the Differentiated Service model and mechanism of operation. The architecture of Differentiated Service consists of two basic sets of functions:
Edge functions: include packet classification and traffic conditioning. At the inbound edge of the network, incoming packets are marked. In particular, the DS field in the packet header is set to a certain value. For example, in Figure 2.12, packets sent from H1 to H3 are marked at R1, while packets from H2 to H4 are marked at R2. The labels on the received packets identify the service class to which they belong. Different traffic classes receive different services in the core network. The RFC definition uses the term behavior aggregate rather than the term traffic class. After being marked, a packet can be forwarded immediately into the network, delayed for a period of time before being forwarded, or dropped. We will see that there are many factors that affect how a packet is marked, and whether it is forwarded immediately, delayed, or dropped.
Figure 2.12 DiffServ Example
Core functionality: When a DS-marked packet arrives at a Diffservcapable router, the packet is forwarded to the next router based on
Per-hop behavior is associated with packet classes. Per-hop behavior affects router buffers and the bandwidth shared between competing classes. An important principle of the Differentiated Service architecture is that a routers per-hop behavior is based only on the packets marking or the class to which it belongs. Therefore, if packets sent from H1 to H3 as shown in the figure receive the same marking as packets from H2 to H4, then the network routers treat the packets exactly the same, regardless of whether the packet originated from H1 or H2. For example, R3 does not distinguish between packets from h1 and H2 when forwarding packets to R4. Therefore, the Differentiated Service architecture avoids the need to maintain router state about separate source-destination pairs, which is important for network scalability.
Chapter Conclusion
Chapter 2 has presented and clarified two main models of deploying and installing quality of service in IP networks. While the traditional best-effort model has many disadvantages, later models such as IntServ and DiffServ have partly solved the problems that best-effort could not solve. IntServ follows the direction of ensuring quality of service for each separate flow, it is built similar to the circuit switching model with the use of the RSVP resource reservation protocol. IntSer is suitable for services that require fixed bandwidth that is not shared such as VoIP services, multicast TV services. However, IntSer has disadvantages such as using a lot of network resources, low scalability and lack of flexibility. DiffServ was born with the idea of solving the disadvantages of the IntServ model.
DiffServ follows the direction of ensuring quality based on the principle of hop-by-hop behavior based on the priority of marked packets. The policy for different types of traffic is decided by the administrator and can be changed according to reality, so it is very flexible. DiffServ makes better use of network resources, avoiding idle bandwidth and processing capacity on routers. In addition, the DifServ model can be deployed on many independent domains, so the ability to expand the network becomes easy.
Chapter 3: METHODS TO ENSURE QoS FOR MULTIMEDIA COMMUNICATIONS
In packet-switched networks, different packet flows often have to share the transmission medium all the way to the destination station. To ensure the fair and efficient allocation of bandwidth to flows, appropriate serving mechanisms are required at network nodes, especially at gateways or routers, where many different data flows often pass through. The scheduler is responsible for serving packets of the selected flow and deciding which packet will be served next. Here, a flow is understood as a set of packets belonging to the same priority class, or originating from the same source, or having the same source and destination addresses, etc.
In normal state when there is no congestion, packets will be sent as soon as they are delivered. In case of congestion, if QoS assurance methods are not applied, prolonged congestion can cause packet drops, affecting service quality. In some cases, congestion is prolonged and widespread in the network, which can easily lead to the network being frozen, or many packets being dropped, seriously affecting service quality.
Therefore, in this chapter, in sections 3.2 and 3.3, we introduce some typical network traffic load monitoring techniques to predict and prevent congestion before it occurs through the measure of dropping (removing) packets early when there are signs of impending congestion.
3.1. DropTail method
DropTail is a simple, traditional queue management method based on FIFO mechanism. All incoming packets are placed in the queue, when the queue is full, the later packets are dropped.
Due to its simplicity and ease of implementation, DropTail has been used for many years on Internet router systems. However, this algorithm has the following disadvantages:
− Cannot avoid the phenomenon of “Lock out”: Occurs when 1 or several traffic streams monopolize the queue, making packets of other connections unable to pass through the router. This phenomenon greatly affects reliable transmission protocols such as TCP. According to the anti-congestion algorithm, when locked out, the TCP connection stream will reduce the window size and reduce the packet transmission speed exponentially.
− Can cause Global Synchronization: This is the result of a severe “Lock out” phenomenon. Some neighboring routers have their queues monopolized by a number of connections, causing a series of other TCP connections to be unable to pass through and simultaneously reducing the transmission speed. After those monopolized connections are temporarily suspended,
Once the queue is cleared, it takes a considerable amount of time for TCP connections to return to their original speed.
− Full Queue phenomenon: Data transmitted on the Internet often has an explosion, packets arriving at the router are often in clusters rather than in turn. Therefore, the operating mechanism of DropTail makes the queue easily full for a long period of time, leading to the average delay time of large packets. To avoid this phenomenon, with DropTail, the only way is to increase the routers buffer, this method is very expensive and ineffective.
− No QoS guarantee: With the DropTail mechanism, there is no way to prioritize important packets to be transmitted through the router earlier when all are in the queue. Meanwhile, with multimedia communication, ensuring connection and stable speed is extremely important and the DropTail algorithm cannot satisfy.
The problem of choosing the buffer size of the routers in the network is to “absorb” short bursts of traffic without causing too much queuing delay. This is necessary in bursty data transmission. The queue size determines the size of the packet bursts (traffic spikes) that we want to be able to transmit without being dropped at the routers.
In IP-based application networks, packet dropping is an important mechanism for indirectly reporting congestion to end stations. A solution that prevents router queues from filling up while reducing the packet drop rate is called dynamic queue management.
3.2. Random elimination method – RED
3.2.1 Overview
RED (Random Early Detection of congestion; Random Early Drop) is one of the first AQM algorithms proposed in 1993 by Sally Floyd and Van Jacobson, two scientists at the Lawrence Berkeley Laboratory of the University of California, USA. Due to its outstanding advantages compared to previous queue management algorithms, RED has been widely installed and deployed on the Internet.
The most fundamental point of their work is that the most effective place to detect congestion and react to it is at the gateway or router.
Source entities (senders) can also do this by estimating end-to-end delay, throughput variability, or the rate of packet retransmissions due to drop. However, the sender and receiver view of a particular connection cannot tell which gateways on the network are congested, and cannot distinguish between propagation delay and queuing delay. Only the gateway has a true view of the state of the queue, the link share of the connections passing through it at any given time, and the quality of service requirements of the
traffic flows. The RED gateway monitors the average queue length, which detects early signs of impending congestion (average queue length exceeding a predetermined threshold) and reacts appropriately in one of two ways:
− Drop incoming packets with a certain probability, to indirectly inform the source of congestion, the source needs to reduce the transmission rate to keep the queue from filling up, maintaining the ability to absorb incoming traffic spikes.
− Mark “congestion” with a certain probability in the ECN field in the header of TCP packets to notify the source (the receiving entity will copy this bit into the acknowledgement packet).
Figure 3. 1 RED algorithm
The main goal of RED is to avoid congestion by keeping the average queue size within a sufficiently small and stable region, which also means keeping the queuing delay sufficiently small and stable. Achieving this goal also helps: avoid global synchronization, not resist bursty traffic flows (i.e. flows with low average throughput but high volatility), and maintain an upper bound on the average queue size even in the absence of cooperation from transport layer protocols.
To achieve the above goals, RED gateways must do the following:
− The first is to detect congestion early and react appropriately to keep the average queue size small enough to keep the network operating in the low latency, high throughput region, while still allowing the queue size to fluctuate within a certain range to absorb short-term fluctuations. As discussed above, the gateway is the most appropriate place to detect congestion and is also the most appropriate place to decide which specific connection to report congestion to.
− The second thing is to notify the source of congestion. This is done by marking and notifying the source to reduce traffic. Normally the RED gateway will randomly drop packets. However, if congestion
If congestion is detected before the queue is full, it should be combined with packet marking to signal congestion. The RED gateway has two options: drop or mark; where marking is done by marking the ECN field of the packet with a certain probability, to signal the source to reduce the traffic entering the network.
− An important goal that RED gateways need to achieve is to avoid global synchronization and not to resist traffic flows that have a sudden characteristic. Global synchronization occurs when all connections simultaneously reduce their transmission window size, leading to a severe drop in throughput at the same time. On the other hand, Drop Tail or Random Drop strategies are very sensitive to sudden flows; that is, the gateway queue will often overflow when packets from these flows arrive. To avoid these two phenomena, gateways can use special algorithms to detect congestion and decide which connections will be notified of congestion at the gateway. The RED gateway randomly selects incoming packets to mark; with this method, the probability of marking a packet from a particular connection is proportional to the connections shared bandwidth at the gateway.
− Another goal is to control the average queue size even without cooperation from the source entities. This can be done by dropping packets when the average size exceeds an upper threshold (instead of marking it). This approach is necessary in cases where most connections have transmission times that are less than the round-trip time, or where the source entities are not able to reduce traffic in response to marking or dropping packets (such as UDP flows).
3.2.2 Algorithm
This section describes the algorithm for RED gateways. RED gateways calculate the average queue size using a low-pass filter. This average queue size is compared with two thresholds: minth and maxth. When the average queue size is less than the lower threshold, no incoming packets are marked or dropped; when the average queue size is greater than the upper threshold, all incoming packets are dropped. When the average queue size is between minth and maxth, each incoming packet is marked or dropped with a probability pa, where pa is a function of the average queue size avg; the probability of marking or dropping a packet for a particular connection is proportional to the bandwidth share of that connection at the gateway. The general algorithm for a RED gateway is described as follows: [5]
For each packet arrival
Caculate the average queue size avg If minth ≤ avg < maxth
div.maincontent .s1 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 15pt; }
div.maincontent .s2 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 15pt; }
div.maincontent .p { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; }
div.maincontent p { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; }
div.maincontent .s3 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 14pt; }
div.maincontent .s4 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; }
div.maincontent .s5 { color: black; font-family:Times New Roman, serif; font-style: italic; font-weight: normal; text-decoration: none; font-size: 14pt; }
div.maincontent .s6 { color: black; font-family:Times New Roman, serif; font-style: italic; font-weight: bold; text-decoration: none; font-size: 14pt; }
div.maincontent .s7 { color: black; font-family:Wingdings; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; }
div.maincontent .s8 { color: black; font-family:Arial, sans-serif; font-style: italic; font-weight: bold; text-decoration: none; font-size: 15pt; }
div.maincontent .s9 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 14pt; }
div.maincontent .s10 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 9pt; vertical-align: 6pt; }
div.maincontent .s11 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 13pt; }
div.maincontent .s12 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 10pt; }
div.maincontent .s13 { color: black; font-family:Times New Roman, serif; font-style: normal; font-weight: normal; text-d](https://tailieuthamkhao.com/uploads/2022/05/15/danh-gia-hieu-qua-dam-bao-qos-cho-truyen-thong-da-phuong-tien-cua-chien-6-1-120x90.jpg)


