CA2216982C - Internet ncp over atm - Google Patents
Internet ncp over atm Download PDFInfo
- Publication number
- CA2216982C CA2216982C CA002216982A CA2216982A CA2216982C CA 2216982 C CA2216982 C CA 2216982C CA 002216982 A CA002216982 A CA 002216982A CA 2216982 A CA2216982 A CA 2216982A CA 2216982 C CA2216982 C CA 2216982C
- Authority
- CA
- Canada
- Prior art keywords
- network
- atm
- address
- station
- switch
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/4608—LAN interconnection over ATM networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3081—ATM peripheral units, e.g. policing, insertion or extraction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0478—Provisions for broadband connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5614—User Network Interface
- H04L2012/5615—Network termination, e.g. NT1, NT2, PBX
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5619—Network Node Interface, e.g. tandem connections, transit switching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5625—Operations, administration and maintenance [OAM]
- H04L2012/5626—Network management, e.g. Intelligent nets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5638—Services, e.g. multimedia, GOS, QOS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5638—Services, e.g. multimedia, GOS, QOS
- H04L2012/564—Connection-oriented
- H04L2012/5643—Concast/multipoint-to-point
Abstract
A telecommunications network is provided for establishing communication between at least one originating station and at least one destination station. The network includes a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol. A server, which is coupled to at least one of the IP switches, receives at least one service attribute requested by the originating station in communication with the IP
switch. A network control point (NCP) is employed to provide data, in response to a request from the server, pertaining to the service attribute. At least one address database is associated with each of the IP switches. The address database includes a subset of the data available in the NCP.
switch. A network control point (NCP) is employed to provide data, in response to a request from the server, pertaining to the service attribute. At least one address database is associated with each of the IP switches. The address database includes a subset of the data available in the NCP.
Description
Internet NCP Over ATM
Technical Field This invention relates generally to a method for e-stablishing communication over a telecommunications network and more particularly to a method for establishing communications over a network incorporating IP switches.
Background of the Invention The recent growth of the Internet's backbone network has been facilitated by several newly emerging technologies. As this growth has continued with the deployment of many additional routers and Web servers, it has become increasingly evident that a high-speed Internet backbone is needed to allow further growth and to improve performance. One technology that can support such growth is Asynchronous Transfer Mode (ATM) protocol. ATM is a LAN/WAN networking infrastructure which provides fast cell switching at rates ranging from DS 1 up to OC 12. ATM is a protocol that resides at layer two of the OSI
model. As is well known in the art, the layers in the OSI model refer to the seven layer networking reference model developed by the International Standards Organization (ISO). ATM is well suited to become the technology of choice for the Internet backbone because of its ability to support various levels of quality/class of service, its speed and scalability over distance.
The Internet protocol (IP), which is a layer three protocol in the OSI model, may operate over an ATM backbone. However, such operation requires the resolution of various internetworking issues arising between IP and ATM. During the past few years, these issues have been addressed by the Internet Engineering Task Force (IETF), ATM Forum, ITU-T and many industry leaders. As a result, a variety of approaches have been proposed which are suitable for an Internet backbone that employs ATM. In one approach, a so-called IP switch is provided that integrates a conventional router and an ATM switch into a single device.
While IP switches provide many advantages over conventional switching and routing techniques, there remain a number of shortcomings. For example, IP switches do not presently allow a client to~ specify the data path's quality of service (QoS) since pairs of IP switches multiplex traffic. Moreover, a packet must undergo two router hops across the Internet backbone even when both the source and destination clients belong to the same ATM network.
x No direct cut-through path between the two clients is available. Additionally, IP switches currently do not provide a mechanism for segmenting a given IP switched network into multiple Intranets having appropriate levels of firewalls located therebetween.
Summary of the Invention The present invention provides a communications network that employs IP
switches and which overcomes the previously enumerated deficiencies. Specifically, in accordance with one embodiment of the invention, a telecommunications network is provided for establishing communication between at least one originating station and at least one destination station. The network includes a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol. A
server, which is coupled to at least one of the IP switches, receives at least one service attribute requested by the originating station in communication with the IP switch. A network control point (NCP) is employed to provide data., in response to a request from the server, pertaining to the service attribute. At least one address database is associated with each of the IP switches.
The address database includes a subset of the data available in the NCP.
In accordance with one aspect of the invention, the address database includes ATM to IP address correspondence data for the various end-point stations coupled to the IP switch.
The address database may also include address correspondence data from ATM to the dialed telephone number or to MAC. The service attribute requested by the originating station may include, for example, quality of service requirements and specification of the interface (e.g., ATM, frame relay, private line) between the originating and destination station.
In accordance with another aspect of the present invention there is provided a method for establishing communication between at least one originating station and at least one destination station over a network including a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol, said method comprising the steps of receiving an IP packet from the originating station addressed to the destination station; identifying an entry in an address database, that includes a subset of data available in a Network Control Point (NCP), for providing data in response to a request for information, the database containing address correspondence data for routing the IP packet to the destination station; identifying, by launching an inquiry to the NCP, at least one service attribute associated with transmission of the IP packet to the destination station; routing the IP packet to the destination station in accordance with the service attribute.
Brief Description of the Drawings FIG. 1 shows a simplified exemplary illustrating the behavior of the classical IP
model.
FIG. 2 shows a simplified exemplary network illustrating the classical IP
model with a cut-through path.
FIG. 3 shows a simplified, exemplary diagram of an IP-switched, ATM network in accordance with the present invention.
FIG. 4 shows a flow chart illustrating the steps performed when a client initiates communication with a server via with an address database that is arranged in a fully distributed manner.
CA 02216982 2000-o~-il 2a Detailed Description To fully convey an appreciation of the present invention, the proceeding discussion will first review select routing techniques for implementing IP over an ATM
network.
Classical IP Model - Hop-by-Hop Routing The most commonly known model supporting IP over an ATM network is referred to as classical IP over ATM. This model maintains traditional IP switching functions on top of ATM and does not require changes in the routing and switching infrastructures.
In classical IP, the IP and ATM addressing and routing models are maintained independently. A
mapping function is needed to map from an IP address to the corresponding ATM address.
That is, traditional overlay IP models such as classical IP view the underlying ATM
network as simply another OSI layer two technology. Consequently, classical IP does not take full advantage of the benefits of ATM. Details concerning the classical IP model may be found in Classical IP
Over ATM, M. Laubach, January, 1994, RFC 1577.
Although both the IP and ATM routing protocols employed in the Classical IP
model may determine reachability information for the same hosts, they run independently of one another. For example, IP routers run routing protocols such as RIP and OSPF
exchange reachability information pertinent to IP destinations. Likewise, ATM switches run independent protocols such as PNNI to determine ATM network topology and address reachability.
Typically, separate IP routers and ATM switches are provided. In fact, many networking scenarios even employ different IP and ATM network topologies.
In the Classical IP model, IP switching is totally decoupled from the ATM
network infrastructure even when the originating and target hosts are both directly connected to the same ATM network. In many ATM networks, an IP packet is routed to its final destination in several router hops, each muter along the path determining the next hop router to the destination. Each router determines the appropriate next hop router by requiring each muter to perform a layer three processing on the IP packet to inspect the destination IP address. The appropriate next hop router is then derived from routing tables resident in the router.
FIG. 1 shows a simplified ex$mplary network to illustrate the behavior of the classical IP
model when routing packets between two ATM-attached hosts 2 and 4. In this simple scenario, the source host 2 sends a packet to the destination host 4. The destination host 4 is located F
outside the local IP subnet of the source host 2. In operation, the source host 2 first sends the packet to router A via ATM switch 6 (labeled in FIG. 1 as path 1). To establish path 1 over the ATM network the source host 2 translates the IP address of router A to an ATM
address so that a virtual path is built to router A. An address resolution protocol (ARP) server 7 performs the IP
to ATM address translation service to all registered clients (i.e., hosts and routers) within a Local IP Subnet. (It should be noted that while the ARP server 7 in FIG. 1 resides on an end-point attached to the ATM switch 6, it may alternatively be a component of either an ATM
switch or a router). Source host 2 sends an address resolution request to ARP
server 7 to obtain the ATM address corresponding to the IP address of router A, which is located in the same local IP subnet. In tum, the ARP server 7 sends back an address resolution response with the ATM
address of muter A. Source host 2 thereafter assembles' path 1 over the ATM
network to the ATM address of router A.
Next, muter A determines that the appropriate following hop is to router B.
Router A
determines the ATM address of router B from ARP server 7 and forwards the packet to router B
via ATM switches 6 and 8 (labeled in FIG. 1 as path 2). Similarly, router B
forwards the packet through ATM switches 8 and 10 (labeled in FIG. 1 as path 3) to muter C, which in turn determines that it is the last hop router on the path to destination host 4.
Router C sends the packet to destination host 4 via ATM switch 10 (labeled in FIG. 1 as path 4).
It should be noted that this procedure requires three consecutive layer 3, i.e. IP, packet processing steps (one in each of the IP routers), four IP to ATM address mapping steps (one in each of the ARP servers), and four ATM switched virtual path establishment steps along the path between the source and destination hosts 2 and 4.
Classical IP Model - Cut-Through Routing In situations where large quantities of IP data flow from one end point to another, it is desirable to have a cut-through path to the destination over the ATM network.
A cut-through path directly connects the two end points, without traversing intermediate muter hops. (It should be noted that each router performs segmentation and reassembly of each IP packet, thus reducing throughput and speed.) For example, since source host 2 knows the IP
address of destination host 4, source host 2 could establish a cut-through path to destination host 4 via switches 6, 8, and 10 without traversing routers A, B and C if source host 2 could determine the ATM address of host 4 from its IP address. As a result, end-to-end performance is significantly improved ~. not traversing routers A, B, and C since multiple stages of layer three packet processing and forwarding are avoided. Cell processing and forwarding at the ATM layer are comparatively faster than at layer two, resulting in reduced delay and increased throughput.
As discussed in Next Hop Routing Protocol (NHRP), J. Luciani and D. Katz, Internet Draft, the Internet Engineering Task Force (IETF) is currently studying a new address resolution protocol known as NHRP (next hop routing protocol). This protocol maps IP
addresses to the corresponding ATM addresses that are located across LISs so that cut-through paths across distinct ATM clouds may be realized. In the NHRP model, each LIS (or multiple LISs) employs a Next Hop Server (NHS), which is analogous to an ARP server. While an ARP
server can only communicate with clients located in its own LIS, an NHS can communicate with clients located in its own LIS and with neighboring NHSs which support other LISs. That is, an NHS
essentially functions like a series of ARP servers located in a network that are in communication with one another. NHSs determine routes through routing protocols such as RIP
and OSPF.
The hardware performing the functionality of the NHS may reside in a router, as illustrated in Figure 2, or alternatively, it may reside on an ATM switch or end-station. In FIGS. 1 and 2 like components are provided with like reference numerals.
An IP host connected to an ATM network that employs NHSs serves as an NHRP
Client (NHC). Each NHC registers its IP address and corresponding ATM address within the registration database of its respective NHS. When an NHC wants to transmit its data traffic over a cut-through path rather than over its default (hop-by-hop) path, it requests its NHS to map the IP address of the destination to its corresponding ATM address (note that the destination may be located in a different LIS from the NHC): The NHS receiving this request maintains the corresponding addresses in its database either because the destination is in its own LIS, or because it cached the correspondence between addresses during a previous address resolution request. However, if the NHS does not have the correspondence between addresses in its database, it forwards a request to the next hop NHS. The request is forwarded until the last NHS
on the path to the destination is reached. The response containing the appropriate ATM address of the destination then traverses the same path as the request, except in reverse ( i.e., paths 1-4 in FIG. 2). Finally, the response is forwarded by the local NHS of the source host so that a virtual t path may be developed to the destination without traversing the routers located between the source and destination.
IP Switching Recently, a single device known as an IP switch has been developed. An IP
switch integrates a conventional router and ATM switch to route IP over ATM networks much more efficiently than in the traditional model, which employs distinct devices. The IP over ATM
model may be substantially simplified if the router and the ATM switch physically reside in the same device, as illustrated in FIG. 3. As previously mentioned, when the functionality of an ATM switch and an IP router reside on separate devices, the ATM switch does not have knowledge pertaining to routing and addressing at the IP layer. In contrast, when the functionality of an ATM switch and an IP router are merged onto the same device, it becomes possible to further integrate routing at the IP level into routing at the ATM
level. For example, a perfect topology match is achieved when a layer two node (an ATM switch) is physically integrated into a layer three node (an IP router). Although this configuration does not eliminate the problem of matching an IP address with its corresponding ATM address, the elimination of the topological mismatch creates the opportunity to use a single routing protocol for routing at both the IP and ATM layers. An Illustrative protocol that may serve in this capacity includes I-PNNI (see R. Callon, Relationship Between MPOA and I-PNNI, April 1996, ATM
Forum 96-0352), which has been submitted to the ATM Forum to integrate routing at the IPO layer into PNNI. I-PNNI facilitates the bootstrapping and ongoing operation of Internet routing protocols and associated packet forwarding protocols over an ATM network.
In a network employing IP switches, each IP switch pair may be provided with direct connectivity to further simplify the processes. of exchanging routing updates and forwarding of packets. Direct connectivity means that each IP switch is connected to every other IP switch without the need for any intermediate switches therebetween. Direct connectivity provides a number of advantages. For example, in a network employing direct connectivity, each host that is connected to one of the IP switches is only two hops away from any other host connected to an IP switch in the same network.
In addition, as a result of direct connectivity each IP switch knows about the IP routing topology of the entire network. Thus, it knows which IP switch is connected to which host.
i As well known to one of ordinary skill, direct connectivity may be achieved in a number of different_way_s.For example, a mesh of virtual paths may be employed, in which each IP
switch is connected to every other IP switch with a point-to-point (ptp) virtual path. The switch-to-switch virtual path can be a semi-permanent switched circuit or a permanent virtual circuit.
Such a topology yields N-squared point-to-point virtual paths between N
switches. Many segments of the point-to-point virtual paths may run over common physical links. Alternatively, direct connectivity may be achieved by using a point-to-multipoint (i.e., multicasting) connection in which one IP switch serves as the so-called root and all other switches serve as so-called leaves. In such a network having N IP switches, only N point-to-multipoint connections are required, thus considerably reducing the number of connections in comparison to a point-to-point topology. Point-to-multipoint connections may be used to transmit unicast packets as well as broadcast packets by having the packet originate at an IP switch serving as one of the leaves.
In this case the root IP switch serves as the destination receiving the unicast packet.
IP switching on the Internet Backbone The current Internet backbone consists of large-scale routers which are interconnected with private lines at a DS3 (45 Mbps) rate. However, in the future it would be advantageous to use an ATM backbone rather than a DS3 backbone. Such an ATM backbone network may employ IP switches since IP switching is optimized for IP routing over an ATM
network and thus represents a near ideal switch for the Internet backbone. If IP switching were to be employed in the current Internet, the legacy routers currently employed would be upgraded to IP
switches, which, with backbone facilities running the ATM protocol, can operate at rates up to an OC 12. The ATM backbone may employ direct connectivity, either point-to-point or point-to-multipoint, both of which require only two hop paths to cross the ATM network and use best effort connections to accommodate the least common denominator quality of service.
FIG. 3 shows a simplified, exemplary diagram of an IP switched ATM network in accordance with the present invention which offers the user or service provider a greater variety of selectable options. The network is accessible via client end-points that may be conveniently classified as either an ATM end-point or a non-ATM endpoint. ATM end-points, such as client 52 in FIG. 3, directly access an IP switch that is located at the periphery of the Internet backbone via an ATM UNI. ATM end-points run IP over ATM using known protocols such as LANE, Classical IP Over ATM, or Multiprotocol Over ATM. Non-ATM end points, such as client 51 in FIG. 3, access an IP switch located at the periphery of the Internet backbone via a non-ATM
technology such as Frame-Relay, ISDN or analog lines, all of which run the IP
protocol. A
protocol adaptation function may be located between the non-ATM end-point and the IP switch.
Alternatively, the peripheral IP switch may directly support non-ATM
interfaces.
As seen in FIG. 3, an Internet attached server 53 functions as an agent or proxy through which a client may request special services by allowing the client or service provider to specify client characteristics or desired service attributes. The proxy server 53 is typically a Web-server that is administered by the Internet service provider. The client may access the proxy server 53 via a Web-browser that is secured by a password. Once access is provided, the client may conveniently select the desired service attribute or attributes from a list of attributes. The client specifies to the proxy server 53 one or more desired service attributes pertaining to the quality of service. For purposes of illustration, service attributes include the type of access requested by the client such as ATM or non-ATM (dial, ISDN, etc.) and Quality of Service (QOS) requirements, which may be defined per application, destination, time-of day, and/or per port. Additional service attributes that may be specified via the proxy server 53 include the IP address of the host (if known), the IntraNet name, the host name and billing address, a credit card number or any special filters.
The proxy server 53 also may be employed to appropriately configure the end-point. For example, the proxy server 53 may provide to the user the NHS address or IP
switch address to which the end-point should connect.
As seen in FIG. 3, the proxy server 53 functions in cooperation with an Internet network control point (NCP) 54. The NCP 54, which is analagous to known network control points used in telephone networks that employ intelligent call processing, is the master database of the network which stores end-point information such as the correspondence between ATM, IP and MAC addresses, QoS requirements, special security filters, and billing properties. End-points can access the NCP 54 via the proxy server 53 to retrieve information and update the database as appropriate. That is, the proxy server 53 functions as a client interface to the NCP 54. The NCP
54 also may be updated in an automatic fashion by the individual IP switches in the network, such as when an end-point registers or unregisters an IP to ATM address correspondence or a particular QoS.
The individual IP switches within the Internet backbone each have an address database 56 that contains essentially a subset of the data in the NCP 54. At a minimum, the address databases 56 contain the correspondence between the ATM and IP addresses for their respective end-points. In contrast to an NHS, which only supports an ATM end-point, the address databases 56 support both ATM and non-ATM endpoints. Accordingly, the address databases 56 serve as NHS's with enhanced functionality.
The address databases 56 may be employed not only to construct an ATM cut-through across the Internet backbone, but also to specify a desired quality of service across the Internet backbone. If both the source and destination end-points access the backbone via ATM, a cut-though is feasible, assuming the source end-point can map the IP address of the destination end-point to its ATM address.
The address database may also perform additional functions such as: receiving updated IP-ATM address registrations from clients or other address databases;
receiving IP-ATM
address de-registration requests from clients or other address databases;
adding or deleting IP to ATM address correspondences from the database; receiving address queries from clients or other address databases; forwarding address query requests to clients or other address databases;
forwarding address query responses; and receiving provisioned end-point information updates from the Internet NCP.
The addxess databases may be implemented in any convenient manner. Two possible implementations are a fully distributed implementation and a fully duplicated implementation.
In the fully distributed approach, each IP switch only maintains an address database for those end-points that access the Internet at that particular IP switch. Accordingly, there is no need for synchronization among different address databases in different IP switches.
For example, when a source end-point sends an address query to its IP switch regarding a destination end-point and the IP to ATM address correspondence is not found in the queried IP switch, the switch will forward the request only to the IP switch responsible for the destination end-point. In a fully distributed arrangement, the Internet NCP serves as the master database that stores alI
provisioned information for the network, including the IP to ATM address correspondences.
When a change in the address database of an IP switch occurs (due to a host disconnecting from the IP switch, for example), the same change is forwarded to the Internet NCP
to update the master database. Similarly, when the Internet NCP is modified by the service provider or the user, the appropriate individual address databases) within the IP switch(es) will be updated accordingly.
If the address databases 56 are configured in a fully-duplicated arrangement, each IP
switch maintains the database for all the end-points. When a new database entry is registered with a given IP switch, that registration is sent to all other IP switches.
Accordingly, the address databases of all the IP switches are identical. That is, while the Internet NCP contains the master copy of the database, each IP switch maintains its own complete copy of the database. Similar to the fully distributed arrangement, if an IP switch makes a change in its database, the change will be reflected in all the other address databases, including the master database of the Internet NCP. Likewise, if a change is made to the Internet NCP database, it will be reflected in all the other address databases.
FIG. 4 shows a flow chart illustrating the steps performed when client 51 initiates communication with server 52 with an address database that is arranged in a fully distributed manner. In step 41, the client 51 sends to IP switch 57 the first IP packet addressed to server 52.
In step 43, IP switch 57 determines if its address database 56 has an entry for server 52. If IP
switch 57 does not have such an entry, it sends a query to the next hop database in step 47 to determine the address of server 52. Once IP switch 57 receives the appropriate address, it then obtains the requested service attributes for server 52 in step 49. In step 51, IP switch 57 accesses whether the requested service attributes require any special treatment. If they do not, in step 53 IP switch 57 routes the packet on a switched virtual circuit using default parameters. If special treatment is required, in step 55 IP switch 57 routes the call in conformance with the requested service parameters.
Technical Field This invention relates generally to a method for e-stablishing communication over a telecommunications network and more particularly to a method for establishing communications over a network incorporating IP switches.
Background of the Invention The recent growth of the Internet's backbone network has been facilitated by several newly emerging technologies. As this growth has continued with the deployment of many additional routers and Web servers, it has become increasingly evident that a high-speed Internet backbone is needed to allow further growth and to improve performance. One technology that can support such growth is Asynchronous Transfer Mode (ATM) protocol. ATM is a LAN/WAN networking infrastructure which provides fast cell switching at rates ranging from DS 1 up to OC 12. ATM is a protocol that resides at layer two of the OSI
model. As is well known in the art, the layers in the OSI model refer to the seven layer networking reference model developed by the International Standards Organization (ISO). ATM is well suited to become the technology of choice for the Internet backbone because of its ability to support various levels of quality/class of service, its speed and scalability over distance.
The Internet protocol (IP), which is a layer three protocol in the OSI model, may operate over an ATM backbone. However, such operation requires the resolution of various internetworking issues arising between IP and ATM. During the past few years, these issues have been addressed by the Internet Engineering Task Force (IETF), ATM Forum, ITU-T and many industry leaders. As a result, a variety of approaches have been proposed which are suitable for an Internet backbone that employs ATM. In one approach, a so-called IP switch is provided that integrates a conventional router and an ATM switch into a single device.
While IP switches provide many advantages over conventional switching and routing techniques, there remain a number of shortcomings. For example, IP switches do not presently allow a client to~ specify the data path's quality of service (QoS) since pairs of IP switches multiplex traffic. Moreover, a packet must undergo two router hops across the Internet backbone even when both the source and destination clients belong to the same ATM network.
x No direct cut-through path between the two clients is available. Additionally, IP switches currently do not provide a mechanism for segmenting a given IP switched network into multiple Intranets having appropriate levels of firewalls located therebetween.
Summary of the Invention The present invention provides a communications network that employs IP
switches and which overcomes the previously enumerated deficiencies. Specifically, in accordance with one embodiment of the invention, a telecommunications network is provided for establishing communication between at least one originating station and at least one destination station. The network includes a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol. A
server, which is coupled to at least one of the IP switches, receives at least one service attribute requested by the originating station in communication with the IP switch. A network control point (NCP) is employed to provide data., in response to a request from the server, pertaining to the service attribute. At least one address database is associated with each of the IP switches.
The address database includes a subset of the data available in the NCP.
In accordance with one aspect of the invention, the address database includes ATM to IP address correspondence data for the various end-point stations coupled to the IP switch.
The address database may also include address correspondence data from ATM to the dialed telephone number or to MAC. The service attribute requested by the originating station may include, for example, quality of service requirements and specification of the interface (e.g., ATM, frame relay, private line) between the originating and destination station.
In accordance with another aspect of the present invention there is provided a method for establishing communication between at least one originating station and at least one destination station over a network including a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol, said method comprising the steps of receiving an IP packet from the originating station addressed to the destination station; identifying an entry in an address database, that includes a subset of data available in a Network Control Point (NCP), for providing data in response to a request for information, the database containing address correspondence data for routing the IP packet to the destination station; identifying, by launching an inquiry to the NCP, at least one service attribute associated with transmission of the IP packet to the destination station; routing the IP packet to the destination station in accordance with the service attribute.
Brief Description of the Drawings FIG. 1 shows a simplified exemplary illustrating the behavior of the classical IP
model.
FIG. 2 shows a simplified exemplary network illustrating the classical IP
model with a cut-through path.
FIG. 3 shows a simplified, exemplary diagram of an IP-switched, ATM network in accordance with the present invention.
FIG. 4 shows a flow chart illustrating the steps performed when a client initiates communication with a server via with an address database that is arranged in a fully distributed manner.
CA 02216982 2000-o~-il 2a Detailed Description To fully convey an appreciation of the present invention, the proceeding discussion will first review select routing techniques for implementing IP over an ATM
network.
Classical IP Model - Hop-by-Hop Routing The most commonly known model supporting IP over an ATM network is referred to as classical IP over ATM. This model maintains traditional IP switching functions on top of ATM and does not require changes in the routing and switching infrastructures.
In classical IP, the IP and ATM addressing and routing models are maintained independently. A
mapping function is needed to map from an IP address to the corresponding ATM address.
That is, traditional overlay IP models such as classical IP view the underlying ATM
network as simply another OSI layer two technology. Consequently, classical IP does not take full advantage of the benefits of ATM. Details concerning the classical IP model may be found in Classical IP
Over ATM, M. Laubach, January, 1994, RFC 1577.
Although both the IP and ATM routing protocols employed in the Classical IP
model may determine reachability information for the same hosts, they run independently of one another. For example, IP routers run routing protocols such as RIP and OSPF
exchange reachability information pertinent to IP destinations. Likewise, ATM switches run independent protocols such as PNNI to determine ATM network topology and address reachability.
Typically, separate IP routers and ATM switches are provided. In fact, many networking scenarios even employ different IP and ATM network topologies.
In the Classical IP model, IP switching is totally decoupled from the ATM
network infrastructure even when the originating and target hosts are both directly connected to the same ATM network. In many ATM networks, an IP packet is routed to its final destination in several router hops, each muter along the path determining the next hop router to the destination. Each router determines the appropriate next hop router by requiring each muter to perform a layer three processing on the IP packet to inspect the destination IP address. The appropriate next hop router is then derived from routing tables resident in the router.
FIG. 1 shows a simplified ex$mplary network to illustrate the behavior of the classical IP
model when routing packets between two ATM-attached hosts 2 and 4. In this simple scenario, the source host 2 sends a packet to the destination host 4. The destination host 4 is located F
outside the local IP subnet of the source host 2. In operation, the source host 2 first sends the packet to router A via ATM switch 6 (labeled in FIG. 1 as path 1). To establish path 1 over the ATM network the source host 2 translates the IP address of router A to an ATM
address so that a virtual path is built to router A. An address resolution protocol (ARP) server 7 performs the IP
to ATM address translation service to all registered clients (i.e., hosts and routers) within a Local IP Subnet. (It should be noted that while the ARP server 7 in FIG. 1 resides on an end-point attached to the ATM switch 6, it may alternatively be a component of either an ATM
switch or a router). Source host 2 sends an address resolution request to ARP
server 7 to obtain the ATM address corresponding to the IP address of router A, which is located in the same local IP subnet. In tum, the ARP server 7 sends back an address resolution response with the ATM
address of muter A. Source host 2 thereafter assembles' path 1 over the ATM
network to the ATM address of router A.
Next, muter A determines that the appropriate following hop is to router B.
Router A
determines the ATM address of router B from ARP server 7 and forwards the packet to router B
via ATM switches 6 and 8 (labeled in FIG. 1 as path 2). Similarly, router B
forwards the packet through ATM switches 8 and 10 (labeled in FIG. 1 as path 3) to muter C, which in turn determines that it is the last hop router on the path to destination host 4.
Router C sends the packet to destination host 4 via ATM switch 10 (labeled in FIG. 1 as path 4).
It should be noted that this procedure requires three consecutive layer 3, i.e. IP, packet processing steps (one in each of the IP routers), four IP to ATM address mapping steps (one in each of the ARP servers), and four ATM switched virtual path establishment steps along the path between the source and destination hosts 2 and 4.
Classical IP Model - Cut-Through Routing In situations where large quantities of IP data flow from one end point to another, it is desirable to have a cut-through path to the destination over the ATM network.
A cut-through path directly connects the two end points, without traversing intermediate muter hops. (It should be noted that each router performs segmentation and reassembly of each IP packet, thus reducing throughput and speed.) For example, since source host 2 knows the IP
address of destination host 4, source host 2 could establish a cut-through path to destination host 4 via switches 6, 8, and 10 without traversing routers A, B and C if source host 2 could determine the ATM address of host 4 from its IP address. As a result, end-to-end performance is significantly improved ~. not traversing routers A, B, and C since multiple stages of layer three packet processing and forwarding are avoided. Cell processing and forwarding at the ATM layer are comparatively faster than at layer two, resulting in reduced delay and increased throughput.
As discussed in Next Hop Routing Protocol (NHRP), J. Luciani and D. Katz, Internet Draft, the Internet Engineering Task Force (IETF) is currently studying a new address resolution protocol known as NHRP (next hop routing protocol). This protocol maps IP
addresses to the corresponding ATM addresses that are located across LISs so that cut-through paths across distinct ATM clouds may be realized. In the NHRP model, each LIS (or multiple LISs) employs a Next Hop Server (NHS), which is analogous to an ARP server. While an ARP
server can only communicate with clients located in its own LIS, an NHS can communicate with clients located in its own LIS and with neighboring NHSs which support other LISs. That is, an NHS
essentially functions like a series of ARP servers located in a network that are in communication with one another. NHSs determine routes through routing protocols such as RIP
and OSPF.
The hardware performing the functionality of the NHS may reside in a router, as illustrated in Figure 2, or alternatively, it may reside on an ATM switch or end-station. In FIGS. 1 and 2 like components are provided with like reference numerals.
An IP host connected to an ATM network that employs NHSs serves as an NHRP
Client (NHC). Each NHC registers its IP address and corresponding ATM address within the registration database of its respective NHS. When an NHC wants to transmit its data traffic over a cut-through path rather than over its default (hop-by-hop) path, it requests its NHS to map the IP address of the destination to its corresponding ATM address (note that the destination may be located in a different LIS from the NHC): The NHS receiving this request maintains the corresponding addresses in its database either because the destination is in its own LIS, or because it cached the correspondence between addresses during a previous address resolution request. However, if the NHS does not have the correspondence between addresses in its database, it forwards a request to the next hop NHS. The request is forwarded until the last NHS
on the path to the destination is reached. The response containing the appropriate ATM address of the destination then traverses the same path as the request, except in reverse ( i.e., paths 1-4 in FIG. 2). Finally, the response is forwarded by the local NHS of the source host so that a virtual t path may be developed to the destination without traversing the routers located between the source and destination.
IP Switching Recently, a single device known as an IP switch has been developed. An IP
switch integrates a conventional router and ATM switch to route IP over ATM networks much more efficiently than in the traditional model, which employs distinct devices. The IP over ATM
model may be substantially simplified if the router and the ATM switch physically reside in the same device, as illustrated in FIG. 3. As previously mentioned, when the functionality of an ATM switch and an IP router reside on separate devices, the ATM switch does not have knowledge pertaining to routing and addressing at the IP layer. In contrast, when the functionality of an ATM switch and an IP router are merged onto the same device, it becomes possible to further integrate routing at the IP level into routing at the ATM
level. For example, a perfect topology match is achieved when a layer two node (an ATM switch) is physically integrated into a layer three node (an IP router). Although this configuration does not eliminate the problem of matching an IP address with its corresponding ATM address, the elimination of the topological mismatch creates the opportunity to use a single routing protocol for routing at both the IP and ATM layers. An Illustrative protocol that may serve in this capacity includes I-PNNI (see R. Callon, Relationship Between MPOA and I-PNNI, April 1996, ATM
Forum 96-0352), which has been submitted to the ATM Forum to integrate routing at the IPO layer into PNNI. I-PNNI facilitates the bootstrapping and ongoing operation of Internet routing protocols and associated packet forwarding protocols over an ATM network.
In a network employing IP switches, each IP switch pair may be provided with direct connectivity to further simplify the processes. of exchanging routing updates and forwarding of packets. Direct connectivity means that each IP switch is connected to every other IP switch without the need for any intermediate switches therebetween. Direct connectivity provides a number of advantages. For example, in a network employing direct connectivity, each host that is connected to one of the IP switches is only two hops away from any other host connected to an IP switch in the same network.
In addition, as a result of direct connectivity each IP switch knows about the IP routing topology of the entire network. Thus, it knows which IP switch is connected to which host.
i As well known to one of ordinary skill, direct connectivity may be achieved in a number of different_way_s.For example, a mesh of virtual paths may be employed, in which each IP
switch is connected to every other IP switch with a point-to-point (ptp) virtual path. The switch-to-switch virtual path can be a semi-permanent switched circuit or a permanent virtual circuit.
Such a topology yields N-squared point-to-point virtual paths between N
switches. Many segments of the point-to-point virtual paths may run over common physical links. Alternatively, direct connectivity may be achieved by using a point-to-multipoint (i.e., multicasting) connection in which one IP switch serves as the so-called root and all other switches serve as so-called leaves. In such a network having N IP switches, only N point-to-multipoint connections are required, thus considerably reducing the number of connections in comparison to a point-to-point topology. Point-to-multipoint connections may be used to transmit unicast packets as well as broadcast packets by having the packet originate at an IP switch serving as one of the leaves.
In this case the root IP switch serves as the destination receiving the unicast packet.
IP switching on the Internet Backbone The current Internet backbone consists of large-scale routers which are interconnected with private lines at a DS3 (45 Mbps) rate. However, in the future it would be advantageous to use an ATM backbone rather than a DS3 backbone. Such an ATM backbone network may employ IP switches since IP switching is optimized for IP routing over an ATM
network and thus represents a near ideal switch for the Internet backbone. If IP switching were to be employed in the current Internet, the legacy routers currently employed would be upgraded to IP
switches, which, with backbone facilities running the ATM protocol, can operate at rates up to an OC 12. The ATM backbone may employ direct connectivity, either point-to-point or point-to-multipoint, both of which require only two hop paths to cross the ATM network and use best effort connections to accommodate the least common denominator quality of service.
FIG. 3 shows a simplified, exemplary diagram of an IP switched ATM network in accordance with the present invention which offers the user or service provider a greater variety of selectable options. The network is accessible via client end-points that may be conveniently classified as either an ATM end-point or a non-ATM endpoint. ATM end-points, such as client 52 in FIG. 3, directly access an IP switch that is located at the periphery of the Internet backbone via an ATM UNI. ATM end-points run IP over ATM using known protocols such as LANE, Classical IP Over ATM, or Multiprotocol Over ATM. Non-ATM end points, such as client 51 in FIG. 3, access an IP switch located at the periphery of the Internet backbone via a non-ATM
technology such as Frame-Relay, ISDN or analog lines, all of which run the IP
protocol. A
protocol adaptation function may be located between the non-ATM end-point and the IP switch.
Alternatively, the peripheral IP switch may directly support non-ATM
interfaces.
As seen in FIG. 3, an Internet attached server 53 functions as an agent or proxy through which a client may request special services by allowing the client or service provider to specify client characteristics or desired service attributes. The proxy server 53 is typically a Web-server that is administered by the Internet service provider. The client may access the proxy server 53 via a Web-browser that is secured by a password. Once access is provided, the client may conveniently select the desired service attribute or attributes from a list of attributes. The client specifies to the proxy server 53 one or more desired service attributes pertaining to the quality of service. For purposes of illustration, service attributes include the type of access requested by the client such as ATM or non-ATM (dial, ISDN, etc.) and Quality of Service (QOS) requirements, which may be defined per application, destination, time-of day, and/or per port. Additional service attributes that may be specified via the proxy server 53 include the IP address of the host (if known), the IntraNet name, the host name and billing address, a credit card number or any special filters.
The proxy server 53 also may be employed to appropriately configure the end-point. For example, the proxy server 53 may provide to the user the NHS address or IP
switch address to which the end-point should connect.
As seen in FIG. 3, the proxy server 53 functions in cooperation with an Internet network control point (NCP) 54. The NCP 54, which is analagous to known network control points used in telephone networks that employ intelligent call processing, is the master database of the network which stores end-point information such as the correspondence between ATM, IP and MAC addresses, QoS requirements, special security filters, and billing properties. End-points can access the NCP 54 via the proxy server 53 to retrieve information and update the database as appropriate. That is, the proxy server 53 functions as a client interface to the NCP 54. The NCP
54 also may be updated in an automatic fashion by the individual IP switches in the network, such as when an end-point registers or unregisters an IP to ATM address correspondence or a particular QoS.
The individual IP switches within the Internet backbone each have an address database 56 that contains essentially a subset of the data in the NCP 54. At a minimum, the address databases 56 contain the correspondence between the ATM and IP addresses for their respective end-points. In contrast to an NHS, which only supports an ATM end-point, the address databases 56 support both ATM and non-ATM endpoints. Accordingly, the address databases 56 serve as NHS's with enhanced functionality.
The address databases 56 may be employed not only to construct an ATM cut-through across the Internet backbone, but also to specify a desired quality of service across the Internet backbone. If both the source and destination end-points access the backbone via ATM, a cut-though is feasible, assuming the source end-point can map the IP address of the destination end-point to its ATM address.
The address database may also perform additional functions such as: receiving updated IP-ATM address registrations from clients or other address databases;
receiving IP-ATM
address de-registration requests from clients or other address databases;
adding or deleting IP to ATM address correspondences from the database; receiving address queries from clients or other address databases; forwarding address query requests to clients or other address databases;
forwarding address query responses; and receiving provisioned end-point information updates from the Internet NCP.
The addxess databases may be implemented in any convenient manner. Two possible implementations are a fully distributed implementation and a fully duplicated implementation.
In the fully distributed approach, each IP switch only maintains an address database for those end-points that access the Internet at that particular IP switch. Accordingly, there is no need for synchronization among different address databases in different IP switches.
For example, when a source end-point sends an address query to its IP switch regarding a destination end-point and the IP to ATM address correspondence is not found in the queried IP switch, the switch will forward the request only to the IP switch responsible for the destination end-point. In a fully distributed arrangement, the Internet NCP serves as the master database that stores alI
provisioned information for the network, including the IP to ATM address correspondences.
When a change in the address database of an IP switch occurs (due to a host disconnecting from the IP switch, for example), the same change is forwarded to the Internet NCP
to update the master database. Similarly, when the Internet NCP is modified by the service provider or the user, the appropriate individual address databases) within the IP switch(es) will be updated accordingly.
If the address databases 56 are configured in a fully-duplicated arrangement, each IP
switch maintains the database for all the end-points. When a new database entry is registered with a given IP switch, that registration is sent to all other IP switches.
Accordingly, the address databases of all the IP switches are identical. That is, while the Internet NCP contains the master copy of the database, each IP switch maintains its own complete copy of the database. Similar to the fully distributed arrangement, if an IP switch makes a change in its database, the change will be reflected in all the other address databases, including the master database of the Internet NCP. Likewise, if a change is made to the Internet NCP database, it will be reflected in all the other address databases.
FIG. 4 shows a flow chart illustrating the steps performed when client 51 initiates communication with server 52 with an address database that is arranged in a fully distributed manner. In step 41, the client 51 sends to IP switch 57 the first IP packet addressed to server 52.
In step 43, IP switch 57 determines if its address database 56 has an entry for server 52. If IP
switch 57 does not have such an entry, it sends a query to the next hop database in step 47 to determine the address of server 52. Once IP switch 57 receives the appropriate address, it then obtains the requested service attributes for server 52 in step 49. In step 51, IP switch 57 accesses whether the requested service attributes require any special treatment. If they do not, in step 53 IP switch 57 routes the packet on a switched virtual circuit using default parameters. If special treatment is required, in step 55 IP switch 57 routes the call in conformance with the requested service parameters.
Claims (23)
1. A telecommunications network for establishing communication between at least one originating station and at least one destination station, comprising:
a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol;
a server, coupled to at least one of the IP switches, for receiving at least one service attribute requested by an originating station in communication with the IP switch;
a network control point (NCP) for providing data in response to a request from the server for providing said at least one service attribute;
at least one address database associated with each of the IP switches, said at least one address database including a subset of the data available in the NCP.
a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol;
a server, coupled to at least one of the IP switches, for receiving at least one service attribute requested by an originating station in communication with the IP switch;
a network control point (NCP) for providing data in response to a request from the server for providing said at least one service attribute;
at least one address database associated with each of the IP switches, said at least one address database including a subset of the data available in the NCP.
2. The network of claim 1 wherein said address database includes ATM to IP
address correspondence data for end-point stations coupled to the IP switch with which said address database is associated.
address correspondence data for end-point stations coupled to the IP switch with which said address database is associated.
3. The network of claim 1 wherein said address database includes ATM to telephone number address correspondence data for end-point stations coupled to the IP switch with which said address database is associated.
4. The network of claim 1 wherein said address database includes ATM to MAC
address correspondence data for end-point stations coupled to the IP switch with which said address database is associated.
address correspondence data for end-point stations coupled to the IP switch with which said address database is associated.
5. The network of claim 1 wherein said address databases are implemented in a fully distributed manner.
6. The network of claim 1 wherein said address databases are implemented in a fully duplicated manner.
7. The network of claim 6 wherein said address database incorporates a next hop server (NHS) address correspondence data for routing the IP packet to the destination station.
8. The network of claim 1 wherein said data provided by the NCP pertaining to an end-point destination is selected from the group consisting of end-point information, quality of service requirements, security filters, and billing arrangements.
9. The network of claim 1 wherein said server receives the service attribute from a station in accordance with an IP protocol.
10. The network of claim 1 wherein said service attributes include a specification of an interface for establishing a connection between an originating station and a destination station.
11. The network of claim 10 wherein said interface is selected from the group consisting of an ATM interface, an analog interface, a digital interface, a frame relay interface and a private line interface.
12. The network of claim 11 wherein said digital interface is an ISDN
interface.
interface.
13. The network of claim 1 wherein said service attributes include quality of service requirements.
14. The network of claim 13 wherein said quality of service requirements are specifiable on a user-application basis.
15. The network of claim 13 wherein said quality of service requirements are specifiable on a time-of-day basis.
16. The network of claim 1 wherein said originating station has a dial interface and said destination station has an ATM interface so that a cut-through path is established between an IP switch associated with said originating station and said destination station.
17. The network of claim 1 wherein said originating station has an ATM
interface and said destination station has a dial interface so that a cut-through path is established between said originating station and an IP switch associated with said destination station.
interface and said destination station has a dial interface so that a cut-through path is established between said originating station and an IP switch associated with said destination station.
18. The network of claim 1 wherein said originating station and said destination station have an ATM interface so that a cut-through path is established between said originating station and said destination station.
19. The network of claim 1 wherein said originating station has a dial interface and said destination station has a dial interface so that a cut-through path is established between an IP switch associated with said originating station and an IP switch associated with said destination station.
20. A method for establishing communication between at least one originating station and at least one destination station over a network including a plurality of IP switches for addressing and routing data in accordance with an Internet protocol and an ATM protocol, said method comprising the steps of:
receiving an IP packet from the originating station addressed to the destination station;
identifying an entry in an address database, that includes a subset of data available in a Network Control Point (NCP), for providing data in response to a request for information, the database containing address correspondence data for routing the IP packet to the destination station;
identifying, by launching an inquiry to the NCP, at least one service attribute associated with transmission of the IP packet to the destination station;
routing the IP packet to the destination station in accordance with the service attribute.
receiving an IP packet from the originating station addressed to the destination station;
identifying an entry in an address database, that includes a subset of data available in a Network Control Point (NCP), for providing data in response to a request for information, the database containing address correspondence data for routing the IP packet to the destination station;
identifying, by launching an inquiry to the NCP, at least one service attribute associated with transmission of the IP packet to the destination station;
routing the IP packet to the destination station in accordance with the service attribute.
21. The method of claim 20 wherein the step of identifying an entry in an address database comprises the step of transmitting a query to a next hop IP switch requesting said address correspondence data for routing the IP packet to the destination station.
22. The method of claim 20 wherein said service attribute includes a default parameter.
23. The method of claim 20 wherein said service attribute is requested by the originating station.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US728,276 | 1991-07-11 | ||
| US08/728,276 US5828844A (en) | 1996-10-08 | 1996-10-08 | Internet NCP over ATM |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2216982A1 CA2216982A1 (en) | 1998-04-08 |
| CA2216982C true CA2216982C (en) | 2001-05-01 |
Family
ID=24926168
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002216982A Expired - Fee Related CA2216982C (en) | 1996-10-08 | 1997-09-30 | Internet ncp over atm |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US5828844A (en) |
| EP (1) | EP0836359B1 (en) |
| JP (1) | JPH10215263A (en) |
| CA (1) | CA2216982C (en) |
| DE (1) | DE69737342T2 (en) |
Families Citing this family (126)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9603582D0 (en) | 1996-02-20 | 1996-04-17 | Hewlett Packard Co | Method of accessing service resource items that are for use in a telecommunications system |
| JPH09186723A (en) | 1995-12-29 | 1997-07-15 | Hitachi Ltd | Network communication processing system |
| US6021263A (en) * | 1996-02-16 | 2000-02-01 | Lucent Technologies, Inc. | Management of ATM virtual circuits with resources reservation protocol |
| US6154445A (en) | 1996-04-18 | 2000-11-28 | Bell Atlantic Network Services, Inc. | Telephony communication via varied redundant networks |
| US6069890A (en) | 1996-06-26 | 2000-05-30 | Bell Atlantic Network Services, Inc. | Internet telephone service |
| JP2982727B2 (en) * | 1996-08-15 | 1999-11-29 | 日本電気株式会社 | Authentication method |
| JPH1079740A (en) * | 1996-09-03 | 1998-03-24 | Hitachi Ltd | Router device using atm switch |
| JP3455032B2 (en) * | 1996-10-31 | 2003-10-06 | 株式会社日立製作所 | Communications system |
| US6101180A (en) | 1996-11-12 | 2000-08-08 | Starguide Digital Networks, Inc. | High bandwidth broadcast system having localized multicast access to broadcast content |
| US6078582A (en) | 1996-12-18 | 2000-06-20 | Bell Atlantic Network Services, Inc. | Internet long distance telephone service |
| SE511581C2 (en) * | 1996-12-20 | 1999-10-25 | Ericsson Telefon Ab L M | System and method for ATM connection of a telephone connection |
| US5903559A (en) * | 1996-12-20 | 1999-05-11 | Nec Usa, Inc. | Method for internet protocol switching over fast ATM cell transport |
| JP2842530B2 (en) * | 1997-01-08 | 1999-01-06 | 日本電気株式会社 | ATM VLAN client-server system |
| US6061346A (en) * | 1997-01-17 | 2000-05-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Secure access method, and associated apparatus, for accessing a private IP network |
| JP3591753B2 (en) * | 1997-01-30 | 2004-11-24 | 富士通株式会社 | Firewall method and method |
| JP3653917B2 (en) * | 1997-02-25 | 2005-06-02 | 富士通株式会社 | Packet relay method and end system in communication network |
| US6137869A (en) | 1997-09-16 | 2000-10-24 | Bell Atlantic Network Services, Inc. | Network session management |
| US6574216B1 (en) | 1997-03-11 | 2003-06-03 | Verizon Services Corp. | Packet data network voice call quality monitoring |
| JP3457493B2 (en) * | 1997-03-18 | 2003-10-20 | 富士通株式会社 | ARP server |
| US6292479B1 (en) | 1997-03-19 | 2001-09-18 | Bell Atlantic Network Services, Inc. | Transport of caller identification information through diverse communication networks |
| US6870827B1 (en) | 1997-03-19 | 2005-03-22 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
| US6009097A (en) * | 1997-04-04 | 1999-12-28 | Lucent Technologies Inc. | System for routing packet switched traffic |
| US6026085A (en) | 1997-04-08 | 2000-02-15 | 3Com Corporation | Architecture to support a single system image across multiple network access servers |
| US6278705B1 (en) * | 1997-04-08 | 2001-08-21 | 3Com Corporation | Integrated architecture to support a single system image across multiple network access servers |
| US5936936A (en) * | 1997-04-11 | 1999-08-10 | International Business Machines Corporation | Redundancy mechanisms for classical internet protocol over asynchronous transfer mode networks |
| JP2002513535A (en) * | 1997-04-25 | 2002-05-08 | ノーテル・ネットワークス・リミテッド | Method and apparatus for ATM address determination |
| US6260072B1 (en) * | 1997-06-12 | 2001-07-10 | Lucent Technologies Inc | Method and apparatus for adaptive routing in packet networks |
| JPH113307A (en) * | 1997-06-13 | 1999-01-06 | Canon Inc | Information processor and its method |
| US6324183B1 (en) | 1998-12-04 | 2001-11-27 | Tekelec | Systems and methods for communicating messages among signaling system 7 (SS7) signaling points (SPs) and internet protocol (IP) nodes using signal transfer points (STPS) |
| US7050456B1 (en) * | 1998-12-04 | 2006-05-23 | Tekelec | Methods and systems for communicating signaling system 7 (SS7) user part messages among SS7 signaling points (SPs) and internet protocol (IP) nodes using signal transfer points (STPs) |
| US6944184B1 (en) | 1998-12-04 | 2005-09-13 | Tekelec | Methods and systems for providing database node access control functionality in a communications network routing node |
| JPH1198183A (en) * | 1997-09-17 | 1999-04-09 | Toshiba Corp | Repeater |
| JPH1198191A (en) * | 1997-09-19 | 1999-04-09 | Nec Corp | Ip switch |
| CA2217275C (en) * | 1997-10-03 | 2005-08-16 | Newbridge Networks Corporation | Multiple internetworking realms within an internetworking device |
| US6614765B1 (en) * | 1997-10-07 | 2003-09-02 | At&T Corp. | Methods and systems for dynamically managing the routing of information over an integrated global communication network |
| US6147993A (en) | 1997-10-14 | 2000-11-14 | Cisco Technology, Inc. | Method and apparatus for implementing forwarding decision shortcuts at a network switch |
| US6189041B1 (en) * | 1997-11-12 | 2001-02-13 | International Business Machines Corporation | Next hop resolution protocol cut-through to LANs |
| US6222826B1 (en) * | 1997-11-19 | 2001-04-24 | Lucent Technologies Inc. | Multimedia calling method and apparatus |
| US6307860B1 (en) | 1998-04-03 | 2001-10-23 | Mmc Networks, Inc. | Systems and methods for data transformation and transfer in networks |
| US6343083B1 (en) * | 1998-04-09 | 2002-01-29 | Alcatel Usa Sourcing, L.P. | Method and apparatus for supporting a connectionless communication protocol over an ATM network |
| US6279035B1 (en) * | 1998-04-10 | 2001-08-21 | Nortel Networks Limited | Optimizing flow detection and reducing control plane processing in a multi-protocol over ATM (MPOA) system |
| JP3233208B2 (en) * | 1998-04-30 | 2001-11-26 | 日本電気株式会社 | Layer 3 flow switching method |
| US7079515B1 (en) * | 1998-05-15 | 2006-07-18 | Ericsson, Inc. | Signal decoding with and without second synchronization word in a mobile communication system |
| WO1999066758A2 (en) | 1998-06-19 | 1999-12-23 | Unisphere Solutions, Inc. | An interconnect network for operation within a communication node |
| US6980543B1 (en) * | 1998-06-19 | 2005-12-27 | Juniper Networks, Inc. | Interconnect network for operation within a communication node |
| US6356548B1 (en) | 1998-06-29 | 2002-03-12 | Cisco Technology, Inc. | Pooled receive and transmit queues to access a shared bus in a multi-port switch asic |
| US6078586A (en) * | 1998-08-03 | 2000-06-20 | Mci Communications Corporation | ATM virtual private networks |
| US6615358B1 (en) | 1998-08-07 | 2003-09-02 | Patrick W. Dowd | Firewall for processing connection-oriented and connectionless datagrams over a connection-oriented network |
| US7073196B1 (en) | 1998-08-07 | 2006-07-04 | The United States Of America As Represented By The National Security Agency | Firewall for processing a connectionless network packet |
| US6442588B1 (en) * | 1998-08-20 | 2002-08-27 | At&T Corp. | Method of administering a dynamic filtering firewall |
| US6445715B1 (en) | 1998-08-27 | 2002-09-03 | Cisco Technology, Inc. | Dynamic trunk protocol |
| US6295296B1 (en) | 1998-09-08 | 2001-09-25 | Cisco Technology, Inc. | Use of a single data structure for label forwarding and imposition |
| US6266705B1 (en) | 1998-09-29 | 2001-07-24 | Cisco Systems, Inc. | Look up mechanism and associated hash table for a network switch |
| US6731627B1 (en) * | 1998-11-17 | 2004-05-04 | Cisco Technology, Inc. | Virtual loop carrier system |
| US7246168B1 (en) | 1998-11-19 | 2007-07-17 | Cisco Technology, Inc. | Technique for improving the interaction between data link switch backup peer devices and ethernet switches |
| US6704318B1 (en) | 1998-11-30 | 2004-03-09 | Cisco Technology, Inc. | Switched token ring over ISL (TR-ISL) network |
| US6563832B1 (en) | 1998-11-30 | 2003-05-13 | Cisco Technology, Inc. | Token ring bridge distributed in a switched fabric |
| JP5113963B2 (en) * | 1998-12-03 | 2013-01-09 | ノーテル・ネットワークス・リミテッド | Provision of desired service policies to subscribers accessing the Internet |
| US6466976B1 (en) | 1998-12-03 | 2002-10-15 | Nortel Networks Limited | System and method for providing desired service policies to subscribers accessing the internet |
| US6633563B1 (en) | 1999-03-02 | 2003-10-14 | Nortel Networks Limited | Assigning cell data to one of several processors provided in a data switch |
| US6987781B1 (en) | 1998-12-04 | 2006-01-17 | Tekelec | Methods and systems for routing signaling messages in a communications network using circuit identification code (CIC) information |
| US7002988B1 (en) | 1998-12-04 | 2006-02-21 | Tekelec | Methods and systems for communicating SS7 messages over packet-based network using transport adapter layer interface |
| US6609153B1 (en) | 1998-12-24 | 2003-08-19 | Redback Networks Inc. | Domain isolation through virtual network machines |
| US6748416B2 (en) * | 1999-01-20 | 2004-06-08 | International Business Machines Corporation | Client-side method and apparatus for improving the availability and performance of network mediated services |
| US6574664B1 (en) * | 1999-01-29 | 2003-06-03 | Hewlett-Packard Development Company, L.P. | Apparatus and method for IP and MAC address discovery at the process layer |
| JP2000242574A (en) * | 1999-02-22 | 2000-09-08 | Mitsubishi Electric Corp | Data transfer method and scheduled transfer destination database generating method |
| JP3082760B1 (en) * | 1999-02-26 | 2000-08-28 | 日本電気株式会社 | MPOA packet transfer method |
| DE19910023C2 (en) * | 1999-03-08 | 2002-07-18 | Rohde & Schwarz | System for data transmission from a provider to a user |
| US7474660B1 (en) | 1999-03-31 | 2009-01-06 | Cisco Technology, Inc. | MAC address extension to maintain router information in source routed computer networks |
| US6954526B1 (en) | 1999-04-05 | 2005-10-11 | Tekelec | Methods and systems for routing calling name service query messages in a communication network |
| EP1045611B1 (en) * | 1999-04-12 | 2006-03-22 | Alcatel | Method of supporting shortcuts in the network layer |
| US6401127B1 (en) | 1999-05-04 | 2002-06-04 | Cisco Technology, Inc. | Adaptive timer for LLC type 2 reliable transport in a computer network |
| US7136387B2 (en) * | 1999-08-09 | 2006-11-14 | Mci, Llc | Method of and system for providing quality of service in IP telephony |
| US6714541B1 (en) | 1999-08-10 | 2004-03-30 | Cisco Technology, Inc. | Method and apparatus for encoding bridging/switching information within a routing information filed in a token ring environment |
| KR100326332B1 (en) * | 1999-09-06 | 2002-03-08 | 윤종용 | Method for communicating between terminal of packet-based network and terminal to be connected through remote access server |
| US7388846B1 (en) | 1999-09-08 | 2008-06-17 | Qwest Communications International Inc. | Cellularized packetized voice and data |
| US6831902B1 (en) | 1999-09-08 | 2004-12-14 | Qwest Communications International, Inc. | Routing information packets in a distributed network |
| US6483470B1 (en) | 1999-09-08 | 2002-11-19 | Qwest Communications International, Inc. | Power supply for a light pole mounted wireless antenna |
| US6987769B1 (en) | 1999-09-08 | 2006-01-17 | Qwest Communications International Inc. | System and method for dynamic distributed communication |
| US8005077B1 (en) | 1999-09-08 | 2011-08-23 | Qwest Communications International Inc. | Distributively routed VDSL and high-speed information packets |
| US7561895B1 (en) | 1999-09-08 | 2009-07-14 | Qwest Communications International, Inc. | Reverse sectorization wireless communication |
| US6898200B1 (en) * | 1999-10-29 | 2005-05-24 | Nortel Networks Limited | Method for improving signaling efficiency and performing service load balancing in a connection oriented network |
| US6529983B1 (en) | 1999-11-03 | 2003-03-04 | Cisco Technology, Inc. | Group and virtual locking mechanism for inter processor synchronization |
| FR2800956B1 (en) * | 1999-11-10 | 2002-02-22 | Sagem | FAX SYSTEM WITH CENTRAL DIRECTORY |
| US6785738B1 (en) | 1999-12-23 | 2004-08-31 | Cisco Technology, Inc. | ARP packet to preserve canonical form of addresses |
| KR100360776B1 (en) * | 1999-12-24 | 2002-11-13 | 한국전자통신연구원 | MPOA based router system and method for service interworking between MPOA based router system and frame relay network |
| US6751218B1 (en) * | 2000-02-26 | 2004-06-15 | Avaya Technology Corp. | Method and system for ATM-coupled multicast service over IP networks |
| SE518422C2 (en) * | 2000-03-10 | 2002-10-08 | Ericsson Telefon Ab L M | Method and apparatus for point-to-point connections in a communication network |
| AU2001255546A1 (en) | 2000-04-21 | 2001-11-07 | Tekelec | Methods and systems for providing dynamic routing key registration |
| US6505269B1 (en) | 2000-05-16 | 2003-01-07 | Cisco Technology, Inc. | Dynamic addressing mapping to eliminate memory resource contention in a symmetric multiprocessor system |
| US7318091B2 (en) * | 2000-06-01 | 2008-01-08 | Tekelec | Methods and systems for providing converged network management functionality in a gateway routing node to communicate operating status information associated with a signaling system 7 (SS7) node to a data network node |
| US7126947B2 (en) * | 2000-06-23 | 2006-10-24 | Broadcom Corporation | Switch having external address resolution interface |
| US6967956B1 (en) | 2000-07-18 | 2005-11-22 | Tekelec | Methods and systems for providing message translation, accounting and routing service in a multi-protocol communications network environment |
| US7092390B2 (en) * | 2000-09-07 | 2006-08-15 | Sbc Technology Resources, Inc. | Internal substitution bi-level addressing for compatible public networks |
| US6990089B2 (en) * | 2000-12-12 | 2006-01-24 | Telelec | Methods and systems for routing messages in a radio access network |
| US6965592B2 (en) * | 2001-01-24 | 2005-11-15 | Tekelec | Distributed signaling system 7 (SS7) message routing gateway |
| US7200146B2 (en) * | 2001-08-17 | 2007-04-03 | Intel Corporation | System and method of IP packet forwarding across directly connected forwarding elements |
| US7403986B1 (en) | 2001-10-18 | 2008-07-22 | Network Equipment Technologies, Inc. | Method for synchronizing circuit related objects between network management systems and network control processors |
| US7298750B2 (en) * | 2002-07-31 | 2007-11-20 | At&T Knowledge Ventures, L.P. | Enhancement of resource reservation protocol enabling short-cut internet protocol connections over a switched network |
| US7301951B2 (en) * | 2002-07-31 | 2007-11-27 | At&T Knowledge Ventures, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network |
| US7272145B2 (en) * | 2002-07-31 | 2007-09-18 | At&T Knowledge Ventures, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network through proxy signaling |
| US7065092B2 (en) * | 2002-07-31 | 2006-06-20 | Sbc Properties, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol (IP) connections over a switched network using newly assigned IP addresses |
| US7739394B2 (en) * | 2003-07-29 | 2010-06-15 | At&T Intellectual Property I, L.P. | Bi-level addressing for internet protocol broadband access |
| US7447203B2 (en) * | 2003-07-29 | 2008-11-04 | At&T Intellectual Property I, L.P. | Broadband access for virtual private networks |
| US7876757B2 (en) * | 2003-11-06 | 2011-01-25 | International Business Machines Corporation | Router-assisted fast processing of packet termination in host |
| US7769011B1 (en) * | 2003-12-24 | 2010-08-03 | Embarq Holdings Company, Llc | Method and system for automatically requesting, generating and maintaining ATM addresses |
| US7804789B2 (en) | 2004-03-18 | 2010-09-28 | Tekelec | Methods, systems, and computer program products for organizing, managing, and selectively distributing routing information in a signaling message routing node |
| US7532647B2 (en) | 2004-07-14 | 2009-05-12 | Tekelec | Methods and systems for auto-correlating message transfer part (MTP) priority and internet protocol (IP) type of service in converged networks |
| US7796614B1 (en) * | 2004-11-30 | 2010-09-14 | Symantec Corporation | Systems and methods for message proxying |
| US7965771B2 (en) | 2006-02-27 | 2011-06-21 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
| US8218654B2 (en) | 2006-03-08 | 2012-07-10 | Cisco Technology, Inc. | Method for reducing channel change startup delays for multicast digital video streams |
| US8031701B2 (en) | 2006-09-11 | 2011-10-04 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
| US10031830B2 (en) * | 2006-10-13 | 2018-07-24 | International Business Machines Corporation | Apparatus, system, and method for database management extensions |
| US7937531B2 (en) * | 2007-02-01 | 2011-05-03 | Cisco Technology, Inc. | Regularly occurring write back scheme for cache soft error reduction |
| US8769591B2 (en) | 2007-02-12 | 2014-07-01 | Cisco Technology, Inc. | Fast channel change on a bandwidth constrained network |
| US7940644B2 (en) * | 2007-03-14 | 2011-05-10 | Cisco Technology, Inc. | Unified transmission scheme for media stream redundancy |
| US20080253369A1 (en) | 2007-04-16 | 2008-10-16 | Cisco Technology, Inc. | Monitoring and correcting upstream packet loss |
| US8279826B1 (en) * | 2007-07-19 | 2012-10-02 | Sprint Communications Company L.P. | Presence based routing in an IP multimedia subsystem network |
| US9043451B2 (en) | 2007-07-31 | 2015-05-26 | Tekelec, Inc. | Methods, systems, and computer readable media for managing the flow of signaling traffic entering a signaling system 7 (SS7) based network |
| US8787153B2 (en) | 2008-02-10 | 2014-07-22 | Cisco Technology, Inc. | Forward error correction based data recovery with path diversity |
| WO2010083509A2 (en) | 2009-01-16 | 2010-07-22 | Tekelec | Methods, systems, and computer readable media for centralized routing and call instance code management for bearer independent call control (bicc) signaling messages |
| US8670320B2 (en) * | 2009-02-09 | 2014-03-11 | Hewlett-Packard Development Company, L.P. | Quality of service routing architecture |
| US8238538B2 (en) | 2009-05-28 | 2012-08-07 | Comcast Cable Communications, Llc | Stateful home phone service |
| EP2534811B1 (en) | 2010-02-12 | 2018-08-08 | Tekelec, Inc. | Methods, systems, and computer readable media for diameter network management |
| US9168946B2 (en) * | 2010-03-19 | 2015-10-27 | Javad Gnss, Inc. | Method for generating offset paths for ground vehicles |
| US8787388B1 (en) * | 2011-08-29 | 2014-07-22 | Big Switch Networks, Inc. | System and methods for forwarding packets through a network |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH06318951A (en) * | 1993-01-07 | 1994-11-15 | Toshiba Corp | Method and system for transferring cell |
| US5673262A (en) * | 1993-06-03 | 1997-09-30 | Nec Corporation | Communication network comprising transit switches without asynchronous transfer mode switching capability |
| US5461611A (en) * | 1994-06-07 | 1995-10-24 | International Business Machines Corporation | Quality of service management for source routing multimedia packet networks |
| US5673263A (en) * | 1995-03-31 | 1997-09-30 | International Business Machines Corporation | Method for using an IP address-based routing protocol in an ATM environment |
| JP2723084B2 (en) * | 1995-07-19 | 1998-03-09 | 日本電気株式会社 | Link state routing device |
-
1996
- 1996-10-08 US US08/728,276 patent/US5828844A/en not_active Expired - Fee Related
-
1997
- 1997-09-30 CA CA002216982A patent/CA2216982C/en not_active Expired - Fee Related
- 1997-10-01 EP EP97307736A patent/EP0836359B1/en not_active Expired - Lifetime
- 1997-10-01 DE DE69737342T patent/DE69737342T2/en not_active Expired - Lifetime
- 1997-10-07 JP JP9274846A patent/JPH10215263A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| DE69737342T2 (en) | 2007-10-31 |
| DE69737342D1 (en) | 2007-03-29 |
| CA2216982A1 (en) | 1998-04-08 |
| EP0836359B1 (en) | 2007-02-14 |
| US5828844A (en) | 1998-10-27 |
| JPH10215263A (en) | 1998-08-11 |
| EP0836359A3 (en) | 1999-08-25 |
| EP0836359A2 (en) | 1998-04-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2216982C (en) | Internet ncp over atm | |
| US5996021A (en) | Internet protocol relay network for directly routing datagram from ingress router to egress router | |
| US5600644A (en) | Method and apparatus for interconnecting LANs | |
| EP1021931B1 (en) | Multiple internetworking realms within an internetworking device | |
| US6516000B1 (en) | Communications system for transmission of datagram packets over connection-oriented networks | |
| US6351465B1 (en) | System for routing packet switched traffic | |
| US6205146B1 (en) | Method of dynamically routing to a well known address in a network | |
| EP0903028B1 (en) | Connection aggregation in switched communications networks | |
| US6587467B1 (en) | Virtual channel multicast utilizing virtual path tunneling in asynchronous mode transfer networks | |
| EP1021890B1 (en) | Virtual path merging in a multipoint-to-point network tunneling protocol | |
| US6289017B1 (en) | Method of providing redundancy and load sharing among multiple LECs in an asynchronous mode network | |
| Chen et al. | Evolution of ATM internetworking | |
| Catania et al. | A routing strategy for MAN interconnection | |
| Xu | IP over ATM: Classical IP, NHRP, LANE, MPOA, PAR and I-PNNI | |
| Woodworth et al. | Connection request protocol (CRP) for IP over ATM | |
| KR100261291B1 (en) | Global address resolution method for ipoa(internet protocol and address resolution protocol over atm) | |
| Kim et al. | A way to accommodate IP services in ATM access networks | |
| Haas et al. | PNNI augmented routing (PAR) and proxy-PAR | |
| JP2001197076A (en) | Ip packet transfer method for atm network and ip packet repeating system | |
| Kim et al. | IPOA with LAG model: for easy implementation and guaranteeing high performance | |
| Kim et al. | Global address resolution scheme for IP and ARP over ATM | |
| Kim et al. | BGP based shortcut virtual channels for transit IP traffic over ATM networks | |
| Park et al. | Next hop resolution using classical IP over ATM | |
| Lengerli et al. | Understanding and Using MSS Release 1.1 and 2.0 | |
| Park et al. | IP routing on logical address group |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |