EP1131926B1 - Voice over data telecommunications network architecture - Google Patents

Voice over data telecommunications network architecture Download PDF

Info

Publication number
EP1131926B1
EP1131926B1 EP99959070.6A EP99959070A EP1131926B1 EP 1131926 B1 EP1131926 B1 EP 1131926B1 EP 99959070 A EP99959070 A EP 99959070A EP 1131926 B1 EP1131926 B1 EP 1131926B1
Authority
EP
European Patent Office
Prior art keywords
network
soft switch
call
format
gateway
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP99959070.6A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP1131926A4 (en
EP1131926A1 (en
Inventor
Isaac K. Elliott
Steven P. Higgins
Andrew John Dugan
Jon Peterson
Robert L. Hernandez
Rick D. Steele
Bruce W. Baker
Rich Terpstra
Jonathan S. Mitchell
Jin-Gen Wang
Harold Stearns
Eric Zimmerer
Ray Waibel
Kraig Owen
Shawn M. Lewis
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Level 3 Communications LLC
Original Assignee
Level 3 Communications LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Level 3 Communications LLC filed Critical Level 3 Communications LLC
Priority to EP10184126.0A priority Critical patent/EP2317711B1/en
Priority to EP10075638A priority patent/EP2317710A3/en
Publication of EP1131926A1 publication Critical patent/EP1131926A1/en
Publication of EP1131926A4 publication Critical patent/EP1131926A4/en
Application granted granted Critical
Publication of EP1131926B1 publication Critical patent/EP1131926B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/1026—Media gateways at the edge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/1036—Signalling gateways at the edge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1106—Call signalling protocols; H.323 and related
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/765—Media network packet handling intermediate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1245—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks where a network other than PSTN/ISDN interconnects two PSTN/ISDN networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/125—Details of gateway equipment
    • H04M7/1255—Details of gateway equipment where the switching fabric and the switching logic are decomposed such as in Media Gateway Control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0025—Provisions for signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H04Q3/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6472—Internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers

Definitions

  • the present invention relates generally to telecommunications networks and, more particularly, to a system and method for providing transmission of voice and data traffic over a data network, including the signaling, routing and manipulation of such traffic.
  • the present invention relates to telecommunications, and in particular to voice and data communication operating over a data network.
  • PSTN Public Switched Telephone 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.
  • TDM time division multiplexed
  • the channels are directed independently through multiple circuit switches from an originating switch to a destination switch.
  • 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.”
  • Telecommunications networks were originally designed to connect one device, such as a telephone, to another device, such as a telephone, using switching services.
  • 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.
  • 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 multifrequency (MF) in-band signaling.
  • DTMF dual-tone multiple frequency
  • IXC interexchange carrier
  • Out-of-band signaling uses a signaling network that is separate from the circuit switched network used for carrying the actual call information.
  • ISDN integrated services digital network
  • D data
  • CCIS Common Channel Interoffice Signaling
  • SS7 Signaling System 7
  • SS7 out-of-band signaling provided additional benefits beyond fraud prevention.
  • out-of-band signaling eased quick adoption of advanced features (e.g., caller id) by permitting modifications to the separate signaling network.
  • 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.
  • MFJ modified final judgment
  • 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).
  • SSP Service Switching Points
  • STPs Signaling Transfer Points
  • SCPs Service Control Points
  • 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.
  • Links between SSPs and STPs can be, for example, A, B, C, D, E or F links.
  • 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.
  • 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).
  • LEC local exchange carrier
  • a LEC is commonly referred to as a local telephone company.
  • the SSP will process triggers and internal route rules based on satisfaction of certain criteria.
  • 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.
  • 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)
  • LATAs local access transport areas
  • IXC inter exchange carrier
  • 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).
  • CLECs Competitive LECs
  • Traditional LECs or RBOCs are now also known as incumbent LECs (ILECs).
  • ILECs incumbent LECs
  • 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.
  • 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.
  • Packet switching provides for more efficient use of a communication channel as compared to circuit switching.
  • many different calls e.g., voice, data, video, fax, Internet, etc.
  • digitized voice information might be transferred between the callers only 50% of the time, with the other 50% being silence.
  • information might be transferred between two computers 10% of the time.
  • the voice call would tie-up a communications channel that may have 50% of its bandwidth being unused.
  • 90% of the channel's bandwidth may go unused.
  • 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.
  • IP Internet Protocol
  • IP network 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 to call.
  • 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.
  • EP0817452 describes a method for establishing communication between an originating station and a destination station over a computer network. At least one service attribute is requested by the originating station. A communication path is established in conformance with the requested service attribute.
  • a first aspect of the present invention is a method as set out in claim 1.
  • a second aspect of the invention is a system as set out in claim 15.
  • the present invention is a system and method for communicating both voice and data over a packet-switched network that may be adapted to coexist and communicate with a PSTN.
  • the system may permit 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.
  • a PSTN carrier e.g., LEC or IXC
  • the invention may receive signaling from the legacy SS7 signaling network or the ISDN D-channel or from inband signaling trucks.
  • data channel signaling or inband signaling may be received.
  • signaling messages can travel over the data network.
  • 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.
  • the system may include 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 may interface with customer facilities (e.g., a PBX), carrier facilities (e.g., a PSTN carrier, a LEC (e.g., ILECs and CLECSs), 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.
  • customer facilities e.g., a PBX
  • carrier facilities e.g., a PSTN carrier, a LEC (e.g., ILECs and CLECSs), 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-net
  • 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 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 may receive signaling messages from and send 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.
  • ISDN integrated services digital network
  • PRI primary rate interface
  • 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.
  • 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.
  • the gateway sites may originate and terminate calls between calling parties and called parties through the data network.
  • the soft switch sites can control or manage the gateway sites.
  • 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.
  • IPDC Internet Protocol Device Control
  • other protocols could be used, including, for example, network access server messaging interface (NMI) and the ITU media gateway control protocol (MGCP).
  • 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).
  • TGs trunking gateways
  • AGs access gateways
  • NASs network access servers
  • the gateway sites may provide for transmission of both voice and data traffic through the data network.
  • the gateway sites may 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.
  • DALs dedicated access lines
  • the data network may connect one or more of the soft switch sites to one or more of the gateway sites.
  • the data network may route data packets through routing devices (e.g., routers) to destination sites (e.g., gateway sites and soft switch sites) on the data network.
  • routing devices e.g., routers
  • destination sites e.g., gateway sites and soft switch sites
  • IP internet protocol
  • the data network represents any art-recognised data network including the global Internet, a private intranet or internet, a frame relay network, and an asynchronous transfer mode (ATM) network.
  • ATM asynchronous transfer mode
  • 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.
  • 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.
  • OSS operational support services
  • the provisioning component distributes provisioning data to appropriate network elements and maintains data synchronization, consistency, and integrity across multiple soft switch sites.
  • the network management component includes a network operations centre (NOC) for centralized network management.
  • NOC network operations centre
  • Each network element NE
  • SNMP simple network management protocol
  • the NOC uses the events generated by each network element to determine the health of the network and to perform other network management functions.
  • the invention operates as follows to process, for example, a long distance call (also known as a 1+ call).
  • 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 analyses the initial digit of the dialed number of the call and determines that it is a 1+call.
  • the soft switch site 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.
  • 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.
  • 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.
  • Verification can result in the need to enforce a restriction, such as a class of service (COS) restriction (COSR).
  • COS class of service
  • COSR class of service restriction
  • 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 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.
  • LATAs pre-loaded access and transport areas
  • the soft switch site then completes customer service processing and prepares to terminate the call.
  • the soft switch site has finished executing all customer service logic and has a 10-digit dialed number that must be terminated.
  • the soft switch site determines the terminating gateway.
  • the dialed number i.e., the number of the called party dialed by the calling party
  • 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.
  • the invention may use 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.
  • ISP internet service provider
  • ILEC ILEC
  • CLEC CLEC
  • ISPs may be 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.
  • data networks e.g., IP data packets
  • switched voice networks e.g., PPP signals
  • 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.
  • 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.
  • This section provides a high-level description of the voice over IP network architecture according to the present invention.
  • a structural implementation of the voice over IP (VOIP) network architecture is described at a high-level.
  • 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.
  • 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.
  • 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.
  • Calling parties 102, 122 and called parties 120, 124 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.
  • 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.
  • 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.
  • DAL dedicated access line
  • 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.
  • PSTN Public Switched Telephone Network
  • 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.
  • Soft switch sites 104, 106 receive signaling messages from and send signaling messages to signaling network 114.
  • 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).
  • Calls can be transmitted between any combination of on-network and off-network callers.
  • 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.
  • signaling messages for a call which cither 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.
  • 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.
  • Soft switch sites 104, 106 use other voice network components to assist with the processing of calls.
  • gateway sites 108, 110 provide the means to originate and terminate calls on the PSTN.
  • 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.
  • IPDC Internet Protocol Device Control
  • the IPDC protocol is described below with reference to Tables 144-185.
  • 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.
  • MGCP Media Gateway Control Protocol
  • IETF Internet Engineering Task Force
  • 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.
  • 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.
  • 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.
  • 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.
  • Gateway sites 108, 110 are controlled or managed by one or more soft switch sites 104, 106.
  • soft switch sites 104, 106 can communicate with gateway sites 108, 110 via the IPDC, NMI, MGCP, or alternative protocols.
  • 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).
  • CPE customer premises equipment
  • PBX private branch exchange
  • 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.
  • 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.
  • 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.
  • IP internet protocol
  • 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.
  • ATM asynchronous transfer mode
  • 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.
  • signaling network 114 can use Common Channel Interoffice Signaling (CCIS), which is a network architecture for out-of-band signaling.
  • CCIS Common Channel Interoffice 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.
  • 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.
  • 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.
  • OSS operational support services
  • Network management component 118 can include a network operations center (NOC) for centralized network management.
  • NOC network operations center
  • Each network element(NE) of block diagram 100 can generate simple network management protocol (SNMP) events or alerts.
  • SNMP simple network management protocol
  • the NOC uses the events generated by a NE to determine the health of the network, and to perform other network management functions.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • data network 112 e.g. using IPDC protocol commands
  • 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.
  • 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.
  • 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 .
  • step 2202 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.
  • 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.
  • the soft switch site queries a customer profile database to retrieve the originating trigger plan associated with the calling customer.
  • 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.
  • the lookup returns subscription information.
  • the customer profile can require entry of an account code.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • data network 112 e.g. using IPDC protocol commands
  • 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.
  • 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.
  • 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 .
  • step 2202 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.
  • 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.
  • the soft switch site queries a customer profile database to retrieve the originating trigger plan associated with the calling customer.
  • 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.
  • the lookup returns subscription information.
  • the customer profile can require entry of an account code.
  • 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.
  • 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.
  • 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.
  • 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.
  • step 2216 verification can result in the need to enforce a restriction, such as a class of service (COS) restriction (COSR).
  • COS class of service
  • 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.
  • LATAs local access and transport areas
  • PACs project account codes
  • COS class of service
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • data network 112 e.g. using IPDC protocol commands
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • any switch in the PSTN is an SSP if it provides SS7 functions.
  • a soft switch is an SSP.
  • signal transfer point STP
  • 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 server/ configuration database CDB
  • Configuration servers are servers managing customer profiles, voice 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.
  • RNECP regional network event collection point
  • Route servers are responsible for 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.
  • 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.
  • 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.
  • TG Gateway site component Description trunking gateway
  • 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 system A digital access and cross-connect 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 An announcement server provides a network with PSTN terminating announcements.
  • 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.
  • 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. 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.
  • 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)).
  • NOC network operations center
  • SNMP simple network management protocol
  • Table 4 below describes the functions of these network elements in detail.
  • 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 protocol (SNMP) Simple network management protocol provides site filtering of element alarms and messages before forwarding them to the NOC.
  • Network event component 116 includes master network event database (MNEDB) 226.
  • MNEDB master network event database
  • Table 5A below describes the functions of this network element in detail.
  • MNEDB Master network event database
  • RNECPs regional network event collection points
  • Provisioning component 117 includes data distributor (DD) 222.
  • Table 5B below describes the functions of this network element in detail.
  • 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.
  • OSS Operational Support Systems
  • 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 .
  • call flow 258 includes 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.
  • PACs project account codes
  • COS class of service
  • 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.
  • Exemplary call flow 258 begins with 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.
  • 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.
  • trunking gateway 232 sends an acknowledgement message to soft switch 204.
  • soft switch 204 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.
  • 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.
  • this type of call i.e., a 1+ call
  • 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.
  • ANI originating automatic number identification
  • 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).
  • 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.
  • COS class of service
  • 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.
  • 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.
  • 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.
  • PACs project account codes
  • 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.
  • 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.
  • the COS restriction can be applied based on ANI or ingress trunk group.
  • 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.
  • 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.
  • 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.
  • route server 212 returns a route that indicates the connections that soft switch 204 must make to connect the call.
  • 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.
  • soft switch 304 queries port status 298 of route server 314 to identify available ports in trunking gateway 234.
  • route server 314 returns an available port to soft switch 304.
  • soft switch 304 communicates with trunking gateway 234 to allocate a port for termination of the call to called party 120.
  • step 284 soft switch 304 communicates with soft switch 204 to indicate terminating ports have been allocated.
  • 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.
  • RTP session i.e. an RTP over UDP over IP session
  • the Specific Implementation Example Embodiments 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.
  • 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.
  • a functional implementation for this structure is described at a low-level.
  • 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.
  • 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.
  • Data network 112 can route both signaling and transport traffic between the regional soft switch sites and regional gateway sites.
  • 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.
  • 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.
  • 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.
  • 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.
  • Western soft switch site 104 includes SS7 gateway (GW) 208, configuration server/configuration database (CS/CDB) 206a and route server (RS) 212a.
  • GW SS7 gateway
  • CS/CDB configuration server/configuration database
  • RS route server
  • western soft switch site 104 includes a redundant SS7 GW, a redundant CS/CDB and a redundant RS.
  • western soft switch site 104 includes SS7 GW 210, CS/CDB 206b and RS 212b.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .
  • soft switch 204 provides the call processing function for telecommunications network 200.
  • Call processing refers to the handling of voice and data calls.
  • 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.)
  • 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.
  • Soft switch 204 communicates 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.
  • 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).
  • 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.
  • This primary soft switch e.g., soft switch 204, assumes a primary responsibility or control of the access servers.
  • 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.
  • western soft switch site 104, central soft switch site 106 and eastern soft switch site 302 are geographically diverse.
  • western soft switch site 104 can be a soft switch site located in San Diego, CA.
  • Central soft switch site 106 can be a soft switch site located in Denver, CO.
  • Eastern soft switch site 302 can be a soft switch site located in Boston, MA.
  • additional network nodes are provided at any of soft switch sites 104, 106 and 302.
  • 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.
  • ANS announcement server
  • NECP network event collection point
  • SCP network event collection point
  • STPs on-network STPs.
  • telecommunications network 200 includes ANSs 246, 248.
  • 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.
  • interface 402 is an SS7 integrated services digital network (ISDN) user part (ISUP) over a transmission control protocol/internet protocol (TCP/IP).
  • ISDN integrated services digital network
  • TCP/IP transmission control protocol/internet protocol
  • Soft switch 204 interfaces with configuration server 206 over interface 406.
  • interface 406 is a TCP/IP connection.
  • Soft switch 204 interfaces with RNECP 224 over interface 410.
  • interface 410 is a TCP/IP connection.
  • Soft switch 204 interfaces with route server 212 over interface 408.
  • interface 408 is a TCP/IP connection.
  • Soft switch 204 interfaces with SCP 214 over interface 404.
  • interface 404 is a TCP/IP connection.
  • Soft switch 204 interfaces with announcement servers 246, 248 over interface 416.
  • interface 416 can include the IPDC protocol used over a TCP/IP connection.
  • Soft switch 204 interfaces with TGs 232, 234 over interface 412.
  • interface 412 can include the IPDC protocol used over a TCP/IP connection.
  • Soft switch 204 interfaces with AGs 238, 240 over interface 414.
  • interface 414 can include the IPDC protocol used over a TCP/IP connection.
  • 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 .
  • MMI man-machine interface
  • MMI maintenance and monitoring interface
  • a soft switch-to-soft switch 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 304 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.
  • 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.
  • VDC -48 volts DC
  • 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.
  • a PBX 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.
  • E&M tie trunk interface device is a form of standard that exists in the PBX, T-1 I 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.
  • the sample configuration depicted in FIG. 2B can use a soft switch 204-to-soft switch 304 protocol.
  • 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.
  • SCN switch circuit network
  • 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.
  • 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).
  • AVPs attribute value pairs
  • the other AVPs can contain additional information necessary to establish a voice-over-IP connection between the originating and terminating ends of the call.
  • SS7 gateways (GWs) 208, 210 will now be described further with reference to FIG. 2A and FIG. 5A .
  • SS7 GWs 208, 210 receive signaling messages from signaling network 114 and communicate these messages to soft switch 204.
  • 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.
  • 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.
  • SS7 GWs 208,210 are application programs running on a computer system.
  • An exemplary application program providing SS7 GW 208, 210 functionality is OMNI SIGNAL WARE (OMNI), available from DGM&S, of Mount Laurel, NJ.
  • 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, CA.
  • 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 SIGNAL WARE architecture, OMNI has the ability to simultaneously support variants of SS7 signaling technology (ITU-T, ANSI, China and Japan).
  • the SIGNAL WARE 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.
  • MTP Message Transfer Part
  • SCCP Service Connection Control Part
  • OMNI supports multiple protocol stacks simultaneously, each potentially with the point code format and protocol support of one of the major SS7 variants.
  • OMNI SIGNALWARE Application Programming Interfaces 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), EIAlTIA Interim Standard 41 (IS-41 MAP), Advanced Intelligent Network (AIN), and Intelligent Network Application Part (INAP).
  • 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, offs7 GWs 208, 210 respectively. SS7 GWs 208, 210 together comprise a CE cluster 207.
  • 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.
  • TG trunking gateway
  • 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.
  • 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.
  • 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.
  • CICs 1-48 512, 516, 520, and CICs 49-96 514, 518, 522 are the trunking gateway circuits serviced by soft switch site 104.
  • soft switches are partitioned such that any single soft switch will only service a subset of circuits serviced at a given soft switch site.
  • soft switch 204a can service CICs 1-48 512, 516
  • soft switch 204b services CICs 49-96 514 and CICs 1-48 520
  • soft switch 204c services CICs 49-96 518,522.
  • 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).
  • LEC local exchange carrier
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 Switch ID Unique Identifier for the Soft Switch that will service requests for the OPC, DPC, CIC values Servicing Soft Switch IP address IP address for the Soft Switch that will service requests for the OPC, DPC, CIC values Servicing Soft Switch IP port Port number that the Soft Switch is listening on for incoming signaling messages. Primary/Secondary/Tertiary identification The Soft Switch identifies itself as the primary, secondary or tertiary contact for signaling messages for the specified OPC. DPC and CIC.
  • Table 7 includes the mapping of circuits to soft switches.
  • 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.
  • 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.
  • 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
  • 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).
  • 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:
  • the IAM message can then be routed by signaling network114 (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.
  • the IAM message having OPC 524 of value 777, DPC of value 111 and CIC 55 can be routed to soft switch 204b.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • SS7 signaling messages are transferred through signaling network 114 from STP to STP until arriving at a final destination.
  • 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
  • STPs and A-F links can be provided by an SS7 signaling services provider, such as, e.g., Transaction Network Services (TNS).
  • TSS7 signaling services provider such as, e.g., Transaction Network Services (TNS).
  • 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.
  • STP pairs 250a, 252a are linked together by one or more C-links 1728.
  • STP pairs 1722, 1724, STP pairs 250b, 252b, STP pairs 1718, 1720, and STP pairs 1714, 1716 can be linked together by C-links.
  • 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.
  • 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.
  • 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.
  • SNMP simple network management protocol
  • 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.
  • NOC network operation center
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • STPs 250b, 252b, STPs 1718, 1720, STPs 1722, 1724, STPs 1714, 1716, and STPs 216,218 can also be respectively linked via C-links.
  • 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.
  • 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.
  • the soft switch sites 104, 106, 302 have a fully redundant, fully meshed, fault tolerant signaling architecture.
  • 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.
  • NOC network operation center
  • 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.
  • 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.
  • STP 250a and STP 252a are connected together by C-Links 1728.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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, CA, is a high speed packet switch designed to support SS7 signaling.
  • STPs 250, 252 can be equipped with a plurality of links.
  • STPs 250, 252 can support up to, for example, 84 links.
  • 14 links can be used initially, and additional links can be added in the future.
  • several additional features can be added to STPs 250, 252.
  • 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.
  • STPs 250, 252 can support up to, for example, 1,000 global title translation requests per second, per application service module (ASM).
  • ASM application service module
  • 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.
  • LIMs link interface modules
  • ASMs application service modules
  • LNP local number portability
  • MSAs very large metropolitan serving areas
  • 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.
  • the STP-to-LAN interface could be used to carry SS7 signaling over IP packets.
  • STPs 250, 252 can include a feature referred to as the ANSI-ITU gateway feature.
  • 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.
  • MSU message signaling unit
  • the ANSI-ITU feature can allow a smooth transition from an all-ANSI network to a combined ANSI-ITU network.
  • 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.
  • 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.
  • 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 can use this common interface.
  • SCP 610 is an off-network or off-switch SCP, meaning that it is not within soft switch site 104.
  • 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.
  • 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.
  • 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.
  • 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.
  • PAC project account code
  • LNP local number portability
  • CNAM calling name
  • ACD advanced toll-free/network automatic call distribution
  • customer premise toll-free routing services customer premise toll-free routing services
  • CPE customer premises equipment
  • 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.
  • 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.
  • 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.
  • LEC local exchange carrier
  • IXC inter-exchange
  • Operator services service bureau 628 operator services service bureau 628.
  • 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.
  • 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.
  • 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.
  • OSCP off-switch call processing
  • 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.
  • 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.
  • FIG. 6C illustrates additional off-switch services 630.
  • 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.
  • 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.
  • FIG. 6D depicts additional services 634.
  • 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.
  • 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.
  • 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.
  • CTI computer telephony integration
  • ACD automatic call distributor
  • FIG. 6D also depicts an IP client connected via a customer network into data network 112.
  • 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.
  • 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 distributer (ACD) 644.
  • the H.323 Recommendation will now be briefly overviewed with reference to FIGs. 58A-61 .
  • the H.323 standard provides a foundation for, for example, audio, video, and data communications across IP-based networks, including the Internet.
  • 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.
  • 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.
  • ITU International Telecommunications Union
  • LANs Local Area Networks
  • QoS Quality of Service
  • H.323 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.
  • H.323 is part of a larger series of communications standards that enable videoconferencing across a range of networks.
  • this series includes H.320 and H.324, which address ISDN and PSTN communications, respectively.
  • 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.
  • 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.
  • 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.
  • RAS Registration/Admission/Status
  • Optional components in an H.323 terminal are video codecs, T.120 data conferencing protocols, and MCU capabilities (described further below).
  • 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).
  • 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.
  • gateway 5806 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:
  • 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.
  • H.323 gateways 5806 can support terminals that comply with H.310, H.321, H.322, and V.70.
  • 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.
  • the ITU has positioned H.323 as the glue that holds the world of standards-based conferencing endpoints together.
  • 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.
  • 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.
  • 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.
  • 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.
  • gatekeeper 5808 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.
  • 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.
  • 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • An exemplary embodiment of basic toll-free SCP 214b is a GENESYS Network Interaction Router available from GENESYS of San Francisco, CA.
  • 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.
  • SCP 214b can receive a dialed number of 800-202-2020 and return a DDD such as 303-926-3000.
  • 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.
  • Soft-Switch 204 can connect the calling party with Announcement Server 246 for the playing of an announcement and then disconnect the caller.
  • 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.
  • CS Configuration Server
  • CDB Configuration Database
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • Tables necessary to support class of service restrictions include: LATA tables; state tables; and blocked country code tables.
  • 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.
  • 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.
  • Table 12 includes an example of a customer profile query.
  • 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
  • Table 13 includes an example of a customer profile query response provided by configuration server 206.
  • 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.
  • 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.
  • 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.
  • configuration server 206 can be combined with that of route server 212 in a single network component.
  • functions of either or both of CS 206 and RS 212 can be performed by application logic residing on soft switch 204.
  • 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).
  • soft switch 204a is in communication with TG 232a and TG 232b.
  • 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.
  • 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.
  • route server 212 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.
  • 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. Table 14 Number Routing Table Number Terminating Circuit Group Priority Lead 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
  • 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.
  • route server 212 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.
  • 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.
  • the logic for route server 212 can include routing for international calls.
  • Table 14 it is possible to have fully specified international numbers, or simply specified routing, for calls going to a particular country.
  • 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).
  • 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.
  • 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.
  • Table 15A Circuit Group Parameters Circuit group Selection algorithm 34 Random 35 Least recently used 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
  • 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.
  • route server 212 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 .)
  • 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.
  • 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.
  • 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.
  • IDDD international DDD
  • route server 212 can return the port on an AG 238, 240 or TG 232, 234 that should be used to terminate this call.
  • soft switch 204 can then signal the originating and terminating TG or AG to connect the call through data network 112.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • soft switch 204 makes a route request to route server 212.
  • the routing logic uses the NPA-NXX-XXX to identify 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.
  • 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.
  • route server 212 responds to soft switch 204 with the terminating circuit group.
  • 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.
  • 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.
  • TG 232 manages its own ports.
  • TG 232 uses real time protocol (RTP) over UDP, and RTP sessions, which are ports used to implement an RTP connection.
  • RTP real time protocol
  • TG 232 returns to soft switch 204 the IP address and listed RTP port.
  • 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.
  • 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.
  • route server 314 allocates a termination port and returns the allocated termination port to terminating soft switch 304.
  • 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.
  • step 282 terminating TG 234 returns the allocated resources for the call to soft switch 304.
  • VOIP voice over IP
  • step 284 terminating soft switch 304 returns to originating soft switch 204 the IP address of TG 234.
  • 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.
  • originating TG 232 and terminating TG 234 have enough information to exchange full duplex information.
  • step 288 originating TG 232 acknowledges the receipt of the communication from soft switch 304 to soft switch 204.
  • 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.
  • 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
  • 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.
  • each route response can include one route termination, and multiple consecutive route terminations can be determined with multiple route request/response transactions.
  • 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 - I Terminating circuit group for the first route Destination circuit - I Terminating circuit allocated by the route server for the first route Outpulse digits - I Outpulse digit format for selected circuit on the first route Destination number - I Destination number for the first route Destination Soft Switch - I 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
  • 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.
  • 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.
  • 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.
  • each route response can include one route termination and multiple consecutive route terminations can be determined with multiple route request/route response transactions.
  • 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.
  • 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.
  • RNECP Regional Network Event Collection Point
  • RNECPs regional network event collection points
  • 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.
  • IPs intelligent peripherals
  • AGs 238,240 AGs 238,240
  • TGs 232,234 TGs 232,234, and signaling components, such as STPs 250,252, SSPs, and off switch SCPs.
  • 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.
  • MNEDB master network event database
  • 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.
  • 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.
  • 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.
  • MNEDB 226b uses primary and secondary disks, 926a, 926b.
  • MNEDB 226a and MNEDB 226b can be collocated or can be geographically diverse.
  • master data center 912 can be either in one geographical area or in multiple locations.
  • 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.
  • 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.
  • 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.
  • Event blocks are recorded call events that are created during call processing.
  • 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).
  • NOC network operation center
  • 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.
  • 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.
  • 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.
  • 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.
  • CABS carrier access billing services
  • Example Mandatory and Augmenting event blocks can be explained as follows.
  • 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.
  • Tables 20-143 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.
  • soft switch site 104 comprises a plurality of object oriented programs (OOPs) running on a computer.
  • OOPs object oriented programs
  • soft switch site 104 can alternatively be written in any form of software.
  • OOPs can be described at a high level by defining object oriented programming classes.
  • 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.
  • 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.
  • 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.
  • 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.
  • classes on the inheritance hierarchy give the programmer a head start to program design and creation.
  • 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.
  • 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.
  • 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, CA, 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.
  • the invention is not limited to these platforms, and can be implemented on any appropriate computer systems or operating systems.
  • FIG. 70B 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.
  • 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.
  • 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.
  • 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.
  • Computer programs also called computer control logic
  • 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.
  • 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.
  • the invention is directed to a computer program product comprising a computer readable medium having control logic (computer software) stored therein.
  • control logic computer software
  • the control logic when executed by processor 7012, causes processor 7012 to perform the functions of the invention as described herein.
  • 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.
  • FIG. 70A is a graphical representation of a software object 7002.
  • Software object 7002 is comprised of methods and variables.
  • software object 7002 includes methods 1-8 7004 and variables V 1 -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.
  • 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.
  • a software class of vehicles may contain objects that define a truck, a car, a trailer and a motorcycle.
  • 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • FIG. 4B also includes route response 430, signaling message 432, and IPDC message 434, which can be passed parameters from soft switch class 418.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4C illustrates a call context class 438 OOP class definition.
  • Call context class 438 includes variables 440 and methods 442.
  • Variables 440 can be used to store information about call context class objects 438.
  • 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.
  • Methods 442 include various functions which can be performed by call context class 438.
  • 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.
  • 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.
  • 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.
  • Classes 481 inherit from classes 432. i.e. class 432 is the base class for SS7 signaling messages.
  • 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.
  • Rhs request/response header
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • soft switch 204 uses 542 command and control registration of the soft switch 204 with SS7 gateway 208.
  • 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.
  • FIG. 5E depicts a block diagram of a soft switch registering with SS7 gateways sequencing diagram 550, including message flows 552-564.
  • 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).
  • 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.
  • FIG. 4E also includes exemplary IPDC messages 495, which inherit from IPDC base class 434.
  • IPDC messages 495 include ACR message 490, ACSI message 492, CONI connect message 494, connect message 496, RCR message 498, RTP connect message 454, and TDM cross connect message 497.
  • IPDC messages can include various methods.
  • ACR message 490 can include ACR message function 493.
  • connect message 496, RCR message 498, and RTP connect message 454 can include connect message function 491, RCR message function 489, RTP connect function methods, respectively.
  • FIG. 7A illustrates configuration server proxy OOP class definition 702.
  • Configuration server proxy 702 includes methods 704.
  • Methods 704 include multiple functions.
  • methods 704 include the register function, the get configuration data function, the update function, the update all function, and the get data function.
  • FIG. 7B depicts a block diagram 706 of interprocess communication including soft switch interaction with configuration server (CS) 206.
  • Diagram 706 illustrates intercommunications between CS 206 and soft switch 204.
  • CS 206 communicates 708, 710 with soft switch 418.
  • Soft switch 418 communicates 708 with CS proxy 702 to register soft switch 204 with CS.
  • Soft switch 418 communicates 710 with CS proxy 702 to permit soft switch 204 to accept configuration information from CS 206.
  • FIG. 8B depicts route server class diagram 802.
  • Class diagram 802 includes route server OOP class definition 804.
  • Route server class 804 includes variables 806 and methods 808.
  • Variables 806 include, for a respective route server 212, an identifier (ID), a ten digit table, a six digit table, a three digit table, a treatment table, a potential term table, an local serving area (LSA) table, a circuit group (CG) table, an destination AD table, a runtime parameters and an alarm server.
  • ID identifier
  • LSA local serving area
  • CG circuit group
  • AD destination AD table
  • runtime parameters 806 include, for a respective route server 212, an identifier (ID), a ten digit table, a six digit table, a three digit table, a treatment table, a potential term table, an local serving area (LSA) table, a circuit group (CG) table, an destination AD table, a runtime parameters and an alarm server.
  • LSA local serving area
  • CG circuit group
  • destination AD table a runtime parameters and an alarm server.
  • Methods 808 include several functions. For example methods 808 include a start function, a receive message function, a receive request function, an update function, a process function and a digit analysis function.
  • FIG. 8B includes route server proxy class 426.
  • FIG. 8B also includes route request class 430, from route objects superclass 803, which is passed parameters from route server class 804.
  • FIG. 8B also includes route server message class 810, also from route objects superclass 803, similarly receiving parameters from route server class 804.
  • FIG. 8B also includes configuration server proxy class 428, which is in communication with route server class 804.
  • FIG. 8B also includes RTP pool class 812, chain pool class 814 and modem pool class 818, all of which are from superclass pools 805. and are in communication with route server class 804.
  • Circuit pool class 816 which is also from a superclass 805, is also in communication with route server class 804.
  • FIG. 8C illustrates superclass route objects 803 in greater detail.
  • FIG. 8C includes route response OOP class definition 430.
  • Route response class 430 includes variables 820 and methods 822.
  • Variables 820 include the type of a route response and a version of the route response.
  • Methods 822 include several functions. For example, methods 822 include the route response function, the get type of route response function, the get call event identifier function, the get originating out BMLC function, the get originating IP function, the get terminating out BMLC function, the get terminating IP function, and the get terminating network ID function.
  • FIG. 8C includes route calculator class 824, including methods 826, which include a calculate function.
  • FIG. 8C includes route server message class 810, including methods 828.
  • Methods 828 include several functions, including the route server message function, and the get BMLCs function.
  • FIG. 8C includes call event identifier class 448.
  • Network call event identifier 448 is in communication with route response class 430.
  • FIG. 8C also depicts route request class 832 in communication with call event identifier class 448.
  • Route request class 832 includes variables 834 and methods 836.
  • Variables 834 include the nature of address, the dialed digits, the ANI, version, and the jurisdiction information parameters, of route request class 832.
  • Methods 836 include multiple functions. Methods 836 include the route request function, the get dialed digits function, the get nature of address function, and the get network ID function. Network ID class 452 is in communication with route request class 832. Potential term container class 844 is in communication with route response class 430.
  • Route class 840 is in communication with route response class 430.
  • Route class 840 includes methods 842.
  • Methods 842 include several functions. For example methods 842 can include a route function, a get next function, a begin function, an end function, a get current function, an add route node function, and an end function.
  • Route node class 846 is in communication with route class 840.
  • Route node 846 includes variables 848 and methods 850.
  • Variables 848 include a BMLC, an IP, a location, and a bay name for a particular route node.
  • Methods 850 include several functions. For example methods 850 can include a get OPC function, a get DPC function, a get terminating CIC (TCIC) function , a get IP function, a reserve function, a route node function, a get type function, a match function, a get pool function and a get BMLC function.
  • TCIC terminating CIC
  • Call event identifier class 448 is in communication with route node class 846.
  • Route node class 846 has additional route node subclasses 851.
  • Route node subclasses 851 include MLC route node class 852, modem route node class 856, RTP route node class 858 and treatment route node class 862.
  • MLC route node class 852 includes methods 854.
  • Methods 854 includes several functions. For example methods 854 can include a match function, an are you available function, a get BMLC function and an unreserve function.
  • RTP route node class 858 includes methods 860. Methods 860 include several functions, e.g., a get address port pair function. Treatment route node class 862 includes variables 864, e.g., an announcement to play variable. RTP route node class 858 has two subclasses, i.e. IP address class 866 and IP port class 868.
  • FIG. 8C includes route node container class 488.
  • Route node container class 488 includes methods 853.
  • Methods 853 can include several functions, e.g., a begin function, a get current function, and a next function.
  • FIG. 8F depicts a block diagram 894 of interprocess communication including soft switch interaction with route server (RS) 212.
  • Diagram 894 illustrates intercommunications between RS 212 and soft switch 204.
  • RS 804 accepts 896 route requests from soft switch 418 and sends 898 route responses from RS 804 to soft switch 418.
  • Soft switch manages ports by using RS 804 to process 899 unallocate messages from soft switch 418.
  • FIG. 8D depicts superclass pool class 870.
  • Pool class 870 includes methods 872, including a get route node function and a find route node function.
  • Pool class 870 has a plurality of subpool classes 871.
  • Subpool classes 871 include modem pool class 818, real-time transport protocol (RTP) pool class 812, and chain pool class 814.
  • RTP pool class 812 includes methods 876.
  • Methods 876 include several functions, including a get originating route node function, a get terminating out route node function and a get route node function.
  • Chain pool class 814 includes methods 878, including a get function, a get route node function, a get chain pair function and a get route node function.
  • modem route node class 818 In communication with modem pool class 818 is modem route node class 856, which is a subclass from route objects 803.
  • chain pair class 874 In communication with chain pool class 814 is chain pair class 874.
  • Chain pair class 874 includes methods 880, including a match MLC route node function, a match function and an are you available function.
  • Chain pair class 874 is in communication with MLC route node class 852, i.e., a subclass of route objects class 803.
  • FIG. 8E illustrates circuit pool class 816 having methods 886. including a get circuit function.
  • a circuit class 882 having methods 888, including a get route node function.
  • circuit group class 884 having variables 890 and methods 892.
  • Variables 890 include a trunk group reference and a type for circuit groups of circuit group class 884.
  • Methods 892 include an any available function.
  • Method ID class 452 is in communication with circuit class 882.
  • FIG. 8E also includes module line channel (MLC) route node class 852 from the route objects superclass.
  • MLC module line channel
  • FIG. 10A depicts a more detailed drawing 1000 of gateway site 108.
  • FIG. 10A includes gateway site 108 comprising TG 232, NAS 228, AG 238, DACS 242 and announcement server ANS 246.
  • TG 232, NAS 228 and AG 238 collectively are referred to as access server 254.
  • DACs 242 could also be considered an access server 254 if it can be controlled by soft switch 204.
  • TG 232, NAS 228 and AG 238 are connected via an IP interface connection to data network 112.
  • TG 232, NAS 228, AG 238 are connected via separate interface to network management component 118.
  • TG 232 is connected to network management component 118 via interface 1002.
  • NAS 228 is connected to network management component 118 via interface 1004.
  • AG 238 is connected to network management component 118 via interface 1006.
  • FIG. 10A includes ANS 246, which as pictured is connected directly via the IP connection to data network 112.
  • the ANS can functionally exist in other areas of the telecommunications network.
  • ANS 246 can functionality exist in TG 232, as depicted by ANS 1008, TG 232 having ANS functionality 1008.
  • ANS functionality shown as ANS 1010) can be provided by AG 238.
  • FIG. 10A includes customer facility 128, providing access for calling party 122 to AG 238 via a direct access line or dedicated access line (e.g., a PRI or T1).
  • signaling for calling party 122 is carried inband between customer facility 128 and AG 238 via a signaling channel, e.g., an integrated services digital network (ISDN) data channel (D-channel).
  • ISDN integrated services digital network
  • Calling party 102 is connected via carrier facility 126 to DACS 242, in order to provide connectivity to TG 232 and NAS 228.
  • signaling for calling party 102 is carried out-of-band over signaling network 114, as shown in FIG. 10A .
  • FIG. 10B depicts a block diagram 1012 of interprocess communication including soft switch interaction with access servers such as trunking gateway 232a.
  • Diagram 1012 illustrates intercommunications between access server 232a and soft switch 204.
  • Soft switch 418 accepts 1014 IPDC messages from access server 232a.
  • Soft switch 418 sends 1016 IPDC messages to access server 232a.
  • a TG is a gateway enabling termination of PSTN co-carrier trunks and feature group-D (FG-D) circuits.
  • FIG. 11A illustrates an exemplary TG 232.
  • Gateway common media processing is illustrated in FIGs. 11B and 11C below. Gateway common media processing on the ingress side will be described with reference to FIG. 11B . Gateway common media processing on the egress side will be described with reference to FIG. 11C .
  • FIG. 11A depicts a trunking gateway high level functional architecture 1100 for TG 232.
  • FIG. 11A includes calling party 102, connected via carrier facility 126 to DS3 trunks, which in turn provide connection to TG 232.
  • Signaling for a call from calling party 102 is carried via out-of-band signaling network 114, through SS7 gateway 208, to soft switch 204. This is shown with signaling 1118.
  • TG 232 is controlled by soft switch 204, via the IPDC protocol 1116 through data network 112.
  • TG 232 includes PSTN interface card 1102 connecting TG 232 to the incoming DS3 trunks from the PSTN.
  • PSTN interface card 1102 is connected to a time division multiplexed (TDM) bus 1104.
  • TDM time division multiplexed
  • TDM bus 1104 takes the incoming DS3 trunks and separates the trunks, using time division multiplexing, into separate DS1 signals 1106.
  • DS1 1106 can be encoded/decoded via, for example, DSP-based encoder/decoder 1108.
  • Encoder/decoder 1108 typically performs a voice compression, such as G.723.1, G.729, or simply breaks out G.711 64 kbps DS0 channels.
  • Encoder/decoder 1108 is connected to packet bus 1110, for packetizing the incoming digital signals.
  • Packet bus 1110 is connected to IP Interface cards 1112-1114.
  • IP Interface cards 1112-1114 provide connectivity to data network 112 for transmission of VOIP packets to distant gateways and control messages to soft switch 204.
  • TG 232 also includes network management IP interface 1002 for receiving and sending network management alarms and events via the simple network management protocol (SNMP) to network management component 118.
  • SNMP simple network management protocol
  • Trunks can handle switched voice traffic and data traffic.
  • trunks can include digital signals DS1-DS4 transmitted over T1-T4 carriers.
  • Table 17 provides typical carriers, along with their respective digital signals, number of channels, and bandwidth capacities.
  • Table 17 Digital signal Number of channels Designation of carrier Bandwidth in Megabits per second (Mbps) DS0 1 None 0.064 DS1 24 T1 1.544 DS2 96 T2 6.312 DS3 672 T3 44.736 DS4 4032 T4 274.176
  • trunks can include optical carriers (OCs), such as OC-1, OC-3, etc.
  • Table 18 provides typical optical carriers, along with their respective synchronous transport signals (STSs), ITU designations, and bandwidth capacities.
  • TGs 232 and 234 can receive call control messages from and send messages to soft switch 204, via the IPDC protocol.
  • Soft switch site 104 implements a signaling stack, e.g., an SS7 signaling network stack, for communications with legacy PSTN devices.
  • signaling stack e.g., an SS7 signaling network stack
  • ingress trunking gateway 232 seizes a circuit as a call is initiated (i.e. assuming calling party 102 is placing a call to called party 120).
  • SS7 signaling network 114 begins the process of setting up a call, by sending messages via SS7 GW 208 to soft switch 204.
  • ingress TG 232 can receive commands from soft switch 204 to complete the call through ingress TG 232 and out through the virtual voice network via the IP interface 1114 to a destination gateway.
  • this process is reversed to complete the call through the interconnected network to egress trunking gateway 234 and ultimately to called party 120.
  • FIG. 11B depicts gateway common media processing components on the ingress side 1140.
  • FIG. 11B begins with incoming media stream 1142. From incoming media stream 1142, tone detection 1144 can occur and then data detection 1146 can occur or tone detection 1144 can be bypassed (see path 1148), as disabled/enabled by soft switch 204 via IPDC. From data detection 1146, silence detection/ suppression 1150 can be performed. Next, a coder 1152 can be processed and then the packet stream can be transferred, as shown in 1154.
  • FIG. 11B is now described with respect to ingress trunking gateway 232.
  • Incoming media stream 1142 must be processed as it passes through ingress gateway 232 to complete the call via the IP core data network 112.
  • the first process that takes place is data detection process 1146.
  • Data detection process 1146 attempts to detect the media type of the call traffic.
  • the media type of the call traffic can include voice, data and modem.
  • the media type information can be passed via IPDC protocol to soft switch 204 for process determination.
  • a compression/decompression software component that is used in performing media processing, can be selected based on data detection process 1146. Specifically, if the data is determined to be modem traffic and if a suitable CODEC exists for the data rate, soft switch 204 can choose to incorporate this CODEC on the stream. Alternatively, if the call is a voice call, soft switch 204 can select the CODEC optimized for voice processing and current network conditions. In an embodiment of the invention, data calls can always be processed with the default bit rate CODEC.
  • CODEC compression/decompression software component
  • silence in a voice call can be detected and suppressed, yielding potential decreases in the volume of transmission of packets carrying no digitized voice, due to silence.
  • encoding process 1152 once a CODEC has been chosen by soft switch 204 or the decision is made to use the default CODEC, the media stream passes through a digital signal processor (DSP) 1108 to apply an appropriate compression algorithm.
  • DSP digital signal processor
  • This compression processing algorithm can take the media stream as a traditional stream from the traditional voice world and transform it into a stream suitable for digital packetization.
  • ingress TG 232 can process the packets into IP packets and prepare the packets for transport through the IP backbone 112 to egress TG 234.
  • egress TG 234 can take the packets from data network 112 and decompress them and decode them with the same DSP process and algorithm used on the ingress side of the network.
  • FIG. 11C depicts exemplary gateway common media processing components on the egress side 1120.
  • FIG. 11C begins with egress TG 234 receiving packets 1122.
  • packets are buffered to compensate for jitter 1124, and comfort noise 1126 can be inserted into the call.
  • Comfort background noise process 1126 can provide reassurance to the party on the other end of the call that the call has not been interrupted, but instead that the other party is merely being silent.
  • decoding process 1128 can be performed by DSP 1108 and echo processing 1130 can detect and cancel echo.
  • digital bit stream media (e.g., a DS0), is transferred to a telephony interface (e.g., a DS3 port).
  • a telephony interface e.g., a DS3 port
  • Additional media stream processing functions internal to TGs 232, 234 can include, for example, the ancillary processes of silence detection and suppression 1150, voice activation, and comfort noise insertion 1126.
  • the media stream processing functions include, for example, the major core functionality needed for TGs 232, 234.
  • trunking gateways 232, 234 can also be included.
  • Other functional components can include the provisioning and maintenance of trunking gateways 232, 234.
  • TGs 232, 234 provide voice network connectivity to the traditional public switched telephone network (PSTN).
  • PSTN public switched telephone network
  • TGs 232, 234 can accept co-carrier and feature group-D (FG-D) trunks. It would be apparent to those skilled in the art that TGs 232, 234 can accept other telecommunications trunks.
  • TGs 232, 234 allow for termination of SS7 signaled calls to and from telecommunications network 200.
  • TGs 232, 234 can convert the media stream into packets for transmission over data network 112.
  • TGs 232, 234 also provide a management interface for remote management, control and configuration changes.
  • TGs 232, 234 can interface to multiple components of telecommunications network 200.
  • TGs 232, 234 can interface with, for example, the PSTN for carrying media, soft switch 204 for communication of control messages from soft switch 204, the voice network interface of data network 112 for carrying packetized voice media, and network management component 118 for sending SNMP alerts to the network operation center (NOC).
  • NOC network operation center
  • TGs 232,234 interface to the PSTN via co-carrier or FG-D trunks. These trunks are groomed via DACS 242, 244, to allow multiple two-way 64 kilobits per second (KPS) circuits to pass the media stream into and out of TGs 232, 234.
  • KPS kilobits per second
  • the PSTN interface to TGs 232, 234 provides all low level hardware control for the individual circuits and allows the interface to look like another switch connection to the PSTN network.
  • TGs 232, 234 also interface with soft switch 204.
  • the TG to soft switch interface 412 is used to pass information needed to control the multiple media streams.
  • Soft switch 204 controls all available circuit channels that connect through TGs 232, 234.
  • TG to soft switch interface 412 uses the physical IP network interface cards (NICs) 1112-1114 to send and receive control information to and from soft switch 204 using the IPDC protocol.
  • NICs IP network interface cards
  • TGs 232, 234 interface with a voice virtual private network (VPN) that is overlaid on an IP data network 112.
  • the TG to voice VPN interface sends or receives voice packets on the IP side of the network from TGs 232,234 to other network components, e.g., to another of TGs 232, 234.
  • TG to voice VPN interface in a preferred embodiment, can physically be a 100 BaseT Ethernet interface, but can be logically divided into virtual ports that can be addressable via soft switch 204.
  • the media stream can be connected through this interface, i.e., the TG to voice VPN interface, to a distant connection with a real-time transport protocol (RTP) connection.
  • RTP real-time transport protocol
  • TGs 232, 234 can also interface with network management component (NMC) 118 for the purposes of communicating network management SNMP alerts.
  • NMC network management component
  • the TGs 232, 234 to SNMP interface is a management interface that can be connected to NMC 118 of the network management network through a dedicated connection on TGs 232, 234.
  • SNMP messages that are generated at TGs 232, 234 can be passed to the network operations center (NOC) through the TG to SNMP interface.
  • NOC network operations center
  • messages and commands from the NOC can be passed to TGs 232, 234 through this interface for several purposes including, for example, network management, configuration and control.
  • An AG is a gateway that enables customers to connect via a Direct Access Line (DAL) from their customer premise equipment (CPE), such as, for example, a private branch exchange (PBX), to the telecommunications network.
  • CPE customer premise equipment
  • PBX private branch exchange
  • the AG terminates outgoing and incoming calls between the CPE, the telecommunications network and the PSTN.
  • FIG. 12 depicts an AG high level functional architecture 1200.
  • FIG. 12 includes calling party 122, connected via customer facility 128 to DAL (e.g., either an ISDN PRI or a T1 DAL).
  • DAL e.g., either an ISDN PRI or a T1 DAL.
  • a PRI DAL is connected from the PSTN-to-PSTN interface card 1202a.
  • PSTN interface card 1202a includes ISDN signaling and media, meaning it includes both bearer channels (B-channels) for carrying media and data channels (D-channels) for carrying ISDN signaling information.
  • a T1 DAL can be connected from the PSTN to a PSTN interface card 1202b, supporting T1 in-band channel associated signaling (CAS).
  • PSTN interface cards 1202a, 1202b are connected to TDM bus 1204.
  • TDM bus 1204 Using TDM bus 1204, incoming T1 and PRI signals are broken into separate DS1 signals 1206.
  • DS1 1206 is then encoded via DSP-based encode/decode 1208.
  • the signal is packetized via packet bus 1210, to be transmitted via IP interface cards 1212-1214, over data network 112.
  • IP packets containing signaling information e.g., D-channel
  • IP packets containing media are transmitted to other media gateways, i.e. access servers such as an AG or TG
  • IP interface card 1214 includes both control and signaling information in its packets. This is illustrated showing IPDC protocol control information 1216 and signaling information 1218.
  • AG 238 delivers signaling information inband over data network 112 to soft switch 204. Accordingly, calling party 122 need not have its customer facility 128 have connectivity with SS7 signaling network 114.
  • AG 238 is functionally equivalent to TG 232.
  • AG 238 differs from TG 232 only in the circuit types and scale of the terminated circuits supported.
  • the circuit types and scale of terminated circuits supported drives the line side cards and signaling that AG 238 provides to a PBX or other customer facility 128.
  • the circuit associated and in-band signaling provided by the PBX or customer facility 128 must be passed from AG 238 to soft switch 204 via the IPDC protocol.
  • AG 238 receives call-processing information from soft switch 204.
  • AGs 238, 240 interface to several components of telecommunications network 200.
  • the interfaces of AGs 238, 240 include interfaces facing the network, i.e., data network 112, and network management component 118, as described for TGs 232, 234 above.
  • AGs 238, 240 also interface on the line side, through line side card interfaces, which can be needed to support in-band T1 and ISDN primary rate interface (ISDN PRI) circuits.
  • ISDN PRI ISDN primary rate interface
  • In-band T1 and ISDN PRI interfaces can be provisioned on an as-needed basis on AGs 238,240, to support the equipment that can terminate the circuit on the far end.
  • the ISDN PRI can support standard ISDN circuit associated D-channel signaling in the 23B+1 D, NB+1D and NB+2D (bearer (B-) and data (D-) channel) configurations.
  • the circuit can support wink start or loop start signaling.
  • Wink start refers to seizing a circuit by using a short duration signal.
  • the signal is typically of a 140 millisecond duration.
  • the wink indicates the availability of an incoming register for receiving digital information from a calling switch. Wink starts are used in telephone systems which use address signaling.
  • Loop start refers to seizing a circuit using a supervisory signal.
  • a loop start signal is typically generated by taking the phone off hook. With a loop start, a line is seized by bridging a tip and ring (i.e., the wires of the telephone line) through a resistance.
  • a loop start trunk is the most common type of trunk found in residential installations. The ring lead is connected to -48 V and the tip lead is connected to 0 V (i.e., connected to ground).
  • a "loop" ring can be formed through the telephone to the tip.
  • a central office (CO) can ring a telephone by sending an AC voltage to the ringer within the telephone. When the telephone goes off-hook, the DC loop is formed. The CO detects the loop and the fact that it is drawing a DC current, and stops sending the ringing voltage.
  • Ground starting refers to seizing a trunk, where one side of a two-wire trunk (the ring conductor of the tip and ring) is temporarily grounded to get a dial tone. Ground starts are typically used for CO to PBX connections. Ground starting is effectively a handshaking routine that is performed by the CO and PBX. The CO and PBX agree to dedicate a path so that incoming and outgoing calls cannot conflict, so that "glare" cannot occur.
  • the PBX can check to see if a CO ground start trunk has been dedicated. In order to see if the trunk has been dedicated, the PBX checks to see if the tip lead is grounded. An undedicated ground start trunk has an open relay between 0 V (ground) and the tip lead connected to the PBX. If the trunk has been dedicated, the CO will close the relay and ground the tip lead.
  • the PBX can also indicate to the CO that it requires a trunk.
  • the PBX has a PBX CO caller circuit.
  • the PBX CO caller circuit can call a CO ground start trunk.
  • the PBX CO caller circuit briefly grounds the ring lead causing DC current to flow. The CO detects the current flow and interprets it as a request for service from the PBX.
  • Glare occurs when both ends of a telephone line or trunk are seized at the same time for different purposes or by different users. Glare resolution refers to the ability of a system to ensure that if a trunk is seized by both ends simultaneously, then one caller is given priority, and the other is switched to another trunk.
  • AGs 238 and 240 interface to the PSTN via T1 CAS signaling and ISDN PRI trunks.
  • ISDN PRI trunks are groomed via the DACS 242 and 244 to allow multiple two-way 64 kps circuits to pass signaling information circuits to pass signaling information and the media stream into and out of AGs 238 and 240.
  • the AG to PSTN interface provides all low level hardware control for the individual circuits.
  • the AG to PSTN interfaces, specifically, PSTN interface cards 1202a and 1202, also allow the interface to look like a switch connection to the PSTN network.
  • AG to soft switch interface 414 can be used to pass information needed to control multiple media streams.
  • Soft switch 204 can control all available circuit channels that connect through AGs 238, 240.
  • AG to soft switch interface 414 can use the physical voice network interface card to send and receive control information to and from soft switch 204 using the IPDC protocol.
  • AGs 238, 240 can have a separate physical interface to network management component (NMC) 118.
  • AG 238 has network management IP interface 1006, which sends network management alarms and events in the SNMP protocol format to NMC 118.
  • the AG to NMC interface can be used for delivery of SNMP messages and additional functions. Examples of additional functions that can be defined include, for example, functions for provisioning, updating, and passing special alarms and performance parameters to AGs 238, 240 from the network operation center (NOC) of NMC 118.
  • NOC network operation center
  • NAS Network Access Server
  • NASs 228, 230 accept control information from soft switch 204 and process the media stream accordingly. Modem traffic is routed to the internal processes within NASs 228,230 to terminate the call and route the data traffic out to data network 112.
  • the reader is directed to U.S. Patent Application entitled “System and Method for Bypassing Data from Egress Facilities", filed concurrently herewith, Attorney Docket No. 1757.0060000, which is incorporated herein by reference in its entirety, describing with greater details the interaction between NASs 228, 230 and control server soft switch 204.
  • FIG. 13 depicts a NAS high-level architecture 1300.
  • FIG. 13 includes calling party 102 calling into carrier facility 126. Its signaling information is routed via out-of-band signaling network 114 to SS7 GW 208. The signaling information 1318 is sent to soft switch 204.
  • NAS 228 receives trunk interfaces from the PSTN at PSTN interface card 1302.
  • PSTN interface card 1302 is connected to TDM bus 1304.
  • TDM bus 1304 can break out separate DS1 signals 1306. These DSI signals 1306 can be terminated to modems 1308. Modem 1308 can convert the incoming data stream from a first format to a second format over packet bus 1310 to IP interface card 1312 or 1314. It is important to note that IP interfaces 1312 and 1314 are the same.
  • Interface card 1312 carries media (e.g., data, voice traffic, etc.) over data network 112. The media can be sent over multiple routers in data network 112 to the media's final destination. IP interface card 1314 transmits packets of information through data network 112 to soft switch 204, including control information 1316 in the IPDC protocol format. Interface cards 1312 and 1314 can also perform additional functions
  • NAS 228 includes network management interface card (NMIC) 1004, for providing network management alarms and events in an SNMP protocol format to network management component 118.
  • NMIC network management interface card
  • Telecommunications network 200 supports interaction with NASs via communication of control information from soft switch 204.
  • the interfaces between NASs 228, 230 and the other network components of telecommunications network 200, can be identical to those found on TGs 232, 234, with the exception of the FG-D interface.
  • NASs 228, 230 can interface to the PSTN via co-carrier trunks.
  • the co-carrier trunks can be groomed via the DACS 242,244, to allow multiple two-way 64 kps circuits to pass the media stream into and out of NASs 228, 230.
  • the NASs to PSTN interface provides all low level hardware control for the individual circuits.
  • the NASs to PSTN interface looks like another switch connection to the PSTN network.
  • NASs 228,230 interface with soft switch 204 in order to pass information required to control the multiple media streams.
  • Soft switch 204 via the NASs to soft switch interface, can control all available circuit channels that connect through NASs 228, 230.
  • the interface between NASs 228, 230 and soft switch 204 uses the physical voice network interface card (NIC) to send and receive control information to and from soft switch 204 and NASs 228, 230 via the IPDC protocol.
  • NIC physical voice network interface card
  • NASs 228,230 can interface with the backbone network of data network 112.
  • the NASs to backbone interface of data network 112 can allow the media stream to access the data network 112 and to terminate to any termination with an IP address including public Internet and world wide web sites, and other Internet service providers (ISP).
  • ISP Internet service providers
  • Modem traffic can enter NASs 228, 230 in the form of serial line interface protocol (SLIP) or a point to point protocol (PPP) protocol and can be terminated to modems and can then be converted into another protocol, such as, for example, an IPX, an Apple Talk, a DECNET protocol, an RTP protocol, an Internet protocol (IP) protocol, a transmission control protocol/ user datagram protocol (UDP), or any other appropriate protocol for routing to, for example, another private network destination.
  • SLIP serial line interface protocol
  • PGP point to point protocol
  • IPX Internet protocol
  • UDP transmission control protocol/ user datagram protocol
  • NASs 228, 230 can use a separate physical interface for communication of SNMP alerts and messages to NMC 118.
  • the NAS to NMC interface can be used for additional functions. Examples of additional functions that can be defined include, for example, provisioning, updating, and passing special alarms, and performance parameters to NASs 228, 230 from the network operations center (NOC).
  • NOC network operations center
  • DACS Digital Cross-Connect System
  • FIG. 14 illustrates exemplary DACS 242 in detail.
  • DACS 242 is a time division multiplexer providing switching capability for incoming trunks.
  • voice and data traffic comes into DACS 242 from carrier facility 126 on incoming trunks.
  • DACS 242 receives a signal from soft switch 204 (over data network 112) indicating how DACS 242 is to switch the traffic.
  • Soft switch 204 can switch the incoming traffic onto either circuits directed to TG 232. or circuits directed to NAS 228.
  • a DACS 242 is a digital switching machine, employed to manage or "groom" traffic at a variety of different traffic speeds. Grooming functions of DACS 242 include the consolidation of traffic from partly filled incoming lines with a common destination and segregation of incoming traffic of differing types and destinations.
  • a traditional DACS 242 can have one of several available architectures. Example architectures, which accommodate different data rates and total port counts, include narrowband (or 1/0), wideband (or 3/1), and broadband (or 3/3).
  • DACS 242 As backbone traffic has grown, with increased data traffic, there is an emerging need for even higher capacity DACS 242, having interface speeds of OC-48 and beyond, as well as cell and packet-switching capabilities to accommodate the increasing data traffic.
  • DACS e.g., DACS 242
  • DACS 242 are migrating to include higher-speed switching matrices capable of terabit throughput.
  • DACS 242 can also include high-speed optical interfaces.
  • Telecommunications network 200 can also make use of virtual DACS (VDACS).
  • VDACS are conceptually the use of a computer software controlled circuit switch.
  • a DACS can be built which is capable of intercommunicating with a soft switch via, a protocol such as, for example, internet protocol device control (IPDC), to perform the functionality of a DACS.
  • IPDC internet protocol device control
  • a NAS is used to terminate co-carrier, or local trunks, and a TG is used to terminate long distance trunks.
  • a voice call could be transmitted to the TG for termination.
  • One approach that can be used to terminate this voice call includes occupying an outgoing channel to transmit the call out of the NAS and into the TG.
  • Another approach uses a commandable DACS, a VDACS.
  • the VDACS can cross-connect on command, so as to act as a commandable circuit switch.
  • the soft switch can send a command down to the VDACS via IPDC, for example.
  • a VDACS can be built by using a traditional DACS with the addition of application program logic supporting control and communication with a soft switch.
  • ANSs 246, 248 store pre-recorded announcements on disk in an encoded format.
  • ANSs 246, 248 provide telecommunications network 200 with the ability to play pre-recorded messages and announcements, at the termination of a call. For example, ANSs 246, 248 can play a message stating that "all circuits are busy.”
  • ANSs 246, 248 can be included in TG 232 and/or AG 238. The features of this embodiment are dependent on the amount of resources in TG 232 and AG 238.
  • This internal announcement server capability is shown in FIG. 10A , including, for example, ANS 1008 in TG 232 and ANS 1010 in AG 238. It would be apparent to those skilled in the art that ANS functionality can be placed in other systems, such as, for example, soft switch 204 and NAS 1004.
  • ANSs 246, 248 are applications running on one or more separate servers, as shown in FIG. 15.
  • FIG. 15 depicts an announcement server (ANS) component interface design 1500.
  • FIG. 15 includes ANS 246, which is in communication with TG 232, AG 238 and soft switch 204 over data network 112.
  • ANS 246 can be controlled by soft switch 204 via the IPDC protocol.
  • ANS 246 can send network management alerts and events to network management component (NMC) 118.
  • NMC network management component
  • Data distributor 222 can send announcement files to ANS 246.
  • a benefit of providing separate ANSs 246, 248 is that a more robust database of announcements can be stored and made available for use by the soft switch than is supported in conventional networks. Another benefit of a separate ANS 246, 248 is that less storage is required in TGs and AGs since the announcement functionality is supported by the server of ANSs 246,248 server. ANSs 246, 248 can be controlled by one or more soft switches to play the voice messages, via the IPDC protocol.
  • Soft switch 204 After determining that an announcement should be played, Soft switch 204 chooses an ANS 246 or 248 that is closest to the point of origination for the call, if available.
  • the ANS and gateway site establish a real-time transport protocol (RTP) session for the transmission of the voice announcement. Then ANS 246 or 248 streams the file over RTP to the terminating gateway.
  • RTP real-time transport protocol
  • ANSs 246, 248 can store the message files in each of the media coder/decoders (CODECs) that the network supports.
  • ANSs 246, 248 can send announcements stored in the format of the G.711, G.726, and G.728, and other standard CODECs.
  • the soft switch can direct ANS 246, 248 to play announcements using other CODECS if the network enters a state of congestion.
  • Soft switch 204 can also direct ANS 246, 248 to play announcements using other CODECs if the gateway or end client is an IP client that only supports a given CODEC.
  • the CODEC of an announcement can be modified while the announcement is playing.
  • ANS 246 will now be described with greater detail with reference to FIG. 15 .
  • ANS 246 has several interfaces.
  • ANS interfaces include the provisioning, control, alarming, and voice path interfaces.
  • ANS 246 also has several data paths.
  • the path from ANS 246 to TG 232 or to AG 238, have a common voice path interface (i.e., which is the same for TG 232 and AG 238).
  • the voice path interface can use RTP and RTCP.
  • ANS 246 to soft switch 204 interface provides for a data path using the internet protocol device control (IPDC) protocol to control announcement server 246.
  • IPDC internet protocol device control
  • the ANS 246 to SNMP agent in network management component 118 data path is used to send alarm and event information from ANS 246 to SNMP agent via SNMP protocol.
  • Data distributor 222 to announcement server 246 data path carries announcement files between announcement server 246 and data distributor 222.
  • the provisioning interface downloads, via a file transfer protocol (FTP), encoded voice announcement files to announcement server 246.
  • FTP file transfer protocol
  • Announcement server 246 uses a separate physical interface for all SNMP messages and additional functions that can be defined. Examples of additional functions that can be defined include provisioning, updating, and passing of special alarms and performance parameters to announcement servers 246 from NOC 2114.
  • announcement server 246 is located in soft switch site 104. It would be apparent to those skilled in the art that announcement server 246 could be placed in other parts of telecommunications network 200.
  • data network 112 can be a packet-switched network.
  • a packet-switched network such as, for example, an ATM network, unlike a circuit switch network, does not require dedicated circuits between originating and terminating locations within the packet switch network.
  • the packet-switched network instead breaks a message into pieces known as packets of information. Such packets are then encapsulated with a header which designates a destination address to which the packet must be routed.
  • the packet-switched network then takes the packets and routes them to the destination designated by the destination address contained in the header of the packet.
  • FIG. 16A depicts a block diagram of an exemplary soft switch/gateway network architecture 1600.
  • FIG. 16A illustrates a more detailed version of an exemplary data network 112.
  • data network 112 is a packet-switched network, such as, for example, an asynchronous transfer mode (ATM) network.
  • FIG. 16 includes western soft switch site 104 and gateway sites 108, 110 connected to one another via data network 112. Data is routed from western soft switch 104 to gateway sites 108, 110 through data network 112, via a plurality of routers located in western soft switch site 104 and gateway sites 108, 110.
  • ATM asynchronous transfer mode
  • Western soft switch site 104 of FIG. 16A includes soft switches 204a, 204b, 204c, SS7 GWs 208, 210, CSs 206a, 206b, RSs 212a, 212b and RNECPs 224a, 224b, all interconnected by redundant connections to ethernet switches (ESs) 332, 334.
  • ESs 332, 334 are used to interconnect the host computers attached to them, to create an ethernet-switched local area network (LAN).
  • ESs 332, 334 are redundantly connected to routers 320, 322.
  • the host computers in the local area network included in western soft switch site 104 can communicate with host computers in other local area networks, e.g., at gateway sites 108, 110, via routers 320,322.
  • Gateway site 108 of FIG. 16A includes TGs 232a, 232b, AGs 238a, 238b and NASs 228a, 228b, 228c, interconnected via redundant connections to ESs 1602,1604.
  • ESs 1602, 1604 interconnect the multiple network devices to create a LAN. Information can be intercommunicated to and from host computers on other LANs via routers 1606, 1608 at gateway site 108. Routers 1606, 1608 are connected by redundant connections to ESs 1602, 1604.
  • Gateway site 110 of FIG. 16A includes TGs 234a, 234b, AGs 240a, 240b, and NASs 230a, 230b, 230c, connected via redundant connections to ESs 1610, 1612 to form a local area network.
  • Ethernet switches (ESs) 1610, 1612 can in turn intercommunicate information between the LAN in gateway site 110 and LANs at other sites, e.g., at western soft switch site 104 and gateway site 108 via routers 1614, 1616.
  • Routers 1614, 1616 are connected to ESs 1610, 1612 via redundant connections.
  • Routers 320, 322 of western soft switch site 104, routers 1606, 1608 of gateway site 108, and routers 1614, 1616 of gateway site 110 can be connected via NICs, such as, for example, asynchronous transfer mode (ATM) interface cards in routers 320, 322, 1606, 1608, 1614, 1616 and physical media such as, for example, optical fiber link connections, and/or copper wire connections.
  • Routers 320, 322, 1606, 1608, 1614, 1616 transfer information between one another and intercommunicate according to routing protocols.
  • Data network 112 can include a plurality of network routers.
  • Network routers are used to route information between multiple networks. Routers act as an interface between two or more networks. Routers can find the best path between any two networks, even if there are several different networks between the two networks.
  • Network routers can include tables describing various network domains.
  • a domain can be thought of as a local area network (LAN) or wide area network (WAN).
  • Information can be transferred between a plurality of LANs and/or WANs via network devices known as routers.
  • Routers look at a packet and determine from the destination address in the header of the packet the destination domain of the packet. If the router is not directly connected to the destination domain, then the router can route the packet to the router's default router, i.e. a router higher in a hierarchy of routers. Since each router has a default router to which it is attached, a packet can be transmitted through a series of routers to the destination domain and to the destination host bearing the packet's final destination address.
  • LAN local area network
  • WAN wide area network
  • LANs Local Area Networks
  • WANs Wide Area Networks
  • a local area network can be thought of as a plurality of host computers interconnected via network interface cards (NICs) in the host computers.
  • NICs network interface cards
  • the NICs are connected via, for example, copper wires so as to permit communication between the host computers.
  • Examples of LANs include an ethernet bus network, an ethernet switch network, a token ring network, a fiber digital data interconnect (FDDI) network, and an ATM network.
  • FDDI fiber digital data interconnect
  • a wide area network is a network connecting host computers over a wide area.
  • network interfaces interconnecting the LANs and WANs must exist.
  • An example of a network interface is a router discussed above.
  • a network designed to interconnect multiple LANs and/or WANs is known as an internet.
  • An internet can transfer data between any of a plurality of networks including both LANs and WANs. Communication occurs between host computers on one LAN and host computers on another LAN via, for example, an internet protocol (IP) protocol.
  • IP internet protocol
  • the IP protocol requires each host computer of a network to have a unique IP address enabling packets to be transferred over the internet to other host computers on other LANs and/or WANs that are connected to the internet.
  • An internet can comprise a router interconnecting two or more networks.
  • the "Internet” (with a capital “I”) is a global internet interconnecting networks all over the world.
  • the Internet includes a global network of computers which intercommunicate via the internet protocol (IP) family of protocols.
  • IP internet protocol
  • Intranet is an internet which is a private network that uses internet software and internet standards, such as the internet protocol (IP).
  • IP internet protocol
  • Data network 112 includes a plurality of wires, and routes making up its physical hardware infrastructure.
  • Network protocols provide the software infrastructure of data network 112.
  • Telecommunications vendors have moved away from proprietary network protocols and technologies to multi-vendor protocols. However, it can be difficult for all necessary vendors to agree on how to add new features and services to a multi-vendor protocol. This can be true because vendor-specific protocols can in some cases offer a greater level of sophistication. For example, initial versions of asynchronous transfer mode (ATM) completed by the ATM Forum did not have built-in quality of service (QoS) capabilities. Recent releases of the specification added those features, including parameters for cell-transfer delay and cell-loss ratio. However, interoperability among equipment of different vendors and device performance still need improvement.
  • ATM asynchronous transfer mode
  • QoS quality of service
  • IP classes of service could provide a rough equivalent to ATMs QoS.
  • IP classes of service is included as part of the IETF's integrated services architecture (ISA).
  • ISA's proposed elements include the resource reservation protocol (RSVP), a defined packet scheduler, a call admission control module, an admission control manager, and a set of policies for implementing these features (many of the same concepts already outlined in ATM QoS).
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • IP Internet protocol
  • TCP/IP transmission control protocol/internet protocol
  • IPX/SPX from Novell's NetWare network operating system (NOS).
  • NOS Novell's NetWare network operating system
  • IPX/SPX is losing ground to TCP/IP.
  • Novell has announced that it will incorporate native IP support into NetWare, ending NetWare's need to encapsulate IPX packets when carrying them over TCP/IP connections.
  • Both UNIX and Windows NT servers can use TCP/IP.
  • Banyan's VINES, IBM's OS/2 and other LAN server operating systems can also use TCP/IP.
  • IPv4 Internet Protocol (IP)v4 and IPv6
  • IPv6 (previously called next-generation IP or IPng) is a backward-compatible extension of the current version of the Internet protocol, IPv4.
  • IPv6 is designed to solve problems brought on by the success of the Internet (such as running out of address space and router tables). IPv6 also adds needed features, including circuiting security, auto-configuration, and real-time services similar to QoS. Increased Internet usage and the allocation of many of the available IP addresses has created an urgent need for increased addressing capacity.
  • IPv4 uses a 32-byte number to form an address, which can offer about 4 billion distinct network addresses. In comparison, IPv6 uses 128-bytes per address, which provides for a much larger number of available addresses.
  • RSVP helps network managers allocate bandwidth based on the bandwidth requirements of an application.
  • RSVP is an emerging communications protocol that signals a router to reserve bandwidth for real-time transmission of data, video, and audio traffic.
  • RSVP Resource reservation protocols that operate on a per-connection basis can be used in a network to elevate the priority of a given user temporarily.
  • RSVP runs end to end to communicate application requirements for special handling. RSVP identifies a session between a client and a server and asks the routers handling the session to give its communications a priority in accessing resources. When the session is completed, the resources reserved for the session are freed for the use of others.
  • RSVP offers only two levels of priority in its signaling scheme. Packets are identified at each router hop as either low or high priority. However, in crowded networks, two-level classification may not be sufficient. In addition, packets prioritized at one router hop might be rejected at the next.
  • RSVP does not attempt to govern who should receive bandwidth, and questions remain about what will happen when several users all demand a large block of bandwidth at the same time.
  • the technology outlines a first-come, first-served response to this situation.
  • the IETF has formed a task force to address the issue.
  • RSVP provides a special level of service
  • many people equate QoS with the protocol.
  • RSVP is only a small part of the QoS picture because it is effective only as far as it is supported within a given client/server connection.
  • RSVP allows an application to request latency and bandwidth, RSVP does not provide for congestion control or network-wide priority with the traffic flow management needed to integrate QoS across an enterprise.
  • RTP Real-time Transport Protocol
  • RTP is an emerging protocol for the Internet championed by the audio/video transport workgroup of the IETF. RTP supports real-time transmission of interactive voice and video over packet-switched networks. RTP is a thin protocol that provides content identification, packet sequencing, timing reconstruction, loss detection, and security. With RTP, data can be delivered to one or more destinations, with a limit on delay.
  • RTP and other Internet real-time protocols focus on the efficiency of data transport.
  • RTP and other Internet real-time protocols are designed for communications sessions that are persistent and that exchange large amounts of data.
  • RTP does not handle resource reservation or QoS control. Instead, RTP relies on resource reservation protocols such as RSVP, communicating dynamically to allocate appropriate bandwidth.
  • RSVP resource reservation protocols
  • RTP adds a time stamp and a header that distinguishes whether an IP packet is data or voice, allowing prioritization of voice packets, while RSVP allows networking devices to reserve bandwidth for carrying unbroken multimedia data streams.
  • Real-time Control Protocol is a companion protocol to RTP that analyzes network conditions.
  • RTCP operates in a multi-cast fashion to provide feedback to RTP data sources as well as all session participants.
  • RTCP can be adopted to circumvent datagram transport of voice-over-IP in private IP networks.
  • software can adjust to changing network loads by notifying applications of spikes, or variations, in network transmissions.
  • telephony software can switch compression algorithms in response to degraded connections.
  • Multi-casting involves the broadcasting of a message from one host to many hosts in a one-to-many relationship.
  • a network device broadcasts a message to a select group of other devices such as PCS or workstations on a LAN, WAN. or the Internet.
  • a router might send information about a routing table update to other routers in a network.
  • IP multi-casting Several protocols are being implemented for IP multi-casting, including upgrades to the Internet protocol itself. For example, some of the changes in the newest version of IP, IPv6, will support different forms of addressing for uni-cast (point-to-point communications), any cast (communications with the closest member of a device group), and multi-cast. Support for IP multi-casting comes from several protocols, including the Internet group management protocol (IGMP), protocol-independent multi-cast (PIM) and distance vector multi-cast routing protocol (DVMRP). Queuing algorithms can also be used to ensure that video or other multi-cast data types arrive when they are supposed to without visible or audible distortion.
  • IGMP Internet group management protocol
  • PIM protocol-independent multi-cast
  • DVMRP distance vector multi-cast routing protocol
  • Real-time transport protocol is currently an IETF draft, designed for end-to-end, real-time delivery of data such as video and voice.
  • RTP works over the user datagram protocol (UDP), providing no guarantee of in-time delivery, quality of service (QoS), delivery, or order of delivery.
  • UDP user datagram protocol
  • QoS quality of service
  • RTP works in conjunction with a mixer and translator and supports encryption and security.
  • the real-time control protocol (RTCP) is a part of the RTP definition that analyzes network conditions. RTCP provides mandatory monitoring of services and collects information on participants.
  • RTP communicates with RSVP dynamically to allocate appropriate bandwidth.
  • RSVP Resource Reservation Protocol
  • RSVP protocol is used by a host, on behalf of an application, to request a specific QoS from the network for particular data streams or flows. Routers can use the RSVP protocol to deliver QoS control requests to all necessary network nodes to establish and maintain the state necessary to provide the requested service. RSVP requests can generally, although not necessarily, result in resources being reserved in each node along the data path.
  • RSVP is not itself a routing protocol. RSVP is designed to operate with current and future uni-cast and multi-cast routing protocols. An RSVP process consults the local routing database to obtain routes. In the multi-cast case for example, the host sends IGMP messages to join a multi-cast group and then sends RSVP messages to reserve resources along the delivery paths of that group. Routing protocols determines where packets are forwarded. RSVP is concerned with only the QoS of those packets as they are forwarded in accordance with that routing.
  • VPNs Virtual Private Networks
  • a virtual private network is a wide area communications network operated by a telecommunications carrier that provides what appears to be dedicated lines when used, but that actually includes trunks shared among all customers as in a public network.
  • a VPN allows a private network to be configured within a public network.
  • VPNs can be provided by telecommunications carriers to customers to provide secure, guaranteed, long-distance bandwidth for their WANs. These VPNs generally use frame relay or switched multi-megabyte data service (SMDS) as a protocol of choice because those protocols define groups of users logically on the network without regard to physical location.
  • SMDS switched multi-megabyte data service
  • ATM has gained favor as a VPN protocol as companies require higher reliability and greater bandwidth to handle more complex applications.
  • VPNs using ATM offer networks of companies with the same virtual security and QoS as WANs designed with dedicated circuits.
  • the Internet has created an alternative to VPNs, at a much lower cost, i.e. the virtual private Internet.
  • the virtual private Internet (VPI) lets companies connect disparate LANs via the Internet.
  • a user installs either a software-only or a hardware-software combination that creates a shared, secure intranet with VPN-style network authorizations and encryption capabilities.
  • a VPI normally uses browser-based administration interfaces.
  • IP security IP security
  • PPTP point-to-point tunneling protocol
  • L2F layer 2 forwarding protocol
  • L2TP layer 2 tunneling protocol
  • IPsec facilitates secure private sessions across the Internet between organizational firewalls by encrypting traffic as it enters the Internet and decrypting it at the other end, while allowing vendors to use many encryption algorithms, key lengths and key escrow techniques.
  • the goal of IPsec is to let companies mix-and-match the best firewall, encryption, and TCP/IP protocol products.
  • Point-to-point tunneling protocol provides an alternate approach to VPN security than the use of IPsec. Unlike IPsec, which is designed to link two LANs together via an encrypted data stream across the Internet, PPTP allows users to connect to a network of an organization via the Internet by a PPTP server or by an ISP that supports PPTP. PPTP was proposed as a standard to the IETF in early 1996. Firewall vendors are expected to support PPTP.
  • PPTP was developed by Microsoft along with 3Com, Ascend and US Robotics and is currently implemented in WINDOWS NT SERVER 4.0, WINDOWS NT WORKSTATION 4.0, WINDOWS 95 via an upgrade and WINDOWS 98, available from Microsoft Corporation of Redmond, Washington.
  • the "tunneling" in PPTP refers to encapsulating a message so that the message can be encrypted and then transmitted over the Internet.
  • PPTP by creating a tunnel between the server and the client, can tie up processing resources.
  • L2F layer 2 forwarding protocol
  • PPTP layer 2 forwarding protocol
  • L2F resembles PPTP in that it also encapsulates other protocols inside a TCP/IP packet for transport across the Internet, or any other TCP/IP network, such as data network 112.
  • L2F requires a special L2F-compliant router (which can require changes to a LAN or WAN infrastructure), runs at a lower level of the network protocol stack and does not require TCP/IP routing to function.
  • L2F also provides additional security for user names and passwords beyond that found in PPTP.
  • L2TP The layer 2 tunneling protocol
  • Cisco is putting L2TP into its Internet operating system software and Microsoft is incorporating it into WINDOWS NT 5.0.
  • a key advantage of L2TP over IPsec, which covers only TCP/IP communications, is that L2TP can carry multiple protocols.
  • L2TP also offers transmission capability over non-IP networks. L2TP however ignores data encryption, an important security feature for network administrators to employ VPNs with confidence.
  • Data network 112 will now be described in greater detail relating to example packet-switched networks. It will be apparent to persons having skill in the art that multiple network types could be used to implement data network 112, including, for example, ATM networks, frame relay networks, IP networks FDDI WAN networks SMDS networks, X-25 networks, and other kinds of LANs and WANs.
  • SMDS Switched multi-megabyte data service
  • BISDN broadband ISDN
  • ATM Asynchronous Transfer Mode
  • ATM is a high-bandwidth, low-delay, packet-switching, and multiplexing network technology.
  • ATM packets are known as "cells.”
  • Bandwidth capacity is segmented into 53-byte fixed-sized cells, having a header and payload fields.
  • ATM is an evolution of earlier packet-switching network methods such as X.25 and frame relay, which used frames or cells that varied in size. Fixed-length packets can be switched more easily in hardware than variable size packets and thus result in faster transmissions.
  • Each ATM cell contains a 48-byte payload field and a 5-byte header that identifies the so-called "virtual circuit" of the cell.
  • ATM can allocate bandwidth on demand, making it suitable for high-speed combinations of voice, data, and video services.
  • Currently, ATM access can perform at speeds as high as 622 Mbps or higher.
  • ATM has recently been doubling its maximum speed every year.
  • data network 112 is an asynchronous transfer mode (ATM) network.
  • An ATM cell of data network 112 includes a header (having addressing information and header error checking information), and a payload (having the data being carried by the cell).
  • ATM is a technology, defined by a protocol standardized by the International Telecommunications Union (ITU-T), American National Standards Institute (ANSI), ETSI, and the ATM Forum.
  • ITU-T International Telecommunications Union
  • ANSI American National Standards Institute
  • ETSI European Telecommunications Institute
  • ATM comprises a number of building blocks, including transmission paths, virtual paths, and virtual channels.
  • ATM Asynchronous transfer mode
  • ATM is a cell based switching and multiplexing technology designed to be a general purpose connection-oriented transfer mode for a wide range of telecommunications services.
  • ATM can also be applied to LAN and private network technologies as specified by the ATM Forum.
  • ATM handles both connection-oriented traffic directly or through adaptation layers, or connectionless traffic through the use of adaptation layers.
  • ATM virtual connections may operate at either a constant bit rate (CBR) or a variable bit rate (VBR).
  • CBR constant bit rate
  • VBR variable bit rate
  • Each ATM cell sent into an ATM network contains addressing information that establishes a virtual connection from origination to destination. All cells are transferred, in sequence, over this virtual connection.
  • ATM provides either permanent or switched virtual connections (PVCs or SVCs).
  • PVCs or SVCs switched virtual connections
  • ATM is asynchronous because the transmitted cells need not be periodic as time slots of data are required to be in synchronous transfer mode (STM).
  • ATM uses an approach by which a header field prefixes each fixed-length payload.
  • the ATM header identifies the virtual channel (VC). Therefore, time slots are available to any host which has data ready for transmission. If no hosts are ready to transmit, then an empty, or idle, cell is sent.
  • VC virtual channel
  • ATM permits standardization on one network architecture defining a multiplexing and a switching method.
  • Synchronous optical network provides the basis for physical transmission at very high-speed rates.
  • ATM also supports multiple quality of service (QoS) classes for differing application requirements, depending on delay and loss performance.
  • QoS quality of service
  • ATM can also support LAN-like access to available bandwidth.
  • the primary unit in ATM defines a fixed-size cell with a length of 53 octets (or bytes) comprised of a five-octet header and 48-octet payload. Bits in the cells are transmitted over a transmission path in a continuous stream. Cells are mapped into a physical transmission path, such as the North American DS 1, DS3, and SONET; European, E1, E3, and E4; ITU-T STM standards; and various local fiber and electrical transmission payloads. All information is multiplexed and switched in an ATM network via these fixed-length cells.
  • the ATM cell header field identifies the destination, cell type, and priority., and includes six portions.
  • An ATM cell header includes a generic flow control (GFC), a virtual path identifier (VPI), a virtual channel identifier (VCI), a payload type (PT), a call loss priority (CLP), and a header error check (HEC).
  • GFC generic flow control
  • VPI virtual path identifier
  • VCI virtual channel identifier
  • PT payload type
  • CLP call loss priority
  • HEC header error check
  • VPI and VCI hold local significance only, and identify the destination.
  • GFC allows a multiplexer to control the rate of an ATM terminal.
  • PT indicates whether the cell contains user data, signaling data, or maintenance information.
  • CLP indicates the relative priority of the cell, i.e., lower priority cells are discarded before higher priority cells during congested intervals.
  • HEC detects and corrects errors in the header.
  • the ATM cell payload field is passed through the network intact, with no error checking or correction.
  • ATM relies on higher-layer protocols to perform error checking and correction on the payload.
  • a transmission control protocol TCP
  • TCP transmission control protocol
  • the fixed cell size simplifies the implementation of ATM switches and multiplexers and enables implementations at high speeds.
  • ATM switches take traffic and segment it into the fixed-length cells, and multiplex the cells into a single bit stream for transmission across a physical medium.
  • different kinds of traffic can be transmitted over an ATM network including voice, video, and data traffic.
  • Video and voice traffic are very time-sensitive, so delay cannot have significant variations.
  • Data can be sent in either connection-oriented or connectionless mode. In either case, data is not nearly as delay-sensitive as voice or video traffic, conventionally. Conventional, however, data traffic is very sensitive to loss. Therefore, ATM conventionally must discriminate between voice, video, and data traffic. Voice and video traffic requires priority and guaranteed delivery with bounded delay, while data traffic requires, simultaneously, assurance of low loss.
  • data traffic can also carry voice traffic, making it also time-dependent.
  • ATM in one embodiment, multiple types of traffic can be combined over a single ATM virtual path (VP), with virtual circuits (VCs) being assigned to separate data, voice, and video traffic.
  • VP virtual path
  • VCs virtual circuits
  • FIG. 16B depicts graphically the relationship 1618 between a physical transmission path 1620, virtual paths (VPs) 1622, 1624 and 1626, and virtual channels (VCs) 1628, 1630, 1632, 1634, 1636, 1638, 1640, 1642, 1644, 1646, 1648 and 1650.
  • a transmission path 1620 includes one or more VPs 1622, 1624 and 1626.
  • Each VP 1622, 1624 and 1626 includes one or more VCs 1628, 1630, 1632, 1634, 1636,1638, 1640, 1642, 1644, 1646, 1648 and 1650.
  • multiple VCs 1628-1650 can be trunked over a single VP and 1622. Switching can be performed on either a transmission path 1620, VPs 1622-1626, or at the level of VCs 1628-1650.
  • ATM The capability of ATM to switch to a virtual channel level is similar to the operation of a private or public branch exchange (PBX) or telephone switch in the telephone world.
  • PBX public branch exchange
  • a PBX switch each channel within a trunk group can be switched.
  • VC switches Devices which perform VC connections are commonly called VC switches because of the analogy to telephone switches.
  • ATM devices which connect VPs are commonly referred to as VP cross-connects, by analogy with the transmission network.
  • the analogies are intended for explanatory reasons, but should not be taken literally.
  • An ATM cell-switching machine need not be restricted to switching only VCs and cross-connection to only VPs.
  • VPC virtual path connection
  • VCC virtual channel connection
  • VPIs and VCIs are used to route calls through a network. Note that VPI and VCI values must be unique on a specific transmission path (TP).
  • data network 112 can be any of a number of other data-type networks, including various packet-switched data-type networks, in addition to an ATM network.
  • data network 112 can be a frame relay network. It would be apparent to persons having ordinary skill in the art, that a frame relay network could be used as data network 112. Rather than transporting data in ATM cells, data could be transported in frames.
  • Frame relay is a packet-switching protocol used in WANs that has become popular for LAN-to-LAN connections between remote locations. Formerly frame relay access would top out at about 1.5 Mbps. Today, so-called "high-speed" frame relay offers around 45 Mbps. This speed is still relatively slow as compared with other technology such as ATM.
  • Frame relay services employ a form of packet-switching analogous to a streamlined version of X.25 networks.
  • the packets are in the form of frames, which are variable in length.
  • a frame relay network can accommodate data packets of various sizes associated with virtually any native data protocol.
  • a frame relay network is completely protocol independent.
  • a frame relay network embodiment of data network 112 does not undertake a lengthy protocol conversion process, and therefore offers faster and less-expensive switching than some alternative networks.
  • Frame relay also is faster than traditional X.25 networks because it was designed for the reliable circuits available today and performs less-rigorous error detection.
  • IP Internet Protocol
  • data network 112 can be an internet protocol (IP) network over an ATM network. It would be apparent to persons having ordinary skill in the art, that an internet protocol (IP) network (with any underlying data link network) could be used as data network 112. Rather than transporting data in ATM cells, data could be transported in IP datagram packets.
  • IP internet protocol
  • the IP data network can lie above any of a number of physical networks such as, for example, a SONET optical network.
  • FIG. 17C illustrates signaling network 114 in greater detail.
  • signaling network 114 is an SS7 signaling network.
  • the SS7 signaling network 114 is a separate packet-switched network used to handle the set up, tear down, and supervision of calls between calling party 102 and called party 120.
  • SS7 signaling network 114 includes service switching points (SSPs) 104,106,126 and 130, signal transfer points (STPs) 216,218,250a, 250b, 252a and 252b, and service control point (SCP) 610.
  • SSPs service switching points
  • STPs signal transfer points
  • SCP service control point
  • SSPs 104, 106, 126 and 130 are the portions of the backbone switches providing SS7 functions.
  • the SSPs 104, 106, 126 and 130 can be, for example, a combination of a voice switch and an SS7 switch, or a computer connected to a voice switch.
  • SSPs 104, 106, 126 and 130 communicate with the switches using primitives, and create packets for transmission over SS7 signaling network 114.
  • Carrier facilities 126,130 can be respectively represented in SS7 network 114 as SSPs 126, 130. Accordingly, the connections between carrier facilities 126 and 130 and signaling network 114 (presented as dashed lines in FIG. 2A ) can be represented by connections 1726b and 1726d. The types of these links are described below.
  • STPs 216, 218, 250a, 250b, 252a and 252b act as routers in the SS7 network, typically being provided as adjuncts to in-place switches.
  • STPs 216, 218, 250a, 250b, 252a and 252b route messages from originating SSPs 104 and 126 to destination SSPs 106 and 130.
  • STPs 216, 218, 250a, 250b, 252a and 252b can be and are typically provided in "mated pairs" to provide redundancy in the event of congestion or failure and to share resources (i.e. load sharing is done automatically). As illustrated in FIGs.
  • STPs 216, 218, 250a, 250b, 252a and 252b can be arranged in hierarchical levels, to provide hierarchical routing of signaling messages. For example, mated STPs 250a, 252a and mated STPs 250b, 252b are at a first hierarchical level, while mated STPs 216, 218 are at a second hierarchical level.
  • SCP 610 can provide database functions. SCP 610 can be used to provide advanced features in SS7 signaling network 114, including routing of special service numbers (e.g., 800 and 900 numbers), storing information regarding subscriber services, providing calling card validation and fraud protection, and offering advanced intelligent network (AIN) services. SCP 610 is connected to mated STPs 216 and 218.
  • special service numbers e.g. 800 and 900 numbers
  • AIN advanced intelligent network
  • Mated STP pairs are connected together by C links.
  • STPs 216 and 218, mated STPs 250a and 252a, and mated STPs 250b and 252b are connected together by C links 1728a, 1728b, 1728c, 1728d, 1728e and 1728f, respectively.
  • SSPs 104 and 126 and SSPs 106 and 130 are connected together by F links 1734 and 1736, respectively.
  • Mated STPs 250a and 252a and mated STPs 250b and 252b, which are at the same hierarchical level, are connected by B links 1732a, 1732b, 1732c and 1732d.
  • Mated STPs 250a and 252a and mated STPs 216 and 218, which are at different hierarchical levels, are connected by D links 1730a, 1730b, 1730e and 1730f.
  • mated STPs 250b and 252b and mated STPs 216 and 218, which are at different hierarchical levels are connected by D links 1730c, 1730d, 1730g and 1730h.
  • SSPs 104 and 126 and mated STPs 250a and 252a are connected by A links 1726a and 1726b.
  • SSPs 106 and 130 and mated STPs 250b and 252b are connected by A links 1726c and 1726d.
  • SSPs 104 and 126 can also be connected to mated STPs 216 and 218 by E links (not shown). Finally, mated STPs 216 and 218 are connected to SCP 610 by A links 608a and 608b.
  • a links connect SSPs to STPs, or SCPs to STPs, providing network access and database access through the STPs.
  • Bridge (B) links links connect mated STPs to other mated STPs.
  • Cross (C) links C links connect the STPs in a mated pair to one another. During normal conditions, only network management messages are sent over C links.
  • Diagonal (D) links connect the mated STPs at a primary hierarchical level to mated STPs at a secondary hierarchical level.
  • Extended (E) links E links connect SSPs to remote mated STPs, and are used in the event that the A links to home mated STPs are congested.
  • Fully associated (F) links F links provide direct connections between local SSPs (bypassing STPs) in the event there is much traffic between SSPs, or if a direct connection to an STP is not available. F links are used only for call setup and call teardown.
  • STPs Signal Transfer Points
  • STPs Signal transfer points
  • STPs are tandem switches which route SS7 signaling messages long the packet switched SS7 signaling network 114. See the description of STPs with reference to FIG. 17A , in the soft switch site section, and with reference to FIG. 17C above.
  • SSPs Service Switching Points
  • SSPs Service switching points
  • Services control points can provide database features and advanced network features in the SS7 signaling network 114. See the description of SCPs with reference to FIG. 17B in the soft switch site section, and with reference to FIG. 17C above.
  • FIG. 18 depicts a provisioning component and network event component architecture 1800.
  • FIG. 18 includes a spool-shaped component (including provisioning component 117 and network event component 116), and three soft switch sites, i.e. western soft switch site 104, central soft switch site 106 and eastern soft switch site 302.
  • the top elliptical portion of the spool-shaped component illustrates an embodiment of provisioning component 117, including operational support services (OSS) order entry (O/E) component 1802, alternate order entry component 1804 and data distributors 222a and 222b.
  • OSS operational support services
  • O/E alternate order entry
  • data distributors 222a and 222b comprise application programs.
  • data distributors 222a and 222b include ORACLE 8.0 relational databases from Oracle Corporation of Redwood Shores, CA, Tuxedo clients and a BEA M3 OBJECT MANAGEMENT SYSTEM, CORBA-compliant interface, available from BEA Systems, Inc. of San Francisco, CA, with offices in Golden, CO.
  • BEA M3 is based on the CORBA distributed objects standard.
  • BEA M3 is a combination ofBEA OBJECTBROKER CORBA ORB (including management, monitoring, and transactional features underlying BEA TUXEDO), and an object-oriented transaction and state management system, messaging and legacy access connectivity.
  • BEA M3 is scalable, high performance, designed for high availability and reliability, supports transactions, includes CORBA/IIOP ORB, security, MIB-based managment, supports fault management, dynamic load balancing, gateways and adapters, client support, multi-platform porting, data integrity, management, reporting and TUXEDO Services.
  • data distributors 222a and 222b include an application program by the name of automated service activation process (ASAP) available from Architel Systems Corporation of Toronto, Ontario.
  • ASAP automated service activation process
  • Customer service request calls can be placed to a customer service office. Customer service operators can perform order entry of customer service requests via OSS 1802 order entry (O/E) 1803 system. In the event of the unavailability of OSS O/E 1802, customer service requests may be entered via alternate O/E 1804. Customer service requests are inputted into data distributors 222a and 222b for distribution and replication to configuration servers 312a, 312b, 206a, 206b, 316a and 316b which contain customer profile database entries. In addition, provisioning requests can be performed. Replication facilities in data distributors 222a and 222b enable maintaining synchronization between the distributed network elements of telecommunications network 200.
  • data distributors 222a and 222b receive service requests from upstream provisioning components such as, e.g., OSS systems. Data distributors 222a and 222b then translate the service requests and decompose the requests into updates to network component databases. Data distributors 222a and 222b then distribute the updates to voice network components in soft switch sites and gateway sites.
  • FIG. 19A depicts examples of both the upstream and downstream network components interfacing to data distributors 222 and 222b.
  • FIG. 19A depicts data distributor architecture 1900.
  • FIG. 19A includes a data distributor 222 interfacing to a plurality of voice network elements.
  • Voice network elements illustrated in FIG. 19A include SCPs 214a and 214b, configuration servers 206a, 312a and 316a route servers 212a. 212b, 314a, 314b, 316a and 316b TGs 232 and 234, AGs 238 and 240, and SS7 GWSI 208 and 210.
  • data distributor 222 interfaces to a plurality of services. Services include provisioning services 1902, customer profiles/order entry services 1803, OSS 1802, route administration services 1904, service activation services 1906, network administration services 1908, network inventory services 1910 and alternate data entry (APDE) services 1804.
  • APDE alternate data entry
  • Data distributor 222 has a plurality of functions. Data distributor 222 receives provisioning requests from upstream OSS systems, distributes provisioning data to appropriate network elements and maintains data synchronization, consistency and integrity across data centers, i.e., soft switch sites 104, 106, 302.
  • Data distributor 222 accepts various requests from multiple upstream OSS systems 1922,1924,1926,1928 and APDE 1804.
  • Services request processes (SRPs) 1938 manage the upstream interface between data distributor 222 and OSS systems 1922-1928.
  • SRPs 1938 are developed to support communication between individual OSS systems 1802,1922-1928, APDE 1804 and data distributor 222.
  • a common service description layer 1936 acts as an encapsulation layer for upstream applications.
  • Common service description layer 1936 translates service requests from upstream OSS systems 1922-1928 and APDE 1804 to a common format.
  • Common service description layer 1936 buffers the distribution logic from any specific formats or representations of OSS 1922-1928 and APDE 1804.
  • Distribution layer 1930 includes the actual distribution application logic resident within data distributor 222. Distribution layer 1930 manages incoming requests, performs database replications, maintains logical work units, manages application revisions, performs roll-backs when required, maintains synchronization, handles incoming priority schemes and priority queues, and other data distribution functions. Distribution layer 1930 includes access to multiple redundant high-availability database disks 1940, 1942, which can include a database of record.
  • Network element description layer 1932 is an encapsulation layer that insulates data distributor 222 from the individual data formats required by specific network element types.
  • a network element processor (NEP) 1934 performs a role analogous to SRP 1938, but instead for downstream elements rather than upstream elements. NEPs 1934 manage the physical interface between data distributor 222 and heterogeneous network elements 1943, i.e. the down stream voice network elements to which data distributor 222 distributes updates.
  • Heterogeneous network elements 1943 include SCPs 214a and 214b, configuration servers 206a, 212a and 216a, route servers 212a, 212b, 314a, 314b, 316a and 316b, TGs 232 and 234, AGs 238 and 240, and SS7 GWs 208 and 210.
  • Each NEP 1934 handles a particular type of heterogeneous network elements, e.g., route servers.
  • data distributor 222 allows updates directly to distribution layer 1930 via APDE 1804.
  • APDE 1 804 enables update of distribution layer 1930 and allows updates to the network in the unlikely event that an emergency update is required when interfacing OSS systems 1922-1928 upstream application are out of service or down for maintenance activity.
  • APDE 1804 the alternate provisioning order entry system can comprise a small local area network including several PCs and connectivity peripherals.
  • APDE 1804 provides a backup for OSSs 1922-1928.
  • data distributor 222 is an application program BEA M3 available from BEA Systems, Inc. of San Francisco, CA.
  • data distributor 222 could be another application program capable of distributing/replication/rollback of software such as, for example, AUTOMATED SERVICE ACTIVATION PROCESS (ASAP) available from Architel of Toronto, Canada.
  • Example upstream operational support services (OSS) components include application programs which perform multiple functions.
  • FIG. 19C illustrates some example OSS applications 1802 including provisioning application 1902, customer profiles/order entry application 1803, route administration application 1904, service activation triggers 1906, network administration application 1908, network inventory application 1910, alternate provisioning data entry application (APDE) 1804, and trouble ticketing application (not shown). Browsing tools can also be used, such as, for example, a browsing or query application programs.
  • FIG. 19C illustrates a more detailed view of an example embodiment of data distributor 222.
  • Data distributor 222 includes distribution layer 1930 interfacing to database disks 1940 and 1942.
  • Distribution layer 1930 of FIG. 19 interfaces to common service description layer 1936.
  • common service description layer 1936 is a common object request broker architecture (CORBA) compliant server such as, for example, BEA M3 from BEA Systems, Inc. of San Francisco, CA.
  • Alternate provisioning data entry (APDE) 1804 interfaces to CORBA server 1936.
  • Upstream voice provisioning components, i.e., operational support services (OSS) 1922-1928, include application components 1802 and 1902-1910.
  • Provisioning component 1902 has a CORBA client in communication with CORBA server common service description layer 1936.
  • CORBA common object request broker architecture
  • Customer profiles/order entry 1802 includes a CORBA client interface into CORBA server common service description layer 1936.
  • routing administration 1904, network inventory 1910, network administration 1908 and service triggers 1906 all interface via CORBA clients to CORBA server common service description layer 1936.
  • Distribution layer 1930 also interfaces to downstream voice network elements via an application program, i.e., network element description layer 1932.
  • network element description layer 1932 is an application program running on a work station, such as, for example BEA TUXEDO, available from BEA Systems, Inc..
  • Voice network element configuration servers 206, 312a and 314a interface via a TUXEDO client to TUXEDO server network element description layer 1932.
  • Routing servers 212a, 212b, 314a, 314b, 316a and 316b interface via a TUXEDO client to TUXEDO server network element description layer 1932, as well.
  • SS7 GWs 208 and 210, SCPs 214a and 214b, AGs 238 and 240, and TGs 232 and 234, interface to TUXEDO server network element description layer 1932 via TUXEDO clients.
  • BEA TUXEDO available from BEA Systems, Inc. of San Francisco, CA (Colorado Springs and Denver/Golden, CO office) supports among other functions, rollback and data integrity features.
  • FIG. 19C also includes database of record (DOR) 1940, 1942.
  • FIG. 19E includes a more detailed illustration of a specific example embodiment of the data distributor and provisioning element 116.
  • FIG. 19E includes DOR 1940 and 1942, which can be in a primary/secondary relationship for high availability purposes.
  • DORs 1940,1942 can have stored on their media, images of the Route Server and Configuration Server databases.
  • the functions of route server 314a and configuration server 312a are performed by the same physical workstation element, a routing and configuration database (RCDB).
  • RCDB routing and configuration database
  • DOR 1940 can be used for referential integrity.
  • ORACLE relational database management (RDBMS) databases e.g., ORACLE 8.0 RDBMS can support the use of a foreign key between a database and an index.
  • DOR 1940 can be used to maintain integrity of the database.
  • DOR 1940 sets constraints on the RCDB databases.
  • DOR 1940 is used to maintain integrity of RCDB data and can be used to query data without affecting call processing.
  • DOR 1940 supports parity calculations to
  • FIG. 19E includes distribution layer 1930 which can be used to distribute service level updates of telecommunications network system software to network elements using database replication features of, e.g., ORACLE 8.0.
  • Other business processes demand updating the software on network elements.
  • other business processes requiring updates include, NPA splits. NPA splits, occur when one area code becomes two or more area codes. An NPA split can require that thousands of rows of numbers must be updated.
  • FIG. 19E includes an automated tool to distribute changes, i.e. a routing administration tool (RAT) 1904.
  • RAT routing administration tool
  • FIG. 19E also includes data distributor common interface (DDCI) 1999, which can be thought of as an advanced programming interface (API) functional calls that OSS developers can invoke in writing application programs.
  • OSS applications include programs such as, e.g., provisioning, order management and billing, (each of which can require the means to provision the RCDB. i.e., RS and CS, or can provide updates to the database of record (DOR).
  • FIG. 19E illustrates a data distributor including BEA M3, a CORBA-compliant interface server 1936 with an imbedded TUXEDO layer.
  • BEA M3 communicates through the CORBA server interface 1936 to CORBA- compliant clients.
  • CORBA compliant distributed object connectivity software includes, for example, VISIGENICS VISIBROKER. available from Inprise Corporation, of Scotts Valley, CA.
  • DOR 1940 includes a plurality of relational database tables including each EO, NPA, NXX, LATA, and state. Each EO can home to 150,000 NPA/NXXs. Multiple inputs must be replicated into DOR 1040.
  • LEG Lockheed Martin Local Exchange and Routing Guide
  • FIG. 19E demonstrates an exemplary monthly reference data update process 1957.
  • Monthly, a LERG 1941 compact disk (CD) is received by the carrier including changes to all of the 12 tables.
  • Process 1957 includes merging an image snapshot of DOR 1940 with the LERG CD and storing the results in a temporary routing database (shown) to create a discrepancy report.
  • This process can be used to yield a subset of the NPA/NXXs which have changed, which can then be audited and used to update the production DOR 1940 if found to be necessary. Once an updated version of the database is prepared, the database update can be sent to data distributor 1930 for distribution to all the relevant network elements.
  • FIG. 19F depicts an even more detailed example embodiment block diagram 1958 of BEA M3 data distributor of provisioning element 116.
  • Diagram 1958 shows the flow of a provisioning request from OSS 1802 or APDE 1804 through BEA M3 CORBA interface 1936 through queues to data distributor 1930 for distribution/replication through queue servers 1995a,1995b,1995c, and queues 1996a, 1996b, 1996c for dispatch to geographically diverse RCDBs 212a, 206 (RSs and CSs at remote soft switch sites) through dispatch servers 1997a, 1997b, 1997c and DBProxyServers 1998a. 1998b, 1998c, 1998d, 1998e and 1998f.
  • Priority queuing is enabled by BEA TUXEDO.
  • Tuxedo creates a plurality of queues in order to protect database integrity, e.g., a high, medium and low priority queue.
  • An example of the use of queues might be to place a higher priority on customer updates that to LERG updates, which are less time sensitive.
  • Requests can be categorized in queues based on dates such as, for example, the effective date of the request, the effective deactivation date. Once categorized by date, the updates can be stored with a timestamp placed on them, and can then be placed in a TUXEDO queue.
  • TUXEDO permits the use of down word transaction in its multi-level queuing architecture. This permits pulling back transactions, also known as "rolling back" a replication/update, so updates will occur to all of or none of the databases. In some instances one network element can be removed from the network, but this is done rarely. For an example, in the event of RCDB crashing, the NOC can remove the crashing RCDB from the network configuration and thus it might not be capable of being updated.. However, for normal situations of the network, updates are either performed on all elements or no updates are performed.
  • FIG. 19G depicts a block diagram illustrating a high level conceptual diagram of the CORBA interface 1960.
  • CORBA IDL Interface 1936 includes routing provisioning 1966, common configuration provisioning (configuration server provisioning) 1803, provisioning factory 1902, routing factory 1968, common configuration factory 1970, routing services 1908, 1910, common configuration services 1960 and SQL translator 1972.
  • SQL translator 1972 takes the application API calls and translates them into structured query language queries for queuing for eventual invocation against database of record 1940.
  • FIG. 19H depicts a block diagram 1962 illustrating additional components of the high level conceptual diagram of the CORBA interface 1960.
  • CORBA IDL Interface 1936 includes routing administration 1904, routing validation z1974, routing administration factory 1980, composite updates 1976, batch updates 1982, and projects 1978.
  • SQL translator 1972 can take the application API calls and translate them into structured query language queries for queuing for eventual invocation against project database 1984.
  • FIG. 19I depicts a block diagram illustrating a data distributor sending data to configuration server sequencing diagram 1964 including message flows 1986-1994.
  • Data distributor 222 receives service requests from upstream OSS systems 1922, 1924, 1926 and 1928.
  • OSS service requests appear in the form of provisioning updates and administrative reference updates.
  • Provisioning updates include high-level attributes required to provision a customer's telecommunications service.
  • Example high-level attributes required for provisioning include, for example, customer automatic number identification (ANI), and trunk profiles: class of service restrictions (COSR) and project account codes (PAC) profiles: AG and TG assignments: and toll-free number to SCP translation assignments.
  • ANI customer automatic number identification
  • COSR class of service restrictions
  • PAC project account codes
  • Administrative reference updates include high-level attributes required to support call processing.
  • Example high-level attributes required to perform administrative updates include, for example, 3/6/10 digit translation tables, international translation tables and blocked country codes.
  • Alternate provisioning data entry (APDE) 1804 replicates OSS functionality supported at the interface with data distributor 222.
  • APDE 1804 can provide an alternative mechanism to provide provisioning and reference data to data distributor 222 in the event that an OSS 1922-1928 is unavailable.
  • FIG. 19D illustrates data distributor 222 passing provisioning information from upstream OSSs 1922-1928 to downstream SCPs 214.
  • a plurality of tables are distributed from data distributor 222 to each SCP 214.
  • Exemplary data tables distributed include a PAC table, an ANI table, blocking list tables, numbering plan area (NPA)/NXX tables, state code tables, and LATA tables. Each of these tables is maintained at the customer level to ensure customer security.
  • FIG.19D illustrates block diagram 1946 depicting provisioning interfaces into SCPs.
  • SCP 214 can receive customer and routing provisioning from data distributor 222.
  • Data distributor 222 distributes customer database tables to SCP 214.
  • Data distributor 222 also distributes route plan updates of configurations to SCP 214.
  • Customer tables are updated through a database replication server.
  • An exemplary database replication server is an ORACLE database replication server, available from ORACLE of Redwood Shores, CA.
  • ORACLE replication server performs replication functions including data replication from data distributor to SCP 1952 and route plan distribution from data distributor to SCP 1954. These functions are illustrated in FIG. 19D originating from ORACLE databases 1940 and 1942 of data distributor 222 and replicating to an ORACLE database in SCP 214.
  • ORACLE databases 1940 and 1942 in data distributor 222 are updated via toll-free routing provisioning 1950 from SCP 1902.
  • ORACLE databases 1940 and 1942 of data distributor 222 can also be updated via order entry application 1802 including customer tables 1948 of OSS systems 1922-1928. Routing plans are updated via an SCP vendor's proprietary interfaces.
  • toll-free routing provisioning 1950 may be updated via a computer 1902 which interfaces to data distributor 222.
  • data distributor 222 passes provisioning and configuration information from upstream OSS systems 1922-1928 (primarily the provisioning system) to configuration servers 206a, 312a and 314a.
  • a plurality of tables are distributed from data distributor 222 to each configuration server.
  • Exemplary tables distributed include, for example, toll-free numbers to SCP-type tables, SCP-type to SCP tables, carrier identification code (CIC) profile tables, ANI profile summary tables, ANI profile tables, account code profile tables, NPA/NXX tables, customer profile tables, customer location profile tables, equipment service profile tables, trunk group service profile summary tables, trunk group service tables, high risk country tables, and selected international destinations tables.
  • CIC carrier identification code
  • Datadistributor222 passes administrative and reference information from upstream OSS systems 1922-1928 to route server 212.
  • a plurality of tables are distributed from data distributor 222 to route servers 212a, 212b, 314a, 314b, 316a and 316b.
  • Exemplary tables distributed include country code routing tables, NPA routing tables, NPA/NXX routing tables, ten-digit routing tables, route group tables, circuit group tables, and circuit group status tables.
  • Data distributor 222 passes administrative configuration information to TGs 232 and234.
  • Data distributor 222 passes administration configuration information to AGs 238 and 240.
  • Data distributor passes administrative configuration information to SS7 gateways 208 and 210.
  • the administrative configuration information sent can be used in the routing of SS7 signaling messages throughout signaling network 114.
  • Data distributor 222 uses a separate physical interface for all SNMP messages and additional functions that can be defined. Additional functions that can be defined include, for example, provisioning, and passing special alarm and performance parameters to data distributor 222 from the network operation center (NOC).
  • NOC network operation center
  • FIG. 18 depicts the provisioning component and network event component architecture 1800.
  • FIG. 18 includes a spool-shaped component (comprising provisioning component 117 and network event component 116), and three soft switch sites, i.e. western soft switch site 104, central soft switch site 106 and eastern soft switch site 302.
  • the spindle portion of the spool-shaped component includes western soft switch site 104.
  • Western soft switch site 104 includes configuration servers 206a and 206b, route servers 212a and 212b, soft switches 204a. 204b and 204c, and network event collection points, i.e., RNECPs 224a and 224b.
  • FIG. 18 also includes central soft switch site 106 including configuration servers 312a and 312b, route servers 314a and 314b, soft switches 304a, 304b and 304c, and RNECPs 902 and 904.
  • FIG. 18 also includes eastern soft switch site 302 including configuration servers 316a and 316b, route servers 318a and 318b, soft switches 306a, 306b and 306c and RNECPs 906 and 908.
  • network call events are collected at regional network event collection points via RNECPs 902, 904, 224a, 224b, 906 and 908, at the regional soft switch sites 104, 106 and 302, which are like FIFO buffers.
  • a call record can be created by the ingress soft switch.
  • the ingress soft switch can generate a unique identifier (UID) for the call based, for example, on the time of origination of the call.
  • Ingress related call event blocks can be generated throughout the call and are forwarded on to the RNECPs for inclusion in a call event record identified by the UID.
  • the call event records can be sent from the RNECPs to master network event data base NEDB 226a and 226b for storage in database disks 926a, 926b and 926c for further processing using application programs such as, for example, fraud DB client 1806, browser 1808, statistics DB client 1810 and mediation DB client 1812.
  • application programs such as, for example, fraud DB client 1806, browser 1808, statistics DB client 1810 and mediation DB client 1812.
  • a version of the call record including all call event blocks as of that time can be forwarded from the RNECPs to the NEDB on a periodic basis, to permit real-time, mid-call call event statistics to be analyzed.
  • the call records can be indexed by the UID associated with the call.
  • a copy of a call event record for a call remains in the RNECP until completion of the phone call.
  • the ingress soft switch and egress soft switch can communicate using inter soft switch communication, identifying the call by means of the UID.
  • a load balancing scheme can be used to balance storage and capacity requirements of the RNECPs. For example, in one embodiment, calls can be assigned, based on origination time, i.e., a UID can be assigned to a specific RNECP(based. e.g., on time of origination of the call) for buffered storage.
  • the egress soft switch can similarly generate and forward call event blocks to the same or another RNECP for inclusion in the call event record.
  • all the call event blocks for the call record for a given call are sent to one RNECP which maintains a copy throughout the call(i.e. even if interim copies are transmitted for storage).
  • the call event record is removed from the RNECP upon completion of the call to free up space for additional calls.
  • the bottom elliptical portion of spool-shaped component illustrates an embodiment of network event component 116 including master NEDBs 226a and 226b having database disks 926a, 926b and 926c.
  • MNEDBs 226a and 226b can be in communication with a plurality of applications which process network call event blocks.
  • a fraud DB client 1806, a browser 1808, a statistics DB client 1810, and a mediation DB client 1812 can process call event blocks (EBs).
  • EBs call event blocks
  • MNEDBs 226a and 226b can be in set up in a primary and secondary mode.
  • MNEDB Master Network Event Database
  • the master network event database (MNEDB) 226 is a centralized server which acts as a repository for storing call event records. MNEDB 226 collects data from each of RNECPs 224 which transmit information real-time to MNEDB 226. MNEDB 226 can also be implemented in a primary and secondary server strategy, wherein RNECPs 224 are connected to a primary and a secondary MNEDB 226 for high availability redundancy. MNEDB 226 can store call event blocks (EBs) received from RNECPs 224 organized based on a unique call/event identifier as the primary key and a directional flag element as the secondary key. MNEDB 226 can serve as the "database of record" for downstream systems to be the database of record.
  • EBs call event blocks
  • Downstream systems include, for example, an accounting/billing system, a network management system, a cost analysis system, a call performance statistics system, a carrier access billing system (CABS), fraud analysis system, margin analysis system, and others.
  • MNEDB 226, in a preferred embodiment, has enough disk space to store up to 60 days of call event records locally.
  • MNEDBs 226 can create and feed real-time call event data to downstream systems.
  • Real-time call event data provides significant advantages over call event data available in conventional circuit-switched networks. Conentional circuit-switched networks can only provide call records for completed calls to downstream systems.
  • the advantages of real-time call event data include, for example, fraud identification and prevention. and enablement of real-time customized customer reporting and billing (e.g., billing based on packets sent).
  • MNEDBs 226 collect recorded call event blocks (EBs) from RNECPs 224. MNEDB 226 correlates the EBs and forwards the data to various downstream systems.
  • EBs call event blocks
  • FIG. 20 illustrates master data center architecture 2000.
  • FIG. 20 includes master data center 2004 having MNEDBs 226a and 226b.
  • MNEDBs 226a and 226b have multiple redundant high availability disks 926a and 926b which can be arranged in a primary and secondary fashion for high availability redundancy.
  • MNEDBs 226a and 226b intercommunicate as shown via communication line 2006.
  • MNEDBs 226a and 226b are in communication via multiple redundant connections with a plurality of downstream application systems.
  • Downstream application systems include, for example, browser system 1808, fraud DB client system 1806, carrier access billing system (CABS) DB client 2002, statistics DB client 1810 and mediation DB client 1812.
  • CABS carrier access billing system
  • MNEDBs 226a and 226b provide recorded call event record data to fraud database client 1806 in real-time.
  • Real-time call event data allows fraud DB client 1806 to detect fraudulent activities at the time of their occurrence, rather than after the fact.
  • Traditional circuit-switched networks can only identify fraud after completion of a call, since event records are "cut" at that time.
  • Real-time fraud detection permits operations personnel to take immediate action against fraudulent perpetrators.
  • MNEDBs 226a and 226b provide recorded call event data to CABS DB client 2002.
  • CABS DB client 2002 uses the recorded call event data to bill other LECs and IXCs for their usage of telecommunications network 200, using reciprocal billing.
  • MNEDBs 226a and 226b provide recorded call data to statistics DB client 1810.
  • Statistics DB client 1810 uses the recorded call event data to assist in traffic engineering and capacity forecasting.
  • MNEDBs 226a and 226b can provide recorded call event data to mediation DB client 1812, in one embodiment.
  • Mediation DB client 212 normalizes the recorded call data it receives from MNEDBs 226a and 226b and provides a data feed to a billing system at approximately real-time.
  • MNEDBs 226a and 226b use a separate physical interface for all SNMP messages and additional functions that can be defined to communicate with network management component 118. Additional functions can include, for example, provisioning, updating and passing special alarm and performance parameters to MNEDBs 326a and 326b from the network operation center (NOC) of network management component 118.
  • NOC network operation center
  • Event Blocks that can be recorded during call processing are detailed in this section.
  • EB 0001 defines a Domestic Toll (TG origination), which can be the logical data set generated for all Domestic Long Distance calls, originating via a Trunking Gateway, i.e., from facilities of the PSTN. Typically, these calls can be PIC-calls, originating over featuring group-D (FGD) facilities.
  • TG origination can be the logical data set generated for all Domestic Long Distance calls, originating via a Trunking Gateway, i.e., from facilities of the PSTN. Typically, these calls can be PIC-calls, originating over featuring group-D (FGD) facilities.
  • Table 20 EB 0001 - Domestic Toll (TG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0002 defines Domestic Toll (TG termination), which can be the logical data set generated for all Domestic Long Distance calls terminating via a Trunking Gateway to the PSTN.
  • Table 21 EB 0002 - Domestic Toll (TG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Calling Party Category 6 3 Originating Number 7 10 Overseas Indicator 8 1 Terminating NPA/CC 9 5 Terminating Number (NANP) 10 10 Call Type Identification 79 3 Carrier Identification Code 12 4 Jurisdiction Information 30 6
  • EB 0003 defines Domestic Toll (AG origination), which can be the logical data set generated for all Domestic Long Distance calls, originating via an Access Gateway, i.e., entering via a DAL or ISDN PRI line.
  • AG origination can be the logical data set generated for all Domestic Long Distance calls, originating via an Access Gateway, i.e., entering via a DAL or ISDN PRI line.
  • Table 22 EB 0003 - Domestic Toll (AG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0004 defines Domestic Toll (AG termination), which can be the logical data set generated for all Domestic Long Distance calls, terminating via an Access Gateway to a DAL or PRI Table 23 EB 0004 - Domestic Toll (AG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Calling Party Category 6 3 Originating Number 7 10 Overseas Indicator 8 1 Terminating NPA/CC 9 5 Terminating Number (NANP) 10 10 Call Type Identification 79 3 Carrier Identification Code 12 4
  • EB 0005 defines Local (TG origination), which can be the logical data set generated for all local calls, originating via a Trunking Gateway from a facility on the PSTN.
  • TG origination can be the logical data set generated for all local calls, originating via a Trunking Gateway from a facility on the PSTN.
  • Table 24 EB 0005 - Local (TG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0006 defines Local (TG termination), which can be the logical data set generated for all local calls terminating via a Trunking Gateway to facilities of the PSTN.
  • Table 25 EB 0006 - Local (TG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Calling Party Category 6 3 Originating Number 7 10 Terminating NPA/CC 9 5 Terminating Number (NANP) 10 10 Call Type Identification 79 3
  • EB 0007 defines Local (AG origination), which can be the logical data set generated for all local calls, originating via an Access Gateway.
  • EB 0007 - Local (AG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0008 defines Local (AG termination), which can be the logical data set generated for all local calls, terminating via an Access Gateway.
  • Table 27 EB 0008 - Local (AG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Calling Party Category 6 2 Originating Number 7 10 Terminating NPA/CC 9 5 Terminating Number (NANP) 10 10 Call Type Identification 79 3
  • EB 0009 defines 8XX/Toll-Free (TG origination), which can be the logical data set generated for Toll-Free (8XX) calls, originating via a Trunking Gateway from facilities of the PSTN.
  • Table 28 EB 0009 - 8XX / Tool-Free (TG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0010 defines 8XX/Toll-Free (TG termination), which can be the logical data set generated for Toll-Free (8XX)s calls, terminating via a Trunking Gateway to the facilities of the PSTN.
  • Table 29 EB 0010 - 8XX / Toll-Free (TG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Calling Party Category 6 3 Originating Number 7 10 Dialed NPA 25 3 Dialed Number 26 7 Destination NPA/CC 27 5 Destination Number 28 10 Call Type Identification 79 3
  • EB 0011 defines 8XX/Toll-Free (AG origination), which can be the logical data set generated for Toll-Free (8XX) calls, originating via an Access Gateway.
  • EB 0011 - 8XX / Toll-Free (AG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0012 defines 8XX/Toll-Free (AG termination), which can be the logical data set generated for Toll-Free (8XX)s calls, terminating via an Access Gateway.
  • EB 0012 - 8XX / To // -Free (AG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Calling Party Category 6 3 Originating Number 7 10 Dialed NPA 25 3 Dialed Number 26 7 Destination Number 28 10 Destination NPA/CC 27 5 Call Type Identification 79 3
  • EB 0013 defines Domestic Operator Services (TG origination), which can be the logical data set generated for all Domestic Operator Assisted calls, originating via a TG.
  • the actual billing information (which can include the services utilized on the operator services platform (OSP): 3rd party billing, collect, etc.) can be derived from the OSP.
  • OSP operator services platform
  • Table 33 below provides a definition of event block (EB) 0014.
  • EB 0014 defines Domestic Operator Services (AG origination), which can be the logical data set generated for all Domestic Operator Assisted calls, originating via an AG.
  • the actual billing information (which can include the services utilized on the OSP) can be derived from the OSP.
  • EB 0014 - Domestic Operator Services (AG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0015 defines Domestic Operator Services (OSP termination), which can be the logical data set generated for all Domestic Operator Assisted calls, terminating to the OSP.
  • the actual billing information(which can include the services utilized on the OSP) can be derived from the OSP.
  • Table 34 EB 0015 - Domestic Operator Services (OSP termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0016 defines International Operator Services (TG origination), which can be the logical data set generated for all International Operator Assisted calls, originated via a TG.
  • the actual billing information(which can include the services utilized on the OSP) can be derived from the OSP.
  • Table 35 EB 0016 - International Operator Services (TG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0017 defines International Operator Services (AG origination), which can be the logical data set generated for all International Operator Assisted calls, originated via an AG. The actual billing information(which will include the services utilized on the OSP) can be derived from the OSP.
  • AG origination International Operator Services
  • Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0018 defines International Operator Services (OSP termination), which can be the logical data set generated for all International Operator Assisted calls, terminating to the OSP.
  • the actual billing information(which will include the services utilized on the OSP) can be derived from the OSP.
  • Table 37 EB 0018 - International Operator Services (OSP termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • Table 38 below provides a definition of event block (EB) 0019.
  • EB 0019 defines Directory Assistance/555-1212 (TG origination), which can be the logical data set generated for 555-1212 calls, originating via a TG from the PSTN.
  • Table 38 EB 0019 - Directory Assistance / 555-1212 (TG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0020 defines Directory Assistance/555-1212 (AG origination), which can be the logical data set generated for 555-1212 calls, originating via an AG on a DAL.
  • EB 0020 - Directory Assistance / 555-1212 (AG origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0021 defines Directory Assistance/555-1212 (Directory Assistance Services Platform (DASP) termination), which can be the logical data set generated for 555-1212 calls, terminating to the DASP.
  • DASP Directory Assistance Services Platform
  • Table 40 EB 0021 - Directory Assistance / 555-1212 (DASP termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • Table 41 below provides a definition of event block (EB) 0022.
  • EB 0022 defines OSP/DASP Extended Calls (Domestic), which can be the logical data set generated for all Domestic Operator and Directory Assisted calls that are extended back to telecommunications network 200 for termination.
  • Table 41 EB 0022 - OSP / DASP Extended Calls (Domestic) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • Table 42 below provides a definition of event block (EB) 0023.
  • EB 0023 defines OSP/ DASP Extended Calls (International), which can be the logical data set generated for all International Operator and Directory Assisted calls that are extended back to the telecommunications network 200 for termination.
  • Table 42 EB 0023 - OSP / DASP Extended Calls (International) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0024 defines International Toll (TG Origination), which can be the logical data set generated for all International Long Distance calls, originating via a Trunking Gateway from facilities of the PSTN. Typically, these calls can be PIC-calls, originating over FGD facilities.
  • TG Origination International Toll
  • EB 0025 defines International Toll (AG Origination), which can be the logical data set generated for all International Long Distance calls, originating via an Access Gateway.
  • EB 0025 - International Toll (AG Origination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0026 defines International Toll (TG Termination), which can be the logical data set generated for all International Long Distance calls terminating via a Trunking Gateway to facilities of the PSTN.
  • TG Termination International Toll
  • Table 45 EB 0026 - International Toll (TG Termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0027 defines International Toll (AG Termination), which can be the logical data set generated for all International Long Distance calls, terminating via an Access Gateway to a DPL or PRI.
  • AG Termination International Toll
  • Table 46 EB 0027 - International Toll (AG Termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0040 defines IP Origination, which can be the logical data set generated for ALL IP originations.
  • Table 47 EB 0040 - IP Origination Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Originating Number 7 10 Customer Identification 80 12 Customer Location Identification 81 12 Terminating NPA/CC 9 5 Terminating Number 10 10 Call Type Identification 79 3 Originating IP Address 63 12 Ingr. Security Gateway IP Address 65 12 Ingress Firewall IP Address 67 12
  • EB 0041 defines IP Termination, which can be the logical data set generated for ALL IP terminations.
  • Table 48 EB 0041 - IP Termination Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Connect Date 3 8 Connect Time 4 9 Originating Number 7 10 Terminating NPA/CC 9 5 Terminating Number (NANP) 10 10 Call Type Identification 79 3 Terminating IP Address 64 12 Egr. Security Gateway IP Address 66 12 Egress Firewall IP Address 68 12
  • EB 0050 defines a Final Event Block, which can be used as the FINAL Event Block for ALL calls/events. It signifies the closure of a call/event.
  • Table 49 EB 0050 - Final Event Block Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 End Date 40 8 End Time 39 9 Elapsed Time 11 10 Audio Packets Sent 59 9 Audio Packets Received 60 9 Audio Packets Lost 61 9 Audio Bytes Transferred 62 9
  • Table 50 below provides a definition of event block (EB) 0051.
  • EB 0051 defines Answer Indication, which can be used as to indicate whether or not a call/session was answered or unanswered. If the call was unanswered, the Answer Indicator element will indicate that the call was not answered and the Answer Time element will contain the time that the originating party went on-hook.
  • Table 50 EB 0051 - Answer Indication Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Answer Indicator 5 1 Answer Date 41 8 Answer Time 42 9
  • Table 51 below provides a definition of event block (EB) 0052.
  • EB 0052 defines Ingress Trunking Disconnect Information which can contain Ingress Trunking Disconnect information. The release date and time of the ingress circuit used in the call can be recorded. This EB can be extremely important to downstream systems (i.e. cost analysis/CABS analysis) that may need to audit the bills coming from LECs/CLECs/Carriers.
  • Table 51 EB 0052 - Ingress Trunking Disconnect Information Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Ingress Carrier Disconnect Date 44 8 Ingress Carrier Disconnect Time 43 9
  • EB 0053 defines Egress Trunking Disconnect Information, which can contain Egress Trunking Disconnect information. The release date and time of the egress circuit used in the call can be recorded. This EB can be extremely important to downstream systems (i.e. cost analysis/CABS analysis) that can need to audit the bills coming from LECs/CLECs/Carriers.
  • Table 52 EB 0053 - Egress Trunking Disconnect Information Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Egress Carrier Disconnect Date 46 8 Egress Carrier Disconnect Time 45 9
  • Table 53 below provides a definition of event block (EB) 0054.
  • EB 0054 defines Basic 8XX/Toll-Free SCP Transaction Information, which can be used for all basic toll-free (8XX) SCP transactions.
  • Table 53 EB 0054 - Basic 8XX / Toll-Free SCP Transaction Information Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0055 defines Calling Party (Ported) Information, which can be used to record information in regards to a Calling Party Number that has been ported.
  • Table 54 EB 0055 - Calling Party (Ported) Information Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Location Routing Number 48 11 LRN Supporting Information 49 1
  • Table 55 below provides a definition of event block (EB) 0056.
  • EB 0056 defines Called Party (Ported) Information, which can be used to record information in regards to a Called Party Number that has been ported.
  • Table 55 EB 0056 - Called Party (Ported) Information Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Location Routing Number 48 11 LRN Supporting Information 49 1
  • Table 56 below provides a definition of event block (EB) 0057.
  • EB 0057 defines Egress Routing Information (TG termination), which can be used to record the egress routing information (i.e., terminating via the PSTN).
  • Table 56 EB 0057 - Egress Routing Information (TG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID.
  • EB 0058 defines Routing Congestion Information, which can be used to record routes/trunks that were unavailable (e.g., due to congestion, failure, etc.) during the route selection process in soft switch 204.
  • EB 0057 for TG termination
  • EB 0060 for AG termination
  • This information can be extremely valuable to, for example, traffic engineering, network management, cost analysis.
  • Table 58 below provides a definition of event block (EB) 0059.
  • EB 0059 defines Account Code Information, which can be used for all calls requiring account codes.
  • Table 58 EB 0059 - Account Code Information Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Account Code Type 71 1 Account Code 38 14 Account Code Validation Flag 56 1
  • EB 0060 defines Egress Routing Information (for AG termination), which can be used to record the egress routing information (i.e., terminating via an AG).
  • Table 59 EB 0060 - Egress Routing Information (AG termination) Element Element Number Number of Characters Event Block Code 0 6 Unique Call/Event Identifier 1 26 Call Event Block Sequence Number 82 2 Soft-Switch ID 2 6 Soft Switch Version ID. 50 4 Directional Flag 77 1 Egress Routing Selection 54 2 Egress Access Gateway 37 6 Egress Carrier Connect Date 73 8 Egress Carrier Connect Time 19 9 Egress Trunk Group Number 21 4 Egress Circuit Identification Code 22 4 Trunk Group Type 78 3
  • EB 0061 defines Long Duration Call Information, which can be used to record a timestamp of long duration calls.
  • Soft switch 204 can generate this block when a call has been up for a duration that spans over two midnights. Subsequent LDCI EBs can be generated after each additional traverse of a single midnight. As an example, if a call has been up from 11:52 pm on Monday, through 4:17 pm on Thursday (of the same week), then TWO EB 0061s can be generated for the call. One can be generated at midnight on Tuesday, the other can be generated at midnight on Wednesday.
  • Event Blocks are logical groupings of elements. Each element can contain information that is collected during call/event processing, whether from, for example, signaling messages, external databases (SCPs and intelligent peripherals (IPs)), Access GTGs, customer attributes, or derived by a soft switch. All of the elements contain information that is used by various downstream systems. Downstream systems include, for example, billing/mediation, traffic engineering, carrier access billing, statistical engines, cost analysis engines, and marketing tools.
  • Element 0 defines an Event Block Code element, which contains a code that can be mapped/correlated to a type of call/event.
  • the EB code can be used for parsing and data definition for downstream systems.
  • Element 1 defines an Unique Call/Event Identifier (UCEI), which can be used to correlate all events (EBs) for a particular call/session. The correlation can be done in the MNEDB.
  • UAEI Unique Call/Event Identifier
  • Element 2 defines a Soft-Switch ID element, which contains the soft switch identification number. This can indicate which soft switch recorded the call event data.
  • Element 3 defines a Connect Date element, which contains the date when the call was originated.
  • Element 4 defines a Connect Time element, which contains the time when the soft switch received an IAM.
  • Element 5 defines an Answer Indicator element, which states whether or not a call/session was answered/unanswered.
  • Element 6 defines a Calling Party Category element, which contains whether a call was originated from, for example, a Hotel, a Prison, a Cell Phone, a pay phone, a PVIPS, and an inward wide area telephone service (INWATS), based on the Calling Party Category received in the Initial Address Message (IAM), derived from a soft switch, or received from a database external from the soft switch.
  • IAM Initial Address Message
  • Element 7 defines an Originating Number element, which contains the NPA NXX-XXX (DN) that originated the call.
  • Element 8 defines an Overseas Indicator element, which provides the digit length of an overseas call, as well as whether or not an NPA was dialed or implied/derived from the soft switch. This element is crucial to downstream systems (i.e., billing/mediation) which need to differentiate between NPAs and CCs.
  • Element 9 defines a Terminating Numbering Plan Area/Country Code (NPA/CC) element, which contains either the NPA of the dialed number for domestic calls, or up to five characters of the overseas number dialed.
  • NPA/CC Terminating Numbering Plan Area/Country Code
  • Element 10 defines a Terminating Number North American Numbering Plan (NANP) element, which contains the NXX-LINE of the dialed number for domestic calls. The terminating number element should be populated for ALL calls that require a terminating number for billing.
  • NANP Terminating Number North American Numbering Plan
  • Element 11 defines an Elapsed Time element, which contains the elapsed time (duration) of a completed call/session.
  • the time can be GMT.
  • Element 12 defines a Carrier Identification Code element, which contains the toll carrier's identification code. This can be an extremely useful element for downstream systems (i.e. billing), that need to parse records for wholesale customers!
  • Element 13 defines an Ingress Carrier Connect Time element, which contains the time that the ingress trunk/circuit was seized for a call, that is, when an ACM was sent towards the PSTN. This element can be important to downstream systems (i.e. cost analysis/CABS analysis) that may need to audit the bills coming from LECs/CLECs/Carriers.
  • Element 14 defines an Ingress Carrier Elapsed Time element, which contains the elapsed time(duration) that the ingress trunk/circuit was in use(from seizure to release) for both answered and unanswered calls/sessions. This element can be important to downstream systems (i.e. cost analysis/CABS analysis) that may need to audit the bills coming from LECs/CLECs/Carriers.
  • Element 15 defines an Ingress Trunk Group Number element, which contains the Trunk Number on the originating/ingress side of a call.
  • the information can be derived from either TG or AG, or from a correlation table, using Element 16 - Ingress Circuit Identification Code, Element 17 - Ingress Originating Point Code, and Element 18 - Ingress Destination Point Code, to correlate to a specific trunk group.
  • This element can be important to downstream systems (i.e. cost analysis/CABS analysis) that may need to audit the bills coming from LECs/CLECs/Carriers. This can also assist traffic engineers in trunk sizing.
  • Element 16 defines an Ingress Circuit Identification Code element, which contains the circuit number/id of the circuit used on the originating/ingress side of a call. The information can be derived from either TG or AG, or from the Circuit Identification Code (CIC) field in the IAM.
  • CIC Circuit Identification Code
  • Element 17 defines an Ingress Originating Point Code (IOPC) element, which contains the ingress OPC.
  • IOPC Ingress Originating Point Code
  • Element 18 defines an Ingress Destination Point (IDC) Code.
  • IDC Ingress Destination Point
  • Element 19 defines an Egress Carrier Connect Time element, which contains the time that the egress trunk/circuit was seized for a call. The time can be derived from the Access or Trunking Gateways, or from the Initial Address Message. This element can be important to downstream systems (i.e. CABS) that need this information to BILL other LECs/CLECs/Carriers.
  • Element 20 defines an Egress Carrier Elapsed Time element, which contains the elapsed time (duration) that the egress trunk/circuit was in use (from seizure to release) for both answered and unanswered calls/sessions. This element can be important to downstream systems (i.e. CABS) that need this information to BILL other LECs/CLECs/Carriers.
  • CABS downstream systems
  • Element 21 defines an Egress Trunk Group Number element, which contains the Trunk Number on the terminating/egress side of a call.
  • the information can be derived from either TG or AG, or from a correlation table, using Element 22 - Egress Circuit Identification Code, Element 23 - Egress Originating Point Code, and Element 24 - Egress Destination Point Code, to correlate to a specific trunk group.
  • This element can be important to downstream systems (i.e. cost analysis/CABS analysis) that may need to audit the bills coming from LECs/CLECs/Carriers.
  • Element 22 defines an Egress Circuit Identification Code element, which contains the circuit number/id of the circuit used on the terminating/egress side of a call. The information can be derived from either TG or AG, or from the Circuit Identification Code (CIC) field in the IAM message.
  • CIC Circuit Identification Code
  • Element 23 defines an Egress Originating Point (EOP) Code.
  • Element 24 defines an Egress Destination Point (EDP) Code.
  • Element 25 defines a Dialed NPA element, which contains the 8XX code for a toll-free call.
  • Element 26 defines a Dialed Number element, which contains the NXX-LINE of the dialed number for domestic toll-free calls.
  • the terminating number element has seven significant characters and a sign (delimiter) character.
  • Element 27 defines a Destination NPA/CC element, which contains the Numbering Plan Area (NPA) for domestic calls and the Country Code (CC) for international calls. This information is SCP derived for 8XX calls. The element is right justified and padded (with 0s) if necessary.
  • NPA Numbering Plan Area
  • CC Country Code
  • Element 28 defines a Destination Number element, which contains the NXX-LINE of the destination number for domestic toll-free calls. This number is the routing number returned from a SCP 800 query.
  • the terminating number element has seven significant characters and a sign (delimiter) character. The terminating number element should be populated for ALL calls that require a terminating number for billing.
  • Element 29 defines an Alternate Billing Number field element, which contains the billing number obtained from the optional billing number data received from SCP.
  • Element 30 defines a Jurisdiction Information element, which contains the NPA-NXX of the originating Switch. This information can be contained in the Initial Address Message.
  • Element 31 defines a Transaction Identification element, which contains a unique identification number for each external request to a SCP, an Intelligent Peripheral (IP), or some other database.
  • IP Intelligent Peripheral
  • Element 32 defines a Transaction Start Time element, which contains the time that the Soft Switch sent an external request to an SCP, an Intelligent Peripheral (IP), or some other database.
  • IP Intelligent Peripheral
  • Element 33 defines a Transaction End Time element, which contains the time that the Soft Switch received a response from an external request to a SCP, an Intelligent Peripheral (IP), or some other database.
  • IP Intelligent Peripheral
  • Elemem 34 defines a Database Identification element, which contains the SCP, Intelligent Peripheral (IP), or some other database's identification number, that a transaction was performed.
  • IP Intelligent Peripheral
  • Element 36 defines an Ingress Access Gateway element, which contains the AG identification number.
  • Element 37 defines an Egress Access Gateway element, which contains the AG identification number.
  • Element 38 defines an Account Code element, which contains the length of the account code, as well as the actual account code digits that were entered.
  • Element 39 defines an End Time element, which contains the time when the call completed. The time should be recorded after both parties, originating and terminating, go on-hook.
  • Element 40 defines an End Date element, which contains the date when the call was completed.
  • Element 41 defines an Answer Date element, which contains the date when the call was answered.
  • Element 42 defines an Answer Time element, which contains the time when the terminating station went off-hook. The timer could start when the Soft Switch receives an answer message. If the call was unanswered, the Answer Time will contain the time that the originating party went on-hook.
  • Element 43 defines an Ingress Carrier Disconnect Time element, which contains the time that the ingress trunk/circuit was released for a call. The time will either be derived from the Access or Trunking Gateways, or from the Release Message. This element can be important to downstream systems (i.e. cost analysis/CABS analysis) that may need to audit the bills coming from LECs/CLECs/Carriers.
  • Element 44 defines an Ingress Carrier Disconnect Date Disconnect Date element, which contains the date when the ingress trunk/circuit was released for a call.
  • Element 45 defines an Egress Carrier Disconnect Time element, which contains the time that the egress trunk/circuit was released for a call. The time will either be derived from the Access or Trunking Gateways, or from the Release Message. This element can be extremely important to downstream systems (i.e. CABS) that need this information to BILL other LECs/CLECs/Carriers.
  • Element 46 defines an Egress Carrier Disconnect Date element, which contains the date when the egress trunk/circuit was released for a call.
  • Element 47 defines an Announcement Identification element, which contains the announcement number (correlating to an announcement) that was invoked during call processing.
  • Element 48 defines a Location Routing Number (LRN) element, which contains the Location Routing Number. Depending on the EB being created (EB 0055 or EB 0056), this field contains the LRN for the Calling Party Number (if ported) or the LRN for the Called Party Number (if ported).
  • LRN Location Routing Number
  • Element 49 defines a LRN Supporting Information element, which contains the source/system where the LRN was derived.
  • Element 50 defines a Soft Switch Version element, which contains the current software version that is operating on the soft switch.
  • Element 51 defines a Carrier Selection Information element, which contains the toll carrier selection method. This allows downstream systems, such as end-user billing and fraud, to parse records based on carrier selection methods (e.g., pre-subscription. dial-around/casual-calling.)
  • Element 52 defines an Ingress Trunking Gateway element, which contains the TG identification number.
  • Element 53 defines an Egress Trunking Gateway element, which contains the TG identification number.
  • Element 54 defines an Egress Routing Selection.
  • Element 55 defines an Egress Route Congestion Code element, which contains the reason for congestion on a trunk.
  • Element 56 defines an Account Code Validation Flag element, which contains a flag that specifies whether or not the account code validation was successful.
  • Element 57 defines a Routing Attempt Time element, which contains the time that an unsuccessful routing attempt was made on a trunk. This information can be useful to downstream Network Management and Traffic Engineering systems.
  • Element 58 defines a Routing Attempt Date element, which contains the date that an unsuccessful routing attempt was made on a trunk. This information can be useful to downstream Network Management and Traffic Engineering systems.
  • Element 59 defines an Audio Packets Sent element, which contains the number of audio packets that were sent from an AG or TG during a session.
  • Element 60 defines an Audio Packets Received element, which contains the number of audio packets that were received by an AG or TG during a session.
  • Element 61 defines an Audio Packets Lost element, which contains the number of audio packets that were lost during a session.
  • Element 62 defines an Audio Bytes Transferred element, which contains the total number of audio packets that were transferred sent from an AG or TG during a session.
  • Element 63 defines an Originating IP Address element, which contains the Internet Protocol (IP) address of the originator.
  • IP Internet Protocol
  • Element 64 defines a Terminating IP Address element, which contains the Internet Protocol (IP) address of the termination.
  • IP Internet Protocol
  • Element 65 defines an Ingress Security Gateway IP Address element, which contains the Internet Protocol (IP) address of the security gateway on the ingress portion of a call/session.
  • IP Internet Protocol
  • Element 66 defines an Egress Security Gateway IP Address element, which contains the Internet Protocol (IP) address of the security gateway on the egress portion of a call/session.
  • IP Internet Protocol
  • Element 67 defines an Ingress Firewall IP Address element, which contains the Internet Protocol (IP) address of the security gateway on the ingress portion of a call/session.
  • IP Internet Protocol
  • Element 68 defines an Egress Firewall IP Address element, which contains the Internet Protocol (IP) address of the security gateway on the egress portion of a call/session.
  • IP Internet Protocol
  • Element 69 defines an Operator Trunk Group Number element, which contains the trunk group number for the trunk selected to the Operator Services Platform (OSP).
  • OSP Operator Services Platform
  • Element 70 defines an Operator Circuit Identification Code (CIC) element, which contains the circuit number/id of the circuit used for an Operator service call.
  • CIC Operator Circuit Identification Code
  • Element 71 defines an Account Code Type element, which contains a value associated with the type of account used in the call.
  • Element 72 defines an Ingress Carrier Connect Date element, which contains the date when the ingress trunk/circuit was seized.
  • Element 73 defines an Egress Carrier Connect Date element, which contains the date when the egress trunk/circuit was seized.
  • Element 74 defines a Terminating Number (International) element, which contains the overseas number that was dialed for domestic calls. The terminating number element should be populated for ALL calls that require a terminating number for billing. This field can be right-justified, padded with 0s.
  • Element 75 defines a DA Trunk Group Number element, which contains the trunk group number for the trunk selected to the directory assistance (DA) service provider.
  • DA directory assistance
  • Element 76 defines a DA Circuit Identification Code element, which contains the circuit number/id. of the circuit used for a DA service call.
  • Element 77 defines a Directional Flag element, which contains a flag that specifies whether a call event block is an ingress or an egress generated block.
  • Element 78 defines a Trunk Group Type element, which contains a type identification number, which maps to a type/use of a trunk.
  • the element can be useful to downstream systems, such as mediation/billing, fraud, etc. This element can also be used in call processing.
  • Element 79 defines a Call Type Identification element, which contains a call type identification number, which maps to a type of a call.
  • the element can be useful to downstream systems, such as, for example, mediation/billing, fraud. This element can also be used in call processing. This element can be derived during LSA analysis.
  • Element 80 defines a Customer Identification element, which contains a customer account number.
  • Element 81 defines a Customer Location Identification element, which contains a customer location identification number.
  • Element 82 defines a Call Event Block Sequence Number element, which contains a sequence number for each event block created by the soft switch for a particular call.
  • Element 83 defines a Long Duration Sequence Number element, which contains a sequence number for each long duration call (LDC) event block created by the soft switch for a particular call.
  • LDC long duration call
  • Element 84 defines a Long Duration Event Time element, which contains the time when the soft switch generated the LDC Event Block.
  • Element 85 defines a Long Duration Event Date element, which contains the date when the soft switch generated the LDC Event Block.
  • Telecommunications network 200 includes network management component 118 which can use a simple network management protocol (SNMP) to trap alarm conditions within and receive network alerts from hardware and software elements of the network.
  • FIG. 21A illustrates in detail SNMP network management architecture 2100. SNMP network management architecture 2100 is organized into a plurality of tiers and layers (not shown).
  • Tier 1 addresses hardware specific events that are generated on each respective hardware and software system.
  • hardware vendors provide tier 1 functionality in the form of a management information base (MIB).
  • MIB management information base
  • Tier 2 is designed to capture operating system specific events and is also available as a commercially sold product in the form of an MIB from a software vendor.
  • Tier 3 is related to events generated by customized software running on the platform.
  • tiers 1 and 2 are provided by a hardware vendor, for example, from Sun Microsystems of Palo Alto, CA.
  • Tier 1 and 2 MIBs are designed to provision, update, and pass special event and performance parameters to a network operations center (NOC), pictured as NOC 2114 in FIG. 21A .
  • NOC network operations center
  • Tier 3 can support alarm transmission from software applications and can be designed and implemented via a customized software solution from a third party vendor.
  • Software applications can call a standardized alarm transport application programming interface (API) to signal events and alarms within the software code.
  • the vendor supplied alarm API can redirect events to a local alarm manager application.
  • the local alarm manager can log events to a disk-based database.
  • the local alarm manager can also log events to a disk-based log file and can then forward the events from the database or log file to a specialized MIB component.
  • the specialized MIB component can then divert this information to a regional SNMP agent at each geographical location, i.e., at each soft switch site 104, 106 and 302, or gateway site 108a, 108b, 108C, 108D, 108E, 110a, 110b, 110c, 110D and 110E.
  • Regional SNMP agents can then route all incoming network management events or alarms to master SNMP managers 2102 and 2104 at the NOC 2114.
  • NEC Network operations center
  • FIG. 21A includes Network Operations Center (NOC) 2114 in SNMP network management architecture 2100.
  • Soft switch sites 104, 106 and 302 include a plurality of network components each having their own SNMP agents.
  • soft switch site 104 includes RNECP 224a and 224b having their own SNMP agents.
  • Soft switch site 104 also includes configuration servers 206a and 206b, soft switches 204a, 204b and 204c, route servers 212a and 212b, SS7 GWs 208 and 210, and ESs 332 and 334, each having their own SNMP agents.
  • Soft switch site 104 can also include one or more redundant SNMP servers 2110 and 2112 for collecting regional SNMP alerts.
  • SNMP servers 2110 and 2112 can maintain log files of network management events. SNMP servers 2110 and 2112 can then send events and alarms upstream to NOC 2114 of network management component 118.
  • NOC 2114 can include one or more centralized SNMP manager servers 2102 and 2104 for centrally managing telecommunications network 200.
  • Soft switch sites 106 and 302 can have similar SNMP agents in network components included in their sites.
  • Gateway sites 108a, 108b, 108c, 108d. 108e, 110a, 110b, 110c, 110d and 110e include multiple gateway site components which can each have their SNMP agents.
  • gateway site 108a can include TGs 232a and 232b which have SNMP agents 1002.
  • Gateway site 108a can also include AGs 238a and 238b having SNMP agents 1006.
  • Gateway sites 108a can also include ESs 1602 and 1604 and routers 1606 and 1608 having their own SNMP agents.
  • Gateway site 108a can also have one or more SNMP servers 2106 and 2108 for gathering SNMP alerts, events and alarms at gateway site 108a, from SNMP agents such as, for example, SNMP agents 1002 and 1006. SNMP servers 2106 and 2108 can then forward network management events and alarms to NOC 2114 for centralized network management processing.
  • SNMP servers 2106 and 2108 can then forward network management events and alarms to NOC 2114 for centralized network management processing.
  • Simple network management protocol (SNMP) events generated by network elements can enable NOC 2114 to determine the health of the voice network components and the rest of telecommunications network 200.
  • Tier 1 and tier 2 MIBs can be purchased as commercially off the shelf (COTS) components, or are provided with computer hardware and operating systems.
  • Events generated within the customized third tier can be prioritized according to multiple levels of severity. Prioritization can allow a programmer to determine the level of severity of each event generated and sent to NOC 2114.
  • Customized alarm managers resident in each computer system can serve as alarm logging components and transport mechanisms for transport to downstream SNMP agents.
  • Personnel working at NOC 2114 can log into a computer system to analyze special alarm conditions and to focus on the cause of the SNMP alarms.
  • a local log file can store all events processed by a local alarm manager application.
  • local alarm manager applications can reside in SNMP servers 2106 and 2108 at gateway site 108a, and at SNMP servers 2110 and 2112 of soft switch site 104.
  • the local log files can serve as a trace mechanism to identify key network and system event conditions generated on the computer systems.
  • FIG. 21B illustrates an example outage recovery scenario 2116.
  • Outage recovery scenario 2116 can be used in the event of, for example, a fiber cut, a period of unacceptable latency or a period of unacceptable packet loss failure in data network 112.
  • FIG. 21B includes a calling party 102 placing a call to called party 120.
  • Calling party 102 is connected to carrier facility 126.
  • Called party 120 is connected to carrier facility 130.
  • a call path from calling party 102 to called party 120 is illustrated between carrier facility 126 and carrier facility 130 over a normal call path route 2118 through DACS 242 and 244 and TGs 232 and 234 of gateway sites 108 and 110, respectively.
  • Normal call path route 2118 would go through, in succession, TG 232, one of ESs 1602 and 1604, one of routers 1606 and 1608, data network 112, one of routers 1614 and 1616, one of ESs 1610 and 1612, and TG 234, before exiting DACs 244 to connect to carrier facility 130.
  • outage recovery scenario 2116 routes the call over backup call path 2117 of FIG. 21B .
  • Backup call path 2117 takes a call which originated from carrier facility 126 through DACS 242 to TG 232, and connects the call back out through DACS 242 to an off-network carrier 2115 which connects the call traffic for termination at carrier facility 130.
  • SLA service level agreements
  • Outage recovery scenario 2116 would cover any failure or degradation in a network device which falls after TG 232 including IP media processes within TG 232, in normal call path route 2116, assuming that TG 232 can still be controlled so as to route the call out over DACS 242 over backup call path 2117 to off-network carrier 2115.
  • FIG. 21C depicts an example network outage recovery scenario 2120.
  • Outage recovery scenario 2120 envisions a complete gateway site outage. Specifically, gateway site 108 is illustrated as experiencing a complete gateway outage. In such a scenario, normal call path 2118 will never be received by the internal network telecommunications network 200.
  • the call is rerouted via carrier facility routing from carrier facility 126 over backup call path 2122 through off-network carrier 2115 to carrier facility 130 for termination to called party 120.
  • CIC overflow routing tables in carrier facility 126 will automatically reroute traffic through off-network carrier 2115.
  • FIG. 21D illustrates outage recovery scenario 2124 depicting another complete gateway site outage, different from that illustrated in FIG. 21C .
  • it is gateway site 110 that has experienced a complete gateway site outage.
  • call path 2118 from calling party 102 does reach an on-network device TG 232, but the call is placed to a called party on failed gateway site 110.
  • Backup call path 2126 is rerouted via soft switch overflow routing from TG 232 over DACS 242 to off-network carrier 2115 for termination at carrier facility 130 of called party 120.
  • soft switch 204 overflow routing automatically reroutes call traffic through off-network carrier 2115.
  • the back-up soft switch 304 initiates fail-over, it notifies the primary and secondary SS7 GWs 208 and 308 that the back-up soft switches 204 and 304 are now the contact points for signaling messages that had previously been targeted for failed soft switch 204.
  • FIGs. 21E and 21F illustrate outage recovery scenarios 2132 and 2140 involving a complete soft switch site outage.
  • FIG. 21E depicts soft switch site coverage of various gateway sites. Specifically, FIG. 21E illustrates western soft switch site 104, central soft switch site 106 and eastern soft switch site 302. Western soft switch site 104 is responsible for controlling all access servers 254 and 256 in circle 2136. Central soft switch site 106 is responsible for controlling all access servers 254 and 256 within circle 2134. Similarly, eastern soft switch site 302 is responsible for controlling all access servers 254 and 256 within circle 2138.
  • Western soft switch site 104 thus is responsible for controlling access servers 254 and 256 (not shown) in gateway sites 2135a, 2135b, 2135c, 2135d and 2135e.
  • Central soft switch site 106 is responsible for controlling access servers 254 and 256 (not shown) in gateway sites 2133a, 2133b, 2133c, 2133d, 2133e and 2133f.
  • Eastern soft switch site 302 is responsible for controlling access servers 254 and 256 (not shown) which are located in gateway sites 2139a, 2139b, 2139c, 2139d, 2139e and 2139f.
  • FIG. 21F illustrates outage recovery scenario 2140 depicting a complete soft switch site outage.
  • central soft switch site 106 has failed or been shut down for maintenance in outage recovery scenario 2140. Failure of central soft switch site 106 means that central soft switch site 106 can no longer control access servers 254 and 256 (not shown) which lie within circle 2134. Specifically, access servers 254 and 256 which lie within gateway sites 2133a-2133f cannot be controlled by central soft switch site 106.
  • FIG. 21F illustrates how western soft switch site 104 and eastern soft switch site 302 can take over control of gateway sites 2133a-2133f to overcome the outage of central soft switch site 106.
  • western soft switch site 104 can take over control of gateway sites 2133a, 2133d, 2133e and 2133f.
  • eastern soft switch site 302 can take over control of gateway sites 2133b and 2133c.
  • access servers 254 and 256 located in gateway sites 2133a, 2133b, 2133c, 2133d, 2133e and 2133f can seemlessly be controlled by soft switch sites 106 and 302 in other geographies. It would be apparent to persons having ordinary skill in the art that other outage scenarios could be similarly remedied via communication between soft switch sites 104, 106 and 302.
  • FIG. 21G depicts a block diagram 2146 of interprocess communication including a NOC 2114 communicating with a soft switch 204.
  • NOC 2114 communicates 2148 to soft switch 418 to startup command and control.
  • Soft switch 418 communicates 2150 in order to send alarms and network management alerts to NOC 2114.
  • NOC 2114 communicates 2152 in order to shut down soft switch 418 command and control.
  • Soft switch 418 can also accept management instructions from NOC 2114 at startup 2154 or at shutdown 2156.
  • IPDC Internet Protocol Device Control
  • the IPDC base protocol described below provides the basis for the IP device control family of protocols.
  • the IPDC protocols include a protocol suite.
  • the components of the IPDC protocol suite can be used individually or together to perform multiple functions. Functions which can be performed by the IPDC protocol suite include, for example, connection control, media control, and signaling transport for environments where the control logic is separated from the access server 254 and 256.
  • the IPDC protocol suite operates between the media gateway controller and the media gateway.
  • the media gateway controller can be thought of as soft switch 204.
  • the media gateway can be thought of as access servers 254 and 256, including, for example, TGs 232 and 234, AGs 238 and 240 and NASs 228 and 230.
  • the corresponding entities of media gateway controller and the media gateway are the call control and media control portions of the H.323 gateway.
  • IPDC acts to fulfill a need for protocols to control gateway devices which sit at the boundary between the circuit-switched telephone network and the Internet and to terminate circuit-switched trunks.
  • Examples of such devices include NASs 228 and 230 and voice-over-IP gateways, also known as access servers 254 and 256, including TGs 232 and 234 and AGs 238 and 240.
  • This need for a control protocol separate from call signaling arises when the service control logic needed to process calls lies partly or wholly outside the gateway devices.
  • the protocols implement the interface between soft switch 204 and access servers 254, 256.
  • IPDC views access servers 254 and 256, also known as media gateways, as applications which may control one or more physical devices.
  • IPDC can be used to control devices which do not meet the strict definition of a media gateway such as DACS 242 and 244 and ANSs 246 and 248.
  • IPDC builds on a base provided by DIAMETER.
  • DIAMETER has a number of advantages as a starting point including, for example, built-in provision for control security, facilities for starting up the control relation, and ready extensibility both in modular increments and at the individual command and attribute level.
  • DIAMETER is specifically written for authentication, authorization and accounting applications. Calhoun, Rubins, "DIAMETER based protocol", July 1998 . The DIAMETER based protocol specification was written by Pat Calhoun of Sun Microsystems, Inc. and Alan C. Rubins of Ascend Communications.
  • the IPDC protocol includes a message header followed by attribute-value-pairs (AVPs)
  • AVPs attribute-value-pairs
  • An IPDC command is a specialized data object which indicates the purpose and structure of the message which contains the IPDC command.
  • the command name can be used to denote the message format.
  • a DIAMETER device can be a client or server system that supports the DIAMETER based protocol.
  • a DIAMETER device can support extensions in addition to the DIAMETER based protocol.
EP99959070.6A 1998-11-20 1999-11-22 Voice over data telecommunications network architecture Expired - Lifetime EP1131926B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP10184126.0A EP2317711B1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture
EP10075638A EP2317710A3 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09/197,203 US6614781B1 (en) 1998-11-20 1998-11-20 Voice over data telecommunications network architecture
US197203 1998-11-20
PCT/US1999/027658 WO2000031933A1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture

Related Child Applications (3)

Application Number Title Priority Date Filing Date
EP10184126.0A Division-Into EP2317711B1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture
EP10184126.0A Division EP2317711B1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture
EP10075638A Division-Into EP2317710A3 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture

Publications (3)

Publication Number Publication Date
EP1131926A1 EP1131926A1 (en) 2001-09-12
EP1131926A4 EP1131926A4 (en) 2005-08-31
EP1131926B1 true EP1131926B1 (en) 2014-09-03

Family

ID=22728451

Family Applications (3)

Application Number Title Priority Date Filing Date
EP10184126.0A Expired - Lifetime EP2317711B1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture
EP99959070.6A Expired - Lifetime EP1131926B1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture
EP10075638A Withdrawn EP2317710A3 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP10184126.0A Expired - Lifetime EP2317711B1 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP10075638A Withdrawn EP2317710A3 (en) 1998-11-20 1999-11-22 Voice over data telecommunications network architecture

Country Status (5)

Country Link
US (7) US6614781B1 (un)
EP (3) EP2317711B1 (un)
AU (1) AU1631900A (un)
CA (1) CA2352961C (un)
WO (1) WO2000031933A1 (un)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9582371B1 (en) 2015-12-09 2017-02-28 International Business Machines Corporation Balancing latency and consistency requirements during data replication

Families Citing this family (1043)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100208634A1 (en) 1994-10-11 2010-08-19 Arbinet Corporation System and Method For Managing Multimedia Communications Across Convergent Networks
US6154445A (en) 1996-04-18 2000-11-28 Bell Atlantic Network Services, Inc. Telephony communication via varied redundant networks
US6069890A (en) 1996-06-26 2000-05-30 Bell Atlantic Network Services, Inc. Internet telephone service
US7158960B2 (en) * 1996-06-04 2007-01-02 Informative, Inc. Asynchronous network collaboration method and apparatus
US6754712B1 (en) * 2001-07-11 2004-06-22 Cisco Techonology, Inc. Virtual dial-up protocol for network communication
US6266328B1 (en) * 1996-08-26 2001-07-24 Caritas Technologies, Inc. Dial up telephone conferencing system controlled by an online computer network
CA2218218A1 (en) * 1996-11-08 1998-05-08 At&T Corp. Promiscuous network monitoring utilizing multicasting within a switch
US6101180A (en) 1996-11-12 2000-08-08 Starguide Digital Networks, Inc. High bandwidth broadcast system having localized multicast access to broadcast content
US6078582A (en) 1996-12-18 2000-06-20 Bell Atlantic Network Services, Inc. Internet long distance telephone service
US7031442B1 (en) 1997-02-10 2006-04-18 Genesys Telecommunications Laboratories, Inc. Methods and apparatus for personal routing in computer-simulated telephony
US6480600B1 (en) 1997-02-10 2002-11-12 Genesys Telecommunications Laboratories, Inc. Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality
US6104802A (en) 1997-02-10 2000-08-15 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
US6137869A (en) 1997-09-16 2000-10-24 Bell Atlantic Network Services, Inc. Network session management
US6574216B1 (en) 1997-03-11 2003-06-03 Verizon Services Corp. Packet data network voice call quality monitoring
US6292479B1 (en) 1997-03-19 2001-09-18 Bell Atlantic Network Services, Inc. Transport of caller identification information through diverse communication networks
US6870827B1 (en) 1997-03-19 2005-03-22 Verizon Services Corp. Voice call alternative routing through PSTN and internet networks
US7490169B1 (en) 1997-03-31 2009-02-10 West Corporation Providing a presentation on a network having a plurality of synchronized media types
US7412533B1 (en) 1997-03-31 2008-08-12 West Corporation Providing a presentation on a network having a plurality of synchronized media types
US6493338B1 (en) 1997-05-19 2002-12-10 Airbiquity Inc. Multichannel in-band signaling for data communications over digital wireless telecommunications networks
US6690681B1 (en) * 1997-05-19 2004-02-10 Airbiquity Inc. In-band signaling for data communications over digital wireless telecommunications network
US6324183B1 (en) 1998-12-04 2001-11-27 Tekelec Systems and methods for communicating messages among signaling system 7 (SS7) signaling points (SPs) and internet protocol (IP) nodes using signal transfer points (STPS)
US6944184B1 (en) 1998-12-04 2005-09-13 Tekelec Methods and systems for providing database node access control functionality in a communications network routing node
US7561538B2 (en) * 1997-07-24 2009-07-14 Oki Electronic Industry Co. Ltd. Concentrator for speech telephones and method of communication over LAN using same
US6711611B2 (en) 1998-09-11 2004-03-23 Genesis Telecommunications Laboratories, Inc. Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure
US6985943B2 (en) * 1998-09-11 2006-01-10 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US6201805B1 (en) 1997-10-21 2001-03-13 Dialogic Corporation Apparatus and method for computer telephone integration in packet switched telephone networks
US7126942B2 (en) * 1997-10-21 2006-10-24 Intel Corporation Apparatus and method for integrated computer controlled call processing in packet switched telephone networks
US7072308B2 (en) 1997-10-21 2006-07-04 Intel Corporation Apparatus and method for computer controlled call processing applications in packet switched telephone networks
US6876633B2 (en) * 1997-10-21 2005-04-05 Intel Corporation Apparatus and method for computer telephone integration in packet switched telephone networks
US6901068B1 (en) 1997-10-21 2005-05-31 Intel Corporation Apparatus and method for computer controlled call processing applications in packet switched telephone networks
US7068648B2 (en) * 1997-10-21 2006-06-27 Intel Corporation Apparatus and method for computer controlled call processing and information provision
US6856618B2 (en) * 1997-10-21 2005-02-15 Intel Corporation Apparatus and method for computer telephone integration in packet switched telephone networks
USRE46528E1 (en) 1997-11-14 2017-08-29 Genesys Telecommunications Laboratories, Inc. Implementation of call-center outbound dialing capability at a telephony network level
US7283561B1 (en) * 1997-12-12 2007-10-16 Level 3 Communications, Llc Secure network architecture with quality of service
US7907598B2 (en) 1998-02-17 2011-03-15 Genesys Telecommunication Laboratories, Inc. Method for implementing and executing communication center routing strategies represented in extensible markup language
US7227837B1 (en) 1998-04-30 2007-06-05 At&T Labs, Inc. Fault tolerant virtual tandem switch
US6169735B1 (en) * 1998-04-30 2001-01-02 Sbc Technology Resources, Inc. ATM-based distributed virtual tandem switching system
USRE46153E1 (en) 1998-09-11 2016-09-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US9037451B2 (en) * 1998-09-25 2015-05-19 Rpx Corporation Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses and methods for implementing language capabilities using the same
US7212522B1 (en) * 1998-09-30 2007-05-01 Cisco Technology, Inc. Communicating voice over a packet-switching network
AUPP702498A0 (en) * 1998-11-09 1998-12-03 Silverbrook Research Pty Ltd Image creation method and apparatus (ART77)
US6442169B1 (en) * 1998-11-20 2002-08-27 Level 3 Communications, Inc. System and method for bypassing data from egress facilities
US6614781B1 (en) 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
FI109439B (fi) * 1998-12-04 2002-07-31 Ericsson Telefon Ab L M Signalointiviestin siirtomekanismi
US6785233B1 (en) * 1998-12-16 2004-08-31 At&T Corp. Method for bandwidth management by resizing pipes
US7301964B1 (en) * 1998-12-16 2007-11-27 At&T Corp. Method for bandwidth management by resizing pipes
FI106499B (fi) * 1998-12-29 2001-02-15 Nokia Networks Oy Tiedonsiirtomenetelmä ja verkkoelementti
US6950441B1 (en) * 1999-03-30 2005-09-27 Sonus Networks, Inc. System and method to internetwork telecommunication networks of different protocols
US6765931B1 (en) * 1999-04-13 2004-07-20 Broadcom Corporation Gateway with voice
US7423983B1 (en) * 1999-09-20 2008-09-09 Broadcom Corporation Voice and data exchange over a packet based network
US7002970B1 (en) * 1999-05-19 2006-02-21 Edge Access, Inc. Private dialing plan for voice on a packet-based network
US6385615B1 (en) * 1999-05-21 2002-05-07 Cisco Technology, Inc. Communicating network information using universal resource locators
US6957346B1 (en) * 1999-06-15 2005-10-18 Ssh Communications Security Ltd. Method and arrangement for providing security through network address translations using tunneling and compensations
US6275470B1 (en) 1999-06-18 2001-08-14 Digital Island, Inc. On-demand overlay routing for computer-based communication networks
US7444407B2 (en) 2000-06-29 2008-10-28 Transnexus, Inc. Intelligent end user devices for clearinghouse services in an internet telephony system
US6404746B1 (en) * 1999-07-13 2002-06-11 Intervoice Limited Partnership System and method for packet network media redirection
GB2352111A (en) * 1999-07-14 2001-01-17 Ericsson Telefon Ab L M IP telecommunications
US7457280B2 (en) * 1999-07-14 2008-11-25 Telefonaktiebolaget L M Ericsson (Publ) Combining narrowband applications with broadband transport
US6563797B1 (en) * 1999-08-18 2003-05-13 At&T Corp. IP voice call surveillance through use of non-dedicated IP phone with signal alert provided to indicate content of incoming call prior to an answer as being a monitored call
CA2281356A1 (en) * 1999-09-01 2001-03-01 Andreas Weirich Enhanced line card and packetizing cpe for lifeline packet voice telephony
PT1208699E (pt) * 1999-09-02 2010-06-23 Nokia Siemens Networks Oy Controlo de chamadas nas redes inteligentes
US7457279B1 (en) 1999-09-10 2008-11-25 Vertical Communications Acquisition Corp. Method, system, and computer program product for managing routing servers and services
US7539179B1 (en) * 1999-09-30 2009-05-26 Cisco Technology, Inc. Scalable packet-switched call control signaling
US6973091B1 (en) 1999-10-04 2005-12-06 Hester Rex R Enabling quality voice communications from web page call control
US6987756B1 (en) * 1999-10-07 2006-01-17 Nortel Networks Limited Multi-mode endpoint in a communication network system and methods thereof
GB2355362B (en) * 1999-10-12 2003-08-06 Ericsson Telefon Ab L M Media gateway control
WO2001035655A2 (en) * 1999-11-08 2001-05-17 Polycom Israel Ltd. A method for controlling one or more multipoint control units with one multipoint control unit
US7002915B1 (en) * 1999-11-22 2006-02-21 Alcatel Canada Inc. Automated mass calling control for public switched telephone networks employing a packet based virtual tandem
US7929978B2 (en) 1999-12-01 2011-04-19 Genesys Telecommunications Laboratories, Inc. Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network
EP1238489B1 (en) * 1999-12-13 2008-03-05 Broadcom Corporation Voice gateway with downstream voice synchronization
FI19992720A (fi) 1999-12-17 2001-06-18 Nokia Networks Oy Datapuhelun reititys IP-yhteyksillä
US7203956B2 (en) 1999-12-22 2007-04-10 Transnexus, Inc. System and method for the secure enrollment of devices with a clearinghouse server for internet telephony and multimedia communications
US7353251B1 (en) * 1999-12-23 2008-04-01 Polycom, Inc. Automated call launching
GB2391134B (en) * 1999-12-23 2004-05-12 Mitel Knowledge Corp Communication system architecture for voice first collaboration
US7068668B2 (en) * 2000-01-07 2006-06-27 Feuer Donald S Method and apparatus for interfacing a public switched telephone network and an internet protocol network for multi-media communication
AU2001230921A1 (en) * 2000-01-11 2001-07-24 Transnexus, Inc. Architectures for clearing and settlement services between internet telephony clearinghouses
US6754232B1 (en) * 2000-01-12 2004-06-22 Cisco Technology, Inc. Dynamic codec speed selection and bandwidth preallocation in a voice packet network method and apparatus
US6343065B1 (en) * 2000-01-20 2002-01-29 Sbc Technology Resources, Inc. System and method of measurement-based adaptive caching of virtual connections
AU2001232894A1 (en) * 2000-01-20 2001-07-31 Mci Worldcom, Inc. Intelligent network and method for providing voice telephony over atm and closeduser groups
US7006980B1 (en) 2000-02-04 2006-02-28 Callvision, Inc. Method and system for selecting optimal commodities based upon business profile and preferences
US7443969B2 (en) * 2003-09-24 2008-10-28 At&T Intellectual Property I, L.P. Methods and systems for billing and routing local toll-free communications
JP2001237897A (ja) * 2000-02-22 2001-08-31 Nec Corp ハイブリッド型テレフォニーシステム
CN100477701C (zh) * 2000-02-22 2009-04-08 北方电讯网络有限公司 控制无线分组交换语音呼叫的系统及方法
US8977621B1 (en) 2000-02-24 2015-03-10 Richard Paiz Search engine optimizer
US9355352B1 (en) 2000-02-24 2016-05-31 Richard Paiz Personal search results
US7328239B1 (en) * 2000-03-01 2008-02-05 Intercall, Inc. Method and apparatus for automatically data streaming a multiparty conference session
US6985905B2 (en) * 2000-03-03 2006-01-10 Radiant Logic Inc. System and method for providing access to databases via directories and other hierarchical structures and interfaces
US20060173873A1 (en) * 2000-03-03 2006-08-03 Michel Prompt System and method for providing access to databases via directories and other hierarchical structures and interfaces
US20020010736A1 (en) * 2000-03-06 2002-01-24 Telenova Communications Corp. Internet based audio and video communication system using a virtual desktop
US6980526B2 (en) 2000-03-24 2005-12-27 Margalla Communications, Inc. Multiple subscriber videoconferencing system
US6684250B2 (en) * 2000-04-03 2004-01-27 Quova, Inc. Method and apparatus for estimating a geographic location of a networked entity
DE50113446D1 (de) * 2000-04-06 2008-02-14 Nokia Siemens Networks Gmbh Anordnung zum anschluss einer telekommunikationseinrichtung an ein paketvermittelndes kommunikationsnetz
US6615034B1 (en) * 2000-04-27 2003-09-02 Sprint Communications Company L.P. Communication billing system
US7324635B2 (en) 2000-05-04 2008-01-29 Telemaze Llc Branch calling and caller ID based call routing telephone features
US7222147B1 (en) * 2000-05-20 2007-05-22 Ciena Corporation Processing network management data in accordance with metadata files
US7286652B1 (en) * 2000-05-31 2007-10-23 3Com Corporation Four channel audio recording in a packet based network
US7318091B2 (en) 2000-06-01 2008-01-08 Tekelec Methods and systems for providing converged network management functionality in a gateway routing node to communicate operating status information associated with a signaling system 7 (SS7) node to a data network node
AU2000256813A1 (en) * 2000-06-13 2001-12-24 Nokia Corporation System and method for controlling a media gateway
US6869028B2 (en) * 2000-06-14 2005-03-22 The Procter & Gamble Company Spraying device
US7046658B1 (en) * 2000-06-23 2006-05-16 At & T Corp. Method and system for customer selected direct dialed voice-over-internet protocol (VOIP)
US7117152B1 (en) 2000-06-23 2006-10-03 Cisco Technology, Inc. System and method for speech recognition assisted voice communications
US7082119B1 (en) 2000-06-28 2006-07-25 Cisco Technology, Inc. Full PBX telephony feature preservation across a voice over packet network
US6785301B1 (en) * 2000-06-29 2004-08-31 Cisco Technology, Inc. Method and apparatus for conducting call waiting-caller identification in a packet switched network
US8041817B2 (en) 2000-06-30 2011-10-18 At&T Intellectual Property I, Lp Anonymous location service for wireless networks
US7184538B1 (en) 2000-06-30 2007-02-27 Verizon Services Corp. Method of and apparatus for mediating common channel signaling message between networks using control message templates
US7224686B1 (en) 2000-06-30 2007-05-29 Verizon Services Corp. Method of and apparatus for mediating common channel signaling messages between networks using a pseudo-switch
US7218613B1 (en) * 2000-06-30 2007-05-15 Verizon Services Corp Method and apparatus for in context mediating common channel signaling messages between networks
FI20001578A (fi) * 2000-06-30 2001-12-31 Nokia Networks Oy QoS-arkkitehtuuri
US7360090B1 (en) 2000-06-30 2008-04-15 Verizon Services Corp. Method of and apparatus for authenticating control messages in a signaling network
US7111163B1 (en) 2000-07-10 2006-09-19 Alterwan, Inc. Wide area network using internet with quality of service
US7693976B2 (en) * 2000-07-11 2010-04-06 Ciena Corporation Granular management of network resources
US7996310B1 (en) * 2000-07-19 2011-08-09 Globys, Inc. Electronic financial management and analysis system and related methods
US7065070B1 (en) * 2000-07-21 2006-06-20 Chang Ifay F Method and system for establishing a voice communication service for business transactions and commerce applications
US7286521B1 (en) * 2000-07-21 2007-10-23 Tellme Networks, Inc. Localized voice over internet protocol communication
US7796998B1 (en) * 2000-08-01 2010-09-14 At&T Intellectual Property, I, L.P. Method and system for delivery of a calling party's location
EP1305918B1 (de) * 2000-08-01 2007-03-28 Siemens Aktiengesellschaft Verfahren zum übertragen von sprachdaten über verschiedene arten von netzen sowie zugehörige einheiten
EP1305958A1 (de) * 2000-08-02 2003-05-02 Siemens Aktiengesellschaft Verfahren zum vermitteln für die übertragung von nutzdatenpaketen sowie zugehörige signalisierungseinheit
US6944166B1 (en) * 2000-08-09 2005-09-13 Nortel Networks Limited Method for controlling service levels over packet based networks
US20020042832A1 (en) * 2000-08-14 2002-04-11 Fallentine Mark D. System and method for interoperability of H.323 video conferences with network address translation
US7002919B1 (en) * 2000-08-16 2006-02-21 Lucent Technologies Inc. Method and system for guaranteeing quality of service for voice-over-IP services
US7002993B1 (en) * 2000-08-18 2006-02-21 Juniper Networks, Inc. Method and apparatus providing media aggregation in a packet-switched network
US7586899B1 (en) * 2000-08-18 2009-09-08 Juniper Networks, Inc. Methods and apparatus providing an overlay network for voice over internet protocol applications
US7106722B1 (en) * 2000-08-20 2006-09-12 Telefonktiebolaget Lm Ericsson (Publ) System for media gateway to media gateway address information exchange
US6839416B1 (en) 2000-08-21 2005-01-04 Cisco Technology, Inc. Apparatus and method for controlling an audio conference
US7254832B1 (en) * 2000-08-28 2007-08-07 Nortel Networks Limited Firewall control for secure private networks with public VoIP access
US6738472B1 (en) * 2000-09-06 2004-05-18 Sigvalue Technologies Ltd System and method for managing telephony network resources
US7227927B1 (en) * 2000-09-08 2007-06-05 Tekelec Scalable call processing node
EP1319281B1 (en) * 2000-09-11 2007-05-09 TransNexus, Inc. Clearinghouse server for internet telephony and multimedia communications
US6757275B2 (en) * 2000-09-11 2004-06-29 Bob Sorrentino Method and system of managing connections between circuit-switched and packet-switched networks
US7454518B1 (en) * 2000-09-12 2008-11-18 Nortel Networks Limited System, device, and method for receiver access control in a multicast communication network
US8250357B2 (en) 2000-09-13 2012-08-21 Fortinet, Inc. Tunnel interface for securing traffic over a network
US7574495B1 (en) * 2000-09-13 2009-08-11 Fortinet, Inc. System and method for managing interworking communications protocols
US7111072B1 (en) 2000-09-13 2006-09-19 Cosine Communications, Inc. Packet routing system and method
US7272643B1 (en) 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US7487232B1 (en) * 2000-09-13 2009-02-03 Fortinet, Inc. Switch management system and method
WO2002023806A2 (en) * 2000-09-15 2002-03-21 British Telecommunications Public Limtied Company Design of communications networks
US7436839B1 (en) * 2001-10-09 2008-10-14 At&T Delaware Intellectual Property, Inc. Systems and methods for providing services through an integrated digital network
US7675900B1 (en) * 2000-10-09 2010-03-09 Genband Inc. System and method for interfacing between signaling protocols
US7082102B1 (en) * 2000-10-19 2006-07-25 Bellsouth Intellectual Property Corp. Systems and methods for policy-enabled communications networks
US6888839B1 (en) * 2000-10-19 2005-05-03 Nortel Networks Limited Method and apparatus for tunneling operating codes to and from a call server in a packet network
EP1202521B1 (en) * 2000-10-31 2005-06-29 Hewlett-Packard Company, A Delaware Corporation A method for processing in a gatekeeper of an internet protocol network
WO2002037301A1 (en) * 2000-11-02 2002-05-10 Polycom, Inc. Conferencing network resource management for call connectivity
DE10054940B4 (de) * 2000-11-06 2005-06-02 Siemens Ag Verfahren zum Übertragen von Faxdaten über ein Paketübertragungsnetz, zugehörige Einheiten und zugehöriges Programm
US6693897B1 (en) * 2000-11-10 2004-02-17 Sbc Technology Resources, Inc. Method and system of screening and control of telephone calls while using a packet-switched data network
JP4225681B2 (ja) * 2000-12-06 2009-02-18 富士通株式会社 仮想閉域網構築方法及び装置並びに中継装置
US6865162B1 (en) 2000-12-06 2005-03-08 Cisco Technology, Inc. Elimination of clipping associated with VAD-directed silence suppression
US6925063B2 (en) * 2000-12-14 2005-08-02 Shmuel Goldshtein Voice over internet communications algorithm and related method for optimizing and reducing latency delays
ES2656351T3 (es) * 2000-12-14 2018-02-26 Counterpath Corporation Método de re-selección de teléfono móvil entre una red celular de conmutación de circuitos y una red de conmutación de paquetes
US7333512B2 (en) * 2000-12-18 2008-02-19 Rmi Corporation Dynamic mixing TDM data with data packets
US7130630B1 (en) 2000-12-19 2006-10-31 Bellsouth Intellectual Property Corporation Location query service for wireless networks
US7110749B2 (en) 2000-12-19 2006-09-19 Bellsouth Intellectual Property Corporation Identity blocking service from a wireless service provider
US7428411B2 (en) 2000-12-19 2008-09-23 At&T Delaware Intellectual Property, Inc. Location-based security rules
US7085555B2 (en) 2000-12-19 2006-08-01 Bellsouth Intellectual Property Corporation Location blocking service from a web advertiser
US7116977B1 (en) 2000-12-19 2006-10-03 Bellsouth Intellectual Property Corporation System and method for using location information to execute an action
US7181225B1 (en) 2000-12-19 2007-02-20 Bellsouth Intellectual Property Corporation System and method for surveying wireless device users by location
US7224978B2 (en) 2000-12-19 2007-05-29 Bellsouth Intellectual Property Corporation Location blocking service from a wireless service provider
US7245925B2 (en) 2000-12-19 2007-07-17 At&T Intellectual Property, Inc. System and method for using location information to execute an action
US7095741B1 (en) * 2000-12-20 2006-08-22 Cisco Technology, Inc. Port isolation for restricting traffic flow on layer 2 switches
US7415029B1 (en) * 2000-12-22 2008-08-19 Cisco Technology, Inc. Programmable FSM engine using a new CAS application language
US7440413B1 (en) * 2000-12-27 2008-10-21 Bellsouth Intellectual Property Corporation Asynchronous digital subscriber line (ADSL) resource planning
JP2002204268A (ja) * 2000-12-28 2002-07-19 Fujitsu Ltd 通信制御装置及び方法並びにこの通信制御装置を用いたシステム
US7085279B1 (en) 2000-12-29 2006-08-01 Cisco Technology, Inc. Method and apparatus for carrying telephony network traffic over an ATM network
US6898637B2 (en) * 2001-01-10 2005-05-24 Agere Systems, Inc. Distributed audio collaboration method and apparatus
US7525956B2 (en) 2001-01-11 2009-04-28 Transnexus, Inc. Architectures for clearing and settlement services between internet telephony clearinghouses
US7039720B2 (en) * 2001-01-25 2006-05-02 Marconi Intellectual Property (Ringfence) , Inc. Dense virtual router packet switching
US7668916B2 (en) * 2001-02-07 2010-02-23 Paltalk Holdings, Inc. System architecture for linking packet-switched and circuit-switched clients
GB0103381D0 (en) * 2001-02-12 2001-03-28 Eyretel Ltd Packet data recording method and system
US7277444B2 (en) * 2001-02-12 2007-10-02 Redknee Inc. Method and system for distributing and executing service logic
US6925082B2 (en) * 2001-02-15 2005-08-02 Lucent Technologies Inc. ATM packet access gateway
US7461148B1 (en) * 2001-02-16 2008-12-02 Swsoft Holdings, Ltd. Virtual private server with isolation of system components
US7606909B1 (en) * 2001-02-20 2009-10-20 Michael Ely Method and apparatus for a business contact center
KR100422410B1 (ko) * 2001-02-22 2004-03-10 주식회사 넷투싸이버 네트워크 기반의 브이오아이피를 이용한 통화 서비스 시스템
US7006489B2 (en) * 2001-02-23 2006-02-28 Santera Systems, Inc. Voice packet switching system and method
US6823197B1 (en) * 2001-03-13 2004-11-23 At&T Corp. Method and system for providing mobility to enhanced call service features at remote locations
US7406306B2 (en) * 2001-03-20 2008-07-29 Verizon Business Global Llc Method for billing in a telecommunications network
US7945592B2 (en) 2001-03-20 2011-05-17 Verizon Business Global Llc XML based transaction detail records
US7599351B2 (en) * 2001-03-20 2009-10-06 Verizon Business Global Llc Recursive query for communications network data
US8380840B2 (en) 2001-12-17 2013-02-19 Verizon Business Global Llc Method for recording events in an IP network
US20020188713A1 (en) * 2001-03-28 2002-12-12 Jack Bloch Distributed architecture for a telecommunications system
US7388858B2 (en) * 2001-03-28 2008-06-17 Nokia Siemens Networks Gmbh & Co. Kg Distributed architecture for a telecommunications software switch
US7664119B2 (en) * 2001-03-30 2010-02-16 Intel Corporation Method and apparatus to perform network routing
JP2002300181A (ja) * 2001-03-30 2002-10-11 Nec Corp 統合ネットワークＱｏＳ制御方式
US7130281B1 (en) * 2001-03-30 2006-10-31 Cisco Technology, Inc. Devices, softwares and methods with improved performance of acoustic echo canceler in VoIP communication
US6954455B1 (en) * 2001-04-02 2005-10-11 At&T Corp. Technique for providing intelligent features for calls in a communications network independent of network architecture
US7797530B2 (en) * 2001-04-09 2010-09-14 Hewlett-Packard Company Authentication and encryption method and apparatus for a wireless local access network
US20020150221A1 (en) * 2001-04-12 2002-10-17 Carson Douglas John Generating call detail records
US6868059B1 (en) * 2001-04-24 2005-03-15 Cisco Technology, Inc. Clusters of devices, softwares and methods for improved handling of a gatekeeper load in VoIP communication
US20020159439A1 (en) * 2001-04-25 2002-10-31 Marsh Anita B. Dynamically downloading telecommunication call services
CN1524369A (zh) * 2001-04-27 2004-08-25 在基于因特网协议的话音网络中使呼叫信令和话路建立同步的方法
AU2002309882A1 (en) * 2001-05-16 2002-11-25 Nact Telecommunications, Inc. System, apparatus and method for dynamically mapping virtual signaling system 7 circuit identification codes for use between voip gateways on ip-based networks
US20020176378A1 (en) * 2001-05-22 2002-11-28 Hamilton Thomas E. Platform and method for providing wireless data services
KR100383625B1 (ko) * 2001-05-26 2003-05-14 삼성전자주식회사 보이스 오버 인터넷 프로토콜 시스템에서의 라우팅 서비스방법
US6704406B1 (en) * 2001-05-29 2004-03-09 Cisco Technology, Inc. Automated route plan generation
US7281043B1 (en) * 2001-05-31 2007-10-09 Cisco Technology, Inc. System for sharing resources among RSVP sessions
US7617292B2 (en) 2001-06-05 2009-11-10 Silicon Graphics International Multi-class heterogeneous clients in a clustered filesystem
US7765329B2 (en) * 2002-06-05 2010-07-27 Silicon Graphics International Messaging between heterogeneous clients of a storage area network
US8010558B2 (en) 2001-06-05 2011-08-30 Silicon Graphics International Relocation of metadata server with outstanding DMAPI requests
US7640582B2 (en) 2003-04-16 2009-12-29 Silicon Graphics International Clustered filesystem for mix of trusted and untrusted nodes
US20040139125A1 (en) 2001-06-05 2004-07-15 Roger Strassburg Snapshot copy of data volume during data access
US20020188732A1 (en) * 2001-06-06 2002-12-12 Buckman Charles R. System and method for allocating bandwidth across a network
US7369535B2 (en) * 2001-06-11 2008-05-06 Level 3 Communications, Llc Voice over Internet Protocol real time protocol routing
US7106706B1 (en) * 2001-06-27 2006-09-12 Sprint Spectrum L.P. Method and system for providing dial-up data sessions
US7181547B1 (en) 2001-06-28 2007-02-20 Fortinet, Inc. Identifying nodes in a ring network
US20030002478A1 (en) * 2001-06-29 2003-01-02 Hani El-Gebaly Lightweight internet protocol telephony client
US7095715B2 (en) 2001-07-02 2006-08-22 3Com Corporation System and method for processing network packet flows
US7046659B1 (en) * 2001-07-03 2006-05-16 Cisco Technology, Inc. Call signaling approach to user self-provisioning on VoIP using a touch-tone interface
US20030013465A1 (en) * 2001-07-11 2003-01-16 Choong Philip T. System and method for pseudo-tunneling voice transmissions
US7043731B2 (en) * 2001-07-12 2006-05-09 Qwest Communications International, Inc. Method and system for distributing access to group of objects based on round robin algorithm and only when the object is available
US7899167B1 (en) * 2003-08-15 2011-03-01 Securus Technologies, Inc. Centralized call processing
US7327720B2 (en) * 2001-07-18 2008-02-05 Emerson Iii Harry E Integrated telephone central office systems for integrating the internet with the public switched telephone network
US8098651B1 (en) * 2001-07-27 2012-01-17 Rockstar Bidco, LP Integrating multimedia capabilities with circuit-switched calls
US7046683B1 (en) * 2001-07-31 2006-05-16 Cisco Technology, Inc. VoIP over access network
US7339908B2 (en) * 2001-07-31 2008-03-04 Arraycomm, Llc. System and related methods to facilitate delivery of enhanced data services in a mobile wireless communications environment
US6977906B2 (en) * 2001-08-14 2005-12-20 The Directv Group, Inc. System and method for provisioning broadband service in a PPPoE network using a random username
US7154912B2 (en) * 2001-08-14 2006-12-26 The Directv Group, Inc. System and method for provisioning broadband service in a PPPoE network using a list of stored domain names
US7047304B2 (en) * 2001-08-14 2006-05-16 The Directv Group, Inc. System and method for provisioning broadband service in a PPPoE network using a configuration domain name
US7126941B1 (en) * 2001-08-24 2006-10-24 Cisco Technology, Inc. Managing packet voice networks using a virtual switch approach
US7466710B1 (en) 2001-08-24 2008-12-16 Cisco Technology, Inc. Managing packet voice networks using a virtual entity approach
CN1180573C (zh) * 2001-08-29 2004-12-15 华为技术有限公司 Ip网络系统中的节点跨区域呼叫方法
DE10142613A1 (de) * 2001-08-31 2003-04-03 Siemens Ag Anordnung zum Bereitstellen von Ansagen und Dialogen in Paketnetzen
US7533410B1 (en) * 2001-09-06 2009-05-12 At & T Corp. Architecture to support public voice VPN services over an IP network
US20080002669A1 (en) * 2001-09-14 2008-01-03 O'brien Ray Packet voice gateway
US7079527B2 (en) * 2001-09-20 2006-07-18 The Directv Group, Inc. System and method for provisioning broadband service in a PPPoE network using DTMF communication
DE10147148A1 (de) * 2001-09-25 2003-04-24 Siemens Ag Netzübergangseinrichtung und Kommunikationssystem für Echtzeitkommunikationsverbindungen
DE10147164B4 (de) * 2001-09-25 2004-05-06 Siemens Ag Verfahren zur Ermittlung der Laufzeitverzögerung einer Verbindung mit Übertragung über ein paketbasiertes Netz
US7257110B2 (en) * 2001-09-28 2007-08-14 Siemens Communications, Inc. Call processing architecture
DE10148875A1 (de) * 2001-10-04 2003-04-24 Siemens Ag Verfahren zum Aktuellhalten von Software auf verschiedenen Endgeräten
US7274684B2 (en) * 2001-10-10 2007-09-25 Bruce Fitzgerald Young Method and system for implementing and managing a multimedia access network device
EP1303118A1 (de) * 2001-10-12 2003-04-16 Siemens Aktiengesellschaft Verfahren zur Herstellung einer Kommunikationsverbindung zwischen Teilnehmerstellen eines zwei Kommunikationsnetze umfassenden Vermittlungssystems
US7469299B2 (en) * 2001-10-25 2008-12-23 Verizon Business Global Llc Bridging user agent and a proxy server for supporting network services
US7865621B1 (en) * 2001-10-26 2011-01-04 Spice I2I Limited Open settlement protocol bridge for multi-network voice connections
US7215965B2 (en) 2001-11-01 2007-05-08 Airbiquity Inc. Facility and method for wireless transmission of location data in a voice channel of a digital wireless telecommunications network
US7987270B2 (en) 2001-11-05 2011-07-26 Spyder Navigations L.L.C. Apparatus, and associated method, for facilitating QoS and bearer setup in an IP-based communication system
WO2003049462A1 (en) * 2001-12-03 2003-06-12 Nokia Corporation Context filter in a mobile node
US20040003046A1 (en) * 2001-12-12 2004-01-01 3Com Corporation System and methods for providing instant services in an internet protocol network
US6954456B2 (en) * 2001-12-14 2005-10-11 At & T Corp. Method for content-aware redirection and content renaming
CN100433695C (zh) * 2001-12-19 2008-11-12 中兴通讯股份有限公司 一种软交换机域内用户的登记方法
US7103001B1 (en) * 2001-12-19 2006-09-05 Bell South Intellectual Property Corp. System and method for planning ports in DSL network elements
US7408928B2 (en) * 2001-12-21 2008-08-05 Nortel Networks Limited Methods and apparatus for setting up telephony connections between two address domains having overlapping address ranges
US8477758B2 (en) * 2001-12-21 2013-07-02 At&T Intellectual Property I, L.P. Voice over network (VoN)/voice over internet protocol (VoIP) architect having hotline and optional tie line
US7391761B1 (en) 2001-12-21 2008-06-24 At&T Delaware Intellectual Property, Inc. System and method for voice over internet protocol using a standard telephone system
WO2003055153A2 (en) * 2001-12-21 2003-07-03 Muirhead Charles S System for supply chain management of virtual private network services
US20030120553A1 (en) * 2001-12-21 2003-06-26 Bell Canada Method and apparatus for vending and delivering telephone services
US7801289B2 (en) * 2001-12-21 2010-09-21 At&T Intellectual Property I, L.P. Voice-over network (VoN)/voice-over internet protocol (VoIP) architect using advance intelligent network alternatives
US7239639B2 (en) 2001-12-27 2007-07-03 3Com Corporation System and method for dynamically constructing packet classification rules
US7324501B1 (en) * 2001-12-28 2008-01-29 Cisco Technology, Inc. Method and system for multicasting over a UTOPIA bus
US6978001B1 (en) 2001-12-31 2005-12-20 Cisco Technology, Inc. Method and system for controlling audio content during multiparty communication sessions
US7177304B1 (en) * 2002-01-03 2007-02-13 Cisco Technology, Inc. Devices, softwares and methods for prioritizing between voice data packets for discard decision purposes
US20030131132A1 (en) * 2002-01-10 2003-07-10 Shih-An Cheng Method and system for a routing server for selecting a PSTN gateway
US7277421B1 (en) * 2002-01-16 2007-10-02 Verizon Services Corp. Telephone call processing using SIP and/or ENUM
US7656794B2 (en) * 2002-01-24 2010-02-02 General Instrument Corporation Method and apparatus for authenticated quality of service reservation
US6996225B1 (en) * 2002-01-31 2006-02-07 Cisco Technology, Inc. Arrangement for controlling congestion in an SS7 signaling node based on packet classification
US6973082B2 (en) * 2002-02-01 2005-12-06 Fujitsu Limited Forwarding packets to aggregated links using distributed ingress card processing
US7020150B2 (en) * 2002-02-22 2006-03-28 Nortel Networks Limited System, device, and method for traffic and subscriber service differentiation using multiprotocol label switching
US7245611B2 (en) * 2002-02-27 2007-07-17 J2 Global Communications Method and process for signaling, communication and administration of networked objects
US7668306B2 (en) * 2002-03-08 2010-02-23 Intel Corporation Method and apparatus for connecting packet telephony calls between secure and non-secure networks
US7792973B2 (en) * 2002-03-12 2010-09-07 Verizon Business Global Llc Systems and methods for initiating announcements in a SIP telecommunications network
US7092385B2 (en) * 2002-03-12 2006-08-15 Mci, Llc Policy control and billing support for call transfer in a session initiation protocol (SIP) network
US20030177283A1 (en) * 2002-03-18 2003-09-18 Hamilton Thomas E. Application program interface
US9332037B2 (en) * 2002-03-27 2016-05-03 Alcatel Lucent Method and apparatus for redundant signaling links
US20050232256A1 (en) * 2002-03-29 2005-10-20 Jason White Applying object oriented concepts to switch system configurations
US7333483B2 (en) * 2002-04-02 2008-02-19 Huawei Technologies Co., Ltd. Integrated mobile gateway device used in wireless communication network
EP1351478A1 (de) * 2002-04-03 2003-10-08 Siemens Aktiengesellschaft Steuerung einer Sprachkommunikationsverbindung in einem paketvermittelnden Kommunikationsnetz zwischen unterschiedlichen Domänen zugeordneten Kommunikationseinrichtungen
US7860222B1 (en) 2003-11-24 2010-12-28 Securus Technologies, Inc. Systems and methods for acquiring, accessing, and analyzing investigative information
US8098804B1 (en) * 2002-04-29 2012-01-17 Securus Technologies, Inc. Systems and methods for call treatment using a third party database
US20040015541A1 (en) * 2002-07-22 2004-01-22 Web.De Ag Communications environment having a portal
US20050182824A1 (en) * 2002-04-30 2005-08-18 Pierre-Alain Cotte Communications web site
US20040015563A1 (en) * 2002-07-22 2004-01-22 Web. De Ag Communications environment having web sites on a portal
US20040019629A1 (en) * 2002-07-23 2004-01-29 Web.De Ag Communications environment
US20040013258A1 (en) * 2002-07-22 2004-01-22 Web. De Ag Communications environment having a connection device
US20040015546A1 (en) * 2002-07-22 2004-01-22 Web.De Ag Communications environment having communications between portals
US20040015588A1 (en) * 2002-07-22 2004-01-22 Web.De Ag Communications environment having multiple web sites
US20030214939A1 (en) * 2002-05-15 2003-11-20 Ismail I. Eldumiati Method and apparatus for providing life line service to access gateway telephony subscribers
US7248565B1 (en) 2002-05-16 2007-07-24 Cisco Technology, Inc. Arrangement for managing multiple gateway trunk groups for voice over IP networks
US7324502B2 (en) * 2002-05-20 2008-01-29 Agilent Technologies, Inc. System and method for mapping a PSTN trunk to a packet network endpoint
EP1370093A1 (en) * 2002-06-03 2003-12-10 Alcatel New generation telecommunications network with gateways for voice transmission
US7376125B1 (en) 2002-06-04 2008-05-20 Fortinet, Inc. Service processing switch
US7203192B2 (en) 2002-06-04 2007-04-10 Fortinet, Inc. Network packet steering
US6674758B2 (en) * 2002-06-06 2004-01-06 Clinton Watson Mechanism for implementing voice over IP telephony behind network firewalls
EP1372302A3 (en) * 2002-06-14 2007-07-18 Polycom, Inc. Multipoint multimedia/audio conference using IP trunking
US7437463B1 (en) * 2002-06-21 2008-10-14 Polycom, Inc. Method and means for providing scheduling for a videoconferencing network in a manner to ensure bandwidth
US8667105B1 (en) * 2002-06-26 2014-03-04 Apple Inc. Systems and methods facilitating relocatability of devices between networks
US7236484B2 (en) * 2002-07-22 2007-06-26 Lucent Technologies Inc. Methods and systems for providing wide-band voice service via a telephone switch system
US7283541B2 (en) * 2002-07-30 2007-10-16 At&T Corp. Method of sizing packets for routing over a communication network for VoIP calls on a per call basis
DE10234937A1 (de) * 2002-07-31 2004-02-19 Siemens Ag Effiziente Behandlung von ISDN-Anschlüssen durch eine paketorientierte Vermittlungsstelle
US20040078601A1 (en) * 2002-08-02 2004-04-22 Chris Tengwall System and method for operating a wireless device network
US7154880B2 (en) * 2002-08-12 2006-12-26 Vodtel Communications Inc. Non-server type voice packet communication device and method
US20040045033A1 (en) * 2002-08-27 2004-03-04 Broadcom Corporation Distributed cable modem termination system (CMTS) architecture implementing a media access control chip
US7551610B2 (en) * 2002-08-27 2009-06-23 Broadcom Corporation MiniMAC implementation of a distributed cable modem termination system (CMTS) architecture
US20040045035A1 (en) * 2002-08-27 2004-03-04 Broadcom Corporation Distributed cable modem termination system (CMTS) architecture
US20040045037A1 (en) * 2002-08-27 2004-03-04 Broadcom Corporation Distributed cable modem termination system (CMTS) architecture implementing a media access control chip
US7298708B2 (en) 2002-08-28 2007-11-20 Mitel Knowledge Corporation IP device registration
US7716725B2 (en) * 2002-09-20 2010-05-11 Fortinet, Inc. Firewall interface configuration and processes to enable bi-directional VoIP traversal communications
US7716311B2 (en) * 2002-09-30 2010-05-11 Avaya Inc. Method and apparatus for monitoring of switch resources using resource group definitions
US7920546B2 (en) 2002-10-01 2011-04-05 Nortel Networks Limited Automated attendant multimedia session
US7646761B2 (en) * 2002-10-01 2010-01-12 Nortel Networks Limited Integrating multimedia capabilities with legacy networks
US7382768B2 (en) * 2002-10-11 2008-06-03 Agilent Technologies, Inc. Real-time protocol (RTP) flow analysis using network processor
US7372848B2 (en) * 2002-10-11 2008-05-13 Agilent Technologies, Inc. Dynamically controlled packet filtering with correlation to signaling protocols
US7372849B2 (en) * 2002-10-15 2008-05-13 Cisco Technology, Inc. Port policy management for calls in a centralized call control packet network
US7876744B2 (en) 2002-11-14 2011-01-25 Ey-Taeg Kwon Method for collect call service based on VoIP technology and system thereof
US7366159B1 (en) * 2002-11-14 2008-04-29 At&T Corp. Mix protocol multi-media provider system incorporating a session initiation protocol based media server adapted to form preliminary communication with calling communication devices
US7266120B2 (en) * 2002-11-18 2007-09-04 Fortinet, Inc. System and method for hardware accelerated packet multicast in a virtual routing system
US7801171B2 (en) 2002-12-02 2010-09-21 Redknee Inc. Method for implementing an Open Charging (OC) middleware platform and gateway system
JP4266625B2 (ja) * 2002-12-02 2009-05-20 Ｎｅｃインフロンティア株式会社 Ｌａｎ外接続ｉｐキーテレフォンシステム及びその端末と主装置並びにそのｌａｎ外接続方法
WO2004051945A1 (en) * 2002-12-03 2004-06-17 Zte Corporation The implementation of the intelligent network in the next generation networks and its interconnection to the pstn
JP3862652B2 (ja) * 2002-12-10 2006-12-27 キヤノン株式会社 印刷制御方法及び情報処理装置
KR100475188B1 (ko) * 2002-12-13 2005-03-10 삼성전자주식회사 사설교환기에서의 ＶｏＩＰ 호 제어 장치 및 그 방법
US7023977B2 (en) * 2002-12-16 2006-04-04 Alcatel Method and system for providing softswitch failure protection in a communication network
US7388868B2 (en) * 2002-12-17 2008-06-17 Alcatel Lucent Call-routing apparatus, and associated method, for providing local call handling functions in a communication network
US8150018B2 (en) * 2002-12-18 2012-04-03 Cisco Technology, Inc. System and method for provisioning connections as a distributed digital cross-connect over a packet network
US20040136362A1 (en) * 2002-12-18 2004-07-15 John Landau Multiple carrier gateway system, method and apparatus
US7920690B2 (en) * 2002-12-20 2011-04-05 Nortel Networks Limited Interworking of multimedia and telephony equipment
US7496192B1 (en) * 2002-12-20 2009-02-24 Nortel Networks Limited Interworking of multimedia and telephony equipment
US20040120505A1 (en) * 2002-12-20 2004-06-24 Motorola, Inc. Method and apparatus for providing a voiced call alert
US7620154B2 (en) 2002-12-23 2009-11-17 Cambron G Keith Equivalent working length determinative system for digital subscriber line circuits
US7372957B2 (en) * 2002-12-24 2008-05-13 Intel Corporation Method and apparatus for implementing call processing in packet telephony networks
US7363381B2 (en) 2003-01-09 2008-04-22 Level 3 Communications, Llc Routing calls through a network
US20040148391A1 (en) * 2003-01-11 2004-07-29 Lake Shannon M Cognitive network
US7457865B2 (en) * 2003-01-23 2008-11-25 Redknee Inc. Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system
US6885973B1 (en) * 2003-01-28 2005-04-26 Sprint Communications Company L.P. Alarm facilitator and method for analyzing computer hardware alarms
US8254372B2 (en) 2003-02-21 2012-08-28 Genband Us Llc Data communication apparatus and method
US20040165580A1 (en) * 2003-02-25 2004-08-26 Stillman Scott Traynham Checking of broadband network components
US7756105B1 (en) * 2003-02-28 2010-07-13 Occam Networks On-hook signal detector
US20040199631A1 (en) * 2003-03-21 2004-10-07 Hitachi, Ltd. Ubiquitous information utilities and services for convention center
US20040252706A1 (en) * 2003-04-01 2004-12-16 Siemens Aktiengesellschaft Method and systems for non-call associated signaling in a multi-protocol telecommunications environment
US20060094472A1 (en) * 2003-04-03 2006-05-04 Core Mobility, Inc. Intelligent codec selection to optimize audio transmission in wireless communications
US8571584B1 (en) 2003-04-03 2013-10-29 Smith Micro Software, Inc. Delivery of voice data from multimedia messaging service messages
US20040218613A1 (en) * 2003-04-10 2004-11-04 Fortman Peter A. Communicating diagnostic information of an active modem session to an online service
US7428234B2 (en) 2003-04-28 2008-09-23 At&T Intellectual Property Ii, L.P. Voice-over-IP hybrid digital loop carrier
US20040223497A1 (en) * 2003-05-08 2004-11-11 Onvoy Inc. Communications network with converged services
US7512683B2 (en) * 2003-05-15 2009-03-31 At&T Intellectual Property I, L.P. Systems, methods and computer program products for managing quality of service, session, authentication and/or bandwidth allocation in a regional/access network (RAN)
US7684432B2 (en) * 2003-05-15 2010-03-23 At&T Intellectual Property I, L.P. Methods of providing data services over data networks and related data networks, data service providers, routing gateways and computer program products
US7848229B2 (en) * 2003-05-16 2010-12-07 Siemens Enterprise Communications, Inc. System and method for virtual channel selection in IP telephony systems
JP2004349802A (ja) * 2003-05-20 2004-12-09 Sharp Corp Ｉｐ電話装置
US8437368B2 (en) * 2003-06-04 2013-05-07 Nokia Corporation System and method for handing over a call from a packet-switched network to a circuit-switched network
JP3984929B2 (ja) * 2003-06-11 2007-10-03 Ｎｅｃインフロンティア株式会社 ＶｏＩＰシステム、ＶｏＩＰサーバ、及びマルチキャストパケット通信方法
US7440441B2 (en) * 2003-06-16 2008-10-21 Redknee Inc. Method and system for Multimedia Messaging Service (MMS) rating and billing
US7873347B2 (en) * 2003-06-19 2011-01-18 Redknee Inc. Method for implementing a Wireless Local Area Network (WLAN) gateway system
US20050008024A1 (en) * 2003-06-27 2005-01-13 Marconi Communications, Inc. Gateway and method
US9160714B2 (en) * 2003-06-30 2015-10-13 Telefonaktiebolaget L M Ericsson (Publ) Using tunneling to enhance remote LAN connectivity
DE10329877A1 (de) * 2003-07-02 2005-01-27 Siemens Ag Verfahren zum Betrieb eines Sprach-Endgerätes an einer abgesetzten Nebenstellenanlage, Kommunikationsanordnung und Sprach-Endgerät
NO319205B1 (no) * 2003-07-07 2005-06-27 Tandberg Telecom As Automatisk samtaleruting
US8139585B1 (en) * 2003-07-10 2012-03-20 Sprint Spectrum L.P. Method and system for controlling sessions from a subscriber terminal
US8503658B2 (en) * 2003-07-14 2013-08-06 Cisco Technology, Inc. Call notification with rich caller identification
US7293291B2 (en) 2003-07-18 2007-11-06 Sbc Knowledge Ventures, L.P. System and method for detecting computer port inactivity
US7412541B1 (en) * 2003-07-18 2008-08-12 Core Mobility, Inc. Tokenized compression of session initiation protocol data
US7729339B2 (en) * 2003-07-31 2010-06-01 Alcatel-Lucent Usa Inc. Audio watermarking for call identification in a telecommunications network
US7620034B1 (en) * 2003-08-01 2009-11-17 At&T Mobility Ii Llc Systems and methods for providing service migration between first and second cellular technologies
US8238905B2 (en) * 2003-08-05 2012-08-07 Roamware, Inc. Predictive intelligence
US8583109B2 (en) 2005-05-09 2013-11-12 Roamware, Inc. Method and system for exchanging NRTRDE files between a visited network and a home network in real time
US20050141431A1 (en) 2003-08-06 2005-06-30 Caveney Jack E. Network managed device installation and provisioning technique
WO2005018266A1 (ja) * 2003-08-13 2005-02-24 Matsushita Electric Industrial Co., Ltd. 基地局装置及びその送信方法
US7720095B2 (en) * 2003-08-27 2010-05-18 Fortinet, Inc. Heterogeneous media packet bridging
US7734282B2 (en) * 2003-08-28 2010-06-08 Qwest Communications International Inc System and method for provisioning customer premises equipment
DE50302405D1 (de) * 2003-09-02 2006-04-20 Siemens Ag Multimediale Videotelephonie
US7313231B2 (en) * 2003-09-02 2007-12-25 At&T Bls Intellectual Property, Inc. Methods, apparatus and computer program products for routing phone calls to a PSTN or a packet switched network based on called number
US7593414B2 (en) * 2003-09-04 2009-09-22 At&T Intellectual Property I, L.P. Enhanced CSU/DSU (channel service unit/data service unit) for frame relay over DSL
US7548980B2 (en) * 2003-09-04 2009-06-16 At&T Intellectual Property I, L.P. Enhanced network management system
US11736311B2 (en) 2003-09-05 2023-08-22 Comcast Cable Communications, Llc Gateway for transporting out-of-band messaging signals
CA2536106C (en) * 2003-09-05 2015-03-24 Comcast Cable Holdings, Llc Method and system for out-of-band messaging between customer premises equipment and a cable modem termination station
US20050052996A1 (en) * 2003-09-09 2005-03-10 Lucent Technologies Inc. Method and apparatus for management of voice-over IP communications
US7885208B2 (en) * 2003-09-11 2011-02-08 Nokia Corporation IP-based services for circuit-switched networks
US8520511B2 (en) * 2003-09-11 2013-08-27 Qualcomm Incorporated Automatic handling of incoming communications at a wireless device
US20090286515A1 (en) * 2003-09-12 2009-11-19 Core Mobility, Inc. Messaging systems and methods
US8924464B2 (en) 2003-09-19 2014-12-30 Polycom, Inc. Method and system for improving establishing of a multimedia session
DE10345017A1 (de) * 2003-09-23 2005-04-14 Deutsche Telekom Ag Verfahren und Vorrichtung zur Adressierbarkeit von Personen für Sprachkommunikation hinter beliebigen verbindungsorientierten Anschlussarten
US7460652B2 (en) 2003-09-26 2008-12-02 At&T Intellectual Property I, L.P. VoiceXML and rule engine based switchboard for interactive voice response (IVR) services
US8750289B2 (en) * 2003-10-01 2014-06-10 Itxc Ip Holdings S.A.R.L. Call setup using voice over the internet protocol (VoIP)
US20070223408A1 (en) * 2003-10-06 2007-09-27 Broadbeam Corporation Method and Apparatus for Intelligent Seamless Network Switching
US7475003B1 (en) * 2003-10-09 2009-01-06 Cisco Technology, Inc. Method and apparatus for initiating call analysis using an internet protocol phone
US7636805B2 (en) * 2003-10-20 2009-12-22 Logitech Europe S.A. Method and apparatus for communicating data between two hosts
US7886057B2 (en) * 2003-10-20 2011-02-08 Logitech Europe S.A. Method and apparatus for communicating data between two hosts
EP1528774A1 (en) * 2003-10-30 2005-05-04 Alcatel Method and system of providing lawful interception of calls
KR100617291B1 (ko) * 2003-11-05 2006-08-30 한국전자통신연구원 Ｉｐ와 레이블 교환의 혼합형 데이터를 전달하는 다중 프로토콜 레이블 교환 장치 및 그 방법
US20050105559A1 (en) * 2003-11-14 2005-05-19 Santera Systems, Inc. Methods and systems for providing transport of media gateway control commands using high-level datalink control (HDLC) protocol
US20050114490A1 (en) * 2003-11-20 2005-05-26 Nec Laboratories America, Inc. Distributed virtual network access system and method
US7729267B2 (en) 2003-11-26 2010-06-01 Cisco Technology, Inc. Method and apparatus for analyzing a media path in a packet switched network
US7519006B1 (en) 2003-11-26 2009-04-14 Cisco Technology, Inc. Method and apparatus for measuring one-way delay at arbitrary points in network
JP2007513578A (ja) * 2003-12-01 2007-05-24 インターデイジタル テクノロジー コーポレーション ユーザ手動のハンドオフに基づく、セッション開始プロトコルＳＩＰ（ＳｅｓｓｉｏｎＩｎｉｔｉａｔｉｏｎＰｒｏｔｏｃｏｌ）
US20050125559A1 (en) * 2003-12-02 2005-06-09 Mutha Kailash K. Employment of one or more identifiers of one or more communication devices to determine one or more internet protocol addresses
KR100560749B1 (ko) * 2003-12-03 2006-03-13 삼성전자주식회사 차세대 네트워크의 단대단 망관리를 위한 통합 이엠에스및 그 망관리 방법
CN1555164B (zh) * 2003-12-25 2010-09-29 中兴通讯股份有限公司 路由服务装置及应用该装置实现呼叫路由的方法和系统
US7460517B2 (en) * 2003-12-29 2008-12-02 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for routing traffic between nodes in a network that are connected by redundant links
US7739374B1 (en) 2003-12-30 2010-06-15 Sap Ag System and method for configuring tracing and logging functions
US7493624B1 (en) 2003-12-30 2009-02-17 Sap Ag Management architecture and method employed within a clustered node configuration
US7941521B1 (en) 2003-12-30 2011-05-10 Sap Ag Multi-service management architecture employed within a clustered node configuration
US6929507B2 (en) * 2003-12-30 2005-08-16 Huang Liang Precision Enterprise Co., Ltd. Coaxial connector structure
US7475401B1 (en) 2003-12-30 2009-01-06 Sap Ag Filtered unified logging service
US7725572B1 (en) 2003-12-30 2010-05-25 Sap Ag Notification architecture and method employed within a clustered node configuration
US8166152B1 (en) 2003-12-30 2012-04-24 Sap Ag Architecture and method for monitoring system resources within an enterprise network
US7606893B2 (en) * 2003-12-30 2009-10-20 Sap Ag System and method for integrated logging and tracing functions in an enterprise network
US7756968B1 (en) 2003-12-30 2010-07-13 Sap Ag Method and system for employing a hierarchical monitor tree for monitoring system resources in a data processing environment
US7822826B1 (en) 2003-12-30 2010-10-26 Sap Ag Deployment of a web service
US7272209B2 (en) * 2004-01-20 2007-09-18 Sbc Knowledge Ventures, L.P. Automated DSL performance adjustment
US7356475B2 (en) * 2004-01-05 2008-04-08 Sbc Knowledge Ventures, L.P. System and method for providing access to an interactive service offering
US7653051B2 (en) * 2004-01-13 2010-01-26 Hewlett-Packard Development Company, L.P. Signaling gateway aggregation
WO2005071888A1 (en) * 2004-01-20 2005-08-04 Koninklijke Philips Electronics, N.V. Remotely controlled gateway management with security
US7362713B2 (en) 2004-01-20 2008-04-22 Sbc Knowledge Ventures, Lp. System and method for accessing digital subscriber line data
US7308101B2 (en) * 2004-01-22 2007-12-11 Cisco Technology, Inc. Method and apparatus for transporting encrypted media streams over a wide area network
US7522607B2 (en) * 2004-01-26 2009-04-21 Sprint Communications Company Lp Congestion handling in a packet communication system
US7126914B2 (en) * 2004-01-28 2006-10-24 Sbc Knowledge Ventures, Lp Digital subscriber line user capacity estimation
US7342920B2 (en) * 2004-01-28 2008-03-11 Sbc Knowledge Ventures, L.P. Voice over internet protocol (VoIP) telephone apparatus and communications systems for carrying VoIP traffic
US20060285496A1 (en) * 2004-01-28 2006-12-21 Sbc Knowledge Ventures, L.P. Digital subscriber line user capacity estimation
US7123584B2 (en) * 2004-01-28 2006-10-17 Sbc Knowledge Ventures, L.P. Digital subscriber line user capacity estimation
WO2005076582A1 (de) * 2004-01-30 2005-08-18 Combots Product Gmbh & Co.Kg Aufbau von verbindungen mit hilfe von kontaktelementen
KR100602643B1 (ko) * 2004-02-02 2006-07-19 삼성전자주식회사 브이 오 아이 피 단말의 호 백업 제공 방법 및 그 장치
US7565448B1 (en) * 2004-02-03 2009-07-21 Sprint Communications Company L.P. Network control system for a communication network
US7876775B2 (en) * 2004-02-12 2011-01-25 At&T Intellectual Property I, L.P. Connection management for data networks
CN1658547B (zh) * 2004-02-16 2010-08-18 华为技术有限公司 密钥分发方法
US20050195802A1 (en) * 2004-02-20 2005-09-08 Klein Mark D. Dynamically routing telephone calls
US7395051B2 (en) 2004-02-23 2008-07-01 Research In Motion Limited Cellular communications system for providing non-real time subscription data and related methods
WO2005084128A2 (en) * 2004-03-04 2005-09-15 Outsmart Ltd. Integration of packet and cellular telephone networks
WO2005089147A2 (en) * 2004-03-11 2005-09-29 Transnexus, Inc. Method and system for routing calls over a packet switched computer network
US10142392B2 (en) 2007-01-24 2018-11-27 Icontrol Networks, Inc. Methods and systems for improved system performance
US11368429B2 (en) 2004-03-16 2022-06-21 Icontrol Networks, Inc. Premises management configuration and control
US11244545B2 (en) 2004-03-16 2022-02-08 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
EP1738540B1 (en) 2004-03-16 2017-10-04 Icontrol Networks, Inc. Premises management system
US7711796B2 (en) 2006-06-12 2010-05-04 Icontrol Networks, Inc. Gateway registry methods and systems
US9531593B2 (en) 2007-06-12 2016-12-27 Icontrol Networks, Inc. Takeover processes in security network integrated with premise security system
US20160065414A1 (en) 2013-06-27 2016-03-03 Ken Sundermeyer Control system user interface
US11277465B2 (en) 2004-03-16 2022-03-15 Icontrol Networks, Inc. Generating risk profile using data of home monitoring and security system
US11113950B2 (en) 2005-03-16 2021-09-07 Icontrol Networks, Inc. Gateway integrated with premises security system
US11316958B2 (en) 2008-08-11 2022-04-26 Icontrol Networks, Inc. Virtual device systems and methods
US9141276B2 (en) 2005-03-16 2015-09-22 Icontrol Networks, Inc. Integrated interface for mobile device
US11582065B2 (en) 2007-06-12 2023-02-14 Icontrol Networks, Inc. Systems and methods for device communication
US11489812B2 (en) 2004-03-16 2022-11-01 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US11159484B2 (en) 2004-03-16 2021-10-26 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US11368327B2 (en) 2008-08-11 2022-06-21 Icontrol Networks, Inc. Integrated cloud system for premises automation
US11343380B2 (en) 2004-03-16 2022-05-24 Icontrol Networks, Inc. Premises system automation
US20090077623A1 (en) 2005-03-16 2009-03-19 Marc Baum Security Network Integrating Security System and Network Devices
US11811845B2 (en) 2004-03-16 2023-11-07 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US10522026B2 (en) 2008-08-11 2019-12-31 Icontrol Networks, Inc. Automation system user interface with three-dimensional display
US11201755B2 (en) 2004-03-16 2021-12-14 Icontrol Networks, Inc. Premises system management using status signal
US10237237B2 (en) 2007-06-12 2019-03-19 Icontrol Networks, Inc. Communication protocols in integrated systems
US11916870B2 (en) 2004-03-16 2024-02-27 Icontrol Networks, Inc. Gateway registry methods and systems
US10156959B2 (en) 2005-03-16 2018-12-18 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
US11677577B2 (en) 2004-03-16 2023-06-13 Icontrol Networks, Inc. Premises system management using status signal
US10339791B2 (en) 2007-06-12 2019-07-02 Icontrol Networks, Inc. Security network integrated with premise security system
US9729342B2 (en) 2010-12-20 2017-08-08 Icontrol Networks, Inc. Defining and implementing sensor triggered response rules
US10721087B2 (en) 2005-03-16 2020-07-21 Icontrol Networks, Inc. Method for networked touchscreen with integrated interfaces
US7856493B1 (en) * 2004-03-17 2010-12-21 Cisco Technology, Inc. Method and apparatus providing device-initiated network management
US7804789B2 (en) 2004-03-18 2010-09-28 Tekelec Methods, systems, and computer program products for organizing, managing, and selectively distributing routing information in a signaling message routing node
US8027265B2 (en) 2004-03-19 2011-09-27 Genband Us Llc Providing a capability list of a predefined format in a communications network
US7990865B2 (en) 2004-03-19 2011-08-02 Genband Us Llc Communicating processing capabilities along a communications path
US7721266B2 (en) * 2004-03-26 2010-05-18 Sap Ag Unified logging service with a logging formatter
US7526550B2 (en) * 2004-03-26 2009-04-28 Sap Ag Unified logging service with a log viewer
GB2413454B (en) * 2004-04-19 2006-12-27 Intelli Call Ltd Providing information relating to a telephone call
US7570599B2 (en) * 2004-04-21 2009-08-04 At&T Intellectual Property I, Llp. Adaptively applying a target noise margin to a digital subscriber line (DSL) loop for DSL data rate establishment
US20050238000A1 (en) * 2004-04-23 2005-10-27 Pollock Graham S System and method for computing demand placed on a packet-switched network by streaming media communication
US9014355B2 (en) 2004-04-27 2015-04-21 Value-Added Communications, Inc. Telecommunication revenue management system
US8929524B2 (en) 2004-04-27 2015-01-06 Value-Added Communications, Inc. System and method for determining and associating tariff rates for institutional calls
US20060115057A1 (en) * 2004-04-30 2006-06-01 Donald Laliberte Method and system for control of a voice/data communications device using a radio frequency component
US7783013B2 (en) 2004-04-30 2010-08-24 At&T Intellectual Property I, L.P. Method and system for routing emergency communications
US7388906B2 (en) * 2004-05-03 2008-06-17 Sbc Knowledge Ventures, L.P. Method for detecting bridged taps on telephony cable
US7991889B2 (en) * 2004-05-07 2011-08-02 Alcatel-Lucent Usa Inc. Apparatus and method for managing networks having resources having reduced, nonzero functionality
US7480546B2 (en) * 2004-05-12 2009-01-20 General Motors Corporation System and method for providing language translation in a vehicle telematics device
US20050273464A1 (en) * 2004-05-21 2005-12-08 Brown Deborah J Method and apparatus for administering configuration information in a private branch exchange switch
GB2414622A (en) * 2004-05-26 2005-11-30 Siemens Ag Switching from an established media path to a new media path in a Packet based network.
US7580405B2 (en) 2004-05-27 2009-08-25 At&T Intellectual Property I, L. P. Method and system for routing emergency data communications
TWI244855B (en) * 2004-05-28 2005-12-01 Octtel Comm Co Ltd Method of communication protocol for voice over Internet protocol (VoIP) gateways
US7203291B2 (en) * 2004-06-01 2007-04-10 Agilent Technologies, Inc. Apparatus and method for generating call information data for calls on long duration
US9462122B1 (en) 2004-06-07 2016-10-04 Aol Inc. Selective call routing and blocking
US7760707B1 (en) 2004-06-07 2010-07-20 Aol Inc. Voice over internet protocol application development framework
US20050281398A1 (en) * 2004-06-15 2005-12-22 Starling Gerald A Methods, systems, and storage mediums for providing an optimized call routing service
JP4189360B2 (ja) * 2004-06-30 2008-12-03 株式会社東芝 電話交換装置及びネットワーク電話システム
US20060002403A1 (en) * 2004-06-30 2006-01-05 Glenayre Electronics, Inc. Distributed IP architecture for telecommunications system
JP2006033124A (ja) * 2004-07-13 2006-02-02 Fujitsu Ltd トンネル障害通知装置および方法
KR20060005830A (ko) * 2004-07-14 2006-01-18 삼성전자주식회사 통합 슬롯이 탑재된 인쇄 회로 기판
ATE552708T1 (de) * 2004-07-16 2012-04-15 Bridgeport Networks Präsenzdetektion und weiterreichung für die zellulare und internet-protokoll-telefonie
US20060018448A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Routing telephone calls via a data network
US20060018449A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Telephone call routing
US20060018310A1 (en) * 2004-07-20 2006-01-26 Qwest Communications International Inc. Data network call routing
US8184793B2 (en) 2004-07-20 2012-05-22 Qwest Communications International Inc. Multi-line telephone calling
US7936861B2 (en) 2004-07-23 2011-05-03 At&T Intellectual Property I, L.P. Announcement system and method of use
US8165281B2 (en) 2004-07-28 2012-04-24 At&T Intellectual Property I, L.P. Method and system for mapping caller information to call center agent transactions
US7684374B2 (en) * 2004-07-28 2010-03-23 Broadcom Corporation Handling of multimedia call sessions and attachments using multi-network simulcasting
US20060026108A1 (en) * 2004-07-30 2006-02-02 Paul Wilson Voice/data financial transaction monitoring methods and systems
US20060026099A1 (en) * 2004-07-30 2006-02-02 Barry Danz Voice/data financial transaction communications device
US7580837B2 (en) 2004-08-12 2009-08-25 At&T Intellectual Property I, L.P. System and method for targeted tuning module of a speech recognition system
US20060029195A1 (en) * 2004-08-18 2006-02-09 Karen Mullis Methods, apparatus and computer program products for message notification in a voice over internet protocol communication system
US7602898B2 (en) 2004-08-18 2009-10-13 At&T Intellectual Property I, L.P. System and method for providing computer assisted user support
US7720827B2 (en) * 2004-08-24 2010-05-18 Alcatel-Lucent Usa Inc. Network meta-data libraries and related methods
US11468128B1 (en) 2006-10-20 2022-10-11 Richard Paiz Search engine optimizer
US10959090B1 (en) 2004-08-25 2021-03-23 Richard Paiz Personal search results
US7411975B1 (en) 2004-08-26 2008-08-12 Juniper Networks, Inc. Multimedia over internet protocol border controller for network-based virtual private networks
KR100594018B1 (ko) * 2004-09-01 2006-06-30 삼성전자주식회사 휴대용 단말기에서 선불카드를 이용한 통화서비스 실행방법
EP1794605B1 (en) * 2004-09-14 2015-04-29 Genband US LLC Object-based operation and maintenance (OAM) systems and related methods and computer program products
US7830864B2 (en) * 2004-09-18 2010-11-09 Genband Us Llc Apparatus and methods for per-session switching for multiple wireline and wireless data types
US7729346B2 (en) 2004-09-18 2010-06-01 Genband Inc. UMTS call handling methods and apparatus
US20060062375A1 (en) * 2004-09-23 2006-03-23 Sbc Knowledge Ventures, L.P. System and method for providing product offers at a call center
US7499419B2 (en) * 2004-09-24 2009-03-03 Fortinet, Inc. Scalable IP-services enabled multicast forwarding with efficient resource utilization
US7827307B2 (en) * 2004-09-29 2010-11-02 Cisco Technology, Inc. Method for fast switchover and recovery of a media gateway
US7543064B2 (en) * 2004-09-30 2009-06-02 Logitech Europe S.A. Multiplayer peer-to-peer connection across firewalls and network address translators using a single local port on the local host
US7197130B2 (en) 2004-10-05 2007-03-27 Sbc Knowledge Ventures, L.P. Dynamic load balancing between multiple locations with different telephony system
US7542761B2 (en) * 2004-10-06 2009-06-02 At&T Mobility Ii Llc Voice quality on a communication link based on customer feedback
US7924999B1 (en) * 2004-10-13 2011-04-12 Sprint Communications Company L.P. Using remote processors to generate routing information to terminate calls to a customer premises
US7760713B2 (en) * 2004-10-15 2010-07-20 Tran Bao Q Camera-phone barcode scanning support
US20060081703A1 (en) * 2004-10-15 2006-04-20 Tran Bao Q Systems and methods for providing virtual reception services
EP1650969A1 (en) * 2004-10-25 2006-04-26 Alcatel Method for establishing an IP video-conference using a telephone network for voice transmission
US7668889B2 (en) 2004-10-27 2010-02-23 At&T Intellectual Property I, Lp Method and system to combine keyword and natural language search results
US7643468B1 (en) 2004-10-28 2010-01-05 Cisco Technology, Inc. Data-center network architecture
US7657005B2 (en) 2004-11-02 2010-02-02 At&T Intellectual Property I, L.P. System and method for identifying telephone callers
US7613207B2 (en) * 2004-11-03 2009-11-03 Cisco Technology, Inc. Securing telephony communications between remote and enterprise endpoints
JP4592551B2 (ja) * 2004-11-10 2010-12-01 シャープ株式会社 通信装置
US8072909B2 (en) * 2004-11-15 2011-12-06 Applied Voice & Speech Technologies, Inc. Apparatus and method for notification of a party in a telephone conference
CN100466653C (zh) * 2004-11-18 2009-03-04 英保达股份有限公司 网络语音电话系统中建立通讯进行数据传送与接收的方法
US7724889B2 (en) 2004-11-29 2010-05-25 At&T Intellectual Property I, L.P. System and method for utilizing confidence levels in automated call routing
US20060115068A1 (en) * 2004-11-30 2006-06-01 Smart-Ss7 Ltd. Virtual service switching function
US7545920B2 (en) * 2004-11-30 2009-06-09 Sbc Knowledge Ventures, L.P. Call reporting
US7715429B2 (en) * 2004-12-06 2010-05-11 Hewlett-Packard Development Company, L.P. Interconnect system for supply chain management of virtual private network services
US7864942B2 (en) 2004-12-06 2011-01-04 At&T Intellectual Property I, L.P. System and method for routing calls
US7242751B2 (en) 2004-12-06 2007-07-10 Sbc Knowledge Ventures, L.P. System and method for speech recognition-enabled automatic call routing
US20060126808A1 (en) * 2004-12-13 2006-06-15 Sbc Knowledge Ventures, L.P. System and method for measurement of call deflection
GB2435587B (en) * 2004-12-13 2008-10-01 Transnexus Inc Method and system for securely authorizing VOIP interconnections between anonymous peers of VOIP networks
US8238329B2 (en) 2005-12-13 2012-08-07 Transnexus, Inc. Method and system for securely authorizing VoIP interconnections between anonymous peers of VoIP networks
US8675857B1 (en) * 2004-12-22 2014-03-18 At&T Intellectual Property Ii, L.P. Method and apparatus for enabling customized and selectable network announcements
US7626980B1 (en) * 2004-12-22 2009-12-01 At&T Corp. Method and apparatus for enabling communications assistance for law enforcement act services
US7881712B1 (en) * 2004-12-23 2011-02-01 Cisco Technology, Inc. Generating and signaling tones in a communications network
DE102004063298B4 (de) * 2004-12-29 2006-11-16 Infineon Technologies Ag Verfahren zum rechnergestützten Verwalten von Kommunikationsrechten zum Kommunizieren mittels mehrerer unterschiedlicher Kommunikationsmedien in einer Telekommunikations-Konferenz mit mehreren Telekommunikations-Einrichtungen
US7593390B2 (en) 2004-12-30 2009-09-22 Intel Corporation Distributed voice network
US20060149815A1 (en) * 2004-12-30 2006-07-06 Sean Spradling Managing participants in an integrated web/audio conference
US7788226B2 (en) * 2004-12-30 2010-08-31 Sap Ag Monitoring availability of applications
US7751551B2 (en) 2005-01-10 2010-07-06 At&T Intellectual Property I, L.P. System and method for speech-enabled call routing
US7627096B2 (en) 2005-01-14 2009-12-01 At&T Intellectual Property I, L.P. System and method for independently recognizing and selecting actions and objects in a speech recognition system
US7450698B2 (en) 2005-01-14 2008-11-11 At&T Intellectual Property 1, L.P. System and method of utilizing a hybrid semantic model for speech recognition
US7688742B2 (en) * 2005-01-14 2010-03-30 Alcatel Lucent System and method for monitoring end nodes using ethernet connectivity fault management (CFM) in an access network
US8351419B2 (en) 2005-01-19 2013-01-08 Qualcomm Iskoot, Inc. Local access to a mobile network
US8856359B2 (en) * 2005-06-29 2014-10-07 Qualcomm Connected Experiences, Inc. Caller-callee association of a plurality of networked devices
US8756328B2 (en) * 2005-01-19 2014-06-17 Qualcomm Connected Experiences, Inc. Caller-callee association of a plurality of networked devices with direct dial through thin client
US8718258B2 (en) * 2005-01-24 2014-05-06 Sprint Communication Company L.P. System and method for jurisdictional routing
US7508810B2 (en) 2005-01-31 2009-03-24 Airbiquity Inc. Voice channel control of wireless packet data communications
US7627109B2 (en) 2005-02-04 2009-12-01 At&T Intellectual Property I, Lp Call center system for multiple transaction selections
US20060177029A1 (en) * 2005-02-10 2006-08-10 Outsmart Ltd. Virtual multi-line telephone service
US20060188087A1 (en) * 2005-02-18 2006-08-24 Sbc Knowledge Ventures, Lp System and method for caller-controlled music on-hold
WO2006089273A2 (en) * 2005-02-18 2006-08-24 Santera Systems, Inc. Methods, systems, and computer program products for providing time division multiplexed(tdm) terminating service in a packet network
US8130936B2 (en) * 2005-03-03 2012-03-06 At&T Intellectual Property I, L.P. System and method for on hold caller-controlled activities and entertainment
US20110128378A1 (en) * 2005-03-16 2011-06-02 Reza Raji Modular Electronic Display Platform
US20120324566A1 (en) 2005-03-16 2012-12-20 Marc Baum Takeover Processes In Security Network Integrated With Premise Security System
US11700142B2 (en) 2005-03-16 2023-07-11 Icontrol Networks, Inc. Security network integrating security system and network devices
US11615697B2 (en) 2005-03-16 2023-03-28 Icontrol Networks, Inc. Premise management systems and methods
US11496568B2 (en) 2005-03-16 2022-11-08 Icontrol Networks, Inc. Security system with networked touchscreen
US20170180198A1 (en) 2008-08-11 2017-06-22 Marc Baum Forming a security network including integrated security system components
US10999254B2 (en) 2005-03-16 2021-05-04 Icontrol Networks, Inc. System for data routing in networks
US20060209828A1 (en) * 2005-03-18 2006-09-21 The Boeing Company Interoperable communications architecture
US7499395B2 (en) * 2005-03-18 2009-03-03 Cisco Technology, Inc. BFD rate-limiting and automatic session activation
US7933399B2 (en) * 2005-03-22 2011-04-26 At&T Intellectual Property I, L.P. System and method for utilizing virtual agents in an interactive voice response application
US8223954B2 (en) 2005-03-22 2012-07-17 At&T Intellectual Property I, L.P. System and method for automating customer relations in a communications environment
US7738468B2 (en) * 2005-03-22 2010-06-15 Logitech Europe S.A. Method and apparatus for packet traversal of a network address translation device
US8649498B1 (en) * 2005-03-25 2014-02-11 Cisco Technology, Inc. Network architecture for hosting voice services
US8134999B2 (en) * 2005-04-05 2012-03-13 Cisco Technology, Inc. Generic provisioning of voice over internet protocol (VoIP)
US8825108B2 (en) 2005-04-06 2014-09-02 Qwest Communications International Inc. Call handling on dual-mode wireless handsets
US9363384B2 (en) 2005-04-06 2016-06-07 Qwest Communications International Inc. Systems for delivering calls on dual-mode wireless handsets
US9363370B2 (en) * 2005-04-06 2016-06-07 Qwest Communications International Inc. Methods of delivering calls on dual-mode wireless handsets
US8989813B2 (en) 2005-04-06 2015-03-24 Qwest Communications International Inc. Handset registration in a dual-mode environment
US8265255B1 (en) * 2005-04-07 2012-09-11 Marvell International Ltd. End-to-end session without signaling protocol
US11258531B2 (en) * 2005-04-07 2022-02-22 Opanga Networks, Inc. System and method for peak flow detection in a communication network
US8228926B2 (en) * 2005-04-12 2012-07-24 Genband Us Llc Dynamic loading for signaling variants
US7583660B2 (en) * 2005-04-19 2009-09-01 At&T Corp. Method and apparatus for enabling peer-to-peer communication between endpoints on a per call basis
US7810075B2 (en) * 2005-04-29 2010-10-05 Sap Ag Common trace files
US20060245557A1 (en) * 2005-05-02 2006-11-02 Sbc Knowledge Ventures Lp Configurable interactive voice response messaging control and monitoring system and method
US7764779B2 (en) * 2005-05-06 2010-07-27 Aspect Software, Inc. SIP ACD multi-tenant mechanism that facilitates multiple levels of partitions or tenants
BRPI0608800A2 (pt) * 2005-05-09 2010-01-26 Roamware Inc sistema e método para gerar informações de assinante (mo-csi) de aplicações personalizadas de origem móvel para lógica avançada de rede móvel (camel) de um roamer entrante e produto de programa de computador
US7636432B2 (en) 2005-05-13 2009-12-22 At&T Intellectual Property I, L.P. System and method of determining call treatment of repeat calls
CN100372304C (zh) * 2005-05-15 2008-02-27 华为技术有限公司 基于软交换设备感知业务的wimax动态qos实现方法
US20090103519A1 (en) * 2005-05-18 2009-04-23 Siemens Aktiengesellschaft Method and Computer Product for Switching Subsequent Messages With Higher Priority Than Invite Messages in a Softswitch
JP2006325003A (ja) * 2005-05-19 2006-11-30 Toshiba Corp 交換システム、電話交換装置及び音声メッセージ通知方法
US7751855B2 (en) * 2005-05-20 2010-07-06 Alcatel-Lucent Usa Inc. Private routing control numbers
US7370060B2 (en) * 2005-05-24 2008-05-06 Microsoft Corporation System and method for user edit merging with preservation of unrepresented data
EP1729477B1 (de) * 2005-05-30 2011-08-03 Siemens Enterprise Communications GmbH & Co. KG Verfahren zum Aufbauen einer Verbindung über eine Kommunikationseinrichtung zu einer Endeinrichtung, sowie Endeinrichtung und Kommunikationseinrichtung zur Durchführung des Verfahrens
US7657020B2 (en) 2005-06-03 2010-02-02 At&T Intellectual Property I, Lp Call routing system and method of using the same
US8005204B2 (en) 2005-06-03 2011-08-23 At&T Intellectual Property I, L.P. Call routing system and method of using the same
US8155120B2 (en) * 2005-06-09 2012-04-10 Whirlpool Corporation Software architecture system and method for discovering components within an appliance using fuctionality identifiers
US7558213B2 (en) 2005-06-15 2009-07-07 AT&T Intellectual Property I, LLP Methods and apparatus to determine digital subscriber line configuration parameters
US8503641B2 (en) 2005-07-01 2013-08-06 At&T Intellectual Property I, L.P. System and method of automated order status retrieval
US7613807B2 (en) * 2005-07-04 2009-11-03 Hewlett-Packard Development Company, L.P. System, method, and apparatus for discovering a new server connected within an automated data center
WO2007004224A1 (en) * 2005-07-05 2007-01-11 Mconfirm Ltd. Improved location based authentication system
US8175253B2 (en) * 2005-07-07 2012-05-08 At&T Intellectual Property I, L.P. System and method for automated performance monitoring for a call servicing system
US8432896B2 (en) * 2005-07-22 2013-04-30 Cisco Technology, Inc. System and method for optimizing communications between session border controllers and endpoints in a network environment
US8291469B1 (en) * 2005-08-02 2012-10-16 Sprint Communications Company L.P. Communication access provider that allows a service provider to control an access interface at a customer premise
US7889848B2 (en) * 2005-08-03 2011-02-15 At&T Intellectual Property I, L.P. Telecommunication service with pre-paid access
EP1916835B1 (en) * 2005-08-03 2017-09-20 Comsquare Co., Ltd. Call connecting device, call connecting method and call connecting program
US8737290B2 (en) * 2005-08-12 2014-05-27 Edgeaccess, Inc. Performance enhancement protocol, systems, methods and devices
US7792150B2 (en) 2005-08-19 2010-09-07 Genband Us Llc Methods, systems, and computer program products for supporting transcoder-free operation in media gateway
US20070058657A1 (en) * 2005-08-22 2007-03-15 Graham Holt System for consolidating and securing access to all out-of-band interfaces in computer, telecommunication, and networking equipment, regardless of the interface type
US8526577B2 (en) * 2005-08-25 2013-09-03 At&T Intellectual Property I, L.P. System and method to access content from a speech-enabled automated system
US20070049245A1 (en) * 2005-08-25 2007-03-01 Lipman Steve B Cellular-internet communication system and method
US20070047531A1 (en) * 2005-08-26 2007-03-01 Stmicroelectronics Asia Pacific Pte, Ltd. System and method for implementing proxy independent hunt group function in a packet based network
US8548157B2 (en) 2005-08-29 2013-10-01 At&T Intellectual Property I, L.P. System and method of managing incoming telephone calls at a call center
US7656862B2 (en) 2005-08-29 2010-02-02 At&T Intellectual Property I, L.P. Methods, systems, and devices for providing voice-call services responsive to a dialed sequence
US20070070981A1 (en) * 2005-09-27 2007-03-29 Marian Croak Method and apparatus for dynamically establishing links between IP private branch exchanges
US7978845B2 (en) * 2005-09-28 2011-07-12 Panduit Corp. Powered patch panel
US8150009B1 (en) 2005-09-29 2012-04-03 At&T Intellectual Property Ii, L.P. Method and apparatus for providing dynamic international calling rates
US8223938B2 (en) 2005-09-30 2012-07-17 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing caller identification services
US20070209054A1 (en) 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing communications services
US8804695B2 (en) * 2005-09-30 2014-08-12 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing alerts and notifications
CN100499582C (zh) * 2005-10-14 2009-06-10 华为技术有限公司 一种数据传输方法及系统
US20070116234A1 (en) * 2005-10-19 2007-05-24 Marco Schneider Methods and apparatus for preserving access information during call transfers
US7839988B2 (en) 2005-10-19 2010-11-23 At&T Intellectual Property I, L.P. Methods and apparatus for data structure driven authorization and/or routing of outdial communication services
US20070086436A1 (en) * 2005-10-19 2007-04-19 Denny Michael S Methods, apparatus and computer program products for allowing access to line groups and line group functions in a voice over internet protocol communication system
US7643472B2 (en) 2005-10-19 2010-01-05 At&T Intellectual Property I, Lp Methods and apparatus for authorizing and allocating outdial communication services
US20070086432A1 (en) * 2005-10-19 2007-04-19 Marco Schneider Methods and apparatus for automated provisioning of voice over internet protocol gateways
US7924987B2 (en) * 2005-10-19 2011-04-12 At&T Intellectual Property I., L.P. Methods, apparatus and data structures for managing distributed communication systems
US8238327B2 (en) * 2005-10-19 2012-08-07 At&T Intellectual Property I, L.P. Apparatus and methods for subscriber and enterprise assignments and resource sharing
US20070115923A1 (en) * 2005-10-19 2007-05-24 Denny Michael S Methods, apparatus and computer program products for secondary routing of calls in a voice over internet protocol communication system
US20070086433A1 (en) * 2005-10-19 2007-04-19 Cunetto Philip C Methods and apparatus for allocating shared communication resources to outdial communication services
US20070093249A1 (en) * 2005-10-21 2007-04-26 Sbc Knowledge Ventures L.P. SS7 Link failover communications over existing cellular networks
US20070091812A1 (en) * 2005-10-24 2007-04-26 Sbc Knowledge Ventures L.P. Communication system and method utilizing a satellite network
US7760861B1 (en) * 2005-10-31 2010-07-20 At&T Intellectual Property Ii, L.P. Method and apparatus for monitoring service usage in a communications network
CN1960401B (zh) * 2005-11-02 2010-08-18 华为技术有限公司 一种汇接局实现双业务交替的方法
US8953771B2 (en) * 2005-11-07 2015-02-10 Cisco Technology, Inc. Method and apparatus to provide cryptographic identity assertion for the PSTN
US20070171898A1 (en) * 2005-11-29 2007-07-26 Salva Paul D System and method for establishing universal real time protocol bridging
JP4580865B2 (ja) * 2005-11-30 2010-11-17 株式会社東芝 電話システム及びこの電話システムのチャネル捕捉方法
GB2432993A (en) * 2005-12-01 2007-06-06 Marconi Comm Ltd Combating fraud in telecommunication systems
US9008075B2 (en) * 2005-12-22 2015-04-14 Genesys Telecommunications Laboratories, Inc. System and methods for improving interaction routing performance
US7623548B2 (en) * 2005-12-22 2009-11-24 At&T Intellectual Property, I,L.P. Methods, systems, and computer program products for managing access resources in an internet protocol network
US20100177667A1 (en) * 2005-12-23 2010-07-15 Simmons Gordon S Audio conferencing with integrated access point
US7668302B1 (en) * 2005-12-28 2010-02-23 United Services Automobile Association (Usaa) System and method for reducing toll charges to a customer service center using VoIP
US7492879B1 (en) 2005-12-28 2009-02-17 United Services Automobile Association (Usaa) System and method for reducing toll charges to a customer service center using VoIP
US8085912B1 (en) 2005-12-28 2011-12-27 United Services Automobile Association System and method for reducing toll charges to a customer service center using VolP
US20070153776A1 (en) * 2005-12-29 2007-07-05 Joseph Gigo K Method and apparatus for routing internet telephone calls based upon the media types and formats or CODEC capabilities of the end points or destinations
US7797420B1 (en) * 2006-01-03 2010-09-14 Emc Corporation Method and apparatus for representing, managing and problem reporting in VoIP networks
US9990607B1 (en) 2006-01-13 2018-06-05 Wensheng Hua Balanced network and method
US7835346B2 (en) * 2006-01-17 2010-11-16 Genband Us Llc Methods, systems, and computer program products for providing transcoder free operation (TrFO) and interworking between unlicensed mobile access (UMA) and universal mobile telecommunications system (UMTS) call legs using a media gateway
US9479604B2 (en) * 2006-01-30 2016-10-25 Qualcomm Incorporated System and method for dynamic phone book and network content links in a mobile device
US8479275B1 (en) 2006-02-01 2013-07-02 Cisco Technology, Inc. Secure high-throughput data-center network employing routed firewalls
US8532096B2 (en) * 2006-02-01 2013-09-10 Cisco Technology, Inc. Local exchange routing guide information maintenance system and method
KR20070108425A (ko) 2006-02-06 2007-11-12 엘지전자 주식회사 ＶＣＣ에서의 ｃａｌｌ 수행 방법, 단말 및 ＶＣＣ어플리케이션 서버
US7684547B2 (en) * 2006-02-07 2010-03-23 International Business Machines Corporation Wiretapping VoIP calls
US8144644B1 (en) 2006-02-07 2012-03-27 Sprint Spectrum L.P. Network-side setup of a packet-data communication session on behalf of a mobile station, followed by transfer of the communication session to the mobile station
CA2640694A1 (en) * 2006-02-13 2007-08-23 Outsmart Ltd. Portable soft phone
US7701971B2 (en) 2006-02-27 2010-04-20 Cisco Technology, Inc. System and method for providing a compatibility feature in a session initiation protocol (SIP) environment
US7685223B1 (en) 2006-03-02 2010-03-23 Cisco Technology, Inc. Network-wide service discovery
GB0604537D0 (en) * 2006-03-07 2006-04-12 Ghost Telecom Ltd Method and apparatus of interfacing and connecting a wireless device(s) and specific application server(s) for location update(s), in-and out-going call(s)...
CN100583918C (zh) * 2006-03-16 2010-01-20 华为技术有限公司 用于交换网络的业务中断的安全保护方法及其装置
US20070223463A1 (en) * 2006-03-23 2007-09-27 Weinberger Mark B Method of identity-based intelligent routing, storage, and integration of multiple modes of communication among multiple devices linked through a client/server interaction
US8681775B2 (en) * 2006-04-03 2014-03-25 At&T Intellectual Property I, Lp Switchable voice source network interface device module
US9542642B2 (en) 2006-04-06 2017-01-10 Samuel F. Wood Packet data neural network system and method
US7796511B2 (en) * 2006-04-06 2010-09-14 Wood Samuel F Self-routed layer 4 packet network system and method
US7729489B2 (en) * 2006-04-12 2010-06-01 Cisco Technology, Inc. Transferring a communications exchange
CA2586305A1 (en) * 2006-04-25 2007-10-25 Tektronix International Sales Gmbh System and method of remote testing in loopback mode using mgcp/ncs
US7756134B2 (en) * 2006-05-02 2010-07-13 Harris Corporation Systems and methods for close queuing to support quality of service
US8619636B1 (en) * 2006-05-03 2013-12-31 At&T Mobility Ii Llc Methods and systems for creating optimized transmission paths for VoIP conference calls
US20080146204A1 (en) * 2006-05-05 2008-06-19 Ip Unity Glenayre, Inc. Enhanced services for mobile content on demand
JP5040171B2 (ja) * 2006-05-18 2012-10-03 日本電気株式会社 情報処理装置及び接続制御方法並びにプログラム
US7894509B2 (en) * 2006-05-18 2011-02-22 Harris Corporation Method and system for functional redundancy based quality of service
US20070286351A1 (en) * 2006-05-23 2007-12-13 Cisco Technology, Inc. Method and System for Adaptive Media Quality Monitoring
US8224322B2 (en) 2006-06-12 2012-07-17 Lemko Corporation Roaming mobile subscriber registration in a distributed mobile architecture
US10079839B1 (en) 2007-06-12 2018-09-18 Icontrol Networks, Inc. Activation of gateway device
US7856012B2 (en) * 2006-06-16 2010-12-21 Harris Corporation System and methods for generic data transparent rules to support quality of service
US8064464B2 (en) * 2006-06-16 2011-11-22 Harris Corporation Method and system for inbound content-based QoS
US8516153B2 (en) * 2006-06-16 2013-08-20 Harris Corporation Method and system for network-independent QoS
US7990860B2 (en) * 2006-06-16 2011-08-02 Harris Corporation Method and system for rule-based sequencing for QoS
US20070291656A1 (en) * 2006-06-16 2007-12-20 Harris Corporation Method and system for outbound content-based QoS
US20070291655A1 (en) * 2006-06-19 2007-12-20 Avaya Technology Llc Waveform Quality Feedback for Internet Protocol Traffic
US7916626B2 (en) * 2006-06-19 2011-03-29 Harris Corporation Method and system for fault-tolerant quality of service
US20070291765A1 (en) * 2006-06-20 2007-12-20 Harris Corporation Systems and methods for dynamic mode-driven link management
US8730981B2 (en) 2006-06-20 2014-05-20 Harris Corporation Method and system for compression based quality of service
US7769028B2 (en) * 2006-06-21 2010-08-03 Harris Corporation Systems and methods for adaptive throughput management for event-driven message-based data
US8289965B2 (en) 2006-10-19 2012-10-16 Embarq Holdings Company, Llc System and method for establishing a communications session with an end-user based on the state of a network connection
US8717911B2 (en) 2006-06-30 2014-05-06 Centurylink Intellectual Property Llc System and method for collecting network performance information
US7948909B2 (en) 2006-06-30 2011-05-24 Embarq Holdings Company, Llc System and method for resetting counters counting network performance information at network communications devices on a packet network
US8477614B2 (en) 2006-06-30 2013-07-02 Centurylink Intellectual Property Llc System and method for routing calls if potential call paths are impaired or congested
US9094257B2 (en) 2006-06-30 2015-07-28 Centurylink Intellectual Property Llc System and method for selecting a content delivery network
US8000318B2 (en) 2006-06-30 2011-08-16 Embarq Holdings Company, Llc System and method for call routing based on transmission performance of a packet network
US20080002711A1 (en) * 2006-06-30 2008-01-03 Bugenhagen Michael K System and method for access state based service options
US8488447B2 (en) 2006-06-30 2013-07-16 Centurylink Intellectual Property Llc System and method for adjusting code speed in a transmission path during call set-up due to reduced transmission performance
US8194643B2 (en) 2006-10-19 2012-06-05 Embarq Holdings Company, Llc System and method for monitoring the connection of an end-user to a remote network
KR100916544B1 (ko) * 2006-07-10 2009-09-14 삼성전자주식회사 이동통신 시스템에서 패킷 네트워크를 사용하는 홈 기지국장치 및 방법
US20080013540A1 (en) * 2006-07-11 2008-01-17 Matthew Stuart Gast System and method for selective delivery of media streams
US20080013559A1 (en) * 2006-07-14 2008-01-17 Smith Donald L Systems and methods for applying back-pressure for sequencing in quality of service
US20080025228A1 (en) * 2006-07-26 2008-01-31 Verizon Services Corp. Automated packet switch carrier health monitoring process
US7675864B2 (en) * 2006-07-26 2010-03-09 Verizon Services Corp. Automated packet switch carrier health monitoring process
US8300653B2 (en) 2006-07-31 2012-10-30 Harris Corporation Systems and methods for assured communications with quality of service
EP1892907B1 (en) * 2006-07-31 2009-04-22 Hewlett-Packard Development Company, L.P. Signalling gateway
US7809123B2 (en) 2006-08-02 2010-10-05 At&T Intellectual Property I, L.P. Method and system for determining independent authorization levels in a VPN
US8019058B2 (en) * 2006-08-08 2011-09-13 Research In Motion Limited System and method for fast, reliable setup of voicemail playback
US7808918B2 (en) 2006-08-22 2010-10-05 Embarq Holdings Company, Llc System and method for dynamically shaping network traffic
US8228791B2 (en) 2006-08-22 2012-07-24 Embarq Holdings Company, Llc System and method for routing communications between packet networks based on intercarrier agreements
US8576722B2 (en) 2006-08-22 2013-11-05 Centurylink Intellectual Property Llc System and method for modifying connectivity fault management packets
US8144587B2 (en) 2006-08-22 2012-03-27 Embarq Holdings Company, Llc System and method for load balancing network resources using a connection admission control engine
US8743703B2 (en) 2006-08-22 2014-06-03 Centurylink Intellectual Property Llc System and method for tracking application resource usage
US9479341B2 (en) 2006-08-22 2016-10-25 Centurylink Intellectual Property Llc System and method for initiating diagnostics on a packet network node
US8125897B2 (en) 2006-08-22 2012-02-28 Embarq Holdings Company Lp System and method for monitoring and optimizing network performance with user datagram protocol network performance information packets
US8130793B2 (en) 2006-08-22 2012-03-06 Embarq Holdings Company, Llc System and method for enabling reciprocal billing for different types of communications over a packet network
US8274905B2 (en) 2006-08-22 2012-09-25 Embarq Holdings Company, Llc System and method for displaying a graph representative of network performance over a time period
US8194555B2 (en) 2006-08-22 2012-06-05 Embarq Holdings Company, Llc System and method for using distributed network performance information tables to manage network communications
US8224255B2 (en) 2006-08-22 2012-07-17 Embarq Holdings Company, Llc System and method for managing radio frequency windows
US20080052206A1 (en) * 2006-08-22 2008-02-28 Edwards Stephen K System and method for billing users for communicating over a communications network
US8144586B2 (en) 2006-08-22 2012-03-27 Embarq Holdings Company, Llc System and method for controlling network bandwidth with a connection admission control engine
US8015294B2 (en) 2006-08-22 2011-09-06 Embarq Holdings Company, LP Pin-hole firewall for communicating data packets on a packet network
US8199653B2 (en) 2006-08-22 2012-06-12 Embarq Holdings Company, Llc System and method for communicating network performance information over a packet network
US8238253B2 (en) 2006-08-22 2012-08-07 Embarq Holdings Company, Llc System and method for monitoring interlayer devices and optimizing network performance
US7843831B2 (en) 2006-08-22 2010-11-30 Embarq Holdings Company Llc System and method for routing data on a packet network
US8064391B2 (en) 2006-08-22 2011-11-22 Embarq Holdings Company, Llc System and method for monitoring and optimizing network performance to a wireless device
US8098579B2 (en) 2006-08-22 2012-01-17 Embarq Holdings Company, LP System and method for adjusting the window size of a TCP packet through remote network elements
US8307065B2 (en) 2006-08-22 2012-11-06 Centurylink Intellectual Property Llc System and method for remotely controlling network operators
US8223654B2 (en) * 2006-08-22 2012-07-17 Embarq Holdings Company, Llc Application-specific integrated circuit for monitoring and optimizing interlayer network performance
US8619600B2 (en) 2006-08-22 2013-12-31 Centurylink Intellectual Property Llc System and method for establishing calls over a call path having best path metrics
US8223655B2 (en) 2006-08-22 2012-07-17 Embarq Holdings Company, Llc System and method for provisioning resources of a packet network based on collected network performance information
US8407765B2 (en) 2006-08-22 2013-03-26 Centurylink Intellectual Property Llc System and method for restricting access to network performance information tables
US8549405B2 (en) 2006-08-22 2013-10-01 Centurylink Intellectual Property Llc System and method for displaying a graphical representation of a network to identify nodes and node segments on the network that are not operating normally
US8537695B2 (en) 2006-08-22 2013-09-17 Centurylink Intellectual Property Llc System and method for establishing a call being received by a trunk on a packet network
US8531954B2 (en) 2006-08-22 2013-09-10 Centurylink Intellectual Property Llc System and method for handling reservation requests with a connection admission control engine
US20080049639A1 (en) * 2006-08-22 2008-02-28 Wiley William L System and method for managing a service level agreement
US8107366B2 (en) 2006-08-22 2012-01-31 Embarq Holdings Company, LP System and method for using centralized network performance tables to manage network communications
US8040811B2 (en) 2006-08-22 2011-10-18 Embarq Holdings Company, Llc System and method for collecting and managing network performance information
US7684332B2 (en) 2006-08-22 2010-03-23 Embarq Holdings Company, Llc System and method for adjusting the window size of a TCP packet through network elements
US8750158B2 (en) 2006-08-22 2014-06-10 Centurylink Intellectual Property Llc System and method for differentiated billing
US7940735B2 (en) 2006-08-22 2011-05-10 Embarq Holdings Company, Llc System and method for selecting an access point
US7889660B2 (en) 2006-08-22 2011-02-15 Embarq Holdings Company, Llc System and method for synchronizing counters on an asynchronous packet communications network
US20080049629A1 (en) * 2006-08-22 2008-02-28 Morrill Robert J System and method for monitoring data link layer devices and optimizing interlayer network performance
US8189468B2 (en) 2006-10-25 2012-05-29 Embarq Holdings, Company, LLC System and method for regulating messages between networks
US8190753B2 (en) * 2006-08-28 2012-05-29 Samsung Electronics Co., Ltd. System and method for protecting emergency response services in telecommunication networks from attack
US7848770B2 (en) * 2006-08-29 2010-12-07 Lgc Wireless, Inc. Distributed antenna communications system and methods of implementing thereof
US7830859B1 (en) 2006-08-29 2010-11-09 Sprint Communications Company L.P. Network element control for a communication system coupled to a mobile network
US7912204B1 (en) 2006-08-29 2011-03-22 Sprint Communications Company L.P. Emergency route control for a communication network
US7796581B1 (en) * 2006-08-29 2010-09-14 Sprint Communications Company L.P. Automated route control for a communication network
US7986773B2 (en) * 2006-08-29 2011-07-26 Cisco Technology, Inc. Interactive voice response system security
US7813335B2 (en) * 2006-08-30 2010-10-12 Level 3 Communications, Llc Internet protocol trunk groups
US7869438B2 (en) * 2006-08-31 2011-01-11 Symbol Technologies, Inc. Pre-authentication across an 802.11 layer-3 IP network
US8775621B2 (en) * 2006-08-31 2014-07-08 Redknee Inc. Policy services
US7711370B2 (en) * 2006-09-20 2010-05-04 Cisco Technology, Inc. Method for establishing voice communications using a mobile handset
WO2008042990A1 (en) * 2006-10-03 2008-04-10 Yardarm Technologies, Llc Methods and systems for providing advanced call services
CN101163175A (zh) * 2006-10-11 2008-04-16 鸿富锦精密工业（深圳）有限公司 网络语音装置及其服务切换方法
JP4847270B2 (ja) * 2006-10-12 2011-12-28 キヤノン株式会社 ファクシミリ装置及びその制御方法、プログラム、記憶媒体
US7822046B2 (en) * 2006-10-13 2010-10-26 Cisco Technology, Inc. Triggering bandwidth reservation and priority remarking
CN100452786C (zh) * 2006-10-16 2009-01-14 武汉市中光通信公司 基于ngn的大型综合接入网关系统
ES2324750B1 (es) * 2006-10-17 2010-06-01 Enrique Cimadevila Lage Centro integrado de comunicaciones de voz y datos.
US8090366B2 (en) 2006-10-19 2012-01-03 At&T Mobility Ii Llc Systems and methods for file sharing through mobile devices
US7792097B1 (en) * 2006-10-25 2010-09-07 Cisco Technology, Inc. Static, dynamic and intelligent VRF routing for services traffic
US8995252B2 (en) * 2006-10-29 2015-03-31 FatPipe Networks VoIP multiline failover
US8868719B1 (en) * 2006-10-31 2014-10-21 Symantec Corporation Identity and reputation monitoring
CA3045683C (en) 2006-11-02 2021-10-26 Voip-Pal.Com, Inc. Producing routing messages for voice over ip communications
WO2008064481A1 (en) 2006-11-29 2008-06-05 Digifonica (International) Limited Intercepting voice over ip communications and other data communications
US9307079B2 (en) 2006-12-08 2016-04-05 Telefonaktiebolaget L M Ericsson (Publ) Handling announcement media in a communication network environment
CN101202696B (zh) * 2006-12-11 2010-11-03 华为技术有限公司 用于局内跨网关间承载的流控方法和装置
US20080144655A1 (en) * 2006-12-14 2008-06-19 James Frederick Beam Systems, methods, and computer program products for passively transforming internet protocol (IP) network traffic
US8599747B1 (en) * 2006-12-20 2013-12-03 Radisys Canada Inc. Lawful interception of real time packet data
US8203959B2 (en) * 2006-12-20 2012-06-19 Verizon Patent And Licensing Inc. Apparatus for remotely managing network elements of A VoIP communication system and an associated method and computer program product
US7738383B2 (en) 2006-12-21 2010-06-15 Cisco Technology, Inc. Traceroute using address request messages
WO2008078798A1 (ja) * 2006-12-27 2008-07-03 Kyocera Corporation 通信システム、無線通信端末、通信方法、無線通信方法、無線通信装置、およびその制御方法
CN101622711B (zh) 2006-12-28 2012-07-18 杰恩邦德公司 用于无声插入描述符（sid）转换的方法、系统
US7765173B2 (en) * 2006-12-31 2010-07-27 Ektimisi Semiotics Holdings, Llc Method, system, and computer program product for delivering smart services
US8099084B2 (en) 2006-12-31 2012-01-17 Ektimisi Semiotics Holdings, Llc Method, system, and computer program product for creating smart services
US8660113B1 (en) * 2006-12-31 2014-02-25 At&T Intellectual Property Ii, L.P. Method and apparatus for providing enhanced services local routing
US7647283B2 (en) * 2006-12-31 2010-01-12 Ektimisi Semiotics Holdings, Llc Method, system, and computer program product for adaptively learning user preferences for smart services
US20080167020A1 (en) 2007-01-08 2008-07-10 Jacob Guedalia Methods and systems of accessing contact information on a mobile device
WO2008086412A2 (en) 2007-01-09 2008-07-17 Iskoot, Inc. Method and system for transmitting audio data between computing devices
US11706279B2 (en) 2007-01-24 2023-07-18 Icontrol Networks, Inc. Methods and systems for data communication
US7706278B2 (en) 2007-01-24 2010-04-27 Cisco Technology, Inc. Triggering flow analysis at intermediary devices
US8515079B1 (en) * 2007-01-26 2013-08-20 Cisco Technology, Inc. Hybrid rekey distribution in a virtual private network environment
US7616650B2 (en) * 2007-02-05 2009-11-10 Cisco Technology, Inc. Video flow control and non-standard capability exchange for an H.320 call leg
WO2008100909A2 (en) 2007-02-12 2008-08-21 Iskoot, Inc. Methods and systems for performing authentication and authorization in a user-device environment
US8542802B2 (en) 2007-02-15 2013-09-24 Global Tel*Link Corporation System and method for three-way call detection
US7633385B2 (en) 2007-02-28 2009-12-15 Ucontrol, Inc. Method and system for communicating with and controlling an alarm system from a remote server
US7796643B1 (en) * 2007-03-07 2010-09-14 Sprint Communications Company L.P. Source and event based parameter determination
EP1971100A1 (en) * 2007-03-12 2008-09-17 Siemens Networks GmbH & Co. KG Method and device for processing data in a network component and system comprising such a device
WO2008110896A1 (en) * 2007-03-15 2008-09-18 Telefonaktiebolaget Lm Ericsson (Publ) Transfer of user dial plan to an access gateway
US8265793B2 (en) * 2007-03-20 2012-09-11 Irobot Corporation Mobile robot for telecommunication
WO2008116296A1 (en) 2007-03-26 2008-10-02 Digifonica (International) Limited Emergency assistance calling for voice over ip communications systems
US20080240083A1 (en) * 2007-03-28 2008-10-02 Lowell Phillip Feldman System and method for managing interoperability of internet telephony networks and legacy telephony networks
US8451986B2 (en) 2007-04-23 2013-05-28 Icontrol Networks, Inc. Method and system for automatically providing alternate network access for telecommunications
US20080275788A1 (en) * 2007-05-03 2008-11-06 Utbk, Inc. Systems and Methods to Provide Peer to Peer Connections for Real Time Communications and Commerce
US8089886B1 (en) * 2007-05-22 2012-01-03 At&T Intellectual Property Ii, L.P. Method and apparatus for detecting and reporting timeout events
US7929676B2 (en) * 2007-05-31 2011-04-19 Level 3 Communications, Llc Local routing management in a telecommunications network
US8111692B2 (en) 2007-05-31 2012-02-07 Embarq Holdings Company Llc System and method for modifying network traffic
US8391848B2 (en) * 2007-06-07 2013-03-05 Qualcomm Iskoot, Inc. Telecommunication call support for mobile devices with presence features
US11089122B2 (en) 2007-06-12 2021-08-10 Icontrol Networks, Inc. Controlling data routing among networks
US11423756B2 (en) 2007-06-12 2022-08-23 Icontrol Networks, Inc. Communication protocols in integrated systems
US10523689B2 (en) 2007-06-12 2019-12-31 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US11218878B2 (en) 2007-06-12 2022-01-04 Icontrol Networks, Inc. Communication protocols in integrated systems
US11646907B2 (en) 2007-06-12 2023-05-09 Icontrol Networks, Inc. Communication protocols in integrated systems
US11316753B2 (en) 2007-06-12 2022-04-26 Icontrol Networks, Inc. Communication protocols in integrated systems
US11237714B2 (en) 2007-06-12 2022-02-01 Control Networks, Inc. Control system user interface
US11601810B2 (en) 2007-06-12 2023-03-07 Icontrol Networks, Inc. Communication protocols in integrated systems
US11212192B2 (en) 2007-06-12 2021-12-28 Icontrol Networks, Inc. Communication protocols in integrated systems
US20080313319A1 (en) * 2007-06-18 2008-12-18 Avocent Huntsville Corporation System and method for providing multi-protocol access to remote computers
US8548433B1 (en) 2007-06-27 2013-10-01 Smith Micro Software, Inc. Voice messaging service for network-based instant connect systems
US8248953B2 (en) 2007-07-25 2012-08-21 Cisco Technology, Inc. Detecting and isolating domain specific faults
US8724521B2 (en) * 2007-07-30 2014-05-13 Verint Americas Inc. Systems and methods of recording solution interface
US9043451B2 (en) 2007-07-31 2015-05-26 Tekelec, Inc. Methods, systems, and computer readable media for managing the flow of signaling traffic entering a signaling system 7 (SS7) based network
US9456009B2 (en) * 2007-08-03 2016-09-27 Centurylink Intellectual Property Llc Method and apparatus for securely transmitting lawfully intercepted VOIP data
US10223903B2 (en) 2010-09-28 2019-03-05 Icontrol Networks, Inc. Integrated security system with parallel processing architecture
US11831462B2 (en) 2007-08-24 2023-11-28 Icontrol Networks, Inc. Controlling data routing in premises management systems
GB2465124B (en) * 2007-09-04 2012-09-05 Fujitsu Ltd Access gateway and method of operation by the same
US20090070246A1 (en) * 2007-09-10 2009-03-12 First Data Corporation Electronic Financial Transaction Routing
EP2201508A4 (en) * 2007-09-13 2011-08-31 Redknee Inc MANAGER OF INVOICING PROFILES
US20090083639A1 (en) * 2007-09-26 2009-03-26 Mckee Cooper Joel Distributed conference and information system
US8155128B2 (en) * 2007-09-26 2012-04-10 Alcatel Lucent Method and apparatus for establishing and managing diameter associations
US8656415B2 (en) * 2007-10-02 2014-02-18 Conexant Systems, Inc. Method and system for removal of clicks and noise in a redirected audio stream
US8160448B2 (en) * 2007-10-17 2012-04-17 Hitachi, Ltd. Communication system using passive optical network and passive optical network
US7979095B2 (en) 2007-10-20 2011-07-12 Airbiquity, Inc. Wireless in-band signaling with in-vehicle systems
US7961720B2 (en) * 2007-11-19 2011-06-14 Level 3 Communications, Llc Geographic trunk groups
CN102084620B (zh) * 2007-11-21 2015-09-30 阿尔卡特朗讯 在网络中执行策略的方法和服务管理系统
US8687650B2 (en) 2007-12-07 2014-04-01 Nsgdatacom, Inc. System, method, and computer program product for connecting or coupling analog audio tone based communications systems over a packet data network
US9059871B2 (en) 2007-12-27 2015-06-16 Redknee Inc. Policy-based communication system and method
WO2009093244A2 (en) * 2008-01-22 2009-07-30 I.T.C. - Tech Systems Ltd. A method and a system for unifying telephony and computerized services
US11916928B2 (en) 2008-01-24 2024-02-27 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US8601443B2 (en) * 2008-02-12 2013-12-03 International Business Machines Corporation Method and system for correlating trace data
US8621198B2 (en) * 2008-02-19 2013-12-31 Futurewei Technologies, Inc. Simplified protocol for carrying authentication for network access
AU2009217708C1 (en) * 2008-02-26 2013-05-23 Bt Americas Inc. System and method for replying to voice messages left by callers
US7948910B2 (en) * 2008-03-06 2011-05-24 Cisco Technology, Inc. Monitoring quality of a packet flow in packet-based communication networks
US8300630B2 (en) * 2008-03-14 2012-10-30 International Business Machines Corporation UPD-based soft phone state monitoring for CTI applications
US9106452B2 (en) * 2008-03-24 2015-08-11 Shoretel, Inc. Cloud VoIP system with bypass for IP media
US8483045B2 (en) * 2008-03-24 2013-07-09 Shoretel, Inc. User activated bypass for IP media
US8451714B2 (en) * 2008-03-24 2013-05-28 Shoretel, Inc. PSTN bypass for IP media
US8537687B2 (en) * 2008-04-03 2013-09-17 Verizon Patent And Licensing Inc. Least cost routing
WO2009126839A2 (en) * 2008-04-09 2009-10-15 Level 3 Communications, Llc Content delivery in a network
US8068425B2 (en) 2008-04-09 2011-11-29 Embarq Holdings Company, Llc System and method for using network performance information to determine improved measures of path states
US9426244B2 (en) 2008-04-09 2016-08-23 Level 3 Communications, Llc Content delivery in a network
US8046420B2 (en) 2008-04-23 2011-10-25 Lemko Corporation System and method to control wireless communications
US8856003B2 (en) 2008-04-30 2014-10-07 Motorola Solutions, Inc. Method for dual channel monitoring on a radio device
US9049293B2 (en) * 2008-05-06 2015-06-02 International Business Machines Corporation Performing proximity based routing of a phone call
US8244282B2 (en) * 2008-05-06 2012-08-14 International Business Machines Corporation Performing recipient based routing of a phone call
US8280415B2 (en) 2008-05-06 2012-10-02 International Business Machines Corporation Performing caller based routing of a phone call
US8345837B2 (en) * 2008-05-06 2013-01-01 International Business Machines Corporation Preventing unintended users from accessing a re-routed communication
KR100942775B1 (ko) * 2008-05-19 2010-02-18 최현일 음성/영상 통화 시스템
US8401166B1 (en) 2008-05-20 2013-03-19 Peerless Network, Inc. Systems and methods of mitigating phantom call traffic
WO2009149133A2 (en) * 2008-06-02 2009-12-10 Tekelec Methods, systems, and computer readable media for providing next generation network (ngn)-based end user services to legacy subscribers in a communications network
US8274955B2 (en) * 2008-06-16 2012-09-25 Xg Technology, Inc. Keep alive timeslots in a heterogeneous MAC protocol to track handsets in a wireless network
JP5272536B2 (ja) * 2008-06-25 2013-08-28 富士通株式会社 呼中継方法および呼中継システム
US10922363B1 (en) 2010-04-21 2021-02-16 Richard Paiz Codex search patterns
US10915523B1 (en) 2010-05-12 2021-02-09 Richard Paiz Codex search patterns
US11048765B1 (en) 2008-06-25 2021-06-29 Richard Paiz Search engine optimizer
US20170185278A1 (en) 2008-08-11 2017-06-29 Icontrol Networks, Inc. Automation system user interface
US8340667B2 (en) * 2008-06-26 2012-12-25 Lemko Corporation System and method to control wireless communications
US8706105B2 (en) 2008-06-27 2014-04-22 Lemko Corporation Fault tolerant distributed mobile architecture
US20090323560A1 (en) * 2008-06-27 2009-12-31 Microsoft Corporation Customized Media Routing For Conferencing
CN101304330B (zh) * 2008-06-28 2010-12-08 华为技术有限公司 一种资源配置方法、服务器、及网络系统
CN101621506A (zh) * 2008-07-01 2010-01-06 鸿富锦精密工业（深圳）有限公司 透过nat实现实时多媒体双向通信的方法
US8107409B2 (en) 2008-07-11 2012-01-31 Lemko Corporation OAMP for distributed mobile architecture
US7855988B2 (en) 2008-07-14 2010-12-21 Lemko Corporation System, method, and device for routing calls using a distributed mobile architecture
WO2010104747A2 (en) * 2009-03-10 2010-09-16 Baylor Research Institute Antigen presenting cell targeted vaccines
US20100014431A1 (en) * 2008-07-17 2010-01-21 Paritosh Bajpay Method and apparatus for providing automated processing of a network service alarm
US8306200B2 (en) * 2008-07-17 2012-11-06 At&T Intellectual Property I, L.P. Method and apparatus for processing of a toll free call service alarm
US8363790B2 (en) * 2008-07-17 2013-01-29 At&T Intellectual Property I, L.P. Method and apparatus for providing automated processing of a switched voice service alarm
US8630234B2 (en) * 2008-07-28 2014-01-14 Digifonica (International) Limited Mobile gateway
WO2010014856A2 (en) * 2008-07-31 2010-02-04 Tekelec Methods, systems, and computer readable media for throttling traffic to an internet protocol (ip) network server using alias hostname identifiers assigned to the ip network server with a domain name system (dns)
US20100027524A1 (en) * 2008-07-31 2010-02-04 Nokia Corporation Radio layer emulation of real time protocol sequence number and timestamp
US11758026B2 (en) 2008-08-11 2023-09-12 Icontrol Networks, Inc. Virtual device systems and methods
US11258625B2 (en) 2008-08-11 2022-02-22 Icontrol Networks, Inc. Mobile premises automation platform
US11729255B2 (en) 2008-08-11 2023-08-15 Icontrol Networks, Inc. Integrated cloud system with lightweight gateway for premises automation
US11792036B2 (en) 2008-08-11 2023-10-17 Icontrol Networks, Inc. Mobile premises automation platform
US10530839B2 (en) 2008-08-11 2020-01-07 Icontrol Networks, Inc. Integrated cloud system with lightweight gateway for premises automation
WO2010027739A2 (en) * 2008-08-27 2010-03-11 Globys, Inc. Targeted customer offers based on predictive analytics
JP5307508B2 (ja) * 2008-08-29 2013-10-02 キヤノン株式会社 通信装置、通信方法、コンピュータプログラム
GB2463494A (en) * 2008-09-15 2010-03-17 Data Connection Ltd Providing a single telephone dialling number for multiple telephony devices
US7983310B2 (en) 2008-09-15 2011-07-19 Airbiquity Inc. Methods for in-band signaling through enhanced variable-rate codecs
US8594138B2 (en) 2008-09-15 2013-11-26 Airbiquity Inc. Methods for in-band signaling through enhanced variable-rate codecs
US8392631B1 (en) 2008-10-02 2013-03-05 Apple Inc. Methods and apparatus for transmitting data streams via a heterogeneous network
JP5171527B2 (ja) * 2008-10-06 2013-03-27 キヤノン株式会社 メッセージの受信装置およびデータ抽出方法
US8565075B2 (en) * 2008-10-30 2013-10-22 Verizon Patent And Licensing Inc. Method and system for determining alternate paths
US8468253B2 (en) * 2008-12-02 2013-06-18 At&T Intellectual Property I, L.P. Method and apparatus for multimedia collaboration using a social network system
US20100150329A1 (en) * 2008-12-12 2010-06-17 Verizon Data Services Llc Distributed order processing
US20100174575A1 (en) * 2009-01-02 2010-07-08 International Business Machines Corporation Meeting management system with failover and failback capabilities for meeting moderators
KR101530219B1 (ko) * 2009-01-05 2015-06-22 삼성전자주식회사 음성 패킷망에서 음성 페이징 서비스를 제공하기 위한 그룹캐스팅 전송방법 및 장치
WO2010083509A2 (en) 2009-01-16 2010-07-22 Tekelec Methods, systems, and computer readable media for centralized routing and call instance code management for bearer independent call control (bicc) signaling messages
US8146159B2 (en) * 2009-01-20 2012-03-27 Check Point Software Technologies, Ltd. Methods for inspecting security certificates by network security devices to detect and prevent the use of invalid certificates
US8582560B2 (en) * 2009-01-30 2013-11-12 Level 3 Communications, Llc System and method for routing calls associated with private dialing plans
US9225838B2 (en) 2009-02-12 2015-12-29 Value-Added Communications, Inc. System and method for detecting three-way call circumvention attempts
US8724790B2 (en) * 2009-02-13 2014-05-13 Conexant Systems, Inc. Systems and methods for network facsimile transmissions
US8775674B2 (en) * 2009-02-27 2014-07-08 Telecom Recovery Systems and methods for seamless communications recovery and backup using networked communication devices
CN101505469B (zh) * 2009-03-03 2011-08-24 中兴通讯股份有限公司 一种回呼业务实现系统及方法
US9357065B2 (en) 2009-03-18 2016-05-31 Centurylink Intellectual Property Llc System, method and apparatus for transmitting audio signals over a voice channel
US20100238842A1 (en) * 2009-03-19 2010-09-23 Microsoft Corporation Phone conferencing architecture with optimized services management
EP3668008B1 (en) 2009-03-20 2022-05-18 Huawei Technologies Co., Ltd. Method, apparatus, and system for controlling self-optimization switch
US8036600B2 (en) 2009-04-27 2011-10-11 Airbiquity, Inc. Using a bluetooth capable mobile phone to access a remote network
US8638211B2 (en) 2009-04-30 2014-01-28 Icontrol Networks, Inc. Configurable controller and interface for home SMA, phone and multimedia
US20100281123A1 (en) * 2009-05-04 2010-11-04 Charles Greenberg System and method for targeted communication
US8659639B2 (en) 2009-05-29 2014-02-25 Cisco Technology, Inc. System and method for extending communications between participants in a conferencing environment
ES2702464T3 (es) 2009-06-17 2019-03-01 Bridgeport Networks Inc Detección de presencia mejorada para decisiones de enrutamiento
US8488745B2 (en) * 2009-06-17 2013-07-16 Microsoft Corporation Endpoint echo detection
US20110013762A1 (en) * 2009-07-18 2011-01-20 Gregg Bieser Notification apparatus & method
US8418039B2 (en) 2009-08-03 2013-04-09 Airbiquity Inc. Efficient error correction scheme for data transmission in a wireless in-band signaling system
US8908541B2 (en) 2009-08-04 2014-12-09 Genband Us Llc Methods, systems, and computer readable media for intelligent optimization of digital signal processor (DSP) resource utilization in a media gateway
US9082297B2 (en) 2009-08-11 2015-07-14 Cisco Technology, Inc. System and method for verifying parameters in an audiovisual environment
WO2011028848A1 (en) * 2009-09-01 2011-03-10 Lp Partners, Inc. Ip based microphone and intercom
CA2812174C (en) 2009-09-17 2018-05-15 Digifonica (International) Limited Uninterrupted transmission of internet protocol transmissions during endpoint changes
US20110075654A1 (en) * 2009-09-29 2011-03-31 Sonus Networks, Inc. Method and System for Implementing Redundancy at Signaling Gateway Using Dynamic SIGTRAN Architecture
US20110078274A1 (en) * 2009-09-29 2011-03-31 Sonus Networks, Inc. Method and System for Implementing Redundancy at Signaling Gateway Using Dynamic SIGTRAN Architecture
CN102035950B (zh) * 2009-09-30 2014-08-13 华为技术有限公司 坐席业务处理方法及ip坐席终端
US8838800B2 (en) * 2009-11-23 2014-09-16 Hewlett-Packard Development Company, L.P. Binding resources in a shared computing environment
US8249865B2 (en) 2009-11-23 2012-08-21 Airbiquity Inc. Adaptive data transmission for a digital in-band modem operating over a voice channel
US9098320B2 (en) * 2009-12-23 2015-08-04 Savvis Inc. Systems and methods for automatic provisioning of a user designed virtual private data center in a multi-tenant system
US20120054624A1 (en) 2010-08-27 2012-03-01 Owens Jr Kenneth Robert Systems and methods for a multi-tenant system providing virtual data centers in a cloud configuration
US8897377B2 (en) * 2009-12-31 2014-11-25 Broadcom Corporation Transcoding multiple media elements for independent wireless delivery
US8306420B2 (en) * 2010-01-08 2012-11-06 Ciena Corporation Optical network real time latency measurement systems and methods
US9014369B2 (en) * 2010-02-11 2015-04-21 International Business Machines Corporation Voice-over internet protocol (VoIP) scrambling mechanism
IN2012CN07525A (un) 2010-02-12 2015-05-29 Tekelec Inc
US9225916B2 (en) 2010-03-18 2015-12-29 Cisco Technology, Inc. System and method for enhancing video images in a conferencing environment
CN101815024B (zh) * 2010-03-24 2014-10-22 中兴通讯股份有限公司 以太业务互通方法及装置
US8441962B1 (en) * 2010-04-09 2013-05-14 Sprint Spectrum L.P. Method, device, and system for real-time call announcement
US11423018B1 (en) 2010-04-21 2022-08-23 Richard Paiz Multivariate analysis replica intelligent ambience evolving system
US10936687B1 (en) 2010-04-21 2021-03-02 Richard Paiz Codex search patterns virtual maestro
US11379473B1 (en) 2010-04-21 2022-07-05 Richard Paiz Site rank codex search patterns
US8346160B2 (en) 2010-05-12 2013-01-01 Andrew Llc System and method for detecting and measuring uplink traffic in signal repeating systems
US9313452B2 (en) 2010-05-17 2016-04-12 Cisco Technology, Inc. System and method for providing retracting optics in a video conferencing environment
WO2011156696A1 (en) * 2010-06-11 2011-12-15 Triasys Technoloigies Corporation System and method for mapping ss7 bearer channels
EP2583415B1 (en) * 2010-06-15 2018-07-25 Tekelec, Inc. Method, diameter node, and computer readable medium for providing dynamic origination-based routing key registration in a diameter network
US8976949B2 (en) 2010-06-29 2015-03-10 Telmate, Llc Central call platform
US8064354B1 (en) 2010-07-21 2011-11-22 Intelepeer, Inc. Optimized path call routing with device identifier
CN102377635B (zh) * 2010-08-06 2014-01-01 北京乾唐视联网络科技有限公司 一种城域网通信方法及通信系统
CN102377633B (zh) * 2010-08-06 2014-10-08 北京乾唐视联网络科技有限公司 一种接入网设备的通信连接方法及系统
US8836467B1 (en) 2010-09-28 2014-09-16 Icontrol Networks, Inc. Method, system and apparatus for automated reporting of account and sensor zone information to a central station
US20120092439A1 (en) * 2010-10-19 2012-04-19 Cisco Technology, Inc. System and method for providing connectivity in a network environment
US8923498B2 (en) * 2010-10-26 2014-12-30 Vonage Network, Llc Systems and methods for integrating information from voice over internet protocol systems and social networking systems
US8774010B2 (en) 2010-11-02 2014-07-08 Cisco Technology, Inc. System and method for providing proactive fault monitoring in a network environment
KR101413295B1 (ko) * 2010-11-04 2014-06-30 한국전자통신연구원 확장성과 적응성을 가지는 ｄｄｓ 구조 및 ｄｄｓ를 구성하는 노드
US8559341B2 (en) 2010-11-08 2013-10-15 Cisco Technology, Inc. System and method for providing a loop free topology in a network environment
US8543653B2 (en) * 2010-11-11 2013-09-24 Sap Ag Systems and methods for business network management discovery and consolidation
US9111138B2 (en) 2010-11-30 2015-08-18 Cisco Technology, Inc. System and method for gesture interface control
US9077799B2 (en) * 2010-11-30 2015-07-07 International Business Machines Corporation Facilitating context delivery during communication sessions
US8611360B2 (en) * 2010-12-15 2013-12-17 At&T Intellectual Property I, L.P. System for processing a call with a TDM network and routing the call with an IP network
US11750414B2 (en) 2010-12-16 2023-09-05 Icontrol Networks, Inc. Bidirectional security sensor communication for a premises security system
US9147337B2 (en) 2010-12-17 2015-09-29 Icontrol Networks, Inc. Method and system for logging security event data
US9521015B2 (en) * 2010-12-21 2016-12-13 Genband Us Llc Dynamic insertion of a quality enhancement gateway
US8681783B2 (en) * 2011-02-18 2014-03-25 Verizon Patent And Licensing Inc. Prevention of call spoofing in a Voice over Internet Protocol (VoIP) network
EP2681892A4 (en) 2011-02-28 2014-12-03 Interactive Social Internetworks Llc SYSTEMS AND METHODS FOR NETWORK COMMUNICATION
EP2681940B1 (en) 2011-03-03 2016-05-25 Tekelec, Inc. Methods, systems, and computer readable media for enriching a diameter signaling message
US8982733B2 (en) 2011-03-04 2015-03-17 Cisco Technology, Inc. System and method for managing topology changes in a network environment
KR101589239B1 (ko) * 2011-03-09 2016-01-28 한국전자통신연구원 패킷 호 설정 방법 및 장치
US8670326B1 (en) 2011-03-31 2014-03-11 Cisco Technology, Inc. System and method for probing multiple paths in a network environment
US8681961B2 (en) * 2011-04-18 2014-03-25 Zetron, Inc. Call center system with assisted-configuration and method of operation thereof
US8897173B2 (en) * 2011-04-29 2014-11-25 T-Mobile Usa, Inc. Microwave backhaul arrangements
US9064017B2 (en) * 2011-06-01 2015-06-23 D2L Corporation Systems and methods for providing information incorporating reinforcement-based learning and feedback
US8724517B1 (en) 2011-06-02 2014-05-13 Cisco Technology, Inc. System and method for managing network traffic disruption
US8830875B1 (en) 2011-06-15 2014-09-09 Cisco Technology, Inc. System and method for providing a loop free topology in a network environment
US9184779B2 (en) * 2011-07-22 2015-11-10 Texas Instruments Incorporated Dynamic medium switch in co-located PLC and RF networks
US9063673B2 (en) * 2011-08-30 2015-06-23 Uniquesoft, Llc System and method for implementing application code from application requirements
US8493898B2 (en) 2011-09-15 2013-07-23 International Business Machines Corporation Macro diversity in a mobile data network with edge breakout
US9014023B2 (en) 2011-09-15 2015-04-21 International Business Machines Corporation Mobile network services in a mobile data network
US8848825B2 (en) 2011-09-22 2014-09-30 Airbiquity Inc. Echo cancellation in wireless inband signaling modem
US8891743B2 (en) * 2011-10-04 2014-11-18 Cisco Technology, Inc. Gain control enhancement for modulated communications
US9197948B2 (en) 2011-10-11 2015-11-24 Level 3 Communications, Llc Regional independent tandem telephone switch
US9210225B2 (en) 2011-11-01 2015-12-08 Vonage Network Llc Method and system for dynamically assigning a server
CN102611947B (zh) * 2011-11-24 2017-11-17 中兴通讯股份有限公司 创建组播频道的方法、系统和媒体服务器
WO2013090839A1 (en) * 2011-12-14 2013-06-20 Realnetworks, Inc. Customizable media auto-reply systems and methods
US8479271B1 (en) 2011-12-20 2013-07-02 International Business Machines Corporation Hosting edge applications at the edge of a mobile data network
US9009221B2 (en) * 2011-12-21 2015-04-14 Verizon Patent And Licensing Inc. Transaction services management system
US9141646B1 (en) * 2011-12-30 2015-09-22 Teradata Us, Inc. Database redistribution in dynamically-configured database systems
US9001651B2 (en) * 2012-02-06 2015-04-07 Verizon Patent And Licensing Inc. Method for call admission control in MPLS networks
US9444635B2 (en) 2012-02-09 2016-09-13 Cisco Technology, Inc. Bandwidth allocation for multimedia conferencing
US9112792B2 (en) 2012-04-10 2015-08-18 International Business Machines Corporation Hosting device-specific edge applications at the edge of a mobile data network
US9686164B1 (en) * 2012-04-12 2017-06-20 Sprint Communications Company L.P. Packet allocation schema for 3G and 4G routers
US8983507B1 (en) * 2012-04-23 2015-03-17 Peerless Network, Inc. Private packet network backbone exchange with variable call termination location capability
US9270155B2 (en) 2012-05-20 2016-02-23 Mts Systems Corporation Linear actuator assembly
US9367826B2 (en) 2012-06-28 2016-06-14 Sap Se Consistent interface for entitlement product
US8989141B2 (en) 2012-07-17 2015-03-24 International Business Machines Corporation Transferring a session for user equipment to a different basestation running a needed edge application
US9001733B2 (en) 2012-07-17 2015-04-07 International Business Machines Corporation Offloading running a needed edge application to a neighboring basestation in a mobile data network
US9547833B2 (en) 2012-08-22 2017-01-17 Sap Se Consistent interface for financial instrument impairment calculation
TWI463886B (zh) * 2012-08-27 2014-12-01 Hon Hai Prec Ind Co Ltd 用戶終端設備的處理器資源管控系統及方法
US9083579B1 (en) 2012-09-28 2015-07-14 Emc Corporation Stateless services in content management clients
US9100503B2 (en) * 2012-10-04 2015-08-04 Level 3 Communications, Llc Class 4 long distance softswitch network with integrated class 5 application services
US9450846B1 (en) 2012-10-17 2016-09-20 Cisco Technology, Inc. System and method for tracking packets in a network environment
US9167484B2 (en) * 2012-10-30 2015-10-20 T-Mobile Usa, Inc. Transition from packet-switched to circuit-switched connection based on communication quality
CN102938729B (zh) * 2012-10-30 2016-12-21 山东智慧生活数据系统有限公司 智能网关、智能家居系统及家电设备的远程控制方法
US8972061B2 (en) 2012-11-02 2015-03-03 Irobot Corporation Autonomous coverage robot
US20140185491A1 (en) * 2012-12-29 2014-07-03 Simon Ma Systems and Methods for Providing Telecommunications
US9602569B2 (en) * 2013-02-14 2017-03-21 Metaswitch Networks Limited Management of a remote digital terminal
US11809506B1 (en) 2013-02-26 2023-11-07 Richard Paiz Multivariant analyzing replicating intelligent ambience evolving system
US11741090B1 (en) 2013-02-26 2023-08-29 Richard Paiz Site rank codex search patterns
US8954037B2 (en) 2013-02-28 2015-02-10 Dell Products L.P. System and method of signaling the importance of a transmission in a wireless communications network
US9674233B2 (en) 2013-03-04 2017-06-06 Vonage Business Inc. Method and apparatus for performing network registration
US8879476B2 (en) * 2013-03-04 2014-11-04 Vonage Network Llc Method and apparatus for performing network registration
US9755900B2 (en) * 2013-03-11 2017-09-05 Amazon Technologies, Inc. Managing configuration updates
US20140278626A1 (en) * 2013-03-15 2014-09-18 Sap Ag Consistent Interface for Task Activity Business Object
US20140269678A1 (en) * 2013-03-15 2014-09-18 Evan Patrick McGee Method for providing an application service, including a managed translation service
JP5769748B2 (ja) * 2013-03-26 2015-08-26 京セラドキュメントソリューションズ株式会社 ネットワーク通信装置、ファクシミリ装置
US20140298195A1 (en) * 2013-04-01 2014-10-02 Harman International Industries, Incorporated Presence-aware information system
CN104104661A (zh) * 2013-04-09 2014-10-15 中兴通讯股份有限公司 客户端、服务器、远程用户拨号认证能力协商方法及系统
US20140376541A1 (en) * 2013-06-19 2014-12-25 Microsoft Corporation Dual-tone multi-frequency (dtmf) programming of an auto-dialer
US8737973B1 (en) * 2013-07-22 2014-05-27 Robert W. Petrunka Enhanced voice calling using smart phone services
US9414415B1 (en) * 2013-09-10 2016-08-09 Sprint Communications Company L.P. Call setup system and method for setting up a wireless media session extending from a first network to a second network
JP6160409B2 (ja) * 2013-09-30 2017-07-12 ブラザー工業株式会社 ファクシミリ装置
US9203936B2 (en) * 2013-10-07 2015-12-01 At&T Intellectual Property I, Lp Method and apparatus for initiating communication sessions
US9602616B2 (en) 2013-11-06 2017-03-21 Neustar, Inc. System and method for facilitating routing
US9020483B1 (en) 2013-11-26 2015-04-28 At&T Mobility Ii Llc Setting voice and data priority using a registration message
US11146637B2 (en) 2014-03-03 2021-10-12 Icontrol Networks, Inc. Media content management
US11405463B2 (en) 2014-03-03 2022-08-02 Icontrol Networks, Inc. Media content management
US10397407B1 (en) 2014-04-24 2019-08-27 8X8, Inc. Apparatus and method for user configuration and reporting of virtual services
CN105338501B (zh) * 2014-08-08 2020-08-07 中兴通讯股份有限公司 一种通话过程中信息的传送方法、获取方法、装置及终端
US9282442B1 (en) 2014-10-29 2016-03-08 Sprint Communications Company L.P. Communication system to route telephony signals based on originating line information
US9992352B2 (en) 2014-11-01 2018-06-05 Somos, Inc. Toll-free telecommunications and data management platform
US10560583B2 (en) 2014-11-01 2020-02-11 Somos, Inc. Toll-free numbers metadata tagging, analysis and reporting
CA3061385C (en) 2014-11-01 2022-04-12 Somos, Inc. Toll-free telecommunications management platform
CN105653374B (zh) * 2014-11-12 2020-04-28 华为技术有限公司 分布式事务资源执行的方法、装置和系统
US9704043B2 (en) 2014-12-16 2017-07-11 Irobot Corporation Systems and methods for capturing images and annotating the captured images with information
US20160227229A1 (en) * 2015-02-04 2016-08-04 Harris Corporation Mobile ad hoc network media aware networking element
US10200302B2 (en) * 2015-02-04 2019-02-05 Cisco Technology, Inc. Techniques for allocating resources for communication in a communication network
US9237121B1 (en) * 2015-03-24 2016-01-12 OTC Systems, Ltd. Commercial email management system
US10516905B2 (en) * 2015-04-01 2019-12-24 Nokia Of America Corporation Dynamic service flow creation for packet cable quality of service guarantee in a distributed cable management system
US9276862B1 (en) * 2015-06-19 2016-03-01 SipNav, LLC Telecommunications and network traffic control and rate deck synchronization system
US10484513B2 (en) 2015-07-17 2019-11-19 Nsgdatacom, Inc. System, method, and computer program product for connecting or coupling audio communications systems over a software defined wide area network
US9918154B2 (en) 2015-07-30 2018-03-13 Skullcandy, Inc. Tactile vibration drivers for use in audio systems, and methods for operating same
US9838439B2 (en) 2015-09-04 2017-12-05 Level 3 Communications, Llc Telephone number simplification for VoIP networks
US9854104B2 (en) * 2015-11-18 2017-12-26 Level 3 Communications, Llc Method and system for dynamic trunk group based call routing
EP3395099A4 (en) * 2015-12-21 2019-07-24 Nokia Solutions and Networks Oy INTERNET PROTOCOL (IP) (IMS) MULTIMEDIA SUBSYSTEM LEVEL RECOGNITION OF A HIGH LATENCY DEVICE
CN111954174B (zh) * 2015-12-31 2022-07-29 华为技术有限公司 一种提示呼叫的方法
WO2017125922A1 (en) * 2016-01-18 2017-07-27 Sckipio Technologies S.I Ltd Dynamic resource allocation (dra) for communication systems
JP6549996B2 (ja) * 2016-01-27 2019-07-24 アラクサラネットワークス株式会社 ネットワーク装置、通信方法、及び、ネットワークシステム
US9854528B2 (en) 2016-04-05 2017-12-26 At&T Intellectual Property I, L.P. Tuning networks and user equipment using a power profile
US10263954B2 (en) 2016-06-17 2019-04-16 At&T Intellectual Property I, L.P Identifying the source and destination sites for a VoIP call with dynamic-IP address end points
US11671533B1 (en) 2016-06-23 2023-06-06 8X8, Inc. Programming/data sets via a data-communications server
US11044365B1 (en) * 2016-06-23 2021-06-22 8X8, Inc. Multi-level programming/data sets with decoupling VoIP communications interface
US11412084B1 (en) 2016-06-23 2022-08-09 8X8, Inc. Customization of alerts using telecommunications services
US10938740B2 (en) * 2016-08-18 2021-03-02 Level 3 Communications, Llc System and methods for routing traffic in a telecommunications network using trunk group identification
US10650621B1 (en) 2016-09-13 2020-05-12 Iocurrents, Inc. Interfacing with a vehicular controller area network
US10313259B2 (en) * 2016-12-09 2019-06-04 Vmware, Inc. Suppressing broadcasts in cloud environments
US10205825B2 (en) 2017-02-28 2019-02-12 At&T Intellectual Property I, L.P. System and method for processing an automated call based on preferences and conditions
JP6766696B2 (ja) * 2017-03-06 2020-10-14 コニカミノルタ株式会社 情報処理システム
US10284392B2 (en) 2017-05-19 2019-05-07 At&T Intellectual Property I, L.P. Virtual private network resiliency over multiple transports
US10536409B2 (en) * 2017-06-01 2020-01-14 Lenovo (Singapore) Pte. Ltd. Relaying an interpersonal communication
US10104710B1 (en) 2017-06-19 2018-10-16 Global Tel*Link Corporation Dual mode transmission in a controlled environment
US9930088B1 (en) 2017-06-22 2018-03-27 Global Tel*Link Corporation Utilizing VoIP codec negotiation during a controlled environment call
US11575732B1 (en) 2017-06-23 2023-02-07 8X8, Inc. Networked device control using a high-level programming interface
US10277557B1 (en) * 2017-07-01 2019-04-30 Juniper Networks, Inc. Apparatus, system, and method for compressing port list definitions for sparse port indices
US10333870B2 (en) 2017-07-06 2019-06-25 Global Tel*Link Corporation Presence-based communications in a controlled environment
US10097490B1 (en) * 2017-09-01 2018-10-09 Global Tel*Link Corporation Secure forum facilitator in controlled environment
CN109474449A (zh) * 2017-09-08 2019-03-15 华为技术有限公司 一种处理网络切片实例的方法及装置
US10944873B2 (en) 2017-10-13 2021-03-09 Comcast Cable Communications, FFC Routing VOIP traffic
JP6839113B2 (ja) * 2018-02-01 2021-03-03 日本電信電話株式会社 転送装置及び転送方法
US10388286B1 (en) * 2018-03-20 2019-08-20 Capital One Services, Llc Systems and methods of sound-based fraud protection
US10116803B1 (en) * 2018-03-28 2018-10-30 Airespring, Inc. System and method of rerouting a toll free telephony call in the event of the failure to connect to the target telephony station
DE102018205264B3 (de) * 2018-04-09 2019-10-10 Continental Automotive Gmbh Verfahren zum Betreiben eines Ethernet-Bordnetzes eines Kraftfahrzeugs, Steuereinheit und Ethernet-Bordnetz
CN108494803B (zh) * 2018-05-24 2019-04-19 广西电网有限责任公司 基于人工智能的多元异构网络安全数据可视化系统
WO2019246506A1 (en) * 2018-06-21 2019-12-26 Securelogix Corporation Call authentication service systems and methods
JP7006533B2 (ja) * 2018-08-09 2022-01-24 日本電信電話株式会社 メディアゲートウェイ装置、および、メディアパス設定方法
US11039007B2 (en) * 2018-08-10 2021-06-15 Somos, Inc. Toll-free telecommunications data management interface
US10248527B1 (en) 2018-09-19 2019-04-02 Amplero, Inc Automated device-specific dynamic operation modifications
CN109462753B (zh) * 2018-11-19 2021-12-03 视联动力信息技术股份有限公司 一种视联网多会议测试系统和方法
US10681206B1 (en) 2018-12-05 2020-06-09 At&T Intellectual Property I, L.P. Detecting a spoofed call
US11063809B2 (en) 2018-12-07 2021-07-13 Hewlett Packard Enterprise Development Lp Redundant simple network management protocol (SNMP) systems and methods
EP3900313A1 (en) * 2018-12-17 2021-10-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for different mid-call announcements to both served and non-served parties at the same time
US11425134B1 (en) * 2019-04-10 2022-08-23 Ca, Inc. Secure access to a corporate web application with translation between an internal address and an external address
CN110198279B (zh) * 2019-04-16 2022-05-20 腾讯科技（深圳）有限公司 一种转发媒体包的方法及转发服务器
US11606403B2 (en) * 2019-04-22 2023-03-14 Johnson Controls Tyco IP Holdings LLP Systems and methods for echo management in conferencing over a network using mixed multicast
US10542140B1 (en) * 2019-05-08 2020-01-21 The Light Phone Inc. Telecommunications system
US11240276B2 (en) * 2019-09-27 2022-02-01 Ametek, Inc. Communication system for interfacing with an alarm system control panel
US11889028B2 (en) 2021-04-26 2024-01-30 Zoom Video Communications, Inc. System and method for one-touch split-mode conference access
US11916979B2 (en) 2021-10-25 2024-02-27 Zoom Video Communications, Inc. Shared control of a remote client
US11656926B1 (en) 2022-01-26 2023-05-23 Bank Of America Corporation Systems and methods for automatically applying configuration changes to computing clusters
US20230344893A1 (en) * 2022-04-25 2023-10-26 Zoom Video Communications, Inc. Third Party Application Control Of A Client
US11729148B1 (en) * 2022-09-04 2023-08-15 Uab 360 It Optimized utilization of internet protocol addresses in a virtual private network

Family Cites Families (335)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US223968A (en) 1880-01-27 Peters
US4100377A (en) 1977-04-28 1978-07-11 Bell Telephone Laboratories, Incorporated Packet transmission of speech
JPS585541B2 (ja) 1978-05-08 1983-01-31 富士通株式会社 パケット伝送方式
JPS57104339A (en) 1980-12-19 1982-06-29 Ricoh Co Ltd Optical communication network
JPS58139543A (ja) 1982-02-15 1983-08-18 Ricoh Co Ltd 通信回路網
US5355371A (en) 1982-06-18 1994-10-11 International Business Machines Corp. Multicast communication tree creation and control method and apparatus
JPS5918923A (ja) 1982-07-23 1984-01-31 Toshiba Corp 複屈折測定装置
US4674082A (en) 1982-10-05 1987-06-16 Telex Computer Products, Inc. PBX telephone system I/O interface
US4569041A (en) 1983-03-17 1986-02-04 Nec Corporation Integrated circuit/packet switching system
US4679191A (en) 1983-05-04 1987-07-07 Cxc Corporation Variable bandwidth switching system
US4651316A (en) 1983-07-11 1987-03-17 At&T Bell Laboratories Data link extension for data communication networks
JPS60151236A (ja) 1984-01-18 1985-08-09 Okamoto Tokushu Glass Kk 装飾ガラスの製造方法
US4608685A (en) 1984-04-30 1986-08-26 Northern Telecom Limited Packet and circuit switched communications network
EP0162173B1 (fr) 1984-05-23 1989-08-16 International Business Machines Corporation Sytème numérique de transmission de la voix par paquets
US4661947A (en) 1984-09-26 1987-04-28 American Telephone And Telegraph Company At&T Bell Laboratories Self-routing packet switching network with intrastage packet communication
GB2166320B (en) 1984-10-25 1988-10-12 Stc Plc Packet switching system
US4819228A (en) 1984-10-29 1989-04-04 Stratacom Inc. Synchronous packet voice/data communication system
US4771425A (en) 1984-10-29 1988-09-13 Stratacom, Inc. Synchoronous packet voice/data communication system
US4903261A (en) 1984-10-29 1990-02-20 Stratacom, Inc. Synchronous packet voice/data communication system
DE3517006A1 (de) 1985-05-09 1986-11-13 Siemens AG, 1000 Berlin und 8000 München Schaltungsanordnung fuer ein kommunikationssystem zur uebertragung von nachrichteninformationen von schmal- und breitband-endgeraeten innerhalb ringfoermig strukturierter lokaler netzwerke
US4630260A (en) 1985-06-27 1986-12-16 At&T Bell Laboratories Self-routing multipath packet switching network with sequential delivery of packets
IL79775A (en) 1985-08-23 1990-06-10 Republic Telcom Systems Corp Multiplexed digital packet telephone system
US4734907A (en) 1985-09-06 1988-03-29 Washington University Broadcast packet switching network
US4690491A (en) 1985-10-04 1987-09-01 Southwestern Bell Telephone Building data transmission system
JPH0666990B2 (ja) 1985-11-28 1994-08-24 富士通株式会社 加入者線交換制御方式
US4736462A (en) 1986-03-20 1988-04-05 American Telephone And Telegraph Company, At&T Bell Laboratories Photonic switching
US4723238A (en) 1986-03-24 1988-02-02 American Telephone And Telegraph Company Interface circuit for interconnecting circuit switched and packet switched systems
US4679190A (en) 1986-04-28 1987-07-07 International Business Machines Corporation Distributed voice-data switching on multi-stage interconnection networks
JPH0754933B2 (ja) 1986-08-14 1995-06-07 日本電気株式会社 パケツトネツトワ−クにおける回線交換方法及び装置
US4901307A (en) 1986-10-17 1990-02-13 Qualcomm, Inc. Spread spectrum multiple access communication system using satellite or terrestrial repeaters
US4723338A (en) * 1986-11-24 1988-02-09 Hirofusa Otsubo Suction cleaning device
US4757497A (en) 1986-12-03 1988-07-12 Lan-Tel, Inc. Local area voice/data communications and switching system
GB8727846D0 (en) 1987-11-27 1987-12-31 British Telecomm Optical communications network
DE3777797D1 (de) 1987-01-28 1992-04-30 Ibm Vorrichtung zur vermittlung zwischen kanaelen fuer synchronen nachrichtenverkehr und zur vermittlung von asynchronen datenpaketen.
US4809362A (en) 1987-03-13 1989-02-28 Center For Innovative Technology Fiber-optic star tree network
US4914648A (en) 1987-03-26 1990-04-03 American Telephone And Telegraph Company Multichannel, multihop lightwave communication system
US4975695A (en) 1987-10-01 1990-12-04 Data General Corporation High speed communication processing system
US4932022A (en) 1987-10-07 1990-06-05 Telenova, Inc. Integrated voice and data telephone system
US5022071A (en) 1987-10-21 1991-06-04 Electronic Speech Systems Two-way voice & digital data analyzer for telephones
JPH0834479B2 (ja) 1987-10-22 1996-03-29 国際電信電話株式会社 光パケット交換方式
US4885739A (en) 1987-11-13 1989-12-05 Dsc Communications Corporation Interprocessor switching network
US5291489A (en) 1987-11-13 1994-03-01 Dsc Communications Corporation Interprocessor switching network
DE3742939A1 (de) 1987-12-18 1989-07-06 Standard Elektrik Lorenz Ag Verfahren zur hybriden paketvermittlung und einrichtungen hierzu
US5933608A (en) 1988-02-04 1999-08-03 The City University Multiway signal switching device including a WSIC and optical communication ports
IT1219054B (it) 1988-02-29 1990-04-24 Cselt Centro Studi Lab Telecom Nodo per rete a commutazione veloce di pacchetto in tecnologia ottico elettrica
US4866704A (en) 1988-03-16 1989-09-12 California Institute Of Technology Fiber optic voice/data network
JP2595025B2 (ja) 1988-03-18 1997-03-26 株式会社日立製作所 空間分割形スイッチを用いた高速パケット交換装置
US4958341A (en) 1988-03-31 1990-09-18 At&T Bell Laboratories Integrated packetized voice and data switching system
US4872160A (en) 1988-03-31 1989-10-03 American Telephone And Telegraph Company, At&T Bell Laboratories Integrated packetized voice and data switching system
US4872159A (en) 1988-03-31 1989-10-03 American Telephone And Telegraph Company At&T Bell Laboratories Packet network architecture for providing rapid response time
NL8801033A (nl) 1988-04-21 1989-11-16 At & T & Philips Telecomm Schakelstelsel voor circuit- en/of pakketgeschakelde communicatie.
JPH024083A (ja) 1988-06-17 1990-01-09 Fujitsu Ltd 網間接続における統合課金方式
NL8801590A (nl) 1988-06-22 1990-01-16 Nederland Ptt Optisch netwerk waarbij transmissie, samenvoegen resp. scheiden van informatie- en stuursignalen en routering in het optische domein plaatsvinden.
DE3885753D1 (de) 1988-09-23 1993-12-23 Siemens Ag Verfahren und Schaltungsanordnung zum Übertragen von Sprachsignalen in einem Breitband-Kommunikationsnetz.
US5396491A (en) 1988-10-14 1995-03-07 Network Equipment Technologies, Inc. Self-routing switching element and fast packet switch
US5014266A (en) 1988-12-28 1991-05-07 At&T Bell Laboratories Circuit switching system for interconnecting logical links between packet switching networks
US5221983A (en) 1989-01-19 1993-06-22 Bell Communications Research, Inc. Passive photonic loop architecture employing wavelength multiplexing
US5020058A (en) 1989-01-23 1991-05-28 Stratacom, Inc. Packet voice/data communication system having protocol independent repetitive packet suppression
US5726984A (en) * 1989-01-31 1998-03-10 Norand Corporation Hierarchical data collection network supporting packetized voice communications among wireless terminals and telephones
US4969184A (en) 1989-02-02 1990-11-06 Alphanet Technology Corporation Data transmission arrangement
US4924616A (en) * 1989-03-24 1990-05-15 Bell Ross A Portable firearm rest
US4996685A (en) 1989-04-10 1991-02-26 Bell Communications Research, Inc. Technique for dynamically changing an ISDN connection during a host session
US5150357A (en) 1989-06-12 1992-09-22 Emil Hopner Integrated communications system
US5138615A (en) 1989-06-22 1992-08-11 Digital Equipment Corporation Reconfiguration system and method for high-speed mesh connected local area network
US5477364A (en) 1989-07-21 1995-12-19 British Telecommunications Public Limited Company Data transmission on optical networks
US5060305A (en) 1989-08-29 1991-10-22 The Trustees Of Princeton University Self clocked, self routed photonic switch
US5197067A (en) 1989-09-18 1993-03-23 Fujitsu Limited Packet communication system using a telephone switching network and a data flow control method
US5093827A (en) 1989-09-21 1992-03-03 At&T Bell Laboratories Control architecture of a multi-node circuit- and packet-switching system
US4962497A (en) 1989-09-21 1990-10-09 At&T Bell Laboratories Building-block architecture of a multi-node circuit-and packet-switching system
US5001702A (en) 1989-09-26 1991-03-19 At&T Bell Laboratories Packet switching network for multiple packet types
CA1331215C (en) 1989-09-29 1994-08-02 Andrew Lazlo Aczel Resource-decoupled architecture for a telecommunications switching system
US5050164A (en) 1989-10-31 1991-09-17 Bell Communications Research, Inc. Optical customer premises network
US5007070A (en) 1989-10-31 1991-04-09 Bell Communications Research, Inc. Service clock recovery circuit
JP2930624B2 (ja) 1989-11-17 1999-08-03 松下電送システム株式会社 Ｉｓｄｎ用端末装置
US5048081A (en) 1989-12-28 1991-09-10 At&T Bell Laboratories Arrangement for routing packetized messages
US5008929A (en) 1990-01-18 1991-04-16 U.S. Intelco Networks, Inc. Billing system for telephone signaling network
JPH03235555A (ja) 1990-02-13 1991-10-21 Hitachi Ltd データ通信装置及びデータ通信方式
JP2783630B2 (ja) 1990-02-15 1998-08-06 キヤノン株式会社 端末装置
US5359598A (en) 1990-06-22 1994-10-25 Unisys Corporation Voice server for digital communication network
US5231633A (en) 1990-07-11 1993-07-27 Codex Corporation Method for prioritizing, selectively discarding, and multiplexing differing traffic type fast packets
JPH0490645A (ja) 1990-08-03 1992-03-24 Mitsubishi Electric Corp 音声パケット組立分解装置
US5251205A (en) 1990-09-04 1993-10-05 Digital Equipment Corporation Multiple protocol routing
US5115431A (en) 1990-09-28 1992-05-19 Stratacom, Inc. Method and apparatus for packet communications signaling
US5241588A (en) 1990-12-18 1993-08-31 Bell Communications Research, Inc. Systems and processes providing programmable or customized customer telephone information services
US5223968A (en) 1990-12-20 1993-06-29 The United States Of America As Represented By The Secretary Of The Air Force First come only served communications network
WO1992014320A1 (en) 1991-02-01 1992-08-20 Republic Telcom Systems Corporation Packet switching communications system
US5351276A (en) 1991-02-11 1994-09-27 Simpact Associates, Inc. Digital/audio interactive communication network
US5153757A (en) 1991-02-27 1992-10-06 At&T Bell Laboratories Network control arrangement
US5341374A (en) 1991-03-01 1994-08-23 Trilan Systems Corporation Communication network integrating voice data and video with distributed call processing
US5128789A (en) 1991-03-06 1992-07-07 The United States Of America As Represented By The Secretary Of The Air Force Node for grid type single mode fiber optic local area network
US5218602A (en) 1991-04-04 1993-06-08 Dsc Communications Corporation Interprocessor switching network
DE69124596T2 (de) 1991-04-22 1997-08-21 Ibm Kollisionsfreies Einfügen und Entfernen von durchschaltevermittelten Kanälen in einer paketvermittelnden Übertragungsstruktur
GB9112898D0 (en) * 1991-06-14 1991-07-31 Digital Equipment Int Communication networks
US5268900A (en) 1991-07-05 1993-12-07 Codex Corporation Device and method for implementing queueing disciplines at high speeds
US5195090A (en) 1991-07-09 1993-03-16 At&T Bell Laboratories Wireless access telephone-to-telephone network interface architecture
US5572347A (en) 1991-07-30 1996-11-05 Alcatel Network Systems, Inc. Switched video architecture for an optical fiber-to-the-curb telecommunications system
US5181106A (en) 1991-07-31 1993-01-19 Alcatel Network Systems, Inc. Video line shelf arrangement in an optical fiber telecommunications network providing broadband switched video services
US5303229A (en) 1991-07-31 1994-04-12 Alcatel Network Systems, Inc. Optical network unit
US5544168A (en) 1991-08-02 1996-08-06 Gpt Limited ATM switching arrangement
EP0528085A1 (de) 1991-08-19 1993-02-24 Siemens Aktiengesellschaft Fernmeldenetz mit ATM- und STM-Vermittlung
JPH0563734A (ja) 1991-08-28 1993-03-12 Nec Corp データ通信装置
EP0533391A3 (en) 1991-09-16 1993-08-25 American Telephone And Telegraph Company Packet switching apparatus using pipeline controller
US5383181A (en) 1991-10-31 1995-01-17 Nec Corporation Packet switching system capable of reducing a delay time for each packet
GB2261799B (en) 1991-11-23 1995-04-19 Dowty Communications Ltd Packet transmission system
WO1993012624A1 (en) 1991-12-19 1993-06-24 Northern Telecom Limited Fibre optic telephone loop network
IT1252576B (it) 1991-12-20 1995-06-19 Italtel Spa Struttura di rete ottica passiva con elevata insensibilita' ai guasti
US5295137A (en) * 1992-02-12 1994-03-15 Sprint International Communications Corp. Connection establishment in a flat distributed packet switch architecture
US5295133A (en) 1992-02-12 1994-03-15 Sprint International Communications Corp. System administration in a flat distributed packet switch architecture
US5365521A (en) 1992-02-20 1994-11-15 Nippon Telegraph And Telephone Corporation Data transmission and transmission path setting among exchange modules in building block type exchanger
US5247571A (en) 1992-02-28 1993-09-21 Bell Atlantic Network Services, Inc. Area wide centrex
EP0559981A3 (en) 1992-03-11 1994-07-20 Intervoice Inc Fully digital voice response system
FR2689711B1 (fr) * 1992-04-03 1994-05-13 France Telecom Reseau de telecommunications.
US5555477A (en) 1992-04-08 1996-09-10 Hitachi, Ltd. Optical transmission system constructing method and system
US5572583A (en) 1992-04-17 1996-11-05 Bell Atlantic Advanced intelligent network with intelligent peripherals interfaced to the integrated services control point
FR2690799B1 (fr) 1992-04-30 1994-06-10 Cit Alcatel Systeme optique de raccordement d'installations d'abonne a un centre de commutation d'un reseau de telecommunication assurant des services interactifs et des services non interactifs.
CA2094410C (en) 1992-06-18 1998-05-05 Joshua Seth Auerbach Distributed management communications network
US5262906A (en) 1992-06-19 1993-11-16 Alcatel Network Systems, Inc. Message routing for SONET telecommunications maintenance network
US5477362A (en) 1992-09-09 1995-12-19 Hitachi, Ltd. Optical switching system
ES2100707T3 (es) 1992-09-14 1997-06-16 British Telecomm Red de comunicaciones distributiva y metodo.
CA2144953A1 (en) 1992-09-29 1994-04-14 Paul Baran Cell based wide area network alternative access telephone and data system
US5345444A (en) 1992-09-30 1994-09-06 At&T Bell Laboratories Chuted, growable packet switching arrangement
US5289303A (en) 1992-09-30 1994-02-22 At&T Bell Laboratories Chuted, optical packet distribution network
US5436898A (en) 1992-10-08 1995-07-25 International Business Machines Corporation Multi-media network bus
US5384840A (en) 1992-10-09 1995-01-24 At&T Corp. Telecommunications system SS7 signaling interface with signal transfer capability
US5485297A (en) 1992-10-09 1996-01-16 Alcatel N.V. Optical switching matrix
ATE260532T1 (de) 1992-10-15 2004-03-15 Canon Kk Optischer konzentrator und optisches übertragungsnetz mit einem derartigen konzentrator
US5327421A (en) 1992-11-06 1994-07-05 At&T Bell Laboratories Apparatus for interfacing between telecommunications call signals and broadband signals
US5396359A (en) * 1992-11-12 1995-03-07 The United States Of America As Represented By The Secretary Of The Air Force Node for grid type single mode fiber optic local area network using tunable filters
US5274635A (en) 1992-11-18 1993-12-28 Stratacom, Inc. Method and apparatus for aligning a digital communication data stream across a cell network
US5452289A (en) 1993-01-08 1995-09-19 Multi-Tech Systems, Inc. Computer-based multifunction personal communications system
US5812534A (en) 1993-01-08 1998-09-22 Multi-Tech Systems, Inc. Voice over data conferencing for a computer-based personal communications system
US5453986A (en) 1993-01-08 1995-09-26 Multi-Tech Systems, Inc. Dual port interface for a computer-based multifunction personal communication system
US5740164A (en) 1993-02-09 1998-04-14 Teledesic Corporation Traffic routing for satellite communication system
US5351286A (en) 1993-02-23 1994-09-27 Bell Communications Research, Inc. Method and system for billing an ISDN data user interconnection to the public switched telephone network
US5351146A (en) 1993-03-01 1994-09-27 At&T Bell Laboratories All-optical network architecture
US5479411A (en) 1993-03-10 1995-12-26 At&T Corp. Multi-media integrated message arrangement
US5592538A (en) 1993-03-10 1997-01-07 Momentum, Inc. Telecommunication device and method for interactive voice and data
DE69434078T2 (de) 1993-03-11 2005-11-03 At & T Corp. Optisches Netzwerk mit Endgerätfernabfrage und optische Netzwerkeinheit dafür, dass Wellenlängen transformiert
US5815295A (en) 1993-03-11 1998-09-29 Lucent Technologies Inc. Optical communication system with improved maintenance capabilities
US5381405A (en) 1993-03-18 1995-01-10 At&T Corp. Communications access network routing
US5689553A (en) 1993-04-22 1997-11-18 At&T Corp. Multimedia telecommunications network and service
US5420858A (en) 1993-05-05 1995-05-30 Synoptics Communications, Inc. Method and apparatus for communications from a non-ATM communication medium to an ATM communication medium
US5539884A (en) 1993-05-20 1996-07-23 Bell Communications Research, Inc. Intelligent broadband communication system and method employing fast-packet switches
US5353283A (en) 1993-05-28 1994-10-04 Bell Communications Research, Inc. General internet method for routing packets in a communications network
US5430719A (en) 1993-06-28 1995-07-04 Bellsouth Corporation Mediation of open advanced intelligent network interface by shared execution environment
US5701301A (en) 1993-06-28 1997-12-23 Bellsouth Corporation Mediation of open advanced intelligent network in SS7 protocol open access environment
EP0632625B1 (en) 1993-06-30 1996-10-30 International Business Machines Corporation Programmable high performance data communication adapter for high speed packet transmission networks
KR100304063B1 (ko) 1993-08-04 2001-11-22 썬 마이크로시스템즈, 인코포레이티드 2지점간상호접속통신유틸리티
US5446571A (en) 1993-09-10 1995-08-29 British Telecommunications, Plc Manchester code optical code recognition unit
GB2282018B (en) 1993-09-14 1998-03-18 Northern Telecom Ltd Optical communications network
US5600643A (en) 1993-09-23 1997-02-04 Bell Communications Research, Inc. Broadband intelligent telecommunications network and method providing enhanced capabilities for customer premises equipment
US5444709A (en) 1993-09-30 1995-08-22 Apple Computer, Inc. Protocol for transporting real time data
US5390184A (en) 1993-09-30 1995-02-14 Northern Telecom Limited Flexible scheduling mechanism for ATM switches
US5631897A (en) 1993-10-01 1997-05-20 Nec America, Inc. Apparatus and method for incorporating a large number of destinations over circuit-switched wide area network connections
US5581479A (en) 1993-10-15 1996-12-03 Image Telecommunications Corp. Information service control point, which uses different types of storage devices, which retrieves information as blocks of data, and which uses a trunk processor for transmitting information
US5590181A (en) 1993-10-15 1996-12-31 Link Usa Corporation Call-processing system and method
DE69429761T2 (de) 1993-11-16 2002-06-06 Fujitsu Ltd Netzwerkdrucker
US5881131A (en) 1993-11-16 1999-03-09 Bell Atlantic Network Services, Inc. Analysis and validation system for provisioning network related facilities
US5434913A (en) 1993-11-24 1995-07-18 Intel Corporation Audio subsystem for computer-based conferencing system
USH1641H (en) 1993-11-30 1997-04-01 Gte Mobile Communications Service Corporation Connection of mobile devices to heterogenous networks
US5473679A (en) * 1993-12-09 1995-12-05 At&T Corp. Signaling system for broadband communications networks
JPH07170264A (ja) 1993-12-14 1995-07-04 Nec Corp デジタル通話路網の構成方式
JPH07170288A (ja) 1993-12-15 1995-07-04 Hitachi Ltd 音声通信システムおよび音声通信方法
US5426636A (en) 1993-12-20 1995-06-20 At&T Corp. ATM distribution networks for narrow band communications
US5428607A (en) 1993-12-20 1995-06-27 At&T Corp. Intra-switch communications in narrow band ATM networks
US5422882A (en) 1993-12-20 1995-06-06 At&T Corp. ATM networks for narrow band communications
US5457684A (en) 1993-12-21 1995-10-10 At&T Ipm Corp. Delay-less signal processing arrangement for use in an ATM network
US5504743A (en) * 1993-12-23 1996-04-02 British Telecommunications Public Limited Company Message routing
US5625677A (en) 1993-12-30 1997-04-29 At&T Simultaneous voice and data communications
US5519694A (en) * 1994-02-04 1996-05-21 Massachusetts Institute Of Technology Construction of hierarchical networks through extension
US5423003A (en) 1994-03-03 1995-06-06 Geonet Limited L.P. System for managing network computer applications
US5544163A (en) 1994-03-08 1996-08-06 Excel, Inc. Expandable telecommunications system
US5418779A (en) * 1994-03-16 1995-05-23 The Trustee Of Columbia University Of New York High-speed switched network architecture
EP0676878A1 (en) * 1994-04-07 1995-10-11 International Business Machines Corporation Efficient point to point and multi point routing mechanism for programmable packet switching nodes in high speed data transmission networks
US5793762A (en) 1994-04-12 1998-08-11 U S West Technologies, Inc. System and method for providing packet data and voice services to mobile subscribers
US6181703B1 (en) * 1995-09-08 2001-01-30 Sprint Communications Company L. P. System for managing telecommunications
US5535195A (en) 1994-05-06 1996-07-09 Motorola, Inc. Method for efficient aggregation of link metrics
US5729544A (en) 1994-05-09 1998-03-17 Motorola, Inc. Method for transmitting data packets based on message type
JP3247540B2 (ja) 1994-05-12 2002-01-15 株式会社日立製作所 パケット化通信装置および切替え装置
ES2143632T3 (es) 1994-05-23 2000-05-16 British Telecomm Red de telecomunicaciones optica.
US5438614A (en) 1994-05-25 1995-08-01 U.S. Robotics, Inc. Modem management techniques
US5504606A (en) * 1994-06-01 1996-04-02 At&T Corp. Low power optical network unit
SE503317C2 (sv) 1994-06-13 1996-05-13 Ericsson Telefon Ab L M Sätt och väljarnod för att koppla STM-celler i en kretsemulerad ATM-väljare
NL9401050A (nl) 1994-06-24 1996-02-01 Nederland Ptt Werkwijze voor het verwerken van omgevingsafhankelijke toegangsnummers van spraakpostbussen, alsmede stelsel voor spraakpost met omgevingsafhankelijke toegangsnummers.
US5532856A (en) 1994-06-30 1996-07-02 Nec Research Institute, Inc. Planar optical mesh-connected tree interconnect network
US5502587A (en) * 1994-06-30 1996-03-26 At&T Corp. Network comprising a space division photonic switch and a terminal which forms an output signal from an input signal
US5521914A (en) 1994-07-21 1996-05-28 Newbridge Networks Corporation Switched access to frame relay
US5550906A (en) 1994-08-05 1996-08-27 Lucent Technologies Inc. Telecommunications feature server
US5530575A (en) 1994-09-09 1996-06-25 The Trustees Of Columbia University Systems and methods for employing a recursive mesh network with extraplanar links
US5553063A (en) 1994-09-12 1996-09-03 Dickson; William D. Voice over data communication system
US5592477A (en) 1994-09-12 1997-01-07 Bell Atlantic Network Services, Inc. Video and TELCO network control functionality
US5541917A (en) 1994-09-12 1996-07-30 Bell Atlantic Video and TELCO network control functionality
US5740231A (en) 1994-09-16 1998-04-14 Octel Communications Corporation Network-based multimedia communications and directory system and method of operation
US5621727A (en) 1994-09-16 1997-04-15 Octel Communications Corporation System and method for private addressing plans using community addressing
GB9418772D0 (en) 1994-09-16 1994-11-02 Ionica L3 Limited Digital telephony
US5550818A (en) 1994-09-19 1996-08-27 Bell Communications Research, Inc. System for wavelength division multiplexing/asynchronous transfer mode switching for network communication
US5502719A (en) * 1994-10-27 1996-03-26 Hewlett-Packard Company Path allocation system and method having double link list queues implemented with a digital signal processor (DSP) for a high performance fiber optic switch
US5528584A (en) 1994-10-27 1996-06-18 Hewlett-Packard Company High performance path allocation system and method with fairness insurance mechanism for a fiber optic switch
US5490007A (en) * 1994-10-31 1996-02-06 Hewlett-Packard Company Bypass switching and messaging mechanism for providing intermix data transfer for a fiber optic switch
US5825771A (en) 1994-11-10 1998-10-20 Vocaltec Ltd. Audio transceiver
US5570355A (en) 1994-11-17 1996-10-29 Lucent Technologies Inc. Method and apparatus enabling synchronous transfer mode and packet mode access for multiple services on a broadband communication network
US5613069A (en) 1994-12-16 1997-03-18 Tony Walker Non-blocking packet switching network with dynamic routing codes having incoming packets diverted and temporarily stored in processor inputs when network ouput is not available
US5526353A (en) 1994-12-20 1996-06-11 Henley; Arthur System and method for communication of audio data over a packet-based network
US5568475A (en) 1994-12-21 1996-10-22 Lucent Technologies Inc. ATM network architecture employing an out-of-band signaling network
CA2139081C (en) 1994-12-23 1999-02-02 Alastair Gordon Unified messaging system and method
US5546390A (en) 1994-12-29 1996-08-13 Storage Technology Corporation Method and apparatus for radix decision packet processing
US5537403A (en) 1994-12-30 1996-07-16 At&T Corp. Terabit per second packet switch having distributed out-of-band control of circuit and packet switching communications
US5692126A (en) 1995-01-24 1997-11-25 Bell Atlantic Network Services, Inc. ISDN access to fast packet data network
US5568786A (en) 1995-01-25 1996-10-29 Lynch; Patrick J. Checkmate communication system
JP3169523B2 (ja) 1995-01-27 2001-05-28 三菱電機株式会社 パーソナル通信装置
US5610744A (en) * 1995-02-16 1997-03-11 Board Of Trustees Of The University Of Illinois Optical communications and interconnection networks having opto-electronic switches and direct optical routers
US5659542A (en) 1995-03-03 1997-08-19 Intecom, Inc. System and method for signalling and call processing for private and hybrid communications systems including multimedia systems
US5594732A (en) 1995-03-03 1997-01-14 Intecom, Incorporated Bridging and signalling subsystems and methods for private and hybrid communications systems including multimedia systems
US5610904A (en) * 1995-03-28 1997-03-11 Lucent Technologies Inc. Packet-based telecommunications network
US5544161A (en) 1995-03-28 1996-08-06 Bell Atlantic Network Services, Inc. ATM packet demultiplexer for use in full service network having distributed architecture
US5684799A (en) 1995-03-28 1997-11-04 Bell Atlantic Network Services, Inc. Full service network having distributed architecture
US5706286A (en) 1995-04-19 1998-01-06 Mci Communications Corporation SS7 gateway
US5640446A (en) 1995-05-01 1997-06-17 Mci Corporation System and method of validating special service calls having different signaling protocols
US5737333A (en) 1995-06-23 1998-04-07 Lucent Technologies Inc. Method and apparatus for interconnecting ATM-attached hosts with telephone-network attached hosts
US5659541A (en) 1995-07-12 1997-08-19 Lucent Technologies Inc. Reducing delay in packetized voice
US5764736A (en) 1995-07-20 1998-06-09 National Semiconductor Corporation Method for switching between a data communication session and a voice communication session
US5610910A (en) 1995-08-17 1997-03-11 Northern Telecom Limited Access to telecommunications networks in multi-service environment
US5712903A (en) 1995-08-21 1998-01-27 Bell Atlantic Network Services, Inc. Split intelligent peripheral for broadband and narrowband services
IL115263A (en) 1995-09-12 1999-04-11 Vocaltec Ltd System and method for distributing multi-media presentations in a computer network
US5642421A (en) * 1995-09-15 1997-06-24 International Business Machines Corporation Encryption of low data content ATM cells
US5737331A (en) 1995-09-18 1998-04-07 Motorola, Inc. Method and apparatus for conveying audio signals using digital packets
US6009469A (en) 1995-09-25 1999-12-28 Netspeak Corporation Graphic user interface for internet telephony application
US6108704A (en) 1995-09-25 2000-08-22 Netspeak Corporation Point-to-point internet protocol
US5915008A (en) 1995-10-04 1999-06-22 Bell Atlantic Network Services, Inc. System and method for changing advanced intelligent network services from customer premises equipment
US20010040885A1 (en) 1995-10-13 2001-11-15 Howard Jonas Method and apparatus for transmitting and routing voice telephone calls over a packet switched computer network
FI955093A0 (fi) 1995-10-25 1995-10-25 Finland Telecom Oy Datornaetelettelefonsystem och foerfarande foer styrning av det
US6243373B1 (en) 1995-11-01 2001-06-05 Telecom Internet Ltd. Method and apparatus for implementing a computer network/internet telephone system
IL115967A (en) 1995-11-12 1999-05-09 Phonet Communication Ltd Network based distributed pbx system
US5579308A (en) 1995-11-22 1996-11-26 Samsung Electronics, Ltd. Crossbar/hub arrangement for multimedia network
US5805587A (en) 1995-11-27 1998-09-08 At&T Corp. Call notification feature for a telephone line connected to the internet
US5754641A (en) 1995-11-30 1998-05-19 Bell Atlantic Network Services, Inc. Method of screening outgoing calls via a video display
CN1087572C (zh) 1995-12-13 2002-07-10 北方电讯网络有限公司 集成蜂窝话音和数字分组数据电信系统及该系统的运行方法
US5881060A (en) 1996-05-30 1999-03-09 Northern Telecom Limited Integrated cellular voice and digital packet data telecommunications systems and methods for their operation
JP3644108B2 (ja) * 1995-12-19 2005-04-27 ソニー株式会社 通話システム、接続装置、通信端末装置及び通話方法
US7336649B1 (en) * 1995-12-20 2008-02-26 Verizon Business Global Llc Hybrid packet-switched and circuit-switched telephony system
US5712908A (en) 1995-12-22 1998-01-27 Unisys Corporation Apparatus and method for generating call duration billing records utilizing ISUP messages in the CCS/SS7 telecommunications network
US5809121A (en) 1995-12-29 1998-09-15 Mci Communications Corporation System and method for generating a network call identifier
US5764756A (en) 1996-01-11 1998-06-09 U S West, Inc. Networked telephony central offices
US5809128A (en) 1996-11-01 1998-09-15 Interactive Telecom Inc. Method and apparatus permitting notification and control of blocked incoming calls over a data network
US5732078A (en) 1996-01-16 1998-03-24 Bell Communications Research, Inc. On-demand guaranteed bandwidth service for internet access points using supplemental user-allocatable bandwidth network
WO1997027692A1 (en) 1996-01-23 1997-07-31 Firetalk, Inc. Internet telecommunications system
US5790538A (en) 1996-01-26 1998-08-04 Telogy Networks, Inc. System and method for voice Playout in an asynchronous packet network
AU1851397A (en) 1996-01-31 1997-08-22 Labs Of Advanced Technologies International Corporation Hybrid network for real-time phone-to-phone voice communications
US6173044B1 (en) 1996-02-06 2001-01-09 International Business Machines Corporation Multipoint simultaneous voice and data services using a media splitter gateway architecture
KR100923483B1 (ko) 1996-02-09 2009-10-27 아이-링크 시스템즈, 아이엔씨. 오디오 전송 시스템 및 방법
DE69615225T2 (de) 1996-02-21 2002-06-27 Ibm Verteilte architektur für dienste eines telefonsystems
US5710769A (en) 1996-02-29 1998-01-20 Lucent Technologies Inc. Merging the functions of switching and cross connect in telecommunications networks
GB2310970A (en) 1996-03-05 1997-09-10 Ibm Voice mail on the Internet
AU2202897A (en) 1996-03-06 1997-09-22 Joseph B. Thompson System for interconnecting standard telephony communications equipment to internet protocol networks
US5838665A (en) 1996-03-11 1998-11-17 Integrated Technology, Inc. Data network telephone adaptor device
DE69736340T2 (de) 1996-03-19 2007-07-12 Lucent Technologies Inc. Verfahren und Vorrichtung in einem integrierten Telekommunikationsnetzwerk zur Umsetzung von synchronen Schmallband-Signalen in nach dem asynchronen Übertragungsmodus arbeitende Signale
US5809022A (en) 1996-03-19 1998-09-15 Lucent Technologies Inc. Method and apparatus for converting synchronous narrowband signals into broadband asynchronous transfer mode signals
US6327258B1 (en) 1996-04-04 2001-12-04 Alcatel Usa Sourcing, L.P. Method and apparatus for routing internet calls
US6487200B1 (en) 1996-04-04 2002-11-26 At&T Corp. Packet telephone system
EP0893021A1 (en) 1996-04-12 1999-01-27 Nortel Networks Corporation Terminating data voice call architecture
US6069890A (en) * 1996-06-26 2000-05-30 Bell Atlantic Network Services, Inc. Internet telephone service
US6122255A (en) * 1996-04-18 2000-09-19 Bell Atlantic Network Services, Inc. Internet telephone service with mediation
US5802045A (en) * 1996-04-30 1998-09-01 Lucent Technologies Inc. Method of using a narrowband server to provide service features to broadband subscribers
TW357514B (en) 1996-06-04 1999-05-01 Ericsson Telefon Ab L M An access network over a dedicated medium
SE506775C2 (sv) 1996-06-04 1998-02-09 Ericsson Telefon Ab L M Sätt och anordning för samtidig telefon- och Internetförbindelse på en telefonlinje
US5680437A (en) 1996-06-04 1997-10-21 Motorola, Inc. Signaling system seven distributed call terminating processor
US5751706A (en) 1996-06-05 1998-05-12 Cignal Global Communications, Inc. System and method for establishing a call telecommunications path
WO1997050277A2 (en) 1996-06-25 1997-12-31 Northern Telecom Limited Method and architecture for providing telephony between data networks and pstn
US5799154A (en) 1996-06-27 1998-08-25 Mci Communications Corporation System and method for the remote monitoring of wireless packet data networks
US5793771A (en) 1996-06-27 1998-08-11 Mci Communications Corporation Communication gateway
US6298120B1 (en) * 1996-06-28 2001-10-02 At&T Corp. Intelligent processing for establishing communication over the internet
CA2180685C (en) 1996-07-08 2003-09-09 Wynn Quon Internet telephony gateway
US6332153B1 (en) 1996-07-31 2001-12-18 Vocaltec Communications Ltd. Apparatus and method for multi-station conferencing
GB9616589D0 (en) 1996-08-07 1996-09-25 Harper John Telephone system
US5815505A (en) 1996-08-13 1998-09-29 Advanced Micro Devices, Inc. Combined analog and digital communications device
US6584094B2 (en) * 1996-09-12 2003-06-24 Avaya Technology Corp. Techniques for providing telephonic communications over the internet
WO1998011704A2 (en) 1996-09-12 1998-03-19 Dialnet, Inc. Dedicated system and process for distributed communication on a packet-switched network
US5892764A (en) 1996-09-16 1999-04-06 Sphere Communications Inc. ATM LAN telephone system
KR100196491B1 (ko) 1996-09-23 1999-06-15 전찬구 인터넷 전화교환 장치
US6195357B1 (en) 1996-09-24 2001-02-27 Intervoice Limited Partnership Interactive information transaction processing system with universal telephony gateway capabilities
US5963551A (en) 1996-09-30 1999-10-05 Innomedia Pte Ltd. System and method for dynamically reconfigurable packet transmission
US5724412A (en) 1996-10-07 1998-03-03 U S West, Inc. Method and system for displaying internet identification on customer premises equipment
US5922047A (en) 1996-10-22 1999-07-13 Motorola, Inc. Apparatus, method and system for multimedia control and communication
US6028860A (en) 1996-10-23 2000-02-22 Com21, Inc. Prioritized virtual connection transmissions in a packet to ATM cell cable network
US6859525B1 (en) 1996-10-23 2005-02-22 Riparius Ventures, Llc Internet telephony device
SE510663C2 (sv) 1996-10-28 1999-06-14 Ericsson Telefon Ab L M Anordning och förfarande för kommunikation mellan datanät och telekommunikationsnät
WO1998019425A1 (en) 1996-10-29 1998-05-07 Mci Communications Corporation Method and architecture for a wide area network
CA2217838C (en) 1996-11-07 2003-07-29 At&T Corp. Wan-based voice gateway
US5954799A (en) 1996-11-07 1999-09-21 Northern Telecom Limited Access to telecommunications networks in a multi-service environment by mapping and exchanging control message between CPE adaptors and access server
US6128301A (en) 1996-11-07 2000-10-03 Nortel Networks Limited Architecture for distribution of voice over ATM networks
US5999525A (en) 1996-11-18 1999-12-07 Mci Communications Corporation Method for video telephony over a hybrid network
BR9714315A (pt) 1996-11-18 2000-02-08 Mci Communications Corp Arquitetura para sistema de comunicação.
US6909708B1 (en) 1996-11-18 2005-06-21 Mci Communications Corporation System, method and article of manufacture for a communication system architecture including video conferencing
US6754181B1 (en) 1996-11-18 2004-06-22 Mci Communications Corporation System and method for a directory service supporting a hybrid communication system architecture
US5867495A (en) 1996-11-18 1999-02-02 Mci Communications Corporations System, method and article of manufacture for communications utilizing calling, plans in a hybrid network
US7145898B1 (en) 1996-11-18 2006-12-05 Mci Communications Corporation System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture
US5867494A (en) 1996-11-18 1999-02-02 Mci Communication Corporation System, method and article of manufacture with integrated video conferencing billing in a communication system architecture
JP3085216B2 (ja) 1996-11-28 2000-09-04 日本電気株式会社 電話通信端末及びそれを使用した通信方法
JPH10164135A (ja) 1996-12-03 1998-06-19 Nippon Telegr & Teleph Corp <Ntt> 通信システム
US5917817A (en) 1996-12-06 1999-06-29 International Business Machines Corporation User invocation of services in public switched telephone network via parallel data networks
SE511342C2 (sv) 1996-12-09 1999-09-13 Telia Ab Metod och anordning för telefoni via Internet
SE516244C2 (sv) 1996-12-20 2001-12-10 Ericsson Telefon Ab L M Internet-SS7 gateway
US6169734B1 (en) 1996-12-31 2001-01-02 Mci Communications Corporation Internet phone set
US6829231B1 (en) 1996-12-31 2004-12-07 Mci Communications Corporation Internet phone system and directory search engine using same
EP0966815A4 (en) 1997-02-02 2001-12-12 Fonefriend Systems Inc INTERNET SWITCHING BOX, SYSTEM AND METHOD FOR INTERNET TELEPHONY
IL131102A0 (en) 1997-02-03 2001-01-28 Mci Communications Corp A communication system architecture
AU5979298A (en) 1997-02-03 1998-08-25 Omicron Telesystems, Inc. Fax over internet
SE511802C2 (sv) 1997-02-14 1999-11-29 Telia Ab Gatewaylokaliseringssystem för ett internet- telekommunikationssystem
EP1235415A3 (en) 1997-02-20 2006-01-04 Hewlett-Packard Company, A Delaware Corporation Provision of telecommunication services
IL120370A0 (en) 1997-03-04 1997-07-13 Shelcad Engineering Ltd Internet and intranet phone system
US6104711A (en) * 1997-03-06 2000-08-15 Bell Atlantic Network Services, Inc. Enhanced internet domain name server
US5933490A (en) 1997-03-12 1999-08-03 Bell Atlantic Network Services, Inc. Overload protection for on-demand access to the internet that redirects calls from overloaded internet service provider (ISP) to alternate internet access provider
US5889774A (en) 1997-03-14 1999-03-30 Efusion, Inc. Method and apparatus for selecting an internet/PSTN changeover server for a packet based phone call
WO1998042104A1 (en) 1997-03-16 1998-09-24 Vocaltec Communications Ltd. System and method for providing audio communication over an integrated switched telephone and computer network
US6075796A (en) 1997-03-17 2000-06-13 At&T Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony
US6104704A (en) 1997-03-20 2000-08-15 At&T Corp. Methods and apparatus for gathering and processing billing information for internet telephony
US6546005B1 (en) 1997-03-25 2003-04-08 At&T Corp. Active user registry
IT1293882B1 (it) 1997-04-14 1999-03-11 Sip Dispositivo e procedimento per la trasmissione di segnali digitali, particolarmente su sistemi di tipo dect.
EP0980623A1 (en) 1997-05-06 2000-02-23 Nortel Networks Corporation Call management apparatus and methods for handling calls during an internet session
US6324183B1 (en) * 1998-12-04 2001-11-27 Tekelec Systems and methods for communicating messages among signaling system 7 (SS7) signaling points (SPs) and internet protocol (IP) nodes using signal transfer points (STPS)
CA2304214C (en) * 1997-09-16 2006-05-23 Transnexus, Llc Internet telephony call routing engine
US6779030B1 (en) * 1997-10-06 2004-08-17 Worldcom, Inc. Intelligent network
US6134235A (en) * 1997-10-08 2000-10-17 At&T Corp. Pots/packet bridge
US6278707B1 (en) * 1998-01-07 2001-08-21 Mci Communications Corporation Platform for coupling a circuit-switched network to a data network
US6169735B1 (en) * 1998-04-30 2001-01-02 Sbc Technology Resources, Inc. ATM-based distributed virtual tandem switching system
US6304565B1 (en) * 1998-05-20 2001-10-16 At&T Corp. Method of completing long distance pots calls with IP telephony endpoints
US6457043B1 (en) 1998-10-23 2002-09-24 Verizon Laboratories Inc. Speaker identifier for multi-party conference
US6298062B1 (en) 1998-10-23 2001-10-02 Verizon Laboratories Inc. System providing integrated services over a computer network
US6031896A (en) * 1998-10-23 2000-02-29 Gte Laboratories Incorporated Real-time voicemail monitoring and call control over the internet
US6128304A (en) 1998-10-23 2000-10-03 Gte Laboratories Incorporated Network presence for a communications system operating over a computer network
US7116656B1 (en) 1998-10-23 2006-10-03 Verizon Laboratories Inc. Multi-line appearance telephony via a computer network
US6707797B1 (en) * 1998-10-23 2004-03-16 Verizon Corporate Services Group Inc. Multi-line telephony via network gateways
US6614781B1 (en) 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
DE202006016582U1 (de) 2006-10-26 2007-01-11 Chen, Jen-Lin, Cupertino Verpackung
EP2088922A1 (en) 2006-11-02 2009-08-19 Koninklijke Philips Electronics N.V. Ambient light reduction for optical tomography

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9582371B1 (en) 2015-12-09 2017-02-28 International Business Machines Corporation Balancing latency and consistency requirements during data replication

Also Published As

Publication number Publication date
US6614781B1 (en) 2003-09-02
US20120177195A1 (en) 2012-07-12
US8270421B2 (en) 2012-09-18
US20080025294A1 (en) 2008-01-31
EP2317711B1 (en) 2018-04-11
EP1131926A4 (en) 2005-08-31
EP2317711A1 (en) 2011-05-04
US8089958B2 (en) 2012-01-03
US7564840B2 (en) 2009-07-21
US20040022237A1 (en) 2004-02-05
CA2352961A1 (en) 2000-06-02
EP2317710A2 (en) 2011-05-04
EP2317710A3 (en) 2012-04-11
US20080013531A1 (en) 2008-01-17
US20130070757A1 (en) 2013-03-21
EP1131926A1 (en) 2001-09-12
WO2000031933A1 (en) 2000-06-02
US8693347B2 (en) 2014-04-08
US8036214B2 (en) 2011-10-11
CA2352961C (en) 2011-02-01
US20080025295A1 (en) 2008-01-31
AU1631900A (en) 2000-06-13
US8085761B2 (en) 2011-12-27

Similar Documents

Publication Publication Date Title
EP1131926B1 (en) Voice over data telecommunications network architecture
US7139263B2 (en) Voice over IP architecture
US6937713B1 (en) IP call forward profile
US6687360B2 (en) Personal IP follow-me service
US8711735B2 (en) Personal IP toll-free number
Greene et al. Media gateway control protocol architecture and requirements
US6775273B1 (en) Simplified IP service control
US6678265B1 (en) Local number portability database for on-net IP call
US6816469B1 (en) IP conference call waiting
US6680935B1 (en) Anonymous call rejection
Hamdi et al. Voice service interworking for PSTN and IP networks
WO2002075605A9 (en) Xml based transaction detail records
CA2289455A1 (en) A communication system architecture
CA2286132A1 (en) A system, method and article of manufacture for switched telephony communication
US8611522B2 (en) Telephone call processing method and apparatus
Cisco H.323 Applications
Cisco Index
Greene et al. RFC2805: Media Gateway Control Protocol Architecture and Requirements
Abu-awwad More over I want to pay special regards to my parents who are enduring these all expenses and supporting me in all events. I am nothing without their prayers. They also encouraged me in crises. I shall never forget their sacrifices for my education so that I can enjoy my successful life as they are expecting.
Rosen Network Working Group N. Greene Request for Comments: 2805 Nortel Networks Category: Informational M. Ramalho Cisco Systems
Taylor Gateway Control Protocol Version

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20010620

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL PAYMENT 20010621;LT PAYMENT 20010621;LV PAYMENT 20010621;MK PAYMENT 20010621;RO PAYMENT 20010621;SI PAYMENT 20010621

RIN1 Information on inventor provided before grant (corrected)

Inventor name: TERPSTRA, RICH

Inventor name: BAKER, BRUCE, W.

Inventor name: STEELE, RICK, D.

Inventor name: HERNANDEZ, ROBERT, L.

Inventor name: PETERSON, JON

Inventor name: DUGAN, ANDREW, JOHN

Inventor name: HIGGINS, STEVEN, P.

Inventor name: ELLIOTT, ISAAC, K.

RIC1 Information provided on ipc code assigned before grant

Ipc: 7H 04L 29/06 B

Ipc: 7H 04L 12/66 A

A4 Supplementary search report drawn up and despatched

Effective date: 20050714

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: LEVEL 3 COMMUNICATIONS, LLC

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20140519

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 686094

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140915

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: MARKS AND CLERK (LUXEMBOURG) LLP, CH

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 69945178

Country of ref document: DE

Effective date: 20141016

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 686094

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140903

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141204

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150105

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 69945178

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20141130

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

26N No opposition filed

Effective date: 20150604

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140903

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 19

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: LU

Payment date: 20181113

Year of fee payment: 20

Ref country code: NL

Payment date: 20181114

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20181113

Year of fee payment: 20

Ref country code: IE

Payment date: 20181109

Year of fee payment: 20

Ref country code: MC

Payment date: 20181109

Year of fee payment: 20

Ref country code: DE

Payment date: 20181106

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20181121

Year of fee payment: 20

Ref country code: CH

Payment date: 20181115

Year of fee payment: 20

Ref country code: FR

Payment date: 20181011

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 69945178

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MK

Effective date: 20191121

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20191121

REG Reference to a national code

Ref country code: IE

Ref legal event code: MK9A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20191122

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20191121

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG