Voice over data telecommunications network architecture

[0001] This application is a continuation of U.S. patent application Ser. No. 10/366,061, entitled “Voice Over Data Telecommunications Network Architecture,” filed Feb. 12, 2003, which is a continuation of U.S. patent application Ser. No. 09/197,203 (now U.S. Pat. No. 6,614,781), entitled “Voice Over Data Telecommunications Network Architecture,” filed Nov. 20, 1998. This application of common assignee contains a related disclosure to U.S. Pat. No. 6,442,169, entitled “System and Method for Bypassing Data From Egress Facilities.” Both U.S. patent application Ser. No. 09/197,203 and U.S. Pat. No. 6,442,169 are incorporated herein by reference in their entirety. In addition, this application is related to applications identified by U.S. patent application Ser. No. 11/781,098) and U.S. patent application Ser. No. 11/781,118, having common title and assignee, and filed on even date herewith.

[0002] 1. Field of the Invention

[0003] The present invention relates generally to telecommunications networks and, more particularly, to a system and method for providing transmission for voice and data traffic over a data network, including the signaling, routing and manipulation of such traffic.

[0004] 2. Related Art

[0005] The present invention relates to telecommunications, and in particular to voice and data communication operating over a data network. The Public Switched Telephone Network (PSTN) is a collection of different telephone networks owned by different companies which have for many years provided telephone communication between users of the network. Different parts of the PSTN network use different transmission media and compression techniques.

[0006] Most long distance calls are digitally coded and transmitted along a transmission line such as a T1 line or fiber optic cable, using circuit switching technology to transmit the calls. Such calls are time division multiplexed (TDM) into separate channels, which allow many calls to pass over the lines without interacting. The channels are directed independently through multiple circuit switches from an originating switch to a destination switch. Using conventional circuit switched communications, a channel on each of the T1 lines along which a call is transmitted is dedicated for the duration of the call, whether or not any information is actually being transmitted over the channel. The set of channels being used by the call is referred to as a “circuit.”

[0007] Telecommunications networks were originally designed to connect one device, such as a telephone, to another device, such as a telephone, using switching services. As previously mentioned, circuit-switched networks provide a dedicated, fixed amount of capacity (a “circuit”) between the two devices for the entire duration of a transmission session. Originally, this was accomplished manually. A human operator would physically patch a wire between two sockets to form a direct connection from the calling party to the called party. More recently, a circuit is set up between an originating switch and a destination switch using a process known as signaling.

[0008] Signaling sets up, monitors, and releases connections in a circuit-switched system. Various signaling methods have been devised. Telephone systems formerly used in-band signaling to set up and tear down calls. Signals of an in-band signaling system are passed through the same channels as the information being transmitted. Early electromechanical switches used analog or multi-frequency (MF) in-band signaling. Thereafter, conventional residential telephones used in-band dual-tone multiple frequency (DTMF) signaling to connect to an end office switch. Here, the same wires (and frequencies on the wires) were used to dial a number (using pulses or tones), as are used to transmit voice information. However, in-band signaling permitted unscrupulous callers to use a device such as a whistle to mimic signaling sounds to commit fraud (e.g., to prematurely discontinue billing by an interexchange carrier (IXC), also known as a long distance telephone company).

[0009] More recently, to prevent such fraud, out-of-band signaling systems were introduced. Out-of-band signaling uses a signaling network that is separate from the circuit switched network used for carrying the actual call information. For example, integrated services digital network (ISDN) uses a separate channel, a data (D) channel, to pass signaling information out-of-band. Common Channel Interoffice Signaling (CCIS) is another network architecture for out-of-band signaling. A popular version of CCIS signaling is Signaling System 7 (SS7). SS7 is an internationally recognized system optimized for use in digital telecommunications networks.

[0010] SS7 out-of-band signaling provided additional benefits beyond fraud prevention. For example, out-of-band signaling eased quick adoption of advanced features (e.g., caller id) by permitting modifications to the separate signaling network. In addition, the SS7 network enabled long distance “Equal Access” (i.e., 1+ dialing for access to any long distance carrier) as required under the terms of the modified final judgment (MFJ) requiring divestiture of the Regional Bell Operating Companies (RBOCs) from their parent company, AT&T.

[0011] An SS7 network is a packet-switched signaling network formed from a variety of components, including Service Switching Points (SSPs), Signaling Transfer Points (STPs) and Service Control Points (SCPs). An SSP is a telephone switch which is directly connected to an SS7 network. All calls must originate in or be routed through an SSP. Calls are passed through connections between SSPs. An SCP is a special application computer which maintains information in a database required by users of the network. SCP databases may include, for example, a credit card database for verifying charge information or an “800” database for processing number translations for toll-free calls. STPs pass or route signals between SSPs, other STPs, and SCPs. An STP is a special application packet switch which operates to pass signaling information.

[0012] The components in the SS7 network are connected together by links. Links between SSPs and STPs can be, for example, A, B, C, D, E or F links. Typically, redundant links are also used for connecting an SSP to its adjacent STPs. Customer premises equipment (CPE), such as a telephone, are connected to an SSP or an end office (EO) switch.

[0013] To initiate a call in an SS7 telecommunications network, a calling party using a telephone connected to an originating EO switch, dials a telephone number of a called party. The telephone number is passed from the telephone to the SSP at the originating EO (referred to as the “ingress EO”) of the calling party's local exchange carrier (LEC). A LEC is commonly referred to as a local telephone company. First, the SSP will process triggers and internal route rules based on satisfaction of certain criteria. Second, the SSP will initiate further signaling messages to another EO or access tandem (AT), if necessary. The signaling information can be passed from the SSP to STPs, which route the signals between the ingress EO and the terminating end office, or egress EO. The egress EO has a port designated by the telephone number of the called party. The call is set up as a direct connection between the EOs through tandem switches if no direct trunking exists or if direct trunking is full. If the call is a long distance call, i.e., between a calling party and a called party located in different local access transport areas (LATAs), then the call is connected through an inter exchange carrier (IXC) switch of any of a number of long distance telephone companies. Such a long distance call is commonly referred to as an inter-LATA call. LECs and IXCs are collectively referred to as the previously mentioned public switched telephone network (PSTN).

[0014] Emergence of competitive LECs (CLECs) was facilitated by passage of the Telecommunications Act of 1996, which authorized competition in the local phone service market. Traditional LECs or RBOCs are now also known as incumbent LECs (ILECs). Thus, CLECs compete with ILECs in providing local exchange services. This competition, however, has still not provided the bandwidth necessary to handle the large volume of voice and data communications. This is due to the limitations of circuit switching technology which limits the bandwidth of the equipment being used by the LECs, and to the high costs of adding additional equipment.

[0015] Since circuit switching dedicates a channel to a call for the duration of the call, a large amount of switching bandwidth is required to handle the high volume of voice calls. This problem is exacerbated by the fact that the LECs must also handle data communications over the same equipment that handle voice communications.

[0016] If the PSTN were converted to a packet-switched network, many of the congestion and limited bandwidth problems would be solved. However, the LECs and IXCs have invested large amounts of capital in building, upgrading and maintaining their circuit switched networks (known as “legacy” networks) and are unable or unwilling to jettison their legacy networks in favor of the newer, more powerful technology of packet switching. Accordingly, a party wanting to build a packet-switched network to provide voice and data communications for customers must build a network that, not only provides the desired functionality, but also is fully compatible with the SS7 and other, e.g., ISDN and MF, switching networks of the legacy systems.

[0017] Currently, internets, intranets, and similar public or private data networks that interconnect computers generally use packet switching technology. Packet switching provides for more efficient use of a communication channel as compared to circuit switching. With packet switching, many different calls (e.g., voice, data, video, fax, Internet, etc.) can share a communication channel rather than the channel being dedicated to a single call. For example, during a voice call, digitized voice information might be transferred between the callers only 50% of the time, with the other 50% being silence. For a data call, information might be transferred between two computers 10% of the time. With a circuit switched connection, the voice call would tie-up a communications channel that may have 50% of its bandwidth being unused. Similarly, with the data call, 90% of the channel's bandwidth may go unused. In contrast, a packet-switched connection would permit the voice call, the data call and possibly other call information to all be sent over the same channel.

[0018] Packet switching breaks a media stream into pieces known as, for example, packets, cells or frames. Each packet is then encoded with address information for delivery to the proper destination and is sent through the network. The packets are received at the destination and the media stream is reassembled into its original form for delivery to the recipient. This process is made possible using an important family of communications protocols, commonly called the Internet Protocol (IP).

[0019] In a packet-switched network, there is no single, unbroken physical connection between sender and receiver. The packets from many different calls share network bandwidth with other transmissions. The packets are sent over many different routes at the same time toward the destination, and then are reassembled at the receiving end. The result is much more efficient use of a telecommunications network than could be achieved with circuit-switching.

[0020] Recognizing the inherent efficiency of packet-switched data networks such as the Internet, attention has focused on the transmission of voice information over packet-switched networks. However, such systems are not compatible with the legacy PSTN and therefore are not convenient to use.

[0021] One approach that implements voice communications over an IP network requires that a person dial a special access number to access an IP network. Once the IP network is accessed, the destination or called number can be dialed. This type of call is known as a gateway-type access call.

[0022] Another approach involves a user having a telephone that is dedicated to an IP network. This approach is inflexible since calls can only be made over the IP network without direct access to the PSTN.

[0023] What is needed is a system and method for implementing packet-switched communications for both voice calls and data calls that do not require special access numbers or dedicated phones and permit full integration with the legacy PSTN.

[0024] The present invention is a system and method for communicating both voice and data over a packet-switched network that is adapted to coexist and communicate with a PSTN. The system permits efficient packet switching of voice calls and data calls from a PSTN carrier such as, for example, a LEC, IXC, a customer facility or a direct IP connection on the data network to any other LEC, IXC, customer facility or direct IP connection. For calls from a PSTN carrier, e.g., LEC or IXC, the invention receives signaling from the legacy SS7 signaling network or the ISDN D-channel or from inband signaling trunks. For calls from a customer facility, data channel signaling or inband signaling is received. For calls from a direct IP connection on the data network, signaling messages can travel over the data network. On the call destination side, similar signaling schemes are used depending on whether the called party is on a PSTN carrier, a customer facility or a direct IP connection to the data network.

[0025] The system includes soft switch sites, gateway sites, a data network, a provisioning component a network event component and a network management component. The system of the invention interfaces with customer facilities (e.g., a PBX), carrier facilities (e.g., a PSTN carrier, a LEC (e.g., LECs and CLECs), an independent telephone company (ITC), an IXC, an intelligent peripheral or an enhanced service provider (ESP)) and legacy signaling networks (e.g., SS7) to handle calls between any combination of on-network and off-network callers.

[0026] The soft switch sites provide the core call processing for the voice network architecture. Each soft switch site can process multiple types of calls including calls originating from or terminating at off-network customer facilities as well as calls originating from or terminating at on-network customer facilities. Each soft switch site receives signaling messages from and sends signaling messages to the signaling network. The signaling messages can include, for example, SS7, integrated services digital network (ISDN) primary rate interface (PRI) and in-band signaling messages. Each soft switch site processes these signaling messages for the purpose of establishing new calls through the data network and tearing down existing calls and in-progress call control functions. Signaling messages can be transmitted between any combination of on-network and off-network callers.

[0027] Signaling messages for a call which either originates off-network or terminates off-network can be carried over the out-of-band signaling network of the PSTN via the soft switch sites. Signaling messages for a call which both originates on-network and terminates on-network can be carried over the data network rather than through the signaling network.

[0028] The gateway sites originate and terminate calls between calling parties and called parties through the data network. The soft switch sites control or manage the gateway sites. In a preferred embodiment, the soft switch sites use a protocol such as, for example, the Internet Protocol Device Control (IPDC) protocol, to manage network access devices in the gateway sites to request the set-up and tear-down of calls. However, other protocols could be used, including, for example, network access server messaging interface (NMI) and the ITU media gateway control protocol (MGCP).

[0029] The gateway sites can also include network access devices to provide access to network resources (i.e., the communication channels or circuits that provide the bandwidth of the data network). The network access devices can be referred to generally as access servers or media gateways. Exemplary access servers or media gateways are trunking gateways (TGs), access gateways (AGs) and network access servers (NASs). The gateway sites provide for transmission of both voice and data traffic through the data network. The gateway sites also provide connectivity to other telecommunications carriers via trunk interfaces to carrier facilities for the handling of voice calls. The trunk interfaces can also be used for the termination of dial-up modem data calls. The gateway sites can also provide connectivity via private lines and dedicated access lines (DALs), such as T1 or ISDN PRI facilities, to customer facilities.

[0030] The data network connects one or more of the soft switch sites to one or more of the gateway sites. The data network routes data packets through routing devices (e.g., routers) to destination sites (e.g., gateway sites and soft switch sites) on the data network. For example, the data network routes internet protocol (IP) packets for transmission of voice and data traffic from a first gateway site to a second gateway site. The data network represents any art-recognized data network including the global Internet, a private intranet or internet a frame relay network, and an asynchronous transfer mode (ATM) network.

[0031] The network event component collects call events recorded at the soft switch sites. Call event records can be used, for example, for fraud detection and prevention, and billing.

[0032] The provisioning event component receives provisioning requests from upstream operational support services (OSS) systems such as, for example, for order-entry, customer service and customer profile changes. The provisioning component distributes provisioning data to appropriate network elements and maintains data synchronization, consistency, and integrity across multiple soft switch sites.

[0033] The network management component includes a network operations center (NOC) for centralized network management. Each network element (NE) (e.g., soft switch sites, gateway sites, provisioning, and network event components, etc.) generates simple network management protocol (SNMP) events or alerts. The NOC uses the events generated by each network element to determine the health of the network and to perform other network management functions.

[0034] In a preferred embodiment, the invention operates as follows to process, for example, a long distance call (also known as a 1+ call). First, a soft switch site receives an incoming call signaling message from the signaling network. The soft switch site determines the type of call by performing initial digit analysis on the dialed number. Based upon the information in the signaling message, the soft switch site analyzes the initial digit of the dialed number of the call and determines that it is a 1+ call. The soft switch site then queries a customer profile database to retrieve the originating trigger plan associated with the calling customer. The query can be made using, for example, the calling party number provided in the signaling message from the signaling network. This look-up in the customer profile database returns subscription information. For example, the customer profile may indicate that the calling party has subscribed to an account code verification feature that requires entry of an account code before completion of the call. In this case, the soft switch site will instruct the gateway site to collect the account code digits entered by the calling party. Assuming that the gateway site collects the correct number of digits, the soft switch site can use the customer profile to determine how to process the received digits. For account code verification, the soft switch site verifies the validity of the received digits.

[0035] Verification can result in the need to enforce a restriction, such as a class of service (COS) restriction (CO SR). In this example, the soft switch site can verify that the account code is valid, but that it requires that an intrastate COSR should be enforced. This means that the call is required to be an intrastate call to be valid. The class of service restriction logic can be performed within the soft switch site using, for example, pre-loaded local access and transport areas (LATAs) and state tables. The soft switch would then allow the call to proceed if the class of service requested matches the authorized class of service. For example, if the LATA and state tables show that the LATA of the originating party and the LATA of the terminating party are in the same state, then the call can be allowed to proceed. The soft switch site then completes customer service processing and prepares to terminate the call. At this point, the soft switch site has finished executing all customer service logic and has a 10-digit dialed number that must be terminated. To accomplish the termination, the soft switch site determines the terminating gateway. The dialed number (i.e., the number of the called party dialed by the calling party) is used to select a termination on the data network. This termination may be selected based on various performance, availability or cost criteria. The soft switch site then communicates with a second soft switch site associated with the called party to request that the second soft switch site allocate a terminating circuit or trunk group in a gateway site associated with the called party. One of the two soft switch sites can then indicate to the other the connections that the second soft switch site must make to connect the call. The two soft switch sites then instruct the two gateway sites to make the appropriate connections to set up the call. The soft switch sites send messages to the gateway sites through the data network using, for example, IPDC protocol commands. Alternately, a single soft switch can set up both the origination and termination.

[0036] The present invention provides a number of important features and advantages. First, the invention uses application logic to identify and direct incoming data calls straight to a terminating device. This permits data calls to completely bypass the egress end office switch of a LEC. This results in significant cost savings for an entity such as an internet service provider (ISP), ILEC, or CLEC. This decrease in cost results partially from bypass of the egress ILEC end office switch for data traffic.

[0037] A further advantage for ISPs is that they are provided data in the digital form used by data networks (e.g., IP data packets), rather than the digital signals conventionally used by switched voice networks (e.g., PPP signals). Consequently, the ISPs need not perform costly modem conversion processes that would otherwise be necessary. The elimination of many telecommunications processes frees up the functions that ISPs, themselves, would have to perform to provide Internet access.

[0038] Another advantage of the present invention is that voice traffic can be transmitted transparently over a packet-switched data network to a destination on the PSTN.

[0039] Yet another advantage of the invention is that a very large number of modem calls can be passed over a single channel of the data network, including calls carrying media such as voice, bursty data, fax, audio, video, or any other data formats.

[0040] Further features and advantages of the invention, as well as the structure and operation of various embodiments of the invention, are described in detail below with reference to the accompanying figures.

[0175] In the figures, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The figure in which an element first appears is indicated by the leftmost digit(s) in the reference number.

[0176]

Detailed Description of the Preferred Embodiments
Table of Contents
I.	High level description
	A.	Structural description
	1.	Soft Switch Sites
	2.	Gateway Sites
	3.	Data Network
	4.	Signaling Network
	5.	Network Event Component
	6.	Provisioning Component
	7.	Network Management Component
	B.	Operational description
II.	Intermediate Level Description
	A.	Structural Description
	1.	Soft Switch Site
	a.	Soft Switch
	b.	SS7 Gateway
	c.	Signal Transfer Points (STPs)
	d.	Services Control Points (SCPs)
	e.	Configuration Server (CS) or Configuration Database
		(CDB)
	f.	Route Server
	g.	Regional Network Event Collection Point (RNECP)
	2.	Gateway Site
	a.	Trunking Gateway (TG)
	b.	Access Gateway (AG)
	c.	Network Access Server (NAS)
	d.	Digital Cross-Connect System (DACS)
	e.	Announcement Server (ANS)
	3.	Data Network
	a.	Routers
	b.	Local Area Networks (LANs) and Wide Area
		Networks (WANs)
	c.	Network Protocols
	4.	Signaling Network
	a.	Signal Transfer Points (STPs)
	b.	Service Switching Points (SSPs)
	c.	Services Control Points (SCPs)
	5.	Provisioning Component and Network Event Component
	a.	Data Distributor
	6.	Provisioning Component and Network Event Component
	a.	Master Network Event Database
	7.	Network management component
	B.	Operational Description
