CZ175899A3 - Telecommunication system - Google Patents

Abstract

The solution provides a telecommunications signal processor (400) for processing the signaling signaling telecorrosion signals System # 7 (SS7) to select ATM virtual connections and providing control messages that indicate selected ATMs virtual connections. Signal Processor: Computer System data structures, initial process logic and logic end process. Data Structure Circuit Table trunk lines (500), trunk group table (502), the exception table (504), the ANI table (506), the table called numbers (508) and routing table (510). Logic the initial process and the logic process stored in a computer system and process information of (SS7) signal messages related to the initial circuit and the circuit and enter the data structures so that have received the final ATM connection in response requirement from the initial process.

Description

Telecommunication system

Technical field

The invention relates to the processing of telecommunications communications for the purpose of establishing telecommunications routes. In particular, the invention relates to signaling signaling of Signaling System # 7 for establishing communication paths.

BACKGROUND OF THE INVENTION

Phone calls usually consist of call signaling and caller information. The call signaling is usually made up of data (eg, the called number) that the switches use to establish a call connection. The call connection transmits the caller's information (eg voice). The telecommunications switch comprises a processor capable of handling telecommunications signaling to select a call connection. These switches also include a switching matrix that can set the selected connections. The combination of the signal processor and switch matrix in the switch is problematic. The matrix increases cost and complexity. There has been a need to provide signal processors that will not be combined with a switching matrix.

In the United States, Signaling System # 7 (SS7) is the predominant form of telecommunications signaling. At the same time, the Asynchronous Transfer Mode (ATM) device for the transport of all kinds of data flows at high speed over connections is rapidly developing. Synchronous Optical Network (SONET). It is therefore necessary to provide signaling processors that will be able to process SS7 signaling and select ATM connections.

• · · · · · · · ·

SUMMARY OF THE INVENTION

The invention is a telecommunications signaling processor that processes Signal System # 7 telecommunications signaling messages to select asynchronous transfer mode (ATM) virtual connections and generates control messages that identify selected ATM virtual connections. The signal processor consists of: computer system, data structures, initial process logic and end process logic. The computer system stores the data structures and executes the stored logic. The call control data structure contains call-related information. The circuit data structure contains information relating to telecommunications connections. The exception data structure contains information relating to call routing exceptions. The call number data structure contains information related to caller numbers. The dialed data data structure contains information related to the dialed numbers. The routing data structure contains information related to call routing. The initial process logic is stored in the computer system and processes information from those SS7 signaling messages relating to the initial circuit, and enters data structures requiring. terminal ATM virtual connection. The end process logic is stored in the computer system and processes the information from the SS7 signaling messages and selects the end ATM virtual connection in response to the request from the start process.

Overview of pictures

Fig. 1 is a block diagram of a version of the invention.

Fig. 2 is a block diagram of a version of the invention.

Fig. 3 is a block diagram of a version of the invention.

Fig. 4 is a block diagram of a version of the invention.

r · · · · · «« «« «« «« * «« · · ·

US 28V · ’

Fig. 5 is a logic diagram of a version of the invention.

Fig. 6 is a logic diagram of a version of the invention.

Fig. 7 is a logic table used in a version of the invention.

Fig. 8 is a logic table used in a version of the invention.

Fig. 9 is a logic table used in a version of the invention.

Fig. 10 is a logic table used in a version of the invention.

Fig. 11 is a logic table used in a version of the invention.

Fig. 12 is a logic table used in a version of the invention.

Fig. 13 is a logic table used in a version of the invention.

Fig. 14 is a logic table used in a version of the invention.

Fig. 15 is a flow chart of the logic used in the version of the invention.

Figures 16A-16P are logic flow diagrams used in the version of the invention.

Figures 17A-17E are logic flow diagrams used in a version of the invention.

18A-18F are logic flow diagrams used in a version of the invention.

Figures 19A-19C are logic flow diagrams used in the 35 version of the invention.

·· ········ υΞ- * £ * 8? · *

Figures 20A-20D are version of the invention. logic flowcharts used ve 5 Figures 21A-21D are version of the invention. logic flowcharts used ve In Figs. 22A-22Q are shown version of the invention. logic flowcharts used ve 10 Figures 23A-23T are version of the invention. logic flowcharts used ve 15 Dec In Figures 24A-24M are shown version of the invention. logic flowcharts used ve In Figs. 25A-25B are shown version of the invention. logic flowcharts used ve 20 May In Figures 26A-26B are shown version of the invention. logic flowcharts used ve Figs. 27A-27D show version of the invention. logic flowcharts used ve 25 FIGS. 28A-28B show version of the invention. logic flowcharts used ve 30 Figures 29A-29C show version of the invention. logic flowcharts used ve Figures 30A-30L are version of the invention. logic flowcharts used ve

· «·« 7 ♦ · «« «

Figures 31A-31D are logic flow diagrams used in a version of the invention.

Figures 32A-32B are logic flowcharts used in the 5 version of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Giant. 1 shows a version of the invention. Shown are the Call / Connection Manager (CCM) 100, the communication device 110, and the communication device 112. The communication device 110 is connected to the communication device 112 by a connection 130. The communication device 112 is connected to other communication devices (not shown) by connections 131, 132 and 133. The CCM 100 is coupled to a communication device

110 via link 140 and communication device 112 via link 141. With other communication devices (not shown), the CCM 100 is connected via link 142.

The communication device 110 may be any device that aids communication through telecommunication signaling. Examples of such communication devices are switches, service platforms and Customer Premises Equipment (CPE). Examples of switches are Nortel DMS-250 and Lucent 5ESS. Examples of the service platform are voice response units and host computers that provide services such as voice messages or calling card use. Examples of CPEs are PBX devices, LAN devices, computers, telephones and switches. All these devices are known to those skilled in the art.

The communication device 112 may be any device that can establish a communication path in response to control instructions. Examples can be found between switches and ATM conversion multiplexers. The connection 130 may be any connection that supports communication with the network. The connection 130 may be any connection that supports communication. between communication devices 110 and 112. Examples are time division multiplex (TDM) connections such as DS3, DS1, DS0, E3, E1 and E0. Other examples are SONET, SDH, ATM, CDMA, GSM, PCS and cellular connections. Connections 131 to 133 are similar, although not necessarily the same, to connections 130. All of these connections are known to those skilled in the art.

The CCM 100 is a telecommunications signaling processor. Signaling System # 7 is a well known method of telecommunications signaling. SS7 signaling includes information that is exchanged between communication devices and which facilitates the establishment of communication paths for the user. A communication path usually consists of a set of connections between communication devices.

The signaling processor receives the signaling, processes it to select the connection, and sends control instructions to the at least one communication device to realize the connection. A detailed description of the CCM 100 is provided below.

Links 140 to 142 are any links capable of transmitting signaling or control messages between the CCM and the communication devices. Examples are SS7, ISDN or UDP / IP (or TCP / IP) over Ethernet. In some cases, a bus arrangement may also be used. Although not shown for the sake of clarity, various interworking devices such as routers, STPs (Signaling Transfer Point), or signal converters can be used to route signaling over links. Such devices and connections are well known to those skilled in the art.

The invention operates as follows. The communication device 110 requests a communication path by sending signaling over link 140. The CCM 100 receives the signaling and, if necessary, converts it to SS7. The CCM 100 processes the signaling and selects a connection, such as a connection 132. Next, the CCM 100 generates a control «9».

For example, the S * ~ * 2 θ instruction identifies connections 130 and 132 and sends it to communication device 112 over link 141.

Communication device 110 typically occupies a connection to 5 communication device 112 (this connection represents connection 130). The CCM 100 can also select this connection and then instruct the communication device to use connection 130. The communication device 112, based on a control instruction from CCM 100, will extend the communication path from connection 130 to connection 132. The CCM 100 can send another signaling over connection 142. facilitate further extension of the communication path. As a result of signaling processing in the CCM 100, a communication path is established from the communication device 110 through the communication device 112 over connections 130 and 132.

Giant. 2 is a more specific embodiment of the invention, but other versions are contemplated. Shown are CCM 200, communication device 210, ATM Interworking Unit 212, and ATM crosslink 220. ATM IWU

212 is coupled to ATM crosslink 220 by connection 234.

ATM cross-connect 220 is connected to other devices (not shown) via connections 231, 232 and 233. CCM 200 is connected to communication device 210 by link 240, to ATM IWU link 241, and to other devices by link 242.

The elements of FIG. 2 are similar to those described above with reference to FIG. 1, except that the communication devices 112 have replaced the ATM IWU 212, the ATM cross link 220, and the link 234. In addition, the communication devices 210 and link 230 do not

ATM. The ATM IWU 212 is a device that, based on control instructions from CCM 200, translates between non-ATM communication and ATM communication. ATM cross-connect 220 is a device that provides a predefined plurality of ATM virtual connections to ATM IWU 212. Connections 231-233 each «1 ··· * ·« · »* •» · v «• t · _Λ · ·· The US- ^e 287 carries a number of virtual connections. An example of an ATM cross-link is the NEC model 20. Connection 234 is an ATM connection.

In operation, the non-ATM communication device 210 requests 5 by sending signaling over link 240 for a communication path. The CCM 200 receives the signaling and processes it to select an ATM virtual connection. This ATM virtual connection has been previously defined via ATM crosslink 220 to the corresponding destination. For example, virtual connection A may form a path over connections 234 and 232 interconnected by ATM cross-link 220 and virtual connection B may form a path over connections 234 and 233 interconnected by ATM cross-link 220. CCM 200 may then select virtual connection B and provide ATM IWU 212 control instruction The ATM IWU 212 converts non-ATM communication on connection 230 to ATM communication on virtual connection B. CCM 200 may also send additional signaling over link 242 to facilitate further extension of the communication path. As a result, a communication path is established from the communication device 210 via the ATM IWU 212 and the ATM crosslink 220 over connections 230, 234 and 233.

The CCM 200, the ATM IWU 212, and the ATM Crosslink 220 are capable of providing ATM virtual connections to multiple destinations.

An important feature of the invention is that it makes it possible to select and establish connections to different destinations on the basis of individual calls. The CCM 200 is able to do this on a call-by-call basis without directly controlling the ATM cross link or switch. The ATM cross-connection is preconfigured to provide ATM connections to different destinations. Thus, the CCM 200 can route calls by selecting ATM connections and transferring non-ATM and ATM connections in the ATM IWU 212.

• ♦ · »US US US US US US US------------

In one embodiment, the communication device 210 is a conventional circuit switch, and the connection 230 is a DS0 busy for calling the switch. Switch (device 210) sends SS7 Initial Address Message (IAM) over link 240 to CCM

200. For example, the CCM 200 processes the IAM by examining the called number. Then, the CCM 200 selects an ATM Virtual Path Identifier / Virtual Circuit Identifier (VPI / VCI) that represents a virtual connection predefined via an ATM cross-connection

220 to the corresponding destination. The CCM 200 sends 241 bps over the link

ATM IWU 212 control message that identifies DS0 and selected VPI / VCI. The CCM 200 also sends another IAM to the destination via link 242. The ATM IWU 212, in response to the control instruction, converts communication between the DS0 and the selected VPI / VCI. The conversion involves translating the DS0 into ATM blocks and placing the VPI / VCI in the block headers. As a result, a communication path is established from the switch (device 210) through the ATM 'IWU 212 and the ATM crosslink 220 through the DS0 and the selected VPI / VCI (connections 230, 234 and 232).

For reverse call, CCM 200 receives IAM over link 242 and selects DS0 to communication device 210. To call used VPI / VCI and selected DS0, ATM IWU 212 is forwarded over link 241. / VCI and selected DS0. As a result, a communication path to the switch (device 210) is established via ATM cross link 220 and ATM IWU 212 over VPI / VCI and selected DS0 (connections 232, 234 and 230). From the foregoing description, it is apparent how an ATM connection from a limit switch to an end switch can be provided via two ATM IWUs and an ATM cross-link. CCM selects VPI / VCI and outgoing DS0. The first ATM IWU converts the incoming DS0 to VPI / VCI. The second ATM IWU converts the VPI / VCI to the outgoing DS0.

An important feature of the invention is that the switches can be provided with an ATM virtual connection to the corresponding fr »

JÍJS-2 # 7 destinations that are selected on a per-call basis. This can be achieved without the need to control the ATM switching matrix or cross wiring based on individual calls.

ATM Conversion Unit (ATM IWU) The subject of this section is a description of a preferred embodiment of an ATM IWU. Fig. 3 shows one embodiment of an ATM conversion multiplexer (mux) that is suitable for the invention

ATM IWU. Of course, other ATM IWUs capable of implementing the requirements of the invention may also be used. Shown are control interface 30, OC-3 interface 305, DS3 interface 310, DS1 interface 315, DS0 interface 320, digital signal processor 325, ATM Adaptation Layer (AAL) 330, and

OC-3 interface 335.

The control interface 300 receives messages from the CCM. More specifically, the control interface 300 provides the AAL 330 to realize a DS0 / virtual connection assignment. The control interface 300 may receive control messages from the CCM with instructions for DSO 320. These instructions may involve DSO interconnection to: 1) another DSO, 2) digital signal processor 325, or 3) AAL 330 (by-pass) digital signal processor 325). The control interface 300 can receive control messages from the CCM with instructions for the digital signal processor 325. An example of such an instruction is to disable echo cancellation on a particular connection.

The OC-3 interface 305 receives the OC-3 format and converts it into

DS3. The DS3 interface 310 receives the DS3 format and converts it into DS1. DS3 interface 310 can receive DS3 from either OC-3 interface 305 or from an external connection. The DS1 interface 315 receives the DS1 format and converts it into a DS0. DS1 interface 315 can receive DS1 from either DS3 interface 310 or an external connection. DSO • · a «« «* a a a a a a

The DSO interface 320 receives the DS0 format and provides an interface to the digital signal processor 325 or AAL 330. In some embodiments, the DSO interface 320 may be able to directly interconnect certain DS0s. This can be the case, for example, when a call enters and exits from the same mux. In addition, it also facilitates the continuity test performed by the switch. The OC-3 interface 335 is operative to receive ATM blocks from the AAL 330 and transmit them, usually after a cross link connection.

The digital signal processor 325 is operative to apply various digital processes to a particular DS0 in response to control instructions received through the control interface 300. Examples of digital processing are, for example: tone detection, tone transmission, feedback, voice detection, voice messages, echo cancellation, compression and Encryption. In some embodiments, digital signal processing 325 may also perform continuity testing. For example, CCM may instruct the mux to provide a loopback loop for the continuity test and to apply echo cancellation. The digital signal processor 325 is coupled to the AAL 330. As noted, the DS0 from the DS0 interface 320 can bypass digital signal processing 325 and connect directly to the AAL 330.

The AAL 330 includes both a Convergence Sublayer and a Segmentation And Reassembly sublayer (SAR). The AAL 330 is operative to receive user information in DS0 format from DSO interface 320 or digital signal processor 325 and convert the information to ATM blocks. AALs are known to those skilled in the art and can be found in the International Telecommunications Union (ITU) document 1.363. The AAL for voice communication signals is also the subject of patent application Serial No. 08 / 395,745, filed February 28, 1995, entitled Processing Voice Transmission Blocks, which is incorporated herein by reference. AAL 330 from the control interface

4 'i 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 444 444

300 obtains a Virtual Path Identifier (VPI) and a Virtual Circuit Identifier (VCI) for each call. The AAL 330 also acquires the DS0 identity of each call (or multiple DS0s for Nx64 calls).

The AAL 330 then converts the user information between the identified DS0 and the identified ATM virtual connection. Confirmation of the realization of the assignment, if desired, can be sent back to the CCM. Calls with a bit rate that is a multiple of 64 kbit per second are known as a name

Nx64 calls. If desired, the AAL 330 may also be able to receive control messages for the Nx64 call via the control interface 300.

As mentioned above, mux also handles calls in the opposite direction - from OC-3 interface 335 to DSO interface 320. Such a flow could be transferred to ATM blocks by another mux and routed to OC-3 335 via a selected VPI / VCI cross link. The control interface 300 provides the AAL 330 with the assignment of the selected VPI / VCI to the selected uplink DS0. The mux then converts the ATM blocks with the selected VPI / VCI in the block header to the DS0 format and provides them to the selected uplink DS0 connection.

A VPI / VCI process is described in patent application Serial No. 08 / 653,852 filed May 28, 1996 and entitled Telecommunications System with a Connection Processing System, which is incorporated herein by reference.

DS0 connections are bidirectional and ATM connections are usually only one-way. Thus, for each DS0, two virtual connections in opposite directions are usually needed. As mentioned above, this can be achieved by defining a pooled VPI / VCI in a direction opposite to the original VPI / VCI in a cross-link. Muxes are configured to automatically recall a specific pooled VPI / VCI at each call to create

• You have a two-way virtual connection that corresponds to a two-way DS0 call.

Signal processor

The signaling processor is called Call / Connection Manager (CCM) and is tasked with receiving and processing telecommunication call signaling and connection selection control messages that establish a communication path for calls. In a preferred embodiment, the CCM handles SS7 call signaling for signaling the connection.

In addition to selecting connections, CCM performs many other activities in connection with call processing. It not only controls routing and selects specific connections, but also verifies callers, controls echo cancellation, generates accounting information, invokes smart network functions, accesses remote databases, manages flows, and balances network traffic. Those skilled in the art will appreciate how the CCM described below can be adapted to work in the above embodiments.

Giant. 4 shows the CCM version. Other versions of CCM may be considered. In the embodiment of FIG. 4, the CCM 400 controls an ATM interworking multiplexer (mux) that performs DS0 and VPI / VCI conversion. However, the CCM may control other communication devices and connections in other embodiments.

CCM 400 consists of a signaling platform 410, a control platform 420, and an application platform 430. The platforms 410, 420 and 430 are interconnected.

The signaling platform 410 is interconnected with SS7 systems - more specifically with systems having a MTP Message Transfer Part, an ISDN User Part (ISUP), a Signaling Connection Control (SCCP) part. Two-way virtual connection that corresponds to a two-way DS0 call.

Signal processor

The signaling processor is called Call / Connection Manager (CCM) and is tasked with receiving and processing telecommunication call signaling and connection selection control messages that establish a communication path for calls. In a preferred embodiment, the CCM handles SS7 call signaling for signaling the connection.

In addition to selecting connections, CCM performs many other activities in connection with call processing. It not only controls routing and selects specific connections, but also verifies callers, controls echo cancellation, generates accounting information, invokes smart network functions, accesses remote databases, manages flows, and balances network traffic. Those skilled in the art will appreciate how the CCM described below can be adapted to work in the above embodiments.

Giant. 4 shows the CCM version. Other versions of CCM may be considered. In the embodiment of Fig. 4, the CCM 400 controls an ATM interworking multiplexer (mux) that performs the conversion between DS0 and VPI / VCI. However, the CCM may control other communication devices and connections in other embodiments.

CCM 400 consists of a signaling platform 410, a control platform 42Q, and an application platform 430. The platforms 410, 420 and 430 are interconnected.

Signaling platform 410 is interconnected with SS7 systems - more specifically, systems having a MTP Message Transfer Part, an ISDN User Part (ISUP), a Signaling Connection Control (SCCP) part. • · · · · · ··· ···

- · - ··· · · · · · ·

The accounting interface transmits the relevant accounting information to the accounting system. Common accounting information includes calling parties, time information about the call, and any special features requested by the call. The operating interface allows the CCM 400 to be configured and controlled. Those of ordinary skill in the art will understand how the interface software for the control platform 420 is created.

Application platform 430 is operative to process signaling information 10 from signaling platform 410 to select connections. The identity of the selected connections is passed to the mux interface control platform 420. Application platform 430 performs authentication, translation, routing, call control, exceptions, filtering, and error handling. In addition to providing control requirements for the mux, the application platform 430 is also in charge of creating echo control and resource management requests, which are then passed to the corresponding interface of the control platform 420. Furthermore, the application platform 430 generates signaling information that is transmitted by the signaling platform 410. .

The signaling information may be ISUP, INAP or TCAP messages to external network elements. Calls to the appropriate information are stored in the call to the appropriate call control block (CCB Call Control Block). The CCB is used for call tracking and billing.

The application platform 430 operates in accordance with the Basic Call Model (BCM) developed by the ITU. A BCM instance is established for each call. The BCM includes an initial process and an end process. The application platform 430 includes a Service Switch Function (SSF) that is used to invoke the Service Control Function (SCF). The SCF is typically located at a Service Control Point (SCP). SCF information is required by TCAP or INAP messages. Initial and? 5JS-*8 * 7 .. the end process to intelligent databases has intelligent capabilities network (IN) access via SSF function.

Application Platform 43Q software can be created 5 using the Specification and Description Language (SDL) as defined in ITU-T Z. 100. The SDL can be translated into C code. Additional sections in C or C ++ code can be added as needed to set up your production environment.

The CCM 400 may comprise the aforementioned software in a computer.

For example, the computer may be an Integrated Micro Products (IMP) FT-Sparc 600 with Solaris Operating System and conventional database systems. It may be desirable to utilize the capabilities of parallel (multithreaded) processing of Unix operating systems.

It is apparent from Fig. 4 that the application platform 430 processes signaling information to control the numerous systems and facilitate the connections and services required for the call. SS7 signaling is exchanged with external elements via signaling platform 410, control information exchanged with external systems goes through control platform 420. Preferably, the CCM 400 is not integrated into the CPU switch that is coupled to the switching matrix. Unlike SCP, CCM 400 can process ISUP messages independently of TCAP queries.

Marking of SS7 messages

SS7 messages are well known and the following message designations will surely be familiar to experts:

ACM Message address complete Address Complete Message ANM Answer message Answer Message BLO Blocking (Blocking) BLA Confirm blocking (Blocking Acknowledgment)

·· ··· · · • · ·

US-28? ·

CPG - Call continuation Call Progress CRG - Accounting information Charge Information CGB - Blocking a group circuit Circuit Group Blocking CGBA - Confirm blocking group heading Circuit Group Blocking Acknowledgment GRS - Resetting the group circuit Circuit Group Reset GRA - Confirm reset group heading Circuit Group Reset Acknowledgment) CGU - Unblock the group circuit Circuit Group Unblocking CGUA - Confirm unblocking of circuit group Circuit Group Unblocking Acknowledgment CQM - Query a group circuit (Circuit Group Query) CQR - Answering a question group heading Circuit Group Query Response) CRM - Reservation message circuit Circuit Reservation Message) CRA - Booking confirmation circuit Circuit Reservation Acknowledgment) CVT - Circuit validation test (Circuit Validation Test) CVR - Validation response circuit Circuit Validation Response) CFN - Ambiguity (Confusion) COT - Connection (Continuity) CCR - Continuity check requirement Continuity Check Request EXM - Output message (Exit Message) INF - Information (Information) INR - Information request (Information Request) IAM - Starting address Initial Address LPA - Confirmation feedback loops Loop Back Acknowledgment PASSPORT - Handover Pass Along REL - Release (Release) RLC - Release complete Release Release RSC - Resetting the circuit (Reset Circuit) RES - Renewal (Resume) SUS - Suspension (Suspend)

UBL

Unblocking

• Unblocking

UBA

UCIC

Unblocking

Acknowledgment)

Identification Code (Unequipped 'Unfitted Circuit Identification Code)

Circuit

CCM tables

Call processing typically involves two aspects. First, an incoming or initial connection is recognized by the initial call process. For example, the default connection that a user uses to enter a network is the initial connection on that network. Second, the outgoing or terminal connection is selected by the end call process. For example, the terminal connection is connected to the initial connection so that the call can be forwarded by the network.

These two aspects of the call are usually called the start side of the call and the end side of the call.

On . FIG. 5 shows the data structure that the application platform 430 uses to execute the BCM. This is accomplished by a series of tables that refer to each other in several ways. The pointer typically consists of additional functions and an indication of the next index. The next function points to the following table and the next index points to the value or range of values in that table. The data structure consists of a trunk circuit board (TRK CKT) table, trunk group table 502, exception table 504, ANI table 506, dialed number table 508, and routing table 510.

The trunk circuit table 500 contains connection information. The connections are typically DS0 or ATM connections. Initially, the trunk circuit table 500 is used to obtain initial connection information. Later, the end connection information is retrieved from the table. When processing the initial connection, the trunk group number in the trunk circuit table 500 points to ·· • »*

* TJS-2 € * 7 ·· * the appropriate trunk group of the initial connection in table 502 of the trunk groups.

The trunk group table 502 contains information 5 regarding the trunk group start and end groups. In the initial connection processing, the trunk group table 502 provides information regarding the trunk group for the initial connection and typically points to the exception table 504.

The exception table 504 is used to obtain a variety of exceptions and conditions that are related to a call and that may affect routing or other call processing. Exception table 504 typically points to ANI table 506, although it may point directly to trunk group table 502, dialed number table 508, or routing table 510.

ANI table 506 contains all special characteristics related to the caller number. The caller's number is usually called Automatic Number Identification (ANI). In an SS7 message, ANI information is transmitted in the calling party number field or the account number field. ANI table 506 typically points to dialed number table 508, although it may point directly to trunk group table 502 or routing table 510.

Based on the called number, the called number table 508 is used to identify all routing requests. This is the case with usual telephone calls. The dialed number table 508 usually points to routing table 510, although it may also point to trunk group table 502.

Routing table 510 contains information regarding routing calls over different connections. To the routing table

510 is entered according to the indicator from table 504 of the exceptions, ANI

20 May «· * · • · · · · · · · · · · · · · · · · · • · · · 4 4 ♦ * · »·· Table 506 or Table 508 of dialed numbers. Routing table 510 usually points to remote group management v

Table 502 trunk groups.

If the exception table 504, ANI table 506, dialed number table 508, or routing table 510 point to trunk group table 502, this means that they select a final trunk group. When the final connection is being processed, the trunk group number in the trunk group table 502 points to that trunk group that contains the usable terminal connection in the trunk circuit table 500.

The trunk line is used to extend calls. The trunk circuit is usually VPI / VCI or DS0. As described above, you can move the call tables to select the end connection.

FIG. 6 shows an extension of FIG. 5. The tables of FIG. 5 are also shown in FIG. Giant. 6 shows additional tables that can be accessed from the tables of FIG. 5. The new tables are CCM ID table 600, treatment table 604, query / answer table 606, and message table 608.

CCM ID table 600 contains various CCM SS7 node codes. It can be accessed from trunk group table 502 and points back to this table again.

The treatment table 604 identifies various special actions that can be invoked during call processing. This usually results in a REL release message and a causal value. The treatment table 604 is accessible from the trunk circuit table 500, the trunk group table 502, Λ-2ίί.

exception table 504, ANI table 506, dialed number table 508, routing table 510, and query / answer table 606.

The query / answer table 606 contains information for 5 SCF invocations. It is accessible from trunk group table 502, exception table 504, ANI table 506, dialed number table 508, and routing table 510. It points to trunk group table 502, excepted table 504, ANI table 506, dialed number table 508, routing table 510 and treatment table 604.

The message table 608 is used to provide message instructions from the end side of the call. It is accessible from trunk group table 502 and points again to trunk group table 502.

Figures 7 to 14 are examples of various tables described above. Fig. 7 shows a table of trunk lines. Initially, the trunk circuit table is used to access the initial circuit information. Later in the course of processing, it is used to obtain terminal circuit information. When processing the Initial circuit, the code of the corresponding node is used to enter the table. This is the switch node or CCM code corresponding to the start circuit. When processing the end circuit, the trunk group number is used to enter the table.

The table also includes the Circuit Identification Code (CIC). The CIC determines the circuit, which is usually DS0 or VPI / VCI. Thus, the invention is able to map the relationship between SS7 CIC and ATM VPI / VCI. If the circuit is an ATM, the virtual path (VP) and virtual channel (VC) can also be used for identification. The group member number is the numeric code used to select the end circuit. The hardware identifier identifies the location of the hardware associated with the start loop. Item • · «♦ · · · · ···

the echo canceler (EC) identification (ID) identifies the echo cancellation element of the initial circuit.

The remaining table fields are dynamic, that is, 5 is being filled during call processing. The echo management entry shall be completed on the basis of three boxes in the signaling messages; an echo cancellation indicator in IAM or CRM, an echo control device indicator in ACM or CPM, and the ability to transmit information in IAM. Based on this information, it determines whether the call requires echo control. The satellite indicator is filled with the satellite indicator in IAM or CRM. Can be used to reject calls if too many satellites are used. Circuit status indicates whether the circuit is idle, blocked or not blocked. Circuit status indicates the current status of the circuit, such as active or transient. The time / date indicates when the idle circuit has entered this state.

Fig. 8 shows an example of the trunk group table. During origin processing, the trunk group number from the trunk circuit table is used to access the trunk group table. The collision solution item indicates how to solve the collision situation. A collision (glare) means that one circuit is occupied by two calls. When set to even / odd, a network element with a higher node code controls even circuits and a network element with a smaller node code controls odd circuits. If this item is set to All, all circuits are controlled by CCM. If the collision solution item is set to none, the CCM does not intervene. The continuity control entry indicates the percentage of calls that a continuity test requires for a given trunk group.

The Common Language Location Identifier (CLLI) is a Bellcore standardized entry. Satellite trunk group item indicates that trunk group • · · * ··· · ·· t

♦ «· *

4 · · »·· ♦

· «·

υθ-ΣΘ ··?

uses satellite. The satellite trunk group entry is used together with the above satellite indicator to determine if the call is using too many satellite connections and must therefore be rejected. The operation indicator shows whether there is an incoming message from the CCM (ATM) or the switch (TDM). Outgoing Message Index (OMI) points to a table of messages from which outgoing messages can get parameters. The Number Pian Area (NPA) identifies the area code.

The selection sequence indicates how to select the connection. The selection sequence field tells the trunk group to select circuits based on the following criteria: least idle, longest idle, ascending order, descending order, clockwise, counterclockwise. The hop counter value decreases from IAM. If the hop counter reaches zero, the call is released. The Automatic Congestion Control (ACC) indicator shows whether the congestion control is active or not. If the AAC is active, the CCM can release the call. Additional functions and an index are used to enter the trunk circuit table during the end processing.

Giant. 9 shows an example of an exception table. The index serves as a pointer to enter the table. The Carrier Selection Identification parameter indicates how the caller entered the network and is used to route certain types of calls. The field may include: free or no indication, selected identification, carrier selection code prepaid and inserted by the calling party, selected carrier selection identification code prepaid but not embedded by the calling party, selected carrier selection identification code prepaid but not an indication, that the caller side was inserted and the selected carrier identification code was unpaid and entered by the caller side. The carrier identification indicates the network the caller wants to use. Used to route calls directly to the desired network. The nature of the called party's address distinguishes between 0+ calls, 1+ calls, test calls, and international calls. For example, international calls may be routed to a pre-selected international carrier.

The digits from and digits to the called party direct further processing of a clearly defined range of called numbers. The From field is a decimal number between 1 and 15 digits. It can be of any length, up to 15

digits to be filled zeros. Field digits to Yippee number ranging from 1 to 15 Dec digits. Can have 15 length, remaining places to 15 Dec digits to be filled

The next function and next index entries point to the next table, which is usually an ANI table.

Fig. 10 is an example of an ANI table. The index is used to enter 20 table fields. The calling party category distinguishes between calling party types, such as test calls, emergency calls, and normal calls. The address nature entry indicates how to obtain ANI. This field may include: unknown, unique subscriber number, ANI not available or not provided, unique national number, ANI called party included, ANI called party not included, ANI called party includes national number, subscriber, non-unique national international number, the test code test code and all 30 other parameter values.

non - unique number number, non - unique

The digits from and to indicate further processing unique to a particular ANI within a given range. The data entry indicates whether ANI is a data device that does not need echo control. Initial Route Information (QLI 25

»· • * «V • · • « * » * « • · • · ·· • • ··· »··

Originating Line Information) distinguishes between normal subscriber, multi-user route, ANI failure, station level assessment, special operator treatment, automatically identified external dialing, coin or non-coin call using database access, 800/888 service call, coin call, jail service institute, interception (empty, in trouble and regular), operator-operated call, operation of external intercity telecommunication network, telecommunication relay operation (TRS)

Telecommunications Relay Service), mobile traffic, private pay station, and types of services to access private virtual networks. Other functions and another index point to the next table, which is usually the dialed number table.

Fig. 11 shows an example of a dialed number table. The index is used to enter the table. The nature of the called number address indicates the type of called number, such as the national or international number. The digits from and to indicate further processing of the unique range of dialed numbers. The processing follows the logic described above in relation to the digit from and digit k fields of Figure 9. Additional Functions and Additional Index

show on another table that is usually routing table. On giant. 12 is an example of a routing table. Index up apply for input to the table. Selection identification plan

Transit Network Selection (TNS) indicates the number of digits for the CIC. The TNS digits from and to define the range of numbers to identify the international carrier. The circuit code indicates the need for an operator to make a call. The additional function and next index entries in the routing table are used to identify the trunk group. The second and third items of the next function / next index define alternate directions. The third item of the next function also points back to the next • · · ··· ♦ ·

With £ * 2 £ SJ a set of additional functions in the routing table, whereby the number of alternative directions options can be further expanded. The only other admissible items are indicators to the treatment table. If the routing table points to the trunk group table, then the trunk group table usually points to the trunk circuit in the trunk circuit table. The output from the trunk circuit table is the terminal call connection.

As is apparent from the tables of FIGS. 7 to 12, the tables may be configured and connected to each other in such a way that the call processes can enter the trunk circuit table for the initial connection and further navigate the tables by reference to information and pointers. The output of the tables is usually the terminal connection identified by the trunk circuit table. In some cases, instead of joining the treatment table, a call treatment is specified. If trunk group can be selected at any processing point, processing can proceed directly to trunk group table for direct end circuit selection. For example, it may be desirable to route calls from a particular ANI over a particular set of trunk groups. In this case, the ANI table points directly to the trunk group table and the trunk group table points to the trunk circuit table from which the end connection is already obtained. The preset table path is the order: trunk circuit, trunk group, exceptions, ANI, called number, routing, trunk group, and trunk circuit.

Fig. 13 is an example of a treatment table. Either the index or the causal value of the received message is filled in and used to enter the table. If an index is recorded and used, the general location, coding standard, and causal value indicator are used to generate SS7 REL. The cause value of the received message is the cause value in the received SS7 message. if

4 4

4 4 • 4 4 * 4444

444 ··· 4 ·

444 »44

06-28 * 7 records and uses the causal value of the received message, uses the causal value of the message in REL from the CCM. Other functions and another index point to the next table.

Fig. 14 shows an example of a message table. This CCM table allows you to change information in outgoing messages. The message type that is the outgoing standard SS7 message type is used to enter the table. The parameter is the corresponding parameter in the outgoing SS7 message. The indices point to different items in the trunk group table and determine whether the parameters in outgoing messages should be changed, omitted or modified.

Initial call processing

The tables described above essentially select the connection or call processing during its establishment. The remaining pictures discuss the processing of various SS7 signaling messages in the CCM. Well-known flow chart symbols are used in the figures. In the flowcharts, they indicate processing rectangles and diamonds represent decision making. The rectangles bulging in the shape of an arrow represent the sending of the message, the rectangles with bulging represent the receiving of the message. If a vertical line is added to the rectangle, it is an internal CCM message; if the added vertical line is missing, it is an external message. If the arrow or bulge is to the left, the message refers to the start page of the call.

If the arrow or bulge is to the right, the message refers to the end of the call. The transition from one image to the next will be indicated in the following description by placing the number of the next image in parentheses.

Giant. 15 shows the initial handling of all messages in the CCM.

The process begins with step 2QQQ in an idle state. A report will be adopted in 2002, which will be analyzed in 2004. If the report is not recognized in 2006, the ambiguity (COT) report will be sent back in 2008, the report will be canceled in 2010, and the maintenance process will be notified • · ·· ···· ♦ · ··· uS * -Í28 * S (maintenance) in 2010 and goes into idle again in 2014. If a message is detected in 2006, the trunk circuit table (trunk ckt) in 2016 will be checked. 2018, check the message type in 2020.

For the regular message, the UCIC message is returned at 2022 and the message is canceled in 2010. For 2020, the test message is canceled in 2010. If the 2020 message is CVT, CVR, CQM or CQR, or if it finds with the corresponding CIC at 2018, the message is analyzed at 2024. If the message process is confused (eg if the message is distorted) at 2026, the message is canceled in 2010. If not, the message type is determined at 2028 and 2030. Subsequent messages are sent for maintenance in 2032 before idle at 2034: BLO, BLA, UBA, RSC, CCR, LPA, CQM, CQR, GRS, GRA, CGB, CGBA, CGU, CGUA, CVT, CVR, and UCIC. All other messages are sent at 2036 to process the call before idle at 2038. Step 2036 also means establishing an BCM instance to process the call.

The BCM includes a process that handles the incoming page 20 of the call. This is known as the initial call process. The initial process receives messages and processes information related to the incoming call party. BCM also includes a process that handles the outgoing side of the call - the end call process. The end process receives messages and processes the information related to the outgoing party of the call.

Calls can be called intra-CCM calls. This is when the same CCM controls both ends of the call connection. Messages for intra-CCM calls can then be called internal messages. If the call is not an intra-CCM call, the call messages are either called external messages or have no special designation.

• «• 9 • • · · · · · · · · · · · · · · ·

Processing circuit tables and .... trunk groups for incoming calls

Figures 16A-16P illustrate the use of trunk circuit tables and trunk groups by an initial process. In Fig. 16A, the 2040 BCM is in an idle state. At 2041, an internal cast request is received from the outgoing (outgoing process, also called the end process) call process, at 2042 IAM information is read from the CCB, and processing continues until 2050. If the end (OTG) process requests a 2043 cast or if IAM is received in 2044, the IAM routing flag is checked in 2046. The IAM opens in 2048, and in 2050 the CIC information is read from it. The circuit status for the CIC is checked at 2052 and 2054. If the status is active at 2056 (Fig. 16B), maintenance is informed at 2058, a cause is sent to the treatment table with index 41 at 2060 and goes idle at 2062. v 2064 status pending, '2066 maintenance is informed, the cause table is sent to the treatment table with index 41 at 2068 and goes into idle at 2070. If status is disabled at 2072, the condition at 2070 is checked. blocking, it is ascertained in 2078 whether it is a test call of the called / calling party. If it is not a test call in 2080, the blocked status is removed in 2082 and the process If a local block is detected in 2076,

If it proceeds to 2098, the test call is detected at 2086, it is not the test called party (s), the call is triggered at 2088, and the inactivity is reached at 2090. If either 2080 or 2086 is determined to be a test call, the call at 2092 is marked as a test call. The circuit is designated as transient at 2094 and processing continues to 2272. After 2082, or if idle status is determined at 2096, the circuit is designated as transient at 2098. If the state is transient at 2100, a collision solution is invoked at 2102 and a solution is obtained at 2104. The incoming call collision control (INC) is determined in 2106 and 2108. If it has CCM control, it is marked with *.

k ··· circuit as transient at 2098. If control does not have an initial process, IAM is ignored at 2110 and goes idle at 2112. If the received message is an internal RLC at 2113 or an external RLC at 2114, the message is ignored at 2116 and goes to idle in 2118.

If CRM is received at 2120 (Fig. 16C), the routing flag at 2122 is checked and the message information is recorded in the CCB at 2124. The CIC is checked in the trunk circuit table at 2126 and the CIC status at 2128 and 2130. If the status is active (busy) at 2132, the maintenance at 2134 is inquired (Fig. 16D), a cause is sent to the treatment table with an index of 41 at 2136 and goes idle at 2138. If the status is unequipped at 2140, the maintenance at 2142, a cause is sent to the treatment table with index 47 at 2144 and goes idle at 2148. If remote blocking is detected at 2154, the blocked status at 2162 is removed and processing proceeds to 2192. If local blocking at 2154 is detected, it invokes With the blocking process in 2156, the circuit is marked as transient in

2158 and goes idle at 2160. If the status is transient at 2176, a collision solution is called at 2178 and a solution is obtained at 2180. Collision control for calls is determined at 2182 and 2184. If the control does not have CCM, IAM is ignored at 2186 and goes idle at 2188. If control has an initial process at 2184, processing continues at 2192. After 2162, 2184, or if idle status is detected at 2190, the circuit is designated as transient at 2192. At 2194, the TCRA timer starts and The CRA will be dispatched in 2196.

At 2198, the nature of the link indicator for the COT requests is checked. If COT is requested at 2200 (1), the COT process is invoked at 2204, the COT timer starts at 2206 and the process continues to 2482. If an internal REL at 2209 or an external REL at 2210 is received, the trunk circuit table is used to determine whether the intra-CCM call is at 2211 and 2212. If the intra-CCM call is at 2212, an internal RLC is sent at 2213. If it is not an intra-CCM call at 2212, an external RLC is • • ··· ··· • 87

If received in 2214, another internal message at 2216 or another external message at 2217 goes idle at 2215, then the circuit reset at 2218 is sent and goes to idle at 2215. 2220. If COT is not required at 2200 (0 or 2), 5 processing continues to 2222.

Waiting for IAM starts at 2222 (Fig. 16E). If an external IAM at 2223 or an internal IAM at 2224 is received, the IAM timer stops at 2225 and the continuity testing is set to 0 at 2226.

The process continues to 2272. If a reset is received at 2227 (from resetting a circuit, resetting a circuit group, sending a circuit query or sending a block group circuit), the circuit is marked idle at 2228 and goes idle at 2229. If a reset message is received v 2230 (since receiving a block / unblock circuit group), another internal message at 2231 or another external message at 2232, messages are ignored at 2233 and the process continues to 2222. If an internal REL at 2239 or an external REL at 2240 is received, whether the intraCCM call is at 2241 and 2242 (FIG. 16F). If the call is intra-CCM in

2242, the internal RLC is transmitted at 2243. If the intraCCM call is not at 2242, the external RLC is sent at 2244 and the circuit is marked idle at 2245. Echo control resets at 2246 and goes idle at 2248. If an internal RLC is received at 2249, an external RLC at 2250 or release requires a circuit query process at 2270 to determine whether the call is intra-CCM at 2251 and 2252. If the call is intra-CCM at 2252, an internal REL is sent at 2253. If the call is not intra -CCM at 2252, sends an external RLC with a cause normal at 2254. After 2253 or 2254, the COT is checked at 2255. If it is 1, the incoming continuity process stops at 2256 and the COT timer stops at 2258. If it is 2 at 2255, The COT timer stops at 2258. After 2258 or if 0 is at 2255, the circuit is marked as transient at 2260. The RLC timer starts at 2262 and the send timer REL at 2264. The echo control is reset at 2266 and the process continues to

3724.

After 2094, 2098 or 2226, the nature of the link indicator for COT requests is checked at 2272 (Fig. 16G) and 2274. If 1, the incoming continuity process starts at 2276 and the COT timer starts at 2278. If 2, the COT timer starts starts at 2278. If 0, processing proceeds to 2280 where the IAM information is stored in the CCB. Circuit busy time is sent for billing at 2282. Echo control information from the USI parameter is sent to echo control at 2284. The number of call attempts is counted at 2285. If attempts are 2 or more, the cause treatment table is sent at 2290 to the cause table with index 41 and goes into idle at 2292. If there are fewer than two attempts at 2288, the trunk group will check for automatic overload control (ACC) at 2294. If so, the call will be sent to the ACC process at 2298 ( 16H) and goes idle at 2300. If ACC is not needed at 2296, additional trunk table functions are obtained at 2306 and 2318. If the other function is an exception table at 2320, the index at 2322 is checked and calls are made. sends to exception table at 2324 and goes idle at 2326. If there is no other function at 2328, the call is sent to exception table at 2324. If another function is the trunk group table at 2336, the index at 2338 is checked and the call is sent to the outgoing section of the trunk group table at 2340. The initial process waits for the outgoing circuit to be selected by the end process at 3460.

Waiting for COT starts at 2344 (Fig. 161). If the COT timer expires at 2346, continuity requests are checked at 2348. If continuity testing is required, the incoming continuity check process stops at 2350. The cause is sent to the treatment table with index 41 at 2352 and goes idle at 2354. If continuity checking is not required at 2348, the cause is sent to the treatment table at 2353 and goes idle at 2354. If a call retry message is received at 2356, the process proceeds to step 2280. If it is received. *

··· * ·· • · · · ··· ···

BS-2S7 external COT at 2258 or internal COT at 2359, check continuity requirements at 2360. If continuity testing is required, the incoming continuity check process stops at 2362 and the COT timer stops at 2364. If continuity testing is not required at 2360, The COT timer stops at 2364. After 2364 or if continuity is 0 at 2360, the success test of continuity at 2366 is checked (Fig. 16J). If the test fails, maintenance is notified at 2368, the continuity check process is invoked at 2370 and goes idle at 2372. If the continuity test is successful at 2366, the COT is stored in the CCB at 2374. The process proceeds to 3250. receives reset at 2404, continuity requests are checked at 2406. If continuity testing is required, the incoming continuity check process stops at 2408 and the COT timer stops at 2410. If continuity testing is not required at 2406, the COT timer stops at 2410. After 2410 or if continuity is 0 at 2406, the circuit is set to idle at 2412 and goes idle at 2414.

If an external REL at 2420 (Figure 16K) or an internal REL at 2421 is received, continuity testing requests are checked at 2422. If continuity testing is required (1), the incoming continuity check process stops at 2424 and the COT timer stops at 2426. If continuity check is required on the previous circuit (2), the T8 timer stops at 2426. After 2426 or if continuity check is not required at 2422 (0), it is determined whether the intra-CCM call is a call at 2427 and 2428 ( 16L). If intra-CCM is a call at 2428, an internal RLC is sent at 2429. If it is not an intra-CCM call at 2428, an external RLC is sent at 2430. The idle indicator is sent for billing at 2431 and the circuit goes idle at 2432. resets at 2433 and goes idle at 2440. If a call release request is received at 2442, a message with cause 41 at 2444 is sent to the treatment table and goes idle at 2446. If a query is received *** ** · i · * · * ··· ·· ···· ··· ··· 4º ^- ¢ ^ 7 release circuit in 2462, external RLC in 2435 or internal RLC in 2436, processing continues to 2444. If receives another external message at 2464 or another internal message at 2465, checking for continuity testing at 2466.

If continuity testing is required (1), the incoming continuity check process stops at 2468 and the COT timer stops at 2470. If continuity check is requested on the previous circuit (2), the COT timer stops at 2470. If continuity is not required (0) ), the circuit reset process is invoked at 2472 and goes idle at 2474. If an external information message at 2316 or an internal information message at 2317 is received, call processing information is provided at 2318 and the wait for COT continues at 2344. If a blocking message is received at 2476, it is ignored at 2478 and the process continues to 2344.

Waiting for COT and IAM starts at 2482 (Fig. 16M). If the COT timer expires at 2484, continuity requests are checked at 2486. If continuity testing is required (1), the incoming continuity check process stops at 2488. The cause is sent to the treatment table with index 41 at 2490 and goes into idle at 2492. If continuity checking is not required at 2486 (2), the cause is sent to the treatment table with index 41 at 2490 and goes idle at 2492. If an internal COT at 24 93 or an external COT at 2494 is received, the requirements for continuity at 2496. If continuity testing is required, the incoming continuity check process stops at 2498 and the COT timer at 2500. If continuity check is not required at 2496, the COT timer stops at 2500. At 2502 (Fig. 16N) the success rate of the test is checked. continuity.

If it is not, maintenance is informed at 2504, the continuity check process is invoked at 2506 and goes idle at 2508. If continuity testing at 2502 is successful, the COT is retained in the CCB at 2510 and processing proceeds to 2222. If reset is received v 2512, the continuity requirements in 2514 are checked.

4 4 4

4 4

4444 • 4 • 44 44 »

444 444 requests, the incoming continuity check process stops at 2516 and the COT timer stops at 2518. If the continuity check is requested on the previous circuit (2) at 2514, the COT timer stops at 2518. If the continuity check is not required (0) v 2514, the circuit is set idle at 2520 and goes idle at 2522. If a blocking message is received at 2578, it is ignored at 2580 and the process continues to 2482.

If an external REL is received at 2528 {fig. 160) or internal REL at 2529, the continuity testing requirements are checked at 2530. If continuity testing is required (1), the incoming continuity check process stops at 2532 and the COT timer stops at 2534. If continuity check is requested on the previous circuit (2) or continuity check is not required (0), determine whether the intra-CCM call is a call at 2535 and 2536 (Fig. 16P). If the intra-CCM call is at 2536, an internal RLC is sent at 2537. If it is not an intra-CCM call at 2536, an external RLC is sent at 2538. After 2537 or 2538, the circuit is set idle at 2539. Echo control is reset at 2540 and goes idle at 2542. If an external RLC at 2544 or an internal RLC at 2545 is received, the continuity testing requirements are checked at 2548. If the continuity testing is required (1), the incoming continuity check process stops at 2550 and the COT timer stops at 2552. If continuity check is requested on the previous circuit (2) or continuity check is not required (0), it is determined whether the intra-CCM call is a call at 2553 and 2554. If the intra-CCM call is at 2554, it sends with an internal RLC at 2555. If it is not an intra-CCM call at 2554, an external RLC is sent with cause 41 at 2556. After 2555 or

2556 the circuit is designated as transient at 2557. At 2558, it starts

RLC timer and at 2559 the REL send timer starts. Echo control resets at 2560 and the initial process waits for RLC at 3724. If the circuit enable query is received at 2564, processing continues to 2548. If other external messages at 2566 or other internal messages at 2567 are received, the check will be checked. · Continuity testing requirements in 2568. If continuity testing is required (1), the incoming continuity check process stops at 2570 and the COT timer stops at 2572. If continuity check is required on the previous circuit ( 2) or continuity check is not required (0), the circuit reset process is invoked at 2574 and goes idle at 2576.

Exception table processing

Figures 17A-17E show the use of the exception table. In Fig. 17A at 2600, the use of the exception table is idle. At 2602, the BCM can enter an exception table based on another function in another table. At 2604, the index from the previous table is compared with the indexes of the exception table. If there is no match, the default routing is used at 2608. If the index is found, the IAM is checked for the CSP Carrier Selection Parameter and the Carrier Identification Parameter (CIP) at 2610 and 2612. If the CSP or CIP is not found, processing proceeds to 2670. If the CSP or CIP is found in 2612, the CIP is. checks for carrier identification and length at 2614 and 2616. If length is four digits, then carrier identification is compared to other four-digit carrier codes at 2618. If no match at 2620 is found, maintenance at 2622 is notified and processing proceeds to 2670. If match found at 2620, the CAC is recorded for billing at 2626 and processing proceeds to 2636 (FIG. 17B). If the number of digits at 2616 is three, the carrier identification is compared to the other three-digit carrier codes at 2628. If no match is found at 2630, maintenance is notified at 2632 and processing proceeds to 2670. If a match is found at 2630, CAC is recorded for billing v 2632 and the exception table row is checked for further information at 2636. If the code is free or unassigned at 2642, the CSP is recorded for billing at 2644 and maintenance is notified at 2646. Then a message is sent to the treatment table at 2648 with cause 111 and the process goes idle

37 • ♦ » * · · · • · · ··· v 2650. If checking v 2640 corresponds entry in 2652 (0000 0000 to 0000 0100) records se CSP for posting in

If the match is not found, maintenance is notified at 2660. If the match is found, the called number field is checked at 2664. If it is not filled in 2666, processing continues to 2736 .

If a 2664 match is found, the called party's 10 number in the CCB at 2670 (Fig. 17C) and the nature of the address at 2672 and 2674 are checked. If the subscriber number is found at 2676, the remaining items in that line at 2678 are also checked for match. 2680 (FIG. 17D). If a match is not detected at 2680, maintenance is notified at 2682, a message with an index of 45 at 2684 is sent to the treatment table, and the process goes idle at 2686. If a match is detected at 2680, the ANI is checked for the NPA to be used for If the NPA exists at 2690, the NPA is added to the called number at 2694 and the digits are checked in

2696. If the digits do not fall within a certain range in 2698, processing continues to 2682. If the digits fall within a certain range in 2698, processing continues to 2736. If a national significant number is found at 2700, the remaining entries in the row are checked for 2702 and 2704. If no match is found at 2704, processing continues to 2682. If a match is found at 2704, processing continues to 2696. If a test line or code is detected at 2706, the remaining items in the match line are checked at 2708 and 2710.If finds no match in 2710, processing continues to 2682.

If a match is detected at 2710, the call block is marked as a test call at 2712 and processing continues to 2696. If an international number is found at 2714, the remaining entries in the match line are checked at 2716 and 2718. If no match is found at 2718 , processing continues to 2682. If a match is found in 2718, processing proceeds to 2736. Such a call usually goes directly to a trunk group that is relevant to the international porters. If a cut-through or operator-operated number is detected at 2720, the remaining line items are checked for a match at 2722 and

2724. If no match is found at 2724, processing continues to 2682. If match is found at 2724, processing proceeds to 2736. Such a call usually goes directly to the trunk group that is appropriate to the international carrier. If an unoccupied number is found at 2726, maintenance at 2728 is notified, a message with index 111 at 2730 is sent to the treatment table and goes idle at 2732.

In 2736 (Fig. 17E) additional functions are checked. If the next table is a query / answer table at 2738, an index at 2740 is obtained. The call is sent to the query / answer table at 2742 and goes idle at 2744. If no table is named at 2746 or the next table is an ANI table at 2748 , the index is obtained at 2750. The call is sent to the ANI table at 2752 and goes idle at 2754. If the next table is the dial table at 2762, the index is obtained at 2764. The call is sent to the dial table at 27 66 and goes idle at 2768. If the next table is a routing table at 2770, an index at 2772 is obtained. The call is sent to the routing table at 2774 and goes idle at 2776. If the next table is a trunk group table at 2778, it gets The call is sent to the outgoing portion of the trunk table at 2782. The initial process waits for the outgoing circuit to be selected by the end process at 3460.

ANI table processing

18A-18F illustrates the use of the ANI table. In Fig. 18A, the ANI table is idle at 2800 until the BCM enters it from another function at 2801. At 2802, the index is checked and at 2803 a match is found. If the match is not found, it will be used in 2804. If the index matches the ANI table at 2805. After 2804, the predefined routing at 2803 is used to enter the or 2805, the OLI Originating Line Information at 2806 is checked. If the OLI does not exist at 5 2807, maintenance is notified at 2808 (Fig. 18B), an index message 111 at 2809 is sent to the treatment table and goes to idle at 2810. If the start line information is detected at 2807, the OLI digits are sent for billing at 2811 and the table is checked for OLI match at 2812 and 2813. If 10 match is not detected at 2813, maintenance at 2814 and OLI are equal. 2 is used in 2815. After 2815 or if a match is found in 2813, the calling party category in the IAM is checked at 2816. If the calling party category does not exist in 2817, processing continues to 2808. If the calling party category exists in 15 2817, it is compared s tab 2818 and 2819. For a regular subscriber at 2820, this is indicated in the CCB at 2821 and the table is checked for caller data at 2822 and 2823. If the call is a data call, the echo suppression for the call is turned off at 2824 and the call is 2825. After 2825 or if the call is not a data call at 2823, processing continues to 2834. If the category is other data information at 2826, maintenance is notified at 2827 and processing continues to 2821. If the category points to an emergency calls at 2828, high priority calls at 2830 or calls related to 25 with national security at 2831, the IAM priority is set to 1 and processing continues to 2821. If the category points to a test call at 2832, the call is marked as a test call at 2833 and processing continues to 2821.

At 2834 (Fig. 18C), the calling number, billing number, and calling party category are read from the call control block (CCB) from the IAM. If the calling party number does not exist at 2835, the billing number is checked at 2836. If the billing number does not exist at 2837, maintenance is notified at 2838, an index message 111 is sent to the treatment table at 2839 and passed to; · * · · ···; 40; ; 11 ^ 287

»» ···· ··· ··· ·· ·· idle at 2840. If the billing number exists in 2837, it is used as ANI in 2846. The billing number is ANI and the billing number is the calling number sends the billing in 2848. The nature of the billing number parameter is compared at 2850 and 2852 (FIG. 18D). If there is no match, maintenance is notified at 2854, the treatment table sends a message with cause 45 at 2856 and goes idle at 2858. If the match at 2860 is not an ANI pointer at 2860, the process proceeds to 2838. subscriber at 2862, adds NPA from trunk table at 2864 and adds NPA at 2866 to the billing number process. Then the process proceeds to 2904. If the 2852 match is the national number in 2868, the process proceeds to 2904. If the match is 2852 ANI with the called number at 2870 (0000 0101), add the NPA from the trunk table at 2872, and add the NPA at 2874 to the billing number process. After 2874 or if it matches 2852 ANI with the called number at 2871 (0000 0111), the called number parameter is 800 or 888 at 2876 and 2878. If it is not 800 or 888, the process continues to 2838. For 800 or 888, the process continues to 2904. If the calling party number exists at 2835, an account check is performed If the billing number exists in 2882, it is used as ANI in 2884. Information that the billing number is ANI and the calling number is the calling number is sent to the billing at 2886. Processing proceeds to 2850.

If the billing number does not exist in 2882, the calling party number is used as ANI at 2890. The information that the calling number is ANI and the calling number is the calling number is sent to the billing at 2891. The nature of the billing parameter address is compared at 2892 and 2893. there is no match, maintenance is notified

30, at 2854. If the match at 2893 is not ANI, processing continues to 2838. If the match at 2893 is a subscriber number at 2895, the NPA is added from the trunk table at 2896 and the billing number process is added at 2897. The process then continues to 2904. If the match at 2893 is a unique number in 2898, the process continues to 2904. If the match at 2893 is a unique number in

4i:

*. ** · »··· ··· ··· ·· ··

2899, the number is entered in the called number field and the billing number is left blank at 2900 and the process continues to 2904. If the match at 2893 is the test line or test code at 2901, it is marked as a test call in billing

2902 and processing continues to 2904.

In 2904 (Fig. 18E), a parameter for locating the calling number is determined. If the parameter is not at 2906, the billing number is specified at 2908. If the billing number is not at 2910, maintenance is notified at 2912, the cause with index 111 is sent to the treatment table at 2914 and goes idle at 2916. 2910, the calling party number for translation at 2918 is used. After 2918 or if the calling number parameter is found at 2906, the calling number is compared to the range in the table at 2922. If the number does not match at 2924, maintenance at 2926 is notified (fig. 18F), the cause with index 45 is sent to the treatment table at 2928 and goes idle at 2930. If a match at 2924 is found, the other functions at 3006 and 3008 are checked. If the next table is a 3010 query / answer table, the index is then sent to 3012. The call is then sent to the query / answer table at 3014 and goes idle at 3016. If the table is not listed at 3018 or if the next dialed table is at 3020, the index is The call is then sent to the dialed table at 3024 and goes idle at 3026. If the next routing table is at 3034, the index is obtained at 3036. The call is then sent to a routing table at 3038 and goes idle v 3040. If the next trunk group table is at 3042, the index is obtained at 3044. The call is then sent to the outgoing trunk table section at 3046 and goes idle at 3048.

Processing of dialed numbers table

Figures 19A-19C show the use of the dialed number table. Fig. 19A shows the processing of the dialed number table

«* · ·« · »Idle at 3050. The BCM enters the dialing table at 3052 when the call is forwarded to the dialing table by the previous next function. At 3054, the index is checked and compared to the table at 3056. If no match is found, the predefined routing at 3058 is used. After 3058 or if the index matches at 3056, the called party IAM number in the CCB at 3120 is checked and the nature of the address v 3122 and 3124, If the subscriber number is found in 3126, the remaining line items are checked for match in 3128 and 3130 (Fig. 19B). If no match at 3130 is detected, maintenance at 3132 is notified, index message 45 is sent to the treatment table at 3134 and goes idle at 3136. If a match is detected at 3130, the ANI is checked for the NPA to use, v 3138. If the NPA does not exist at 3140, maintenance is notified at 3142 and processing continues to 3184. If the NPA exists at 3140, it is added to the called number at 3144 and the digits checked at 3146. Processing proceeds to 3184. number in 3150, the remaining line items are checked for 3152 and 3154 matches. If no match is found at 3154, processing continues to 3132. If a match is detected at 3154, processing continues to 3146. If a test line or code is detected at 3156, the remaining line items are checked for matches at 3158 and 3160. If a match is not detected at 3160, processing continues to 3132. If a match is detected at 3160, the call block is flagged to indicate l test call at 3162 and processing continues to 3146. If an international number is detected at 3164, the remaining line items are checked for matches at 3166 and 3168. If a match is not detected at 3168, processing continues to 3132. If a match is detected at 3168, processing continues to

3184. Typically, such a call goes directly to the trunk group that is relevant to the international carrier. If a cut-through or operator-operated number is detected at 3170, the remaining line items are checked for 3172 and 3174 matches. If no 3174 match is found, processing proceeds to 3132. If a 3174 match is found, * · Processing continues to 3184. Such a call would normally go directly to the trunk group that is relevant to the operator's service. If an unoccupied number is detected at 3176, maintenance is notified at 3178, a message with index 111 at 3180 is sent to the treatment table and goes idle at 3182.

In 3184 and 3186 (Fig. 19C) additional functions are checked. If the next query / answer is at 3188, the index at 3190 is obtained. The call is then sent to the query / answer table at 3192 and goes idle at 3194. If the table is not specified at 3202 or if the next routing table is at 3204, the index The call is then sent to the routing table at 3208 and goes idle at 3210. If the next trunk group table is at 3212, the index is obtained at 3214. The call is then sent to the outgoing trunk table section at 3216 Initial process waits for outgoing circuit selection to be completed in 3460.

Routing table processing

20A-20D illustrates the use of a routing table.

In Fig. 20A, routing table processing is idle at 3220. At 3222, the BCM enters a table with a call that was passed by the previous next function. The index is checked at 3224 and 3226. If the index does not match at 3226, the predefined routing at 3228 is used. If the index match is found, the IAM is checked for a Transit Network Selection (TNS) at 3230. If the TNS is detected v 3236, compare the network identification plan to the tables in 3238 and 3240. If no match is found at 3240, maintenance is notified at 3242 (Fig. 20B), a message with index 45 at 3244 is sent to the treatment table and goes into idle v 3246. If a match is found at 3240, the network identification type is determined at 3248 and 3250. If the type is not a national network, processing continues to 3242. If the type is a national network, then the grid numbers in 3252 are compared in the table; of' " · · ··"·

4:: · ii · Ο »* 28Γ7ί.» ···· ··· ··· ·· ·· and 3254. If no match is found, processing continues to 3242. If the TNS is not at 3236 or if a match is found in 3258, the first request is determined at 3260 and 3262. If it is the first request at 3262, the next function at 3264 and 3266 is used. If the next function is empty at 3267, maintenance is notified at 3268, the cause is indexed to the treatment table. 41 at 3269 and goes idle at 3270. If the other database function is at 3271, the index at 3272 is checked. The call is sent to the query / answer table at 3273 and goes idle at 3274.

If the next function is a trunk group at 3275, the index at 3276 is checked and the call is sent to select an outgoing trunk at 3278. The initial process waits for the outgoing circuit to be selected at the 3460 termination process.

If the next function is not the first request at 3262, a second request is determined at 3282 (Fig. 20C) and 3283. If a valid second request is found at 3283, the table is checked to see if the second additional function entry is filled in 3284 and 3285. If the second additional function is not filled in 3285, the maintenance is notified in 3286, a cause message 34 is sent to the treatment table at 3287 and goes idle at 3288. If the second additional function is filled in 3285, the second additional function in 3290 is used. and 3291. If the next function is empty at 3292, the maintenance at 3293 is notified, the cause table is sent to the treatment table with index 41 at 3294 and goes idle at 3295. If the next database function is at 3296, the index at 3297 is checked. The call is sent to the query / answer table at 3298 and goes idle at 3299. If the next function is a trunk group at 3300, the index is checked at 3302 and the call is sent to select the outgoing remote. his leadership in the 3304th The initial process waits for outgoing circuit selection process to end the 3460th

If a valid second request is not found in 3283, the table checks whether the request is the third attempt at 3308 (Figure 20D) and

3310. If the third request is not valid at 3310, it will be notified *; : us «S87í φ · 9 · ·« ·· · * maintenance at 3312, a message with cause 34 at 3314 is sent to the treatment table and goes into idle at 3316. If the request is valid at 3310, the table checks to see if it is valid. If the third additional function is not filled in 3320, the maintenance is notified at 3322, a message with cause 34 at 3324 is sent to the treatment table and goes idle at 3326. If the third additional function is filled in 3320, then the third additional function is used in 3328 and 3330. If the next function is empty in 3332, maintenance in

