ND 56906 307e 04

ND-56906-307 (E)
Issue 4, September 2001

NEAX61S
DIGITAL
SWITCHING SYSTEM
TRAFFIC CONTROL
MANUAL
PRACTICE
NEC Corporation
Copyright
1998, 1999, 2001 by NEC Corporation

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or
transmitted, in any form or by any means, including electronic, mechanical, photographic, or magnetic,
without prior written permission of the publisher.
Printed in Japan
NEC PRACTICE
ND-56906-307 (E) Precautions
PL 1 of 10
Precautions
To prevent you from facing death or suffering injury, this manual and alert labels, attached to the
system, give you various safety instructions. You must read the safety instructions in this manual and
take notice of alert labels on the system before performing operation and maintenance work.
This manual is intended for the operation and maintenance personnel of the NEAX61S system.
Safety Instructions
The Safety Instructions gives you safety instructions for the NEAX61S system and its maintenance
terminals. For other equipment, refer to the relevant manual of the equipment.
DEFINITIONS OF ALERT CATEGORIES
The safety instructions are divided into three categories.
DANGER
This symbol is given to an item that is explicitly dangerous to your life.
Disobedience to this instruction can put you in imminent danger of death
or serious injury.
WARNING
This symbol is given to an item that is potentially dangerous to your life.
Disobedience to this instruction can lead to death or serious injury.
CAUTION
This symbol is given to an item that is potentially dangerous to your body
and property. Disobedience to this instruction can cause injury to you, or
damage to the property such as equipment and components, and the
communication network.
NEC PRACTICE
Precautions ND-56906-307 (E)
PL 2 of 10
LIST OF ALERT LABELS
The following lists alert labels attached to the system. When you see the label, be sure to
follow the instruction on the label.
(Location)
Frame (LTF, RBF, ELF, etc.)
(Explanation)
While working with a drawer-type module pulled out of a frame,
take care not to hit your head or back against the module. Such
an accident can cause injury to you.
(Location)
Frame (BF, CPF, LTF, etc.)
(Explanation)
When you replace a fan, do not touch the fan before the fan
completely stopped. If you touch a rotating fun, you can be
injured.
(Location)
Frame (BF, CPF, etc.)
(Explanation)
The Class 1 laser product (harmless to human body) is used.
(Location)
All types of frames
(Explanation)
Wear a rubber or vinyl gloves to touch a metal-shielded tube.
Touching a metal-shielded tube can cause dermatitis.
NEC PRACTICE
PL 3 of 10
LIST OF SAFETY INSTRUCTIONS
When you find a safety instruction in this manual, be sure to read the instruction before
performing work.
The safety instructions, especially regarding death or injury, contained in this manual are
listed below, being categorized with alert categories.
Alert category: Caution
CAUTION
Safety instructions on whole work:
Before starting operation and maintenance work, ensure that the
working environment is safe.
Before starting operation and maintenance work, secure a refuge in
case of an accident or emergency situation.
Never wear slippers during work. You can fall down and get injured.
Take care not to trip over the cables, components, or tools during the
work. Such an accident can cause injury to you.
Take care so that the sleeves and trouser leg hems of your working
uniform are not caught in equipment and machines during work. A
caught sleeve or hem can lead to an injury or accident.
Do not put liquid like water in the system components or touch the
system with wet hands. Moisture in the system can cause an
electrical shock or a trouble. Should liquid enter the system,
immediately turn off the power of the affected components, and ask
for repairs.
Do not rework or disassemble the system components. An electrical
shock, a fire or trouble can result.
NEC PRACTICE
PL 4 of 10
Alert category: Caution (continued)
Precautions for Normal System Operation
The Precautions for Normal System Operation provides precautions against possible troubles that can
occur on the system. In order to maintain the normal operation of the system, you have to pay
particular attention to each item of the precautions when performing operation and maintenance work
SITE CONSIDERATION
To maintain normal system operation, your site must always meet the requirements listed
below.
(1) Temperature and humidity
CAUTION
Safety instructions on handling cards:
Wear thin cotton gloves when handling cards. Working with bare
hands can lead to an injury or accident.
While working with a drawer-type module pulled out form a frame,
take care not to hit your head or back against the module. Such an
accident can cause injury to you and/or damage to the system.
Handle the card being tested, the test instrument, cables, and all
other components properly in accordance with the instructions given
in the relevant manuals.
Safety instructions on high voltage and high current:
Persons other than the maintenance personnel must not touch the
direct current power distribution board (DC-PDB). The DC-PDB
involves a high voltage and high current. Touching it can lead to an
electrical shock or accident.
Make sure that the switching system contains components with high
voltage or current. An inadvertent contact with any of these
components can cause injury, death, and/or damage to the system.
Be sure to provide grounding where required. A failure to do so can
lead to a system failure or electrical shock at the time of lightening.
When measuring voltage or current, take adequate insulating
measures, such as covering or winding the superfluous parts of the
measuring terminal and tools with insulating tape. Allowing the
measuring terminal to touch another terminal or a short-circuit caused
by a tool can lead to an electrical shock or accident.
Operate the test equipment and the call simulation equipment (CSE)
on the specified voltage (100 or 200 V system). Operating them on an
inadequate voltage can cause a fire.
NEC PRACTICE
PL 5 of 10
(2) Dust
To prevent a short circuit due to dust buildup, make sure that the site is not a dusty place.
(3) Vibration
Since the system components are precision-engineered equipment and devices, make
sure that the site is not subject to vibration.
(4) Heat dissipation
Proper air circulation is necessary to prevent temperature rise inside the system. Make
sure that the vents of the system components are not blocked.
(5) Static electricity
Be sure to connect a wrist strap to ground such as ESD terminal, etc.
Make sure that the temperature and humidity levels are within the acceptable
range: the temperature is 5 to 40C and the humidity 20 to 80% (no condensation).
Make sure that the site is not exposed to liquid such as water and oil.
Make sure that the site is not exposed to direct sunlight or near a fire or heating
appliance like a stove.
NEC PRACTICE
PL 6 of 10
LIST OF PRECAUTIONS
The items of precautions are listed by the following working situations:
When Operating the System
When Handling Cards
When Handling the Power Supply
When Handling Parts and Components
When Operating the System
Keep the doors of the machine room closed during the work. In humid air, vapor can
condense on cards and modules in the switching system, which can lead to a short-
circuit or fire. Dust can cause a short-circuit or fire, too.
While using air-conditioning, take care to prevent water from dropping on cards and
modules in the switching system from the ceiling or refrigerant pipe. If any component
in the system becomes wet, a short-circuit or fire can result.
Keep the humidity in the machine room within the range of 20 to 80%.
Do not leave foreign objects such as screws, wires, or pieces of metal, inside the frames,
modules, main distribution frame (MDF) or terminal devices of the switching system.
Such foreign object can damage the equipment or cause a short-circuit, subsequently
resulting in a malfunction of the switching system.
Wear antistatic shoes during operation and maintenance work.
NEC PRACTICE
PL 7 of 10
When Handling Cards
When you mount or dismount a card of the system components, always wear thin cotton
gloves and a wrist strap to prevent static electricity. Electrostatic charge can damage the
internal parts.
Make sure that the switches and short plugs on the spare card are in the same condition
as those on the card to be replaced.
Wear a pair of gloves.
Wear a wrist strap.
GND
wrist strap
0 1 2 3
ON
OFF
DIP switches
Rotary switch
Short plugs
NEC PRACTICE
PL 8 of 10
Make sure the top and bottom sides of the spare card are correct. Do not force the card
into the slot. Forcibly inserting a card in a wrong direction can damage it.
Do not bend or twist the card. Bending or twisting the card can damage it and lead to a
malfunction.
Be sure to turn the power switch of a card off before removing a card with ! label.
Right Wrong
NEC PRACTICE
PL 9 of 10
When Handling the Power Supply
The system components are kept in operation with the power supply turned on at all
times. Make sure that no personnel except the system administrator is allowed to
operate the power switch. If the power supply is interrupted, communications will be
disrupted, and the unsaved data will be lost.
Never turn the power switch of a card on and off, or insert or remove a fuse except when
necessary. Be careful not to abruptly turn the power supply on and off.
When Handling Parts and Components
Never swing a cable. Never wind a cable forcibly. Swinging a cable or winding a cable
forcibly can break the cable or damage its connector.
Never remove the cap from an optical connector, except when attaching the connector.
If an optical connector is damaged or contaminated with dust, a communication error
can occur.
Never step on a battery. Stepping on a battery can cause a leakage.
Use tools and components such as batteries and cables correctly in accordance with the
instructions given in the relevant manuals.
NEC PRACTICE
PL 10 of 10
(This page is intentionally left blank.)
NEC PRACTICE
ND-56906-307 (E) Preface
PR 1 of 4
Preface
PURPOSE OF THE MANUAL
To keep the system in a satisfactory condition and to maintain the normal call traffic, it is necessary to
prevent or eliminate traffic congestion by traffic control. This manual provides an outline and procedure
for traffic control to help maintenance personnel to carry out traffic control.
MANUAL ORGANIZATION
A. Section
This manual comprises the following sections:
SECTION 1 : OVERVIEW
Provides background knowledge that maintenance personnel need to know before carrying out
traffic control.
SECTION 2 : TRAFFIC CONTROL METHODS
Describes functions and methods of traffic control.
SECTION 3 : TRAFFIC CONTROL PROCEDURES
Describes procedures of setting route or restriction for traffic control.
B. Module
Each section comprises independent information units called modules. For easy identification, a
module number preceded by a module identifier identifies each module. Module identifiers include INT
(introduction) and PRC (procedure) which are defined as follows:
INT: Describes general information on the features mentioned in this manual.
In this manual, Sections 1 and 2 contain INT modules.
PRC: Describes a series of operating procedures.
In this manual, Section 3 contains PRC modules.
Fig. 1 shows module title, module identifier, and module number in each module, and how they
correspond to the Table of Contents.
NEC PRACTICE
Preface ND-56906-307 (E)
PR 2 of 4
Fig. 1 Module Reference
Section 3
Section 2
Section 1
Table of Contents
Preface
Copyright
Cover Sheet
Module title
Title
SECTION 1. OVERVIEW
Index Number Issue Date
INT-023-0100 Brief Description of Traffic 1 12/96
SECTION 3. TRAFFIC CONTROL PROCEDURES
PRC-023-1100 Alternate Route Setting Procedure 1
12/96
Module title
Brief Description of Traffic
INT-023-0100 1/2
PRC
INT
Module title
Alternate Route Setting Procedure
PRC-023-1100 1/4
Module number
Module identifier
NEC PRACTICE
ND-56906-307 (E) Preface
PR 3 of 4
RELATED MANUALS
This manual is positioned as shown in Fig. 2. The related manuals should be referenced as required for
smooth maintenance and operation of the system.
Fig. 2 Relationships Among Manuals
Traffic Data Measurement Manual
IMAT Operation Manual
Input Manual
Office Data Modification Manual
Traffic Control Manual
Charge Data Recording Manual*
Service Order Processing Manual*
GUIDE
Introduction of
documents
Document Guide
GUIDE
Introduction of the
system
System Description
Maintenance (preventive
and fault recovery)
information
MNT HARD
Equipment
Description
OPER
Hardware
Information
System and maintenance
operation information
Card Replacement
Procedures
System Recovery Manual
Routine Maintenance Manual
Output Manual
On-line manual (built in the system)
Output Manual
Input Manual
Other manuals
(Option)
NEC PRACTICE
Preface ND-56906-307 (E)
PR 4 of 4
NOTICE
The screen images shown in this manual might differ from the actual screen images in your system. In
that case, please proceed according to the actual screen images.
NEC PRACTICE
ND-56906-307 (E) Contents
CL 1 of 2
Contents
(*:REVISION)
TITLE INDEX NUMBER ISSUE DATE
SECTION 1
OVERVIEW
Brief Description of Traffic................................................ INT-023-0100-11(E) 1 6/1998
Necessity of Traffic Control .............................................. INT-023-0200-12(E) 1 6/1998
Brief Description of Traffic Control ................................... INT-023-0300-13(E) 5* 9/1999
SECTION 2
TRAFFIC CONTROL METHODS
Traffic Control by Routing Control.................................... INT-023-1100-12(E) 1 6/1998
Traffic Control by Automatic Traffic Control Function....... INT-023-2100-11(E) 1 6/1998
Traffic Control by Traffic Restriction................................. INT-023-3110-13(E) 3* 7/2000
Icons Used for Traffic Control .......................................... INT-023-9100-14(E) 4* 5/2000
SECTION 3
TRAFFIC CONTROL PROCEDURES
Route Sharing Setting Procedure.................................... PRC-023-1150-11(E) 4* 7/2000
Routing Setting Procedure............................................... PRC-023-1250-11(E) 4* 11/1999
TOD Routing Setting Procedure ...................................... PRC-023-1300-16(E) 5* 7/2000
Outgoing Connection Restriction Setting Procedure ....... PRC-023-3100-17(E) 2 11/1998
Originating Restriction Setting Procedure........................ PRC-023-3200-14(E) 5* 7/2000
Route Restriction Setting Procedure ............................... PRC-023-3300-12(E) 5* 7/2000
Restriction Class Setting Procedure................................ PRC-023-3400-16(E) 2 11/1999
NEC PRACTICE
Contents ND-56906-307 (E)
CL 2 of 2
NEC PRACTICE
SECTION 1
OVERVIEW
NEC PRACTICE
NEC PRACTICE
INT-023-0100-11 (E) Brief Description of Traffic
Issue 1, June 1998
INT-023-0100 1 of 2
Brief Description of Traffic
1. SUMMARY
A basic understanding of traffic is required for effective traffic control. This section briefly describes
the concepts of traffic, traffic data, and traffic control in the telecommunications field.
2. TRAFFIC
The term traffic usually refers to the movement of people, cars, or trains along streets, roads, or on
railroads. In telecommunications fields such as switching systems and telecommunication networks,
this term has a similar meaning. It is used to represent the flow of communication by regarding calls
and transmission data as trains or cars, and telecommunication networks as railroads or roads.
3. TRAFFIC AND TRAFFIC DATA
Traffic theory represents the concept of traffic in switching systems in terms of the number of calls and
traffic density. The number of calls is defined as the number of calls that occur within a given period of
time, while traffic density is defined as the average number of simultaneous calls over a given period of
time. Traffic information is vital for the maintenance and administration of switching systems and
telecommunications networks. Unlike the traffic of people or vehicles, the traffic of telecommunication
is invisible. To overcome this difficulty, telecommunication traffic is handled using quantitative
representations, namely, traffic data.
Traffic data shows numerically how much communication data or how many calls arrive at the
switching systems or telecommunications networks, how much communication data or how many calls
are conveyed over the telecommunications networks, and how long these calls have occupied the
telecommunications networks. This traffic data can be used to check the state of traffic flow through
switching systems or over telecommunications networks. Traffic information is automatically collected
on specified measurement items and stored on a hard disk in a switching system. The stored traffic
information can be sorted out as necessary and displayed as traffic data on terminal equipment.
The traffic data obtained this way can be used to understand the operating state of speech path
equipment, the Control Processor (CP) occupancy, and the utilization of subscriber services. Traffic
data forms the basis of traffic management activities such as planning facilities and controlling
telecommunications traffic, and customer and business management activities.
4. TRAFFIC AND TRAFFIC CONTROL
Telecommunications traffic is not uniform. It can be regarded as similar to the traffic of people or
vehicles. As the number of vehicles on a road increases, traffic congestion is inevitable. Similarly, as the
number of calls in a telecommunications system increases, communication traffic becomes congested.
If the number of calls per unit time continues to increase, the traffic flow deteriorates, possibly resulting
in communication being temporarily impossible. This is like a road traffic jam. The operations and
functions used to ease such traffic jams, or traffic congestion, and to keep communication in a normal
state are called traffic control.
Telecommunications networks are designed to avoid traffic congestion. Switching systems are provided
with capacity to process traffic density within an anticipated range. Design is based on analysis of
traffic data collected in the past. Ideally the telecommunications networks and switching systems do not
NEC PRACTICE
Brief Description of Traffic INT-023-0100-11 (E)
Issue 1, June 1998
INT-023-0100 2 of 2
need traffic control. However, congestion may occur because of an unexpected increase in traffic,
insufficient equipment, or load sharing imbalance. Switching systems are provided with traffic control
functions to minimize the impact and to speed recovery from traffic congestion.
NEC PRACTICE
INT-023-0200-12 (E) Necessity of Traffic Control
Issue 1, June 1998
INT-023-0200 1 of 2
Necessity of Traffic Control
1. SUMMARY
To provide stable communication services for subscribers, it is necessary to keep the switching systems
in a satisfactory condition and to maintain the normal call traffic. Traffic control is one of the tasks
needed to attain this goal. This section briefly describes in what situation traffic control is needed.
2. MAINTAINING TELECOMMUNICATIONS SERVICE QUALITY
If traffic is congested, it becomes difficult to connect calls, and this condition may persist for a long
period. If a call is not connected, the subscriber cannot be served with the telecommunications network
which he or she has subscribed to. This condition is unfavorable to both the subscriber requesting
telecommunication services and the service provider earning money by providing these services. To
avoid this condition, it is necessary for the service provider to maintain telecommunication service
quality. To attain this goal, the service provider should consider the following:
Transmission line quality
Routing
High-quality transmission lines are essential to ensure satisfactory service and minimize repeated call
attempts. Routing must be set up and controlled based on the state of links between other switching
systems and on the number of accommodated subscribers, so that traffic is stable and uniformly
distributed.
Transmission line quality and routing are determined based on the result of analyzing the traffic data
collected in the past. These switching system parameters are not frequently changed during normal
operation. Transmission line quality especially depends on the hardware, and a stable traffic flow
depends on the transmission lines having the good quality that suits a specific telecommunications
network. Even if these parameters are set up properly, however, traffic can not always be maintained in
a stable state. To keep traffic in a stable state, it is necessary to monitor the state of traffic constantly and
perform rerouting as required.
3. TAKING ACTION FOR TRAFFIC CONGESTION
The number of calls may temporarily or suddenly increase for some reason, or a physical factor may
cause the number of calls in a switching system to increase. These conditions can rapidly reduce
switching capability, resulting in a degraded communication flow. An overloaded call processing
system in a switching system may become unable to perform normal call processing. These conditions
are called traffic congestion. If traffic congestion occurs, the service provider must take appropriate
action to keep the traffic congestion from spreading over the telecommunications networks, otherwise it
may paralyze communication. The major causes of traffic congestion are:
Traffic congestion due to a system failure
Traffic congestion due to a temporary service or a disaster
Traffic congestion due to a system fault can occur if subscriber cables, transmission lines, or switching
systems are damaged by earthquake, fire, or accident. It takes a long time to clear this type of system
NEC PRACTICE
Necessity of Traffic Control INT-023-0200-12 (E)
Issue 1, June 1998
INT-023-0200 2 of 2
fault. When a system fault is cleared, subscribers will try to place more calls than usual, thus the traffic
congestion may possibly spread over the telecommunications network to other switching offices. On
the other hand, traffic congestion due to a temporary service or a disaster can occur if terminating calls
requesting a specific service concentrate on a specific subscriber who has opened that service, or if
terminating calls for inquiries concentrate in a specific area where a natural disaster has occurred. After
a natural disaster, subscribers also tend to try to place calls all at once. In these cases, it is possible to
anticipate that the traffic density increases to certain degree. For traffic congestion especially due to a
temporary service, the service provider can be provided with telephone numbers and lines that can be
used to distribute the control processor load, so that the occupancy of the Control Processor (CP) in the
signalling destination point can be improved. In this case, however, it is impossible to eliminate traffic
congestion due to terminating calls.
In either case, it is necessary to eliminate traffic congestion as early as possible. To attain this goal,
traffic control is carried out with priority placed on maintaining services for subscribers and on
preventing disorder in the telecommunication networks.
NEC PRACTICE
INT-023-0300-13 (E) Brief Description of Traffic Control
INT-023-0300 1 of 6
Brief Description of Traffic Control
1. SUMMARY
Traffic control is one of the tasks of operating or maintaining a switching system. The purpose of traffic
control is to maintain stable traffic. This section briefly describes when, for what purpose, and how
traffic control is carried out.
2. WHEN TRAFFIC CONTROL IS CARRIED OUT
Traffic congestion is attributable to the increase of calls. Traffic control is intended to prevent or
eliminate traffic congestion. Probable causes of an increase of calls include a system fault, temporary
service, and a disaster. In these cases, the switching system outputs the following information to request
the maintenance personnel to carry out traffic control.
Traffic data signifying a traffic abnormality
Traffic congestion is reflected in a change in the collected traffic data. This change will be an
increase or decrease in the following data items.
Decreasing values
Successful calls, trunk holding time, etc.
Increasing values
Outgoing calls, call volumes on alternate routes, incomplete calls, etc.
If these changes are detected in the traffic data, chances are that traffic congestion will occur.
In this case, traffic control is carried out to prevent possible traffic congestion.
If traffic data indicates that traffic load concentrates on a specific route or network, it would
be necessary to start traffic control. Specifically, if there are more calls or traffic density for a
certain destination or in a certain switching system, or between certain subscribers than for or
between others, traffic control will be carried out to maintain averaged, stable traffic.
Autonomous message indicating traffic congestion
The switching system outputs an autonomous message to indicate the occurrence of traffic
congestion. The types of autonomous messages output in this case are:
Message indicating traffic congestion on a route
*.. 1041012 route_congestion rn=cccccccc
The switching system outputs the above autonomous message when the trunk hunt failure
ratio of the indicated route exceeds the route overflow detection threshold. (The threshold is
predetermined as system data.) If this message is output, carry out traffic control on the route.
Message indicating the CP is expected to be overloaded
#.. 1158002 system_overload_released cpDD
The switching system outputs the above autonomous message when the occupancy ratio of
the indicated Control Processor (CP) exceeds the CP overload detection threshold
NEC PRACTICE
Brief Description of Traffic Control INT-023-0300-13 (E)
INT-023-0300 2 of 6
continuously for 30 seconds. (The threshold is predetermined as system data.) If this message
is output, traffic control should be carry out to prevent possible traffic congestion in future.
Message indicating the CP is overloaded
*** 1158001 system_overload cpDD
The switching system outputs the above autonomous message when the occupancy ratio of
the indicated CP exceeds the CP overload detection threshold continuously for one minute.
(The threshold is predetermined as system data.) And when the occupancy ratio of the
indicated CP exceeds the CP overload detection threshold continuously for five minutes, the
switching system outputs the following autonomous message.
*** 1158003 system_overload_remains_unchanged cpDD
If these messages are output, traffic control must be carried out to eliminate traffic
congestion.
Autonomous message indicating Hard-to-Reach (HTR) destination
A system fault, a temporary increase in services, or a disaster may cause an increase of calls
to a particular destination. The switching system outputs the following autonomous message:
*.. 1158006 hard_to_reach_code trid=cccccc ac=c1-c8 n=d1-d9
ratio=ddd
The switching system outputs the above autonomous message when a call completion ratio
for a particular destination falls below a threshold. For outputting this message, the
destination and threshold must be registered using [Hard to Reach] icon. The switching
system calculates a call completion ratio for the registered destinations and compares it with
the registered thresholds. If the actual call completion ratio for a particular destination falls
below the registered threshold, the system regards the destination as a HTR destination and
outputs the above message. If this message is output, carry out traffic control to the
destination.
Request for traffic control from another switching office
A switching office may be requested by another switching office to carry out traffic control,
when the latter anticipates traffic congestion because of a system fault, temporary service, or
disaster or has actually encountered traffic congestion. The former should carry out necessary
traffic control according to the conditions of the other office and the connection state of the
communication network.
Information used for traffic control is collected traffic data including autonomous messages
indicating traffic congestion. From this point of view, it is important to monitor and analyze
traffic data. To perform suitable traffic control, it is necessary not only to consider the
situation mentioned above but also to analyze collected traffic data accurately.
3. TRAFFIC CONTROL FUNCTIONS
The switching system has traffic control functions and related support functions to cope with conditions
that may cause traffic congestion and to take measures for traffic congestion that actually occurs. These
functions are divided into two as follows:
NEC PRACTICE
INT-023-0300 3 of 6
The functions to prevent traffic congestion are effective mainly for conditions that may lead to traffic
congestion. These functions are intended to maintain a normal traffic state. If a change in traffic data
that signifies an abnormality in traffic is detected, these functions should be used to perform traffic
control to cope with the abnormality. On the other hand, the functions to eliminate traffic congestion are
effective in the early stage of traffic congestion. These functions are intended to eliminate traffic
congestion quickly. If an autonomous message indicating the occurrence of traffic congestion is output,
these functions should be used to perform traffic control. Each function and the traffic control
performed using it are briefly described below.
Routing control
Traffic congestion can be prevented with the routing control function by averaging traffic
volume over the whole communication network and keeping it stable. This type of traffic
control includes the following:
Changing or setting up alternate routes
Setting up route sharing
Setting up Time of Day (TOD) routing
Traffic congestion can be eliminated by changing or setting up alternate routes for diverting
calls concentrating on specific routes or areas. This type of traffic control has the function for
keeping the normal processing work by the switching system. The traffic control by this
function is:
Setting up emergency alternate routes.
Traffic control by an automatic traffic control function
Outgoing and incoming calls are automatically restricted according to the traffic restriction
information previously specified as system data. This type of traffic control is:
Dynamic Processor Overload Control (DPOC) restriction.
Traffic control by a traffic restriction icon
If calls concentrate on a specific route or area, or many subscribers originate calls at the same
time, a traffic restriction icon can be used to restrict traffic, phasing out the traffic congestion.
This type of traffic control includes the following:
Outgoing connection restriction
Originating restriction
Functions to prevent traffic congestion Routing control
Traffic control by an automatic traffic control function
Functions to eliminate traffic congestion Routing control
Traffic control by a traffic restriction icon
NEC PRACTICE
INT-023-0300 4 of 6
Route restriction
Incoming and outgoing combined restriction
Notes:
1 Traffic restriction suspends services for the subscribers. Be very careful when employing
traffic restriction.
2 Incoming and outgoing combined restriction is applied to tandem office only.
Before carrying out traffic control, it is necessary to understand each traffic control function and handle
any situation in need of traffic control properly. Each traffic control function is detailed in Section 2.
4. FUNCTIONS TO SUPPORT TRAFFIC CONTROL
The switching system has functions to support traffic control as follows:
Presetting the data for detecting Hard-to-Reach destination
Early detection of HTR destination is helpful to carry out traffic control. The switching
system can output an autonomous message indicating HTR destination when a call
completion ratio for a particular destination falls below a threshold. To output this message,
the destination and threshold must be registered using [Hard to Reach] icon.
Reserving trunks for priority subscribers
If traffic congestion occurs on a particular route and all trunks in the route become busy, calls
to the route cannot be connected. Calls which form priority subscribers also cannot be
connected under this situation. For preventing this, some trunks can be reserved for priority
subscribers beforehand using [Trunk Reservation] icon. When the number of idle trunks in
the route falls below the registered threshold (i.e., the number of trunks reserved for a smooth
traffic), outgoing ordinary calls to the route are restricted. The restricted calls are connected
to an announcement trunk or rerouted to the next priority route.
Presetting an Out-of-Chain route for route restriction
The route restriction has various restriction patterns. Some restriction patterns need an Out-
of-Chain route. When an Out-of-Chain route is registered to a particular route using
[Routing] icon, overflow calls from the route can be rerouted to the registered Out-of-Chain
route.
Note: For detailed explanation of icons mentioned above, refer to I ntelligent Maintenance
and Administration Terminal (I MAT) Operation Manual
NEC PRACTICE
INT-023-0300 5 of 6
5. FLOW OF TRAFFIC CONTROL
The following diagram shows each traffic state and associated actions.
Fig. 1 Traffic State Transition
Normal state
When the switching systems and communication network are running normally, traffic stays
normal. In this case, no traffic control is needed. It is only necessary to perform periodic
maintenance (diagnosis and testing) for maintaining normal traffic and to monitor and
analyze traffic data.
Increasing calls
If the number of calls and traffic density increase to an abnormal level, the possible cause is a
switching system fault, temporary service start, or disaster. In this case, traffic control to
prevent traffic congestion is carried out according to the results of analyzing the situation in
which the calls were increased and the traffic data.
If the traffic data (the number of calls and traffic density) returns to a normal level as a result
of traffic control, maintenance activities and traffic data monitoring and analysis are resumed.
If the traffic data keeps increasing rather than returning to a normal level, automatic traffic
restriction is started and carried out according to the prescribed parameters.
Traffic congestion
If automatic traffic restriction cannot resume normal traffic, and the calls keep increasing,
traffic control to eliminate congestion is carried out. In this case, an emergency alternate
route is set up for the waiting calls. If the emergency alternate route cannot eliminate traffic
congestion, or there is no time to set up an alternate route, manual traffic restriction is carried
Normal state
Increasing calls
Traffic congestion
Periodic maintenance
Monitoring and analyzing traffic data
Changing or setting up alternate routes
Setting up route sharing
Setting up TOD routing
Emergency alternate route set-up
Outgoing connection restriction
Originating restriction
Automatic traffic restriction
Route restriction
Incoming and outgoing combined restriction
NEC PRACTICE
INT-023-0300 6 of 6
out. If the traffic data (the number of calls and traffic density) returns to a normal level as a
result of traffic control, maintenance activities and traffic data monitoring and analysis are
resumed.
Note: Not only traffic control but also reviewing the capacity of required equipment (for
example, whether more trunks are needed) may be necessary depending on the level
of congestion.
NEC PRACTICE
SECTION 2
TRAFFIC CONTROL METHODS
NEC PRACTICE
NEC PRACTICE
INT-023-1100-12 (E) Traffic Control by Routing Control
Issue 1, June 1998
INT-023-1100 1 of 6
Traffic Control by Routing Control
1. SUMMARY
Traffic control by routing control sets up alternate routes, bundles routes (Route sharing), and selects
routes suited for a particular day of the week and time of the day (Time of Day (TOD) routing). This
section briefly describes each function, its process, and the situation in which it is employed.
2. SETTING UP ALTERNATE ROUTE
2.1 DESCRIPTION OF FUNCTION
Information related to alternate routes has been set up as office data, using icons. This function makes it
easy to set up or change routing control information, including that on alternate routes.
After office data has been set up, [Routing] icon can be employed to change or newly set up alternate
routes or to set up emergency alternate routes.
2.2 OVERVIEW OF PROCESSING
A concept of traffic control based on alternative routing can be explained in terms of routing as shown
below:
Fig. 1 Example of Traffic Control by Alternative Routing
Assume that in the network shown above, traffic on the route between switching offices A and B has
increased. If there is no alternate route between switching offices A and B, traffic congestion will occur
because of the increased traffic on the route between switching offices A and B and of the Control
Processor (CP) being overloaded. To prevent this situation or eliminate congestion on that route (if it
occurs), an alternate route to switching office C is set up to detour the waiting calls to switching office
B via switching office C. If traffic between switching offices C and B also increases and is likely to
result in an overflow, switching office C sets up an alternate route via switching office D to switching
office B. In this way, normal communication between switching offices A and B can be maintained.
This is the basic concept of traffic control based on alternative routing.
C
D
A
B
Alternative routing
Alternative routing
: Traffic congestion point
A, B, C and D: Switching offices
NEC PRACTICE
Traffic Control by Routing Control INT-023-1100-12 (E)
Issue 1, June 1998
INT-023-1100 2 of 6
2.3 APPLICATION
This function can be employed for the following traffic control types:
Setting up new alternate routes to relieve a heavily loaded route
Changing alternate routes to average the route usage rate
Setting up alternate routes to eliminate route congestion.
3. SETTING UP ROUTE SHARING
The route sharing function groups, or bundles, several routes, and hunts trunks in the bundle of routes
according to the number of lines installed on each route so that the line usage rate can be averaged
among the bundled routes. The bundle of routes is assigned a route sharing number that has the same
meaning as a route index. With a route sharing number assigned, the bundle of routes is treated in
routing in the same manner as routes having an ordinary route index.
[Route Sharing] icon is employed for bundling. Each bundled route must have the same ultimate
destination.
A concept of traffic control based on route sharing can be explained in terms of routing as shown below:
Fig. 2 Example of Traffic Control by Route Sharing
In the network shown above, the route between switching offices A and B has fewer lines than other
routes. If traffic from switching office A to switching office B increases, the line occupancy ratio
becomes high, making it more likely for congestion to occur on this route. On the other hand, both of
the alternate routes from switching office A to those B or C have relatively more room for traffic than
that from A to B judging from the number of lines. This situation could be prevented by installing more
lines between switching offices A and B. This method would not be economical if the traffic increases
temporarily on the route between switching offices A and B. This problem is solved by bundling the
three routes to maintain efficient communication with switching office B. Bundling carries out routing
C
B
A
D
Bundling
Alternate route 2
(Number of lines=30)
Alternate route 1
NEC PRACTICE
Issue 1, June 1998
INT-023-1100 3 of 6
from switching offices A to B according to the ratio of the number of lines on one route to the number
of lines on another route, enabling even usage of the lines on each route. Normal communication
between switching offices A and B can be maintained this way. This is the basic concept of traffic
control based on route sharing.
The line usage ratio of each bundled route is determined using the following formula (with the
remainder rounded down):
If the sum of the obtained seizure ratios throughout the bundle is not greater than 16, a correction is
made using the following formula (with the remainder rounded down):
The line usage ratio of each route mentioned above obtained using these formulas are as follows (on the
assumption that there is no line under installation for any route).
Route between switching offices A and B: 1
Route between switching offices A and D: 2
Route between switching offices A and C: 3
3.3 APPLICATION
This function can be employed for the following traffic control type:
Maintaining an appropriate line usage ratio on a route
4. SETTING UP TOD ROUTING
TOD routing function selects an outgoing route according to a predetermined combination of a day of
the week and time. TOD routing needs a schedule index to set up a combination of a day of the week
and time. If TOD routing has been specified, a route is selected according to the routing information
consisting of an ordinary route index and this schedule index.
[Routing Schedule] and [Holiday] icons are employed for TOD routing. They generate a schedule
index, and [Routing] icon specifies this schedule index in routing.
Line usage ratio of each route=
(minimum number of lines in the bundle -number of lines under installation)
(total number of lines on the other routes -total number of lines under installation)
(Number of lines on each route - number of lines under installation)x
(minimum number of lines in the bundle -number of lines under installation)
(sum of the line usage ratios obtained using the above formula)
16
(rounded up)
NEC PRACTICE
Issue 1, June 1998
INT-023-1100 4 of 6
A concept of traffic control based on TOD routing can be explained in terms of routing as shown below:
Fig. 3 Example of Traffic Control by TOD Routing
If in the network shown above, traffic from switching office A to switching office B increases at the
specific time or on a specific day of the week, the routes between switching offices A and B including
the route via switching office C become heavily loaded temporarily. If the increased traffic remains
within the allowable range of each route, no problem occurs on communication. If the traffic goes out
of the allowable range of a route, however, congestion may arise on that route. To prevent this situation,
a new alternate route to switching office B is set up only for the specific time or on a specific day of the
week during which a traffic increase is expected, so that normal communication with switching office B
can be maintained. This method is useful if a day of the week or time during which a traffic increase is
expected is foreseeable. A temporary traffic increase can be handled this way to maintain normal
communication between switching offices A and B. This is the basic concept of traffic based on TOD
routing.
To carry out TOD routing, it is necessary to set up a schedule index table previously, so that a route to
switching office D can be used as an alternate route for the specific period of time or a specific day of
the week. The schedule index table is set up with the following information, using [Routing Schedule]
and [Holiday] icons:
Day of the week ([Routing Schedule] icon)
Eight day types including Monday through Sunday, and national holidays
Time ([Routing Schedule] icon)
48 time zones around the clock, each consisting of 30 minutes
National holiday ([Holiday] icon)
Date (month and day) of a national holiday to be specified in setting a day of the week by
[Routing Schedule] icon
4.3 APPLICATION
C
B
A
D
Alternate route
Alternative routing
NEC PRACTICE
Issue 1, June 1998
INT-023-1100 5 of 6
Preventing congestion in busy hours
Preventing congestion on a specific day.
NEC PRACTICE
Issue 1, June 1998
INT-023-1100 6 of 6
NEC PRACTICE
INT-023-2100-11 (E) Traffic Control by Automatic Traffic Control Function
Issue 1, June 1998
INT-023-2100 1 of 2
Traffic Control by Automatic Traffic Control Function
1. SUMMARY
The automatic traffic control function supports Dynamic Processor Overload Control (DPOC) control.
This section briefly describes this function, its process, and the situation in which it is employed.
2. DPOC CONTROL
DPOC control automatically restricts the number of outgoing calls and incoming calls acceptable per
unit time according to a Control Processor (CP) occupancy. To carry out DPOC control, it is necessary
to specify the CP occupancy as traffic restriction information beforehand.
First, DPOC control judges the current control processor capacity according to the CP occupancy, and
determines the maximum number of calls that can be processed with the current control processor
capacity. The calculated maximum number of persuasible calls is set as a threshold. Automatic
restriction is carried out over outgoing calls or incoming calls that exceed this threshold. This restriction
applies only to ordinary subscribers. It does not apply to previously registered priority subscribers.
The following diagram shows how DPOC control is carried out.
Fig. 1 Process of DPOC Control
(1) The traffic monitor measures the CP occupancy periodically, and reports it to the traffic
controller. The CP occupancy is measured 12 times at 5-second intervals (for one minute),
and the average of the CP occupancy for this one minute is reported.
(2) The traffic controller determines the maximum number of calls that can be accepted,
according to the CP occupancy reported from the traffic monitor and the CP occupancy set
up as system data, then reports the calculated maximum number of calls to the protocol
controller.
(3) The protocol controller connects or restricts calls according to the report from the traffic
controller.
Traffic controller
Traffic monitor
System data
Protocol controller
(1)
(2)
(3)
NEC PRACTICE
Traffic Control by Automatic Traffic Control Function INT-023-2100-11 (E)
Issue 1, June 1998
INT-023-2100 2 of 2
2.3 APPLICATION
This function can be employed for the following traffic control type:
CP overload control
The system carries out DPOC control automatically according to the predetermined data. Therefore, the
system does not require setting out the function or making changes to the function during operation.
NEC PRACTICE
INT-023-3110-13 (E) Traffic Control by Traffic Restriction
Issue 3, July 2000
INT-023-3110 1 of 16
Traffic Control by Traffic Restriction
1. SUMMARY
Traffic control by the traffic restriction includes outgoing connection restriction, originating restriction,
route restriction, and incoming and outgoing combined restriction. This section briefly describes each
function, its process, and the situation in which it is employed.
2. OUTGOING CONNECTION RESTRICTION
The outgoing connection restriction function restricts connections of calls outgoing to a specified
destination according to the time specified as a restriction level. To prevent re-dialing for the specified
destination, a recorded-announcement trunk is connected to the calling subscriber. Destinations are
specified for restriction using terminating numbers, and up to 16 restriction levels can be used, so
appropriate restriction can be done according to the situation.
[Restriction Level] icon is employed for outgoing connection restriction.
Outgoing connection restriction can be summarized as shown below:
Fig. 1 Example of Outgoing Connection Restriction
If outgoing connection to switching office A is restricted, the state of call connection becomes as shown
above. Switching office A is specified for restriction using a terminating number (n = 45) that can be
recognized by originating offices. So, outgoing calls routed through switching office C to switching
office A are also restricted. Both subscribers a and b are prohibited from originating calls to switching
office A for the time specified as a restriction level and connected to a recorded-announcement trunk.
A
C
B
A, B, and C: Switching offices
Local switching office
Destination to restrict
45-XXXX
44-XXXX
46-XXXX
a
b
ANM
ANM
(N=44)
(N=45)
(N=46)
44-XXXX
44-XXXX
45-XXXX
45-XXXX
46-XXXX
46-XXXX
NEC PRACTICE
Traffic Control by Traffic Restriction INT-023-3110-13 (E)
Issue 3, July 2000
INT-023-3110 2 of 16
The subscribers are not prohibited from originating calls to other destinations; they are prohibited from
originating calls to the specified destination only. Therefore, when subscriber a or b tries to call a
subscriber accommodated in switching office B or C, the attempted outgoing call is connected
normally. This is traffic control based on outgoing connection restriction.
Outgoing connection restriction is carried out by specifying the restricted destination and restriction
level as stated above. These specifications can be detailed to take appropriate measures according to the
actual congestion. A destination specified for outgoing connection restriction and restriction level are
explained below.
Specifying a destination for restriction
A destination is specified for restriction using a terminating number recognized by
originating offices. The terminating number comprises up to 13 digits including a prefix. If a
terminating number is specified with 12 or less digits, the omitted part functions like wild
card characters. Up to 64 destinations can be registered as objects of restriction.
Restriction level
Up to 16 restriction levels can be assigned to each destination according to the restriction
time (Call Gap Interval). More than one restriction level can be assigned to one destination.
When a restriction level from 9 to 13 is specified, the call gap interval for each call changes in
the predetermined regular rotation.
The following paragraphs describe the correspondence between the restriction level and call
gap interval, rotation of the restriction time, and multiple specification of restriction levels to
the same destination.
Correspondence between the restriction level and call gap interval
Table 1 shows the correspondence between the restriction level and call gap interval
(restriction time).
Table 1 Correspondence between The Restriction Level and Call Gap Interval (1/2)
Restriction level Call gap interval
0 0
1 0.1
2 0.25
3 0.5
4 1.0
5 2.0
6 5.0
7 10.0
8 15.0
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 3 of 16
Notes:
1 Restriction levels 1 to 14 apply to ordinary subscribers. Restriction level 15 applies
also to priority subscribers.
2 The measurement unit of a call gap interval is a second.
Restriction time rotation
When restriction levels 9 to 13 are specified, the restriction time is periodically changed
as shown in the following example:
Example: (Restriction level 9 (restriction time of 30 seconds) is specified)
Specifying more than one restriction level for some destinations
When more than one restriction level is specified for some destinations, restriction is
carried out as follows:
Example:
If destinations identified with terminating numbers 2xx, 23x, and 234 are specified with
restriction levels 4, 5, and 6, respectively
9 30.0
10 60.0
11 120.0
12 300.0
13 600.0
14 Infinity()
15 Infinity()
First interval 100% of 30 seconds, or 30 seconds
Second interval 150% of 30 seconds, or 45 seconds
Third interval 50% of 30 seconds, or 15 seconds
Table 1 Correspondence between The Restriction Level and Call Gap Interval (2/2)
Restriction level Call gap interval
100%
150% 50%
30 seconds
45 seconds 15 seconds
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 4 of 16
Announcement
A restricted call is provided with any of the following announcements.
2.3 APPLICATION
Eliminating traffic congestion directed to a specific destination
Eliminating traffic congestion on a route to the distant Local Switching (LS) office
Eliminating traffic congestion in the other office (as requested by that office)
3. ORIGINATING RESTRICTION
Originating restriction prohibits ordinary subscribers from originating calls according to the specified
rotation timing and restriction class. Restriction is carried out for individual CP, Local Controller
(LOC), Remote Local Controller (RLOC), Digital Line Transmission Controller (DLTC), and 61E-
LOC Subhighway Converter (SCONVL) numbers. To be specific, ordinary subscribers accommodated
at these numbers are subjected to restriction. This is done using [Restriction Level] icon.
Scope of restriction objectives
When an LOC, RLOC, or CP number is specified, the restricted subscribers are selected as
described below.
Restriction level 4 applies to destinations identified with n = 2xx
(where xx is other than 34).
Restriction level 5 applies to destinations identified with n = 23x
(where x is other than 4).
Restriction level 6 applies to destinations identified with n = 234.
ec1 (Emergency Announcement Class 1)
nca (No-circuit-available announcement)
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 5 of 16
Fig. 2 Scope of Restriction Objectives
When an LOC or RLOC number is specified
When LOC0000 is specified as objectives of restriction, the subscribers indicated in box
A are prohibited from originating calls. The subscribers accommodated at LOC0001 are
not objectives of restriction.
When a CP number is specified
When CP00 is specified as objectives of restriction, the subscribers (indicated in box B)
accommodated at the LOCs (LOC0000 and LOC0001) under control of CP00 are
prohibited from originating calls.
Specifying restriction class and rotation
The subscribers accommodated in the CP, LOC, or RLOC identified with a number specified
as objectives of restriction are divided into four groups according to the line numbers as
shown in Table 2. When restriction class 25, 50, or 75 is specified, subscribers subjected to
restriction are periodically rotated among these four groups according to the specified
rotation timing as shown in Fig. 3. The specified rotation timing value can range from 2
minutes to 10 minutes in 1-minute steps.
For example, with Restriction class=25 and Rotation=2, subscribers located in line numbers
0 to 7 are restricted for the first 30 seconds, and subscribers in line numbers 32 to 39 are
LC
PHW
LOC
LC
PHW
LOC
KHW0
SSW* TSW
A
LOC0001
CP00
HUB
KHW1
CP01
LOC0000
CP00: Controls LOC0000 and LOC0001.
B
* : Installation of space switch (SSW) varies depending on the office conditions.
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 6 of 16
restricted for the next 30 seconds, and so on.
Restriction class = 25: 25% of the subscribers accommodated in specified equipment
are prohibited from originating calls.
Fig. 3 Restriction Class and Rotation
3.3 APPLICATION
This function can be used for the following traffic control types:
Controlling when the CP is overloaded
Prohibiting all subscribers in the local switching office from simultaneous originating calls.
Table 2 Restriction Class and Line Number for Rotation
Restriction Class
Line No.
of Group
A
Line No.
of Group
B
Line No.
of Group
C
Line No.
of Group
D
cls=25 (25% restriction) 0- 7 32-39 64-71 96-103
cls=50 (50% restriction) 0-15 32-47 64-79 96-111
cls=75 (75% restriction) 0-23 32-55 64-87 96-119
cls=100 (100% restriction) 0-31 32-63 64-95 96-127
A
C
D
B
A
C
D
B
A
C
D
B
A
C
D
B
If 2-minute rotation timing is specified, rotation occurs at 30-second intervals.
If 10-minute rotation timing is specified, rotation occurs at 150-second intervals.
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 7 of 16
4. ROUTE RESTRICTION
The route restriction function controls outgoing calls on a specific route. Restriction is carried out with
specifying control pattern, call category and restriction level. Outgoing calls are accepted or restricted
according to a combination of specified items. The route restriction has four control patterns for each of
which a call category and a restriction level are specified. The restricted calls are connected to an
announcement trunk or rerouted to another route.
The route restriction function has the following control patterns:
(1) Restrict calls to the specified route
This function is used to restrict the outgoing calls which accesses the specified route.
(2) Restrict calls from the specified route
This function is used to restrict the outgoing calls which overflow the specified route.
(3) Skip the specified route
This function is used to forcibly reroute the outgoing calls which accesses the specified next
alternate route.
(4) Reroute calls which overflow the specified route
This function is used to forcibly reroute the outgoing calls which overflow the specified
route to an out-of-chain route.
Note: Data used for out-of-chain routing must be predetermined by [Routing] icon.
[Restriction Level] icon is employed for route restriction.
(1) Restrict calls to the specified route
Restrict direct-routed calls to the specified route
Fig. 4 Restrict Calls to Direct Route
If the route to switching office A is specified for restriction, the state of call connection
A
B
A and B: Switching offices Local switching office
Route to restrict
ANM
Alternate route
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 8 of 16
becomes as shown above. The outgoing calls which accesses the route to switching
office A are accepted/restricted according to the specified restriction level. The
restricted calls are connected to a recorded-announcement trunk.
Restrict alternate-routed calls
Fig. 5 Restrict Calls to An Alternate Route
If the route to switching office B is specified for restriction, the state of call connection
becomes as shown above. The overflow calls from the route to switching office A are
accepted/restricted according to the specified restriction level. The restricted calls are
connected to a recorded-announcement trunk.
(2) Restrict calls from the specified route
Restrict direct-routed calls
Fig. 6 Restrict Calls from A Direct Route
accepted/restricted according to the specified restriction level. The restricted calls are
connected to a recorded-announcement trunk.
A
B
A and B: Switching offices
Route to restrict (Alternate route)
ANM
Overflow calls
A
B
Route to restrict
ANM
Overflow calls
Alternate route
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 9 of 16
Fig. 7 Restrict Calls from An Alternate Route
becomes as shown above. The overflow calls from the specified route are accepted/
restricted according to the specified restriction level. The restricted calls are connected
to a recorded-announcement trunk.
(3) Skip the specified route
Fig. 8 Skip A Direct Route
becomes as shown above. The outgoing calls which accesses the specified route are
accepted/restricted according to the specified restriction level. The restricted calls skip
the specified route and are rerouted to the alternate route.
A
C
B
Route to restrict
ANM
Overflow calls
Overflow calls
(Alternate route 1)
Alternate route 2
A
B
Route to restrict
Skip the route
Alternate route
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 10 of 16
Fig. 9 Skip An Alternate Route
becomes as shown above. The overflow calls which accesses the specified route are
accepted/restricted according to the specified restriction level. The restricted calls skip
the specified route and are rerouted to the next alternate route.
(4) Reroute calls which overflow the specified route
Fig. 10 Reroute Calls which Overflow A Direct Route
A
C
B
Route to restrict
Overflow calls
Skip the route
(Alternate route 1)
Alternate route 2
A
B
Overflow calls
Route to restrict
Alternate route
Out-of-chain Route
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 11 of 16
rerouted to the next alternate route or an out-of-chain route according to the specified
restriction level.
Fig. 11 Reroute Calls which Overflow An Alternate Route
rerouted to the next alternate route or an out-of-chain route according to the specified
restriction level.
The route restriction includes various restriction patterns as stated above. These patterns are specified
according to a combination of control pattern, call category and restriction level. Call category and
restriction level for route restriction are explained below.
Call category
Call category specifies routing and destination information of outgoing calls for the route
restriction. Specifying call category on the control pattern determines basic restriction
pattern. The following four call categories can be specified as objects of restriction.
Direct-routed calls
Restrict calls which accesses the specified route as the direct route to a destination.
Direct-routed calls to a Hard-to-Reach (HTR) destination
Restrict calls which accesses the specified route as the direct route to a HTR destination.
A
C
B
Route to restrict
Overflow calls
Overflow calls
Out-of-chain Route
Alternate route 2
(Alternate route 1)
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 12 of 16
Alternate-routed calls
Restrict calls which accesses the specified route as an alternate route to a destination.
Alternate-routed calls to a Hard-to-Reach (HTR) destination
Restrict calls which accesses the specified route as an alternate route to a HTR
destination.
Restriction level
Restriction level specifies the proportion of restricted calls to attempted calls. Up to 9
restriction levels can be assigned to each control pattern according to the actual congestion.
The following restriction levels are prepared for the route restriction.
Announcement type
The restricted calls are provided with any one of the following announcements:
Note: If the specified announcement is not registered, the restricted calls are
connected to the Reorder Tone (ROT).
4.3 APPLICATION
Eliminating traffic congestion directed to a specific destination
Eliminating traffic congestion on a specific route
Level 1 (restrict 12.5% of calls)
Level 2 (restrict 25% of calls)
Level 8 (restrict 100% of calls from ordinary subscribers)
Level 9 (restrict 100% of calls from ordinary and priority subscribers)
ec1 (Emergency announcement class 1)
nca (No-circuit-available announcement)
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 13 of 16
5. INCOMING AND OUTGOING COMBINED RESTRICTION
The incoming and outgoing combined restriction function restricts specific tandem calls in a tandem
office. Restriction is carried out according to the following combinations:
(1) Combination of an incoming route and outgoing route(s)
Restrict calls which come via a specific incoming route and go via a specific outgoing
route(s).
(2) Combination of an incoming route, destination number(s), and access code
Restrict calls which come via a specific incoming route and go to specific destination
number(s) and access code.
Incoming and outgoing combined restriction is carried out by specifying the combination as stated
above. These specifications can be detailed to take appropriate measures according to the actual
congestion.
[Restriction Class] icon is employed for incoming and outgoing combined restriction.
(1) Restrict with combination of an incoming route and outgoing route(s)
Fig. 12 Example of Incoming and Outgoing Combined Restriction
If a combination of the incoming Route A and the outgoing Route E is specified for
restriction, the state of tandem call connection becomes as shown above. In this case, only
tandem calls which come via the Route A and go via the Route E are restricted. Calls which
come via other routes (except Route A) and go via the Route E, and calls which come via
Route A and go via other routes (except Route E) are connected normally.
Specifying an incoming route for restriction
An Incoming Trunk (ICT) or a Bothway Trunk (BWT) route registered by [Route] icon
can be specified.
Specifying a outgoing route for restriction
Tandem switching office
Route D
Route E
Route F Route C
Route B
Route A
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 14 of 16
A Outgoing Trunk (OGT) or a Bothway Trunk (BWT) route registered by [Route] icon
can be specified.
(2) Restrict with combination of an incoming route, destination number(s), and access code
If a combination of the incoming Route A, the outgoing Route E, and local tandem call is
specified for restriction, the state of tandem call connection becomes as shown above. In
this case, only local tandem calls which come via the Route A and go via the Route E are
restricted. The other calls (except local tandem call) which come via the Route A and go to
via the Route E are not restricted. Also, calls which come via other routes (except Route A)
and go via the Route E, and calls which come via the Route A and go via other routes
(except Route E) are connected normally.
Specifying an incoming route for restriction
An Incoming Trunk (ICT) or a Bothway Trunk (BWT) route registered by [Route] icon can
be specified.
Specifying a destination for restriction
A destination is specified for restriction using a terminating number registered by
[Translator] icon.
Access code
The following call types which are determined by the receiving digit can be specified
for restriction:
trm (Intraoffice terminating call)
lcl (Local call)
dc (Direct call)
ope (Operator call)
std (Subscriber trunk dialing call)
A
B
(N=44)
(N=45)
44-XXXX
44-XXXX
45-XXXX
45-XXXX
Route A
Route B
Route C
Route E
Route D
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 15 of 16
Announcement
A restricted call is provided with any of the following announcements.
5.3 APPLICATION
Eliminating congestion of traffic directed to a specific destination
Eliminating congestion of traffic on a specific route
lt (Local tandem call)
asc (Operator access call)
call_tst (Test call)
isd (International subscriber dialing call)
ac1 (Restriction Announcement 1)
NEC PRACTICE
Issue 3, July 2000
INT-023-3110 16 of 16
NEC PRACTICE
INT-023-9100-14 (E) Icons Used for Traffic Control
Issue 4, May 2000
INT-023-9100 1 of 6
Icons Used for Traffic Control
1. SUMMARY
For easy operation, the switching system has the Graphical User Interface (GUI) function. When
operating and maintaining the switching system, use icons instead of commands in GUI. This section
describes the summary of such icon, and lists using icons in traffic control.
2. ICON AND ICON GROUP
The switching system has many functions for operation and maintenance. When operating and
maintaining the switching system, previously, use commands corresponded to each function. However,
such commands are difficult to use, so other tools called icons are prepared in GUI for easy operation.
The icon is a graphic representation for various functions in the switching system, and operating icon is
the same meaning as inputting command.
The number of icon is as same as the number of command. For easy to use icons, each icon is collected
by its function. The collected icons are called icon group.
NEC PRACTICE
Icons Used for Traffic Control INT-023-9100-14 (E)
Issue 4, May 2000
INT-023-9100 2 of 6
3. ICON WINDOW
To operate or maintain the switching system using icons, choose an appropriate icon and open its
window according to the following procedure:
To activate an appropriate icon:
STEP ACTION / REMARKS
1 Click [Start] located at the lower-left corner of the screen, and position the pointer at
[Program], [VitaOne], and an appropriate icon group in order. Then, click an
appropriate icon.
The selected icon is activated, and its window is opened.
Fig. 1 shows [Routing] icon window, and the following describe the meaning of each element.
Fig. 1 Example of Icon Window
Title bar
The name of the icon is displayed. When more than one windows is opened, the title bar for
the active window is a different color or intensity than others.
Menu bar
The available menus are listed. Most icons have a [File] menu and a [Help] menu.
Tool bar
The office name and the available buttons are displayed.
Tab
Some icons include various functions. These functions are assigned to each tab which has the
different window.
Data display field
Menu bar
Title bar
Tab
Operation field
Pull down button
Command button
[...] button
Data input box
Tool bar
NEC PRACTICE
Issue 4, May 2000
INT-023-9100 3 of 6
Operation field
A list of mutually exclusive operation buttons is displayed in this box. Only one operation
can be selected at a time. The selected operation button contains a black dot. Unavailable
operations are dimmed.
Data input box
Fields used for entering a data. Point and type a data to be entered directly, or specify an
appropriate item from a list box.
Pull down button
Some fields have a pull down button at the side of Data input box for displaying a list box.
[...] button
Some fields have a [...] button at the side of data input box for displaying a dialog box.
Data display field
The registered or a specified data is displayed in this field.
Command button
Executing buttons for the window.
NEC PRACTICE
Issue 4, May 2000
INT-023-9100 4 of 6
4. HOW TO OPERATE ICON WINDOW
Basic operation of each icon window is described below.
To use an icon help:
1 Click [Help] on the menu bar.
The [Help] window is opened, and displayed its contents.
2 Specify a desired item in the contents.
Information of the specified item is displayed.
To input a data in data input box (without pull down button):
1 Click a desired box.
The cursor flashes in specified box.
2 Type a data to be entered.
The typed data is entered in the box.
To input a data in data input box (with pull down button):
1 Click the pull down button of a desired box.
The list box appears.
2 Click an item to be entered from the list box.
The specified item is entered in the box.
To change an active tab to another tab:
1 Click a desired tab.
The screen changes to selected tab window.
To carry out command:
1 Click [Execute] button.
The specified data is registered and displayed in data display field.
NEC PRACTICE
Issue 4, May 2000
INT-023-9100 5 of 6
To clear all data in data input boxes:
1 Click [Clear] button.
The data is cleared from data input box.
To exit an active window:
1 Click [Close] button.
The active icon window is closed.
5. ICON LIST
Icons used for traffic control are as follows:
To set up an alternate route [Routing] icon
To set up route sharing [Route Sharing] icon
To set up TOD routing [Routing] icon
[Routing Schedule] icon
[Holiday] icon
To set up outgoing connection restriction [Restriction Level] icon
To set up originating restriction [Restriction Level] icon
To set up route restriction [Restriction Level] icon
To set up restriction class [Restriction Class] icon
NEC PRACTICE
Issue 4, May 2000
INT-023-9100 6 of 6
NEC PRACTICE
SECTION 3
TRAFFIC CONTROL PROCEDURES
NEC PRACTICE
NEC PRACTICE
PRC-023-1150-11 (E) Route Sharing Setting Procedure
Issue 4, July 2000
PRC-023-1150 1 of 6
Route Sharing Setting Procedure
1. SUMMARY
Setting route sharing allows traffic control. Route sharing refers to grouping several routes to a certain
destination into one group which is identified by a route sharing number. This module describes the
procedure for route sharing.
Notes:
1 Before setting routing data (PRC-1250 and PRC-1300), register route sharing data.
2 If more detailed explanation of parameters specification is needed, refer to I ntelligent
Maintenance and Administration Terminal (I MAT) Operation Manual.
2. BEFORE SETTING UP
Setting route sharing helps to prevent traffic congestion. Based on traffic data, route sharing and routing
information, determine which routes should be grouped.
NEC PRACTICE
Route Sharing Setting Procedure PRC-023-1150-11 (E)
Issue 4, July 2000
PRC-023-1150 2 of 6
To confirm the route sharing data
1 Activate [Route Sharing] icon in [Routing Control] icon group.
[Route Sharing] window appears.
2 Select View from Operation field.
3 Specify the desired route sharing number in Route Sharing Number box.
The registered route sharing data appears.
NEC PRACTICE
Issue 4, July 2000
PRC-023-1150 3 of 6
3. PROCEDURE
To register new route sharing data
1 In [Route Sharing] window, select Create from Operation field.
2 Specify a new route sharing number in Route Sharing Number box.
NEC PRACTICE
Issue 4, July 2000
PRC-023-1150 4 of 6
3 Click [Edit...] button.
The Route Sharing Data dialog appears.
4 Click [Add...] button.
The Route dialog appears.
5 Set the desired route sharing data.
5-A Specify a route name in Route Name box.
5-B Specify a digit addition/deletion control index in Edit Number box.
5-C If necessary, specify a route sharing rate in Rate box.
Notes:
1 When route sharing rate is omitted, the rate depends on the ratio of the number of
trunks in each route to a total number of trunks in a route sharing number.
2 Route sharing rate must not be partially omitted within the same route sharing
number.
5-D Click [OK] button.
The Route dialog disappears, and the specified route sharing data is displayed in the
Route Sharing dialog.
6 Click [OK] button.
NEC PRACTICE
Issue 4, July 2000
PRC-023-1150 5 of 6
The Route Sharing dialog disappears.
The new route sharing data is registered.
To change route sharing rate
1 In [Route Sharing] window, select View from Operation field.
All registered route sharing data appears.
3 Select Modify from Operation field.
4 Select the desired route sharing number from the left list box.
NEC PRACTICE
Issue 4, July 2000
PRC-023-1150 6 of 6
The Route Sharing Data dialog appears.
6 Select the data to be modified from the list box.
8 Specify a new route sharing rate in Rate box, and click [OK] button.
The Route dialog disappears.
The Route Sharing Data dialog disappears.
The changed route sharing data is registered.
4. EXAMPLE OF SETTING
Fig. 1 shows the example of setting up route sharing data.
Fig. 1 Example of Setting Up Route Sharing Data
In this case, the registered data in each box of [Route Sharing] window is as follows:
Route Sharing Number box 001
Route Name box in Route dialog abcd01, abcd02, abcd03
C
B
A
D
Grouping
Routing priority 3: abcd03
Route Sharing No.: 001
NEC PRACTICE
PRC-023-1250-11 (E) Routing Setting Procedure
Issue 4, November 1999
PRC-023-1250 1 of 8
Routing Setting Procedure
1. SUMMARY
Setting efficient routing allows traffic control. This module describes the procedure for setting normal
routing.
Notes:
1 Before setting routing data, register route sharing data by referring to PRC-1150.
Based on traffic data and routing information, determine which route or route sharing data should be set
as primary or alternate route.
To confirm the routing data
1 Activate [Routing] icon in [Routing Control] icon group.
[Routing] window appears.
NEC PRACTICE
Routing Setting Procedure PRC-023-1250-11 (E)
PRC-023-1250 2 of 8
3 Select Routing Data in Data Type box.
4 Specify the desired route index name in Route Index box.
5 Specify appropriate processing identifier in Processing Identifier box.
The registered routing data appears.
3. PROCEDURE
To set new routing data
1 In [Routing] window, select Create from Operation field.
5 Click Routing Data tab.
NEC PRACTICE
PRC-023-1250 3 of 8
The Routing Data dialog appears.
7 Set appropriate data for primary route.
7-A Click [Add...] button.
7-B To specify route data for primary route, select Route in Data Type box.
-or-
To specify route sharing data for primary route, select Route Sharing Number in
Data Type box.
The display of Route dialog is changed to either of the following:
NEC PRACTICE
PRC-023-1250 4 of 8
7-C For route data, specify route name in Route Name box and digit addition/deletion
control index in Edit Index box.
-or-
For route sharing data, specify route sharing number in Route Sharing Number
box.
Note: Routing priority depends on the order of setting routing data; the first entered
route name or route sharing number is used as the primary route.
The Route dialog disappears, and specified route data or route sharing data is
displayed in the list box of the Routing Data dialog.
Note: No. of the list box of the Routing Data dialog indicates routing priority; route
name or route sharing number assigned to No.00 corresponds to the primary
route.
8 Set appropriate data for alternate routes.
8-B To specify route data for alternate route, select Route in Data Type box.
-or-
To specify route sharing data for alternate route, select Route Sharing Number in
Data Type box.
-or-
box.
names or route sharing numbers assigned to No.01 through No.15 correspond
to the first alternate route through fifteenth alternate route. Routing priority
depends on the order of setting routing data.
8-E Repeat STEPs 8-A to 8-D until all necessary alternate routes are set.
Note: Up to 15 route names or route sharing numbers in total can be entered as
NEC PRACTICE
PRC-023-1250 5 of 8
alternate routes.
The Routing Data dialog disappears.
The specified data is registered.
To modify the routing data
1 In [Routing] window, select Modify from Operation field.
5 Click Routing Data tab.
NEC PRACTICE
PRC-023-1250 6 of 8
7 Modify the routing data as follows:
The specified data is modified.
To add a new route Click [Add...] button; the Route dialog appears.
Specify appropriate data for a new alternate route
in the Route dialog, and click [OK] button; the
dialog disappears.
To change the registered value
for route name, digit addition/
deletion control index or route
sharing number
Select the data to be modified from the list box.
Click [Edit...] button; the Route dialog appears.
Specify appropriate data in the Route dialog, and
click [OK] button; the dialog disappears.
To change the routing priority Select the data to be modified from the list box,
and click the up or down arrow button to change
the priority of the data.
To remove registered route Select the data to be removed from the list box,
and click [Remove] button.
To cancel the setting Click [Cancel] button.
NEC PRACTICE
PRC-023-1250 7 of 8
Fig. 1 shows the example of adding an alternate route to destination office B in order to prevent
congestion on route ogtb.
Fig. 1 Example of Adding Alternate Route
In this case, the registered data in each box of [Routing] window or Route dialog is as follows:
(1) To confirm the routing data
Route Index box
officeb
(2) To add an alternate route
Route Index box
officeb
Route Name box of Route dialog
ogtc
Edit Index box of Route dialog
Appropriate digit addition/deletion control index for route ogtc
Route index
officeb
Destination
office B
Adjacent
office C
B
C
D
Primary route
ogtb
Adjacent
office D