III.	Specific Implementation Example Embodiments
	A.	Structural description
	1.	Soft Switch Site
	a.	Soft Switch
	(1)	Soft Switch Interfaces
	b.	SS7 Gateway
	(1)	SS7 Gateway Example Embodiment
	(2)	SS7 Gateway-to-Soft Switch Interface
	c.	Signal Transfer Points (STPs)
	(1)	STP Example Embodiment
	(a)	Global Title Translation
	(b)	Gateway Screening Software
	(c)	Local Number Portability (LNP)
	(d)	STP to LAN Interface
	(e)	ANSI to ITU Gateway
	d.	Services Control Points (SCPs)
	(1)	Additional Services Calls
	(2)	Project Account Codes
	(3)	Basic Toll-Free
	e.	Configuration Server (CS) or Configuration Database
		(CDB)
	f.	Route Server
	(1)	Route Server Routing Logic
	(2)	Route Server Circuit Management
	g.	Regional Network Event Collection Point (RNECP)
	(1)	Example Mandatory Event Blocks EBs
	(2)	Augmenting Event Blocks EBs
	h.	Software Object Oriented Programming (OOPs) Class
		Definitions
	(1)	Introduction to Object Oriented Programming
		(OOP)
	(2)	Software Objects in an OOP Environment
	(3)	Class Definitions
	(a)	Soft Switch Class
	(b)	Call Context Class
	(c)	Signaling Message Class
	(d)	SS7 Gateway Class
	(e)	IPDC Message Class
	(f)	Call Event Identifier Class
	(g)	Configuration Proxy Class
	(h)	Route Server Class
	(i)	Route Objects Class
	(j)	Pool Class
	(k)	Circuit Pool Class
	2.	Gateway Site
	a.	Trunking Gateway (TG)
	(1)	Trunking Gateway Interfaces
	b.	Access Gateway (AG)
	(1)	Access Gateway Interfaces
	c.	Network Access Server (NAS)
	(1)	Network Access Server Interfaces
	d.	Digital Cross-Connect System (DACS)
	e.	Announcement Server (ANS)
	3.	Data Network
	a.	Routers
	b.	Local Area Networks (LANs) and Wide Area
		Networks (WANs)
	c.	Network Protocols
	(1)	Transmission Control Protocol/Internet
		Protocol (TCP/IP)
	(2)	Internet Protocol (IP)v4 and IPv6
	(3)	Resource Reservation Protocol (RSVP)
	(4)	Real-time Transport Protocol (RTP)
	(5)	IP Multi-Casting Protocols
	d.	Virtual Private Networks (VPNs)
	(1)	VPN Protocols
	(a)	Point-to-Point Tunneling
		Protocol (PPTP)
	(b)	Layer 2 Forwarding (L2F) Protocol
	(c)	Layer 2 Tunneling Protocol (L2TP)
	e.	Exemplary Data Networks
	(1)	Asynchronous Transfer Mode (ATM)
	(2)	Frame Relay
	(3)	Internet Protocol (IP)
	4.	Signaling Network
	a.	Signal Transfer Points (STPs)
	b.	Service Switching Points (SSPs)
	c.	Services Control Points (SCPs)
	5.	Provisioning Component and Network Event Component
	a.	Data Distributor
	(1)	Data Distributor Interfaces
	6.	Provisioning Component and Network Event Component
	a.	Master Network Event Database
	(1)	MNEDB Interfaces
	(2)	Event Block Definitions
	(a)	Example Mandatory Event
		Blocks (EBs) Definitions
	(b)	Example Augmenting Event Block
		(EBs) Definitions
	(3)	Example Element Definitions
	(4)	Element Definitions
	7.	Network management component
	a.	Network operations center (NOC)
	b.	Simple Network Management Protocol (SNMP)
	c.	Network Outage Recovery Scenarios
	(1)	Complete Gateway Site Outage
	(2)	Soft Switch Fail-Over
	(3)	Complete Soft Switch Site Outage Scenario
	8.	Internet Protocol Device Control (IPDC) Protocol
	a.	IPDC Base Protocol
	b.	IPDC Control Protocol
	c.	IPDC Control Message Codes
	d.	A Detailed View of the IPDC Protocol Control
		Messages
	(1)	Startup Messages
	(2)	Protocol Error Messages
	(3)	System Configuration Messages
	(4)	Telephone Company Interface Configuration
		Messages
	(5)	Soft Switch Configuration Messages
	(6)	Maintenance-Status Messages
	(7)	Continuity Test Messages
	(8)	Keepalive Test Messages
	(9)	LAN Test Messages
	(10)	Tone Function Messages
	(11)	Example Source Port Types
	(12)	Example Internal Resource Types
	(13)	Example Destination Port Types
	(14)	Call Control Messages
	(15)	Example Port Definitions
	(16)	Call Clearing Messages
	(17)	Event Notification Messages
	(18)	Tunneled Signaling Messages
	e.	Control Message Parameters
	f.	A Detailed View of the Flow of Control Messages
	(1)	Startup Flow
	(2)	Module Status Notification Flow
	(3)	Line Status Notification Flow
	(4)	Blocking of Channels Flow
	(5)	Unblocking of Channels Flow
	(6)	Keepalive Test Flow
	(7)	Reset Request Flow
	g.	Call Flows
	(1)	Data Services
	(a)	Inbound Data Call via SS7
		Signaling Flow
	(b)	Inbound Data Call via Access Server
		Signaling Flow
	(c)	Inbound Data Call via SS7 Signaling
		(with call-back)
	(d)	Inbound Data Call (with loopback
		continuity testing) Flow
	(e)	Outbound Data Call Flow via SS7
		Signaling
	(f)	Outbound Data Call Flow via Access
		Server Signaling
	(g)	Outbound Data Call Flow Initiated from
		the Access Server with continuity
		testing
	(2)	TDM Switching Setup Connection Flow
	(a)	Basic TDM Interaction Sequence
	(b)	Routing of calls to Appropriate Access
		Server using TDM connections Flow
	(3)	Voice Services
	(a)	Voice over Packet Services Call Flow
		(Inbound SS7 signaling, Outbound
		access server signaling, Soft
		Switch managed RTP ports)
	(b)	Voice over Packet Call Flow (Inbound
		access server signaling, Outbound
		access server signaling, Soft
		switch managed RTP ports)
	(c)	Voice over Packet Call Flow (Inbound
		SS7 signaling, outbound SS7
		signaling, IP network with access
		server managed RTP ports)
	(d)	Unattended Call Transfers Call Flow
	(e)	Attended Call Transfer Call Flow
	(f)	Call termination with a message
		announcement Call Flow
	(g)	Wiretap
	B.	Operational description
	1.	Voice Call originating and terminating via
		SS7 signaling on a Trunking Gateway
	a.	Voice Call on a TG Sequence Diagrams of Component
		Intercommunication
	2.	Data Call originating on an SS7 trunk on
		a Trunking Gateway
	3.	Voice Call originating on an SS7 trunk on a Trunking
		Gateway and terminating via access server signaling on an
		Access Gateway
	4.	Voice Call originating on an SS7 trunk on a Trunking
		Gateway and terminating on an Announcement Server
	5.	Voice Call originating on an SS7 trunk on a
		Network Access Server and terminating on a
		Trunking Gateway via SS7 signaling
	a.	Voice Call on a NAS Sequence Diagrams of
		Component Intercommunication
	6.	Voice Call originating on an SS7 trunk on a NAS and
		terminating via Access Server Signaling on an
		Access Gateway
	7.	Data Call originating on an SS7 trunk and terminating on a
		NAS
	a.	Data Call on a NAS Sequence Diagrams of
		Component intercommunication
	8.	Data Call on NAS with Callback outbound reorigination
	9.	Voice Call originating on Access Server dedicated
		line on an Access Gateway and terminating on an
		Access Server dedicated line on an Access Gateway
	10.	Voice Call originating on Access Server signaled
		private line on an Access Gateway and terminating on SS7
		signaled trunks on a Trunking Gateway
	11.	Data Call on an Access Gateway
	12.	Outbound Data Call from a NAS via Access Server
		signaling from an Access Gateway
	13.	Voice Services
	a.	Private Voice Network (PVN) Service
	b.	1+ Long Distance Service
	(1)	Project Account Codes (PAC)
	(a)	PAC Variations
	(2)	Class of Service Restrictions (COSR)
	(3)	Origination and Termination
	(4)	Call Rating
	(5)	Multiple Service T-1
	(6)	Monthly Recurring Charges (MRCs)
	(7)	PVN Private Dialing Plan
	(8)	Three-Way Conferencing
	(9)	Network Hold with Message Delivery
	c.	8XX Toll Free Services
	(1)	Enhanced Routing Features
	(2)	Info-Digit Blocking
	(3)	Toll-Free Number Portability (TFNP)
	(4)	Multiple-Server T-1
	(5)	Call Rating
	(6)	Project Accounting Codes
	(7)	Toll-Free Directory Listings
	(8)	Menu Routing
	(9)	Network ACD
	(10)	Network Transfer (TBX)
	(11)	Quota Routing
	(12)	Toll-Free Valet (Call Park)
	d.	Operator Services
	(1)	Domestic Operator Services
	(a)	Operator Services Features
	(2)	International Operator Services
	e.	Calling Card Services
	(1)	Calling Card Features
	(2)	Call Rating
	f.	One-Number Services
	(1)	One Number Features
	g.	Debit Card/Credit Card Call Services
	h.	Local Services
	(1)	Local Voice/Dial Tone (LV/DT)
	(2)	Call Handling Features
	(a)	Line Hunting
	(b)	Call Forward Busy
	(c)	Call Forwarding Don't Answer
	(d)	Call Forward Variable
	(e)	Call Hold
	(f)	Three-Way Calling
	(g)	Call Transfer
	(h)	Call Waiting/Cancel Call Waiting
	(i)	Extension or Station-to-Station Calling
	(j)	Direct Connect Hotline/Ring Down
		Line
	(k)	Message Waiting Indicator
	(l)	Distinctive Ringing
	(m)	Six-Way Conference Calling
	(n)	Speed Calling
	(o)	Selective Call Rejection
	(p)	Remote Activation of Call Forward
		Variable
	(3)	Enhanced Services
	(a)	Remote Call Forward (RCF)
	(b)	Voice Messaging Services
	(c)	Integrated Voice Messaging
	(d)	Stand-alone Voice Messaging
	(4)	Class Services
	(5)	Class of Service Restrictions
		(b) Local Voice/Local Calling (LV/LC)
	i.	Conferencing Services
	(1)	Audio Conferencing
	(a)	Audio conferencing features
	(2)	Video Conferencing
	14.	Data Services
	a.	Internet Hosting
	b.	Managed Modem Services
	c.	Collocation Services
	d.	IP network Services
	e.	Legacy Protocol Services - Systems Network
		Architecture (SNA)
	f.	Permanent Virtual Circuits
	15.	Additional Products and Services
IV.	Definitions
V.	Conclusion

I. High Level Description

[0177] This section provides a high-level description of the voice over IP network architecture according to the present invention. In particular, a structural implementation of the voice over IP (VOIP) network architecture is described at a high-level. Also, a functional implementation for this structure is described at a high-level. This structural implementation is described herein for illustrative purposes, and is not limiting. In particular, the process described in this section can be achieved using any number of structural implementations, one of which is described in this section. The details of such structural implementations will be apparent to persons skilled in the relevant arts based on the teachings contained herein.

[0178] A. Structural Description

[0179] FIG. 1 is a block diagram 100 illustrating the components of the VOIP architecture at a high-level. FIG. 1 includes soft switch sites 104, 106, gateway sites 108, 110, data network 112, signaling network 114, network event component 116, provisioning component 117 and network management component 118.

[0180] Included in FIG. 1 are calling parties 102, 122 and called parties 120, 124. Calling parties 102, 122 are homed to gateway site 108. Calling parties 102, 122 are homed to gateway site 108. Called parties 120, 124 are homed to gateway site 110. Calling party 102 can be connected to gateway site 108 via trunks from carrier facility 126 to gateway site 108. Similarly, called party 120 can be connected to gateway site 110 via trunks from carrier facility 130 to gateway site 110. Calling party 122 can be connected to gateway site 108 via a private line or dedicated access line (DAL) from customer facility 128 to gateway site 108. Similarly, called party 124 can be connected to gateway site 110 via a private line or a DAL from customer facility 132 to gateway site 110.

[0181] Calling party 102 and called party 120 are off-network, meaning that they are connected to gateway sites 108, 110 via the Public Switched Telephone Network (PSTN) facilities. Calling party 122 and called party 124 are on-network, meaning that connect to gateway sites 108, 110 as direct customers.

[0182] 1. Soft Switch Sites

[0183] Soft switch sites 104, 106 provide the core call processing for the voice network architecture. Soft switch sites 104, 106 can process multiple types of calls. First, soft switch sites 104, 106 can process calls originating from or terminating at on-network customer facilities 128, 132. Second, soft switch sites 104, 106 can process calls originating from or terminating at off-network customer facilities 126, 130.

[0184] Soft switch sites 104, 106 receive signaling messages from and send signaling messages to signaling network 114. For example, these signaling messages can include SS7, primary rate interface (PRI) and in-band signaling messages. Soft switch sites 104, 106 process these signaling messages for the purpose of establishing new calls from calling parties 102, 122 through data network 112 to called parties 120, 124. Soft switch sites 104, 106 also process these signaling messages for the purpose of tearing down existing calls established between calling parties 102, 122 and called parties 120, 124 (through data network 112).

[0185] Calls can be transmitted between any combination of on-network and off-network callers.

[0186] In one embodiment, signaling messages for a call which either originates from an off-network calling party 102, or terminates to an off-network called party 120, can be carried over out-of-band signaling network 114 from the PSTN to soft switches 104, 106.

[0187] In another embodiment, signaling messages for a call which either originates from an on-network calling party 122, or terminates to on-network called party 124, can be carried in-band over data network 112 or over a separate data network to soft switch sites 104, 106, rather than through signaling network 114.

[0188] Soft switch sites 104, 106 can be collocated or geographically diverse. Soft switch sites 104, 106 can also be connected by redundant connections to data network 112 to enable communication between soft switches 104, 106.

[0189] Soft switch sites 104, 106 use other voice network components to assist with the processing of calls. For example, gateway sites 108, 110 provide the means to originate and terminate calls on the PSTN. In a preferred embodiment, soft switch sites 104, 106 use the Internet Protocol Device Control (IPDC) protocol to control network access devices known as media gateways in gateway sites 108, 110, and to request, for example, the set-up and tear-down of calls. The IPDC protocol is described below with reference to Tables 144-185. Alternatively, any protocol understood by those skilled in the art can be used to control gateway sites 108, 110. One example of an alternative protocol is the Network Access Server (NAS) Messaging Interface (NMI) Protocol, discussed in U.S. patent application entitled “System and Method for Bypassing Data from Egress Facilities”, filed concurrently herewith, application Ser. No. 09/196,756 , the contents of which are incorporated herein by reference in their entirety. Another example of a protocol is the Media Gateway Control Protocol (MGCP) from the Internet Engineering Task Force (IETF).

[0190] Soft switch sites 104, 106 can include other network components such as a soft switch, which more recently can also be known as a media gateway controller, or other network devices.

[0191] 2. Gateway Sites

[0192] Gateway sites 108, 110 provide the means to originate and terminate calls between calling parties 102, 122 and called parties 120, 124 through data network 112. For example, calling party 122 can originate a call terminated to off-network called party 120, which is homed to gateway site 110 via carrier facility 130.

[0193] Gateway sites 108, 110 can include network access devices to provide access to network resources. An example of a network access device is an access server which is more recently commonly known as a media gateway. These devices can include trunking gateways, access gateways and network access servers. Gateway sites 108, 110 provide for transmission of, for example, both voice and data traffic through data network 112.

[0194] Gateway sites 108, 110 are controlled or managed by one or more soft switch sites 104, 106. As noted, soft switch sites 104, 106 can communicate with gateway sites 108, 110 via the IPDC, NMI, MGCP, or alternative protocols.

[0195] Gateway sites 108, 110 can provide trunk interfaces to other telecommunication carriers via carrier facilities 126, 130 for the handling of voice calls. The trunk interfaces can also be used for the termination of dial-up modem data calls. Gateway sites 108, 110 can also provide private lines and dedicated access lines, such as T1 or ISDN PRI facilities, to customer facilities 128, 132. Examples of customer facilities 128, 132 are customer premises equipment (CPE) such as, for example, a private branch exchange (PBX).

[0196] Gateway sites 108, 110 can be collocated or geographically diverse from one another or from other network elements (e.g. soft switch sites 104, 106). Gateway sites 108, 110 can also be connected by redundant connections to data network 112 to enable communication with and management by soft switches 104, 106.

[0197] 3. Data Network

[0198] Data network 112 connects one or more soft switch sites 104, 106 to one or more gateway sites 108, 110. Data Network 112 can provide for routing of data through routing devices to destination sites on data network 112. For example, data network 112 can provide for routing of internet protocol (IP) packets for transmission of voice and data traffic from gateway site 108 to gateway site 110. Data Network 112 represents any art-recognized data network. One well-known data network is the global Internet. Other examples include a private intranet, a packet-switched network, a frame relay network, and an asynchronous transfer mode (ATM) network.

[0199] 4. Signaling Network

[0200] Signaling network 114 is an out-of-band signaling network providing for transmission of signaling messages between the PSTN and soft switch sites 104, 106. For example, signaling network 114 can use Common Channel Interoffice Signaling (CCIS), which is a network architecture for out-of-band signaling. A popular version of CCIS signaling is Signaling System 7 (SS7). SS7 is an internationally recognized system optimized for use in digital telecommunications networks.

[0201] 5. Network Event Component

[0202] Network event component 116 provides for collection of call events recorded at soft switch sites 104, 106. Call event records can be used, for example, for fraud detection and prevention, traffic reporting and billing.

[0203] 6. Provisioning Component

[0204] Provisioning component 117 provides several functions. First, provisioning component 117 receives provisioning requests from upstream operational support services (OSS) systems, for such items as order-entry, customer service, and customer profile changes. Second, provisioning component 117 distributes provisioning data to appropriate network elements. Third, provisioning component 117 maintains data synchronization, consistency, and integrity across multiple soft switch sites 104, 106.

[0205] 7. Network Management Component

[0206] Network management component 118 can include a network operations center (NOC) for centralized network management. Each network element (NE) of block diagram 100 can generate simple network management protocol (SNMP) events or alerts. The NOC uses the events generated by a NE to determine the health of the network, and to perform other network management functions.

[0207] B. Operational Description

[0208] The following operational flows describe an exemplary high level call scenario for soft switch sites 104, 106 and is intended to demonstrate at a high architectural level how soft switch sites 104, 106 process calls. The operational flow of the present invention is not to be viewed as limited to this exemplary illustration.

[0209] As an illustration, FIG. 22A depicts a simple operational call flow chart describing how soft switch sites 104, 106 can process a long distance call, also known as a 1+ call. The operational call flow of FIG. 22A begins with step 2202, in which a soft switch site receives an incoming signaling message. The call starts by soft switch site 104 receiving an incoming signaling message from carrier facility 126 via signaling network 114, indicating an incoming call from calling party 102.

[0210] In step 2204, the soft switch site determines the type of call by performing initial digit analysis. Based upon the information in the signaling message, the soft switch site 104 analyzes the initial digit of the dialed number of the call and determines that it is a 1+ call.

[0211] In step 2222, soft switch site 104 can select a route termination based on the dialed number (i.e., the number of called party 120 dialed by calling party 102) using least cost routing. This route termination can involve termination off data network 112 or off onto another data network. Soft switch site 104 can then communicate with soft switch site 106 to allocate a terminating circuit in gateway site 110 for this call.

[0212] In step 2224, soft switch site 104 can indicate connections to be made to complete the call. Soft switch site 104 or soft switch site 106 can return a termination that indicates the connections that must be made to connect the call.

[0213] In step 2226, soft switch sites 104, 106 instruct the gateway sites to make connections to set up the call. Soft switch sites 104, 106 can send messages through data network 112 (e.g. using IPDC protocol commands) to gateway sites 108, 110, to instruct the gateway sites to make the necessary connections for setting up the call origination from calling party 102, the call termination to called party 120, and the connection between origination and termination.

[0214] In step 2228, soft switch sites 104, 106 generate and send network events to a repository. Soft switch sites 104, 106 can generate and send network events to network event component 116 that are used, for example, in detecting and preventing fraud, and in performing billing.

[0215] In step 2230, network management component 118 monitors the telecommunications network 100. All network elements create network management events such as SNMP protocol alerts or events. Network management component 118 can monitor SNMP events to enable management of network resources.

[0216] FIG. 22B details a more complex operational call flow describing how soft switch sites 104, 106 process a long distance call. FIG. 22B inserts steps 2206, 2208 and 2220 between steps 2204 and 2222 of FIG. 22A.

[0217] The operational call flow of FIG. 22B begins with step 2202, in which a soft switch site receives an incoming signaling message. The call starts by soft switch site 104 receiving an incoming signaling message from carrier facility 126 via signaling network 114, indicating an incoming call from calling party 102.

[0218] In step 2204, the soft switch site determines the type of call by performing initial digit analysis. Based upon the information in the signaling message, the soft switch site 104 analyzes the initial digit of the dialed number of the call and determines that it is a 1+ call.

[0219] In step 2206, the soft switch site queries a customer profile database to retrieve the originating trigger plan associated with the calling customer. With a 1+ type of call, the logic within the soft switch knows to query the customer profile database within soft switch site 104 to retrieve the originating trigger plan for the calling party. The step 2206 query can be made using the calling party number. The customer profile lookup is performed using as the lookup key, the originating number, i.e., the number of calling party 102, provided in the signaling message from signaling network 114.

[0220] In step 2208, the lookup returns subscription information. For example, the customer profile can require entry of an account code. In this example, the customer profile lookup can return an indication that the customer, i.e., calling party 102, has subscribed to an account code verification feature. A class of service restriction can also be enforced, but this will not be known until account code verification identifies an associated account code.

[0221] In step 2220, soft switch site 104 completes customer service processing and prepares to terminate the call. At this point, soft switch site 104 has finished executing all customer service logic and has a 10-digit dialed number that must be terminated.

[0222] In step 2222, soft switch site 104 can select a route termination based on the dialed number (i.e., the number of called party 120 dialed by calling party 102) using least cost routing. This route termination can involve termination off data network 112 or off onto another data network. Soft switch site 104 can then communicate with soft switch site 106 to allocate a terminating circuit in gateway site 110 for this call.

[0223] In step 2224, soft switch site 104 can indicate connections to be made to complete the call. Soft switch site 104 or soft switch site 106 can return a termination that indicates the connections that must be made to connect the call.

[0224] In step 2226, soft switch sites 104, 106 instruct the gateway sites to make connections to set up the call. Soft switch sites 104, 106 can send messages through data network 112 (e.g. using IPDC protocol commands) to gateway sites 108, 110, to instruct the gateway sites to make the necessary connections for setting up the call origination from calling party 102, the call termination to called party 120, and the connection between origination and termination.

[0225] In step 2228, soft switch sites 104, 106 generate and send network events to a repository. Soft switch sites 104, 106 can generate and send network events to network event component 116 that are used, for example, in detecting and preventing fraud, and in performing billing.

[0226] In step 2230, network management component 118 monitors the telecommunications network 100. All network elements create network management events such as SNMP protocol alerts or events. Network management component 118 can monitor SNMP events to enable management of network resources.

[0227] FIG. 22C details an even more complex operational call flow describing how soft switch sites 104, 106 can be used to process a long distance call using project account codes and class of service restrictions. FIG. 22C inserts steps 2210 through 2218 between steps 2208 and 2220 of FIG. 22B.

[0228] The operational call flow of FIG. 22C begins with step 2202, in which a soft switch site receives an incoming signaling message. The call starts by soft switch site 104 receiving an incoming signaling message from carrier facility 126 via signaling network 114, indicating an incoming call from calling party 102.

[0229] In step 2204, the soft switch site determines the type of call by performing initial digit analysis. Based upon the information in the signaling message, the soft switch site 104 analyzes the initial digit of the dialed number of the call and determines that it is a 1+ call.

[0230] In step 2206, the soft switch site queries a customer profile database to retrieve the originating trigger plan associated with the calling customer. With a 1+ type of call, the logic within the soft switch knows to query the customer profile database within soft switch site 104 to retrieve the originating trigger plan for the calling party. The step 2206 query can be made using the calling party number. The customer profile lookup is performed using as the lookup key, the originating number, i.e., the number of calling party 102, provided in the signaling message from signaling network 114.

[0231] In step 2208, the lookup returns subscription information. For example, the customer profile can require entry of an account code. In this example, the customer profile lookup can return an indication that the customer, i.e., calling party 102, has subscribed to an account code verification feature. A class of service restriction can also be enforced, but this will not be known until account code verification identifies an associated account code.

[0232] In step 2210, soft switch site 104 instructs gateway site 108 to collect account codes. Using the information in the customer profile, soft switch site 104 can use the IPDC protocol to instruct gateway site 108 to collect a specified number of digits from calling party 102.

[0233] In step 2212, soft switch site 104 determines how to process received digits. Assuming gateway site 108 collects the correct number of digits, soft switch site 104 can use the customer profile to determine how to process the received digits. For account code verification, the customer profile can specify whether the account code needs to be validated.

[0234] In step 2214, soft switch site 104 verifies the validity of the received digits. If the account code settings in the customer profile specify that the account code must be verified and forced to meet certain criteria, soft switch site 104 performs two functions. Because “verify” was specified, soft switch site 104 queries a database to verify that the collected digits meet such criteria, i.e., that the collected digits are valid. Because “forced” was specified, soft switch site 104 also forces the calling customer to re-enter the digits if the digits were not valid.

[0235] In step 2216, verification can result in the need to enforce a restriction, such as a class of service (COS) restriction (COSR). In this example, soft switch site 104 can verify that the code is valid, but that it requires, for example, that an intrastate COSR should be enforced. This means that the call is required to be an intrastate call to be valid. The class of service restriction logic can be performed within soft switch site 104 using, for example, pre-loaded local access and transport areas (LATAs) and state tables.

[0236] If project account codes (PACs) are not used, class of service (COS) restrictions can be applied based on originating ANI or ingress trunk group.

[0237] In step 2218, soft switch 104 allows the call to proceed if the class of service requested is permitted. For example, if the LATA and state tables show that the LATAs of originating party (i.e., calling party 102) and terminating party (i.e. called party 120), must be, and are, in the same state, then the call can be allowed to proceed.

[0238] In step 2220, soft switch site 104 completes customer service processing and prepares to terminate the call. At this point, soft switch site 104 has finished executing all customer service logic and has a 10-digit dialed number that must be terminated.

[0239] In step 2222, soft switch site 104 can select a route termination based on the dialed number (i.e., the number of called party 120 dialed by calling party 102) using least cost routing. This route termination can involve termination off data network 112 or off onto another data network. Soft switch site 104 can then communicate with soft switch site 106 to allocate a terminating circuit in gateway site 110 for this call.

[0240] In step 2224, soft switch site 104 can indicate connections to be made to complete the call. Soft switch site 104 or soft switch site 106 can return a termination that indicates the connections that must be made to connect the call.

[0241] In step 2226, soft switch sites 104, 106 instruct the gateway sites to make connections to set up the call. Soft switch sites 104, 106 can send messages through data network 112 (e.g. using IPDC protocol commands) to gateway sites 108, 110, to instruct the gateway sites to make the necessary connections for setting up the call origination from calling party 102, the call termination to called party 120, and the connection between origination and termination.

[0242] In step 2228, soft switch sites 104, 106 generate and send network events to a repository. Soft switch sites 104, 106 can generate and send network events to network event component 116 that are used, for example, in detecting and preventing fraud, and in performing billing.

[0243] In step 2230, network management component 118 monitors the telecommunications network 100. All network elements create network management events such as SNMP protocol alerts or events. Network management component 118 can monitor SNMP events to enable management of network resources.

[0244] The intermediate level description and specific implementation example embodiments sections, below, will describe additional details of operation of the invention. For example, how soft switch site 104 performs initial digit analysis to identify the type of call and how to process the call will be discussed further. The sections also provide details regarding how soft switch sites 104, 106 interact with the other components of the voice network architecture.

II. Intermediate Level Description

[0245] This section provides an intermediate level description of the VOIP network architecture according to the present invention. A structural implementation of the VOIP network architecture is described at an intermediate level. Also, a functional implementation for this structure is described at an intermediate level. This structural implementation is described herein for illustrative purposes, and is not limiting. In particular, the process described in this section can be achieved using any number of structural implementations, one of which is described in this section. The details of such structural implementations will be apparent to persons skilled in the relevant arts based on the teachings contained herein.

[0246] A. Structural Description

[0247] FIG. 2A is a block diagram further illustrating the components of VOIP architecture 100 at an intermediate level of detail. FIG. 2A depicts telecommunications system 200. Telecommunications system 200 includes soft switch site 104, gateway sites 108, 110, data network 112, signaling network 114, network event component 116, provisioning component 117 and network management component 118. Included in FIG. 2A are calling parties 102, 122 and called parties 120, 124.

[0248] Soft switch site 104 includes soft switch 204, SS7 gateways 208, 210, service control point (SCP) 214, configuration server/configuration database (CDB) 206, route server 212, signal transfer points (STPs) 250, 252, and regional network event collection point (RNECP) 224. Table 1 below describes the functions of these network elements in detail.

[0249]

TABLE 1
Soft switch component	Description
soft switch (SS)	Soft switches are call control
	components responsible for
	processing of signaling messages,
	execution of call logic and control
	of gateway site access devices.
SS7 gateways (SS7 GW)	SS7 gateways provide an interface
	between the SS7 signaling network
	and the soft switch.
service switching points (SSP)	Service switching points are the
	portions of backbone switches
	providing SS7 functions. For
	example, any switch in the PSTN is
	an SSP if it provides SS7 functions.
	A soft switch is an SSP.
signal transfer point (STP)	Signal transfer points route signaling
	messages from originating service
	switching points (SSPs) to
	destination SSPs.
service control point (SCP)	Service control points provide
	number translations for toll free
	services and validation of project
	account codes for PAC services.
configuration	Configuration servers are servers
server/configuration	managing customer profiles, voice
database (CDB)	network topologies and
	configuration data. The
	configuration database is used for
	storage and retrieval of such data.
route server (RS)	Route servers are responsible for
	selection of least cost routes through
	the network and allocation of
	network ports.
regional network event	Route servers are responsible for
collection point (RNECP)	selection of least cost routes through the
	network and allocation of network ports.
	regional network event collection points
	are points in the network that collect call
	event data.

[0250] Gateway site 108 includes trunking gateway (TG) 232, access gateway (AG) 238, network access server (NAS) 228, digital cross-connect system (DACS) 242 and announcement server (ANS) 246. TG 232, AG 238, and NAS 228 are collectively known as access server 254. Similarly, gateway site 110 includes TG 234, AG 240, NAS 230, DACS 244 and ANS 248. TG 234, AG 240, and NAS 230 are collectively known as access server 256. Gateway sites 108, 110 provide trunk, private line and dedicated access line connectivity to the PSTN. Table 2 below describes the functions of these network elements in detail.

[0251]

TABLE 2
Gateway site component	Description
trunking gateway (TG)	A trunking gateway provides full-
	duplex PSTN to IP conversion for
	co-carrier and feature group D (FG-
	D) trunks.
access gateway (AG)	An access gateway provides full-
	duplex PSTN to IP conversion for
	ISDN-PRI and T1 digital dedicated
	access lines (DALs).
network access server (NAS)	A network access server provides
	modem access to an IP network.
digital access and cross-connect	A digital access and cross-connect
system (DACS)	system is a digital switching system
	used for the routing and switching of
	T-1 lines and DS-0 circuits of lines,
	among multiple T-1 ports.
announcement server (ANS)	An announcement server provides a
	network with PSTN terminating
	announcements.

[0252] Data network 112 provides the network bandwidth over which calls can be connected through the telecommunications system. Data network 112 can be, for example, a packet switched data network including network routers for routing traffic through the network.

[0253] Signaling network 114 includes signal transfer points (STPs) 216, 218 and signaling control points (SCPs) associated with each network node. Table 3 below describes the functions of these network elements in detail.

[0254]

TABLE 3
Signaling network component	Description
signal transfer points (STPs)	Signal transfer points route signaling
	messages from originating service
	switching points (SSPs) to
	destination SSPs.
service control point (SCP)	Service control point provide
	number translations for Toll Free
	services and validation of project
	account codes (PAC) for PAC
	services.
service switching point (SSPs)	Service switching points are the
	portions of backbone switches
	providing SS7 functions. For
	example, any switch in the PSTN is
	an SSP if it provides SS7 functions.
	A soft switch is an SSP.

[0255] Network management component 118 includes the means to manage a network. Network management component 118 gathers events and alarms related to network events. For example, event logs can be centrally managed from a network operations center (NOC). Alerts and events can be communicated to the NOC via the simple network management protocol (SNMP)). Table 4 below describes the functions of these network elements in detail.

[0256]

TABLE 4
Network management component	Description
network operations center (NOC)	Network operations center is a
	centralized location for gathering
	network management events and for
	managing various network elements
	via the SNMP protocol.
simple network management	Simple network management
protocol (SNMP)	protocol provides site filtering of
	element alarms and messages before
	forwarding them to the NOC.

[0257] Network event component 116 includes master network event database (MNEDB) 226. Table 5A below describes the functions of this network element in detail.

[0258]

	TABLE 5A
	Network event component	Description
	master network event database	Master network event database is a
	(MNEDB)	centralized server/database that
		collects call event records from
		regional network event collection
		points (RNECPs). It serves as a
		depository for the event records.

[0259] Provisioning component 117 includes data distributor (DD) 222. Table 5B below describes the functions of this network element in detail.

[0260]

	TABLE 5B
	Provisioning component	Description
	data distributor (DD)	The data distributor distributes
		service requests and data from
		upstream Operational Support
		Systems (OSS) to network elements.
		It maintains synchronization of
		redundant network resources.

[0261] B. Operational Description

[0262] The following operational flow describes an exemplary intermediate level call scenario intended to demonstrate at an intermediate architectural level how call processing is handled. The operational flow of the present invention is not to be viewed as limited to this exemplary illustration.

[0263] FIG. 2B depicts an exemplary call flow 258. FIG. 2B illustrates interaction between a trunking gateway, a soft switch, a configuration server and a route server in order to connect a call through telecommunications network 200. FIG. 2B details a call flow from TG 232 of gateway site 108, controlled by soft switch site 104, to TG 234 of gateway site 110, controlled by soft switch site 106. (Soft switch site 106 is illustrated in FIGS. 1 and 3.) Soft switch site 106, including soft switch 304, route server 314, and configuration server 312, is further described below in the Specific Example Embodiments section, with reference to FIG. 3.

[0264] Included in call flow 258 is a description of how soft switch 204 can process a 1+ long distance call that uses project account codes (PACs) with class of service (COS) restrictions. Call flow 258 also assumes that the origination and termination for the call uses SS7 signaling, i.e., that the call comes into network 200 via trunks from carrier facilities 126, 130, to trunking gateways 232, 234.

[0265] Exemplary call flow 258 begins with step 259. In step 259, soft switch 204 receives an incoming IAM signaling message from an SS7 GW 208, signaling an incoming call from calling party 102 on carrier facility 126 of a co-carrier.

[0266] In step 260, soft switch 204 sends IPDC commands to trunking gateway 232 to set up a connection (e.g. a DS0 or DS1 circuit) between carrier facility 126 and TG 232 described in the received IAM signaling message. In step 262, trunking gateway 232 sends an acknowledgement message to soft switch 204.

[0267] Based upon the information in the IAM message, soft switch 204 performs initial digit analysis on the dialed number, i.e., the number of called party 120, and determines that the incoming call is a 1+ call.

[0268] In step 263, application program logic within soft switch 204 determines that, with this type of call, i.e., a 1+ call, soft switch 204 should query a customer profile database within configuration server 206, to retrieve the originating customer trigger plan 290 for calling party 102.

[0269] The customer profile lookup is performed in configuration server 206 using the originating automatic number identification (ANI) of calling party 102 as the lookup key.

[0270] In step 264 the customer profile lookup returns to soft switch 204 an indication that the calling party 102 has subscribed to project account codes (PAC). Examples of PACs include billing codes. They provide a mechanism for a network customer, such as a law firm, to keep an accounting of which of their clients to bill. Example call flow 258 will also perform a class of service (COS) restriction, but this will not be known by soft switch 204 until account code verification identifies an associated account code requiring the COS restriction. Alternatively, the customer profile information can reside in route server 212, enabling route server 212 to perform the functions of configuration server 206, in addition to its own functions.

[0271] In step 267, using the information in the customer profile (i.e., customer trigger plans 290) of configuration server 206, soft switch 204 uses the IPDC protocol to instruct trunking gateway 232 to collect the specified number of digits, representing the project account code, from calling party 102.

[0272] In step 268, the digits are sent from trunking gateway 232 to soft switch 204. Assuming that trunking gateway 232 collected the correct number of digits, soft switch 204 uses the customer profile of configuration server 206 to determine how to process the received digits. For project account codes (PACs), the customer profile in configuration server 206 specifies whether the project account code needs to be validated.

[0273] If the project account code settings in the customer profile of configuration server 206 specify that the project account code is “verified and forced,” then soft switch 204, in step 265, can query SCP 214 with the collected digits to verify that they are valid. Table 129 below provides alternative PAC settings.

[0274] In step 266, SCP 214 returns an indication that the project account code is valid, and it requires that an intrastate class of service (COS) restriction should be enforced. The class of service (COS) restriction logic can be performed within soft switch 204, using pre-loaded LATA and state tables from configuration server 206.

[0275] If a PAC is not used, the COS restriction can be applied based on ANI or ingress trunk group.

[0276] If the LATA and state tables from configuration server 206 show that the originating LATA (i.e., the LATA of calling party 102) and the terminating LATA (i.e., the LATA of called party 120) are in the same state, then the call is allowed to proceed.

[0277] At this point, soft switch 204 has finished executing all customer service logic and has a 10-digit DDD number (i.e., the phone number of called party 120), that must be terminated.

[0278] In step 269, soft switch 204 queries route server 212 to receive a call route and to allocate circuits to connect the call. Route server 212 is responsible for using the DDD number to select a least cost route through data network 112, and allocating a terminating circuit for this call.

[0279] Additional information on how soft switch 204 interacts with route server 212 and terminating soft switch 304 is described in the Specific Implementation Example Embodiments Section below, in the section entitled Route Server.

[0280] In step 270, route server 212 returns a route that indicates the connections that soft switch 204 must make to connect the call.

[0281] In step 274, soft switch 204 communicates with soft switch 304 to allocate ports in trunking gateway 234 of gateway site 110, for termination of the call. Soft switch 304 is located in a central soft switch site 106. In step 276, soft switch 304 queries port status 298 of route server 314 to identify available ports in trunking gateway 234. In step 278, route server 314 returns an available port to soft switch 304. In steps 280 and 282, soft switch 304 communicates with trunking gateway 234 to allocate a port for termination of the call to called party 120.

[0282] In step 284, soft switch 304 communicates with soft switch 204 to indicate terminating ports have been allocated.

[0283] In steps 286 and 288, soft switch 204 communicates with trunking gateway 232 in order to notify trunking gateway 232 to set up an RTP session (i.e. an RTP over UDP over IP session) with trunking gateway 234 and to permit call traffic to be passed over data network 112.

[0284] The Specific Implementation Example Embodiments Section, in the next section, describes additional information about, for example, how soft switch 204 performs initial digit analysis to identify the type of call, and how to process the call. The next section also describes how soft switch 204 interacts with other components of the voice network architecture 200 in transmitting the call.