3333, the cause is sent to the treatment table with index 41 at 3334 and goes idle at 3335. If the next function is a trunk group at 3336, the index at 3337 is checked and the call is sent to select an outgoing trunk at 3338. Initial process waits for outgoing circuit selection to be terminated at 3460. If the next database function is at 3339, the index at 3340 is checked. The call is sent to the query / answer table at 3341 and goes idle at 3342. If the next function is a routing table at 3343 , check for sub-index match at 3344. If no match is found at 3345, maintenance is notified at 3346, the cause table is sent to the treatment table at index 41 at 3347 and goes idle at 3348. If a match is found at 3345, the CCB resets to the first additional function in 3349 and processing continues to 3260.

Treatment table processing

Figures 21A-21D illustrate the use of a treatment table. In Fig. 21A, the treatment table is idle at 3350. The BCM enters the table at 3352 upon receipt of the message. In 3354 and 3456 the origin of the message is checked. If the message is an incoming REL message, the reason number is mapped to the index in the treatment table at 3358. The index entries and the received message are used to enter the table at 3360. If the number is not detected at 3362, maintenance is notified at 3363 to determine whether is calling intra-CCM at 3364 and

3365. If the intra-CCM call is at 3365, an internal REL ¢ 0 • 9 is sent

9

9 9

9 «» ·

9 • 9 »999 * I •» ··· ···

9

99 in 3366 (Fig. 21Β). If the call is not an intra-CCM at 3365, an external REL is sent with the same cause as received

3367. After 3366 and 3367, it is determined whether it is used at 3368. If 1, the incoming continuity process stops at 3370 and the COT timer at 3372. If 2 is at 3368, COT stops at 3372. After 3372 or if 0 , the circuit is designated as transient at 3374. The RLC timer starts at 3376 and the REL send timer starts at 3378. Echo control resets at 3380 and the initial process waits for RLC at 3724. If the number is detected at 3362, the causal values are checked in the table at 3384 and 3386. If the item is not filled in 3386, additional functions are checked at 3388 and 3390. If the next function type is empty or release at 3390, processing continues to 3364. The causal values of all other types of other functions at 3390 are not considered. v 3392. The next function is used at 3394 and goes into idle at 3396. If the entry is filled in at 3386, additional functions at 3398 and 3400 are checked. If the next function is empty or enabled at 3400, it is determined and is an intra-CCM call at 3401 and 3402. If the intra-CCM call is at 3402, an internal REL is sent at 3403. If the call is not an intra-CCM at 3402, an external REL is sent with a new cause at 3404. After 3403 or 3404 processing continues to

3368. The causal values for all other types of other functions in 3400 are not considered in 3405. The other function is used in 3406 and goes into idle at 3408.

If the message comes from the CCM frame at 3356, the index number at 3410 is checked (FIG. 21C). If the number is not detected at 3410, maintenance is notified at 3411 and it is determined whether the intra-CCM call is at 3412 and 3413. If the intra-CCM call is at 3413, an internal REL is sent at 3414. If the call is not intra-CCM at 3413, an external REL is sent with the same cause as received at 3415 (Fig. 21D). After 3414 and 3415, it is determined whether the COT at 3416 is used. If 1, the incoming continuity process stops at 3418 and the COT timer at 3420. If 2, the COT timer stops at 3420. After 3420 or if 0 is at 3416 , with us «38v.i • · * · · · · · · · · * · · okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh okruh 3426. Echo control resets at 3428 and the initial process waits for RLC at 3724. If the number is detected at 3410, it continues after the index line at

3432 and check the causal values in the table at 3434 and

3436. If the item is not filled in 3436, additional functions are checked in 3438 and 3440. If the next function type is empty or release in 3440, processing continues to 3412. All other types of 3440 additional functions are used in 3442 and go into idle v 3444. If the entry is filled in 3436, additional functions in 3446 and 3448 are checked. If the next function is empty or enable at 3448, it is determined whether the call is intra-CCM, at 3449 and 3450. If the call is intra-CCM at 3450, an internal REL is sent at 3451. If the call is not intra-CCM at

3450, an external REL is sent with a new cause at 3452. After 3451 or 3452 processing continues to 3416. The causal values of all other types of other functions at 3448 are not considered at 3453. The next function is used at 3454 and goes into idle at 3456.

Initial process - Call completion

At various locations in the processes described above, the initial process that handles the incoming call side may wait for some action on the outgoing call side before the call is complete. Examples are waiting to select an outgoing trunk group by the end process or receiving an ACM, ANM or RLC. The initial process can also receive RLC from the incoming side of the call. Giant. 22A-22Q illustrate how call completion processing is performed by the initial BCM process.

In Fig. 22A at 3460, the initial process waits for the outgoing circuit to be selected by the end process. If the outgoing circuit is selected at 3461, it is determined whether a COT was received at 3462. If

COT not accepted, CCB is checked for COT indicator in ΐ: /. ; : «ΆΜδ *:

»···» ... ... ·· ··

3463 and 3464. If 0 (COT not required) is detected, the process proceeds to 3520. If 1 or 2 is detected in 3464 (COT required), processing continues to 2344. If the COT was received at 3462, the COT result is sent to the end process v

3465 and processing continues to 3520. If internal is received

REL at 3466 or external REL at 3467, determines whether continuity check is required at 3468. If continuity check in that circuit is required (1), the incoming continuity check process at 3469 and the COT stop timer at 3470 are stopped. continuity check requests on the previous circuit (2), processing continues to 3470. After 3470 or if continuity check is not required (0), a release request is sent to the end process at 3478 and a release time for billing at 3480 (Fig. 22B). It is determined whether the intra-CCM call is at 3481 and 3482. If the intra-CCM call is at 3482, an internal RLC is sent at 3483. If the call is not an intra-CCM at 3482, an external RLC is sent at 3484. After 3483 or 3484, the circuit is marked as idle in 3485 in the trunk circuit table. It goes idle at 3486. If zeroing at 3479 is received, it is determined whether continuity check is required at 3487. If continuity check is required on that circuit (1) , the incoming continuity check process stops at 3488 and the COT stop timer at 3489. If continuity check is requested at the previous circuit (2), processing continues to 3489. After

3489, or if continuity checking is not required (0), a release request is sent to the end process at 3490 and a release time for billing at 3491. Determines whether the intra-CCM call is at 3492 and 3493. If the intra-CCM call is at 3493, an internal RLC is sent at 3494. If the call is not intra-CCM at

3493, an external RLC is sent at 3495. After 3494 or 3495, the circuit is marked as idle at 3496 in the trunk circuit table. It goes into idle at 3497.

If a release is received from the circuit query at 3498 (fig.

22C), an external RLC in 3499 or an internal RLC in 3500, is sent to ·· · »··: u $ -287 ·:

end process release request at 3501 and release time for posting at 3502. An index 41 message at 3503 is sent to the treatment table and goes idle at 3504. If a circuit selection failure at 3505 is received, it continues processing to 3502. If a COT at 6000 is received, it is determined whether a continuity check at 6002 is required. If a continuity check at that circuit is required (1), the incoming continuity check process at 6004 and the COT stop timer at 6006 stop. if continuity check is not required (0), the process of sending circuit reset is initiated at 6008 and goes idle at 6010. After 6006 a success indication is sent to the CCB or If COT fails in 6012. If COT fails in 6014, maintenance is notified in 6016 and the process goes back to 3460. If COT succeeds in 6014, it sends with the end process release request at 6018. The continuity check process is initiated at 6020 and goes idle at 6022.

If an internal information message at 3506 (Fig. 22D) or an external information message at 3507 is received, the message is sent to the end process at 3508 and the process returns to 3460. If a stall request is received at 3509, it is ignored at 3510 and processed. returns to 3460. If a retry message at 3511 is received, processing proceeds to 2280. If a COT time-out expires, the release time for billing at 3513 is sent and the cause with index 41 to the table at 3514. At 3515, a release request to the end process is sent to determine whether continuity check is required at 3516. If continuity check is requested at that circuit (1), the incoming continuity check process stops at 3517 and passes if idle at 3518. If continuity check is not required (0), it goes idle at 3518. If other internal messages are received at ·· ···. : us * 287 φ φ · · · φ φ

6026 or other external messages at 6028, determine whether continuity check is required at 6030. If continuity check in that circuit is required (1), the incoming continuity check process at 6032 and the stop timer COT at

6034. If continuity checking is required on the previous circuit (2), processing continues to 6034. After 6034, or if continuity checking is not required (0), a release request is sent to the end process at 6036. The continuity check process is initiated at 6038 and goes into idle in 6040.

At 3520 (Fig. 22E), the initial process waits for the ACM from the end process. If an ACM is received at 3522, the circuit in the trunk circuit table is marked as active at 3523.

The ACM time point is sent to the billing at 3524 and it is determined whether the intra-CCM call is at 3535 and 3526. If the intra-CCM call is at 3526, an internal ACM is sent at 3527. If the call is not an intraCCM at 3526, an external ACM is transmitted v 3527. After 3526 or 3527, the trunk group table is checked to see if the incoming trunk group is an Inter Machine Trunk (IMT) at 3529 and 3530 (Fig. 22F). If it is not, processing proceeds to 3600. If it is IMT, an output message is generated in the CCB with an uplink number at 3531. It is determined whether the intra-CCM call is at 3532 and 3533. If the intra-CCM call is at 3533, internal output message at 3534. If the call is not intra-CCM at 3533, an external output message is sent at 3535. After 3534 or 3535 the process continues to 3600. If a response message is received from the end process at 3538, the circuit is marked in the remote circuit table. In 3540 or 3541, the trunk group table is checked to see if the incoming trunk group is an inter-central trunk line (IMT). If the IMT is not at 3541, processing continues to 3547. If the IMT is at 3541, an output message is generated in the CCB with an Outbound number at 3542. It is determined whether the intra-CCM call is at 3543 and 3544. If ·· · «· · • US5-26I · * · '· ··· • ·· ·

if the call is not an intra-CCM at 3544, an external output message is sent at 3546. After 3545 or 3546, the billing time is sent at 3547. It is determined whether is an intra5 CCM call at 3548 and 3549. If the call is intra-CCM at 3549, an internal ANM at 3550 is sent. If the call is not an intra-CCM at 3549, an external ANM is sent at 3551. After 3550 or 3551, the process continues to 3670. If the reset is received at 2552, a release request is sent to the end process at 3553 and a release time to be charged at 3554. It is determined whether the intra-CCM call is at 3555 and 3556. If the intra-CCM call is at 3556, internal RLC at 3557. If the call is not intra-CCM at 3556, an external RLC at 3558 is sent. After 3557 or 3558, the circuit is marked idle in 3559 in the trunk circuit table. It goes into idle at 3560.

If an external REL is received at 3562 {fig. 22G) or internal REL at 3563, a release request is sent to the end process at 3564 and a Release Time to be charged at 3565.

It is determined whether the intra-CCM call is at 3566 and 3567. If the intra-CCM call is at 3567, an internal RLC is sent at 3568. If the call is not an intra-CCM at 3567, an external RLC is sent at 3569. After 3568 or 3569 the circuit is marked as idle in 3570 (fig. 22H) in the trunk circuit table. It goes idle at 3572. If an external RLC at 3575 or an internal RLC at 3576 is received, the idle time is sent to the billing at 3577 and the release request at 3578 is sent to the end process. At 3579, a message with cause 41 and goes idle at 3580. If release from circuit query at 3574 is received, processing continues to 3578. If end-release request is received at 3581 or outbound circuit failure at 3582, processing continues to 3579. If other internal receive is received message in 3583 or another external message in 3584, ignored in 3585 and processing returns to

3520. If a blocking request is received at 3586, it ignores

52 • · · ♦ · · · • · · · «· ♦ ·· • us ^ e ¹ ? ··: '··· · * ··· ·· ·· in 3587 and processing continues to 3520. If is accepted message continuation) Progress) by final process at 3590, determine if it is intra-CCM calls in 3591 and

3592. If the call is intra-CCM at 3592, an internal CPM 5 (CPG?) Is sent at 3593. If the call is not an intra-CCM at 3592, an external CPM is sent at 3594. After 3593 or 3594, the process returns to

3520.

At 3600 (FIG. 221), the initial process waits for a response from the end process. If a response message is received from the end process at 3602, the circuit is marked as active at 3604 in the trunk circuit table. The response time is sent for billing at 3606 and it is determined whether the intra-CCM call is at 3607 and 3608. If the call is not an intra-CCM at 3608, an external ANM at 3610 is sent. After 3609 or 3610, the process proceeds to 3670. If a blocking request is received at 3612, it is ignored. v 3614 and processing continues to 3600. If a call resume message is received from the end process in

3618, determine whether the intra-CCM call is at 3619 and 3620. If the intra-CCM call is at 3620, an internal CPM is sent at 3621. If the call is not an intra-CCM at 3620, an external CPM is sent at 3622. After 3621 or 3622, the process returns to 3520. If a reset is received at 3624, a release request is sent to the end process at 3626 and a release time to be billed at 3628. Determines whether the intra-CCM call is at 3629 and 3630. If the call is intra-CCM at 3630, an internal RLC at 3631 is sent. If the call is not an intra-CCM at 3630, an external RLC at 3632 is sent. After 3631 or 3632, the circuit is marked as idle at 3633 in the trunk circuit table. v 3634.

If an external REL at 3636 (Fig. 22 J) or an internal REL at 3637 is received, a release request at 3638 and a release time for billing at 3640 are sent to the end process.

: U3-287 ··:

· ♦ ··· ·· ♦ ···

Determine whether the intra-CCM call is at 3641 and 3642. If the intra-CCM call is at 3642, an internal RLC is sent at 3643. If the call is not an intra-CCM at 3642, an external RLC is sent at 3644. After 3643 or 3644 the circuit is marked as idle in 3645 in the trunk circuit table (Fig. 22K). It goes idle at 3646. If an external RLC at 3649 or an internal RLC at 3650 is received, the idle time is sent for billing at 3651 and the release process at 3652 is sent to the end process. 3653 and goes idle at 3654. If an end-of-process release request is received at 3656, processing proceeds to 3653. If an outbound loop failure is received at 3658, a message with cause 41 at 3659 is sent to the treatment table and goes to idle at 3660. If another internal message at 3661 or another external message at 3662 is received, it is ignored at 3664 and processing returns to 3520.

At 3670 (Fig. 22L), the initial process had previously received an ANM showing that the incoming circuit had received a response. If an external REL at 3672 or an internal REL at 3673 is received, a release request at 3674 and a release time for billing at 3676 are sent to the end process. Determine whether the intra-CCM call is at 3677 and 3678. If the call is intra- CCM at 3678, an internal RLC at 3679 is sent. If the call is not intra-CCM at

3678, an external RLC is sent at 3680. After 3679 or 3680, the circuit is marked as idle at 3681 in the trunk circuit table. It goes idle at 3682. If another internal message at 3683 or another external message at 3684 is received, it is ignored at 3686 and processing returns to 3670. If a blocking request is received at 3687, it is ignored at 3688 and processing proceeds to 3670. If a reset at 3690 is received, a release request at 3692 and a release time for billing are sent to the end process. v 3694. Determines whether the call is intra-CCM at 3695 and 3696. If the call is intra-CCM at 3696, an internal RLC at 3697 is sent.

US-28T • »»

3696, an external RLC is sent at 3698. After 3697 or 3698, the circuit is marked as idle at 3699 in the trunk circuit table. It goes into idle at 3700.

If an enable is received from the circuit query at 3702 (fig.

22M), processing proceeds to 3708. If an internal RLC at 3703 or an external RLC at 3704 is received, a release time for billing at 3706 and a request for release to the end process at 3708 are sent. 3710 and goes idle at 3712. If the release request is received from the end process at 3713, processing proceeds to 3710. If a network suspension is received from the end process at 3714, it is determined whether the intra-CCM call is determined at 3715 and 3716. If the call is intra-CCM at 3716, an internal SUS is sent at 3717. If the call is not intra-CCM at 3716, an external RLC is sent at 3718. After 3717 or 3718, processing proceeds to 3720.

At 3720 (FIG. 22N), the initial process had previously received the SUS indicating that the incoming circuit was suspended. If an external REL at 3721 or an internal REL at 3722 is received, a release request at 3723 and a release time for billing at 3725 are sent to the end process. Determine whether the intra-CCM call is at 3726 and 3727. If the call is intra- CCM at 3727, an internal RLC at 3728 is sent. If the call is not an intra-CCM at 3727, an external RLC at 3729 is sent. After 3728 or 3729, the circuit is marked as idle at 373Q in the trunk circuit table. It goes idle at 3731. If a blocking request is received at 3732, it is ignored at 3733 and processing returns to

