Patent Grant
6965592
The present invention relates to an SS7 message routing gateway. More particularly, the present invention relates to a distributed SS7 message routing gateway.
The conventional telecommunications network includes two distinct communication pathways or subnetworks—a voice network and a signaling network. These two networks function in a cooperative manner to facilitate a call between users. As implied by its name, the voice network handles the transmission of voice (or user data) information between users. The signaling network has a number of responsibilities, which include call setup, call teardown, and database access features. In simple terms, the signaling network facilitates the dynamic linking together of a number of discrete voice-type communication circuits, such that a voice-type connection is established between the calling and called party. These functions are generically referred to as call setup and call teardown. Additionally, the signaling network provides a framework through which non-voice related information may be transported, with this data and transport functionality being transparent to the users. This signaling technique is often referred to as out-of-band signaling, where the term “band” implies voice band. Common examples of services provided via the signaling network include 800 number database services, calling card verification services, and caller ID services. The original motivation for employing such an out-of-band signaling technique was to provide telecommunications service agents with an infrastructure that allowed for new and enhanced revenue producing services, such as 800 database access, call waiting, and caller ID services and to avoid tying up expensive voice trunks with signaling traffic.
From a hardware perspective, an SS7 network includes a plurality of SS7 nodes, generically referred to as signaling points (SPs), that are interconnected using signaling links, also referred to as SS7 links. At least three types of SPs are provided in an SS7 network: service switching points (SSPs), signal transfer points (STPs) and service control points (SCPs).
An SSP is normally installed in Class 4 tandem or Class 5 end offices. The SSP is capable of handling both in-band signaling and SS7 signaling. An SSP can be a customer switch, an end-office, an access tandem and/or a tandem. An STP transfers signaling messages from one signaling link to another. STPs are packet switches and are generally installed as mated pairs. Finally, SCPs control access to databases such as 800 number translation, 800 number carrier identification, credit card verification, etc. SCPs are also deployed in pairs.
Signaling links are transmission facilities used to connect SPs together. Conventional signaling links are dedicated bidirectional facilities operating at 56 kbps in the U.S. and Canada and at 64 kbps when clear channel capability is deployed. Normally, every link has a mate for redundancy and enhanced network integrity.
In order to ensure consistent and reliable communication across the signaling network infrastructure, a common or standard digital signaling protocol was established by the ITU-TS in the mid-'60s, and this protocol was known as Signaling System 6. By the mid-'80s the protocol had evolved into a slightly more sophisticated system known as Signaling System 7 (SS7). As a protocol, SS7 defines the hierarchy or structure of the information contained within a message or data packet. This internal data structure is often referred to as the protocol stack, which is comprised of a number of well defined strata or layers. In general terms, the SS7 protocol stack consists of 4 levels or layers:
The physical layer is the lowest or most fundamental layer and is the first layer that is used to interpret and process and incoming message. This layer is concerned with determining and/or providing the electrical characteristics needed to transmit the digital data over the interface being used. Following interpretation/processing, the incoming message is passed up the stack to the data link layer.
The data link layer (MTP layer 2) resides adjacent and above the physical layer and is responsible for providing the SS7 network with error detection/correction and properly sequenced delivery of all SS7 message packets. Following interpretation/processing, the incoming message is passed up the stack to the network layer.
The network layer (MTP layer 3) resides adjacent and above the data link layer and is responsible for message packet routing, message packet discrimination, and message packet distribution. Functionally, message discrimination determines to whom the message packet is addressed. If the message contains the local address (of the receiving node), then the message is passed on to message distribution. If the message is not addressed to the local node, then it is passed on to the message router. Following interpretation/processing, the incoming message is passed up the stack to the user part layer only if the message was destined to that node.
The user and application part layer resides adjacent and above the network layer and actually consists of several distinct parts. The parts may include mobile application part (MAP), radio access network application part (RANAP), transaction capabilities application part (TCAP), ISDN user part (ISUP), telephone user part (TUP), and broadband ISDN user part (B-ISUP).
While the SS7 network has functioned successfully for a number of years, such a network typically includes centralized nodes that make routing decisions which can have some disadvantages. Such disadvantages include expense due to processing requirements of centralized nodes, high-traffic volume at the centralized nodes, and possible network outage if one or more of the centralized nodes fails.
Because of the central location of STPs 108 and 110 and because of all of the tasks required to be performed by STPs 108 and 110, STPs 108 and 110 include an extremely complex parallel architecture for handling all of these functions. An example of such an STP with a highly parallel architecture is the EAGLE® STP available from Tekelec of Calabasas, Calif.
While IP networks provide a number of advantages, IP networks do not include the inherent reliability or stability of a conventional SS7 network. As discussed above, the conventional SS7 network architecture includes centralized routing elements which are expensive, complex, and subject to high-traffic volumes. Thus, there exists a need for a distributed SS7 gateway that avoids at least some of the difficulties associated with the prior art.
According to one aspect, the present invention includes a distributed SS7 gateway. The distributed SS7 gateway includes a plurality of distributed gateway routing elements. Each of the distributed gateway routing elements may be co-located with an SS7 node, such as an SSP or an SCP. Each of the distributed gateway routing elements performs an SS7 routing function, such as an MTP3 routing function. The distributed gateway routing elements route messages to other distributed gateway routing elements or to a translation services node for further processing. Such routing is similar to the internal routing performed by an SS7 STP or signaling gateway. As used herein, the phrase “signaling gateway” refers to a network node capable of routing telephony-related signaling messages between other network nodes and that is also capable of performing protocol translations for the signaling messages. However, because the functional components of the distributed gateway are co-located with network endpoints, rather than centrally located in a single node, the possibility of a complete network outage caused by failure of a single node is reduced.
According to another aspect, the invention may include an operations, administration, and maintenance (OA&M) node. The OA&M node may establish initial DGRE routing tables.
According to yet another aspect, the present invention includes a translation services module. The translation services module may be centrally located to perform centralized functions, such as global title translation, protocol conversion, and number portability.
Accordingly, it is an object of the present invention to provide a distributed message routing gateway that avoids at least some of the difficulties associated with conventional centralized routing nodes and with conventional IP telephony networks.
Some of the objects of the invention having been stated hereinabove, other objects will be evident as the description proceeds, when taken in connection with the accompanying drawings as best described hereinbelow.
Preferred embodiments of the invention will now be explained with reference to the accompanying drawings:
FIG. 4(A) is a block diagram illustrating IPv6 header fields including the flow label field that may be used to provide quality of service for call signaling messages routed between distributed gateway routing elements according to embodiments of the present invention;
FIG. 4(B) is a block diagram of sub-field of the flow label field illustrated in FIG. 4(A);
FIG. 6(A) is a block diagram of an IP packet including an MPLS header that may be used to provide quality of service for call signaling messages routed between distributed gateway routing elements according to an embodiment of the present invention;
FIG. 6(B) is a block diagram of fields in an MPLS header that may be used by distributed gateway routing elements to provide quality of service for SS7 messages routed between distributed gateway routing elements according to an embodiment of the present invention;
Rather than locating all of the SS7 routing architecture in a centralized network element, such as a signal transfer point or signaling gateway, embodiments of the present invention include a plurality of distributed gateway routing elements that are co-located with other SS7 network elements. The distributed gateway routing elements function collectively as a signal transfer point or signaling gateway. However, because the distributed gateway routing elements are not located together in a single location, the processing load on each element is reduced and the possibility of a complete network failure is reduced.
Although in the illustrated embodiment each DGRE 310 is connected to a single SS7 signaling point, the present invention is not limited to such an embodiment. For example, in an alternative embodiment of the present invention, each DGRE 310 may be associated with more than one SS7 network element. In addition, DGREs 310 may be connected to network elements other than those illustrated in
Virtual IMT bus 314 performs functions similar to a conventional interprocessor message transfer bus present in an SS7 signal transfer point, such as the EAGLE® STP available from Tekelec. Such functions include reliable delivery of SS7 messages to modules for outbound processing, meeting SS7 message timing requirements, and carrying network management messages, such as routing table establishment and maintenance-related messages between distributed gateway routing elements. However, unlike the conventional IMT bus, virtual IMT bus 314 spans large geographic distances, thus making meeting the SS7 reliability and timing requirements difficult. In order to meet these requirements, it is envisioned that a protocol that guarantees quality of service for each connection may be used. An example of such a protocol may be Internet Protocol version 6 (IPv6).
In IPv6, a new field, referred to as a flow label, is provided in the IPv6 packet header and may be used by distributed gateway routing elements and IP routers that interconnect distributed gateway routing elements to provide quality of service for call signaling messages traveling between distributed gateway routing elements. For call signaling packets, end-to-end delay may be one of the quality of service parameters that is guaranteed. Another quality of service parameter important in transmitting SS7 message packets via virtual IMT bus 314 may be reliability. Both of these parameters may be set for call signaling packets transmitted between distributed gateway routing elements using the flow label in the IPv6 packet header.
More particularly, distributed gateway routing elements 310 may encapsulate SS7 call signaling messages in IP datagrams and set one or more quality of service parameters in the datagrams to notify IP routers that interconnect distributed gateway routing elements 310 of the quality of service expected for these packets. The manner in which IP routers treat such packets depends on the routing algorithm used and is beyond the scope of this disclosure. What is important for purposes of the present invention is that the distributed gateway routing elements set quality of service parameters in the call signaling packets to be transmitted over virtual IMT bus 314 so that the interconnecting IP routers can give such packets the appropriate priority.
FIGS. 4(A) and 4(B) respectively illustrate examples of an IPv6header and a flow label field of the IPv6 header. In FIG. 4(A), IPv6 header 400 includes version field 402 indicates the IP version. Flow label field 404 contains parameters used by routers to provide quality of service. Payload length field 406 specifies the length of the IPv6 payload. Next header field 408 specifies the type of any extension headers that follow the base header. Extension headers are optional in IPv6 and are not of importance to explaining the present invention. Hop limit field 410 provides a strict bound on the maximum number of hops a datagram can make before being discarded. Source address field 412 and destination field 414 each contain 128-bit IP addresses, thus greatly increasing the IP address space over conventional IPv4.
Referring to FIG. 4(B), flow label field 404 is divided into a T-class field 416 and a flow identifier field 418. T-class field 416 specifies the traffic class for the datagram. In the illustrated embodiment, T-class field 416 is a 4-bit field. Values 0-7 of T-class field 416 are used to specify the time sensitivity of flow-controlled traffic. Values 8-15 are used to specify a priority for non-flow-controlled traffic. The remaining 24-bit flow identifier field contains a source-chosen flow identifier for a given traffic stream. Thus, in order to guarantee quality of service for packets routed between distributed gateway routing elements, a source distributed gateway routing element may select a flow identifier for SS7 signaling message traffic and assign a traffic class value indicating high time sensitivity. Using these parameters, a source distributed gateway routing element may forward the SS7 signaling message to another distributed gateway routing element. The receiving distributed gateway routing element may send a response back to the sending distributed gateway routing element using the same flow identifier and T-class. Routers in between the two distributed gateway routing elements may utilize the T-class and flow identifier values to ensure that packets are delivered between the distributed gateway routing elements within a predetermined time period.
The present invention is not limited to using flow identifier field in an IPv6 header to provide quality of service for SS7 messages traveling between distributed gateway routing elements. For example, in an alternative embodiment, the type of service (TOS) field in the IPv4 header may be used to provide quality of service between distributed gateway routing elements.
Another example of a mechanism for providing quality of service for call signaling packets transmitted between distributed gateway routing elements is to use multi-protocol label switching (MPLS). MPLS is used by routers to switch rather than route packets. Switching is faster than routing because it is a layer 2, rather than a layer 3 function of the IP protocol stack. When an incoming packet includes an MPLS header, the receiving router switches the packet based on the label in the MPLS header, rather than routing the packet based on its IP address. The router also changes the label in the MPLS header to a new label, which the next router uses to switch the packet to the appropriate outgoing link. Unlike conventional IP routing, MPLS routes are established in advance before any data is transferred. Since routes are established in advance, MPLS can be used to establish forwarding equivalence classes whereby classes of IP packets are guaranteed the same quality of service.
Forwarding equivalence classes can be used to guarantee special treatment of MPLS-encapsulated SS7 packets transmitted between distributed gateway routing elements according to embodiments of the present invention. For example, distributed gateway routing elements 310 may add MPLS labels to outgoing IP-encapsulated SS7 call signaling message packets. The MPLS label added by the distributed gateway routing element determines the forwarding equivalence class for the SS7 signaling message packets at the time of network ingress. Routers that interconnect the distributed gateway routing elements examine only the MPLS label to determine the outgoing link for the MPLS-encapsulated SS7 message. The label-switched path between distributed gateway routing elements may be agreed upon in advance of transmission to determine the quality of service for SS7 signaling message packets.
FIG. 6(A) illustrates an example of an IP packet including an MPLS header. In the illustrated example, IP packet 600 includes an IP header 602, an MPLS header 604, a TCP header 606, and a payload 608. For an SS7 call signaling message routed between distributed gateway routing elements, IP header 602 may contain the IP address of one of the distributed gateway routing elements. MPLS header 604 may contain a service class identifier that identifies a class of service to be given to IP packet 600. For SS7 call signaling messages, the class of service is preferably a high class of service that has low delay and high reliability. TCP header 606 contains transport layer information such as sequence numbers for a TCP stream that may be established between distributed gateway routing elements. Finally, payload field 608 contains some or all of the SS7 call signaling packet. Thus, a variety of methods may be used to guarantee quality of service for call signaling packets routed between distributed gateway routing elements.
FIG. 6(B) is a block diagram of the fields of MPLS header 604 illustrated in FIG. 6(A). In FIG. 6(B), MPLS header 604 includes a label field 610, an experimental use field 612, a bottom of stack bit 614, and a time to live field 616. As discussed above, label field 610 contains the MPLS label that is assigned by the ingress router, i.e., the distributed gateway routing element, to determine the path forwarding equivalence class of the packet. Distributed gateway routing elements 310 may initialize experimental use field 614 to a value that indicates a quality of service to be given to packets within a forwarding equivalence class. Bottom of stack field and time to live field are not of importance in explaining the present invention. Further details of the multi-protocol labels switching architecture can be found in Internet Engineering Task Force (IETF) Internet draft: Multi-Protocol Label Switching Architecture, draft-ietf-mpls-arch-07.txt, July 2000, the disclosure of which is incorporated herein by reference in its entirety.
Referring back to
HMDT process 706 functions similarly to the HMDT process in the above-referenced EAGLE® STP. However, unlike the HMDT process in the conventional EAGLE® STP which distributes messages internally in the STP, HMDT process 706 distributes messages to DGREs that are part of the same distributed gateway via virtual IMT bus 314 which may span a large geographic area. Thus, in
Additional functions that may be performed by distributed gateway routing elements 310 include gateway screening, message copying, and overriding DPC routing. Gateway screening is a function performed by DGREs 310 to screen messages based on one or more parameters in the messages. For example, DGREs 310 may each include a gateway screening process that screens incoming SS7 messages based on parameters, such as originating point code, destination point code, and/or CIC code. In one screening example, if a message is from an allowed originating point code, distributed gateway routing elements 310 may allow the message into the network comprising virtual IMT bus 314. If a message is not from an allowed originating point code, the message may be discarded.
Message copying refers to copying all or portions of selected message signal units (MSUs) received by a DGRE. For example, it may be desirable to capture all MSUs directed to a database, such as SCP 306 for accounting or billing purposes. For network monitoring purposes, it may be desirable to record copies of or a count of MSUs received by DGREs 310. The copies MSU information received by DGREs 310 may be forwarded to an external node for further processing. Such forwarding may be accomplished by sending the message copies in Internet protocol packets to the external node via a wide or local area network.
Overriding point code routing is another function that may be performed by DGREs 310. For example, as mentioned above, DGREs may route messages to other DGREs based on the destination point code, CIC code, or other parameters in received SS7 MSUs. This is the normal DPC routing function. In addition to this type of routing, DGREs 310 may also override normal DPC routing based on the presence of one or more parameters in a message. One example in which it may be desirable to override normal DPC routing is when providing triggerless number portability service. According to triggered number portability service, an SSP, such as SSP 304, may receive a call to a ported number. In such a situation, SSP 304 would formulate a transaction capabilities application part (TCAP) query to a number portability database, such as SCP 306. The query would be routed to SCP 306 via DGREs 310. The response to the query containing the real directory number corresponding to the ported number is sent from SCP 306 to SSP 304 via DGREs 310. SSP 304 uses the real directory number in the response to set up a call with the called party by formulating an ISDN user part (ISUP) message addressed to the called party end office and containing the subscriber's real directory number.
According to triggerless number portability, when SSP 304 receives a call to a ported number, SSP 304 sends an ISUP message to the destination SSP associated with the dialed directory number via distributed gateway 300. One of the distributed gateway routing elements 310 receives the message, and determines that the message is related to a call to a subscriber whose number has been ported to another service area. In response to determining that the number has been ported, the receiving DGRE 310 forwards the message to translation services module 310, which translates the DPC in the message to the DPC of the SSP servicing the subscriber's new service area, inserts the new directory number in the message, and forwards the message to the appropriate destination SSP. Thus, DGREs 310 according to embodiments of the present invention are capable of performing both triggered and triggerless number portability routing operations.
In order to communicate with other distributed gateway routing elements via virtual IMT bus 314, distributed gateway routing element includes virtual IMT bus address translator 708 and quality of service manager 710. Virtual IMT bus address translator 708 may translate between SS7 and the protocol used on virtual IMT bus 314. As stated above, exemplary protocols that may be used on virtual IMT bus 314 include IP version 6 including flow labels, IP version 4 including the type of service field, and MPLS. Thus, virtual IMT bus address translator is preferably capable of formulating the appropriate header including the quality of service parameters and forwarding the packets to other distributed gateway routing elements via IMT bus 314. Quality of service manager 710 may determine the quality of service required for a given SS7 packet and instruct virtual IMT bus address translator 708 to set the appropriate parameters in the IP and/or MPLS headers. For example, if the packet is an ISUP call signaling packet, quality of service manager 710 may instruct virtual IMT bus address translator 708 to assign a high priority to the packet, using one or more of the above-described parameters, with regard to end-to-end delay.
Virtual IMT bus address translator 708 preferably also receives messages from virtual IMT bus 314, translates the messages from the virtual IMT bus protocol to SS7, and passes the messages to outbound SS7 routing process 712. Outbound SS7 routing process 712 selects the outgoing SS7 link based on the SS7 point code.
In step ST4, the distributed gateway routing element sets the appropriate quality of service parameters in the virtual IMT bus packet. As discussed above, these parameters may include parameters in the flow label of an IPv6 header if the virtual IMT bus is implemented using IP version 6. Additional alternatives for providing quality of service may include setting the TOS field in the IPv4 header or adding an MPLS header to the SS7 message before sending the message over the virtual IMT bus.
In step ST5, the distributed gateway routing element sends the SS7 call signaling message to the distributed gateway routing element associated with the destination SS7 network element via the virtual IMT bus. For example, the destination SS7 network element may be a service control point. In this example, the SS7 call signaling message is delivered to the distributed gateway routing element associated with the service control point via virtual IMT bus 314. The routers between the distributed gateway routing elements may utilize the quality of service parameters in the virtual IMT bus packet that carries the SS7 message to provide the desired quality of service. As a result, SS7 messages can be delivered on time and with sufficient reliability in accordance with SS7 standards.
Although the routing example described with respect to
According to another aspect of the invention, the distributed gateway routing elements exchange routing information via virtual IMT bus 314. More particularly, distributed gateway routing elements 310 illustrated in
In Table 1, SS7 point codes are translated to destination addresses, which in the illustrated example are IP addresses. However, the present invention is not limited to using IP addresses to locate distributed gateway routing elements. For example, as discussed above, in an alternative embodiment, MPLS labels may be used. In addition, other fields in incoming messages in addition to the point code may be used in routing the messages.
In Table 1, the status field indicates a status of a link associated with a distributed gateway routing element. The cost field allows the sending distributed gateway routing element to determine the least cost path over which the message should be routed. Finally, the domain field indicates the domain of the destination SS7 network element.
Routing tables may be initially loaded onto distributed gateway routing elements through OA&M module 316 via virtual IMT bus 314. Once the routing table is loaded, it is desirable to maintain current information in the routing table with regard to link status and cost. In order to maintain link status and cost information in distributed gateway routing element routing tables, distributed gateway routing elements 310 may exchange route update messages via virtual IMT bus 314. For example, when a link goes down between a DGRE and its associated SS7 network element, the DGRE may notify the other DGREs that the status of the link is down. In addition, if the cost associated with routing a message to an SS7 network element changes, the DGRE associated with the SS7 network element may notify the other DGREs of the change in cost in order for them to choose the least cost path for routing messages to that SS7 network element. By exchanging network management messages via virtual IMT bus 314, distributed gateway routing elements 310 maintain current routing information in their respective routing tables in a manner similar to a centralized node, such as a signal transfer point.
Thus, the present invention includes a distributed gateway that includes multiple routing elements that are co-located with SS7 network elements. The distributed gateway routing elements communicate with each other via a virtual IMT bus that guarantees a specified quality of service for SS7 call signaling messages. Because the distributed gateway routing elements are located at the individual nodes rather than in a centralized network node, the probability of a complete network outage due to failure of one of the distributed gateway routing elements is decreased. In addition, the expense of providing SS7 routing services can be distributed among owners of the various SS7 network elements. Finally, distributed gateway routing elements according to embodiments of the present invention are capable of selecting quality of service parameters for outgoing SS7 message packets to ensure on-time, reliable delivery of SS7 message packets.
It will be understood that various details of the invention may be changed without departing from the scope of the invention. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation—the invention being defined by the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5008929 | Olsen et al. | Apr 1991 | A |
| 5142622 | Owens | Aug 1992 | A |
| 5208811 | Kashio et al. | May 1993 | A |
| 5239542 | Breidenstein et al. | Aug 1993 | A |
| 5315641 | Montgomery et al. | May 1994 | A |
| 5384840 | Blatchford et al. | Jan 1995 | A |
| 5420916 | Sekiguchi | May 1995 | A |
| 5430727 | Callon | Jul 1995 | A |
| 5509010 | La Porta et al. | Apr 1996 | A |
| 5568487 | Sitbon et al. | Oct 1996 | A |
| 5581558 | Horney, II et al. | Dec 1996 | A |
| 5583927 | Ely et al. | Dec 1996 | A |
| 5586177 | Farris et al. | Dec 1996 | A |
| 5638431 | Everett et al. | Jun 1997 | A |
| 5640446 | Everett et al. | Jun 1997 | A |
| 5651002 | Van Seters et al. | Jul 1997 | A |
| 5657452 | Kralowetz et al. | Aug 1997 | A |
| 5664102 | Faynberg | Sep 1997 | A |
| 5675635 | Vos et al. | Oct 1997 | A |
| 5680437 | Segal | Oct 1997 | A |
| 5680552 | Netravali et al. | Oct 1997 | A |
| 5696809 | Voit | Dec 1997 | A |
| 5701301 | Weisser, Jr. | Dec 1997 | A |
| 5706286 | Reiman et al. | Jan 1998 | A |
| 5712903 | Bartholomew et al. | Jan 1998 | A |
| 5732213 | Gessel et al. | Mar 1998 | A |
| 5740374 | Raffali-Schreinemachers | Apr 1998 | A |
| 5761281 | Baum et al. | Jun 1998 | A |
| 5761500 | Gallant et al. | Jun 1998 | A |
| 5764750 | Chau et al. | Jun 1998 | A |
| 5764955 | Doolan | Jun 1998 | A |
| 5768361 | Cowgill | Jun 1998 | A |
| 5768525 | Kralowetz et al. | Jun 1998 | A |
| 5774695 | Autrey et al. | Jun 1998 | A |
| 5781534 | Perlman et al. | Jul 1998 | A |
| 5787255 | Parlan et al. | Jul 1998 | A |
| 5793771 | Darland et al. | Aug 1998 | A |
| 5802285 | Hirviniemi | Sep 1998 | A |
| 5805587 | Norris et al. | Sep 1998 | A |
| 5812781 | Fahlman et al. | Sep 1998 | A |
| 5815669 | Lee et al. | Sep 1998 | A |
| 5828844 | Civanlar et al. | Oct 1998 | A |
| 5838782 | Lindquist | Nov 1998 | A |
| 5852660 | Lindquist et al. | Dec 1998 | A |
| 5867495 | Elliott et al. | Feb 1999 | A |
| 5870565 | Glitho | Feb 1999 | A |
| 5872782 | Dendi | Feb 1999 | A |
| 5878129 | Figurski et al. | Mar 1999 | A |
| 5889954 | Gessel et al. | Mar 1999 | A |
| 5892822 | Gottlieb et al. | Apr 1999 | A |
| 5912887 | Sehgal | Jun 1999 | A |
| 5917900 | Allison et al. | Jun 1999 | A |
| 5920562 | Christie et al. | Jul 1999 | A |
| 5923659 | Curry et al. | Jul 1999 | A |
| 5926482 | Christie et al. | Jul 1999 | A |
| 5940598 | Strauss et al. | Aug 1999 | A |
| 5949871 | Kabay et al. | Sep 1999 | A |
| 5958016 | Chang et al. | Sep 1999 | A |
| 5974052 | Johnson et al. | Oct 1999 | A |
| 5991301 | Christie | Nov 1999 | A |
| 5995608 | Detampel, Jr. et al. | Nov 1999 | A |
| 6006098 | Rathnasabapathy et al. | Dec 1999 | A |
| 6011780 | Vaman et al. | Jan 2000 | A |
| 6011794 | Mordowitz et al. | Jan 2000 | A |
| 6011803 | Bicknell et al. | Jan 2000 | A |
| 6014379 | White et al. | Jan 2000 | A |
| 6018515 | Sorber | Jan 2000 | A |
| 6021126 | White et al. | Feb 2000 | A |
| 6023502 | Bouanaka et al. | Feb 2000 | A |
| 6026091 | Christie et al. | Feb 2000 | A |
| 6047005 | Sherman et al. | Apr 2000 | A |
| 6064653 | Farris | May 2000 | A |
| 6067546 | Lund | May 2000 | A |
| 6069890 | White et al. | May 2000 | A |
| 6075783 | Voit | Jun 2000 | A |
| 6078582 | Curry et al. | Jun 2000 | A |
| 6079036 | Moharram | Jun 2000 | A |
| 6084892 | Benash et al. | Jul 2000 | A |
| 6084956 | Turner et al. | Jul 2000 | A |
| 6094437 | Loehndorf, Jr. et al. | Jul 2000 | A |
| 6097719 | Benash et al. | Aug 2000 | A |
| 6097805 | Figurski et al. | Aug 2000 | A |
| 6111893 | Volftsun et al. | Aug 2000 | A |
| 6112090 | Valentine | Aug 2000 | A |
| 6115383 | Bell et al. | Sep 2000 | A |
| 6118779 | Madonna | Sep 2000 | A |
| 6118780 | Dunn et al. | Sep 2000 | A |
| 6119160 | Zhang et al. | Sep 2000 | A |
| 6122255 | Bartholomew et al. | Sep 2000 | A |
| 6122263 | Dahlin et al. | Sep 2000 | A |
| 6122365 | Yegoshin | Sep 2000 | A |
| 6125111 | Snow et al. | Sep 2000 | A |
| 6125177 | Whittaker | Sep 2000 | A |
| H1880 | Vines et al. | Oct 2000 | H |
| H1896 | Hoffpauir et al. | Oct 2000 | H |
| 6128379 | Smyk | Oct 2000 | A |
| 6134235 | Goldman et al. | Oct 2000 | A |
| 6134246 | Cai et al. | Oct 2000 | A |
| 6137869 | Voit et al. | Oct 2000 | A |
| 6137874 | Brown et al. | Oct 2000 | A |
| 6144667 | Doshi et al. | Nov 2000 | A |
| 6144670 | Sponaugle et al. | Nov 2000 | A |
| 6151390 | Volftsun et al. | Nov 2000 | A |
| 6154467 | Hager et al. | Nov 2000 | A |
| 6157710 | Figurski et al. | Dec 2000 | A |
| 6178181 | Glitho | Jan 2001 | B1 |
| 6195425 | Farris | Feb 2001 | B1 |
| 6201804 | Kikinis | Mar 2001 | B1 |
| 6215783 | Neyman | Apr 2001 | B1 |
| 6236722 | Gilbert et al. | May 2001 | B1 |
| 6324183 | Miller et al. | Nov 2001 | B1 |
| 6327267 | Valentine et al. | Dec 2001 | B1 |
| 6330614 | Aggarwal et al. | Dec 2001 | B1 |
| 6333931 | LaPier et al. | Dec 2001 | B1 |
| 6366655 | Book et al. | Apr 2002 | B1 |
| 6411632 | Lindgren et al. | Jun 2002 | B2 |
| 6430189 | Juntumaa et al. | Aug 2002 | B1 |
| 6487286 | Reaves et al. | Nov 2002 | B1 |
| 6507649 | Tovander | Jan 2003 | B1 |
| 6515985 | Shmulevich et al. | Feb 2003 | B2 |
| 6563835 | Chen | May 2003 | B1 |
| 6584190 | Bressler | Jun 2003 | B1 |
| 6594258 | Larson et al. | Jul 2003 | B1 |
| 6611532 | Madour et al. | Aug 2003 | B1 |
| 6611533 | Liao et al. | Aug 2003 | B1 |
| 6674748 | Dykhuizen et al. | Jan 2004 | B1 |
| 6678242 | Simon | Jan 2004 | B1 |
| 20020048360 | Zambre et al. | Apr 2002 | A1 |
| 20020105969 | Benedyk et al. | Aug 2002 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 853 411 | Jul 1998 | EP |
| 1 026 861 | Aug 2000 | EP |
| 1054568 | Nov 2000 | EP |
| WO 9711563 | Mar 1997 | WO |
| WO 9828885 | Jul 1998 | WO |
| WO 0019758 | Apr 2000 | WO |
| WO 0022840 | Apr 2000 | WO |
| WO 0030369 | May 2000 | WO |
| WO 0031933 | Jun 2000 | WO |
| WO 0033519 | Jun 2000 | WO |
| WO 0056032 | Sep 2000 | WO |
| WO 0137532 | May 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20020131400 A1 | Sep 2002 | US |