III. Specific Implementation Example Embodiments

[0285] Various embodiments related to structures, and operations between these structures described above are presented in this section (and its subsections). These embodiments are described herein for purposes of illustration, and not limitation. The invention is not limited to these embodiments. Alternate embodiments (including equivalents, extensions, variations, deviations, etc., of the embodiments described herein) will be apparent to persons skilled in the relevant arts based on the teachings contained herein. The invention is intended and adapted to include such alternate embodiments.

[0286] Specifically, this section provides a detailed description of the VOIP network architecture according to the present invention. A structural implementation of the (VOIP) network architecture is described at a low-level. Also, a functional implementation for this structure is described at a low-level.

[0287] A. Structural Description

[0288] A more detailed structural description of telecommunications network 200 will now be described.

[0289] 1. Soft Switch Site

[0290] FIG. 3 is a block diagram illustrating a more detailed implementation of telecommunications network 200. Specifically, FIG. 3 illustrates telecommunications network 300 containing three geographically diverse soft switch sites. These soft switch sites include western soft switch site 104, central soft switch 106, and eastern soft switch 302.

[0291] Telecommunications network 300 also includes a plurality of gateway sites that may be collocated or geographically diverse. These gateway sites include gateway sites 108a, 108b, 110a and 110b.

[0292] Data network 112 can route both signaling and transport traffic between the regional soft switch sites and regional gateway sites. For example, data network 112 can be used to route traffic between western soft switch site 104 and gateway site 110a. Signaling and transport traffic can also be segregated and sent over separate data networks. As those skilled in the art will recognize, data network 112 can be used to establish a data or voice connection among any of the aforementioned gateway sites 108a, 108b, 110a and 110b under the control of any of the aforementioned soft switch sites 104, 106 and 302.

[0293] Western soft switch site 104 includes soft switch 204a, soft switch 204b, and soft switch 204c. Soft switches 204a, 204b, 204c can be collocated or geographically diverse. Soft switches 204a, 204b, 204c provide the features of redundancy and high availability.

[0294] Failover mechanisms are enabled via this architecture, since the soft switches can act as one big switch. Soft switches 204a, 204b, 204c can intercommunicate via the inter soft switch communication protocol, permitting access servers to reconnect from one soft switch to another.

[0295] Western soft switch site 104 includes SS7 gateway (GW) 208, configuration server/configuration database (CS/CDB) 206a and route server (RS) 212a. To provide high availability and redundancy, western soft switch site 104 includes a redundant SS7 GW, a redundant CS/CDB and a redundant RS. Specifically, western soft switch site 104 includes SS7 GW 210, CS/CDB 206b and RS 212b.

[0296] Soft switches 204a, 204b and 204c are connected to SS7 GWs 208, 210, CS/CDBs 206a, 206b and RSs 212a, 212b via redundant ethernet switches (ESs) 332, 334 having multiple redundant paths. This architecture enables centralization of SS7 interconnection to gain economies of scale from use of a lesser number (than conventionally required) of links to signaling network 114, to be shared by many access servers in gateway sites. ESs 332, 334 also provide connectivity to routers (Rs) 320, 322. Routers 320, 322 respectively provide redundant connectivity between redundant ESs 332, 334 and data network 112. As noted, included in telecommunications network 300 are central soft switch site 106 and eastern soft switch site 302. Central soft switch site 106 and eastern soft switch site 302 respectively include identical configurations to the configuration of western soft switch site 104. Central soft switch site 106 includes SS7 GWs 308, CS/CDBs 312, RSs 314, soft switches 304a, 304b, 304c, ESs 336, 338, and Rs 324, 326. Similarly, eastern soft switch site 302 includes SS7 GWs 310, CS/CDBs 316, RSs 318, soft switches 306a, 306b, 306c, ESs 340, 342, and Rs 328 and 330.

[0297] Gateway site 108a includes TG 232a, NAS 228a, AG 238a and DACS 242a. Gateway sites 108b, 110a and 110b have similar configurations to gateway site 108a. Gateway site 108b includes TG 232b, NAS 228b, AG 238b and DACS 242b. Gateway site 110a includes TG 234a, NAS 230a, AG 240a and DACS 244a. Finally, gateway site 110b includes TG 234b, NAS 230b, AG 240b, and DACS 244b. The details of gateway site 108a, 108b, 110a and 110b will be further described below with reference to FIG. 10A.

[0298] a. Soft Switch

[0299] Referring back to FIG. 2A, soft switch 204 provides the call processing function for telecommunications network 200. Call processing refers to the handling of voice and data calls. There are a number of important call processing functions handled by soft switch 204. Soft switch 204 processes signaling messages used for call setup and call tear down. These signaling messages can be processed by in-band or out-of-band signaling. For an example of out-of-band signaling, SS7 signaling messages can be transmitted between signaling network 114 and soft switch 204. (Soft switch 204 refers to soft switches 204a, 204b and 204c).

[0300] Another call processing function performed by soft switch 204 is preliminary digit analysis. Preliminary digit analysis is performed to determine the type of call arriving at soft switch 204. Examples of calls include toll free calls, 1+ calls, 0+ calls, 011+ calls, and other calls recognized by those skilled in the art.

[0301] One important feature of soft switch 204 is communicating with CS/CDB 206 to retrieve important customer information. Specifically, soft switch 204 queries CS/CDB 206 to retrieve a customer trigger plan. The customer trigger plan effectively identifies the service logic to be executed for a given customer. This trigger plan is similar to a decision tree pertaining to how a call is to be implemented. Subsequently, soft switch 204 executes the customer trigger plan. This includes the processing of special service calls requiring external call processing, i.e., call processing that is external to the functions of telecommunications network 200.

[0302] Another important function soft switch 204 is communicating with RS 212 to provide network routing information for a customer call. For example, soft switch 204 can query RS 212 to retrieve the route having the least cost from an off-network calling party 102 (homed to gateway site 108) to an off-network called party 120 (homed to gateway site 110) over data network 112. Upon finding the least cost route, soft switch 204 allocates ports on TGs 232, 234. As described in detail below, soft switch 204 can also be used to identify the least cost route termination and allocate gateway ports over AGs 238, 240 between an on-network calling party 122 (homed to gateway site 108) and an on-network called party 124 (homed to gateway site 110).

[0303] Soft switch 204 also communicates with AGs 238, 240, TGs 232, 234, and NASs 228, 230 over data network 112. Although AGs 238, 240, TGs 232, 234 and NASs 228, 230 can communicate with a plurality of soft switches, as illustrated in FIG. 3, these network nodes (referred to collectively as access servers 254a, 254b, 256a, and 256b) are respectively assigned to a primary soft switch. This primary soft switch, e.g., soft switch 204, assumes a primary responsibility or control of the access servers. In addition, the access servers can be as respectively assigned to secondary switches, which control the access servers in the event that the primary soft switch is unavailable.

[0304] Referring back to FIG. 3, western soft switch site 104, central soft switch site 106 and eastern soft switch site 302 are geographically diverse. For example, western soft switch site 104 can be a soft switch site located in San Diego, Calif. Central soft switch site 106 can be a soft switch site located in Denver, Colo. Eastern soft switch site 302 can be a soft switch site located in Boston, Mass.

[0305] It is permissible that additional network nodes are provided at any of soft switch sites 104, 106 and 302. For example, additional elements, including, e.g., SS7 GW 208, CDB 206a, and RS 212a can be collocated at western soft switch site 104. Examples of other supporting elements of western soft switch site 104 are an announcement server (ANS), a network event collection point (NECP), an SCP, and on-network STPs. Referring to the more detailed implementation of FIG. 2A, telecommunications network 200 includes ANSs 246, 248, NECP 224, SCP 214, and STPs 250, 252.

[0306] (1) Soft Switch Interfaces

[0307] FIG. 4A is a block diagram illustrating the interfaces between soft switch 204 and the remaining components of telecommunications network 200. The soft switch interfaces of FIG. 4A are provided for exemplary purposes only, and are not to be considered limiting. Soft switch 204 interfaces with SS7 GWs 208, 210 via soft switch-to-SS7 GW interface 402. One example of interface 402 is an SS7 integrated services digital network (ISDN) user part (ISUP) over a transmission control protocol/internet protocol (TCP/IP). Soft switch 204 interfaces with configuration server 206 over interface 406. In an example embodiment, interface 406 is a TCP/IP connection.

[0308] Soft switch 204 interfaces with RNECP 224 over interface 410. In an example embodiment, interface 410 is a TCP/IP connection.

[0309] Soft switch 204 interfaces with route server 212 over interface 408. In an example embodiment, interface 408 is a TCP/IP connection.

[0310] Soft switch 204 interfaces with SCP 214 over interface 404. In an example embodiment, interface 404 is a TCP/IP connection.

[0311] Soft switch 204 interfaces with announcement servers 246, 248 over interface 416. In an example embodiment, interface 416 can include the IPDC protocol used over a TCP/IP connection.

[0312] Soft switch 204 interfaces with TGs 232, 234 over interface 412. In an example embodiment, interface 412 can include the IPDC protocol used over a TCP/IP connection.

[0313] Soft switch 204 interfaces with AGs 238, 240 over interface 414. In an example embodiment, interface 414 can include the IPDC protocol used over a TCP/IP connection.

[0314] In one embodiment, soft switch 204 is an application software program running on a computer. The structure of this exemplary soft switch is an object oriented programming model discussed below with reference to FIGS. 4B-4E.

[0315] Another interface to soft switch 204 (not shown) is a man-machine interface or maintenance and monitoring interface (MMI). MM can be used as a direct controller for management and machine actions. It should be noted that this is not intended to be the main control interface, but is rather available to accommodate the need for on-site emergency maintenance activities.

[0316] Yet another interface permits communication between soft switches 204, 304. A soft switch-to-soft switch interface will be described further with reference to FIG. 2B. A soft switch 204-to-soft switch 1304 interface permits communication between the soft switches 204, 304 that control the originating call-half and terminating call-half of call flow 258. The soft switch 204-to-soft switch 304 interface allows soft switches 204, 304 to set up, tear down and manage voice and data calls. Soft switch 204 to soft switch 304 interface can allow for a plurality of inbound and outbound signaling types including, for example, SS7, ISDN, and in-band E&M signaling.

[0317] In telephony, E&M is a trunking arrangement generally used for two-way (i.e., either side may initiate actions) switch-to-switch or switch-to-network connections. E&M signaling refers to an arrangement that uses separate leads, called respectively the “E” lead and the “M” lead, for signaling and supervisory purposes. The near-end signals the far-end by applying −48 volts DC (“VDC”) to the “M” lead, which results in a ground being applied to the far end's “E” lead. When 48 VDC is applied to the far-end “M” lead, the near-end “E” lead is grounded. “E” lead originally stood for “ear,” i.e., when the near-end “E” lead was grounded, the far end was calling and “wanted your ear.” “M” originally stood for “mouth,” because when the near-end wanted to call (i.e., to speak to) the far end, −48 VDC was applied to that lead.

[0318] When a PBX wishes to connect to another PBX directly, or to a remote PBX, or to an extension telephone over a leased voice-grade line (e.g., a channel on a T-1), the PBX can use a special line interface. This special line interface is quite different from that which the PBX uses to interface to directly-attached phones. The basic reason for the difference between a normal extension interface and a long distance interface is that the respective signaling requirements differ. This is true even if the voice signal parameter, such as level and two-wire, four-wire remain the same. When dealing with tie lines or trunks, it is costly, inefficient, and too slow for a PBX to do what an extension telephone would do, i.e., to go off hook, wait for a dial tone, dial, wait for ringing to stop, etc. The E&M tie trunk interface device is a form of standard that exists in the PBX, T-1 multiplexer, voice-digitizer, telephone company world. E&M signaling can take on a plurality of forms. At least five different versions exist. E&M signaling is the most common interface signaling method used to interconnect switching signaling systems with transmission signaling systems.

[0319] The sample configuration depicted in FIG. 2B, can use a soft switch 204-to-soft switch 304 protocol. In FIG. 2B, the access servers depicted are trunking gateways 232, 234. TGs 232, 234 are connected to the switch circuit network (SCN), i.e., signaling network 114, via SS7 trunks, ISDN trunks, and in-band trunks. The originating soft switch 204 can receive a call over any of these trunks. The signaling information from these SS7, ISDN, and in-band trunks is processed by soft switch 204 to establish the originating call-half The signaling information processed by soft switch 204, can be used to determine the identity of terminating soft switch 304. The identity of terminating soft switch 304 is required to complete the call.

[0320] Originating soft switch 204 can then communicate the necessary information to complete the call, via an inter-soft switch communication (ISSC) protocol. Terminating soft switch 304 can be required to be able to establish the terminating call-half on any of the supported trunk types. The ISSC protocol can use a message set that is structured similarly to the IPDC protocol message set. The messages can contain a header followed by a number of tag-length-value attributes. The incoming signaling message for the call being placed, can be carried in a general data block of one of the attribute value pairs (AVPs). The other AVPs, can contain additional information necessary to establish a voice-over-IP connection between the originating and terminating ends of the call.

[0321] b. SS7 Gateway

[0322] SS7 gateways (GWs) 208, 210 will now be described further with reference to FIG. 2A and FIG. 5A. In FIG. 2A, SS7 GWs 208, 210 receive signaling messages from signaling network 114 and communicate these messages to soft switch 204. Specifically, for SS7 signaled trunks, SS7 GWs 208, 210 can receive SS7 ISUP messages and transfer them to soft switch 204. SS7 GWs 208, 210 can also receive signaling messages from soft switch 204 and send SS7 ISUP messages out to signaling network 114.

[0323] (1) SS7 Gateway Example Embodiment

[0324] In an example embodiment, SS7 GWs 208, 210 can be deployed in a two (2) computing element (CE) cluster 207, depicted in FIG. 5A. SS7 GWs 208, 210, in two-CE-cluster 207 can fully load-share. SS7 GWs 208, 210 can intercommunicate as represented by connection 530 to balance their loads. Load-sharing results in a completely fault resilient hardware and software system with no single point of failure. Each SS7 GW 208, 210 can have, for example, six two-port cards for a total of twelve links to signaling network 114.

[0325] In an example embodiment, SS7 GWs 208, 210 are application programs running on a computer system. An exemplary application program providing SS7 GW 208, 210 functionality is OMNI SIGNALWARE (OMNI), available from DGM&S, of Mount Laurel, N.J. OMNI is a telecommunications middleware product that runs on a UNIX operating system. An exemplary operating system is the SUN UNIX, available from SUN Microsystems, Inc. of Palo Alto, Calif. The core of OMNI resides logically below the service applications, providing a middleware layer upon which telecommunications applications can be efficiently deployed. Since the operating system is not encapsulated, service applications have direct access to the entire operating environment. Because of OMNI's unique SIGNALWARE architecture, OMNI has the ability to simultaneously support variants of SS7 signaling technology (ITU-T, ANSI, China and Japan).

[0326] The SIGNALWARE architecture core is composed of the Message Transfer Part (MTP) Layer 2 and Layer 3, and Service Connection Control Part (SCCP). These core protocols are supplemented with a higher layer of protocols to meet the needs of a target application or service. OMNI supports multiple protocol stacks simultaneously, each potentially with the point code format and protocol support of one of the major SS7 variants.

[0327] OMNI SIGNALWARE Application Programming Interfaces (APIs) are found on the higher layers of the SS7 protocol stack. OMNI APIs include: ISDN User Part (ISUP), Telephony User Part (TUP), Transaction Capabilities Application Part (TCAP), Global System for Mobile Communications Mobile Application Part (GSM MAP), EIA/TIA Interim Standard 41 (IS-41 MAP), Advanced Intelligent Network (AIN), and Intelligent Network Application Part (INAP).

[0328] (2) SS7 Gateway-to-Soft Switch Interface

[0329] FIG. 5A depicts SS7 gateway to soft switch distribution 500. Soft switches receive signaling messages from signaling gateways. Specifically, for SS7 signaled trunks, SS7 GWs 208, 210 send and receive signals from signaling network 114. SS7 GWs 208, 210 communicate with soft switches 204a, 204b, 204c, via redundant connections from the soft switches 204a, 204b, 204c to distributions 508, 510, of SS7 GWs 208, 210 respectively. SS7 GWs 208, 210 together comprise a CE cluster 207.

[0330] Based upon an SS7 network design, a pair of SS7 gateways receive all signaling traffic for the trunking gateway (TG) circuits serviced by the soft switches at a single soft switch site. Specifically, a pair of SS7 GWs 208, 210 receive all signaling traffic for circuits serviced by soft switch site 104. Signals serviced by soft switch site 104 enter telecommunications network 200 from gateway sites 108, 502, 110.

[0331] In an example embodiment, 96 circuits are serviced by each gateway site 108, 502, 110. Gateway site 108 includes TGs 232a, 232b. Gateway site 110 includes TGs 234a, 234b. Gateway site 502 includes TGs 504, 506.

[0332] A circuit is identified by a circuit identification, code (CIC). TG 232a includes line card access to a plurality of circuits including CICs 1-48 512 of gateway site 108. TG 232b provides line card access to CICs 49-96 514 of gateway site 108. TG 504 provides line card access to CICs 1-48 516. TG 506 provides line card access to CICs 49-96 518 of gateway site 502. TG 234a provides line card access to CICs 1-48 520. TG 234b provides line card access to CICs 49-96 522 of gateway site 110. Thus, CICs 1-48 512, 516, 520, and CICs 49-96 514, 518, 522 are the trunking gateway circuits serviced by soft switch site 104.

[0333] In an example embodiment, soft switches are partitioned such that any single soft switch will only service a subset of circuits serviced at a given soft switch site. For example, soft switch 204a can service CICs 1-48 512, 516, while soft switch 204b services CICs 49-96 514 and CICs 1-48 520, and soft switch 204c services CICs 49-96 518, 522. In order to assure that all signaling messages for a particular call get to the correct one of soft switches 204a, 204b, 204c, it is necessary to partition SS7 signaling across the available soft switches based upon the circuits that each soft switch services.

[0334] It is much more efficient to run SS7 links to soft switches than to each individual access server (compare to the conventional approach requiring an SS7 link to each SSP). Centralization of SS7 signaling traffic interconnection enables benefits from economies of scale, by requiring less SS7 interconnection links.

[0335] An exemplary technique for distributing circuits across soft switches 204a, 204b, 204c is based upon the originating point code (OPC), destination point code (DPC), and CIC. OPC represents the originating point code for a circuit group, i.e., the point code of a local exchange carrier (LEC) switch, or signal point (SP). For example, the LEC providing CICs 1-48 512, and CICs 49-96 514 can have an OPC 524 of value 777. The LEC providing CICs 1-48 516, and CICs 49-96 518 can have an OPC 526 of value 888. The LEC switch providing CICs 1-48 520, and CICs 49-96 522 has an OPC 528 of value 999. Similarly, DPC represents the destination point code for a circuit group, i.e., the point code of soft switch site 104. Soft switch site 104 has a point code 529 of value 111, and an alternate point code 531 of value 444. Soft switch site 104 can act as one big switch using a flat network design of the present invention. This flat network design simplifies routing of calls.

[0336] To support distribution of circuits across soft switches 204a, 204b, 204c, SS7 GWs 208, 210 can include a lookup table that allows each signaling message to be routed to the correct soft switch 204a, 204b, 204c. The lookup table can route signaling messages to the correct soft switch 204a, 204b, 204c based upon the OPC, DPC, and CIC fields. This lookup table is built on SS7 GWs 208, 210 based upon registration messages coming from soft switches 204a, 204b, 204c.