3720. If an external RLC at 3735 or an internal RLC at

3736, the release time at 3737 is sent for billing and the release request at 3738 is sent to the ending process. At 3739, a reason message 41 is sent to the treatment table and goes idle at 3740. If a release is received from the circuit query at 3733, proceeds processing to 3738.

• * »

1 & - · £ 2 ··· ··

If the release request is received from the end process at 3741 (Fig. 220), a reason message 41 at 3742 is sent to the treatment table and goes idle at 3743. If a reset of 3744 is received, the release request is sent to the end process at 3745 and release time for billing at 3746. Determine whether the intra-CCM call is at 3747 and 3748. If the intra-CCM call is at 3748, an internal RLC is sent at 3749. If the call is not an intra-CCM at 3748 , an external RLC at

3750. After 3749 or 3750, the circuit is marked as idle in 3751 in the trunk circuit table. It goes idle at 3752. If a network restoration is received from the end process at 3753, the intra-CCM call is determined at 3754 and 3755. If the intra-CCM call is at 3755, an internal RES is sent at 3756.

If the call is not intra-CCM at 3755, an external RES is sent at 3757. After 3756 or 3757, processing continues to 3720. If another internal message at 3758 or another external message at 3759 is received, it is ignored at 3760 and processing returns to 3720 .

At 3724 (Fig. 22P), the initial process waits for RLC. If an external RLC is received at 3762, the idle time is sent for billing at 3763, and the RLC timer stops at 3764. At 3765, the release sending timer stops. It goes idle at 37 66. If the RLC timer expires at 3767, the release sending timer stops at 3768 and the circuit reset is sent at 3769. At 3770, maintenance is notified and goes idle at 3771. If another external message is received v 3772 or other internal message at 3773, ignored at 3774 and processing returns to 3724. If an external REL at 3775 (Fig. 22Q) or internal REL at 3776 is received, the release time for billing at 3777 is sent. whether the call is intra-CCM at 3778 and 3779. If the call is intra-CCM at 3779, an internal SUS is sent at 3780. If the call is not intra-CCM at 3779, an external SUS is sent at 3781. After 3780 or 3781, the process returns to 3724. If reset is received at 3782, the RLC timer stops at 3783. V: ust2 «7 ··: ··:

··········································································

3784 stops the release send timer and the trunk circuit table as idle at 3785. It goes idle at 3786. If the REL send timer expires at 3787, a message is sent to the treatment table with cause 41 at 5 3788. The REL send timer is set at 3789 and the process returns to 3724.

Processing of trunk circuit table and trunk group table for outgoing calls

Giant. 23A-23T show the processing of the trunk table by the BCM back-end process. In Fig. 23A at 2800, the end process is idle. The end process takes another function for the trunk group table from the initial process at 3802. The index is compared at 3806 and 3808. If a match is not found, maintenance is notified at 3810, a message with cause 45 at 3812 is sent to the treatment table and idle at 3814. If a matching trunk group is found at 3808, it is checked at 3816 to determine the trunk group rotation scheme at 3820. If the rotation is the longest idle (MIDL - Most Idle) at 3822 a

3824 (Fig. 23B), a message is sent to the most idle trunk selection process at 3826. This process determines the trunk that has been idle for the longest time at 3828 and returns trunk selection to the end process at 3830. Then the process proceeds to 3870. If the rotation is the least idle in

3822 and 3824, a message is sent to the Least Idle (LIDL) trunk selection process at 3832. This process determines that trunk which is idle for the shortest time in 3834 and returns trunk selection to the end process at 3836. Then, the process proceeds to 3870. If the rotation is ascending order at 3838 and 3840, a message is sent to the ascending trunk selection process (ASEQ) at 3842. This process determines that the trunk that is next in ascending order at 3844 and returns the trunk selection to the end process at 3846. Then the process continues to 3870. If! USr28 at 3838 and remote • φ * ·· φφφφ is a descending order of rotation (DESEQ - Descending)

3840, a message is sent to the downlink selection process at 3848. This process determines that the trunk line, which is next in descending order, at 3850 and returns the trunk line selection to the end process at 3852. Then the process proceeds to 3870. clockwise (CWCTH Clokwise) at 3854 and 3856, a message will be sent to the trunk selection process clockwise at 3858. This process determines the trunk that is next in 10 clockwise order at 3860 and returns the selection then the process continues to 3870. If the counterclockwise rotation (CCWCTH - Counter-Clokwise) at 3854 and 3856 is sent, a message will be sent to the trunk selection process counterclockwise 15 at 3864. This process it determines the trunk line, which is next in the counter-clockwise order, at 3866 and returns the trunk line selection to then process to 3870.

In 3870 (Fig. 23C) the satellite indicator is checked and if the satellite was used for the previous incoming circuit at 3872, the trunk group table is checked to determine whether the selected trunk will use the satellite at 3874 and 3876. If would be reused satellite, realizes maintenance in

3878, a message with cause 47 at 3880 is sent to the treatment table and goes idle at 3882. If the satellite is not reused at 3876, the hop counter is checked at 3884 and 3886 (Fig. 23D). If hop counter is active in CCB at 3888 and 3890. If hop counter is detected in CCB, it is decreased by one in 3892. If hop counter is now at zero at 3894, maintenance is notified at 3896, sent to the treatment table message with cause 47 at 3898 and goes idle at 3900. If the satellite was not used for an incoming circuit at 3872, the trunk group table is checked to determine whether the selected Outgoing Trunk (OTG) uses us * - $ 2 ·; '··:

*, »* ······ ··· ·· ·· satellite, at 3902 and 3904. If a satellite was used at 3904, the network indicator changes to indicate that a satellite was used, at 3906. After 3906 or if the satellite is not used at 3904, processing continues to 3884. If control at 3890 is negative, the IAM hop counter increments by 20 at 3891 and processing proceeds to 3908. If negative control is at 3886 or 3894, processing continues to 3908. At 3908, the service indicator entry is checked. In 3912, the type of trunk line is determined.

For TDM trunking (access), the trunking group is checked for COT capability at 3914 (Fig. 23E). Percent calculations are performed at 3916 to determine whether continuity check is required at 3918. If the trunk line type is ATM trunk line (IMT) at 3912 or if continuity check is not required at 3918, the IAM parameters are determined at 392Q. If the trunk line has a message index at 3922, a message at 3924 is sent to the message table and a response is received at 3926. The response, CIC, and associated node codes are used to build

IAM at 3928 and 3930 (FIG. 23F). Thereafter, processing proceeds to

3936. If the index is not found in 3922, they are used to build

IAM at 3932 and 3934 incoming IAM, CIC and related node codes. After 3930 or 3934, a message is sent to the mux and echo suppression with a circuit assignment - VPI / VCI at 3936 and the mux timer at 3938 is set.

3918, the IAM parameters at 3942 are determined. If the trunk has a message index at 3944, a message at 3946 is sent to the message table and a response is received at 3948. The response, CIC, and associated node codes are used to build the IAM at 3950 and 3952. Then, processing proceeds to 3958. If the index is not found in 3944, the incoming IAM, CIC, and related node codes are used to build the IAMs at 3954 and 3956. After 3952 or 3956, echo control is evaluated at 3958. If echo control is not needed, a circuit assignment message - VPI / VCI at 3960 is sent to the mux and the mux timer is set at 3962. Processing proceeds to 3968.

Echo control required in 3958, send a mux and echo suppression message to the circuit - VPI / VCI at 3964 and set the mux timer at 3966.

The end process is waiting for the mux response at 3968 (Fig. 23G).

If a response is received from the mux at 3970, the response type is determined at 3972. If it is accepted, the circuit is designated as transient at 3974 and a message that identifies the selected outgoing circuit is sent to the initial process at 3975. It is determined whether calls intra-CCM at 3976 and 3977 (Fig. 23H). If the call is intra-CCM at 3977, an internal IAM is sent at 3978. If the call is not intra-CCM at 3977, an external IAM is sent at 3979. After 3978 or 3979, a message is sent to invoke outbound continuity procedures at 3980 At 3982, the ACM timer is set and the process proceeds to 4100. If the answer is 3972 rejection, maintenance is notified at 3986. After 3986, the retry is checked within the same trunk group at 6050 and 6052. If retry is not allowed in 6052, the call counter is incremented to point to the next request, at 6054, the next function is used at 6056, and processing proceeds to 3282. If the retry is allowed at 6052, the first attempt in the CCB at 6058 and 6060 is checked. not the first attempt at 6060, the call counter is incremented to point to the next request, at 6062, the next function is used at 6064, and processing continues to 3282. As for the first attempt at 6060, the circuit is active in maintenance busy at 6066 and a circuit blocking process is initiated at 6068. The call attempt retry counter in the CCB is increased and the call attempt is repeated on the same trunk group in the

6072. Processing continues to 3816.

If the timer expires at 3992 (Fig. 231), the maintenance at 3994 is notified and a second assignment message is sent to the mux at 3996. The mux timer is set at 3998 and awaits a response at 4000. If the timer expires at 4002

* Maintenance at 4004, a reason message 38 at 4006 is sent to the treatment table, the release time is sent to billing at 4008 (Fig. 23J) and goes idle at 4010. If a response is received from the mux at 4012, it is determined response type at 4014. If it is accepted, the circuit is marked as transient at 4016 and a message that identifies the selected outgoing circuit is sent to the initial process at 4017. It is determined whether the intrat-CCM call is at 4018 and 4019. If it is In-CCM call at 4019, sends an internal IAM with continuity at 4020. If the call is not In-CCM at 4019, sends an external IAM with continuity at 4021. After 4020 or 4021, a message is sent to retrieve outgoing continuity procedures at 4022. V 4024, the ACM timer is set and the process proceeds to 4100. If the answer is 4014 rejection, check the retry option within the same trunk group at 6076. If retry is not allowed at 6076, the counter The call is increased at 6078 to point to the next request, the next function is used at 6080 and processing proceeds to 3282. If the retry is allowed at 6076, the first CCB attempt is checked at 6082 and 6084. If this is not the first attempt in 6084, the call counter is incremented in 6086 to point to the next request, the next function in 6088 is used and processing proceeds to 3282. As for the first attempt in 6084, the circuit is marked as active in 6090 and a lockout process is invoked The call attempt retry counter in the CCB is increased at 6094 and the call attempt is repeated on the same trunk group at 6096. Processing proceeds to 3816.

The end process is waiting for the mux response at 4040 (Fig. 23K).

If a response is received from the mux at 4042, the response type is determined at 4044. If it is accepted, the circuit is designated as transient at 4046 and a message identifying the selected outgoing circuit is sent to the initial process at 4047. It is determined whether call in-CCM at 4048 and 4049 (Fig. 23L). If the in-CCM call is at 4049, an internal IAM is sent without continuity at 4050. If u'4-26 ^ ·:

The call is not an intra-CCM at 4049, an external IAM is sent without continuity at 4051. After 4050 or 4051, the ACM timer is set at 4052 and the process proceeds to 4220. If the answer is at 4044 rejection After 4054, the retry is checked within the same trunk group at 6100 and 6102. If retry is not allowed at 6102, the call counter is increased at 3104 to point to the next request, the next one is used. the function at 6106 and processing continues to 3282. If the retry is allowed at 6102, the first attempt at CCB is checked at 6108 and 6110. If this is not the first attempt at 6110, the call counter is incremented at 6112 to point to the next request, the next function at 6114 is used and processing proceeds to 3282. For the first attempt at 6110, the circuit is marked as active in 6116 and the circuit blocking process is invoked at 6118. The call retry counter in C The CB increases in 6120 and the call attempt is repeated on the same trunk group at 6122. Processing continues to 3816.

If the timer expires at 4060 (fig. 23M), maintenance at 4062 is notified and the second message with a different assignment at 4064 is sent to the mux. The mux timer is set at 4066 and awaits a response at 4068. maintenance at 4072, the cause table 38 is sent to the treatment table at 4074, the release time is sent to the billing at 4076 (Fig. 23N) and goes into idle at 4078. If a response is received from the mux at 4080, the type is determined If it is accepted, the circuit is designated as transient at 4084 and a message identifying the selected outgoing circuit is sent to the initial process at 4085. Determine whether the intra-CCM call is at 4086 and 4087. If the call is intra-CCM at 4087, sends an internal IAM without continuity at 4088. If the call is not intraCCM at 4087, sends an external IAM without continuity at 4089. After 4088 or 4089, the ACM timer is set at 4090 and the process continues to 4220.in 4082 rejection, the possibility of retrying within the same is checked

Dál> «* ··· · <· ___ trunk group at 6130 If retry is not allowed at 6130, the call counter is incremented at 6132 to point to the next request, the next function is used at 6134 and processing continues to 3282 If the retry is allowed at 6130, the first CCB attempt is checked at 6136 and 6138. If this is not the first attempt at 6138, the call counter is incremented at 6140 to point to the next request, the next function at 6142 is used and processing proceeds to 3282. For the first attempt at 6138, the circuit is marked as active in maintenance at 6144 and the circuit blocking process is initiated at 6146. The call retry counter in the CCB is increased at 6148 and the call attempt is repeated on the same remote group lead in 6150. Processing continues to 3816.

At 4100 (Fig. 230), the end process waits for a message from the outgoing connection. If the message is successful (CCO Continuity Check Outgoing) at 4102, the CCB is updated at 4103. Determine whether the intra-CCM call is at 4104 and 4105. If the intra-CCM call is at 4105, an internal COT (success) at

4106. If the call is not an intra-CCM at 4105, an external is sent

COT (success) at 4107. After 4106 or 4107 processing proceeds to 4220. If the message is unsuccessful at 4108, the ATM timer stops at 4109 and determines whether the intra-CCM call is at 4110 and 4111. If the intra-CCM call is v 4111, an internal COT (failure) is sent at 4112. If the call is not an intra-CCM at 4111, an external COT (failure) is sent at 4113. After 4112 or 4113, the retry capability is evaluated at 4114 (Fig. 23P) and is allowed at 4116, the call counter is incremented at 4118. The initial process sends a retry message at 4120 and goes idle at 4122. If retry is not enabled at 4116, an outbound re-check process is initiated with the message at 4124 and passed after 4140, it is determined whether the outbound continuity procedure is completed at 4142. If not, the outbound continuity procedure stops at 4144 and processing proceeds to 4146. If they are

Outbound continuity procedures completed at 4142, processing continues to 4146. The ACM timer stops at 4146 and a message with cause 21 at 4148 is sent to the treatment table. The circuit is designated as transient at 4150 and the release time is sent for posting at 4152. At 4154 the RLC timer is set and at 4156 the REL timer is set. Processing proceeds to 4570. If internal RLC is received at 4133, processing proceeds to 4142.

If another internal message at 4160 (Fig. 23Q) or another external message at 4161 is received, it is determined whether the outbound continuity procedure is completed at 4162. If not, the outbound continuity procedure is stopped at 4163 and processing proceeds to 4164. Outbound continuity procedures completed at 4162, processing continues to 4164. The ACM timer stops at

4164 and a call retry message at 4165 is sent to the initial process. The release time is sent for billing at 4166 (FIG. 23R). At 4167, the message invokes the mux release process and goes idle at 4168. If an internal IAM at 4170 or an external IAM at 4171 is received, it is determined whether the outbound continuity procedure is completed at 4172. If not, the outbound continuity procedure at 4173. If a blocking request is received at 4174, or if a release request is received from an incoming process at 4175, a call retry request is sent at 4176. After 4176, it is determined whether the outgoing continuity procedure is completed at 4177. If not, it stops the outgoing continuity procedure at 4178 and processing continues to 4179. If the outgoing continuity procedures are completed at 4177, processing proceeds to 4179. The ACM timer stops at 4179 and a message with cause 21 at 4180 is sent to the treatment table. 4181 and the release time is sent for posting at 4182. At 4183 the RLC timer is set and at 4184 the REL timer is set. Processing continues to 4570.

• US-2 €% ·: * ···

··· ··· ·· ··

