US 6,563,918 B1Grant
Telecommunications system architecture for connecting a call
Issue Date:2003-05-13
•20 Claims
•9 Drawing Sheets
Abstract
An architecture for connecting a call comprises a call processor, a signaling interface, a call process control system (CPCS), and an interworking unit. The signaling interface receives, transmits, and processes call signaling so that call signaling is received into, or transported from, the architecture through the signaling interface. The call processor processes the call signaling to select connections for calls. The CPCS receives data fills from translations, processes the data to be in a format compatible with the call processor, and fills the data into tables in the call processor. The CPCS also interfaces through the signaling processor with other systems, such as accounting systems and operations centers. The interworking unit interworks user communications between time division multiplex and asynchronous transfer mode connections and between time division multiplex connections and other time division multiplex connections.
Metadata
Assignee
- Sprint Communications Company, LP
Inventors
- Tracy Lee Nelson
- William Lyle Wiley
- Royal Dean Howell
- Michael Joseph Gardner
- Albert Daniel DuRee
Application Information
Application Number:US 09/026,906
Filing Date:1998-02-20
Priority Date:1998-02-20
Art Unit:7
Classifications
IPC:
H04M 700H04L 1228
Field of Search:
379207023792210837922109379221133792293792303702593703853703952370396370397370400370401370402370409370426370465370466370467370468370522370524
Patent Drawings (9 sheets)
Description
RELATED APPLICATIONS
[0002] Not Applicable
FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
[0003] Not Applicable
MICROFICHE APPENDIX
[0004] Not Applicable
FIELD OF THE INVENTION
[0005] The present invention relates to the field of telecommunications call switching and transport in a system that provides asynchronous transfer mode connections.
BACKGROUND OF THE INVENTION
[0006] Broadband systems are being developed to provide telecommunications providers with many benefits, including more efficient use of network bandwidth and the ability to integrate voice, data, and video communications. Broadband systems provide telecommunications network users with increased capabilities at lower costs.
[0007] Telecommunications architectures provide call switching and call connections by processing signaling to determine the origination and destination of a call and by selecting a route or connection for the call. This call connection must be completed for local exchange companies as well as interexchange companies. In addition, the call is processed with services before, during, and after the call is connected. Some of these services include N00, calling card, and accounting system services.
[0008] Existing telecommunications architectures are not readily scaleable. Furthermore, it is not convenient to change the services provided by the devices in the architecture. Therefore, there is a need for a telecommunications architecture that is scaleable and that can be programmed and maintained easily by a service provider. There is a need for such an architecture to provide a myriad of intelligent network services in a cost efficient manner.
SUMMARY OF THE INVENTION
[0009] The present invention comprises a system for connecting a call comprising a call processor adapted to receive call information elements and to process the call information elements and call-associated data to select a connection for the call. The call processor transports a control message identifying the selected connection. A signaling interface is adapted to receive the call signaling, to process the call signaling to isolate the call information elements, and to transfer the call information elements to the call processor. A call process control system is adapted to manage the call-associated data and to exchange the call-associated data with the call processor. An interworking unit is adapted to receive the control message from the call processor, to receive user communications, and to interwork the user communications to the selected connection according to the control message.
[0010] The present invention further comprises a system for connecting a call comprising a call processor adapted to receive call information elements and to process the call information elements and call-associated data to select a connection for the call. The call processor transports a control message identifying the selected connection. A signaling interface is adapted to receive the call signaling, to process the call signaling to isolate the call information elements and to transfer the call information elements to the call processor. A call process control system is adapted to manage the call-associated data and to exchange the call-associated data with the call processor.
[0011] The present invention further comprises a method for connecting a call through an asynchronous transfer mode system comprising receiving call-associated data and managing the call-associated data to be used for processing information parameters to select a connection. The call-associated data is moved to a data structure in a call processor. The call signaling is received and processed to the isolate information parameters in the call signaling. The information parameters are moved from the call process control system to the call processor. The information parameters are processed in the call processor using the call-associated data to select a connection for the call and transported a control message identifying the selected connection.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] FIG. 1 is a block diagram of an architecture for connecting calls in accordance with one embodiment of the present invention.
[0013] FIG. 2 is a block diagram of an architecture for connecting calls with a plurality of call processors and with redundancy in accordance with one embodiment of the present invention.
[0014] FIG. 3 is a block diagram of the architecture of FIG. 1 interfacing with systems in accordance with an embodiment of the present invention.
[0015] FIG. 4 is a block diagram of a data structure having tables that are used in the call processor of FIG. 3.
[0016] FIG. 5 is a block diagram of additional tables that are used in the call processor of FIG. 3.
[0017] FIG. 6 is a table diagram of a trunk circuit table used in the call processor of FIG. 3.
[0018] FIG. 7 is a table diagram of a trunk group table used in the call processor of FIG. 3.
[0019] FIG. 8 is a table diagram of an exception circuit table used in the call processor of FIG. 3.
[0020] FIG. 9 is a table diagram of an automated number index table used in the call processor of FIG. 3.
[0021] FIG. 10 is a table diagram of a called number screening table used in the call processor of FIG. 3.
[0022] FIG. 11 is a table diagram of a local routing number table used in the call processor of FIG. 3.
[0023] FIG. 12 is a table diagram of a called number table used in the call processor of FIG. 3.
[0024] FIG. 13 is a table diagram of a routing table used in the call processor of FIG. 3.
[0025] FIG. 14 is a table diagram of a treatment table used in the call processor of FIG. 3.
[0026] FIG. 15 is a table diagram of a message table used in the call processor of FIG. 3.
[0027] FIG. 16 is a functional diagram of an asynchronous transfer mode interworking unit for use with a synchronous optical network system in accordance with the present invention.
[0028] FIG. 17 is a functional diagram of an asynchronous transfer mode interworking unit for use with a synchronous digital hierarchy system in accordance with the present invention.
DETAILED DESCRIPTION
[0029] Telecommunication systems have a number of communication devices in local exchange and interexchange environments that interact to provide call services to customers. Both traditional and intelligent network (IN) services and resources are used to process, route, or connect a call to a designated connection.
[0030] A call has user communications and call signaling. The user communications contain the caller's information, such as a voice communication or data communication, which is transported over a connection. Call signaling contains information that facilitates call processing, and it is communicated over a link. Call signaling contains, for example, information describing the called number and the calling number. Examples of call signaling are standardized signaling, such as signaling system #7 (SS7), C7, integrated services digital network (ISDN), and digital private network signaling system (DPNSS), which are based on ITU recommendation Q.933. A call can be connected to and from communication devices.
[0031] The present invention provides a telecommunications architecture for connecting calls in and between local exchange systems and interexchange systems. The telecommunications architecture provides IN call processing and is scaleable so that it can be applied in small and large systems.
[0032] FIG. 1 illustrates an architecture system 102 according to the present invention. Architecture system 102 comprises a call processor 104, a signaling interface 106, a call process control system (CPCS) 108, and an interworking unit 110. Architecture system 102 is connected to first communication device 112 and second communication device 114. CPCS 108 is connected to operations systems 116.
[0033] It will be appreciated that the elements of the architecture system 102 may be logical or physical entities. In addition, other elements may be connected to the architecture system, but are not shown for clarity. For example, signaling interface 106 may be linked to a signal transfer point (STP) or a service control point (SCP).
[0034] Call processor 104 is linked to CPCS 108 by link 118, to signaling interface 106 by link 120, and to interworking unit 110 by link 122. CPCS 108 is linked to signaling interface 106 by link 124, to interworking unit 110 by link 126, and to operations systems 116 by link 128. Link 130 extends between signaling interface 106 and first communications device 112. Another link 132 extends from signaling interface 106. In some cases, link 132 extends to second communication device 114. Interworking unit 110 is connected to first communication device 112 by connection 134 and to second communication device 114 by connection 136.
[0035] Links are used to transport call signaling and control messages. The term “link” as used herein means a transmission media that may be used to carry call signaling and control messages containing, for example, device instructions and data. A link can carry, for example, out-of-band signaling such as that used in SS7, C7, ISDN, DPNSS, BISDN, GR-303, via local area network (LAN), or data bus call signaling. A link can be, for example, an AAL5 data link, FDDI, ethernet, DS0, or DS1. In addition, a link, as shown in the figures, can represent a single physical link or multiple links, such as one link or a combination of links of ISDN, SS7, TCP/IP, or some other data link. The term “control message” as used herein means a control or signaling message, a control or signaling instruction, or a control or signaling signal, whether proprietary or standardized, that conveys information from one point to another.
[0036] Connections are used to transport user communications and other device information between communication devices and between elements and devices of architecture system 102. The term “connection” as used herein means transmission media that may be used to carry user communications between elements of architecture system 102 and to other devices. For example, a connection could carry a user's voice, computer data, or other communication device data. A connection can be associated with either in-band communications or out-of-band communications.
[0037] Call processor 104 includes a signaling platform that can receive and process call signaling. Call processor 104 has data tables which have call connection data and which are used to process the call signaling. Based on the processed call signaling, call processor 104 selects processing options, services, or resources for the user communications and generates and transmits control messages that identify the communication device, processing option, service, or resource that is to be used. Call processor 104 also selects virtual connections and circuit-based connections for call routing and generates and transports control messages that identify the selected connections.
[0038] Signaling interface 106 receives, processes, and transmits call signaling. Signaling interface 106 can obtain information from, and transmit information to, a communication device. Such information may be transferred, for example, as a transaction capabilities application part (TCAP) message in queries or responses. Signaling interface 106 also passes information to call processor 104 for processing and passes information from call processor 104 to other communication devices (not shown).
[0039] CPCS 108 is a management and administration system. CPCS 108 includes a user interface and an external systems interface into call processor 104. CPCS 108 serves as a collection point for call-associated data such as translations having call routing data, logs, operational measurement data, alarms, statistical information, accounting information, and other call data. CPCS 108 accepts data, such as the translations, from operations systems 116 and updates the data in the tables in call processor 104. CPCS 108 also provides configuration data to various elements of the architecture system 102 including call processor 104, signaling interface 106, and interworking unit 110. In addition, CPCS 108 provides for remote control of call monitoring and call tapping applications from call processor 104.
[0040] Interworking unit 110 interworks traffic between various protocols. Preferably, interworking unit 110 interworks between asynchronous transfer mode (ATM) traffic and non-ATM traffic. Interworking unit 110 operates in accordance with control messages received from call processor 104 over link 122. These control messages typically are provided on a call-by-call basis and typically identify an assignment between a DS0 and a VP/VC for which user communications are interworked. In some instances, interworking unit 110 may transport control messages which may include data.
[0041] Communication devices 112 and 114 may include customer premises equipment (CPE), a service platform, a switch, an exchange carrier, a remote digital terminal, an ATM device, or any other device capable of initiating, handling, or terminating a call. CPE may include, for example, a telephone, a computer, a facsimile machine, or a private branch exchange. A service platform can be, for example, any enhanced computer platform that is capable of processing calls. A remote digital terminal is a device that concentrates analog twisted pairs from telephones and other like devices and converts the analog signals to a digital format known as GR-303.
[0042] Operations systems 116 transports translations and other call-associated data to CPCS 108. In addition, operations systems 116 accepts call-associated data from CPCS 108. Operations systems 116 may include, for example, an alarm monitoring system that receives alarm data, an operations report system to receive trending data, an accounting system to receive accounting data, or a configuration system to transport routing translations or element configuration data to CPCS 108. Operations systems 116 may comprise other elements.
[0043] The system of FIG. 1 operates as follows. Translations and other data are transported to CPCS 108 from operations systems 116 over link 128. In addition, CPCS 108 transports data to operations systems 116 over link 128, if required.
[0044] CPCS 108 processes the data and organizes the data into tables that are identical to call processing tables located in call processor 104. Then, CPCS 108 data fills the call processing tables in call processor 104 over link 116. In addition, CPCS 108 transports data to any device or entity to which it is configured to transport the data. This data fill may be completed at any time, and updates may be transported from CPCS 108 to call processor 104.
[0045] If any configuration of call processor 104, signaling interface 106, or interworking unit 110 is required by CPCS 108, that configuration information is transported to the appropriate element. In addition, alarms from call processor 104, signaling interface 106, or interworking unit 110 are transported to CPCS 108.
[0046] First communication device 112 transports call signaling to signaling interface 106 over link 130. First communication device 112 transports the user communications to interworking unit 110 over connection 134.
[0047] Signaling interface 106 receives the call signaling and processes the call signaling. Signaling interface 106 passes call information elements received from the call signaling to call processor 104 over link 120.
[0048] Call processor 104 processes the call information elements to select a connection 136. The selected connection 136 is preferably a VP/VC. However, it will be appreciated that the selected connection also may be a DS0 or other time-division multiplex (TDM) connection. Call processor 104 sends a first control message to interworking unit 110 over link 122 identifying the selected connection 136 over which user communications will be transported. Call processor 104 also sends a second control message to signaling interface 106 over link 120 destined for another communication device identifying the selected connection 136 over which user communications are to be interworked. The other communication device may be, for example, another call processor or a switch which may handle call signaling.
[0049] Signaling interface 106 receives the second control message and processes the control message to place it into a transportable form. In some instances, the control message is converted to an SS7 message. Signaling interface 106 transports the second control message over link 132.
[0050] Interworking unit 110 receives user communications from first communication device 112 over connection 134 and the first control message from call processor 104 over link 122. Interworking unit 110 interworks the user communications between a TDM format and an ATM format according to the first control message. Therefore, interworking unit 110 converts user communications from TDM user communications to ATM cells that identify selected connection 136 and transports the ATM cells over the selected connection 136 to second communication device 114.
[0051] FIG. 2 illustrates an embodiment of an architecture system 202 according to the present invention that includes redundant elements. Redundant elements may be used to maintain call processing capability in the event a main element is defective or otherwise out of service and cannot complete its functions. Architecture system 202 may have N+1 protection.
[0052] FIG. 2 illustrates an architecture system 202 comprising a first main call processor 204, a first backup call processor 204A, a first main signaling interface 206, a first backup signaling interface 206A, a main CPCS 208, a backup CPCS 208A, a first main interworking unit 210, a first backup interworking unit 210A, a second main call processor 212, a second backup call processor 212A, a second main signaling interface 214, a second backup signaling interface 214A, a second main interworking unit 216, and a second backup interworking unit 216A. Architecture system 202 is connected to first communication device 218 and second communication device 220. The elements of architecture system 202 are the same as the elements of architecture system 102 of FIG. 1, and they are linked and connected as described in the text associated with FIG. 1. However, the links and connections are not referenced with a reference number for clarity.
[0053] Thus, for example, first backup call processor 204A has the same call processing capability, data tables, data structures, and data as first main call processor 204. If first main call processor 204 is unable to process the call information elements to select connections and to complete other processing, because the first main call processor is defective or otherwise is not operating correctly, then first backup call processor 204A may take over call processing without an interruption of service. Signaling interfaces 206, 206A, 214, and 214A, CPCSs 208 and 208A, interworking units 210, 210A, 216, and 216A, and second call processors 212 and 212A also have this redundant structure for their respective operations.
[0054] FIG. 3 more fully illustrates the architecture system 102 illustrated in FIG. 1. Other versions also are contemplated. In the embodiment depicted in FIG. 3, architecture system 102 includes a signaling interface 304, a CPCS 306, and a call processor 308. It will be appreciated that the elements of architecture system 102 may be constructed as modules in a single unit or as multiple units.
[0055] Signaling interface 304 is coupled externally to signaling systems—in particular to signaling systems having a message transfer part (MTP), an ISDN user part (ISUP), a signaling connection control part (SCCP), an intelligent network application part (INAP) and a TCAP. Signaling interface 304 preferably is a platform that comprises an MTP level 1310, an MTP level 2312, and MTP level 3314, an SCCP process 316, an ISUP process 318, and a TCAP process 320. Signaling interface 304 also has INAP functionality (not shown). Signaling interface 304 may be linked to a communication device 322. For example, communication device 322 may be an SCP which is queried by the signaling interface with an AIN 0.1 SCP TCAP query to obtain additional call-associated data. The answer message may have additional information parameters that are required to complete call processing. Communication device 322 also may be an STP or other device.
[0056] Signaling interface 304 is operational to transmit, process, and receive call signaling. The TCAP, SCCP, ISUP, and INAP functionality use the services of MTP to transmit and receive the messages. Preferably, signaling interface 304 transmits and receives SS7 messages for MTP, TCAP, SCCP, and ISUP. Together, this functionality is referred to as an “SS7 stack,” and it is well known. The software required by one skilled in the art to configure an SS7 stack is commercially available. One example is the OMNI SS7 stack from Dale, Gesek, McWilliams & Sheridan, Inc. (the DGM&S company).
[0057] The processes of the signaling interface 304 process information that is received in message signal units (MSUs) and convert the information to call information elements that are sent to call processor 308 to be processed. A call information element may be, for example, an ISUP IAM message parameter from the MSU. Signaling interface 304 strips the unneeded header information from the MSU to isolate the message information parameters and passes the parameters to call processor 308 as the call information elements. Examples of these parameters are the called number, calling number, and user service information. Other examples of messages with information elements are an ANM, an ACM, an REL, an RLC, and an INF. In addition, call information elements are transferred from call processor 308 back to signaling interface 304, and the information elements are reassembled into MSUs and transferred to a signaling point.
[0058] CPCS 306 comprises several data structures and interfaces. For example, CPCS 306 may comprise interfaces and structures to and for an operations system having an alarm monitoring system 324, an operations report system 326, an accounting system 328, and a configuration system 330. CPCS 306 also may have a human-machine interface (HMI) 332. Typically, the messages and data are sent to CPCS 306 through signaling interface 304, through HMI 332, or through the interfaces to the operations system. However, other methods and devices may be used.
[0059] CPCS 306 has data tables which have call connection data. CPCS 306 accepts data from configuration systems 330 and updates the data in the CPCS tables. The data from configuration systems 330 may include routing data, such as translations for the data fill in the call processing tables, and equipment configuration data. The data in the call processing tables is used to data fill similar tables in call processor 308. CPCS 306 receives the data and may process the data to make sure it is in the correct format prior to filling the tables in call processor 308. CPCS 306 maintains a current, historical, and prospective perspective of the tables that are located in call processor 308.
[0060] CPCS 306 also serves as a collection point for alarms. Alarm information is transferred to CPCS 306. CPCS 306 then transports alarm messages to the required communication device or alarm monitoring system 324. For example, CPCS 306 can transport alarms to an operations center.
[0061] HMI 332 allows a person to log onto CPCS 306 and to manage data tables or to review data tables in CPCS 306 or to provide maintenance services. Thus, HMI 332 allows access to CPCS 306 for active call processing and passive call processing.
[0062] Call processor 308 processes call signaling and controls an ATM interworking unit, such as an ATM interworking multiplexer (mux) that performs interworking of DS0s and VP/VCs. However, call processor 308 may control other communications devices and connections in other embodiments.
[0063] Call processor 308 receives and processes telecommunications call signaling, control messages, and customer data to select connections that establish communication paths for calls. In the preferred embodiment, the call processor processes SS7 signaling to select connections for a call. Call processing in the call processor and the associated maintenance that is performed for call processing is described in a U.S. Patent Application entitled “System and Method for Treating a Call for Call Processing” filed on the same date as this application, which is assigned to the same assignee as this patent application, and which is incorporated herein by reference.
[0064] In addition to selecting connections, call processor 308 performs many other functions in the context of call processing. It not only can control routing and select the actual connections, but it also can validate callers, control echo cancelers, generate accounting information, invoke intelligent network functions, access remote databases, manage traffic, and balance network loads. One skilled in the art will appreciate how the call processor described below can be adapted to operate in the above embodiments.
[0065] Call processor 308 comprises a control platform 334 and an application platform 336. Each platform 334 and 336 is coupled to the other platform.
[0066] Control platform 334 is comprised of various external interfaces including an interworking unit interface, an echo interface, a resource control interface, a call information interface and an operations interface. Control platform 334 is externally coupled to an interworking unit control, an echo control, a resource control, accounting, and operations. The interworking unit interface exchanges messages with at least one interworking unit. These messages comprise DS0 to VP/VC assignments, acknowledgments, and status information. The echo control interface exchanges messages with echo control systems. Messages exchanged with echo control systems might include instructions to enable or disable echo cancellation on particular DS0s, acknowledgments, and status information.
[0067] The resource control interface exchanges messages with external resources. Examples of such resources are devices that implement continuity testing, encryption, compression, tone detection/transmission, voice detection, and voice messaging. The messages exchanged with resources are instructions to apply the resource to particular DS0s, acknowledgments, and status information. For example, a message may instruct a continuity testing resource to provide a loopback or to send and detect a tone for a continuity test.
[0068] The call information interface transfers pertinent call information to a call information processing system, such as to CPCS 306. Typical call information includes various accounting information, such as the parties to the call, time points for the call, and any special features applied to the call. One skilled in the art will appreciate how to produce the software for the interfaces in control platform 334.
[0069] Application platform 336 processes signaling information from signaling interface 304 to select connections. The identity of the selected connections are provided to control platform 334 for the interworking unit interface. Application platform 336 is responsible for validation, translation, routing, call control, exceptions, screening, and error handling. In addition to providing the control requirements for the interworking unit, application platform 336 also provides requirements for echo control and resource control to the appropriate interface of the control platform 334. In addition, application platform 336 generates signaling information for transmission by signaling interface 304. The signaling information might be for ISUP, INAP, or TCAP messages to external network elements. Pertinent information for each call is stored in a call buffer information (CBI) location for the call. The CBI can be used for tracking and accounting the call.
[0070] Application platform 336 operates in general accord with the Basic Call Model (BCM) defined by the ITU. An instance of the BCM is created to handle each call. The BCM includes an originating process and a terminating process. Application platform 336 includes a service switching function (SSF) that is used to invoke the service control function (SCF). Typically, the SCF is contained in an SCP. The SCF is queried with TCAP or INAP messages transported by signaling interface 304 which are initiated with information from the SSF in application platform 336. The originating or terminating processes will access remote databases with intelligent network (IN) functionality via the SSF.
[0071] Software requirements for application platform 336 can be produced in specification and description language (SDL) defined in ITU-T Z.100. The SDL can be converted into C code. A real time case tool such as SDT from Telelogic, Inc. or Object Time from Object Time, Inc. can be used. Additional C and C++ code can be added as required to establish the environment.
[0072] Call processor 308 may include the above-described software loaded onto a computer. The computer may be a Tandem S4000 using the non-stop Unix operating system and conventional database systems. It may be desirable to utilize the multi-threading capability of a Unix operating system.
[0073] From FIG. 3, it can be seen that application platform 336 processes signaling information to control numerous systems and facilitate call connections and services. SS7 signaling is exchanged between call processor 308 and external components through signaling interface 304, and control information is exchanged with external systems through control platform 334. Advantageously, signaling interface 304, CPCS 306, and call processor 308 are not integrated into a switch central processing unit (CPU) that is coupled to a switching matrix. Unlike an SCP, the components of signaling processor 302 are capable of processing ISUP messages independently of TCAP queries.
SS7 Message Designations
[0074] SS7 messages are well known. Designations for various SS7 messages commonly are used. Those skilled in the art are familiar with the following message designations:
[0075] ACM—Address Complete Message
[0076] ANM—Answer Message
[0077] BLO—Blocking
[0078] BLA—Blocking Acknowledgment
[0079] CPG—Call Progress
[0080] CRG—Charge Information
[0081] CGB—Circuit Group Blocking
[0082] CGBA—Circuit Group Blocking Acknowledgment
[0083] GRS—Circuit Group Reset
[0084] GRA—Circuit Group Reset Acknowledgment
[0085] CGU—Circuit Group Unblocking
[0086] CGUA—Circuit Group Unblocking Acknowledgment
[0087] CQM—Circuit Group Query
[0088] CQR—Circuit Group Query Response
[0089] CRM—Circuit Reservation Message
[0090] CRA—Circuit Reservation Acknowledgment
[0091] CVT—Circuit Validation Test
[0092] CVR—Circuit Validation Response
[0093] CFN—Confusion
[0094] COT—Continuity
[0095] CCR—Continuity Check Request
[0096] EXM—Exit Message
[0097] INF—Information
[0098] INR—Information Request
[0099] IAM—Initial Address
[0100] LPA—Loop Back Acknowledgment
[0101] PAM—Pass Along
[0102] REL—Release
[0103] RLC—Release Complete
[0104] RSC—Reset Circuit
[0105] RES—Resume
[0106] SUS—Suspend
[0107] TCAP—Transaction Capabilities Application Part
[0108] UBL—Unblocking
[0109] UBA—Unblocking Acknowledgment
[0110] UCIC—Unequipped Circuit Identification Code.
Call Processor Tables
[0111] Call processing typically entails two aspects. First, an incoming or “originating” connection is recognized by an originating call process. For example, the initial connection that a call uses to enter a network is the originating connection in that network. Second, an outgoing or “terminating” connection is selected by a terminating call process. For example, the terminating connection is coupled to the originating connection in order to extend the call through the network. These two aspects of call processing are referred to as the originating side of the call and the terminating side of the call.
[0112] FIG. 4 depicts a data structure used by application platform 336 of FIG. 3 to execute the BCM. This is accomplished through a series of tables that point to one another in various ways. The pointers are typically comprised of next function and next index designations. The next function points to the next table, and the next index points to an entry or a range of entries in that table. The data structure has trunk circuit table 402, trunk group table 404, exception table 406, ANI table 408, called number screening table 410, location routing number (LRN) table 412, called number table 414, and routing table 416.
[0113] Trunk circuit table 402 contains information related to the connections. Typically, the connections are DS0 or ATM connections. Initially, trunk circuit table 402 is used to retrieve information about the originating connection. Later, the table is used to retrieve information about the terminating connection. When the originating connection is being processed, the trunk group number in trunk circuit table 402 points to the applicable trunk group for the originating connection in trunk group table 404.
[0114] Trunk group table 404 contains information related to the originating and terminating trunk groups. When the originating connection is being processed, trunk group table 404 provides information relevant to the trunk group for the originating connection and typically points to exception table 406.
[0115] Exception table 406 is used to identify various exception conditions related to the call that may influence the routing or other handling of the call. Typically, exception table 406 points to ANI table 408. Although, exception table 406 may point directly to trunk group table 404, called number table 414, or routing table 416.
[0116] ANI table 408 is used to identify any special characteristics related to the caller's number. The caller's number is commonly known as automatic number identification (ANI). ANI table 408 typically points to called number screening table 410. Although, ANI table 408 may point directly to trunk group table 404 or routing table 416.
[0117] Called number screening table 410 is used to provide the trigger detection point (TDP) for an AIN 0.1 SCP TCAP query. It is used, for example, with the local number portability (LNP) feature. Called number screening table 410 invokes a TCAP. According to the TCAP response, either LRN table 412 or called number table 414 is accessed.
[0118] LRN table 412 is used to identify routing requirements based on the called number for those calls that have a return response from an LNP query to an SCP, indicating that the called number is ported. LRN table 412 points to routing table 416.
[0119] Called number table 414 is used to identify routing requirements based on the called number. This will be the case for standard telephone calls. Called number table 414 typically points to routing table 416. Although, it may point to trunk group table 404.
[0120] Routing table 416 has information relating to the routing of the call for the various connections. Routing table 416 is entered from a pointer in the exception table 406, ANI table 408, LRN table 412, or called number table 414. Routing table 416 typically points to a trunk group in trunk group table 404.
[0121] When exception table 406, ANI table 408, called number table 414, or routing table 416 point to trunk group table 404, they effectively select the terminating trunk group. When the terminating connection is being processed, the trunk group number in trunk group table 404 and trunk circuit table 406 is the index that points to the trunk group index. The trunk group index contains the applicable terminating connection in trunk circuit table 404.
[0122] The terminating trunk circuit is used to extend the call. The trunk circuit is typically a VP/VC or a DS0. Thus, it can be seen that by migrating through the tables, a terminating connection can be selected for a call.
[0123] FIG. 5 is an overlay of FIG. 4. The tables from FIG. 4 are present, but for clarity, their pointers have been omitted. FIG. 5 illustrates additional tables that can be accessed from the tables of FIG. 4. These include a call processor ID table 502, a treatment table 504, a query/response table 506, and a message table 508.
[0124] Call processor ID table 502 contains various call processor SS7 point codes. It can be accessed from trunk group table 404, and it points back to trunk group table 404.
[0125] Treatment table 504 identifies various special actions to be taken in the course of call processing. This will typically result in the transmission of a release message (REL) and a cause value. Treatment table 504 can be accessed from trunk circuit table 402, trunk group table 404, exception table 406, ANI table 408, called number screening table 410, LRN table 412, called number table 414, routing table 416, and query/response table 506.
[0126] Query/response table 506 has information used to invoke the SCF. It can be accessed by trunk group table 404, exception table 406, ANI table 408, called number screening table 410, LRN table 412, called number table 414, and routing table 416. It points to trunk group table 404, exception table 406, ANI table 408, called number screening table 410, LRN table 412, called number table 414, routing table 416, and treatment table 504.
[0127] Message table 508 is used to provide instructions for signaling messages from the termination side of the call. It can be accessed by trunk group table 404 and points to trunk group table 404.
[0128] FIGS. 6-15 depict examples of the various tables described above. FIG. 6 depicts an example of the trunk circuit table. Initially, the trunk circuit table is used to access information about the originating circuit. Later in the processing, it is used to provide information about the terminating circuit. For originating circuit processing, the associated point code is used to enter the table. This is the point code of the switch or call processor associated with the originating circuit. For terminating circuit processing, the trunk group number is used to enter the table.
[0129] The table also contains the circuit identification code (CIC). The CIC identifies the circuit which is typically a DS0 or a VP/VC. Thus, the invention is capable of mapping the SS7 CICs to the ATM VP/VC. If the circuit is ATM, the VP and the VC also can be used for identification. The group member number is a numeric code that is used for terminating circuit selection. The hardware identifier identifies the location of the hardware associated with the originating circuit. The echo canceler (EC) identification (ID) entry identifies the echo canceler for the originating circuit.
[0130] The remaining fields are dynamic in that they are filled during call processing. The echo control entry is filled based on three fields in signaling messages: the echo suppresser indicator in the IAM or circuit reservation message (CRM), and the information transfer capability in the IAM. This information is used to determine if echo control is required on the call. The satellite indicator is filled with the satellite indicator in the IAM or CRM. It may be used to reject a call if too many satellites are used. The circuit status indicates if the given circuit is idle, blocked, or not blocked. The circuit state indicates the current state of the circuit, for example, active or transient. The time/date indicates when the idle circuit went idle.
[0131] FIG. 7 depicts an example of a trunk group table. During origination processing, the trunk group number from the trunk circuit table is used to key into the trunk table. Glare resolution indicates how a glare situation is to be resolved. Glare is dual seizure of the same circuit. If the glare resolution entry is set to “even/odd,” the network element with the higher point code controls the even circuits, and the network element with the lower point code controls the odd circuits. If the glare resolution entry is set to “all,” the call processor controls all of the circuits. If the glare resolution entry is set to “none,” the call processor yields. The continuity control entry lists the percent of calls requiring continuity tests on the trunk group.
[0132] Continuity control indicates whether continuity is to be checked. The common language location identifier (CLLI) entry is a Bellcore standardized entry. The satellite trunk group entry indicates that the trunk group uses a satellite. The satellite trunk group entry is used in conjunction with the satellite indicator field described above to determine if the call has used too many satellite connections and, therefore, must be rejected. The service indicator indicates if the incoming message is from a call processor (ATM) or a switch (TDM). The outgoing message index (OMI) points to the message table so that outgoing messages can obtain parameters. The associated number plan area (NPA) entry identifies the area code.
[0133] Selection sequence (SEL SEQ) indicates the methodology that will be used to select a connection. The selection sequence field designations tell the trunk group to select circuits based on the following: least idle, most idle, ascending, descending, clockwise, and counterclockwise. The hop counter is decremented from the IAM. If the hop counter is zero, the call is released. Automatic congestion control (ACC) active indicates whether or not congestion control is active. If automatic congestion control is active, the call processor may release the call. During termination processing, the next function and index are used to enter the trunk circuit table. Reattempt circuit indicates if an outgoing call can be reattempted on a different circuit within the same trunk group.
[0134] Default jurisdiction information parameter (JIP) is an NPA-NXX value that is used to identify the switch from which the call originates. If an ISUP JIP is not received in an IAM, the default JIP is the value recorded on the call processor CBI. Alternately, this field can hold a default LRN having a ten digit form of NPA-NXX-XXXX in which the first six digits can populate the JIP parameter. If an ISUP LRN is not received in an IAM, the default IAM is the value recorded on the call processor CBI. The next function and next index entries point to the next table.
[0135] FIG. 8 depicts an example of an exception table. The index is used as a pointer to enter the table. The carrier selection identification (ID) parameter indicates how the caller reached the network and is used for routing certain types of calls. The following are used for this field: spare or no indication, selected carrier identification code presubscribed and input by the calling party, selected carrier identification code presubscribed and not input by the calling party, selected carrier identification code presubscribed and no indication of input by the calling party, and selected carrier identification code not presubscribed and input by the calling party. The carrier identification (ID) indicates the network that the caller wants to use. This is used to route calls directly to the desired network.
[0136] The called party number nature of address differentiates between 0+ calls, 1+ calls, test calls, and international calls. For example, international calls might be routed to a pre-selected international carrier. The called party “digits from” and “digits to” focus further processing unique to a defined range of called numbers. The “digits from” field is a decimal number ranging from 1-15 digits. It can be any length and, if filled with less than 15 digits, is filled with 0s for the remaining digits. The “digits to” field is a decimal number ranging from 1-15 digits. It can be any length and, if filled with less than 15 digits, is filled with 9s for the remaining digits. The next function and next index entries point to the next table which is typically the ANI table.
[0137] FIG. 9 depicts an example of an ANI table. The index is used to enter the fields of the table. The calling party category differentiates among types of calling parties, for example, test calls, emergency calls, and ordinary calls. The calling party/charge number entry nature of address indicates how the ANI is to be obtained. The following is the table fill that is used in this field: unknown, unique subscriber numbers, ANI not available or not provided, unique national number, ANI of the called party included, ANI of the called party not included, ANI of the called party includes national number, non-unique subscriber number, non-unique national number, non-unique international number, test line test code, and all other parameter values.
[0138] The “digits from” and “digits to” focus further processing unique to ANI within a given range. The data entry indicates if the ANI represents a data device that does not need echo control. Originating line information (OLI) differentiates among ordinary subscriber, multiparty line, ANI failure, station level rating, special operator handling, automatic identified outward dialing, coin or non-coin call using database access, 800\888 service call, coin, prison/inmate service, intercept (blank, trouble, and regular), operator handled call, outward wide area telecommunications service, telecommunications relay service (TRS), cellular services, private paystation, and access for private virtual network types of service. The next function and next index point to the next table which is typically the called number table.
[0139] FIG. 10 depicts an example of a called number screening table. The index is used to enter the table. The nature of address entry indicates the type of dialed number, for example, national versus international. The “digits from” and “digits to” entries focus further processing unique to a range of called numbers. This is where the TCAP response information is incorporated in the call processing flow. This is where the trigger occurs for an LNP TCAP query launch. The processing follows the processing logic of the “digits from” and “digits to” fields in FIG. 8. The next function and next index point to the next table which is typically either the called number table or the LRN table.
[0140] FIG. 11 depicts an example of an LRN table. This table will perform the same function as the called number table for those calls that are identified as ported based upon an LNP query response. The index is used to enter the table. The nature of address entry indicates the type of dialed number, for example, national versus international. In an LRN case, the value is a national number. The “digits from” and “digits to” entries focus further processing unique to a range of called numbers. This is where the TCAP response information is incorporated in the call processing flow. The processing follows the processing logic of the “digits from” and “digits to” fields in FIG. 8. The next function and next index point to the next table which is typically the routing table.
[0141] FIG. 12 depicts an example of a called number table. The index is used to enter the table. The called number nature of address entry indicates the type of dialed number, for example, national versus international. The “digits from” and “digits to” entries focus further processing unique to a range of called numbers, and they are used in the LRN table check process. The processing follows the processing logic of the “digits from” and “digits to” fields in FIG. 8. The next function and next index point to the next table which is typically the routing table.
[0142] FIG. 13 depicts an example of the routing table. The index is used to enter the table. The transit network selection (TNS) network identification (ID) plan indicates the number of digits to use for the CIC. The transit network selection “digits” field defines the numbers to identify an international carrier. The circuit code indicates the need for an operator on the call. The next function, next index, and signal route entries in the routing table are used to identify a trunk group. The second and third next function/index/signal route entries define alternate routes. The third next function entry also can point back to another set of next functions in the routing table in order to expand the number of alternate route choices. The only other entries allowed are pointers to the treatment table. If the routing table points to the trunk group table, then the trunk group table typically points to a trunk circuit in the trunk circuit table. The yield from the trunk circuit table is the terminating connection for the call.
[0143] It can be seen from FIGS. 6-13 that the tables can be configured and relate to one another in such a way that call processes can enter the trunk circuit table for the originating connection and can traverse through the tables by keying on information and using pointers. The yield of the tables is typically a terminating connection identified by the trunk circuit table. In some cases, treatment is specified by the treatment table instead of a connection. If, at any point during the processing, a trunk group can be selected, processing may proceed directly to the trunk group table for terminating circuit selection. For example, it may be desirable to route calls from a particular ANI over a particular set of trunk groups. In this case, the ANI table would point directly to the trunk group table, and the trunk group table would point to the trunk circuit table for a terminating circuit. The default path through the tables is: trunk circuit, trunk group, exception, ANI, called number screening, called number, routing, trunk group, and trunk circuit.
[0144] FIG. 14 depicts an example of a treatment table. Either the index or the message received cause number are filled and are used to enter the table. If the index is filled and used to enter the table, the general location, coding standard, and cause value indicator are used to generate an SS7 REL. The message received cause value entry is the cause value in a received SS7 message. If the message received cause value is filled and used to enter the table, then the cause value from that message is used in an REL from the call processor. The next function and next index point to the next table.
[0145] FIG. 15 depicts an example of a message table. This table allows the call processor to alter information in outgoing messages. Message type is used to enter the table, and it represents the outgoing standard SS7 message type. The parameter is the pertinent parameter within the outgoing SS7 message. The indexes point to various entries in the trunk group table and determine if parameters are passed unchanged, omitted, or modified in the outgoing messages.
The ATM Interworking Unit
[0146] FIG. 16 shows one embodiment of an interworking unit which is an ATM interworking unit 1602 suitable for the present invention for use with a SONET system, but other interworking units that support the requirements of the invention also are applicable. ATM interworking unit 1602 may receive and transmit in-band and out-of-band calls.
[0147] ATM interworking unit 1602 has control interface 1604, OC-N/STS-N interface 1606, DS3 interface 1608, DS1 interface 1610, DS0 interface 1612, signal processor 1614, ATM adaptation layer (AAL) 1616, OC-M/STS-M interface 1618, and ISDN/GR-303 interface 1620. As used herein in conjunction with OC or STS, “N” refers to an integer, and “M” refers to an integer.
[0148] Control interface 1604 receives control messages originating from signaling processor 1622, identifies DS0 and virtual connection assignments in control messages, and provides these assignments to AAL 1616 for implementation. Control messages are received over an ATM virtual connection and through OC-M/STS-M interface 1618 to control interface 1604 or directly through control interface 1604 from a link.
[0149] OC-N/STS-N interface 1606, DS3 interface 1608, DS1 interface 1610, DS0 interface 1612, and ISDN/GR-303 interface 1620 each can receive user communications from communication device 1624. Likewise, OC-M/STS-M interface 1618 can receive user communications from communication device 1626.
[0150] OC-N/STS-N interface 1606 receives OC-N formatted user communications and STS-N formatted user communications and converts the user communications to the DS3 format. DS3 interface 1608 receives user communications in the DS3 format and converts the user communications to the DSI format. DS3 interface 1608 can receive DS3s from OC-N/STS-N interface 1606 or from an external connection. DS1 interface; 1610 receives the user communications in the DS1 format and converts the user communications to the DS0 format. DS1 interface 1610 receives DS1s from DS3 interface 1608 or from an external connection. DS0 interface 1612 receives user communications in the DS0 format and provides an interface to AAL 1616. ISDN/GR.303 interface 1620 receives user communications in either the ISDN format or the GR.303 format and converts the user communications to the DS0 format. In addition, each interface may transmit user communications in like manner to communication device 1624.
[0151] OC-M/STS-M interface 1618 is operational to receive ATM cells from AAL 1616 and to transmit ATM cells over the connection to communication device 1626. OC-M/STS-M interface 1618 also may receive ATM cells in the OC format or the STS format and transmit them to AAL 1616.
[0152] AAL 1616 comprises a convergence sublayer and a segmentation and reassembly (SAR) sublayer. AAL 1616 obtains the identity of the DS0 and the ATM VP/VC from control interface 1604. AAL 1616 is operational to convert between the DS0 format and the ATM format. AALs are well known in the art; information about AALs is provided by International Telecommunications Union (ITU) document I.363, which is incorporated herein by reference. An AAL for voice calls is described in U.S. Pat. No. 5,606,553 entitled “Cell Processing for Voice Transmission” which is incorporated herein by reference.
[0153] Calls with multiple 64 Kilo-bits per second (Kbps) DS0s are known as N×64 calls. If desired, AAL 1616 can be configured to accept control messages through control interface 1604 for N×64 calls. ATM interworking unit 1602 is able to interwork, multiplex, and demultiplex for multiple DS0s. Techniques for processing VP/VCs are disclosed in commonly assigned U.S. patent application Ser. No. 08/653,852, filed on May 28, 1996, and entitled “Telecommunications System with a Connection Processing System,” and which is incorporated herein by reference.
[0154] DS0 connections are bidirectional, and ATM connections are typically uni-directional. Therefore, two virtual ATM connections in opposing directions typically will be required for each DS0. Those skilled in the art will appreciate how this can be accomplished in the context of the invention. For example, the cross-connect can be provisioned with a second set of VP/VCs in the opposite direction as the original set of VP/VCs.
[0155] In some embodiments, it may be desirable to incorporate digital signal processing capabilities at the DS0 level. It may also be desired to apply echo cancellation to selected DS0 circuits. In these embodiments, signal processor 1614 is included either separately (as shown) or as a part of DS0 interface 1612. Signaling processor 1622 is configured to send control messages to ATM interworking unit 1602 to implement particular features on particular DS0 circuits. Alternatively, lookup tables may be used to implement particular features for particular circuits or VP/VCs.
[0156] FIG. 17 shows another embodiment of an interworking unit which is an ATM interworking unit 1702 suitable for the present invention for use with an SDH system. ATM interworking unit 1702 has control interface 1704, STM-N electrical/optical (E/O) interface 1706, E3 interface 1708, E1 interface 1710, E0 interface 1712, signal processor 1714, AAL 1716, STM-M electrical/optical (E/O) interface 1718, and digital private network signaling system (DPNSS) interface 1720. As used herein in conjunction with STM, “N” refers to an integer, and “M” refers to an integer.
[0157] Control interface 1704 receives control messages from the signaling processor 1722, identifies E0 and virtual connection assignments in the control messages, and provides these assignments to AAL 1716 for implementation. The control messages are received over an ATM virtual connection and through STM-M interface 1718 to control interface 1604 or directly through control interface 1604 from a link.
[0158] STM-N E/O interface 1706, E3 interface 1708, E1 interface 1710, E0 interface 1712, and DPNSS interface 1720 each can receive user communications from second communication device 1724. Likewise, STM-M E/O interface 1718 can receive user communications from third communication device 1726.
[0159] STM-N E/O interface 1706 receives STM-N electrical or optical formatted user communications and converts the user communications from STM-N electrical or STM-N optical format to E3 format. E3 interface 1708 receives user communications in the E3 format and converts the user communications to the E1 format. E3 interface 1708 can receive E3s from STM-N E/O interface 1706 or from an external connection. El interface 1710 receives user communications in the E1 format and converts the user communications to the E0 format. E1 interface 1710 receives E1s from STM-N E/O interface 1706 or E3 interface 1708 or from an external connection. E0 interface 1712 receives user communications in the E0 format-and provides an interface to AAL 1716. DPNSS interface 1720 receives user communications in the DPNSS format and converts the user communications to the E0 format. In addition, each interface may transmit user communications in a like manner to communication device 1724.
[0160] STM-M E/O interface 1718 is operational to receive ATM cells from AAL 1716 and to transmit ATM cells over the connection to communication device 1726. STM-M E/O interface 1718 may also receive ATM cells in the STM-M E/O format and transmit them to AAL 1716.
[0161] AAL 1716 comprises both a convergence sublayer and a segmentation and reassembly (SAR) sublayer. AAL 1716 obtains the identity of the E0 and the ATM VP/VC from,control interface 1704. AAL 1716 is operational to convert between the E0 format and the ATM format, either in response to a control instruction or without a control instruction. AAL's are well known in the art. If desired, AAL 1716 can be configured to receive control messages through control interface 1704 for N×64 user communications.
[0162] E0 connections are bidirectional and ATM connections typically are unidirectional. As a result, two virtual connections in opposing directions typically will be required for each E0. As described above, those skilled in the art will appreciate how this can be accomplished in the context of the invention.
[0163] In some instances, it may be desirable to incorporate digital signal processing capabilities at the E0 level. Also, it may be desirable to apply echo cancellation. In these embodiments, signal processor 1714 is included either separately (as shown) or as a part of E0 interface 1712. Signaling processor 1722 is configured to send control messages to ATM interworking unit 1702 to implement particular features on particular circuits. Alternatively, lookup tables may be used to implement particular features for particular circuits or VP/VCs.
[0164] Those skilled in the art will appreciate that variations from the specific embodiments disclosed above are contemplated by the invention. The invention should not be restricted to the above embodiments, but should be measured by the following claims.
Claims
What is claimed is:
1. A communication system comprising:
a control system including control system data tables and configured to receive and process call routing data to fill the control system data tables with the call routing data, and to transfer the call routing data from the control system data tables to call processor data tables;
a call processor including the call processor data tables and configured to process signaling information for a call based on the call routing data in the call processor data tables to transfer a control message for the call indicating a first connection and a second connection; and
an interworking unit configured to receive the control message, and in response to the control message, receive user communications in a first format from a first connection, convert the user communications to a second format, and transfer the user communications in the second format over the second connection.
2. The communication system of claim 1 wherein the control system is configured to maintain the control system data tables to format the call routing data for the call processor data tables.
3. The communication system of claim 1 wherein the control system data tables and the call processor data tables are identical.
4. The communication system of claim 1 wherein the control system includes a user interface configured to allow a user to view the control system data tables.
5. The communication system of claim 1 wherein the control system is further configured to transfer the call routing data from the control system data tables to redundant data tables, and further comprising a redundant processor including the redundant data tables and configured to process the signaling information for the call based on the call routing data in the redundant data tables to transfer the control message for the call.
6. The communication system of claim 1 wherein the control system data tables and the call processor data tables each include a called number table.
7. The communication system of claim 1 wherein the call processor is configured to transfer accounting information for the call to the control system.
8. The communication system of claim 1 wherein the call processor is configured to transfer alarm information to the control system.
9. The communication system of claim 1 wherein the first connection comprises a DS0 connection.
10. The communication system of claim 1 wherein the second connection comprises a virtual connection.
11. A method of operating a communication system comprising:
in a control system including control system data tables, receiving and processing call routing data to fill the control system data tables with the call routing data, and transferring the call routing data from the control system data tables to call processor data tables;
in a call processor including the call processor data tables, processing signaling information for a call based on the call routing data in the call processor data tables to transfer a control message for the call indicating a first connection and a second connection; and
in an interworking unit, receiving the control message, and in response to the control message, receiving user communications in a first format from a first connection, converting the user communications to a second format, and transferring the user communications in the second format over the second connection.
12. The method of claim 11 wherein receiving and processing the call routing data to fill the control system data tables comprises formatting the call routing data for the call processor data tables.
13. The method of claim 11 wherein the control system data tables and the call processor data tables are identical.
14. The method of claim 11 wherein the control system includes a user interface, and further comprising allowing a user to view the control system data tables.
15. The method of claim 11 further comprising transferring the call routing data from the control system data tables to redundant data tables, and in a redundant processor including the redundant data tables, processing the signaling information for the call based on the call routing data in the redundant data tables to transfer the control message for the call.
16. The method of claim 11 wherein the control system data tables and the call processor data tables each include a called number table.
17. The method of claim 11 further comprising transferring accounting information for the call from the call processor to the control system.
18. The method of claim 11 further comprising transferring alarm information for the call from the call processor to the control system.
19. The method of claim 11 wherein the first connection comprises a DS0 connection.
20. The method claim 11 wherein the second connection comprises a virtual connection.
Patent Citations (188)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4201889(A) | 1980-05-01 | Lawrence et al. | Applicant |
| US4310727(A) | 1982-01-01 | Lawser | Applicant |
| US4348554(A) | 1982-09-01 | Asmuth | Applicant |
| US4453247(A) | 1984-06-01 | Suzuki et al. | Applicant |
| US4554659(A) | 1985-11-01 | Blood et al. | Applicant |
| US4565903(A) | 1986-01-01 | Riley | Applicant |
| US4683563(A) | 1987-07-01 | Rouse et al. | Applicant |
| US4720850(A) | 1988-01-01 | Oberlander | Applicant |
| US4730312(A) | 1988-03-01 | Johnson | Applicant |
| US4736364(A) | 1988-04-01 | Basso et al. | Applicant |
| US4748658(A) | 1988-05-01 | Gopal | Applicant |
| US4763317(A) | 1988-08-01 | Lehman | Applicant |
| US4823338(A) | 1989-04-01 | Chan et al. | Applicant |
| US4853955(A) | 1989-08-01 | Thorn et al. | Applicant |
| US4896319(A) | 1990-01-01 | Lidinsky et al. | Applicant |
| US4916690(A) | 1990-04-01 | Barri | Applicant |
| US4926416(A) | 1990-05-01 | Weik | Applicant |
| US4979118(A) | 1990-12-01 | Kheradpir | Applicant |
| US4985889(A) | 1991-01-01 | Frankish et al. | Applicant |
| US4991204(A) | 1991-02-01 | Yamamoto et al. | Applicant |
| US4993104(A) | 1991-02-01 | Gordon | Applicant |
| US5003584(A) | 1991-03-01 | Benyacar | Applicant |
| US5018191(A) | 1991-05-01 | Catron et al. | Applicant |
| US5048081(A) | 1991-09-01 | Gavaras | Applicant |
| US5058104(A) | 1991-10-01 | Yonehara et al. | Applicant |
| US5067123(A) | 1991-11-01 | Hyodo et al. | Applicant |
| US5084867(A) | 1992-01-01 | Tachibana et al. | Applicant |
| US5089954(A) | 1992-02-01 | Rago | Applicant |
| US5091903(A) | 1992-02-01 | Schrodi | Applicant |
| US5101404(A) | 1992-03-01 | Kunimoto et al. | Applicant |
| US5115431(A) | 1992-05-01 | Williams et al. | Applicant |
| US5163057(A) | 1992-11-01 | Grupp | Applicant |
| US5168492(A) | 1992-12-01 | Beshai et al. | Applicant |
| US5185743(A) | 1993-02-01 | Murayama | Applicant |
| US5193110(A) | 1993-03-01 | Jones et al. | Applicant |
| US5204857(A) | 1993-04-01 | Obara | Applicant |
| US5216669(A) | 1993-06-01 | Hofstetter et al. | Applicant |
| US5218602(A) | 1993-06-01 | Grant et al. | Applicant |
| US5231631(A) | 1993-07-01 | Buhrke et al. | Applicant |
| US5231633(A) | 1993-07-01 | Hluchyi et al. | Applicant |
| US5233607(A) | 1993-08-01 | Barwig et al. | Applicant |
| US5239539(A) | 1993-08-01 | Uchida et al. | Applicant |
| US5249178(A) | 1993-09-01 | Kurano et al. | Applicant |
| US5251255(A) | 1993-10-01 | Epley | Applicant |
| US5253247(A) | 1993-10-01 | Hirose et al. | Applicant |
| US5255266(A) | 1993-10-01 | Watanabe et al. | Applicant |
| US5258752(A) | 1993-11-01 | Fukaya et al. | Applicant |
| US5258979(A) | 1993-11-01 | Oomuro et al. | Applicant |
| US5268895(A) | 1993-12-01 | Topper | Applicant |
| US5271010(A) | 1993-12-01 | Miyake | Applicant |
| US5274680(A) | 1993-12-01 | Sorton et al. | Applicant |
| US5278889(A) | 1994-01-01 | Papanicolaou et al. | Applicant |
| US5282244(A) | 1994-01-01 | Fuller et al. | Applicant |
| US5285441(A) | 1994-02-01 | Bansal et al. | Applicant |
| US5291479(A) | 1994-03-01 | Vaziri et al. | Applicant |
| US5306318(A) | 1994-04-01 | Bachhuber et al. | Applicant |
| US5311509(A) | 1994-05-01 | Heddes et al. | Applicant |
| US5317562(A) | 1994-05-01 | Nardin et al. | Applicant |
| US5323389(A) | 1994-06-01 | Bitz et al. | Applicant |
| US5327421(A) | 1994-07-01 | Hiller et al. | Applicant |
| US5327433(A) | 1994-07-01 | Hall | Applicant |
| US5329308(A) | 1994-07-01 | Binns et al. | Applicant |
| US5339318(A) | 1994-08-01 | Tanaka | Applicant |
| US5345443(A) | 1994-09-01 | D'Ambrogio et al. | Applicant |
| US5345445(A) | 1994-09-01 | Hiller | Applicant |
| US5345446(A) | 1994-09-01 | Hiller | Applicant |
| US5357510(A) | 1994-10-01 | Norizuki et al. | Applicant |
| US5363433(A) | 1994-11-01 | Isono | Applicant |
| US5365524(A) | 1994-11-01 | Hiller et al. | Applicant |
| US5367566(A) | 1994-11-01 | Moe et al. | Applicant |
| US5373504(A) | 1994-12-01 | Tanaka et al. | Applicant |
| US5375124(A) | 1994-12-01 | D'Ambrogio | Applicant |
| US5377186(A) | 1994-12-01 | Wegner | Applicant |
| US5384771(A) | 1995-01-01 | Isidoro et al. | Applicant |
| US5384840(A) | 1995-01-01 | Blatchford et al. | Applicant |
| US5392402(A) | 1995-02-01 | Robrock | Applicant |
| US5394393(A) | 1995-02-01 | Brisson et al. | Applicant |
| US5394398(A) | 1995-02-01 | Rau | Applicant |
| US5414701(A) | 1995-05-01 | Shtayer et al. | Applicant |
| US5418783(A) | 1995-05-01 | Yamaki et al. | Applicant |
| US5420857(A) | 1995-05-01 | Jurkevich | Applicant |
| US5420858(A) | 1995-05-01 | Marshall et al. | Applicant |
| US5420916(A) | 1995-05-01 | Sekiguchi | Applicant |
| US5422882(A) | 1995-06-01 | Hiller | Applicant |
| US5425090(A) | 1995-06-01 | Orriss | Applicant |
| US5426636(A) | 1995-06-01 | Hiller et al. | Applicant |
| US5428607(A) | 1995-06-01 | Hiller et al. | Applicant |
| US5428609(A) | 1995-06-01 | Eng et al. | Applicant |
| US5434852(A) | 1995-07-01 | LaPorta | Applicant |
| US5434981(A) | 1995-07-01 | Lenihan et al. | Applicant |
| US5440563(A) | 1995-08-01 | Isidoro et al. | Applicant |
| US5444713(A) | 1995-08-01 | Backaus et al. | Applicant |
| US5446738(A) | 1995-08-01 | Kim et al. | Applicant |
| US5452297(A) | 1995-09-01 | Hiller et al. | Applicant |
| US5453981(A) | 1995-09-01 | Katsube et al. | Applicant |
| US5454034(A) | 1995-09-01 | Martin | Applicant |
| US5457684(A) | 1995-10-01 | Bharucha | Applicant |
| US5461669(A) | 1995-10-01 | Vilain | Applicant |
| US5463620(A) | 1995-10-01 | Sriram | Applicant |
| US5463621(A) | 1995-10-01 | Suzuki | Applicant |
| US5473677(A) | 1995-12-01 | D'Amato | Applicant |
| US5473679(A) | 1995-12-01 | LaPorta | Applicant |
| US5477537(A) | 1995-12-01 | Dankert et al. | Applicant |
| US5479401(A) | 1995-12-01 | Bitz et al. | Applicant |
| US5479402(A) | 1995-12-01 | Hata et al. | Applicant |
| US5479495(A) | 1995-12-01 | Blumhardt | Applicant |
| US5483527(A) | 1996-01-01 | Doshi et al. | Applicant |
| US5485455(A) | 1996-01-01 | Dobbins et al. | Applicant |
| US5495484(A) | 1996-02-01 | Self et al. | Applicant |
| US5504742(A) | 1996-04-01 | Kakuma et al. | Applicant |
| US5506844(A) | 1996-04-01 | Rao | Applicant |
| US5509010(A) | 1996-04-01 | LaPorta | Applicant |
| US5509123(A) | 1996-04-01 | Dobbins et al. | Applicant |
| US5513178(A) | 1996-04-01 | Tanaka | Applicant |
| US5513355(A) | 1996-04-01 | Doellinger et al. | Applicant |
| US5519707(A) | 1996-05-01 | Subramanian et al. | Applicant |
| US5521910(A) | 1996-05-01 | Matthews | Applicant |
| US5522042(A) | 1996-05-01 | Fee et al. | Applicant |
| US5526414(A) | 1996-06-01 | Bedard et al. | Applicant |
| US5533106(A) | 1996-07-01 | Blumhardt | Applicant |
| US5539698(A) | 1996-07-01 | Kozaki et al. | Applicant |
| US5539815(A) | 1996-07-01 | Samba | Applicant |
| US5539816(A) | 1996-07-01 | Pinard et al. | Applicant |
| US5539884(A) | 1996-07-01 | Robrock | Applicant |
| US5541918(A) | 1996-07-01 | Ganmukhi et al. | Applicant |
| US5541926(A) | 1996-07-01 | Saito et al. | Applicant |
| US5544152(A) | 1996-08-01 | Obermanns et al. | Applicant |
| US5544161(A) | 1996-08-01 | Bigham et al. | Applicant |
| US5546398(A) | 1996-08-01 | Tucker et al. | Applicant |
| US5548580(A) | 1996-08-01 | Buckland | Applicant |
| US5550819(A) | 1996-08-01 | Duault | Applicant |
| US5550820(A) | 1996-08-01 | Baran | Applicant |
| US5550914(A) | 1996-08-01 | Clarke et al. | Applicant |
| US5563939(A) | 1996-10-01 | La Porta et al. | Applicant |
| US5566173(A) | 1996-10-01 | Steinbrecher | Applicant |
| US5568475(A) | 1996-10-01 | Doshi | Applicant |
| US5570368(A) | 1996-10-01 | Murakami et al. | Applicant |
| US5572583(A) | 1996-11-01 | Wheeler, Jr. et al. | Applicant |
| US5577039(A) | 1996-11-01 | Won et al. | Applicant |
| US5579311(A) | 1996-11-01 | Chopping et al. | Applicant |
| US5587999(A) | 1996-12-01 | Endo | Applicant |
| US5592477(A) | 1997-01-01 | Farris et al. | Applicant |
| US5600640(A) | 1997-02-01 | Blair et al. | Applicant |
| US5600643(A) | 1997-02-01 | Robrock | Applicant |
| US5623491(A) | 1997-04-01 | Skoog | Applicant |
| US5627836(A) | 1997-05-01 | Conoscenti et al. | Applicant |
| US5629930(A) | 1997-05-01 | Beshai et al. | Applicant |
| US5635980(A) | 1997-06-01 | Lin et al. | Applicant |
| US5636210(A) | 1997-06-01 | Agrawal et al. | Applicant |
| US5640446(A) | 1997-06-01 | Everett et al. | Applicant |
| US5661725(A) | 1997-08-01 | Buck | Applicant |
| US5666349(A) | 1997-09-01 | Petri | Applicant |
| US5673262(A) | 1997-09-01 | Shimizu | Applicant |
| US5680390(A) | 1997-10-01 | Robrock | Applicant |
| US5703876(A) | 1997-12-01 | Christie | Applicant |
| US5708702(A) | 1998-01-01 | DePaul et al. | Applicant |
| US5710769(A) | 1998-01-01 | Anderson et al. | Applicant |
| US5719863(A) | 1998-02-01 | Hummel | Applicant |
| US5751706(A) | 1998-05-01 | Land | Applicant |
| US5825780(A) | 1998-10-01 | Christie | Applicant |
| US5835584(A) | 1998-11-01 | Penttonen | Applicant |
| US5844895(A) | 1998-12-01 | Gradisching | Applicant |
| US5848128(A) | 1998-12-01 | Frey | Applicant |
| US5867562(A) | 1999-02-01 | Scherer | Applicant |
| US5920562(A) | 1999-07-01 | Christie et al. | Applicant |
| US5926482(A) | 1999-07-01 | Christie | Applicant |
| US5940393(A) | 1999-08-01 | Duree et al. | Examiner |
| US5940487(A) | 1999-08-01 | Bunch et al. | Applicant |
| US5940491(A) | 1999-08-01 | Anderson et al. | Applicant |
| US5991301(A) | 1999-11-01 | Christie | Applicant |
| US6002689(A) | 1999-12-01 | Christie et al. | Applicant |
| US6005845(A) | 1999-12-01 | Svennesson et al. | Applicant |
| US6016343(A) | 2000-01-01 | Hogan et al. | Applicant |
| US6023474(A) | 2000-02-01 | Gardner | Applicant |
| US6031840(A) | 2000-02-01 | Christie | Applicant |
| US6061364(A) | 2000-05-01 | Hager et al. | Applicant |
| US6081529(A) | 2000-06-01 | Christie | Applicant |
| US6137800(A) | 2000-10-01 | Wiley et al. | Examiner |
| US6181703(B1) | 2001-01-01 | Christie et al. | Applicant |
| US6314103(B1) | 2001-11-01 | Medhat et al. | Examiner |
| EP90312739.7 | 1991-07-01 | Applicant | |
| EP91303312.2 | 1991-10-01 | Applicant | |
| EP91311342.9 | 1992-07-01 | Applicant | |
| EP92307752.3 | 1993-09-01 | Applicant | |
| JP870284896 | 1989-05-01 | Applicant | |
| JP7050057 | 1996-09-01 | Applicant | |
| WO94/06251 | 1994-03-01 | Applicant | |
| WO95/04436 | 1995-02-01 | Applicant |
Non-Patent Literature (81)
- Tanabe, Shirou, Taihei, Suzuki, and Ohtsuki, Ken-Ichi, “A New Distributed Switching System Architecture for B-ISDN,” International Conference on Integrated Broadband Services and Networks, Oct. 15-18, 1990, The Institution of Electrical Engineers, Savoy Place, London.Applicant
- Palmer, Rob, “An Experimental ATM Network for B-ISDN Research,” IEEE 1992, Melbourne, Australia.Applicant
- Thomas F. Laporta, “Distributed Call Processing for Wireless Mobile Networks,” Bell Labs Technical Journal, vol. 1 (No. 1), pp. 127-142, (Oct., 1996).Applicant
- Beckman, Richard T. and Matthews, Joseph R., “Proposal for a Physical Architecture Based on the Harmonized Functional Architecture,” Committee T1 Contribution T1S1.5/95-027, Bellcore, (Feb. 20, 1995).Applicant
- Yoshikai, N., et al., “Report of the Meeting of SWP 13/1-4 (Draft Recommendation I.580),” ITU-T Telecommunication Standardization Sector, Study Group 13, pp. 1-51, (Mar. 7-18, 1994).Applicant
- N/A, “Final Draft Text for Broadband Capability Set 2 Signaling Requirements, Attachment “D” Special Drafting Meeting,” ITU-T Telecommunications Standardization Sector, Study Group 11, p. 1-127, (Sep. 13-22, 1993).Applicant
- Ohta, S., et al., “A Dynamically Controllable ATM Transport Network Based on the Virtual Path Concept,” Communications for the Information Age, Globecom'88, Conference Record, p. 1272-1276, (Nov. 28-Dec. 1, 1988).Applicant
- Fukazawa, M., et al., “Intelligent Network Call Model for Broadband ISDN,” Fujitsu Laboratories, Ltd. (Japan), p. 30.6.1-30.6.5.Applicant
- Minzer, Steven, “A Signaling Protocol for Complex Multimedia Services,” IEEE Journal on Selected Areas in Communications (ISSN 0733-8716), vol. 9 ( No. 9), p. 1383-1394, (Dec. 1991).Applicant
- Faynberg, I., et al., “The Support of Network Interworking and Distributed Context Switching in the IN Service Data Function Model,” 2nd Colloque International, ICIN 92, p. 11-16, (Mar. 1992).Applicant
- Woodworth, Clark B., et al., “A Flexible Broadband Packet Switch for a Multimedia Integrated Network,” International Conference on Communications, Denver, ICC-91, p. 3.2.1-3.2.8, (Jun. 1991).Applicant
- Miller, P., “Intelligent Network/2: A flexible framework for exchange services,” Bell Communications Research EXCHANGE, vol. 3 ( No. 3), (May/Jun. 1987).Applicant
- Cooper, C., et al., “Toward a Broadband Congestion Control Strategy,” IEEE Network, The Magazine of Computer Communications, (May 1990).Applicant
- Batten, A., “A Personal Communications Services and the Intelligent Network,” British Telecommunications Engineering, (Aug. 1990).Applicant
- Fujioka, M., et al., “Universal Service Creation and Provision Environment for Intelligent Network,” IEEE Communications Magazine, (Jan. 1991).Applicant
- Andrews, F., “Switching in a Competitive Market,” IEEE Communications Magazine, (Jan. 1991).Applicant
- N/A, “Network Signaling,” Telephony, TCX12004, University of Excellence, p. 5.8-5.17, (Oct. 21, 1991).Applicant
- Garrahan, J.J., et al., “Intelligent Network Overview,” IEEE Communications Magazine, p. 30-36, (Mar. 1993).Applicant
- Johnson, M.A., et al., “New Service Testing Functions for Advanced Intelligent Networks,” IEEE 1992 Network Operations and Management Symposium, p. 709-720, (Apr. 6, 1992).Applicant
- Yeh, S.Y., et al., “The Evolving Intelligent Network Architecture,” IEEE Conference on Computer and Communication Systems, p. 835-839, (1990).Applicant
- Atoui, M., “Virtual Private Network Call Processing in the Intelligent Network,” International Conference on Communications, p. 561-565, (1992).Applicant
- Bosco, P., et al., “A Laboratory for AIN Service Design and Validation,” International Conference on Communications, p. 566-571, (Jun. 14, 1992).Applicant
- Homa, J., et al., “Intelligent Network Requirements for Personal Communications Services,” IEEE Communications Magazine, p. 70-76, (Feb. 1992).Applicant
- Russo, E.G., et al., “Intelligent Network Platforms in the U.S.,” AT&T Technical Journal, p. 26-43, (1991).Applicant
- Van Den Broek, W., et al., “RACE 2066-Functional models of UMTS and integration into the future networks,” Electronics & Communications Engineering Journal, p. 165-172, (Jun. 1993).Applicant
- Pinkham, G., et al., “The Ericsson Approach to Intelligent Networks,” IEEE Global Telecommunications Conference & Exhibition, Session 10, paragraph 4, p. 320-324, (1988).Applicant
- N/A, “ANSI-TI.111-1992, Signaling System No. 7 (SS7)—Message Transfer Part (MTP),” American National Standard for Telecommunications.Applicant
- N/A, “ANSI-TI.112-1992, Signaling System No. 7 (SS7)—Signaling Connection Control Part (SCCP),” American National Standard for Telecommunications.Applicant
- N/A, “ANSI-TI.113-1992, Signaling System No. 7 (SS7)—Integrated Services digital Network (ISDN) User Part,” American National Standard for Telecommunications.Applicant
- N/A, “ANSI-TI.113a-1993, Signaling System No. 7 (SS7)—Integrated Services Digital Network (ISDN) User Part (NxDSO Multi-rate Connection),” American National Standard for Telecommunications.Applicant
- N/A, “ANSI-TI.113-1995, Signaling System No. 7 (SS7)—Integrated Services Digital Network (ISDN) User Part,” American National Standard for Telecommunications.Applicant
- N/A, “ATM at a Glance,” Transmission Technologies Access Guide, p. 40-42, (1993).Applicant
- Paglialunga, A., “ISCP Baseline Document (VER 3.1),” ITU Telecommunication Standardization Sector, Centre Studi E Laboratori Telecommunicazioni S.p.A., (1993).Applicant
- N/A, “A Technical Report on SPEECH PACKETIZATION,” Document T1A1/94—Prepared by T1A1.7, Working Group on Specialized Signal Processing.Applicant
- N/A, “Draft Revised Recommendation I.580,” ITU—Telecommunication Standardization Sector, Study Group 13, (Jul. 10-21, 1995).Applicant
- Sprague, David, “MTP Level-3 Gateway STP Release 3.2.0,” TEKELEC, p. 1-48, (Aug. 4, 1995).Applicant
- McDysan, David E. and Spohn, Darren L., “ATM Theory and Application,” ATM Layer VPI/VCI Level Addressing, p. 256: 9.3.1, (1994).Applicant
- Minoli, Daniel and Dobrowski, George, “Principles of Signaling for Cell Relay and Frame Relay,” DVI Comm., Inc. / Stevens Institute of Technology / Bell Comm. Research (Bellcore), p. 1-2, 5-6 and 229, (1994).Applicant
- N/A, “B-IDSN ATM Adaptation Layer (AAL) Specification, Types 1 & 2,” ITU Draft Recommendation I.363.1, (Jul. 21, 1995).Applicant
- N/A, “Circuit Emulation Service Interoperability Specification Version 2.0 (Baseline Draft), 95-1504,” The ATM Forum Technical Committee, (Dec. 1995).Applicant
- N/A, “IN/B-ISDN Signalling Three Ways of Integration,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Interworking B-ISUP and Q.93B for DDI, MSN, TP and SUB,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Revised Draft of Q.2650 (DSS2/B-ISUP Interworking Recommendation),” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Draft Broadband / Narrowband NNI interworking recommendation,” ITU—Telecommunication Standardization Sector, Study Group 11, (Dec. 1993).Applicant
- N/A, “Draft Recommendation Q.2761,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Draft Recommendation Q.2762,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Q.2931 Overview,” ITU—Telecommunication Standardization Sector, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Clean final draft text for B-ISUP formats and codes (Q.2763) in ASN.1,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Updated draft of Q.2764 (BQ.764),” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Final B-ISUP SDLs,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Draft Recommendation Q.2650,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Revised Draft of Q.2650 (DSS2/B-ISUP Interworking Recommendation),” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Revision of Recommendation of Q.850,” ITU—T SG 11 WP 2, (Dec. 2-15, 1993).Applicant
- N/A, “Draft Text for Q.2931 (CH. 1, 2 and 3),” ITU—Telecommunication Standardization Sector, Study Group 11, (Dec. 1993).Applicant
- N/A, “Q.2931, Clause 4—Information Elements,” ITU—Telecommunication Standardization Sector, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Section 5 of Q.93B,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Chapter 6 of Recommendation Q.93B,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Clauses 7 and 8 of Q.2931,” ITU—Telecommunication Standardization Sector, Study Group 11, (Dec. 1993).Applicant
- N/A, “Revised Q.2931 User Side SDL Diagrams,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Revised Q.2931 Network Side SDL Diagrams,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “AnnexesB, C, D, F, H and I of Q.2931,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Annex E of Recommendation Q.93B,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Rec. Q.2931, Annex G—Status Monitoring of SPCs,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Annex J of Q.2931,” ITU—Telecommunication Standardization Sector, Study Group 11, (Dec. 1993).Applicant
- N/A, “Appendix 1/Q.2931: Guidelines for the Use of Instruction Indicators,” ITU—Telecommunication Standardization Sector, Study Group 11, (Nov. 29-Dec. 17, 1993).Applicant
- N/A, “Draft text for Q.2931: Appendix II (Information Items Required for Connection Establishment and Routing in B-ISDN),” ITU—Telecommunication Standardization Sector, Study Group 11.Applicant
- N/A, “General Recommendations on Telephone Switching and Signalling—Intelligent Network / Distributed Functional Plane for Intelligent Network CS-1,” ITU-T Recommendation Q.1214.Applicant
- Kumar, Sanjay, “Legacy Voice Service at a Native ATM Terminal,” ATM_Forum/95-0917R1, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Duault, Maurice, et al., “Baseline Text for Voice and Telephony Over ATM—ATM Trunking for Narrowband Services,” ATM_Forum/95-0446R3, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Choi, Don, “Requirements for ATM Trunking,” ATM_Forum/95-1401, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Chiang, Chin, “Proposed Changes to Proxy Signaling Capability,” ATM Forum/95-0046, ATM Forum: Signaling Working Group, (Feb. 6-10, 1995).Applicant
- Amin-Salehi, Bahman, “Third Party Call Setup for a Video-on Demand Connection Establishment,” ATM_Forum/95-0022, ATM Forum Technical Committee, (Feb. 5-8, 1995).Applicant
- Caves, Keith, “Proposed Modifications to the Baseline Text (95-0446R2) of the ‘VTOA—ATM Trunking for Narrowband Services’ Specification,” ATM Forum/95-1134, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Schink, Helmut, et al., “CES as a Flexible Trunking Method,” ATM_Forum/95-1157, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Duault, Maurice, “Proposal for ATM Trunking Options,” ATM_Forum/95-1230, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Okutani, Takenori, et al., “VTOA: Reference Configuration-ATM Trunking for Narrowband Services,” ATM-Forum/95-1364, ATM Forum Technical Committee, (Oct. 2-6, 1995).Applicant
- Stodola, Kevin, “Circuit Emulation Services Version 2 Baseline,” ATM_Forum/95-1504, ATM Forum Technical Committee, (Dec. 11-15, 1995).Applicant
- N/A, “I.751 Asynchronous Transfer Mode (ATM) Management View of the Network Element View,” ITU—Telecommunication Standardization Sector, Study Group 15, (Nov. 13-24, 1995).Applicant
- N/A, “Draft I.732,” ITU—Telecommunication Standardization Sector, Study Group 15, (Nov. 13-24, 1995).Applicant
- N/A, “Editorial Modifications for Draft New ITU-T Recommendation I.731,” ITU—Telecommunication Standardiztion Sector, Study Group 15, (Nov. 13-24, 1995).Applicant
- Buhrke, R.E., “Proposed Unified Functional Model,” T1S1.5/95-036, Committee T1 Contribution, (Feb. 1995).Applicant