[0337] In an example embodiment, each time a TG boots up, the TG finds a soft switch to service its circuits. For example, when TG 232a is powered up, TG 232a must find a soft switch 204a, 204b, 204c to service its circuits, i.e. CICs 1-48 512. In an exemplary technique, TG 232a sends registration messages to soft switch 204a to register circuits CICs 1-48 512. Upon receipt of these registration messages the soft switch 204a registers these circuits with SS7 GWs 208, 210, at soft switch site 104. The circuit registration messages sent to the SS7 gateways are used to build the type of table shown in Table 6.

[0338]

TABLE 6
OPC, DPC, CIC
registration request	Value
Message Type	SS7 gateway circuit registration
OPC	Originating point code for the circuit group. Equals
	the LEC point code.
Primary DPC	Primary destination point code for the circuit group.
	Equals the Soft Switch site point code.
Alias DPC	Alias DPC for the Soft Switch site
Start CIC	Starting Circuit Identification Code for the circuit
	group
End CIC	Ending Circuit Identification Code for the circuit
	group
Servicing Soft	Unique Identifier for the Soft Switch that will
Switch ID	service requests for the OPC, DPC, CIC values
Servicing Soft	IP address for the Soft Switch that will service
Switch IP address	requests for the OPC, DPC, CIC values
Servicing Soft	Port number that the Soft Switch is listening on for
Switch IP port	incoming signaling messages.
Primary/Secondary/	The Soft Switch identifies itself as the primary,
Tertiary	secondary or tertiary contact for signaling messages
identification	for the specified OPC, DPC and CIC.

[0339] The format of a registration message is shown in Table 7. Table 7 includes the mapping of circuits to soft switches.

[0340] The messages used by soft switches 204a, 204b, 204c to register their circuits with SS7 GWs 208, 210 contain information for the OPC, DPC and circuit range, i.e., the CICs that are being registered. Each message also contains information about the soft switch that will be servicing the signaling messages for the circuits being registered.

[0341] The soft switch information includes an indication of whether this soft switch is identified as the primary servicing point for calls to these circuits, the secondary servicing point or the tertiary servicing point. The gateway uses this indicator in failure conditions, when it cannot contact the Soft Switch that is currently servicing a set of circuits.

[0342]

	TABLE 7
	OPC	DPC	CIC range	Soft Switch
	777	111	1-48	204a
	777	111	49-96	204b
	888	111	1-48	204a
	888	111	49-96	204c
	999	111	1-48	204b
	999	111	49-96	204c

[0343] FIG. 5A illustrates, and Table 7 represents in tabular form, the associations between circuit trunk groups of TGs 232a, 232b, 516, 518, 520, 522 and soft switches 204a, 204b, 204c. SS7 GWs 208, 210 distribute incoming SS7 signaling messages to the soft switch 204a, 204b, 204c listed as associated with the particular circuit in the circuit to soft switch mapping lookup table, (i.e., Table 7). For example, when the LEC switch, or signaling point, associated with OPC 524 (having point code 777) sends a call to TG 232b over CIC 55 (of CICs 49-96 514), an IAM message can be created and routed. The IAM includes the following information:

• • [0344] (1) OPC 777 (originating LEC has a point code 777),
  • [0345] (2) DPC 111 (soft switch site 104, the “switch” that the LEC believes it is trunking to, has point code 111), and
  • [0346] (3) CIC 55 (the circuit selected by the LEC has circuit identifier code 55).

[0347] The IAM message can then be routed by signaling network 114 (i.e., the SS7 network) to SS7 GWs 208, 210 at soft switch site 104, having point code 111. SS7 GWs 208, 210 can perform a lookup to Table 7, to identify which of soft switches 204a, 204b, 204c is handling the particular circuit described in the IAM message. In the example above, the IAM message having OPC 524 of value 777, DPC of value 111 and CIC 55 can be routed to soft switch 204b.

[0348] SS7 GWs 208, 210 will now be discussed further with reference to FIG. 17A. FIG. 17A depicts an exemplary signaling network environment 1700. FIG. 17A includes signaling network 114 Specifically, signaling network 114 can be an SS7 national signaling network. FIG. 17A depicts three soft switch sites interfacing via a plurality of STPs to SS7 network 114.

[0349] FIG. 17A includes soft switch sites 104, 106, 302. Western soft switch site 104 includes three soft switches 204a, 204b, 204c redundantly connected to routers 320, 322 and SS7 GWs 208, 210 via ethernet switches 332, 334. SS7 GW 208 and SS7 GW 210 communicate via a TCP/IP connection 1702 and serial link 1704.

[0350] Similarly, central soft switch site 106 includes soft switches 304a, 304b, 304c redundantly connected to routers 324, 326 and SS7 GWs 308a, 308b via ethernet switches 336, 338. SS7 GW 308a and SS7 GW 308b communicate via TCP/IP connection 1706 and serial link 1708.

[0351] Finally, eastern soft switch site 302 includes soft switches 306a, 306b, 306c redundantly connected to routers 328, 330 and SS7 GWs 310a, 310b via ethernet switches 340, 342. SS7 GW 310a and SS7 GW 310b communicate via TCP/IP connection 1710 and serial link 1712.

[0352] FIG. 17A also includes data network 112 connected to soft switch sites 104, 106, 302 via routers 320, 322, routers 324, 326 and routers 328, 330, respectively. Data network 112 can carry data including control message information and call traffic information. Data network 112 can also carry in-band type signaling information and ISDN signaling information, via IPDC messages.

[0353] Out-of-band signaling, such as, e.g., SS7 signaling, information is communicated to (i.e. exchanged with) soft switch sites 104, 106, 302 via SS7 GWs 208, 210, SS7 GWs 308a, 308b, and SS7 GWs 310a, 310b from signaling network 114.

[0354] SS7 signaling messages are transferred through signaling network 114 from STP to STP until arriving at a final destination. Specifically, signaling messages intended for soft switch sites 104, 106, 302, are routed via packet switched SS7 signaling network 114 to STPs 216, 218 which are part of the SS7 national signaling network 114. STP services (i.e., STPs and A-F links) can be provided by an SS7 signaling services provider, such as, e.g., Transaction Network Services (TNS).

[0355] Table 19 defines SS7 signaling links. Some of the SS7 links used are as follows. STPs 216, 218 are linked together by a C-link. STPs 216, 218 are linked by redundant D-links 1730 to STPs 250a, 252a, 1722, 1724, 250b, 252b. STPs 216, 218 can also be linked by redundant D-links 1730 to STPs 1718, 1720, 1714, 1716, though this is not shown.

[0356] STP pairs 250a, 252a are linked together by one or more C-links 1728. Likewise, STP pairs 1722, 1724, STP pairs 250b, 252b, STP pairs 1718, 1720, and STP pairs 1714, 1716 can be linked together by C-links.

[0357] STPs 1714, 1716, 250a, 252a, 1722, 1724, 250b, 252b, 1718, and 1720 can be linked by one or more A-links 1726 to SS7 GWs 208, 210, 308a, 308b, 310a, and 310b. Thus, signaling messages from anywhere in signaling network 114 may be routed by STPs 216, 218 through STPs 1714, 1716, 250a, 252a, 1722, 1724, 250b, 252b, 1718, 1720, to SS7 GWs 208, 210, 308a, 308b, 310a, and 310b of soft switch sites 104, 106, and 302. SS7 GWs 208, 210, 308a, 308b, 310a, and 310b thus route messages through packet switched STPs to signaling network 114.

[0358] SS7 GWs 208, 210, 308a, 308b, 310a, and 310b use a separate physical interface for all simple network management protocol (SNMP) messages and additional functions that may be defined. Exemplary functions that may be defined include provisioning, updating, and passing special alarms, and performance parameters to the SS7 GW from the network operation center (NOC) of network management component 118.

[0359] c. Signal Transfer Points (STPs)

[0360] Signal transfer points (STPs) 216, 218 are the packet switches of signaling network 114. More specifically, STPs are the packet switches of the SS7 network. STPs 250, 252 are the STPs interfacing with SS7 GWs 208, 210 of soft switch site 104. STPs 216, 218 receive and route incoming signaling messages toward the proper destination.

[0361] STPs 250, 252 also perform specialized routing functions. STPs are customarily deployed in pairs. While elements of a pair are not generally collocated, they work redundantly to perform the same logical function.

[0362] STPs have several interfaces. STP interfaces are now described, with reference to FIGS. 17A and 17B. The interfaces can be described in terms of the links used. Table 19 shows links used in SS7 architectures.

[0363] The first interface comprises one or more D-links 1730 from off-network STPs 250, 252 (as shown in FIG. 2A) to on-network STPs 216, 218. D-links connect mated STPs at different hierarchical levels to one another. On-network STPs 216, 218, as well as STPs 1714, 1716, 1722, 1724, 1718 and 1720 are part of the national SS7 signaling network 114. Additional D-links 1730 can connect STPs 216, 218 to STPs 250a, 252a, STPs 1722, 1724, STPs 250b, 252b, and STPs 1718 and 1720.

[0364] The second interface comprises C-links. C-links connect mated STPs together. An example are C-links 1728 between STP 250a and 252a. C-links 1728 enable STPs 250a, 252a to be linked in such a manner that they need not be co-located. Similarly, STPs 250b, 252b, STPs 1718, 1720, STPs 1722, 1724, STPs 1714, 1716, and STPs 216, 218 can also be respectively linked via C-links.

[0365] The third interfaces to STPs comprise A-links and E-links. A-links connect STPs to SSPs and SCPs. E-links are special links that connect SSPs to remote STPs, and are used in the event that A-links to home STPs are congested. The entire soft switch site is viewed as an SSP to a signaling network. A-links or E-links can be used to connect any of STPs 1714, 1716, 250a, 252a, 1722, 1724, 250b, 252b, 1718 and 1720 respectively to soft switch sites 104, 106, 302 at SS7 GWs 208, 210, 308a, 308b, 310a and 310b. In an example embodiment, each of SS7 GWs 208, 210, 308a, 308b, 310a, 310b can have, for example, twelve (12) A-links 1726 distributed among STPs 250a, 252a, 250b, 252b and STPs 1714, 1716, 1722, 1724, 1718, 1720. By using the plurality of A-links, the soft switch sites 104, 106, 302 have a fully redundant, fully meshed, fault tolerant signaling architecture.

[0366] STPs 250a, 252a, 250b, 252b use a separate physical interface for all SNMP messages and additional functions that can be defined. Additional functions that can be defined include provisioning, updating, and passing special alarms and performance parameters to and from STPs 250a, 252a, 250b, 252b and network operation center (NOC) of network management component 118.

[0367] In another embodiment of the invention, as illustrated in FIG. 17B, soft switch sites 104, 106, 302 have additional soft switches and SS7 GWs. Additional soft switches and SS7 GWs can be used, for example, for handling additional traffic and for testing of alternative vendor soft switches and SS7 GWs.

[0368] FIG. 17B includes SS7 gateway to SS7 signaling network alternative embodiment 1740. FIG. 17B includes signaling network 114 interfacing to western soft switch site 104, central soft switch site 106, and eastern soft switch site 302. Signaling network 114 includes STPs 216, 218 connected via multiple D-Links 1730 to STPs 250a, 252a, 250b, 252b. In an example embodiment STP 250a and STP 252a are connected together by C-Links 1728. In an alternative embodiment, STPs 250a, 252a and STPs 250b, 252b can be linked by quad B-Links. B-links connect mated STP pairs to other mated STP pairs. STPs 250a, 252a, 250b, 252b are connected by multiple redundants A-Links 1726 to SS7 GWs in soft switch sites 104, 106, 302.

[0369] Western soft switch site 104 includes SS7 GWs 208, 210, which can communicate via a TCP/IP connection and a serial link. SS7 GWs 208, 210 are connected to soft switches 204a, 204b, and 204c. In addition, western soft switch site 104 includes soft switch 1742 and SS7 GW 1744 connected to STPs 250a and 252a. Also western soft switch site 104 includes soft switch 1746 and SS7 GW 1748 connected to STPs 250a, 252a.

[0370] Central soft switch site 106 includes SS7 GWs 308a, 308B which can communicate via a TCP/IP connection or a serial link. SS7 GWs 308a, 308b connect soft switches 304a, 304b and 304c to STPs 250a and 252a. Central soft switch site 106 also includes soft switch 1750 and SS7 GWs 1752 connected to STPs 250a, 252a. Central soft switch site 106 also includes soft switch 1754 connected to SS7 GW 1756, which is connected to STPs 250a, 252a.

[0371] Eastern soft switch site 302 includes SS7 GWs 310a, SS7 GW 310b, which can communicate over TCP/IP and over a serial link. SS7 GWs 310a, 310b connect soft switches 306a, 306b and 306c to STPs 250b and 252b. Eastern soft switch site 302 also includes soft switch 1758 connected to SS7 GW 1760, which is connected to STPs 250b, 252b. Eastern soft switch site 302 also includes soft switch 1762, which is connected to SS7 GW 1764 which is in turn connected to STPs 250b, 252b.

[0372] Alternative embodiment 1740, by including additional soft switches and SS7 gateways, permits additional redundancy and enables testing of alternate devices for connection to signaling network 114 via STPs 250a, 252a, 250b, 252b, 216 and 218.

[0373] (1) STP Example Embodiment

[0374] STPs 250, 252, in an example embodiment, can be a TEKELEC Network Switching Division's EAGLE STP. An EAGLE STP, available from TEKELEC of Calabasas, Calif., is a high speed packet switch designed to support SS7 signaling. STPs 250, 252 can be equipped with a plurality of links. In an example embodiment, STPs 250, 252 can support up to, for example, 84 links. For example, in a preferred embodiment, 14 links can be used initially, and additional links can be added in the future. In a preferred embodiment, several additional features can be added to STPs 250, 252.

[0375] (a) Global Title Translation

[0376] In a preferred embodiment, STPs 250, 252 can have global title translation capability. Global title translation uses global title information. Global title information is information unrelated to signaling network address, which can be used to determine the appropriate destination of a message. Global title translation can support translations from, for example, one to twenty-one digits. For example, translations can be assigned to translation types from 0 to 225. In a preferred embodiment, STPs 250, 252 can support up to, for example, 1,000 global title translation requests per second, per application service module (ASM).

[0377] (b) Gateway Screening Software

[0378] In a preferred embodiment, STPs 250, 252 include a gateway screening software feature. EAGLE STP can support user definitions of up to 64 screen sets In this embodiment, each screen set can accommodate up to 2,000 condition statements (or rules) with the gateway screening software. Gateway screening can be performed on all in-bound messages from another network. Gateway screening can also be performed on all outgoing network management messages. Since gateway screening can occur on the link interface modules (LIMs) and the application service modules (ASMs), the deployment of the gateway screening feature does not impact link throughput capacity, and can contribute to less than 5 milliseconds increase to cross-STP delays.

[0379] (c) Local Number Portability (LNP)

[0380] In a preferred embodiment, local number portability (LNP) can be integrated into the EAGLE architecture of STPs 250, 252. An advantage of the integration of LNP functionality is that it eliminates the need for costly external LNP databases, and associated transmission equipment. In one embodiment, LNP portability can support, complete scalability in configurations ranging from 500,000 translation entries and up to more than several million translation entries for very large metropolitan serving areas (MSAs).

[0381] (d) STP to LAN Interface

[0382] In a preferred embodiment, the STP-to-LAN interface of the EAGLE architecture can allow the user to connect external data collection or processing systems directly to STPs 250, 252 via a TCP/IP protocol. In this embodiment, the STP-to-LAN interface could be used to carry SS7 signaling over IP packets.

[0383] (e) ANSI to ITU Gateway

[0384] In a preferred embodiment, STPs 250, 252 can include a feature referred to as the ANSI-ITU gateway feature. In a preferred embodiment, the ANSI-ITU feature of STPs 250, 252 allows STPs 250, 252 to interconnect three types of signaling networks, i.e., ITU international, ITU national and ANSI, by means of three different message signaling unit (MSU) protocols. In a preferred embodiment of STPs 250, 252, the ANSI-ITU feature can allow a smooth transition from an all-ANSI network to a combined ANSI-ITU network.

[0385] d. Services Control Points (SCPs)

[0386] FIG. 6A depicts off-switch called processing abstraction diagram 600 showing communication mechanisms between soft switch and STPs. FIG. 6A includes at the gateway-facing layer, soft switch processing 604 which can use the IPDC protocol 602, or alternatively, the Network Access Server (NAS) Messaging Interface (NMI) protocol to interface with access servers, or the messaging gateway control protocol (MGCP). IPDC protocol 602 provides a protocol for communications between soft switches and respectively TGs, AGs, NASs and ANSs. Soft switch processing 604 uses IPDC for gateway communication and uses off-switch call processing 606 to access SCPs 608, 614, 618, 620.

[0387] SS7 TCAP 608 is connected to SCP 610 an off-network SCP, via STP 250. IP TCAP 614 is connected to SCP 612. SCP 616 is connected to custom IP 618. SCP 214 is an on-network SCP and is connected via INAP/IP 620.

[0388] FIG. 6A represents how some interfaces to soft switch 204 sit on top of a common interface used by soft switch 204 to handle off-switch call processing. SCPs and other devices, such as route servers, can use this common interface. For example, SCP 610 is an off-network or off-switch SCP, meaning that it is not within soft switch site 104.

[0389] Off-switch call processing abstraction layer 606 is intended to be a flexible interface, similar to TCAP in function, that allows interaction between any type of SCP (or other call processing logic) and soft switch 204. The abstraction layer is so designed that interfaces to a set of call processors supporting a specific function (e.g., 800 service), contain the same types of data, and can all map arguments to data elements supported by off-switch call processing abstraction layer 606. The field values for messages supplied by off-switch call processing abstraction layer 606 are identified in this section (i.e., describing SCPs) and also in the section describing route servers below.

[0390] The SCPs can be off-switch call processing servers, which support intelligent services within the telecommunications network SCPs 610, 612, and 616 can support such services as, for example, account code verification and toll free/800 services, local number portability (LNP), carrier ID identification, and card services.

[0391] Other services and capabilities of SCPs 610, 612, and 616 include basic toll-free services, project account code (PAC) services, local number portability (LNP) services, 800 carrier ID services, calling name (CNAM) services, advanced toll-free/network automatic call distribution (ACD) services, customer premise toll-free routing services, one number (or follow-me) services, and SCP gateway for customer premises equipment (CPE) route selection services. These services are recognized by those skilled in the art.

[0392] Additional services and capabilities can include intelligent peripherals. Intelligent peripherals can include calling card, debit card, voicemail, unified messaging, conference calling, and operator services. These peripherals are recognized by those skilled in the art.

[0393] FIG. 6B illustrates intelligent network architecture 622. FIG. 6B includes gateway site 110, communicating via data network 112, to soft switch 204. The communication can be performed by the H.323 protocol or the IPDC protocol. Soft switch 204 gains signaling information from signaling network 114 via STP 250, through SS7 gateway 208.

[0394] Gateway site 110, in intelligent network architecture 622, is connected to multiple off-network service providers. Off network service providers include local exchange carrier (LEC) 624, inter-exchange (IXC) carrier 626 and operator services service bureau 628. Thus calls coming in from LEC 624 or from IXC 626 into gateway site 110, if identified as an operator call, may be routed to off-network operator services 628.

[0395] Soft switch 204 does not dictate any particular SCP interface, but it is assumed that this interface will support the following types of interactions: (1) route request; (2) route response; (3) call gapping; and (4) connect to resource.

[0396] A route request is a message sent from soft switch 204 to an external SCP 610. The route request is sent to request a translation service from SCP 610, for example, to translate disclosed digits to a destination number.