If an external REL is received from a downstream network element at 4186 (Fig. 23S) or an internal REL at 4187, it is determined whether the outgoing continuity procedure is completed at 4188. If not, the outgoing continuity procedure at 4189 stops and processing continues to 4190. If the outbound continuity procedures are completed at 4188, processing proceeds to 4190. The ACM timer stops at 4190 and a message with a cause from REL at 4191 is sent to the treatment table. Determine whether the intra-CCM call is at 4192 and 4193 (Fig. 23T) ). If the call is intra-CCM at 4193, an internal RLC is sent at 4194. If the call is not an intra-CCM at 4193, an external RLC is sent at 4195. After 4194 or 4195, the release time is sent for billing at 4196. The mux / echo release procedure goes into idle at 4200. If a lock reset at 4202 is received, it is determined whether the outbound continuity procedure is completed at 4203. If not, the outbound continuity procedure stops at 4204 and processing proceeds to 4205. If the outbound continuity procedures are completed at 4203, processing proceeds to 4205. The ACM timer stops at 4205, and a call retry message is sent at 4206 at the initial process. The release time is sent for billing at 4207. At 4208, the mux / echo release procedure message is invoked; goes idle at 4200. If an information message is received from the initial process at 4210, it is determined whether the intra-CCM call is at 4211 and

4212 (FIG. 23T). If the call is intra-CCM at 4212, an internal INF is sent at 4213. If the call is not intra-CCM at 4212, an external INF is sent at 4214. After 4213 or 4214 processing, it returns to 4100.

End process - Call completion