Current routing:
Route index=officeb
Primary route=ogtb
First alternate route=ogtd
New alternate route:
Second alternate route=ogtc
A
Originating
office A
Congestion
point
1st alternate
route ogtd
2nd alternate
route ogtc
NEC PRACTICE
PRC-023-1250 8 of 8
NEC PRACTICE
PRC-023-1300-16 (E) TOD Routing Setting Procedure
Issue 5, July 2000
PRC-023-1300 1 of 10
TOD Routing Setting Procedure
1. SUMMARY
The Time of Day (TOD) routing refers to a routing for a specific time or day when a traffic increase is
expected. Setting up TOD routing helps to prevent traffic congestion on a route. This module describes
the procedure for setting up TOD routing.
Notes:
1 Before setting TOD routing data, register route sharing data by referring to PRC-1150.
Based on traffic data and routing information, determine which route or route sharing data should be set
for TOD routing.
To confirm routing data
1 Activate [Routing] icon in [Routing Control] icon group.
[Routing] window appears.
NEC PRACTICE
TOD Routing Setting Procedure PRC-023-1300-16 (E)
Issue 5, July 2000
PRC-023-1300 2 of 10
3 Specify Routing Data in Data Type box.
5 Specify appropriate processing identifier for TOD routing in Processing Identifier box.
The registered TOD routing data appears.
To confirm TOD routing schedule
1 Activate [Routing Schedule] icon in [Routing Control] icon group.
[Routing Schedule] window appears.
The color displayed in View Result field tells which type of TOD routing schedule is
assigned to each unit time. The displayed colors are the same as those of the TOD schedule
indexes.
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 3 of 10
To confirm national holidays
1 Activate [Holiday] icon in [Routing Control] icon group.
[Holiday] window appears.
2 Select the desired month from the list box.
In the displayed calendar, the dates set as national holidays appear to be pushed in.
To modify the existing national holiday schedule
1 In [Holiday] window, select Modify from Operation field.
2 Select the desired month from the list box.
3 Click a date to be modified in the calendar.
The appearance of the clicked date is changed.
The national holiday schedule is modified.
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 4 of 10
3. PROCEDURE
Before assigning the specified route data or route sharing data to TOD routing, TOD routing schedule
should be registered.
To register TOD routing schedule
Using [Routing Schedule] icon modifies a schedule for TOD routing. Up to four types of TOD
routing schedules can be registered. Each TOD routing schedule is identified by a schedule index
(TOD01 to TOD04), and associated TOD routing is called TOD01 to TOD04 routing.
1 In the [Routing Schedule] window, select Modify from Operation field.
2 Select from among TOD01 to TOD04 option buttons in TOD Routing Schedule Index
field.
Note: TOD routing schedule index is initially set to TOD01.
3 In View Result field, click a portion corresponding to the desired day of the week and
the desired unit time.
The color of the selected portion changes to that of the selected TOD routing schedule index.
The TOD routing schedule is registered.
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 5 of 10
To set up TOD routing
1 In [Routing] window, select Create from Operation field.
4 To set appropriate TOD schedule index, select among tod1 to tod4 in Processing
Identifier box.
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 6 of 10
6 Set appropriate data for primary route.
6-B To specify route data for primary route, select Route in Data Type box.
-or-
To specify route sharing data for primary route, select Route Sharing Number in
Data Type box.
The display of Route dialog is changed to either of the following:
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 7 of 10
-or-
box.
Note: Routing priority depends on the order of setting routing data; the first entered
route name or route sharing number is used as the primary route.
name or route sharing number assigned to No.00 corresponds to the primary
route.
7 Set appropriate data for alternate routes.
7-B To specify route data for alternate route, select Route in Data Type box.
-or-
To specify route sharing data for alternate route, select Route Sharing Number in
Data Type box.
-or-
box.
names or route sharing numbers assigned to No.01 through No.15 correspond
to the first alternate route through fifteenth alternate route. Routing priority
depends on the order of setting routing data.
7-E Repeat STEPs 6-A to 6-D until all necessary alternate routes are set.
Note: Up to 15 route names or route sharing numbers in total can be entered as
alternate routes.
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 8 of 10
Fig. 1 shows the example of setting up routes from originating office A to destination office B on every
holiday to reduce traffic load on the routes from the office A to the office B.
Fig. 1 Example of Setting TOD Routing
In this case, the registered data in each box or field of [Routing] window, Route dialog and [Routing
Schedule] window is as follows:
(1) To set TOD routing schedule
TOD Routing Schedule Index field
TOD02 option button
View Result field
The day of the week: Holiday
The time of the day: 00 through 23 (all day long)
(2) To set up TOD routing
Route Index box
officeb
Processing Identifier box
tod2
Route Name box of Route dialog
Route index
officeb
Destination
office B
Adjacent
office C
B
C
D
Primary route
ogtb
Adjacent
office D