[0397] A route response is a message sent from SCP 610 to soft switch 204 in response to a route request. The route response includes a sequence of prioritized destinations for the call. SCPs that perform routing can return a list of prioritized destinations. These destinations can be, for example, any combination of destination numbers or circuit groups. If SCP 610 returns a destinations number, soft switch 204 can attempt to route to that destination number using the least cost routing logic included in route server 212. If SCP 610 returns a circuit group, the soft switch 204 can use route server 212 to select an available circuit in that group. Soft switch 204 can try to terminate to the specified destinations in the prioritized order that the destinations are returned from SCP 610.

[0398] The interface that can be used by soft switch 204, in order to interact with SCPs 214, 610, 612, and 616, is called the off-switch call processing (OSCP) interface. This interface is also used for route server 212 and any other call processing engines. OSCP is represented in FIG. 6A as off-switch call processing abstraction layer 606. Tables 8, 9, 10, and 11 identify the fields in the OSCP route request and route response messages, which are necessary for 800 and account code processing service calls.

[0399]

TABLE 8
800 Route Request
	SCP Route Request
	Parameter	800 SCP - Route Request Value
	Message Type	800 Route Request
	Call Reference	Unique call identifier
	Requesting Soft-Switch	Soft Switch ID
	Bearer Capability	Voice, Data or Fax
	Destination type	DDD (an 8XX number was dialed)
	Destination	Dialed 8XX number
	Originating LATA	LATA from IAM or from DAL profile
	Calling Number	ANI
	Originating station type	II-digits from IAM or DAL profile
	Collected Digits	Not Used for 800 processing.

[0400]

TABLE 9
Account Code Route Request
OSCP Route Request
Parameter	Account Code SCP - Route Request Value
Message Type	Account Code Route Request
Call Reference	Unique call identifier
Requesting Soft-Switch	Soft Switch ID
Bearer Capability	Not used for Account Code processing
Destination type	Not used for Account Code processing
Destination	Not used for Account Code processing
Originating LATA	LATA from IAM or from DAL profile
Calling Number	ANI
Originating station type	II-digits from IAM or DAL profile
Collected Digits	Not Used for Account Code processing

[0401]

TABLE 10
800 Route Response
OSCP Route Request Parameter	800 SCP - Route Response Value
Message Type	800 Route Response
Call Reference	Unique call identifier
Result Code	Success/fail
Number of responses	Number of responses sent from the
	SCP
Destination circuit group - 1	Terminating circuit group for the first
	route if the SCP identifies circuit groups
Destination circuit - 1	Not used for 800 processing
Outpulse digits - 1	Outpulse digits for selected termination
Destination number - 1	Destination number for the first route
Destination Soft Switch - 1	Not used for 800 processing
Destination circuit group - N	Terminating circuit group for the Nth
	route, if the SCP identifies circuit
	groups
Destination circuit - N	Not used for 800 processing
Outpulse digits - N	Outpulse digit format for selected
	circuit on the Nth route
Destination number - N	Destination number for the Nth route
Destination Soft Switch - N	Not used for 800 processing

[0402]

TABLE 11
Account Code Route Response
	Account Code SCP - Route Response
OSCP Route Request Parameter	Value
Call Reference	Unique call identifier
Result Code	Success/fail
Number of responses	0 - this is a success/fail response
Destination circuit group - 1	Not used for account code processing
Destination circuit - 1	Not used for account code processing
Outpulse digits - 1	Not used for account code processing
Destination number - 1	Not used for account code processing
Destination Soft Switch - 1	Not used for account code processing
Destination circuit group - N	Not used for account code processing
Destination circuit - N	Not used for account code processing
Outpulse digits - N	Not used for account code processing
Destination number - N	Not used for account code processing
Destination Soft Switch - N	Not used for account code processing

[0403] A route response can also include an indication to initiate a call gapping for a congested call. Call gapping refers to a message sent from an SCP to a soft switch to control the number and frequency of requests sent to that SCP. The call gapping response can indicate a length of time for which gapping should be active, as well as a gap interval, at which the soft switch should space requests going to the SCP. Call gapping can be activated on the SCP for each individual service supported on the SCP. For example, if SCP 214 supports 800 and project account code queries, it may gap on 800, but not on project account codes. Alternatively, SCP 214 can gap on project codes but not on 800, or can gap on both or neither.

[0404] A connect-to resource is a response that is sent from the SCP to the soft switch in response to a route request for requests that require a call termination announcement to be played.

[0405] FIG. 6C illustrates additional off-switch services 630. For example, calling card interactive voice response (IVR) 632 services can be provided off-switch, similarly to operator services 628. FIG. 6C also depicts on-switch SCP services. Specifically, project account codes (PAC) SCP 214a and basic toll-free SCP 214b communicate with soft switch 204 via an INAP/IP protocol 620. Project account codes are discussed further below. Basic toll-free services are also discussed further below.

[0406] FIG. 6D depicts additional services 634. For example, FIG. 6D depicts service node/IP 656, which can be a voice services platform with a voice over IP (VOIP) interface on data network 112. In addition, network IVR 654 is depicted. Network IVR 654 is an IVR that connects to data network 112. Network IVR 654 can communicate with soft switch 204 via the IPDC protocol. Network IVR 654 is also in communication with an advanced toll-free SCP 648, via the SR-3511 protocol.

[0407] Advanced toll-free SCP 648 is in communication with soft switch 204 via INAP/IP protocol 620. Advanced toll-free SCP 648 is also in communication with computer telephony integration (CTI) server 650. CTI server 650 can communicate with an automatic call distributor (ACD) 652.

[0408] FIG. 6D also depicts an IP client connected via a customer network into data network 112. Specifically, IP-Client 660 is connected to data network 112 via customer network 658. Customer network 658 is connected to data network 112 and communicates via an H.323 protocol or via IPDC protocol 602 through data network 112 to soft switch 204. Soft switch 204 is in communication with SS7 gateway 208 via a TCAP/SS7 608 protocol. SS7 gateway 208 is in turn in communication with STP 208 via a TCAP/SS7 608 protocol. STP 208 in turn can communicate with SCPs in the SS7 network via the TCAP/SS7 608 protocol. Specifically, STP 208 can communicate with local number portability (LNP) SCP 636 and also 800 carrier SCP 610. Soft switch 204 can still communicate with PAC SCP 214A and basic toll-free SCP 214B via an INAP/IP 620 protocol. Soft switch 204 can also communicate with an SCP gateway 638 via an INAP/IP 620 protocol. SCP gateway 638 can be used to communicate with customer premises toll-free 640 facilities. Customer premises toll-free 640 facilities can communicate with computer telephony integration (CTI) server 642. CTI server 642 can be in communication with an automatic call distributor (ACD) 644.

[0409] The H.323 Recommendation will now be briefly overviewed with reference to FIGS. 71A-E The H.323 standard provides a foundation for, for example, audio, video, and data communications across IP-based networks, including the Internet. By complying with the H.323 Recommendation, multimedia products and applications from multiple vendors can interoperate, allowing users to communicate without concern for compatibility. H.323 will be the foundation of future LAN-based products for consumer, business, entertainment, and professional applications.

[0410] H.323 is an umbrella recommendation from the International Telecommunications Union (ITU) that sets standards for multimedia communications over Local Area Networks (LANs) that do not provide a guaranteed Quality of Service (QoS). These networks dominate today's corporate desktops and include packet-switched TCP/IP and IPX over Ethernet, Fast Ethernet and Token Ring network technologies. Therefore, the H.323 standards are important building blocks for a broad new range of collaborative, LAN-based applications for multimedia communications.

[0411] The H.323 specification was approved in 1996 by the ITU's Study Group 16. Version 2 was approved in January 1998. The standard is broad in scope and includes both stand-alone devices and embedded personal computer technology as well as point-to-point and multipoint conferences. H.323 also addresses call control, multimedia management, and bandwidth management as well as interfaces between LANs and other networks.

[0412] H.323 is part of a larger series of communications standards that enable videoconferencing across a range of networks. Known as H.32X, this series includes H.320 and H.324, which address ISDN and PSTN communications, respectively.

[0413] FIG. 58A depicts a block diagram of the H.323 architecture for a network-based communications system 5800. H.323 defines four major components for network-based communications system 5800, including: terminals 5802, 5804 and 5810, gateways 5806, gatekeepers 5808, and multipoint control units 5812.

[0414] Terminals 5802, 5804, 5810 are the client endpoints on the LAN that provide real-time, two-way communications. All terminals must support voice communications; video and data are optional. H.323 specifies the modes of operation required for different audio, video, and/or data terminals to work together. It is the dominant standard of the next generation of Internet phones, audio conferencing terminals, and video conferencing technologies.

[0415] All H.323 terminals must also support H.245, which is used to negotiate channel usage and capabilities. FIG. 58B depicts an exemplary H.323 terminal 5802. Three other components are required: Q.931 for call signaling and call setup, a component called Registration/Admission/Status (RAS), which is a protocol used to communicate with a gatekeeper 5808; and support for RTP/RTCP for sequencing audio and video packets.

[0416] Optional components in an H.323 terminal are video codecs, T.120 data conferencing protocols, and MCU capabilities (described further below).

[0417] Gateway 5806 is an optional element in an H.323 conference. FIG. 59 depicts an example H.323 gateway. Gateways 5806 provide many services, the most common being a translation function between H.323 conferencing endpoints and other terminal types. This function includes translation between transmission formats (i.e. H.225.0 to H.221) and between communications procedures (i.e. H.245 to H.242). In addition, gateway 5806 also translates between audio and video codecs and performs call setup and clearing on both the LAN side and the switched-circuit network side. FIG. 59 shows an H.323/PSTN Gateway 5806.

[0418] In general, the purpose of gateway 5806 is to reflect the characteristics of a LAN endpoint to an SCN endpoint and vice versa. The primary applications of gateways 5806 are likely to be:

• • [0419] Establishing links with analog PSTN terminals.
  • [0420] Establishing links with remote H.320-compliant terminals over ISDN-based switched-circuit networks.
  • [0421] Establishing links with remote H.324-compliant terminals over PSTN networks

[0422] Gateways 5806 are not required if connections to other networks are not needed, since endpoints may directly communicate with other endpoints on the same LAN. Terminals communicate with gateways 5806 using the H.245 and Q.931 protocols.

[0423] With the appropriate transcoders, H.323 gateways 5806 can support terminals that comply with H.310, H.321, H.322, and V.70.

[0424] Many gateway 5806 functions are left to the designer. For example, the actual number of H.323 terminals that can communicate through the gateway is not subject to standardization. Similarly, the number of SCN connections, the number of simultaneous independent conferences supported, the audio/video/data conversion functions, and inclusion of multipoint functions are left to the manufacturer. By incorporating gateway 5806 technology into the H.323 specification, the ITU has positioned H.323 as the glue that holds the world of standards-based conferencing endpoints together.

[0425] Gatekeeper 5808 is the most important component of an H.323 enabled network. It acts as the central point for all calls within its zone and provides call control services to registered endpoints. In many ways, an H.323 gatekeeper 5808 acts as a virtual switch.

[0426] Gatekeepers 5808 perform two important call control functions. The first is address translation from LAN aliases for terminals and gateways to IP or IPX addresses, as defined in the RAS specification. The second function is bandwidth management, which is also designated within RAS. For instance, if a network manager has specified a threshold for the number of simultaneous conferences on the LAN, the Gatekeeper 5808 can refuse to make any more connections once the threshold is reached. The effect is to limit the total conferencing bandwidth to some fraction of the total available; the remaining capacity is left for e-mail, file transfers, and other LAN protocols. FIG. 60 depicts a collection of all terminals, gateways 5806, and multipoint control units 5812 which can be managed by a single gatekeeper 5808. This collection of elements is known as an H.323 Zone.

[0427] An optional, but valuable feature of a gatekeeper 5808 is its ability to route H.323 calls. By routing a call through a gatekeeper, it can be controlled more effectively. Service providers need this ability in order to bill for calls placed through their network. This service can also be used to re-route a call to another endpoint if a called endpoint is unavailable. In addition, a gatekeeper 5808 capable of routing H.323 calls can help make decisions involving balancing among multiple gateways. For instance, if a call is routed through a gatekeeper 5808, that gatekeeper 5808 can then re-route the call to one of many gateways based on some proprietary routing logic.

[0428] While a gatekeeper 5808 is logically separate from H.323 endpoints, vendors can incorporate gatekeeper 5808 functionality into the physical implementation of gateways 5806 and MCUs 5812.

[0429] Gatekeeper 5808 is not required in an H.323 system. However, if a gatekeeper 5808 is present, terminals must make use of the services offered by gatekeepers 5808. RAS defines these as address translation, admissions control, bandwidth control, and zone management.

[0430] Gatekeepers 5808 can also play a role in multipoint connections. To support multipoint conferences, users would employ a Gatekeeper 5808 to receive H.245 Control Channels from two terminals in a point-to-point conference. When the conference switches to multipoint, the gatekeeper can redirect the H.245 Control Channel to a multipoint controller, the MC. Gatekeeper 5808 need not process the H.245 signaling; it only needs to pass it between the terminals 5802, 5804, 5808 or the terminals and the MC.

[0431] LANs which contain Gateways 5806 could also contain a gatekeeper 5808 to translate incoming E.164 addresses into Transport Addresses. Because a Zone is defined by its gatekeeper 5808, H.323 entities that contain an internal gatekeeper 5808 require a mechanism to disable the internal function so that when there are multiple H.323 entities that contain a gatekeeper 5808 on a LAN, the entities can be configured into the same Zone.

[0432] The Multipoint Control Unit (MCU) 5812 supports conferences between three or more endpoints. Under H.323, an MCU 5812 consists of a Multipoint Controller (MC), which is required, and zero or more Multipoint Processors (MP). The MC handles H.245 negotiations between all terminals to determine common capabilities for audio and video processing. The MC also controls conference resources by determining which, if any, of the audio and video streams will be multicast. MCU 2112 is depicted in FIG. 61.

[0433] The MC does not deal directly with any of the media streams. This is left to the MP, which mixes, switches, and processes audio, video, and/or data bits. MC and MP capabilities can exist in a dedicated component or be part of other H.323 components. A soft switch includes some functions of an MP. An access server, also sometimes referred to as a media gateway controller, includes some of the functions of the MC. MCs and MPs are discussed further below with respect to the IPDC protocol.

[0434] Approved in January of 1998, version 2 of the H.323 standard addresses deficiencies in version 1 and introduces new functionality within existing protocols, such as Q.931, H.245 and H.225, as well as entirely new protocols. The most significant advances were in security, fast call setup, supplementary services and T.120/H.323 integration.

[0435] (1) Project Account Codes

[0436] Project Account Codes can be used for tracking calls for billing, invoicing, and Class of Service (COS) restrictions. Project account code (PAC) verifications can include, for example, types Unverified Unforced, Unverified Forced, Verified Forced, and Partially Verified Forced. A web interface can be provided for a business customer to manage its accounts. The business customer can use the web interface to make additions, deletions, changes, and modifications to PAC translations without involvement of a carrier's customer service department.

[0437] An example of call processing using PACs follows. PAC SCP 214a of FIG. 6C can receive validation requests from Soft-Switch 204 after Soft-Switch 204 has requested and received PAC digits. The PAC digits can be forwarded to SCP 214a for verification. When SCP 214a receives this request, SCP 214a can compare the entire PAC, if the PAC type is Verified Forced, against a customer PAC table. SCP 214a can compare only the verified portion of the PAC, if the PAC type is Partially Verified Forced, against the customer PAC table.

[0438] The PAC digits can be sent from Soft-Switch 204 to SCP 214a in the ‘Caller Entered Digits’ field. The indicated customer can be sent from Soft-Switch 204 to SCP 214a in the ‘Customer’ field.

[0439] (2) Basic Toll-Free

[0440] Basic Toll-Free Service SCP 214b can translate a toll free (e.g., 800 and 888) number to a final routing destination based on a flexible set of options selected by a subscriber. Basic toll-free service supports e.g., 800 and 8XX Service Access Codes. Subscriber options can include, for example: 1) routing based on NPA or NPA-NXX of calling party; 2) routing based on time of day and day of week; 3) routing based on percent distribution; 4) emergency override routing; and 5) blocking based on calling party's NPA or NPA-NXX or ii-digits.

[0441] An exemplary embodiment of basic toll-free SCP 214b is a GENESYS Network Interaction Router available from GENESYS of San Francisco, Calif. The GENESYS Network Interaction Router product suite provides Basic Toll-Free service. Soft-Switch 204 can send route requests to SCP 214b for any Toll Free numbers that Soft-Switch 204 receives. SCP 214b can then attempt to route the call using a route plan or trigger plan that has been defined for that Toll Free (dialed) number. SCP 214b can have several possible responses to a soft switch routing request, see Table 10 above. Using the subscriber routing option (described in the previous paragraph) SCP 214b can return a number translation for the Toll Free number. For example, SCP 214b can receive a dialed number of 800-202-2020 and return a DDD such as 303-926-3000. Alternatively, SCP 214b can return a circuit identifier. SCP 214b usually returns a circuit identifier when the termination is a dedicated trunk to a customer premise equipment (CPE). Then if SCP 214b determines that it can not route the call or has determined to block the call (per the route plan), SCP 214b returns a ‘route to resource’ response to Soft-Switch 204 with an announcement identifier. In this case Soft-Switch 204 can connect the calling party with Announcement Server 246 for the playing of an announcement and then disconnect the caller.

[0442] SCP 214b can store call events in CDR database tables on SCP 214b. CDR database tables can then be replicated to Master Network Event Database 226 using a data distributor 222, such as, for example, the Oracle Replication Server.

[0443] e. Configuration Server (CS) or Configuration Database (CDB)

[0444] The configuration server 206 will now be described in greater detail with reference to FIG. 2. Configuration server 206 supports transaction requests to a database containing information needed by network components. Configuration server 206 supports queries by voice network components during initialization and call processing. The data contained within configuration server 206 databases can be divided into two types. The first type of data is that used to initialize connections between components. Examples of such data used to initialize connections between network components include the following: IP address and port numbers for all servers that soft switch 204 must communicate with; information indicating initial primary/secondary/tertiary configurations for server relationships; configuration information for access gateways 238, 240 and trunking gateways 232, 234; number and configuration of bays, modules, lines and channels (BMLC); relationship of module, line and channels to originating point code (OPC), destination point code (DPC) and circuit identification code (CIC) values; relationship of module, line and channels to trunk groups; call processing decision trees for soft switch processing; mapping of OPC, DPC and CIC values soft switches 204; mapping of access server 254, 256 ports to dedicated access line (DAL) identifiers and customer IDs; tables necessary to support class of service (COS) restrictions; local access transport area (LATA) tables; state tables; and blocked country code tables.

[0445] The second set of data can be categorized as that data needed by soft switch 204 for use during call processing. This type of data includes customer and DAL profiles. These profiles define the services that a customer has associated with their ANIs or DALs. This information can include information describing class of service restrictions and account code settings.

[0446] The database of configuration server 206 contains voice network topology information as well as basic data tables necessary for soft switch 204 call processing logic. Configuration server 206 is queried by soft switches 204 at start-up and upon changes to this information in order to set up the initial connections between elements of telecommunications network 200. Configuration server 206 is also queried by soft switches 204 in order to configure initial settings within soft switch 204.

[0447] Configuration server 206 contains the following types of information: IP address and port numbers for all servers that soft switch 204 must communicate with; information indicating initial primary/secondary/tertiary configurations for server relationships; configuration information for AGs 238, 240 and TGs 232, 234; call processing decision trees for soft switch 204 call processing; mapping of OPC, DPC and CIC values to soft switch 204; mapping of access server 254, 256 ports to DALs and customer IDs; and tables necessary to support COS restrictions.