At various locations in the above description, the end process that serves the outgoing side of the call may wait for a message or action before the call is complete. Examples are (Js-2 ^ ?; waiting for ACM, ANM, or RLC. Fig. 24A-24M processing the call completion by the BCM end process.

In Fig. 24A at 4220, the end process waits for the ACM. If 5 is received by an external ACM at 4222 or by an internal ACM at 4223, the ACM timer stops at 4224 and the circuit is designated as active at 4226. At 4228, the charging link time is sent and at 4230 the ACM to the initial process. Then, the process proceeds to 4310. If an external ANM at 4232 or an internal ANM at 4233 is received, it stops

The ACM timer at 4234 and the circuit is designated as active at 4236. At 4238, the connection time for billing is sent and at 4240 ANM for the initial process. Then the process continues to 4400.

If a blocking request is received at 4242 (FIG.

24B) when an external RLC at 4244 or an internal RLC at 4244 is received

4245, the call recall message is sent to the initial process

4246. At 4248, the ACM timer is stopped and a message with index 41 at 4250 is sent to the treatment table. At 4252, the circuit is designated as transient and the release time is sent for posting in

4254. The RLC timer starts in 4256 and the send timer starts in 4258

REL. The process continues to 4570. If a release request is received from the initial process at 4260, processing continues to 4248. If the ACM timer expires at 4262, a call failure message is sent to the initial process at 4263 and the process continues to

4250.

If an external REL at 4264 (Fig. 24C) or an internal REL at 4265 is received, the ACM timer stops at 4266 and a message is sent to the treatment table from the REL at 4267. Determine whether the intra-CCM call is at 4268 and 4269 If the call is intraCCM at 4269, an internal RLC is sent at 4270. If the call is not an intra-CCM at 4269, an external RLC at 4271 is sent (Fig. 24D). After 4270 or 4271, the release time is sent for billing at 4272. At 4274, a message is sent to initiate the circuit reset process and goes into idle at 4276. If it is received as shown in · 42 Resetting from blocking at 4278, the ACM timer stops at 4280 and the call process is sent to the initial process at 4282. The release time is sent for billing at 4284 and the process continues to 4274. If an external CPM is received at 4286 or an internal CPM If the external IAM at 4290 or the internal IAM at 4291 is received, a busy message at 4292 is sent to the initial process and goes idle at 4294. If an INF message is received at 4295, it is determined whether the intra-CCM call is at 4296 and 4297. If the intra-CCM call is at 4297, an internal INF is sent at 4298. If the call is not intraCCM at 4297, an external INF is sent at 4299. After 4298 or 4299, the process goes back to 4220. If another external message at 4300 or another internal message at 4301 is received, the ACM timer stops at 4302 and the initial process starts sends a retry call at 4304. The release time sends for billing at 4306 and the process continues to 4274.

At 4310 (Fig. 24E), the end process is waiting for ANM. If a blocking request is received at 4312, it is ignored at 4314 and the process goes back to 4310. If a release request is received from the initial process at 4318, a release index message at 4320 is sent to the treatment table. At 4322, the circuit The RLC timer starts at 4326 and the REL send timer at 4328. Then the process proceeds to 4570. If an external ANM at 4330 or an internal ANM at 4331 is received, the time is sent posting responses at 4332 and ANM are passed to the initial process at 4334. The process continues to 4400. If an external EXM at 4336 or an internal EXM at 4337 is received, the

EXM billing information at 4338 and the process returns to 4310. If an external CPM at 4340 (Fig. 24F) or an internal CPM at 4341 is received, the information is sent to the initial process at 4342 and the process returns to 4310. If a reset is received from blocking at 4344, a kt release request is sent to the initial process at 4346 and the release time to be charged at 4348. The message is sent to the process circuit reset at 4350 and release to mux / echo process at 4352. Goes idle at 4354.

If an external REL at 4356 (Fig. 24G) or an internal REL at 4357 is received, an index report from REL at 4358 and a release time for billing at 4359 are sent to the treatment table. Determine whether the intra-CCM call is at 4360 and 4361. If the call is intra-CCM at 4361, an internal RLC is sent at 4362. If the call is not intra-CCM at 4361, an external INF is sent at 4363. After 4362 or 4363, a message is sent to the mux / echo release process at 4364. It goes idle at 4368. If an external RLC at 4376 is received, a call failure message at 4378 is sent to the initial process. At 4380, an index 41 message is sent to the treatment table. At 4382, the circuit is designated as a transient and release time sends to billing at 4384. At 4386 the RLC timer starts and at 4388 the REL send timer starts. The process continues to 4570. If a release from the circuit query process at 4392 is received or an internal RLC at 4393 is received, the process continues to 4380. If another external message at 4394 or another internal message at 4395 is received, it is ignored at 4396 and the process returns to 4310.

In 4400 (Fig. 24H) the call was answered and the call is active. If a blocking request is received at 4402 (Fig. 241), it is ignored at 4404 and the process returns to 4400. If an external RLC at 4408 or an internal RLC at 4409 is received, a call failure message at 4410 is sent to the initial process. 4412, an index 41 message is sent to the treatment table. At 4414, the circuit is designated as transient and the release time is sent for billing at 4416. At 4418 the RLC timer is started and at 4420 the REL sending timer is started. The process continues to 4570. If a release request is received from the circuit query process at 4424, processing continues to 4412. If a request is received

33-.237:

• · ·· ····

·· ♦ release request time release release from initial process at 4426, a message with release index at 4428 is sent to the treatment table. At 4430, the circuit is designated as transient, and the release time is sent for billing at 4431. At 4432, starts the RLC timer and at 4434 5 the timer sends REL. The process continues to 4570. If an external CPM at 4440 or an internal CPM at 4441 is received, information is sent to the initial process at 4442 and the process returns to 4400. If an external REL at 4444 or an internal REL at 4445 is received, it is sent to the table treat message with index from REL at 10 4446 and release time for billing at 4,447. Determine whether the intra-CCM call is at 4448 and 4449. If the intraCCM call is at 4449, an internal RLC at 4450 is sent. intra-CCM at 444 9, an external RLC at 4451 will be sent. After 4450 or 4451, a message will be sent to the mux / echo release process at 4452. 15 Go to idle at 4454. If reset is received from blocking at 4456, sent to initial process at 4457 and posting at 4458. The message is sent to the circuit reset process at 4459 and the release message to the mux / echo process at 4460. It goes into idle at 4 4 62. If an external SUS at 44 64 or an internal SUS at 4465 is received , SUS time is set The 4466 and the SUS are passed to the initial process at 4468. The process continues to 4480. If another external message at 4472 or another internal message at 4473 is received, it is ignored at 4474 and the process returns to 4400. 25

In 4480 (Fig. 24J) the outgoing circuit was suspended. If an external RLC at 4488 or an internal RLC at 4489 is received, a call failure message at 4490 is sent to the initial process. At 4494, __ XT «1» 4-. Ί ~ -. X 'i-. * __' -, ___ X __1_____ 3- | W / 1/1 Λ f? Us Λ _Λ pusic Λ. At 4470 SC UMUli, it is designated as a transient and the release time is sent for posting at 4498. At 4500, the RLC timer is started and at 4502 the REL send timer. The process continues to 4570. If a release request is received from the circuit query process at 4504, processing continues to 4494. If a release request is received from the initial process at 4506, the table is sent to • 4 • • 44 · · 44 ♦ ttS- 2 £ 7 • 44

4 · treatment message with release index at 4508. At 4512, the circuit is marked as transient and the release time is sent for billing at 4514. The RLC timer starts at 4516 and the REL send timer at 4518. The process continues to 4570. If the timer expires suspended at 4524, a release request at 4526 is sent to the initial process and a message with an index of 100 at 4528 is sent to the treatment table. At 4530, the circuit is designated as transient. At 4532 the RLC timer starts and at 4534 the REL send timer starts. The process continues to 4570.

If a blocking request is received at 4582 (Fig. 24K), it is ignored at 4484 and the process returns to 4400. If another external message at 4562 or another internal message at 4563 is received, it is ignored at 4566 and the process returns to 4400 If an external REL at 4536 or an internal REL at 4537 is received, an index message from REL at 4538 and a release time for billing at 4539 are sent to the treatment table. Determine whether the intra-CCM call is at 4540 and 4551. If If the call is not an intra-CCM at 4541, an external RLC at 4543 is sent. After 4542 or 4543, a message is sent to the mux / echo release process at 4544. Goes to idle at 4546. If a reset is received from the interlock at 4548, a release request is sent to the initial process at 4549 and a release time to billing at 4550. The message is sent to the circuit reset process at 4551. At 4552, it is sent to the mux / echo process. release message and it goes to idle the 4554th If receives an external message RES in 4556 or internal RES in 4557, stopped the timer in 4558 SUS and RES to transmit the initial process in the 4560th process returns to the 4400th

At 4570 (Fig. 24L), the end process is waiting for the RLC. If an external RLC at 4572 or an internal RLC at 4573 is received, the idle transition time at 4574 is sent. At 4578, the REL send timer stops. It goes idle at 4582. If the RLC timer expires at 4584, the send timer stops • * ··· ··· ·· ··

4588. Awareness t · · • * · ·······

REL at 4586 and invokes the circuit reset process at 4590 maintenance and goes into idle at 4592. If a reset is received from the interlock at 4548, a release request is sent to the initial process at 4595 and a release time 5 for billing at 4600 is sent. The message is sent to the circuit reset process at 4601. At 4602, a release message is sent to the mux / echo process and goes idle at 4604. If the REL send timer expires at 4606 (Figure 24M), an index message is sent to the release table. If the external REL at 4611 or the internal REL at 4609 is received, it is determined whether the intra-CCM call is at 4612 and 4613. If the intra call is intra -CCM at 4613, sends an internal RLC at 4614. If the call is not intraCCM at 4613, an external RLC at 4615 is sent. After 4614 or 4615, the 15 process returns to 4570. If another external message at 4616 or another internal message is received at 4616 or 4615. 46 17, ignored at 4618 and the process returns to 4570.

Different processes

In the above description, the BCM triggers the following processes: glare treatment, echo control, incoming circuit continuity check, automatic overload control, circuit reset sending, outgoing trunk selection, outgoing circuit continuity check and mux / echo release.

Figures 25-32 are flow charts of these various processes.

25A-25B illustrates a collision treatment process. At 4620, the collision treatment process is inactive. At 4622 (FIG. 25A), a query is received from the BCM. At 4624 and 4626, it is checked whether an ACM or ANM has been received. If yes, the control call is acknowledged at 4,628 and goes idle at 4630. If none of the messages were received at 4626, the collision solution in the trunk circuit table at 4632 and 4634 is checked. with control call at 4636 and · - ··· Φ ·· ·· ·· set to be used in :: ::. : Ss.ia.-f · ..

· ···· goes idle at 4638. If no control is in 4634, another 4640 is specified. The call is assigned to the new circuit control at 4642 and goes idle at 4644. If control is set to 5 even / odd at 4634, check the Originating Point Code (OPC) in the IAM at 4646 and compare with the CCM node code at 4648 (FIG. 25B). If the OPC in the IAM is higher than the CCM node code, the IIC CIC is checked to see if it is even or odd at 4648 and 4650. If it is even, control is granted 10 calls at 4654 and goes idle at 4656. If it is CIC odd, another circuit to be used is determined at 4658. The call is granted to the new circuit control at 4660 and goes idle at 4662. If the OPC in the IAM is not higher than the CCM node code at 4648, the CIC in the IAM is checked whether it is even or 15 odd at 4664 and 4666. If it is even, call control is acknowledged at 4,668 and goes idle at 4670. If the CIC is odd, another circuit to use is specified at 4672 The call is admitted to the new circuit control at 4674 and goes into idle at 4676.

Figures 26A-26B show the echo control process. At 4680 (Fig. 26A), the echo control process is idle. At 4682, a message is received from the BCM. If echo control information is received at IAM at 4684 or CRM at 4686, the circuit type at 4688 is checked and

4690. If the circuit is of LEC (TDM), the ability to transmit information at 4692 and 4694 is checked. If it is not a 3.1 kHz call, the echo control address is obtained from the trunk circuit table at 4696 (Fig. 26B). The associated echo cancellation is turned off at 4,698 and goes idle at 4700.

If the 3.1 kHz call is a call at 4694, the echo control entry is checked in the forward call indicator at 4702 and 4704. If the echo device is not included, the echo cancellation is not requested in 4706 and goes into idle at 4708. If the echo device is included, the echo control address is obtained from the trunk circuit table at 4710.

í fr ♦ · • 9 9 * * * * * tisk tisk tisk tisk tisk tisk tisk tisk tisk tisk

··· ··

The associated echo cancellation is turned off at 4712 and goes idle at 4714. If the circuit is from another CCM (ATM) at 4690, the information transfer capability is checked at 4716 and 4718. If it is not a 3.1 kHz call, the echo control address is obtained from The trunk circuit table at 4720. The associated echo cancellation is turned off at 4722 and goes idle at 4724. If the call is 3.1 kHz at 4718, the echo cancellation is not requested at 4726 and goes idle at 4728. If information is received echo control in 4730 ACM, 4732 CPM, or 4734 ANM, check the circuit type at 4736 and 4738. If the circuit is from another CCM (ATM), echo cancellation is not requested at 4740 and goes into idle at 4742 If the circuit is from LEC (TDM), the Echo Control item is checked in the callback indicator at 4744 and 4746.

If the echo device is not included, the CCB is checked to see if echo cancellation is enabled at 4748 and 4750. If not, echo cancellation is not required in 4752 and goes idle at 4754. If echo cancellation is enabled at 4750, the echo control address from the trunk circuit table at 4756. The associated echo cancellation is turned off at 4758 and goes idle at 4760. If the echo device is not included at 4746, the echo control off is not required at 4762 and goes to idle at 4764.

27A-27D illustrates the process of checking the continuity of the incoming circuit. In Fig. 27A at 4770, the continuity check process for incoming calls is idle. The message that triggers the process is received at 4772. At 4774, the CCB is checked to determine DS0 for continuity checking. At 477, the mux is instructed to link the DS0 to the feedback loop. The COT timer is set at 4778 and the process waits for a response from the mux at 4780 and 4782. If the COT timer expires at 4784, the mux message is sent again at 4786 and the timer starts again at 4788 (Fig. 27B). The process waits for a response from mux at 4790 and 4792. If the COT timer expires at

4794, the maintenance in 4796 is acknowledged, a message with index 41 at 4798 is sent to the treatment table and goes idle at 4800. If a response is received at 4782 or 4792, the message indicates that the feedback loop has been established at 4802. The COT timer stops at 4804. At 4806 and 4808, the CCB is checked for echo control requests. If echo control is required, the echo control address shall be obtained from the trunk circuit table at

4810. Associated Echo Suppression turns off at 4812.

At 4818 (FIG. 27C), a message is received to stop the continuity check. At 4820, the mux is instructed to disconnect the feedback loop, the COT timer starts at 4822, and the process waits for a response from the mux at 4824 and 4826. If the COT timer expires at 4828, the mux message is sent again at 4830 and the timer starts again at 4832 (FIG. 27D). The process waits for a response from mux at 4834 and 4836. If the COT timer expires at 4838, maintenance is notified at 4840, an index message of 41 at 4842 is sent to the treatment table and goes idle at 4844. If a response is received at 4826 or 4836, indicates that the feedback loop has been disconnected at 4846. The COT timer stops at 4848. The associated echo cancellation is turned on at 4850. It goes idle at 4852. At 4854, a message to stop the continuity check is received. At 4856, the mux is instructed to disconnect the feedback loop, the COT timer starts at 4858, and the process waits for a response from the mux at 4860 and 4862. If

The COT timer expires at 4864, the mux message is sent again at 4866, and the timer starts again at 4868. The process waits for a response from the mux at 4870 and 4872. If the COT timer expires at 4874, maintenance is notified at 4876, the treatment table is sends a message with index 41 at 4878 and goes idle at 4880. If a response is received at 4862 or 4872, the message indicates that the feedback loop was disconnected at 4882. The COT timer stops at 4884. It goes idle at 4886.

28A-28B shows an automatic overload control process. The automatic overload control process is idle at • * · t. ·. • * ····

B ·· »'bsržai ⁵ ..: • · · ·· ··

4890 (FIG. 28A) and the message is received at 4892. At 4894, the CCM load is checked. At 4896, the CCM table ID is checked to obtain a CCM overload level. 4898 determines whether the CCM load exceeds the overload level (ACL) 3. If yes, the maintenance is notified at 4900 and a REL is sent with cause 42 at 4902. If not, the CCM load is determined to exceed level 2 at 4904. If yes, the maintenance at 4906 is notified and REL is sent with cause 42 at 4908. If not, it is determined whether the CCM load exceeds level 1 at 4910. If yes, the maintenance at

4912 and the REL is sent with cause 42 at 4914. The COT is checked at 4916 (Fig. 28B). If 1, the incoming continuity process stops at 4918 and the COT timer at 4920. If 2, the COT timer stops at 4920. After 4920 or if 0 is at 4916, the circuit is marked as transient at 4922. The RLC timer starts at 4924 and REL send timer at 4926. The automatic overload control process waits for RLC at 3724. If the CCM utilization does not exceed congestion level 1 at 4910, the process continues to 2302.

Giant. 29A-29C illustrate the process of sending a circuit reset.

In Fig. 29A at 4940, the circuit reset sending process is idle. If a message is received from the BCM, processing proceeds to 4948. At 4942, a message is received from the mux that indicates a loss of circuit status and at 4944 the call processing is stopped. At 4946, the mux is instructed to release the circuit and reset it. At 4948, the circuit is designated transient. Determine whether the intra-CCM call is at 4949 and 4950. If the intraCCM call is at 4950, an internal RSC at 4951 is sent. If the call is not an intra-CCM at 4950, an external RSC at 4952 is sent. The Tib timer at 4953 and the T17 timer at 4956. Then the process waits for the RLC at 4958. If an internal RSC at 4960 or an external RSC at 4961 is received, it is determined whether the intra-CCM call is at 4962 and 4963 (Fig. 29B). If the call is intra-CCM at 4963, an internal RSC is sent at 4964. If the call is not intra-CCM at 4963, an external RSC is sent at 4965. After 4964 or 4965, the T16 and T17 timers at 4966 are stopped. if it is ·· "

»· ·»

t *

»» ·

E & Hold • * * · * ·· alert indicator on or off. If it is on, maintenance is notified at 4968. After 4968 or if the standby indicator is off at 4967, the circuit is marked idle at 4969 and goes idle at 4970. If an internal RLC at 4971 or an external RLC at 4972 is received, processing continues If an internal REL at 4973 or an external REL at 4974 is received, it is determined whether the intraCCM call is at 4975 and 4976. If the intra-CCM call is at 4976, an internal RLC at 4977 is sent. If the call is not intra-CCM at 4976, an external RLC is sent at 4978. After 4977 or 4978, processing continues to 4958.

If the T16 timer expires at 4979 (Fig. 29C), it is determined whether the intra-CCM call is at 4980 and 4981. If the intra-CCM call is at 4981, an internal RSC at 4982 is sent. after 4982 or 4983, the T16 timer starts at 4984. Then the process returns to 4958. If the T17 timer at 4985 expires, the T16 timer stops at 4986. At 4987, it is determined whether the standby indicator is on or off. . If it is on, the standby indicator is set at 4988 and maintenance is notified at 4989. After 4989 or if the standby indicator is off at 4987, it is determined whether the intra-CCM call is at 4990 and 4991. If the intra-CCM call is at 4991, an internal RLC at 4992 is sent. If the call is not intra-CCM at

4991, an external RLC is sent at 4993. After 4992 or 4993, the T17 timer starts at 4994. Then the process returns to 4958.

Figures 30A-30L show trunk line selection processes. In Fig. 30A-30B at 50 °, the longest idle trunk selection process that selects a trunk that has been idle for the longest time is idle. At 5012, a message requesting circuit selection is received. In 5014, the status and time items for circuits in the trunk group are checked. If there is no circuit in 5016, the maintenance in 5018 is notified and the call counter is incremented in 5020. In 5022, the • * · ♦ ··· ··· ·· ·· option is used

If they are crosses.

• · · ·· ···· Further routing and the process continues to 3260.

If all circuits are set to 0:00 at 5026, the first circuit in group at 5 5028 is selected and the selected circuit is provided to the end process at 5030.

It goes into idle at 5032. If all circuits are not 0:00 at 5026, the time status at 5034 is checked. If any circuits are available from the previous day at 5036, the circuit with the earliest time of the previous day at 5038 is selected. the circuit is provided to the end process at 5040 and goes into idle at 5042. If no circuit from the previous day at 5036 is available, the circuit with the earliest time of that day at 5044 is selected and the process continues to 5040.

In 5050 (FIG. 30C-30D) is the least idle trunk selection process that selects a trunk that has been idle for the shortest time, idle. At 5052, a message requesting circuit selection is received. At 5054, the status and time items for circuits in the trunk group are checked. If there is no circuit at 5056, maintenance at 5058 is notified and the call counter is increased at 5060. At 5062, the next routing option is used and the process continues to 3260. If trunk circuits are available at 5056, idle circuit times are checked. In group 5064. If all circuits are set to 0:00 at 5066, the last circuit in group at 5068 is selected and the selected circuit is provided to the end process at 5070. It goes into idle at 5072. If all circuits are not 0:00 at 5066, check the time state at 5074. If any circuits from that day at 5076 are available, then the circuit with the latest time of that day at 5078 is selected. there is no circuit from that day at 5076, the circuit with the latest time from the previous day at 5084 is selected and the process continues to 5080.

· »· 4 · 4 · ·

* 44 44

4 ·

444 4 • 4

In 5100 (Figs. 30E-30F), the trunk descending order selection process that selects a trunk that is idle and has the lowest order is idle. At 5102, a circuit selection request message is received. In 5104, the status items for idle circuits in the trunk group are checked. If there is no circuit at 5106, maintenance is notified at 5108 and the call counter is increased at 5110. At 5112 the next routing option is used and the process continues to 3260. If trunk circuits are available at 5106, it is determined for the first trunk group request at 5114 and 5116. For the first request at 5116, the last trunk in the group at 5118 is selected and the selected circuit is provided to the end process at 5120. It goes idle at 5122. If this is not the first request at 5116, the last trunk in the group at 5124 is selected. If the selected circuit is not active at 5126, the process proceeds to 5118. If the selected circuit is active at 5126, the next trunk available before the last trunk is selected, in 5128 and the process continues to 5120.

At 5130 (Figs. 30G-3QH), the trunk selection process in ascending trunk order that selects trunk that is idle and has the highest order is idle. At 5132, a message requesting circuit selection is received. At 5134, the status items for idle circuits in the trunk group are checked. If there is no circuit at 5136, maintenance is notified at 5138 and the call counter is increased at 5140. At 5142, the next routing option is used and the process continues to 3260. If trunk circuits are available at 5136, it is determined whether for the first trunk group request at 5144 and 5146. For the first request at 5146, the first trunk group in 5148 is selected and the selected circuit is provided to the end process at 5150. It goes idle at 5152. If this is not the first request in 5146, select the first trunk line in the group at 5154. If the selected circuit is not active in 5156, the process continues to 5148. If the selected circuit is active at 5156, the next trunk line, which is first available after the first trunk line, is selected at 5158 and the process continues to 5150.

In 5160 (Figs. 30I-30J), the counter-clockwise selection process of the trunk line, which selects the trunk line gradually from highest to lowest, is idle. At 5162, a message requesting circuit selection is received. In 5164, the status items for idle circuits in the trunk group are checked. If there is no circuit at 5166, maintenance at 5168 is notified and the call counter is increased at 5170. At 5172, the next routing option is used and the process proceeds to 3260. If trunk circuits are available at 5166, it is determined whether for the first trunk group request at 5174 and 5176. For the first request at 5176, the last trunk in the group at 5178 is selected and the selected circuit is provided to the end process at 5180. It goes idle at 5182. If this is not the first request at 5176, the last selected trunk from the group at 5184 is determined. The next free trunk in descending order at 5186 is selected. The selected circuit is provided to the end process at 5188. It goes idle at 5190.

In the 5200 (Fig. 30K-30L), the truncated selection process of the trunk line, which selects the trunk line gradually from lowest to highest, is idle. At 5202, a message requesting circuit selection is received. At 5204, the status items for idle circuits in the trunk group are checked. If no circuit at 5206 is available, maintenance at 5208 is notified and the call counter is increased at 5210. At 5212, the next routing option is used and the process continues to 3260. If trunk circuits at 5206 are available, it is determined whether o the first request for the trunk group in 5214 and 5216. As for the first request in 5216, and the first trunk selected is η · kové vybraný * vybraný vybraný « The 5218 line will be provided to the end process at 5220. It goes into idle at 5222. If this is not the first request at 5216, the last selected trunk from the group at 5224 is determined. 5226. The selected circuit is provided to the end process at 5228. It goes idle at 5230.

31A-31D illustrates the outgoing circuit continuity check process. In Fig. 31A, the uplink continuity check process is idle at 5240. At 5242, a message requesting uplink circuit continuity check is received. At 5244, the CCB is checked to determine the DS0 call. At 5246, the mux is instructed to establish a continuity test and disable the corresponding echo cancellation.

At 5248, the mux timer starts and awaits a response at 5250. If the mux timer expires at 5252, maintenance at 5254 is notified and the mux message is sent again at 5256. At 5258 (Fig. 31B), the mux timer restarts and waits response to 5260. If the mux timer expires at 5262, maintenance is notified at 5264, an index 41 message at 5266 is sent to the treatment table and goes idle at 5268. If a message is received from mux 5270, the message type is determined v 5272. If it is denied, the maintenance at 5274 is notified, the index table 41 at 5276 is sent to the treatment table and goes idle at 5278. If the message at 5272 is acceptance, the continuity tone is applied at 5280, COT starts 5282 timer and the process continues to 5300. If a message is received from mux 5286, the message type is determined at 5288. If it is rejected, maintenance is notified at 5290, a message with index 41 at 5292 is sent to the treatment table and idle in 5294. If is a message at 5288 acceptance, a continuity tone is applied at 5296, a COT timer is started at 5298, and the process continues to 5300.

At 5300 (Fig. 31C), the process waits for a status message from the mux. If an acceptance message is received (which shows that

• 9 • 999 * · * ··· ·· ·· test complete, tone removed and echo suppression on) at 5302, COT timer stops at 5304. Accept message is sent to BCM at 5306 and goes idle v 5308. If a reject message is received (indicating that the test is complete, the tone has been removed and echo suppression is on) at 5310, the COT timer stops at 5312. The reject message is sent to the BCM at 5314 and goes into idle at 5316. If the COT timer expires at 5318, maintenance is notified at 5320 and the mux is requested to retry the COT information at 5322. The COT timer starts at 5324 and waits for a message from the mux at 5326. If the COT timer expires at 5328 (fig. .

31D), the maintenance at 5330 becomes aware and goes idle at 5332. If an acceptance message (indicating that the test is completed, the tone has been removed and echo suppression on) is received at 5338, the COT timer stops at 5340. Message indicating acceptance is sent to the BCM at 5342 and goes idle at 5344. If a rejection message (indicating that the test is completed, the tone has been removed and echo suppression on) is received at 5346, the COT timer stops at 5348. Message indicating rejection sends to the BCM in 5350 and goes into idle in 5352.

Giant. 32A-32B show the mux / echo release process. The mux / echo release process is idle at 5360 (Fig. 32A). The release request message is received at 5362 and the message is sent to the mux at 5364. The mux timer is started at 5366 and awaits a response at 5368. If the mux timer expires at 5370, maintenance is notified at 5372 and the mux message is sent again at 5374 At 5376 (Fig. 32B), the mux timer is restarted and awaits a response at 5380.

The mux response is determined at 5382. If it is rejected, maintenance is notified at 5384. The circuit is marked as blocked at 5386 in the trunk circuit table and a message is sent at 5388 to the blocking process. It goes idle at 5390. If the message is an accept message at 5382, the circuit is marked idle at 5392 and goes idle at 5394. If a message from mux

If I accept it at 5396, the mux response is determined at 5398. If it is refused, the maintenance at 5400 is notified. The circuit is marked in the trunk circuit table as blocked at 5402 and a message at 5404 is sent to the blocking process. It goes idle at 5406. If the accept message is at 5398, the circuit is marked idle at 5408 and goes idle at 5410.

It will be apparent to those skilled in the art that many variations of the above-described description may be included within the scope of the invention. As such, the invention should be measured by the scope and wording of the following claims.

Claims (11)

PATENT CLAIMS 1. Telecommunications Signaling Processor that Signaling System Signaling Telecommunications # 7 (SS7) 5 for selecting asynchronous transfer mode (ATM) virtual connections and providing control messages that indicate a selected ATM virtual connection, comprising: a computer system that is operative to store data structures and execute stored logic; 10 is a call control data structure that is stored in a computer system and that includes information relevant to each call; circuit data, which is stored in the computer system and which contains relevant information 15 by telecommunications; the exception data structure that is stored on the computer system and which contains information related to call routing exceptions; caller number data structure to be stored in 20 May computer system and which contains caller numbers; information respectively Data structure of dialed numbers which is keeps in a computer system and which contains dialed numbers; information respectively 25 routing data structure that is stored in computer system and which contains call routing selections; information respectively logic of the initial process, which is stored in a computer system operable to process the information from the 30 SS7 signaling messages relating to the start circuit and to enter the data structures to request a terminal ATM virtual connection; and end-process logic, which is stored in a computer system and is operative to process information from: • re * us-aeJA ·· SS7 signaling messages to select the terminal ATM virtual connection in response to a request from the initial process. Signal processor according to claim 1, characterized in that the 5 computer system is located outside the telecommunications switch. 3. The signal processor of claim 1, further comprising a treatment data structure that is stored in the computer system and which includes 10 by treating calls that are not routed. 4. The signal processor of claim 1, further comprising a query data structure that is stored in the computer system and which includes 15 queries for additional call processing. A telecommunication signal processor (400), comprising: a signaling means (410) for receiving an initial 20 address (IAM) message; application means (430) for processing an initial address to select an identifier for asynchronous communication; and control means (420) for transmitting a control message 25 indicating the selected identifier. * t * The telecommunication signal processor of claim 5, wherein the application means comprises: a connection means (500, 502) for storing data about the 5 connections; exception means (504) for storing exception data, wherein the junction means points to an exception means; caller number means (506) for storing caller number data, wherein the exception means points to 10 means the caller's number; dialed number means (508) for storing dialed number data, wherein the exception means and the caller number means point to the dialed number means; a routing means (510) for storing routing data, 15 wherein the exception means, the caller number means and the called number means point to the routing means, and wherein the exception means, the caller number means, the called number means and the routing means point to the connection means, 7. The telecommunication signal processor of claim 6, wherein the application means is for proceeding from the connection means to the exception means, from the exception means to the caller number means, from the caller means to the called number means, from the called number means to the routing means. and from the routing means back to the connection means to select an identifier. 30 The telecommunication signal processor of claim 5, wherein the application means is for generating an echo control message. ·· ··· ··· ··· ·· ·· A method of operating a telecommunications signaling processor (400), comprising the steps of: receiving the start address message; 5 processing an initial address message to select an identifier for asynchronous communication; and transmitting a control message indicating the selected identifier. 10. The method of claim 9, wherein processing the start address message comprises the steps of: progress from link data to exception data; progress from exception data to caller number data; progress from caller data to called party data 15 numbers; progress from dialed data to routing data; and progress from routing data back to connection data. The method of claim 9, wherein processing the start address message 20 comprises selecting an echo control.