A
Originating
office A
Congestion
point
1st alternate
route ogtd
2nd alternate
route ogtc
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 9 of 10
ogtb, ogtd, and ogtc
Edit Index box of Route dialog
Appropriate digit addition/deletion control indexes for routes ogtc, ogtd and ogtc
NEC PRACTICE
Issue 5, July 2000
PRC-023-1300 10 of 10
NEC PRACTICE
PRC-023-3100-17 (E) Outgoing Connection Restriction Setting Procedure
PRC-023-3100 1 of 6
Outgoing Connection Restriction Setting Procedure
1. SUMMARY
Traffic is controlled by traffic restriction including outgoing connection restriction, originating
restriction, route restriction, and incoming and outgoing combined restriction. This module describes
the procedure for setting up outgoing connection restriction.
Note: If more detailed explanation of parameters specification is needed, refer to I ntelligent
2. BEFORE RESTRICTION
Route or traffic congestion may result from an increase in traffic to a specific destination. Such
congestion can be relieved by restricting outgoing connections. Destinations to be specified for
outgoing connection restriction are selected according to autonomous messages which indicate route
congestion, a traffic data, or information about a disaster.
Note: After the congestion is relieved and the traffic returns to normal, outgoing connection
restriction should be cancelled.
NEC PRACTICE
Outgoing Connection Restriction Setting Procedure PRC-023-3100-17 (E)
PRC-023-3100 2 of 6
3. PROCEDURE
To set up outgoing connection restriction
1 Double-click [Restriction Level] icon in [Traffic Control] icon group.
[Restriction Level] window appears.
2 Select Register from Operation field.
3 Specify Outgoing Restriction in Data Type box.
4 Specify terminating number(s) identified at the originating office in Destination
Number box.
5 Select restriction level in Level box.
NEC PRACTICE
PRC-023-3100 3 of 6
6 If necessary, specify reason for incompletion (factor ID) in Factor Identification box.
To change the specified restriction level and/or factor ID for a registered destination
number
3 Specify terminating number(s) identified at the originating office in Destination
Number box.
4 If necessary, select a new restriction level in Level box.
5 If necessary, specify a new factor ID in Factor Identification box.
NEC PRACTICE
PRC-023-3100 4 of 6
To cancel outgoing connection restriction
1 Select Cancel from Operation field.
3 Select restriction type in Restriction Type box.
-or-
Specify terminating number(s) identified at the originating office in Destination
Number box.
The specified data is deleted.
NEC PRACTICE
PRC-023-3100 5 of 6
Fig.1 shows the example of restricting outgoing connection calls to switching office A by specifying an
restriction level.
Fig. 1 Example of Outgoing Connection Restriction
In this case, the registered data in each box of [Restriction Level] window is as follows:
Destination Number box 45
Level box 9
Factor Identification box Emergency announcement Class1
A
C
B
45-XXXX
44-XXXX
46-XXXX
a
b
ANM
ANM
(N=44)
(N=45)
(N=46)
44-XXXX
44-XXXX
45-XXXX
45-XXXX
46-XXXX
46-XXXX
N=: Terminating number
NEC PRACTICE
PRC-023-3100 6 of 6
NEC PRACTICE
PRC-023-3200-14 (E) Originating Restriction Setting Procedure
Issue 5, July 2000
PRC-023-3200 1 of 6
Originating Restriction Setting Procedure
1. SUMMARY
restriction, route restriction, and incoming and outgoing combined restriction. This module describes
the procedure for setting up originating restriction.
Route or traffic congestion may result from an increase in calls. Such congestion can be relieved by
inhibiting ordinary subscribers originating calls. Control Processor (CP), Local Controller (LOC),
Digital Line Transmission Controller (DLTC), or 61E-LOC SHW Converter (SCONVL) is to be
specified for originating restriction according to a traffic data or information about a disaster.
NEC PRACTICE
Originating Restriction Setting Procedure PRC-023-3200-14 (E)
Issue 5, July 2000
PRC-023-3200 2 of 6
3. PROCEDURE
To set up originating restriction
1 Activate [Restriction Level] icon in [Traffic Control] icon group.
3 Specify Line Cut in Data Type box.
4 Specify the desired equipment name and equipment number in appropriate boxes.
5 Select restriction class in Class box.
6 Specify rotation timing in Timing box.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3200 3 of 6
To change restriction class and /or rotation timing for registered equipment
3 Specify the desired equipment name and equipment number in appropriate boxes.
4 If necessary, select a new restriction class in Class box.
5 If necessary, specify a new rotation timing in Timing box.
The selected data is modified.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3200 4 of 6
To cancel originating restriction
-or-
Specify the desired equipment name and equipment number in appropriate boxes.
The specified data is cancelled.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3200 5 of 6
Fig. 1 shows the example of inhibiting subscribers originating calls accommodated at LOC0102.
Fig. 1 Scope of Restriction Objectives
LOC Number box 0102
Class box 25
Timing box 5
LC
PHW
LOC
LC
PHW
LOC
KHW1
SSW* TSW
A
LOC0101
CP00
HUB
KHW0
CP01
LOC0102
CP01: Controls LOC0101 and LOC0102.
B
*: Installation of space switch (SSW) varies depending on the office conditions.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3200 6 of 6
NEC PRACTICE
PRC-023-3300-12 (E) Route Restriction Setting Procedure
Issue 5, July 2000
PRC-023-3300 1 of 6
Route Restriction Setting Procedure
1. SUMMARY
restriction, route restriction, and incoming and outgoing combined restriction.
Applying route restriction restricts outgoing calls on a specific route. Route restriction is carried out
according to the specified control pattern, call category, and restriction level.
This module describes the procedure for setting up route restriction.
Route or traffic congestion may result from an increase in traffic on a route. Such congestion can be
relieved by restricting outgoing calls on the route. Routes are to be specified for route restriction
according to autonomous messages which indicate route congestion, a traffic data, or information about
a disaster.
NEC PRACTICE
Route Restriction Setting Procedure PRC-023-3300-12 (E)
Issue 5, July 2000
PRC-023-3300 2 of 6
3. PROCEDURE
To set up route restriction
1 Activate [Restriction Level] icon in [Traffic Control] icon group.
3 Specify Route Restriction in Data Type box.
4 Specify outgoing route name in Route Name box.
5 Select control pattern in Control Pattern box.
6 Select call category in Call Category box.
7 Select restriction level in Level box.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3300 3 of 6
To change the specified restriction level and/or factor ID for registered route, control
pattern, and call category combination
3 Specify outgoing route name in Route Name box.
4 Select control pattern in Control Pattern box.
5 Select call category in Call Category box.
6 If necessary, select a new restriction level in Level box.
7 If necessary, specify a new factor ID in Factor Identification box.
The selected data is modified.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3300 4 of 6
To cancel route restriction
-or-
Specify outgoing route name in Route Name box, and select control pattern in Control
Pattern box and call category in Call Category box.
Note: The selection of control pattern and call category can be omitted.
The selected data is deleted.
NEC PRACTICE
Issue 5, July 2000
PRC-023-3300 5 of 6
Fig. 1 shows the example of restricting outgoing calls which overflow from the route to switching
office A by specifying an restriction level.
Fig. 1 Example of Route Restriction
Route Name box abcd1
Control Pattern box Reroute
Call Category box arh
Level box 4: Level4 - 50%
A
C
B
RN=: Route name
Route to restrict
Overflow calls
Overflow calls
Out-of-chain Route
Alternate route 2
(Alternate route 1)
RN=abcd2
RN=abcd1
RN=abcd0
50% of calls
50% of calls
(HTR)
NEC PRACTICE
Issue 5, July 2000
PRC-023-3300 6 of 6
NEC PRACTICE
PRC-023-3400-16 (E) Restriction Class Setting Procedure
PRC-023-3400 1 of 12
Restriction Class Setting Procedure
1. SUMMARY
restriction, route restriction, incoming and outgoing combined restriction, and subscriber originating or
terminating restriction. This module describes the procedure for setting up incoming and outgoing
combined restriction, and subscriber originating or terminating restriction.
Route or traffic congestion in a tandem office may result from an increase in calls on a specific route,
to a specific destination or to/from specific subscriber. Such congestion can be relieved by carrying out
incoming and outgoing combined restriction in tandem calls, or subscriber originating or terminating
restriction. Incoming routes, outgoing routes, destinations or subscribers are to be specified for the
restriction according to autonomous messages which indicate route congestion, a traffic data, or
information about a disaster.
NEC PRACTICE
Restriction Class Setting Procedure PRC-023-3400-16 (E)
PRC-023-3400 2 of 12
3. PROCEDURE
To set up the restriction of calls coming via a specific incoming route and going via
specific outgoing route(s)
1 Double-click [Restriction Class] icon in [Traffic Control] icon group window.
[Restriction Class] window appears.
3 Select In Route (Out Route) in Data Type box.
4 Specify incoming route name in In Route box.
5 Specify outgoing route name(s) in Out Route box.
NEC PRACTICE
PRC-023-3400 3 of 12
To set up the restriction of calls coming via a specific incoming route and going to
specific destination number(s) and access code(s)
3 Select In Route (Number) in Data Type box.
5 Specify destination number(s) in Number box.
6 Specify access code(s) in Access Code box.
NEC PRACTICE
PRC-023-3400 4 of 12
To register or modify the subscriber originating restriction
This restriction is applied to restrict subscriber originating calls according to the combination of
originating restriction class and destination restriction class.
3 Select Origination Restriction (Pattern) in Data Type box.
4 Specify originating restriction class in Originating Restriction box.
5 If necessary, specify originating restriction pattern in Pattern box.
The specified data is registered or modified.
NEC PRACTICE
PRC-023-3400 5 of 12
To register or modify the subscriber terminating restriction
This restriction is applied to restrict subscriber terminating calls according to the combination of
terminating restriction class and preceding office type.
3 Select Termination Restriction in Data Type box.
4 Specify terminating restriction class in Termination Restriction box.
5 If necessary, specify preceding office type (route class) in Route Class box.
The specified data is registered or modified.
NEC PRACTICE
PRC-023-3400 6 of 12
To modify factor ID for incoming and outgoing combined restriction
3 Specify In Route (Number) in Data Type box.
5 Specify destination number in Number box.
6 Specify access code in Access Code box.
7 Specify a new factor ID in Factor Identification box.
NEC PRACTICE
PRC-023-3400 7 of 12
To cancel the restriction of calls coming via a specific incoming route and going via
specific outgoing route(s)
1 Double-click [Restriction Class] icon in [Traffic Control] icon group window
3 Select In Route (Out Route) in Data Type box.
5 Specify outgoing route name(s) in Out Route box.
NEC PRACTICE
PRC-023-3400 8 of 12
To cancel the restriction of calls coming via a specific incoming route and going to
specific destination number(s) and access code(s)
3 Select In Route (Number) in Data Type box.
5 Specify destination number(s) in Number box.
6 Specify access code(s) in Access Code box.
NEC PRACTICE
PRC-023-3400 9 of 12
To cancel the restriction on a specified incoming route or outgoing routes
3 Select In Route in Data Type box.
-or-
Select Out Route in Data Type box.
-or-
Specify outgoing route name(s) in Out Route box.
The restriction of specified route(s) is cancelled.
NEC PRACTICE
PRC-023-3400 10 of 12
To cancel the subscriber originating or terminating restriction
3 Select Origination Restriction in Data Type box.
-or-
Select Termination Restriction in Data Type box.
4 Specify originating restriction class in Originating Restriction box.
-or-
Specify terminating restriction class in Termination Restriction box.
NEC PRACTICE
PRC-023-3400 11 of 12
Fig.1 shows the example of restricting local tandem calls from Route A to switching office A.
In this case, the registered data in each box of [Restriction Class] window is as follows:
In Route box abcd01
Number box 45
Access Code box Local tandem
A
B
(RN=abcd01)
(N=45)
44-XXXX
44-XXXX
45-XXXX
45-XXXX
Route A
Route B
Route C
Route E
Route D
ANM
NEC PRACTICE
PRC-023-3400 12 of 12
CC-1
CUSTOMER COMMENT FORM
Your comments on our manual are welcome. They will aid us in our effort to improve the quality and
usefulness of our documentation. Use this form to report errors or to make suggestions on improving
the contents of our manual. Make your comments below and mail or fax this form to the NEC office
serving your switch, or to the address in Japan shown below.
Comments: ..............................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
Date: ......................................................................
Submitted by:
Name: ....................................................................Job/Title: .................................................................
Office: .....................................................................Company: ...............................................................
Address: .................................................................
State/County: .........................................................Country: ..................................................................
Telephone number: .................................................
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cut here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Doc. Title: Traffic Control Manual
Doc. Number: ND-56906-307 (E) Issue: 4
In general, this documents is:
Usable and
Not usable
Usable but inadequate
Easy to understand
Difficult to understand
Reasons explained below
Use the address sheet shown on the left
when you mail directly to NEC.
As NEC is unable to supply the postage,
please make sure that your envelope has the
correct postage.
Attention: Manager (26-35400)
Technical Assistance and Service Center
NEC Corporation
1131 Hinode, Abiko, CHIBA 270-1198
JAPAN
FAX No. : 81-471-82-2125
(Continue overleaf)
NEC Control Number
CC-2
Comments (Cont.):..................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
Customer TASC Documentation
- - - - - - - - - - - - - - - - - - - - - - - - -Please do not write below this line.- - - - - - - - - - - - - - - - - - - -

ND 56906 307e 04

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ND 56906 307e 04

Uploaded by

Copyright:

Available Formats

ND-56906-307 (E)

Issue 4, September 2001

1998, 1999, 2001 by NEC Corporation

You might also like