[0448] Configuration information for AGs and TGs includes: number and configuration of bays, modules, lines and channels; relationship of modules, line and channels to OPC, DPC and CIC values; and relationship of module, line and channels to trunk groups.

[0449] Tables necessary to support class of service restrictions include: LATA tables; state tables; and blocked country code tables.

[0450] Configuration server 206 also contains information related to customer trigger plans and service options. Customer trigger plans provide call processing logic used in connecting a call. Configuration server 206 information is queried during call processing to identify the service logic to be executed for each call.

[0451] The information that soft switch 204 uses to look-up customer profile data is the ANI, trunk ID or destination number for the call. The information that will be returned defines the call processing logic that is associated with ANI, trunk ID or destination number or trunk group.

[0452] Table 12 includes an example of a customer profile query.

[0453]

TABLE 12
Customer Profile Query
	Customer Profile Query Field	Value
	Customer identification type	DDD, DAL ID, Customer ID
	Customer identification	The value for the DDD, Trunk ID

[0454] Table 13 includes an example of a customer profile query response provided by configuration server 206.

[0455]

TABLE 13
Customer Profile Query Response
Customer Profile Response Field	Value
Customer identification type	DDD, Trunk ID
Customer Identification	The value for the DDD, Trunk ID
Class of Service restriction Type	None
	Intrastate
	IntraLATA
	Domestic
	Domestic and selected international
Selected International List ID	When the class of service restriction
	type is domestic and selected
	international destinations, this is
	an index to the list of allowed
	international destinations.
Account Code Type	None
	Verified Forced
	Unverified Forced
	Unverified Unforced
	Partially Verified Forced
Account code length	2-12 digits
Local Service Area, State, LATA,	For queries on numbers, these fields
and Country	are identify the geographic
	information that is necessary to
	process the call.

[0456] Configuration server 206 interfaces to components. Configuration server 206 receives provisioning and reference data updates from data distributor 222 of provisioning component 222. Configuration server 206 also provides data to soft switch 204 for call processing. Configuration server 206 is used by soft switch 204 to retrieve information necessary for initialization and call processing. Information that soft switch 204 retrieves from configuration server 206 during a query is primarily oriented towards customer service provisioning and gateway site 108, 110 port configuration. Configuration server 206 database tables accessible to soft switch 204 include the following: toll free number to SCP type translation; SCP type to SCP translation; CICs profiles; ANI profiles summary; ANI profiles; account code profiles; NPA/NXX; customer profiles; customer location profiles; equipment service profiles; trunk group service profile summaries; trunk group services; high risk countries; and selected international destinations.

[0457] Configuration server 206 uses a separate physical interface for all SNMP messages and additional functions that may be defined. Examples of additional functions that may be defined include provisioning, updating, and the passage of special alarms and performance parameters to configuration server 206 from the NOC.

[0458] In an alternative embodiment, the functionality of configuration server 206 can be combined with that of route server 212 in a single network component. In an additional embodiment of the invention, the functions of either or both of CS 206 and RS 212 can be performed by application logic residing on soft switch 204.

[0459] f. Route Server (RS)

[0460] FIG. 8A depicts route server support for an exemplary soft switch site 800. FIG. 8A includes route server 212a and route server 212b. Route servers 212a and 212b are connected via redundant connections to soft switches 204a, 204b and 204c. Soft switches 204a, 204b and 204c are in turn connected to gateway sites via data network 112 (not shown). For example, soft switch 204a is in communication with TG 232a and TG 232b. Similarly soft switch 204b is in communication with AG 238a and TG 234a. Soft switch 204c is in turn in communication with AG 238b and AG 240a. It would be apparent to a person skilled in the art that additional TGs and AGs, as well as other gateway site devices, (such as a NAS device) can also be in communication with soft switches 204a, 204b and 204c.

[0461] Route server 212 will now be described in further detail with reference to FIG. 2. Route server 212 provides at least two functions. Route server 212 performs the function of supporting the logic for routing calls based upon a phone number. This routing, performed by route server 212, results in the selection of one or more circuit groups for termination.

[0462] Another function of route server 212 is the tracking and allocation of network ports. As shown in FIG. 8A, route server 212 (collocated with other components at soft switch site 104) services routing requests for all soft switches 204a, 204b, 204c at that site. Therefore, route server 212 tracks port resources for all TGs 232a, 232b and 234a and AGs 238a, 238b and 240a that are serviced by soft switches 204a, 204b and 204c at soft switch site 104.

[0463] (1) Route Server Routing Logic

[0464] The routing logic accepts translated phone numbers and uses anywhere from full digit routing to NPA-based routing to identify a terminating circuit group. Routing logic selects the translation based upon the best match of digits in the routing tables. An exemplary routing table is illustrated as Table 14.

[0465]

TABLE 14
Number Routing Table
		Terminating
	Number	Circuit Group	Priority	Load
	303-926-3000	34	1	50%
	303-926-3000	56	1	50%
	303-926-3000	23	2
	303-926	76	1
	303	236	1
	44 1784 470 330	564	1
	44	923	1

[0466] In Table 14, there are five entries that can match the dialed number “303-926-3000”. The first route choice is the one that has a full match of digits with priority one. Since there are two entries with full matching digits, and which are marked as priority one, the load should be distributed as shown in the load column, (i.e., 50% load share is distributed to the first, and 50% load share is distributed to the second). The second route choice is the entry with a full digit match, but marked with the lower priority of two. The third route match is the one that has a matching NPA-NXX. The last route choice is the one that has a matching NPA only.

[0467] In situations where there are multiple route choices for a DDD number (i.e., the number of called party 120) route server 212 must take into consideration several factors when selecting a terminating circuit group. The factors to be considered in selecting a terminating circuit group include: (1) the percent loading of circuit groups as shown in the load column of Table 14; (2) the throttling use of trunk groups to avoid overloaded networks; (3) the fact that end office trunk groups should be selected before tandem office trunk groups; and (4) routing based upon negotiated off-network carrier agreements.

[0468] Agreements should be negotiated with off-network carriers to provide the flexibility to route calls based upon benefits of one agreement another. The following types of agreements can be accounted for: (1) commitments for the number of minutes given to a carrier per month or per year; (2) the agreement that for specific NPA or NPA-NXX sets, one carrier may be preferred over another; (3) the agreement that international calls to specific countries may have preferred carriers; (4) the agreement that intra-LATA or intra-state calls originating for certain areas may have a preferred carrier in that area; and (5) the agreement that extended area service calls may have a preferred carrier.

[0469] The logic for route server 212 can include routing for international calls. In the example shown in Table 14, it is possible to have fully specified international numbers, or simply specified routing, for calls going to a particular country. As with domestic numbers, the routing logic should select the table entry that matches the most digits within the dialed number, (i.e. the number of called party 120).

[0470] (2) Route Server Circuit Management

[0471] Once a terminating circuit group has been identified, route server 212 needs to allocate a terminating circuit within the trunk group. The selection of a terminating circuit is made by querying the port status table. Table 15A shows an exemplary port status table. The results of a query to port status Table 15A yields the location and allocation of a circuit. Route server 212 can use algorithms to select circuits within the trunk group. Each circuit group can be tagged with the selected algorithm that should be used when selecting circuits within that group.

[0472] Example algorithms to select circuits within the group include: (1) the most recently used circuit within a circuit group; (2) the least recently used circuit within a circuit group; (3) a circular search, keeping track of the last used circuit and selecting the next available circuit; (4) the random selection of an available circuit within a circuit group; and (5) a sequential search of circuits within a circuit group, selecting the lowest numbered available circuit. Table 15A illustrates the association between a circuit group and the selection algorithm that should be used to allocate ports from that group.

[0473]

TABLE 15A
Circuit Group Parameters
Circuit group	Selection algorithm
34	Random
35	Least recently used

[0474]

TABLE 15B
Port Status
Circuit group	Port	Status
34	3-4-6-1	Avail
34	3-4-6-2	In-use
34	3-4-6-3	avail
34	3-4-6-4	avail

[0475] Table 15B includes the circuit group (that a port is a member of), a port identifier, and the current status of that port. The port identifier shown in Table 15B assumes the type of port identification currently used in the IPDC protocol, where the port is represented by a bay, module, line and channel (BMLC). It would be apparent to persons skilled in the art that other methods of identifying a port can be used.

[0476] The function of route server 212 is to provide least-cost routing information to soft switch 204, in order to route a call from calling party 102 to called party 120. In addition to providing routing information, route server 212 allocates ports for terminating calls on the least cost routes, e.g., allocating ports within TGs 232, 234. Route server pair 212 is located at each of soft switch sites 104, 106, 302 and services all soft switches 204a, 204b, 204c, 304a, 304b, 304c, 306a, 306b and 306c at that site. (Refer to FIG. 3.)

[0477] Route server 212 interacts with at least two other voice network components. Route server 212 interacts with configuration server 206. Configuration server 206 is used to retrieve initial information on route server 212 start-up to set up the initial routing tables in preparation for receiving requests from soft switches 204a, 204b and 204c, for example.

[0478] Route server 212 also interfaces with soft switch 204. Soft switch 204 can send route requests to route server 212 that contain either a phone number or a circuit group. Route server 212 can perform its least cost routing logic to first select a terminating circuit group for the call. Using that circuit group, route server 212 can then select and allocate a terminating circuit.

[0479] A description of the messages and model of interaction between route server 212 and soft switch 204 follows. Route server 212 is used by soft switch 204 to identify the possible network terminations for a call. Soft switch 204 passes a DDD number, an international DDD (IDDD) number, or a circuit group to route server 212 in a “route request” message. Using this information from soft switch 204, route server 212 can return the port on an AG 238, 240 or TG 232, 234 that should be used to terminate this call. Using this port information, soft switch 204 can then signal the originating and terminating TG or AG to connect the call through data network 112.

[0480] The route server 212 will now be described further with reference to FIG. 2B. FIG. 2B depicts a sample call flow 258, illustrating how soft switch 204 interacts with route server 212 to identify a terminating port for a call.

[0481] In exemplary call flow 258, the call originates and terminates at different sites, specifically, gateway sites 108, and 110. Since exemplary call flow 258 originates and terminates at different sites, the cooperation of the originating soft switch 204 and terminating soft switch 304 and route servers 212, 314, respectively to identify the terminating circuit. Portions of the call flow will now be described in greater detail.

[0482] As depicted in step 259, for calls arriving on SS7 signal trunks, soft switch 204 receives call arrival notifications in the form of IAM messages. Upon receipt of the IAM message from SS7 GW 208, soft switch 204 performs some initial digit analysis to determine the type of the call.

[0483] In step 260, for calls involving customer features, soft switch 204 can use the ANI of calling party 102 (i.e., the telephone number of calling party 102) to query a customer profile database in configuration server 206. This is done to identify the originating customer's feature set. Each customer's feature set is known as a “trigger plan” for origination of the call. A trigger plan can be thought of as a flowchart which branches based on certain triggering events dependent on the caller's identity. Customer trigger plans 290 reside in a customer profile on configuration server 206.

[0484] In step 262, the customer profile database of configuration server 206 returns the customer trigger plan 290 to soft switch 204. Soft switch 204 can perform any processing necessary to implement the customer's specified originating triggers.

[0485] Application logic in soft switch 204 can then generate a translated number or an identification of the terminating circuit group for this call. For example, in the case of an 800 call, a translation may be requested as in step 265 of an SCP 214. SCP 214 converts the 800 number into a normal number for termination, and in step 266 returns the number to soft switch 204.

[0486] In step 267, in order to translate the translated number or circuit group into an egress port, soft switch 204 makes a route request to route server 212. The routing logic uses the NPA-NXX-XXXX to identify the terminating circuit group. Upon identifying the terminating circuit group, the route logic queries a circuit group to soft switch mapping table in route logic 294 of route server 212, to identify the target soft switch that handles the identified termination. For example, the target soft switch may be soft switch 304. It is important to note that there can be multiple route choices, and therefore there can be multiple soft switches 204, 304 supporting a single route request.

[0487] In step 268, route server 212 responds to soft switch 204 with the terminating circuit group. In this example, the terminating circuit group is included in trunks connected to trunking gateway 234, which is serviced by a different soft switch (namely soft switch 304) than originating soft switch 204. Therefore, route server 212 responds with the terminating circuit group and identifies soft switch 304 as the soft switch that handles that terminating circuit group.

[0488] In step 269, originating soft switch 204 initiates the connection from the origination to the termination, by requesting a connection from the originating trunking gateway 232. Trunking gateway 232, upon receipt of the set-up request from soft switch 204, allocates internal resources in trunking gateway 232.

[0489] TG 232 manages its own ports. In an example embodiment, TG 232 uses real time protocol (RTP) over UDP, and RTP sessions, which are ports used to implement an RTP connection. In step 270, TG 232 returns to soft switch 204 the IP address and listed RTP port.

[0490] In step 274, originating soft switch 204 issues a call setup command to terminating soft switch 304. This is the command identified by route server 212.

[0491] In step 276, soft switch 304 queries route server 314 to determine the termination port for the call. Specifically, soft switch 304 queries port status 298 of route server 314. The query in step 276, “passes in” as a parameter the terminating circuit group.

[0492] In step 278, route server 314 allocates a termination port and returns the allocated termination port to terminating soft switch 304.

[0493] In step 280, terminating soft switch 304 instructs the identified end point (i.e., trunking gateway 234) to reserve resources, and to connect the call. Terminating soft switch 304 passes in an IP address and an RTP port corresponding to the port that was allocated by originating TG 232.

[0494] In step 282, terminating TG 234 returns the allocated resources for the call to soft switch 304. For voice over IP (VOIP) connections, this includes the listed port and IP address for the terminating TG 234.

[0495] In step 284, terminating soft switch 304 returns to originating soft switch 204 the IP address of TG 234.

[0496] In step 286, originating soft switch 204 communicates with originating TG 232 in order to inform originating TG 232 of the listed port that was allocated by terminating TG 234. At this point, originating TG 232 and terminating TG 234 have enough information to exchange full duplex information.

[0497] In step 288, originating TG 232 acknowledges the receipt of the communication from soft switch 304 to soft switch 204.

[0498] Table 16A shows fields that can be included in a route request sent from soft switch 204 to route server 212. The route request can contain either a DDD number or a circuit group that requires routing. The route request message can also contain information about the call, collected from the IAM message, that is necessary to perform routing of this call. The route request message can also contain information about the call, necessary to perform routing of the call, which is obtained from the processing of the call. For example, in the case of an 800 call, this information can be a translated number.

[0499]

TABLE 16A
Values for Route Request sent to the Route Server
OSCP Route Request Parameter	Route Server - Route Request Value
Message Type	Route Server Route Request
Call Reference	Unique call identifier
Requesting Soft Switch	Soft Switch ID
Bearer Capability	Voice, Data or Fax
Destination type	DDD or circuit group
Destination	Fully translated DDD (or IDDD)
	number or circuit group ID
Originating LATA	LATA from IAM or from DAL profile
Calling Number	ANI
Originating station type	II-digits from IAM or DAL profile
Collected Digits	Not Used for Route Server

[0500] Table 16B shows fields which can be included in a response corresponding to the route response, sent from route server 212 back to soft switch 204.

[0501] Alternatively, each route response can include one route termination, and multiple consecutive route terminations can be determined with multiple route request/response transactions.

[0502]

TABLE 16B
Values for Route Response sent from the Route Server
Customer Profile Query Field	Route Server - Route Response Value
Message Type	Route Server Route Response
Call Reference	Unique call identifier
Result code	Success/Fail
Number of responses	Number of responses sent from the route
	server
Destination circuit group - 1	Terminating circuit group for the first
	route
Destination circuit - 1	Terminating circuit allocated by the route
	server for the first route
Outpulse digits - 1	Outpulse digit format for selected circuit
	on the first route
Destination number - 1	Destination number for the first route
Destination Soft Switch - 1	Soft switch servicing the circuit group for
	the first route
Destination circuit group - N	Terminating circuit group for the Nth
	route
Destination circuit - N	Terminating circuit allocated by the route
	server for the Nth route
Outpulse digits - N	Outpulse digit format for selected circuit
	on the Nth route
Destination number - N	Destination number for the Nth route
Destination Soft Switch - N	Soft switch servicing the circuit group for
	the Nth route

[0503] The route response message can contain a plurality of route terminations for the DDD or circuit group that was passed in as a parameter to route server 212. For example, the route response message can include 1 to 5 route choices. Each of the route choices of the route response message can include various fields of information. For example, each route choice can include the following information: the circuit group, the circuit, the outpulse digits, the destination number and the destination soft switch 304. Alternatively, each route response can include one route termination and multiple consecutive route terminations can be determined with multiple route request/route response transactions.

[0504] In situations where the selected circuit group is managed by the same route server 212 that serviced the route request, the response for that route can contain all the information about the destination. This is possible because route server 212 can identify and allocate the circuit within the circuit group.

[0505] In situations where another route server 314 services the selected circuit group, the response for that route only contains the circuit group and the destination soft switch 304. Originating soft switch 204 can then make a request to terminating soft switch 304 to query the terminating route server 314 for a circuit within the identified circuit group. The terminating soft switch 304 can then control the termination of the call.

[0506] g. Regional Network Event Collection Point (RNECP)

[0507] Referring back to FIG. 2A, regional network event collection points (RNECPs) 224 serve as collection points for real-time recorded call events that can be used by other systems. Soft switch 204 generates call data. This call data can be collected during call processing. Call data can also be generated by capturing events from other network elements. These network elements include internal soft switch site 104 components and external components. External components include SCPs 214, intelligent peripherals (IPs), AGs 238, 240, TGs 232, 234, and signaling components, such as STPs 250, 252, SSPs, and off switch SCPs.

[0508] Soft switch 204 provides call event data to RNECPs 224. Call data can be collected by a primary and secondary server at each RNECP 224, using high availability redundancy to minimize the possibility of potential data loss. Data from RNECPs 224 can then be transmitted in real-time to a centralized server, called the master network event database (MNEDB) 226. The MNEDB is discussed further below, with reference to FIG. 20.

[0509] FIG. 9 depicts a network event collection architecture 900. FIG. 9 includes western soft switch site 104, central soft switch site 106 and eastern soft switch site 302. Soft switch sites 104, 106, 302 are illustrated as including RNE CPs for collecting events and routing events to a master database. Specifically, western soft switch site 104 has soft switches 204a, 204b, 204c communicating via a local area network to RNECPs 224a, 224b. RNECPs can include disks 914, 916. RNECPs 224a, 224b can be in direct communication with, as well as can take a primary and a secondary role in communicating with, soft switches 204a, 204b, 204c.

[0510] RNECPs 224a, 224b can route network events through management virtual private network (VPN) 910 to master network event data center 912. Network events come through management VPN 910 and can be routed via redundant paths to MNEDB server 226a and/or MNEDB 226b. MNEDBs 226a and 226b can communicate with one another. MNEDB 226a uses disks 926a as primary storage for its database. MNEDB 226a also uses disks 926b for secondary storage. Similarly MNEDB 226b uses primary and secondary disks, 926a, 926b.

[0511] MNEDB 226a and MNEDB 226b can be collocated or can be geographically diverse. Thus master data center 912 can be either in one geographical area or in multiple locations.

[0512] Management VPN 910 also collects events from the other soft switch sites, i.e., central soft switch site 106 and eastern soft switch site 302. Central soft switch site 106 includes soft switches 304a, 304b, 304c redundantly connected via a LAN to RNECPs 902 and 904. RNECP 902 has disks 918 and 920.

[0513] Eastern soft switch site 302 includes soft switches 306a, 306b, 306c, redundantly connected via a LAN. RNECPs 906 and 908 RNECP 906 can have disks 922 and 924.

[0514] RNECPs 902 and 904 of central soft switch site 106 and RNECPs 906 and 908 of eastern soft switch site 302 can route network events for storage in disks 926a, 926b of MNEDBs 226a, 226b.

[0515] This is done by routing network events via management VPN 910 to master data center 912. The soft switches generate event blocks and push event block data to the RNECPs. (Event blocks are recorded call events that are created during call processing.)

[0516] Each RNECP 224a, 224b, 902, 904, 906 and 908 forwards collected event blocks (EBs) to (MNEDBs) 226a, 226b, which are centralized databases. RNECPs 224a, 224b, 902, 904, 906 and 908 use separate physical interfaces for all SNMP messages and additional functions that may be defined. Additional functions that can be defined include provisioning, updating, and passing special alarm and/or performance parameters to RNECPs from the network operation center (NOC).

[0517] RNECPs 224a, 224b, 902, 904, 906 and 908 are used by soft switches 204a, 204b, 204c, 304a, 304b, 304c, 306a, 306b and 306c to collect generated call events for use in such services as preparation of billing and reporting. At specific points throughout the duration of a call, soft switches 204a, 204b, 204c, 304a, 304b, 304c, 306a, 306b and 306c take the information that the soft switches have collected during call processing and push that data to the RNECPs.

[0518] Multiple types of data are logged by the soft switches during call processing of a normal one plus (1+) long distance call using account codes. Examples of data logged by an exemplary soft switch 204 include: a call origination record on the originating side, call termination information on the terminating side, an account code record, egress routing information, answer information on the originating side, call disconnect information on the originating side, call disconnect information on the terminating side, and final event blocks with call statistics.

[0519] Exemplary soft switch 204 can record data during call processing. Soft switch 204 transfers call events from RNECP 224 to MNEDB 226 for storage. This call event data, stored in MNEDB 226, can be used by various downstream systems for post-processing. These systems include, for example, mediation, end-user billing, carrier access billing services (CABS), fraud detection/prevention, capacity management and marketing.

[0520] There are at least two types of EBs. Example Mandatory and Augmenting event blocks can be explained as follows.

[0521] Mandatory EBs are created by soft switch 204 during the initial point-in-call analysis. Initial point-in-call analysis includes going off-hook, (picking up the telephone set) call <insert> setup, initial digit analysis (i.e., digit analysis prior to any external database transactions or route determinations).

[0522] Since other events such as, for example, session/call answer, and SCP transactions, can occur during call processing, soft switch 204 can create augmenting EBs. Augmenting EBs are EBs which can augment the information found in a mandatory EB. Events such as, for example, route determination, and answer indication, can be recorded in an augmenting EBs.

[0523] Examples of mandatory and augmenting EBs follow. For a complete illustration of these EBs, the reader is referred to Tables 20-143 and the corresponding discussions below. Specifically, Tables 20-48 provide mandatory EBs, Tables 49-60 provide augmenting EBs, and Tables 61-143 provide the call event elements that comprise the Ebs.

[0524] (1) Example Mandatory Event Blocks EBs

[0525] The following event blocks are examples of Mandatory Event Blocks:

• • [0526] EB 0001—Domestic Toll (TG Origination);
  • [0527] EB 0002—Domestic Toll (TG Termination);
  • [0528] EB 0003—Domestic Toll (AG Origination);
  • [0529] EB 0004—Domestic Toll (AG Termination);
  • [0530] EB 0005—Local (TG Origination);
  • [0531] EB 0006—Local (TG Termination);
  • [0532] EB 0007—Local (AG Origination);
  • [0533] EB 0008—Local (AG Termination);
  • [0534] EB 0009—8XX/Toll-Free (TG Origination);
  • [0535] EB 0010—8XX/Toll-Free (TG Termination);
  • [0536] EB 0011—8XX/Toll-Free (AG Origination);
  • [0537] EB 0012—8XX/Toll Free (AG Termination);
  • [0538] EB 0013—Domestic Operator Services (TG Termination);
  • [0539] EB 0014—Domestic Operator Services (AG Origination);
  • [0540] EB 0015—Domestic Operator Services (OSP Termination);
  • [0541] EB 0016—International Operator Services (TG Origination);
  • [0542] EB 0017—International Operator Services (AG Origination);
  • [0543] EB 0018—International Operator Services (OSP Termination);
  • [0544] EB 0019—Directory Assistance/555-1212 (TG Origination);
  • [0545] EB 0020—Directory Assistance/555-1212 (AG Origination);
  • [0546] EB 0021—Directory Assistance/555-1212 (DASP Termination);
  • [0547] EB 0022—OSP/DASP Extended Calls (Domestic);
  • [0548] EB 0023—OSP/DASP Extended Calls (International);
  • [0549] EB 0024—International Toll (TG Origination);
  • [0550] EB 0025—International Toll (AG Origination);
  • [0551] EB 0026—International Toll (TG Termination);
  • [0552] EB 0027—International Toll (AG Termination);
  • [0553] EB 0040—IP Origination; and
  • [0554] EB 0041—IP Termination.

[0555] (2) Augmenting Event Blocks EBs

[0556] The following event blocks are examples of Augmenting Event Blocks:

• • [0557] EB 0050—Final Event Block;
  • [0558] EB 0051—Answer Indication;
  • [0559] EB 0052—Ingress Trunking Disconnect Information;
  • [0560] EB 0053—Egress Trunking Disconnect Information;
  • [0561] EB 0054—Basic 8XX/Toll-Free SCP Transaction Information;
  • [0562] EB 0055—Calling Party (Ported) Information;
  • [0563] EB 0056—Called Party (Ported) Information;
  • [0564] EB 0057—Egress Routing Information (TG Termination);
  • [0565] EB 0058—Routing Congestion Information;
  • [0566] EB 0059—Account Code Information;
  • [0567] EB 0060—Egress Routing Information (AG Termination); and
  • [0568] EB 0061—Long Duration Call Information.

[0569] h. Software Object Oriented Programming (OOPs) Class Definitions

[0570] (1) Introduction to Object Oriented Programming (OOP)

[0571] In an example embodiment, soft switch site 104 comprises a plurality of object oriented programs (OOPs) running on a computer. As apparent to those skilled in the art, soft switch site 104 can alternatively be written in any form of software.

[0572] (a) Object Oriented Programming (OOP) Tutorial

[0573] OOPs can be described at a high level by defining object oriented programming classes. For example, in an embodiment of the present invention, soft switch 204 comprise an OOP written in an OOP language. Example languages include C++ and JAVA. An OOP model is enforced via fundamental mechanisms known as encapsulation, inheritance and polymorphism.

[0574] Encapsulation may be thought of as placing a wrapper around the software code and data of a program. The basis of encapsulation is a structure known as a class. An object is a single instance of a class. A class describes general attributes of that object. A class includes a set of data attributes plus a set of allowable operations (i.e., methods). The individual structure or data representation of a class is defined by a set of instance variables.

[0575] Inheritance is another feature of an OOP model. A class (called a subclass) may be derived from another class, (called a superclass) wherein the subclass inherits the data attributes and methods of the superclass. The subclass may specialize the superclass by adding code which overrides the data and/or methods of the superclass, or which adds new data attributes and methods.

[0576] Thus, inheritance represents a mechanism by which subclasses are more precisely specified. A new subclass includes all the behavior and specification of all of its ancestors. Inheritance is a major contributor to the increased programmer efficiency provided by the OOP. Inheritance makes it possible for developers to minimize the amount of new code they have to write to create applications. By providing the significant portion of the functionality needed for a particular task, classes on the inheritance hierarchy give the programmer a head start to program design and creation.

[0577] Polymorphism refers to having one object and many shapes. It allows a method to have multiple implementations selected based on the type of object passed into a method and location. Methods are passed information as parameters. These are parameters passed as both a method and an invocation of a method. Parameters represent the input values to a function that the method must perform. The parameters are a list of “typed” values which comprise the input data to a particular message. The OOP model may require that the types of the values be exactly matched in order for the message to be understood.

[0578] Object-oriented programming is comprised of software objects that interact and communicate with each other by sending one another messages. Software objects are often modeled from real-world objects.

[0579] Object-oriented programs of the present invention are hardware platform independent. Client computer 7008 in a preferred embodiment is a computer workstation, e.g., a Sun UltraSPARC Workstation, available from SUN Microsystems, Inc., of Palo Alto, Calif., running an operating system such as UNIX. Alternatively a system running on another operating system can be used, as would be apparent to those skilled in the art. Other exemplary operating systems include Windows/NT, Windows98, OS/2, Mac OS, and other UNIX-based operating systems. Exemplary UNIX-based operating systems include solaris, IRIX, LINUX, HPUX and OSF. However, the invention is not limited to these platforms, and can be implemented on any appropriate computer systems or operating systems.

[0580] An exemplary computer system is shown in FIG. 70B. Other network components of telecommunications network 200, such as, for example, route server 212 and configuration server 206, can also be implemented using computer system 7008 shown in FIG. 70B. Computer system 7008 includes one or more processors 7012. Processor 7012 is connected to a communication bus 7014.

[0581] Client computer 7006 also includes a main memory 7016, preferably random access memory (RAM), and a secondary memory 7018. Secondary memory 7018 includes hard disk drive 7020 and/or a removable storage drive 7022. Removable storage drive 7022 reads from and/or writes to a removable storage unit 7024 in a well known manner. Removable storage unit 7024 can be a floppy diskette drive, a magnetic tape drive or a compact disk drive. Removable storage unit 7024 includes any computer usable storage medium having stored therein computer software and/or data, such as an object's methods and data.

[0582] Client computer 7008 has one or more input devices, including but not limited to a mouse 7026 (or other pointing device such as a digitizer), a keyboard 7028, or any other data entry device.

[0583] Computer programs (also called computer control logic), including object oriented computer programs, are stored in main memory 7016 and/or the secondary memory 7018 and/or removable storage units 7024. Computer programs can also be called computer program products. Such computer programs, when executed, enable computer system 7008 to perform the features of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 7012 to perform the features of the present invention. Accordingly, such computer programs represent controllers of computer system 7008.

[0584] In another embodiment, the invention is directed to a computer program product comprising a computer readable medium having control logic (computer software) stored therein. The control logic, when executed by processor 7012, causes processor 7012 to perform the functions of the invention as described herein.

[0585] In yet another embodiment, the invention is implemented primarily in hardware using, for example, one or more state machines. Implementation of these state machines so as to perform the functions described herein will be apparent to persons skilled in the relevant arts.

[0586] (2) Software Objects in an OOP Environment

[0587] Prior to describing the class definitions in detail, a description of an exemplary software object in an OOP environment is described.

[0588] FIG. 70A is a graphical representation of a software object 7002. Software object 7002 is comprised of methods and variables. For example software object 7002 includes methods 1-8 7004 and variables V₁-V_N 7006. Methods 7004 are software procedures that, when executed, cause software objects variables 7006 to be manipulated (as needed) to reflect the effects of actions of software object 7002. The performance of software object 7002 is expressed by its methods 7004. The knowledge of software object 7002 is expressed by its variables 7006.

[0589] In object oriented programming, software objects 7002 are outgrowths (or instances) of a particular class. A class defines methods 7004 and variables 7006 that are included in a particular type of software object 7002. Software objects 7002 that belong to a class are called instances of the class. A software object 7002 belonging to a particular class will contain specific values for the variables contained in the class. For example, a software class of vehicles may contain objects that define a truck, a car, a trailer and a motorcycle.

[0590] In object oriented programming, classes are arranged in a hierarchical structure. Objects that are defined as special cases of a more general class automatically inherit the method and variable definitions of the general class. As noted, the general class is referred to as the superclass. The special case of the general class is referred to as the subclass of the general class. In the above example, vehicles is the general class and is, therefore, referred to as the superclass. The objects (i.e. truck, car, trailer, and motorcycle) are all special cases of the general class, and are therefore referred to as subclasses of the vehicle class.

[0591] (3) Class Definitions

[0592] Example OOP class definitions are now described. The functions performed by the methods included in the class definitions, and the type of information stored in and/or passed as parameters in the variables of the classes depicted, will be apparent to those skilled in the art.

[0593] (a) Soft Switch Class

[0594] FIG. 4B depicts a soft switch OOP class 418. Soft switch class 418 may be instantiated to create a soft switch application object. Related OOP classes will be described with reference to FIGS. 4C, 4D and 4E.

[0595] Soft switch class 418 includes variables 420 and methods 422. Variables 420 include information about a soft switch 204, including soft switch 204's identifier (ID), error message information, RNECP information, alarm server information, and run time parameters. Variables 420 can be used to provide information to the methods 422 included in soft switch class 418.

[0596] Methods 422 can include a method to start a soft switch to receive information, to receive a message, to receive a response to a message, and to perform updates. Methods 422 also include the means to read configuration data, to acknowledge messages, to get call context information from a signaling message, and to get call context information from an IPDC message. Methods 422 also include the means to get call context information from a route response, to get call context information from a route server message, and to forward messages.

[0597] FIG. 4B includes SS7 gateway proxy 424 which can have inter-object communication with soft switch class 418. FIG. 4B also includes route server proxy 426 and configuration server proxy 428, which can also have inter-object communication. These proxies can also be instantiated by soft switch class 418 objects.

[0598] FIG. 4B also includes route response 430, signaling message 432, and IPDC message 434, which can be passed parameters from soft switch class 418.

[0599] FIG. 4F depicts a block diagram 401 of interprocess communication including the starting of a soft switch command and control functions by a network operations center. Diagram 401 illustrates intercommunications between network operations center (NOC) 2114, soft switch 204 and configuration server (CS) 206. NOC 2114 communicates 404 with soft switch 418 to startup soft switch command and control. Soft switch command and control startup registers 405 soft switch 204 with CS 206 by communicating 411 with CS proxy 702, and accepts configuration information for soft switch 204 from CS 206.

[0600] FIG. 4G depicts a block diagram of soft switch command and control startup by a network operations center sequencing diagram 413, including message flows 415, 417, 419, 421 and 423.

[0601] FIG. 4H depicts a block diagram of soft switch command and control registration with configuration server sequencing diagram 425, including message flows 427, 429, 431 and 433.

[0602] FIG. 4I depicts a block diagram of soft switch accepting configuration information from configuration server sequencing diagram 435, including message flows 437, 439, 441, 443, 445 and 447.

[0603] (b) Call Context Class

[0604] FIG. 4C illustrates a call context class 438 OOP class definition. Call context class 438 includes variables 440 and methods 442.

[0605] Variables 440 can be used to store information about call context class objects 438. For example, variables 440 can include signaling message information for an incoming message, signaling message information for an outgoing message, a time stamp, and the number of stored signaling messages.

[0606] Methods 442 include various functions which can be performed by call context class 438. For example, methods 442 include a call context message which passes parameters identifying a call event and a signaling message. Other methods 442 include a function to get an IAM message, to get a call event identifier, to get an originating network ID, to get a terminating network ID, to get a signaling message, and to get a subroute. Methods 442 also include the means to add an ACM message, an ANM message, an REL message, an RLC message, a connect message, and a route response message. Methods 442 also permit call context class 438 to set various states as, for example, that an ACM was sent, an IAM was received, an RTP connect was sent, a CONI was received, a connect was sent, an answer was sent, an REL was sent, that the system is idle, that an ANM was sent, or that an RLC was sent. Methods 442 can also get a route.

[0607] FIG. 4C also includes route response 430, call context repository 444, call event identifier 448, and network ID 452. Call context repository 444 includes methods 446. Methods 446 include a register function, a function to get call context, and to find call context. Call event identifier 448 includes the function of identifying a call event 450.

[0608] (c) Signaling Message Class

[0609] FIG. 4D includes signaling message class 432 OOP class definition. Signaling message class 432 includes variables 456 and methods 458. Variables 456 include an originating message and a type of the message.

[0610] Classes 481 inherit from classes 432, i.e. class 432 is the base class for SS7 signaling messages.

[0611] Methods 458 include various signaling message functions which can pass various parameters and receive various parameters. Parameters which can be sent by signaling message functions include the request/response header (Rhs), the signaling message, the network ID, the port, the route response, the IPDC message and the soft switch information. Methods 458 also include the function to set the originating ingress port, to set the network identifier, to get a message type, and to get a network identifier.

[0612] FIG. 4D also includes network ID 452 and route response 430. Network ID 452 can communicate with signal message class objects 432. Route response 430 can receive parameters passed by signaling message class objects 432. FIG. 4D also includes ACK message 460, IAM message 464, ACM message 468, ANM message 472, REL message 476, and RLC message 480, collectively referred to as SS7 signaling message class definitions 481. Each message of SS7 message class definition 481 includes various functions. For example ACK message 460 includes methods 462, i.e., the ACK message function. IAM message 464 includes methods 466. Methods 466 include several functions, such as, for example the IAM message function, the get dialed digits function, the get NOA function and the get ANI function. ACM message 468 includes method 470, which includes function ACM message. ANM message 472 includes methods 474, which includes the ANM message function. REL message 476 includes methods 478, which includes the REL message functions. RLC message 486 includes methods 482, which includes the RLC message functions.

[0613] (d) SS7 Gateway Class

[0614] FIG. 5B includes SS7 gateway OOP class definition 532 and SS7 gateway proxy class definition 424. SS7 gateway class 532 includes variables 534, including runtime parameters, STP information, point code, and alias point code for an SS7 gateway.

[0615] FIG. 5C depicts a block diagram 536 of interprocess communication including soft switch interaction with SS7 gateways. Diagram 536 illustrates intercommunications between SS7 gateways (SS7 GW) 208 and soft switch 204. SS7 GW 208 communicates 538, 540 with soft switch 418. Soft switch 418 communicates 538 with SS7 GW proxy 424 accepting signaling messages from SS7 gateways 208. Soft switch 418 communicates 540 with SS7 GW proxy 424 sending signaling messages to SS7 gateway 208. In sending signaling messages, soft switch 204 uses 542 command and control registration of the soft switch 204 with SS7 gateway 208.

[0616] FIG. 5D depicts a block diagram 542 of interprocess communication including an access server signaling a soft switch to register with SS7 gateways. Diagram 542 illustrates intercommunications between access server 232a, soft switch 204 and SS7 gateway 208. Access server 232a communicates 544 with soft switch 418. Soft switch accepts IPDC messages from access servers from interaction with the servers. This communication extends 544 the soft switch command and control which registers soft switch 204 with SS7 gateways 232a. This registration uses 546 interaction between the soft switch and SS7 gateway 424. SS7 gateway 424 communicates 548 with the soft switch 418.

[0617] FIG. 5E depicts a block diagram of a soft switch registering with SS7 gateways sequencing diagram 550, including message flows 552-564.

[0618] (e) IPDC Message Class

[0619] FIG. 4E illustrates IPDC message OOP class definition 434. IPDC message 434 includes variables 484 and methods 486. Variables 484 include an IPDC identifier for an IPDC message. Methods 486 include IPDC message functions, which pass such parameters as the route node container, RHS, IPDC message, an IN port, an OUT port, and a bay module line channel (BMLC). Methods 486 include the get message type function, the get call event identifier function (i.e. passing the call event identifier variable), and the get IPDC identifier function (i.e., passing the IPDC identifier variable).

[0620] (f) Call Event Identifier Class

[0621] FIG. 4E includes call event identifier 448 in communication with IPDC message class 434, and route node container class 488 also in communication with IPDC message class 434 for passing parameters.