WO1998042107A1 - Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony - Google Patents
Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony Download PDFInfo
- Publication number
- WO1998042107A1 WO1998042107A1 PCT/US1998/004091 US9804091W WO9842107A1 WO 1998042107 A1 WO1998042107 A1 WO 1998042107A1 US 9804091 W US9804091 W US 9804091W WO 9842107 A1 WO9842107 A1 WO 9842107A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- udp
- packets
- packet
- tcp
- addressee
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/164—Adaptation or special uses of UDP protocol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/165—Combined use of TCP and UDP protocols; selection criteria therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
- H04L2012/6424—Access arrangements
- H04L2012/6427—Subscriber Access Module; Concentrator; Group equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
- H04L2012/6472—Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
- H04L2012/6475—N-ISDN, Public Switched Telephone Network [PSTN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
Definitions
- the present invention relates to communication protocols in digital networks. More particularly, the invention relates to methods and apparatus for protocol conversion in order to minimize latency and to improve efficiency and quality of packet transmission in applications including Internet telephony.
- TCP transmission control protocol
- VDP Van Jacobsen compression
- the present invention provides methods and apparatus for protocol conversion between transmission control protocol (“TCP”) and user datagram protocol (“UDP”) .
- TCP is used between the user and the local host.
- TCP is suitable for use in a modem link between a local user and an Internet Service Provider ("ISP"), because the modem itself provides a reliable connection, detecting and resending lost data.
- ISP Internet Service Provider
- This provides a reliable, connection-oriented transmission which can transmit small packets within the bandwidth provided by a typical modem and consistent with local telephone connections such as those provided by twisted wire pairs and standard telephone wires connecting most people to the phone network.
- the latency caused by TCP's detection and resending of lost packets is tolerable, because very few packets are lost at the connection between the user and the local host.
- each packet arrives at the local host, it is converted to UDP format and transmitted over the Internet. While the UDP packets have a big header and thus a high overhead with respect to the amount of data per packet, the local host is able to transmit such packets using UDP with low latency, because the bandwidth between the local host networks is great enough to tolerate the overhead caused by the large header size of the UDP packets.
- the packet arrives at the destination node of the local host network, it is reconverted to TCP, and thence transmitted to the user of the destination node. This conversion allows for the transmission of low latency small packets. By tailoring the protocols used to take advantage of the characteristics of the different connections, significant improvements in efficiency and quality of service may be achieved.
- Fig. 1 is an illustration of a packet transmission network of the prior art, showing connection protocols typically employed for packet transmission between users and hosts, between hosts within a single host network, and between networks;
- Fig. 2 is a packet transmission network employing a protocol conversion system according to the present invention, illustrating the protocols employed between the various nodes of the network;
- Fig. 3 is a more detailed illustration of a protocol conversion system according to the present invention.
- Fig. 4 is a detailed block diagram showing the use of a protocol conversion system according to the present invention, in which an active user registry server is employed in an Internet Service Provider which connects to clients using differing connection methods and which also transmits data to and from other Internet Service Providers which do not use a protocol conversion system according to the present invention;
- Fig. 5 is a diagram showing in greater detail the active user registry server shown in Fig. 4.
- Fig. 6 is a flowchart illustrating a protocol conversion process in accordance with the present invention.
- Fig. 1 illustrates a representative link 10 of the prior art between two data packet networks 36 and 38.
- First network 36 serves users ⁇ , 14, 16 and 18, respectively, and second network 38 serves users 4 . 6 , 30, 32 and 34.
- Users ⁇ communicate with a first local server in a first host node 22 using UDP.
- First host node 22 communicates with a first network communication node 24 using UDP.
- First network communication node 24 and a second network communication node 26 also communicate with one another using UDP.
- the second network communication node 26 communicates with a second host node 28 using UDP.
- Host node 28 communicates with users 4 . 6 , 30, 32 and 34 using UDP.
- UDP is defined at the transport layer and provides the application layer with a fast but unreliable, connectionless delivery system.
- UDP data units are datagrams. A datagram is encapsulated within an IP header.
- the header portions of UDP packets are long. Thus, the overhead for UDP packets is inherently quite large. This problem is typically overcome by making UDP packets large. With sufficiently large UDP packets, the header represents a relatively small portion of the total packet. If used to transmit small packets, however, as would be needed for high- quality Internet telephony, the large headers used by UDP would represent a large proportion of the packet size.
- UDP throughout the first and second networks 36 and 38 provides a fast, connectionless data transfer system between the networks and the users, but the use of UDP is not suitable for high-quality telephony as the use of UDP requires the use of large packets in order to avoid overwhelming the capabilities of the modems of the users and the regular phone lines which typically connect Internet users to their ISPs. If TCP were used for transmission between and throughout the networks 36 and 38, however, that approach would also be unsuitable for high-quality digital telephony. Latency would again be significant, because a lost packet anywhere in the network would require the lost packet to be detected and resent. Resending a lost packet very quickly becomes superfluous in an application such as telephony or voice communication.
- TCP is defined at the transport layer and is responsible for reliable, connection-oriented, end-to-end error detection and correction data delivery services.
- TCP data units are segments and these segments are encapsulated within an IP header.
- TCP is a stream-oriented protocol that provides the application layer with the illusion that a continuous data pipeline is established along which application information is transmitted.
- the major features of TCP are reliable, connection-oriented, full duplex, urgent, stream data transfers and flow control.
- TCP reliability is provided through data segment sequence numbers, data receipt acknowledgments, retransmission timers, and segment checksums.
- Another important feature of TCP is that the header of a TCP packet can be compressed using van Jacobsen compression. The availability of van Jacobsen compression allows TCP protocol packets to have a low overhead.
- a network 40 in accordance with the present invention is illustrated in Fig. 2. While network 40 is shown as serving a first user A 42 having a client computer and a second user B 44 having a remote computer, it will be recognized that a large plurality of users may be readily served.
- User A 42 communicates with a first node 46 using TCP.
- the client computer will include a modem 43 which will typically be connected to the first node 46 by regular telephone lines 45.
- First node 46 passes each data packet received from user A to a first TCP/UDP converter 48, where the data packet is converted to a UDP packet. The UDP packet is then sent to a second node 50.
- the connection of the first and second nodes 46 and 50, respectively is typically by way of a high bandwidth connection 49.
- the UDP packet received from user A is passed to a second TCP/UDP converter 52 where it is converted to a TCP packet.
- the TCP packet is then transmitted to the user B 44 again typically using regular phone lines 51 and a modem 47 located in the client computer.
- Each of the converters 48 and converter 52 preferably operates in a two-way fashion, converting TCP to UDP or UDP to TCP as required.
- the network 40 illustrated in Fig. 2 is suitable for two-way transmission of data between user B 44 and user A 42 making it advantageous for applications such as Internet telephony as discussed in greater detail below.
- Fig. 3 shows a more detailed illustration of the protocol converter 48 of Fig. 2.
- the two-way protocol converter 48 includes a TCP/UDP protocol converter 62 and a UDP/TCP protocol converter 64.
- the TCP/UDP protocol converter 62 includes an incoming TCP network manager 66, a TCP to UDP protocol header converter 68, and an outgoing UDP network manager 70.
- the outgoing UDP network manager 70 includes a calling database 72 which stores routing information for each client. This client routing information is preferably established at the time the client connects to the network. The generation and function of the calling destination database 72 will be described in greater detail below in conjunction with the discussion of Figs. 4 and 5.
- the UDP/TCP protocol converter 64 includes an incoming UDP network manager 74, a UDP to TCP protocol header converter 76, and an outgoing TCP network manager 78.
- the calling destination database 80 contains entries established for each client which are preferably established at the time of connection of the client with the network. The calling destination database 80 is described in greater detail below in conjunction with Figs. 4 and 5.
- the UDP/TCP protocol converter 62 receives data packets in TCP format.
- UDP/TCP protocol converter 62 is shown as part of a digital packet telephony network linking client computers A and B, C and D, and E and F, respectively.
- Client computers A, C, and E each transmit a stream of digital packets to the protocol converter 48 using TCP format.
- Each packet transmitted by the client computers A, C, and E contains header information in TCP format.
- Incoming TCP network manager 66 receives the stream of data packets from the client computers A, C, and E and passes them to TCP/UDP protocol header converter 68.
- the TCP/UDP protocol header converter 68 removes the TCP header information from the packets, translates the TCP header information to UDP header information, and adds the UDP header information to the packets. TCP/UDP protocol header converter 68 then passes the data packets to outgoing UDP network manager 70, which reads the packet headers, looks up the destination information in calling database 72, and directs the packets to their destinations. Packets from client computer A are then routed to remote computer B, packets from client computer C to remote computer D, and packets from client computer E to remote computer F. Typically, packets will not be transmitted directly from converter 62 to a receiving remote computer, but instead will be preferably routed through another network, or another converter according to the present invention. For example, in Fig. 2 packets addressed from client computer A to remote computer B are sent from protocol converter 48 to remote network 50 and thence to protocol converter 52 before being routed to the remote computer B.
- the UDP/TCP protocol converter 64 operates in a similar manner, receiving, as an illustrative example, packets from the remote computers B, D, and F to be transmitted to the client computers A, C, and E.
- Each packet received by protocol converter 64 from the remote computers B, D, and F contains header information in UDP format, a portion of the header information identifying the packet destination. This is because remote computers B, D and F originally transmitted the packets in UDP format, or because the packets were converted to UDP format enroute to protocol converter 64.
- the packets arrive at the incoming UDP network manager 74, where they are passed along to UDP/TCP protocol header converter 76.
- the UDP/TCP protocol header converter 76 removes the UDP headers from the packets, translates the headers into TCP format, and reconstructs the packets as TCP packets.
- the TCP packets are then routed to the outgoing TCP network manager 78.
- Outgoing TCP network manager 78 determines the destination by looking it up in the calling destination database 80. Each packet is then sent to its appropriate destination.
- the remote computers B, D, and F can be either end users or further networks or converters.
- the protocol converter of the present invention has great flexibility.
- One network employing a protocol converter according to the present invention can be used to transmit data to arrive at another similar network, thus providing all the advantages described above, or, if the destination does not belong to such a network, the data packets can nevertheless be transmitted to any standard TCP/IP networ ..
- This feature provides the significant advantage of allowing the ability to communicate with users who do not subscribe to networks employing a protocol converter according to the present invention. This feature is illustrated in greater detail in Fig. 4 below.
- Fig. 4 illustrates communication with a large Internet Service Provider A ("ISP A ”) 82 using a protocol converter according to the present invention.
- the illustrated communication occurs both between its own clients and between its own clients and those of an Internet Service Provider B (“ISP B ”) 108 which does not use a protocol converter according to the present invention.
- ISP A Internet Service Provider A
- ISP B Internet Service Provider B
- ISP A 82 has multiple Points of Presence ("POP") of which POP ! 84 and POP 2 86 are shown as representative examples.
- POP Points of Presence
- a POP is a server system or network which typically provides access to ISP A to users within a local telephone service area.
- POPi 84 and POP 2 86 typically serves clients within a local calling area.
- POPi 84 and POP 2 86 typically communicate with one another through ISP A packet network 88.
- Each of P0P x 84 and POP 2 86 communicates with networks and computers outside of ISP A 82 through a connection to Internet 90.
- Each POP serves a large number of clients, of which client j 92 and client 2 94 are shown as representative examples.
- Clien ⁇ 92 connects to POP ⁇ 84 through a modem 96.
- Modem 96 provides access via the Plain Old Telephone System (POTS) 98.
- POTS Plain Old Telephone System
- Client 2 94 connects to POPj 84 through one of a number of alternative connections 100.
- Such connections may include cable, LAN/WAN connections, 800 numbers, ISDN, wireless, or any other suitable presently known connections or connections which may be developed in the future.
- POP ⁇ 84 includes a modem pool 102 to accommodate clients such as the clientj 92, who connect to POPj 84 through modems such as the modem 96.
- POP : 84 also includes a variety of other edge terminators 104, which accommodate clients such as the client 2 94, who connect through alternative means. Each of the clients, clienti 92 and client 2 94, connects to the POP j 84 using the TCP protocol.
- POPi 84 also includes a router 103. Router 103 includes a converter 105, one suitable example of which is the converter 62 described above.
- POPj 84 also includes an active user registry server 106, which is described in further detail below in connection with the discussion of Fig. 5.
- the active user registry server 106 provides dynamic addressing. In other words, it establishes and stores a virtual address for each user at the time the user first establishes a session with POP : 84. Active user registry server 106 associates with each user a converter address. These converter addresses associated with each client such as the clients 92 and 94 are stored, and are used to provide necessary addressing information.
- the converter 105 receives TCP packets from each of the clients 92 and 94 and converts these packets to UDP packets.
- POP : 84 then transmits these UDP packets to their destinations. For example, POP j 84 transmits some of the packets to other points of presence within ISP A 82 over ISP A packet network 88.
- POP 2 86 When POP 2 86, to take a representative example, receives a packet whose destination is one of its users, for example client la 92a, it sends the packet to a router 103a where the packet is converted by converter 105a from UDP to TCP, finds the user to which the packet is addressed in its calling destination database, and transmits the packet to the client la 92a, who is connected to P0P 2 86 via modem 96a.
- a packet's destination may be to client lb via ISP B 108.
- POPi 84 would transmit the packet over the Internet 90, where it would be routed to ISP B 108.
- the packet would remain in UDP protocol while ISP B 108 routed it to client lb 110 via modem 111.
- Protocol converters in accordance with the teachings of the present invention maintain compatibility with users who are clients of systems that do not employ a protocol converter according to the present invention.
- a packet routed to client lb 110 remains in UDP protocol.
- While communication between client 92 and client lb 110 does not have all of the advantages of a protocol converter according to the present invention, the use of a protocol converter according to the present invention does not interfere in any way with communication between clientj 92 and client lb 110. This feature provides backwards compatibility with existing systems, and thus promotes the universal applicability of the present invention.
- Fig. 5 is a more detailed illustration of the active user registry server 106 shown in Fig. 4.
- the active user registry server 106 preferably consists of a network connection manager 112, a client lookup system 114, a register client circuit 116, and an active user database 118.
- a client such as client 92
- client x 92 or POP : 84 sends a register message to the network connection manager 112 which passes the register message to the register message input 112a of the register client circuit 116.
- the register message preferably contains a converter IP address, a client IP address, and a unique identifier for client 92. This information is associated with client j 92 and stored in the active user database 118.
- a client When a client, such as client la 92a, wants to determine how to route a communication to clientj 92, it sends a message to the active user registry server 106.
- the network communications manager 112 determines that the message is a client look up request message, and sends it to the client lookup system 114.
- the system 114 does the look up for clientj 92 in the active user database 118 and sends the necessary routing information to the requesting client.
- the requesting client now has all the routing information required to send packets to the client 1 92.
- Fig. 6 is a flowchart illustrating process steps which may be suitably carried out by a protocol converter according to the teachings of the present invention.
- step 600 an incoming message is detected and the operating system sends a network interrupt for the incoming message.
- step 601 it is determined whether a first packet of the incoming message is in TCP format. If the packet is a TCP packet, the control process follows the branch including the steps 602, 604, 606 and 607. The packet is received, step 602, the address of the client addressee is looked up, step 604, the TCP packet is converted to UDP, step 606, and routed to the remote addressee, step 607.
- step 608 If in step 601, it had been determined that a TCP packet was not incoming, it would next be determined in step 608 if a UDP packet was incoming. If a UDP packet was identified, process control would follow the control process branch including steps 610-616. In step 610, the UDP packet is received, and in step 612, the client address of the addressee is looked up. In step 614, the packet is converted to TCP. In step 616, the packet is routed to the addressee. Control is then transferred back to block 600. It will be recognized that the process may be suitably extended to other packet formats by determining whether such packet formats are being received and following similar process steps.
Abstract
A digital data packet transmission process and system provides more efficient and higher quality of service in applications such as Internet telephony. In one aspect of this approach, transmission control protocol ('TCP') is used to send data from a first user or client over standard telephone lines to a local Internet service provider ('ISP'). At the ISP, the data packets are converted from TCP to user datagram protocol ('UDP'). The UDP packets are then transmitted, typically over a higher bandwidth link to another local ISP serving the recipient. The UDP packets are translated back to TCP packets and routed to the receiver. Because many existing systems currently employ UDP packets, the present approach is largely backwards compatible should a recipient be hooked up to an ISP that does not employ a TCP/UDP converter. A bidirectional TCP/UDP converter is preferable for two way communication such as Internet telephony.
Description
Methods and Apparatus for Providing Improved Quality of Packet Transmission in Applications Such
As Internet Telephony
FIELD OF THE INVENTION
The present invention relates to communication protocols in digital networks. More particularly, the invention relates to methods and apparatus for protocol conversion in order to minimize latency and to improve efficiency and quality of packet transmission in applications including Internet telephony.
BACKGROUND OF THE INVENTION
More and more information is being shared and transmitted over computer networks, and more and more two-way communication is taking place using computer networks. With the growth and ubiquity of the Internet, more and more people are becoming familiar with computer networks and desire to conduct more and more of their daily affairs using computer networks, especially the Internet. With the increasing popularity of the Internet and other networks, there is a growing demand for increased speed and quality of service. The higher the quality of a particular product or service that can be provided over the Internet, the greater will be the demand for that product or service.
Smaller and more uniform computer networks can provide high- quality services without excessive difficulty, since greater control can be maintained over the network servers and clients. In such an environment, strict standards and protocols can be dictated and maintained. The Internet, on the other hand, must serve a tremendous variety of users, all over the world, and must provide means for transferring data over paths which may be extremely circuitous, with components having differing characteristics and bandwidths. One application which is stimulating considerable interest and which is growing rapidly in popularity, but which is still subject to significant obstacles, is Internet telephony or in other words, real-time voice communication over the Internet. This application has the promise of introducing the Internet into the daily lives of large numbers of people in a substantial way. The
promise is of providing a low-cost substitute for a long distance telephone service with which people are familiar, and which they use frequently, but which, because of its cost, they are constrained to use much less frequently than they might otherwise choose to if the costs were significantly lowered while still providing comparable service. Internet telephony holds forth the promise of allowing people to communicate with friends and loved ones all over the world for the cost of an making an Internet connection. In the present state of the art, there remain, however, significant obstacles to high-quality Internet telephony. These obstacles arise in part because of the protocols used by the Internet for data transmission. For real time voice traffic, latency must be kept to a minimum or the delays incurred will significantly interfere with the quality of the voice conversation. For limited-bandwidth transmission channels such as modems, transmission control protocol ("TCP"), through the use of Van Jacobsen compression, can accommodate small packets without the excessive overhead caused by a large header size. Such compression algorithms do not presently exist for user datagram protocol ("UDP") .
If small packets are used for UDP transmission, the available bandwidth provided by today ' s modems may not be enough to accommodate them, given their large overhead. However, if large UDP packets are used for telephony, voice quality is degraded because a significant latency results. Such latency may arise because a wait is necessary to allow a large UDP packet to fill with data before it is dispatched.
On the other hand, if TCP is used to provide transmission all the way from the initial sender, over the Internet, and to the remote receiver, latencies may be too great for telephony because of the delays occasioned by detecting and resending lost packets. When measured against the quality of standard telephone service, an acceptable quality of Internet telephony service is not yet available. Thus, there exists a need in the art for methods and apparatus to provide Internet telephony data packet transmission
which can accommodate a low-bandwidth connection between a user and a local host, but which can provide high-quality data transmission with low latency.
SUMMARY OF THE INVENTION
The present invention provides methods and apparatus for protocol conversion between transmission control protocol ("TCP") and user datagram protocol ("UDP") . In one aspect of the present invention, TCP is used between the user and the local host. TCP is suitable for use in a modem link between a local user and an Internet Service Provider ("ISP"), because the modem itself provides a reliable connection, detecting and resending lost data. Thus, the latencies caused by TCP's detecting and retransmitting lost packets are unlikely to occur. This provides a reliable, connection-oriented transmission which can transmit small packets within the bandwidth provided by a typical modem and consistent with local telephone connections such as those provided by twisted wire pairs and standard telephone wires connecting most people to the phone network. The latency caused by TCP's detection and resending of lost packets is tolerable, because very few packets are lost at the connection between the user and the local host.
After each packet arrives at the local host, it is converted to UDP format and transmitted over the Internet. While the UDP packets have a big header and thus a high overhead with respect to the amount of data per packet, the local host is able to transmit such packets using UDP with low latency, because the bandwidth between the local host networks is great enough to tolerate the overhead caused by the large header size of the UDP packets. When the packet arrives at the destination node of the local host network, it is reconverted to TCP, and thence transmitted to the user of the destination node. This conversion allows for the transmission of low latency small packets. By tailoring the protocols used to take advantage of the characteristics of the different connections, significant improvements in efficiency and quality of service may be achieved.
A more complete understanding of the present invention, as
well as further features and advantages of the invention, will be apparent from the following Detailed Description and the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is an illustration of a packet transmission network of the prior art, showing connection protocols typically employed for packet transmission between users and hosts, between hosts within a single host network, and between networks;
Fig. 2 is a packet transmission network employing a protocol conversion system according to the present invention, illustrating the protocols employed between the various nodes of the network;
Fig. 3 is a more detailed illustration of a protocol conversion system according to the present invention;
Fig. 4 is a detailed block diagram showing the use of a protocol conversion system according to the present invention, in which an active user registry server is employed in an Internet Service Provider which connects to clients using differing connection methods and which also transmits data to and from other Internet Service Providers which do not use a protocol conversion system according to the present invention;
Fig. 5 is a diagram showing in greater detail the active user registry server shown in Fig. 4; and
Fig. 6 is a flowchart illustrating a protocol conversion process in accordance with the present invention.
DETAILED DESCRIPTION
Fig. 1 illustrates a representative link 10 of the prior art between two data packet networks 36 and 38. First network 36 serves users^, 14, 16 and 18, respectively, and second network 38 serves users4.6, 30, 32 and 34. Users^ communicate with a first local server in a first host node 22 using UDP. First host node 22 communicates with a first network communication node 24 using UDP. First network communication node 24 and a second network communication node 26 also communicate with one another using UDP. The second network communication node 26 communicates with a second
host node 28 using UDP. Host node 28 communicates with users4.6, 30, 32 and 34 using UDP.
UDP is defined at the transport layer and provides the application layer with a fast but unreliable, connectionless delivery system. UDP data units are datagrams. A datagram is encapsulated within an IP header. The header portions of UDP packets are long. Thus, the overhead for UDP packets is inherently quite large. This problem is typically overcome by making UDP packets large. With sufficiently large UDP packets, the header represents a relatively small portion of the total packet. If used to transmit small packets, however, as would be needed for high- quality Internet telephony, the large headers used by UDP would represent a large proportion of the packet size. For a typical modem connection operating at 28.8 kB, the use of small UDP packets for Internet telephony would typically overwhelm the bandwidth which could be provided by the modem. The use of small packets is best to keep down delays for quality critical applications such as Internet telephony.
The use of UDP throughout the first and second networks 36 and 38 provides a fast, connectionless data transfer system between the networks and the users, but the use of UDP is not suitable for high-quality telephony as the use of UDP requires the use of large packets in order to avoid overwhelming the capabilities of the modems of the users and the regular phone lines which typically connect Internet users to their ISPs. If TCP were used for transmission between and throughout the networks 36 and 38, however, that approach would also be unsuitable for high-quality digital telephony. Latency would again be significant, because a lost packet anywhere in the network would require the lost packet to be detected and resent. Resending a lost packet very quickly becomes superfluous in an application such as telephony or voice communication. The speaking transmitted by telephony occurs in real time. The global use of TCP would produce a significant latency in order to resend data which would be out of date and useless by the time it was resent and ultimately received.
TCP is defined at the transport layer and is responsible for reliable, connection-oriented, end-to-end error detection and correction data delivery services. TCP data units are segments and these segments are encapsulated within an IP header. TCP is a stream-oriented protocol that provides the application layer with the illusion that a continuous data pipeline is established along which application information is transmitted. The major features of TCP are reliable, connection-oriented, full duplex, urgent, stream data transfers and flow control. TCP reliability is provided through data segment sequence numbers, data receipt acknowledgments, retransmission timers, and segment checksums. Another important feature of TCP is that the header of a TCP packet can be compressed using van Jacobsen compression. The availability of van Jacobsen compression allows TCP protocol packets to have a low overhead.
The problems of latency and limited bandwidth are substantially addressed by the present invention. A network 40 in accordance with the present invention is illustrated in Fig. 2. While network 40 is shown as serving a first userA 42 having a client computer and a second userB 44 having a remote computer, it will be recognized that a large plurality of users may be readily served. UserA 42 communicates with a first node 46 using TCP. Typically, the client computer will include a modem 43 which will typically be connected to the first node 46 by regular telephone lines 45. First node 46 passes each data packet received from userA to a first TCP/UDP converter 48, where the data packet is converted to a UDP packet. The UDP packet is then sent to a second node 50. The connection of the first and second nodes 46 and 50, respectively is typically by way of a high bandwidth connection 49.
Upon arrival at the second node 50, the UDP packet received from userA is passed to a second TCP/UDP converter 52 where it is converted to a TCP packet. The TCP packet is then transmitted to the userB 44 again typically using regular phone lines 51 and a modem 47 located in the client computer. Each of the converters 48 and converter 52 preferably operates in a two-way fashion,
converting TCP to UDP or UDP to TCP as required. Thus, the network 40 illustrated in Fig. 2 is suitable for two-way transmission of data between userB 44 and userA 42 making it advantageous for applications such as Internet telephony as discussed in greater detail below.
Fig. 3 shows a more detailed illustration of the protocol converter 48 of Fig. 2. The two-way protocol converter 48 includes a TCP/UDP protocol converter 62 and a UDP/TCP protocol converter 64. The TCP/UDP protocol converter 62 includes an incoming TCP network manager 66, a TCP to UDP protocol header converter 68, and an outgoing UDP network manager 70. The outgoing UDP network manager 70 includes a calling database 72 which stores routing information for each client. This client routing information is preferably established at the time the client connects to the network. The generation and function of the calling destination database 72 will be described in greater detail below in conjunction with the discussion of Figs. 4 and 5.
The UDP/TCP protocol converter 64 includes an incoming UDP network manager 74, a UDP to TCP protocol header converter 76, and an outgoing TCP network manager 78. The calling destination database 80 contains entries established for each client which are preferably established at the time of connection of the client with the network. The calling destination database 80 is described in greater detail below in conjunction with Figs. 4 and 5.
The UDP/TCP protocol converter 62 receives data packets in TCP format. For example, UDP/TCP protocol converter 62 is shown as part of a digital packet telephony network linking client computers A and B, C and D, and E and F, respectively. Client computers A, C, and E each transmit a stream of digital packets to the protocol converter 48 using TCP format. Each packet transmitted by the client computers A, C, and E contains header information in TCP format. Incoming TCP network manager 66 receives the stream of data packets from the client computers A, C, and E and passes them to TCP/UDP protocol header converter 68. The TCP/UDP protocol header converter 68 removes the TCP header information from the
packets, translates the TCP header information to UDP header information, and adds the UDP header information to the packets. TCP/UDP protocol header converter 68 then passes the data packets to outgoing UDP network manager 70, which reads the packet headers, looks up the destination information in calling database 72, and directs the packets to their destinations. Packets from client computer A are then routed to remote computer B, packets from client computer C to remote computer D, and packets from client computer E to remote computer F. Typically, packets will not be transmitted directly from converter 62 to a receiving remote computer, but instead will be preferably routed through another network, or another converter according to the present invention. For example, in Fig. 2 packets addressed from client computer A to remote computer B are sent from protocol converter 48 to remote network 50 and thence to protocol converter 52 before being routed to the remote computer B.
The UDP/TCP protocol converter 64 operates in a similar manner, receiving, as an illustrative example, packets from the remote computers B, D, and F to be transmitted to the client computers A, C, and E. Each packet received by protocol converter 64 from the remote computers B, D, and F contains header information in UDP format, a portion of the header information identifying the packet destination. This is because remote computers B, D and F originally transmitted the packets in UDP format, or because the packets were converted to UDP format enroute to protocol converter 64. The packets arrive at the incoming UDP network manager 74, where they are passed along to UDP/TCP protocol header converter 76. The UDP/TCP protocol header converter 76 removes the UDP headers from the packets, translates the headers into TCP format, and reconstructs the packets as TCP packets. The TCP packets are then routed to the outgoing TCP network manager 78. Outgoing TCP network manager 78 determines the destination by looking it up in the calling destination database 80. Each packet is then sent to its appropriate destination.
The remote computers B, D, and F can be either end users or further networks or converters. Thus, the protocol converter of the present invention has great flexibility. One network employing a protocol converter according to the present invention can be used to transmit data to arrive at another similar network, thus providing all the advantages described above, or, if the destination does not belong to such a network, the data packets can nevertheless be transmitted to any standard TCP/IP networ .. This feature provides the significant advantage of allowing the ability to communicate with users who do not subscribe to networks employing a protocol converter according to the present invention. This feature is illustrated in greater detail in Fig. 4 below.
Fig. 4 illustrates communication with a large Internet Service Provider A ("ISPA") 82 using a protocol converter according to the present invention. The illustrated communication occurs both between its own clients and between its own clients and those of an Internet Service Provider B ("ISPB") 108 which does not use a protocol converter according to the present invention.
ISPA 82 has multiple Points of Presence ("POP") of which POP! 84 and POP2 86 are shown as representative examples. A POP is a server system or network which typically provides access to ISPA to users within a local telephone service area. Each of POPi 84 and POP2 86 typically serves clients within a local calling area. POPi 84 and POP2 86 typically communicate with one another through ISPA packet network 88. Each of P0Px 84 and POP2 86 communicates with networks and computers outside of ISPA 82 through a connection to Internet 90.
Each POP serves a large number of clients, of which clientj 92 and client2 94 are shown as representative examples. Clien^ 92 connects to POPα 84 through a modem 96. Modem 96 provides access via the Plain Old Telephone System (POTS) 98. Client2 94 connects to POPj 84 through one of a number of alternative connections 100. Such connections may include cable, LAN/WAN connections, 800 numbers, ISDN, wireless, or any other suitable presently known connections or connections which may be developed in the future.
POPα 84 includes a modem pool 102 to accommodate clients such as the clientj 92, who connect to POPj 84 through modems such as the modem 96. POP: 84 also includes a variety of other edge terminators 104, which accommodate clients such as the client2 94, who connect through alternative means. Each of the clients, clienti 92 and client2 94, connects to the POPj 84 using the TCP protocol. POPi 84 also includes a router 103. Router 103 includes a converter 105, one suitable example of which is the converter 62 described above. POPj 84 also includes an active user registry server 106, which is described in further detail below in connection with the discussion of Fig. 5. The active user registry server 106 provides dynamic addressing. In other words, it establishes and stores a virtual address for each user at the time the user first establishes a session with POP: 84. Active user registry server 106 associates with each user a converter address. These converter addresses associated with each client such as the clients 92 and 94 are stored, and are used to provide necessary addressing information.
The converter 105 receives TCP packets from each of the clients 92 and 94 and converts these packets to UDP packets. POP: 84 then transmits these UDP packets to their destinations. For example, POPj 84 transmits some of the packets to other points of presence within ISPA 82 over ISPA packet network 88. When POP2 86, to take a representative example, receives a packet whose destination is one of its users, for example clientla 92a, it sends the packet to a router 103a where the packet is converted by converter 105a from UDP to TCP, finds the user to which the packet is addressed in its calling destination database, and transmits the packet to the clientla 92a, who is connected to P0P2 86 via modem 96a.
To take another example, a packet's destination may be to clientlb via ISPB 108. In this case, POPi 84 would transmit the packet over the Internet 90, where it would be routed to ISPB 108. The packet would remain in UDP protocol while ISPB 108 routed it to clientlb 110 via modem 111.
Protocol converters in accordance with the teachings of the present invention maintain compatibility with users who are clients of systems that do not employ a protocol converter according to the present invention. A packet routed to clientlb 110 remains in UDP protocol. While communication between client 92 and clientlb 110 does not have all of the advantages of a protocol converter according to the present invention, the use of a protocol converter according to the present invention does not interfere in any way with communication between clientj 92 and clientlb 110. This feature provides backwards compatibility with existing systems, and thus promotes the universal applicability of the present invention.
Fig. 5 is a more detailed illustration of the active user registry server 106 shown in Fig. 4. The active user registry server 106 preferably consists of a network connection manager 112, a client lookup system 114, a register client circuit 116, and an active user database 118. When a client, such as client 92, first connects to a POP such as POPj 84, clientx 92 or POP: 84 sends a register message to the network connection manager 112 which passes the register message to the register message input 112a of the register client circuit 116. The register message preferably contains a converter IP address, a client IP address, and a unique identifier for client 92. This information is associated with clientj 92 and stored in the active user database 118. When a client, such as clientla 92a, wants to determine how to route a communication to clientj 92, it sends a message to the active user registry server 106. The network communications manager 112 determines that the message is a client look up request message, and sends it to the client lookup system 114. The system 114 does the look up for clientj 92 in the active user database 118 and sends the necessary routing information to the requesting client. The requesting client now has all the routing information required to send packets to the client1 92.
Fig. 6 is a flowchart illustrating process steps which may be suitably carried out by a protocol converter according to the teachings of the present invention. In step 600, an incoming
message is detected and the operating system sends a network interrupt for the incoming message. In step 601, it is determined whether a first packet of the incoming message is in TCP format. If the packet is a TCP packet, the control process follows the branch including the steps 602, 604, 606 and 607. The packet is received, step 602, the address of the client addressee is looked up, step 604, the TCP packet is converted to UDP, step 606, and routed to the remote addressee, step 607. It will be recognized that the order of converting and lookup are not critical, and that these steps may be performed in reverse order or in parallel. If additional TCP packets are received as part of the same incoming message, the process continues to repeat itself. If no additional packets are being received by the system, the process will idle until the next network interrupt indicative of an incoming message occurs.
If in step 601, it had been determined that a TCP packet was not incoming, it would next be determined in step 608 if a UDP packet was incoming. If a UDP packet was identified, process control would follow the control process branch including steps 610-616. In step 610, the UDP packet is received, and in step 612, the client address of the addressee is looked up. In step 614, the packet is converted to TCP. In step 616, the packet is routed to the addressee. Control is then transferred back to block 600. It will be recognized that the process may be suitably extended to other packet formats by determining whether such packet formats are being received and following similar process steps.
While the present invention is disclosed in the context of a presently preferred embodiment, it will be recognized that a wide variety of implementations may be employed by persons of ordinary skill in the art consistent with the above discussion and the claims which follow below.
Claims
1. A method of digital data transmission in a packet- switched digital network, comprising the steps of: establishing a data link between a server and a client, said client transmitting to said server digital transmission control protocol (TCP) packets addressed to an addressee; converting each TCP packet received from said client to user datagram protocol (UDP) format; and routing each UDP-converted packet to the addressee.
2. The method of claim 1, wherein said method is used in a packet-switched Internet telephony system.
3. The method of claim 1 wherein the step of establishing a data link between a server and a client further comprises the step of utilizing a modem at the client to connect to the server which is part of a local Internet service provider (ISP) utilizing standard telephone lines.
4. The method of claim 1 further comprising the step of: looking up the addressee's address information in a calling destination database.
5. The method of claim 1 wherein the step of routing each UDP-converted packet to the addressee further comprises the step of routing each UDP-converted packet to a local service provider (ISP) serving the addressee.
6. The method of claim 5 wherein the step of routing each UDP-converted packet to a local ISP serving the addressee further comprises making a connection over a high bandwidth connection.
7. The method of claim 5 further comprising the step of routing each TCP format packet from the local ISP serving the addressee to the addressee utilizing a modem and standard telephone lines.
8. The method of claim 1 wherein the step of routing each UDP-converted packet to the addressee further comprises the step routing each UDP-converted packet through an Internet network to a local Internet service provider (ISP) serving the addressee.
9. The method of claim 8 further comprising the step of receiving each UDP-converted packet at the addressee.
10. The method of claim 1 further comprising the step of establishing a calling destination database.
11. A packet converter for use in a packet-switched communication system, comprising: a server for communicating with a plurality of clients and receiving transmission control protocol (TCP) packets from said clients; a converter for converting said plurality of packets to user datagram protocol (UDP) packets; a database for holding a lookup table associating the plurality of clients with addresses for the plurality of clients; and a router for routing each of said packets to its addressee.
12. The packet converter of claim 11 wherein said server is further operable to receive from each of a plurality of remote hosts a plurality of digital packets, each of said packets being formatted as a UDP packet, and the packet converter further comprises: a converter for converting each of said received UDP packet to TCP format; and a router for routing each of said converted packets to its addressee.
13. A packet-switched communication system comprising: a first local server for communicating with a plurality of clients and receiving transmission control protocol (TCP) packets from said clients on an input; a first converter for converting said TCP packets to user datagram protocol (UDP) packets; a router to direct the converted UDP packets to a second local server for communicating with an addressee; and a second converter for reconverting the converted UDP packets received by the second local server back to TCP packets.
14. The system of claim 13 further comprising a first client including a modem connected to a standard telephone line, said first client transmitting TCP packets representing digital data sampled from a voice of an Internet telephony user.
15. The system of claim 13 further comprising a memory for storing a calling destination database.
16. The system of claim 13 further comprising an active user registry server.
17. The system of claim 13 wherein the first converter further comprises an incoming network manager.
18. The system of claim 13 wherein the first and second local servers are part of local Internet telephony providers which are connected by a high bandwidth connection.
19. The system of claim 13 further comprising an addressee client which includes a modem for connecting the addressee client to the second local converter by way of a standard telephone line.
20. The system of claim 13 wherein the input of the first local server is connected to a standard telephony line.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/819,617 | 1997-03-17 | ||
US08/819,617 US6075796A (en) | 1997-03-17 | 1997-03-17 | Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1998042107A1 true WO1998042107A1 (en) | 1998-09-24 |
Family
ID=25228621
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1998/004091 WO1998042107A1 (en) | 1997-03-17 | 1998-03-17 | Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony |
Country Status (2)
Country | Link |
---|---|
US (3) | US6075796A (en) |
WO (1) | WO1998042107A1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19840329A1 (en) * | 1998-09-04 | 2000-03-09 | Alcatel Sa | Telecommunication system with switching device and data concentrator for access to the Internet |
WO2002011389A2 (en) * | 2000-07-28 | 2002-02-07 | Dialpad Communications, Inc. | Data exchange with computers within a secure network |
US6442169B1 (en) | 1998-11-20 | 2002-08-27 | Level 3 Communications, Inc. | System and method for bypassing data from egress facilities |
US6614781B1 (en) | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
EP1671453A2 (en) * | 2003-09-10 | 2006-06-21 | Hyperdata Technologies, Inc. | Internet protocol optimizer |
EP2027698A1 (en) * | 2006-06-14 | 2009-02-25 | Nokia Corporation | Method and device for wireless transmission of internet protocol tv |
EP2033407A2 (en) * | 2006-06-16 | 2009-03-11 | Harris Corporation | Systems and methods for a protocol transformation gateway for quality of service |
US8848894B2 (en) | 2000-05-04 | 2014-09-30 | Focal Ip, Llc | Tandem access controller within the public switched telephone network |
WO2019007582A1 (en) * | 2017-07-05 | 2019-01-10 | Siemens Aktiengesellschaft | Method and device for feedback-free unidirectional transmission of data to a remote application server |
Families Citing this family (146)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7168084B1 (en) | 1992-12-09 | 2007-01-23 | Sedna Patent Services, Llc | Method and apparatus for targeting virtual objects |
US9286294B2 (en) | 1992-12-09 | 2016-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content suggestion engine |
US20020118671A1 (en) * | 1995-11-15 | 2002-08-29 | Data Race, Inc. | Extending office telephony and network data services to a remote client through the internet |
US6266328B1 (en) * | 1996-08-26 | 2001-07-24 | Caritas Technologies, Inc. | Dial up telephone conferencing system controlled by an online computer network |
US6075796A (en) * | 1997-03-17 | 2000-06-13 | At&T | Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony |
US6546005B1 (en) * | 1997-03-25 | 2003-04-08 | At&T Corp. | Active user registry |
US6047284A (en) | 1997-05-14 | 2000-04-04 | Portal Software, Inc. | Method and apparatus for object oriented storage and retrieval of data from a relational database |
WO1999009716A1 (en) * | 1997-08-19 | 1999-02-25 | Yugen Kaisha Ls Net | Method of communicating with subscriber devices through a global communication network |
CA2225227A1 (en) * | 1997-12-18 | 1999-06-18 | Michael Coveley | Intelligent communication and applications server |
JP3464907B2 (en) * | 1998-03-20 | 2003-11-10 | 富士通株式会社 | Protocol conversion system |
GB2337893B (en) * | 1998-05-28 | 2000-09-06 | Matsushita Electric Ind Co Ltd | Internet telephone apparatus and internet telephone gateway system |
US6810409B1 (en) * | 1998-06-02 | 2004-10-26 | British Telecommunications Public Limited Company | Communications network |
US6765901B1 (en) * | 1998-06-11 | 2004-07-20 | Nvidia Corporation | TCP/IP/PPP modem |
US6584509B2 (en) * | 1998-06-23 | 2003-06-24 | Intel Corporation | Recognizing audio and video streams over PPP links in the absence of an announcement protocol |
JP3225924B2 (en) * | 1998-07-09 | 2001-11-05 | 日本電気株式会社 | Communication quality control device |
EP0975123A1 (en) * | 1998-07-15 | 2000-01-26 | Telefonaktiebolaget L M Ericsson (Publ) | Communication device and method for reliable and low-delay packet transmission |
US6512746B1 (en) * | 1998-09-11 | 2003-01-28 | Nortel Networks Limited | Method and apparatus for measuring voice grade of service in an IP network |
US6526448B1 (en) | 1998-12-22 | 2003-02-25 | At&T Corp. | Pseudo proxy server providing instant overflow capacity to computer networks |
CA2376214A1 (en) * | 1999-06-08 | 2000-12-14 | The Trustees Of Columbia University In The City Of New York | Network telephony appliance and system for inter/intranet telephony |
US6512764B1 (en) * | 1999-07-16 | 2003-01-28 | General Bandwidth Inc. | Method and apparatus for providing voice signals to and from a telecommunications switch |
US6356529B1 (en) * | 1999-08-12 | 2002-03-12 | Converse, Ltd. | System and method for rapid wireless application protocol translation |
US7353208B1 (en) * | 2000-02-02 | 2008-04-01 | Transaction Network Services, Inc. | Transaction processing using intermediate server architecture |
MXPA02005228A (en) * | 1999-11-23 | 2003-09-25 | U S Wireless Data Inc | Transaction processing using intermediate server architecture. |
DE19957301A1 (en) * | 1999-11-29 | 2001-06-07 | Siemens Ag | Multiplex procedure for Gigabit Ethernet signals in the synchronous digital hierarchy |
US6625648B1 (en) * | 2000-01-07 | 2003-09-23 | Netiq Corporation | Methods, systems and computer program products for network performance testing through active endpoint pair based testing and passive application monitoring |
US7343413B2 (en) | 2000-03-21 | 2008-03-11 | F5 Networks, Inc. | Method and system for optimizing a network by independently scaling control segments and data flow |
US8380854B2 (en) | 2000-03-21 | 2013-02-19 | F5 Networks, Inc. | Simplified method for processing multiple connections from the same client |
AU2001271707A1 (en) | 2000-06-29 | 2002-01-14 | Ching-Yi Lin | Phone appliance with display screen and methods of using the same |
EP1314305B1 (en) * | 2000-08-11 | 2018-10-03 | The Trustees of Columbia University in the City of New York | System and method for unified messaging in inter/intranet telephony |
US6839342B1 (en) | 2000-10-09 | 2005-01-04 | General Bandwidth Inc. | System and method for interfacing signaling information and voice traffic |
US7675900B1 (en) | 2000-10-09 | 2010-03-09 | Genband Inc. | System and method for interfacing between signaling protocols |
US7184427B1 (en) * | 2000-11-28 | 2007-02-27 | Genband Inc. | System and method for communicating telecommunication information from a broadband network to a telecommunication network |
US7385963B1 (en) | 2000-11-28 | 2008-06-10 | Genband Inc. | System and method for communicating telecommunication information from a telecommunication network to a broadband network |
KR100451721B1 (en) * | 2000-12-30 | 2004-10-08 | 엘지전자 주식회사 | Method for Matching Inter-processor Communication in Mobile Communication System |
US7024479B2 (en) * | 2001-01-22 | 2006-04-04 | Intel Corporation | Filtering calls in system area networks |
US7266091B2 (en) * | 2001-02-28 | 2007-09-04 | The Trustees Of Columbia University In City Of New York | System and method for conferencing in inter/intranet telephony |
US20020186683A1 (en) * | 2001-04-02 | 2002-12-12 | Alan Buck | Firewall gateway for voice over internet telephony communications |
US20040004966A1 (en) * | 2001-04-27 | 2004-01-08 | Foster Michael S. | Using virtual identifiers to route transmitted data through a network |
US6879667B1 (en) | 2001-05-07 | 2005-04-12 | General Bandwidth Inc. | System and method for interfacing telephony voice signals with a broadband access network |
US7039034B2 (en) * | 2001-05-18 | 2006-05-02 | Network Resonance, Inc. | System, method and computer program product for providing an IP datalink multiplexer |
US7451110B2 (en) * | 2001-05-18 | 2008-11-11 | Network Resonance, Inc. | System, method and computer program product for providing an efficient trading market |
US7936693B2 (en) * | 2001-05-18 | 2011-05-03 | Network Resonance, Inc. | System, method and computer program product for providing an IP datalink multiplexer |
US7464154B2 (en) * | 2001-05-18 | 2008-12-09 | Network Resonance, Inc. | System, method and computer program product for analyzing data from network-based structured message stream |
US7124299B2 (en) * | 2001-05-18 | 2006-10-17 | Claymore Systems, Inc. | System, method and computer program product for auditing XML messages in a network-based message stream |
WO2002102031A2 (en) * | 2001-06-12 | 2002-12-19 | The Trustees Of Columbia University In The City Of New York | System and method for call routing in an ip telephony network |
US6912231B2 (en) * | 2001-07-26 | 2005-06-28 | Northrop Grumman Corporation | Multi-broadcast bandwidth control system |
US7793326B2 (en) | 2001-08-03 | 2010-09-07 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator |
US7908628B2 (en) | 2001-08-03 | 2011-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content coding and formatting |
US7170854B1 (en) | 2001-10-02 | 2007-01-30 | Genband Inc. | System and method using switch fabric to support redundant network ports |
US6970909B2 (en) * | 2001-10-11 | 2005-11-29 | The Trustees Of Columbia University In The City Of New York | Multi-protocol data communication system supporting wireless telephony and content delivery |
DE10200165A1 (en) * | 2002-01-04 | 2003-07-10 | Klaus Rock | Method for reducing the latency in interactive data communication via a satellite network |
DE60212061T2 (en) * | 2002-02-12 | 2006-12-28 | Alcatel | Telecommunication / access system with the ability to work with different address lengths |
MXPA04008028A (en) * | 2002-02-18 | 2004-11-26 | Gemplus Card Int | Device and method for intermediation between service providers and their users. |
US7769997B2 (en) * | 2002-02-25 | 2010-08-03 | Network Resonance, Inc. | System, method and computer program product for guaranteeing electronic transactions |
US6874089B2 (en) * | 2002-02-25 | 2005-03-29 | Network Resonance, Inc. | System, method and computer program product for guaranteeing electronic transactions |
US8099393B2 (en) | 2002-03-22 | 2012-01-17 | Oracle International Corporation | Transaction in memory object store |
US7979528B2 (en) * | 2002-03-27 | 2011-07-12 | Radvision Ltd. | System and method for traversing firewalls, NATs, and proxies with rich media communications and other application protocols |
US6957062B2 (en) * | 2002-05-09 | 2005-10-18 | Casabyte, Inc. | Method, apparatus and article to remotely associate wireless communications devices with subscriber identities and/or proxy wireless communications devices |
JP3734774B2 (en) * | 2002-06-21 | 2006-01-11 | 株式会社リコー | Network facsimile apparatus and facsimile communication method |
EP1376933A1 (en) * | 2002-06-25 | 2004-01-02 | Siemens Aktiengesellschaft | Process and apparatus for reliable remote testing |
US7243150B2 (en) * | 2002-07-10 | 2007-07-10 | Radwin Ltd. | Reducing the access delay for transmitting processed data over transmission data |
US20040015609A1 (en) * | 2002-07-18 | 2004-01-22 | International Business Machines Corporation | Method and system for conversion of message formats in a pervasive embedded network environment |
AU2002951013A0 (en) * | 2002-08-27 | 2002-09-12 | Sunbay Software Ag | System for improved network data access |
WO2004077741A1 (en) * | 2003-02-06 | 2004-09-10 | Matsushita Electric Industrial Co., Ltd. | Information transmission system, information transmission method, electric device communication device, information communication device, communication control program |
US20040156389A1 (en) * | 2003-02-11 | 2004-08-12 | Lucent Technologies Inc. | Cross-layer communication solution(s) across different communication protocols |
KR100533669B1 (en) * | 2003-05-03 | 2005-12-05 | 삼성전자주식회사 | Apparatus for improving efficiency of data packet transmission in a mobile ad hoc network and method thereof |
DE50301192D1 (en) * | 2003-05-27 | 2005-10-20 | Siemens Ag | A method for packet-oriented transmission of data in telecommunication networks by means of conversion in an intermediate node from a connectionless to a connection-oriented transmission protocol and vice versa |
EP1654834A4 (en) * | 2003-08-14 | 2012-07-04 | Seiko Epson Corp | Apparatus, system and method of transmitting data |
US20050100023A1 (en) * | 2003-11-07 | 2005-05-12 | Buckwalter Paul B. | Isochronous audio network software interface |
US7978716B2 (en) | 2003-11-24 | 2011-07-12 | Citrix Systems, Inc. | Systems and methods for providing a VPN solution |
EP1685416A2 (en) * | 2003-11-17 | 2006-08-02 | General Instrument Corporation | Method and apparatuses for using packet data to manage a data stream in a broadband communications system |
US7827205B2 (en) | 2004-05-27 | 2010-11-02 | International Business Machines Corporation | Bi-directional data mapping tool |
US8495305B2 (en) | 2004-06-30 | 2013-07-23 | Citrix Systems, Inc. | Method and device for performing caching of dynamically generated objects in a data communication network |
US7757074B2 (en) | 2004-06-30 | 2010-07-13 | Citrix Application Networking, Llc | System and method for establishing a virtual private network |
US8739274B2 (en) | 2004-06-30 | 2014-05-27 | Citrix Systems, Inc. | Method and device for performing integrated caching in a data communication network |
EP1771979B1 (en) | 2004-07-23 | 2011-11-23 | Citrix Systems, Inc. | A method and systems for securing remote access to private networks |
EP1771998B1 (en) * | 2004-07-23 | 2015-04-15 | Citrix Systems, Inc. | Systems and methods for optimizing communications between network nodes |
GB2417392B (en) * | 2004-08-18 | 2007-05-09 | Wecomm Ltd | Transmitting packets of data |
US7940746B2 (en) | 2004-08-24 | 2011-05-10 | Comcast Cable Holdings, Llc | Method and system for locating a voice over internet protocol (VoIP) device connected to a network |
US20060106929A1 (en) * | 2004-10-15 | 2006-05-18 | Kenoyer Michael L | Network conference communications |
KR100619960B1 (en) * | 2004-11-22 | 2006-09-08 | 엘지전자 주식회사 | Remote control apparatus and method for controlling remotely debugging tool through internet |
US8700695B2 (en) | 2004-12-30 | 2014-04-15 | Citrix Systems, Inc. | Systems and methods for providing client-side accelerated access to remote applications via TCP pooling |
US8954595B2 (en) | 2004-12-30 | 2015-02-10 | Citrix Systems, Inc. | Systems and methods for providing client-side accelerated access to remote applications via TCP buffering |
US8549149B2 (en) | 2004-12-30 | 2013-10-01 | Citrix Systems, Inc. | Systems and methods for providing client-side accelerated access to remote applications via TCP multiplexing |
US7810089B2 (en) | 2004-12-30 | 2010-10-05 | Citrix Systems, Inc. | Systems and methods for automatic installation and execution of a client-side acceleration program |
US8706877B2 (en) | 2004-12-30 | 2014-04-22 | Citrix Systems, Inc. | Systems and methods for providing client-side dynamic redirection to bypass an intermediary |
US8255456B2 (en) | 2005-12-30 | 2012-08-28 | Citrix Systems, Inc. | System and method for performing flash caching of dynamically generated objects in a data communication network |
US20060190992A1 (en) * | 2005-02-24 | 2006-08-24 | Microsoft Corporation | Facilitating Bi-directional communications between clients in heterogeneous network environments |
US20060230148A1 (en) * | 2005-04-06 | 2006-10-12 | John Forecast | TCP forwarding of client requests of high-level file and storage access protocols in a network file server system |
US8223935B2 (en) | 2005-04-30 | 2012-07-17 | Oracle International Corporation | Revenue management systems and methods |
US7313134B2 (en) * | 2005-05-12 | 2007-12-25 | Yahoo! Inc. | Proxy server for relaying VOIP messages |
IES20050376A2 (en) | 2005-06-03 | 2006-08-09 | Asavie R & D Ltd | Secure network communication system and method |
CA2613701C (en) | 2005-06-28 | 2016-04-12 | Alexander Rockel | Revenue management system and method |
AU2006275665A1 (en) | 2005-07-28 | 2007-02-08 | Oracle International Corporation | Revenue management system and method |
WO2007019387A2 (en) * | 2005-08-04 | 2007-02-15 | Transaction Network Services, Inc. | Systems and method for vending machine settlement |
US7957402B2 (en) * | 2005-08-08 | 2011-06-07 | American Megatrends, Inc. | UDP to TCP bridge |
US7716403B2 (en) * | 2005-09-30 | 2010-05-11 | Rockwell Automation Technologies, Inc. | Information technology integration with automation systems |
US8223777B2 (en) * | 2005-11-15 | 2012-07-17 | Oracle International Corporation | Gateway for achieving low latency and high availability in a real time event processing system |
US7921184B2 (en) | 2005-12-30 | 2011-04-05 | Citrix Systems, Inc. | System and method for performing flash crowd caching of dynamically generated objects in a data communication network |
US8301839B2 (en) | 2005-12-30 | 2012-10-30 | Citrix Systems, Inc. | System and method for performing granular invalidation of cached dynamically generated objects in a data communication network |
KR100871422B1 (en) * | 2006-08-30 | 2008-12-03 | 엔에이치엔(주) | Apparatus and method for providing internet-phone service |
WO2009059851A1 (en) * | 2007-11-09 | 2009-05-14 | Nokia Corporation | Method, apparatus and software for packet modification |
US8122140B2 (en) | 2009-03-27 | 2012-02-21 | Wyse Technology Inc. | Apparatus and method for accelerating streams through use of transparent proxy architecture |
US8209430B2 (en) * | 2009-03-27 | 2012-06-26 | Wyse Technology Inc. | Apparatus and method for remote communication and bandwidth adjustments |
US20110164558A1 (en) * | 2009-05-27 | 2011-07-07 | Mobidia, Inc. | Using a proxy to improve a packet based wireless network |
US20110029682A1 (en) * | 2009-07-31 | 2011-02-03 | Ribbit Corporation | Telephonic communications with intelligent protocol switching |
EP2312437A1 (en) * | 2009-09-30 | 2011-04-20 | Thomson Licensing | Detecting client software versions |
US10721269B1 (en) | 2009-11-06 | 2020-07-21 | F5 Networks, Inc. | Methods and system for returning requests with javascript for clients before passing a request to a server |
US20110249667A1 (en) * | 2010-04-13 | 2011-10-13 | Rebelvox, Llc | Apparatus and method for transmitting media using either network efficient protocol or a loss tolerant transmission protocol |
US9141625B1 (en) | 2010-06-22 | 2015-09-22 | F5 Networks, Inc. | Methods for preserving flow state during virtual machine migration and devices thereof |
US10015286B1 (en) | 2010-06-23 | 2018-07-03 | F5 Networks, Inc. | System and method for proxying HTTP single sign on across network domains |
US8347100B1 (en) | 2010-07-14 | 2013-01-01 | F5 Networks, Inc. | Methods for DNSSEC proxying and deployment amelioration and systems thereof |
US8886981B1 (en) | 2010-09-15 | 2014-11-11 | F5 Networks, Inc. | Systems and methods for idle driven scheduling |
WO2012058643A2 (en) | 2010-10-29 | 2012-05-03 | F5 Networks, Inc. | System and method for on the fly protocol conversion in obtaining policy enforcement information |
US10135831B2 (en) | 2011-01-28 | 2018-11-20 | F5 Networks, Inc. | System and method for combining an access control system with a traffic management system |
US8589996B2 (en) | 2011-03-16 | 2013-11-19 | Azuki Systems, Inc. | Method and system for federated over-the-top content delivery |
US9246819B1 (en) * | 2011-06-20 | 2016-01-26 | F5 Networks, Inc. | System and method for performing message-based load balancing |
US9270766B2 (en) | 2011-12-30 | 2016-02-23 | F5 Networks, Inc. | Methods for identifying network traffic characteristics to correlate and manage one or more subsequent flows and devices thereof |
US10230566B1 (en) | 2012-02-17 | 2019-03-12 | F5 Networks, Inc. | Methods for dynamically constructing a service principal name and devices thereof |
US9172753B1 (en) | 2012-02-20 | 2015-10-27 | F5 Networks, Inc. | Methods for optimizing HTTP header based authentication and devices thereof |
US9231879B1 (en) | 2012-02-20 | 2016-01-05 | F5 Networks, Inc. | Methods for policy-based network traffic queue management and devices thereof |
WO2013163648A2 (en) | 2012-04-27 | 2013-10-31 | F5 Networks, Inc. | Methods for optimizing service of content requests and devices thereof |
JP5935602B2 (en) * | 2012-08-30 | 2016-06-15 | 富士通株式会社 | Transfer device, transfer method, and transfer program |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
US10187317B1 (en) | 2013-11-15 | 2019-01-22 | F5 Networks, Inc. | Methods for traffic rate control and devices thereof |
US10015143B1 (en) | 2014-06-05 | 2018-07-03 | F5 Networks, Inc. | Methods for securing one or more license entitlement grants and devices thereof |
US11838851B1 (en) | 2014-07-15 | 2023-12-05 | F5, Inc. | Methods for managing L7 traffic classification and devices thereof |
US10122630B1 (en) | 2014-08-15 | 2018-11-06 | F5 Networks, Inc. | Methods for network traffic presteering and devices thereof |
US10182013B1 (en) | 2014-12-01 | 2019-01-15 | F5 Networks, Inc. | Methods for managing progressive image delivery and devices thereof |
US20160198021A1 (en) * | 2015-01-02 | 2016-07-07 | Citrix Systems, Inc. | Dynamic protocol switching |
US11895138B1 (en) | 2015-02-02 | 2024-02-06 | F5, Inc. | Methods for improving web scanner accuracy and devices thereof |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
US10505818B1 (en) | 2015-05-05 | 2019-12-10 | F5 Networks. Inc. | Methods for analyzing and load balancing based on server health and devices thereof |
US11350254B1 (en) | 2015-05-05 | 2022-05-31 | F5, Inc. | Methods for enforcing compliance policies and devices thereof |
US11757946B1 (en) | 2015-12-22 | 2023-09-12 | F5, Inc. | Methods for analyzing network traffic and enforcing network policies and devices thereof |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
US11178150B1 (en) | 2016-01-20 | 2021-11-16 | F5 Networks, Inc. | Methods for enforcing access control list based on managed application and devices thereof |
US10797888B1 (en) | 2016-01-20 | 2020-10-06 | F5 Networks, Inc. | Methods for secured SCEP enrollment for client devices and devices thereof |
US10791088B1 (en) | 2016-06-17 | 2020-09-29 | F5 Networks, Inc. | Methods for disaggregating subscribers via DHCP address translation and devices thereof |
US10505792B1 (en) | 2016-11-02 | 2019-12-10 | F5 Networks, Inc. | Methods for facilitating network traffic analytics and devices thereof |
US10812266B1 (en) | 2017-03-17 | 2020-10-20 | F5 Networks, Inc. | Methods for managing security tokens based on security violations and devices thereof |
US10972453B1 (en) | 2017-05-03 | 2021-04-06 | F5 Networks, Inc. | Methods for token refreshment based on single sign-on (SSO) for federated identity environments and devices thereof |
US11343237B1 (en) | 2017-05-12 | 2022-05-24 | F5, Inc. | Methods for managing a federated identity environment using security and access control data and devices thereof |
US11122083B1 (en) | 2017-09-08 | 2021-09-14 | F5 Networks, Inc. | Methods for managing network connections based on DNS data and network policies and devices thereof |
IT201900022185A1 (en) * | 2019-11-26 | 2021-05-26 | Mainstreaming S P A | Method for transferring large amounts of data through a telematic network in an efficient, reliable and high-speed manner |
CN112040266A (en) * | 2020-09-10 | 2020-12-04 | 紫光云(南京)数字技术有限公司 | UDP live broadcast service optimization method based on kernel forwarding |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5550984A (en) * | 1994-12-07 | 1996-08-27 | Matsushita Electric Corporation Of America | Security system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services information |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4893307A (en) * | 1988-02-29 | 1990-01-09 | International Business Machines Corporation | Method and apparatus for linking SNA terminals to an SNA host over a packet switched communications network |
US5557798A (en) * | 1989-07-27 | 1996-09-17 | Tibco, Inc. | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5553235A (en) * | 1992-10-23 | 1996-09-03 | International Business Machines Corporation | System and method for maintaining performance data in a data processing system |
US5553083B1 (en) * | 1995-01-19 | 2000-05-16 | Starburst Comm Corp | Method for quickly and reliably transmitting frames of data over communications links |
US5555224A (en) * | 1995-08-18 | 1996-09-10 | Accucare, L.L.C. | Wheelchair seating indicator and methods of constructing and utilizing same |
US5799016A (en) * | 1996-01-11 | 1998-08-25 | U S West, Inc. | Network addressing scheme encoding communication channel information |
US6075796A (en) * | 1997-03-17 | 2000-06-13 | At&T | Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony |
-
1997
- 1997-03-17 US US08/819,617 patent/US6075796A/en not_active Expired - Lifetime
-
1998
- 1998-03-17 WO PCT/US1998/004091 patent/WO1998042107A1/en active Application Filing
-
2000
- 2000-05-02 US US09/565,281 patent/US6233249B1/en not_active Expired - Lifetime
-
2001
- 2001-03-01 US US09/797,358 patent/US6320875B2/en not_active Expired - Lifetime
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5550984A (en) * | 1994-12-07 | 1996-08-27 | Matsushita Electric Corporation Of America | Security system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services information |
Non-Patent Citations (2)
Title |
---|
CIVANLAR M R ET AL: "A practical system for MPEG-2-based video-on-demand over ATM packet networks and the WWW", SIGNAL PROCESSING. IMAGE COMMUNICATION, vol. 8, no. 3, April 1996 (1996-04-01), pages 221-227, XP004047066 * |
WANLEI Z: "Supporting fault-tolerant and open distributed processing using RPC", COMPUTER COMMUNICATIONS, vol. 19, no. 6, June 1996 (1996-06-01), pages 528-538, XP004052739 * |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6687258B1 (en) | 1998-09-04 | 2004-02-03 | Alcatel | Telecommunications system with a switching facility and a data concentrator for providing access to the internet |
DE19840329A1 (en) * | 1998-09-04 | 2000-03-09 | Alcatel Sa | Telecommunication system with switching device and data concentrator for access to the Internet |
USRE42069E1 (en) | 1998-09-04 | 2011-01-25 | Naxos Data Llc | Telecommunications system with a switching facility and a data concentrator for providing access to the internet |
US8693347B2 (en) | 1998-11-20 | 2014-04-08 | Level 3 Communications, Llc | Voice over data telecommunications network architecture |
US6442169B1 (en) | 1998-11-20 | 2002-08-27 | Level 3 Communications, Inc. | System and method for bypassing data from egress facilities |
US6614781B1 (en) | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US8953585B2 (en) | 1998-11-20 | 2015-02-10 | Level 3 Communications, Llc | System and method for bypassing data from egress facilities |
US8848894B2 (en) | 2000-05-04 | 2014-09-30 | Focal Ip, Llc | Tandem access controller within the public switched telephone network |
US9083719B2 (en) | 2000-05-04 | 2015-07-14 | Focal Ip, Llc | Controller for the intelligent interconnection of two communication networks, and method of use for same |
WO2002011389A3 (en) * | 2000-07-28 | 2002-05-23 | Dialpad Communications Inc | Data exchange with computers within a secure network |
WO2002011389A2 (en) * | 2000-07-28 | 2002-02-07 | Dialpad Communications, Inc. | Data exchange with computers within a secure network |
EP1671453A2 (en) * | 2003-09-10 | 2006-06-21 | Hyperdata Technologies, Inc. | Internet protocol optimizer |
EP1671453A4 (en) * | 2003-09-10 | 2010-01-20 | Hyperdata Technologies Inc | Internet protocol optimizer |
US8553572B2 (en) | 2003-09-10 | 2013-10-08 | Hyperdata Technologies, Inc. | Internet protocol optimizer |
EP2027698A1 (en) * | 2006-06-14 | 2009-02-25 | Nokia Corporation | Method and device for wireless transmission of internet protocol tv |
EP2027698A4 (en) * | 2006-06-14 | 2014-04-16 | Nokia Corp | Method and device for wireless transmission of internet protocol tv |
EP2033407A2 (en) * | 2006-06-16 | 2009-03-11 | Harris Corporation | Systems and methods for a protocol transformation gateway for quality of service |
WO2019007582A1 (en) * | 2017-07-05 | 2019-01-10 | Siemens Aktiengesellschaft | Method and device for feedback-free unidirectional transmission of data to a remote application server |
US11368437B2 (en) | 2017-07-05 | 2022-06-21 | Siemens Mobility GmbH | Method and apparatus for repercussion-free unidirectional transfer of data to a remote application server |
Also Published As
Publication number | Publication date |
---|---|
US20010009554A1 (en) | 2001-07-26 |
US6320875B2 (en) | 2001-11-20 |
US6075796A (en) | 2000-06-13 |
US6233249B1 (en) | 2001-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6075796A (en) | Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony | |
US6377571B1 (en) | Virtual modem for dialout clients in virtual private network | |
US6751218B1 (en) | Method and system for ATM-coupled multicast service over IP networks | |
US6700871B1 (en) | Increased throughput across data network interface by dropping redundant packets | |
US7283517B2 (en) | Stand alone multi-media terminal adapter with network address translation and port partitioning | |
EP0935373A2 (en) | a system for providing enhanced grade of service for connections over a large network | |
JP2001520472A (en) | Method and system for a network over a low bandwidth link | |
JPH09510596A (en) | Apparatus and method for hybrid network access | |
JP2005505171A (en) | Packet processing apparatus and method | |
JP2002523981A (en) | Method and apparatus for providing user multiplexing in a real-time protocol | |
US20040160945A1 (en) | Network communication system with a stand alone multi-media terminal adapter | |
JP2005529503A (en) | Method and apparatus for compressing packet headers | |
US20030137985A1 (en) | Communication apparatus with dial-up function | |
US6937598B1 (en) | Method and apparatus for transporting ATM cell traffic over IP networks | |
AU2003230349B2 (en) | Method and device for modem relay termination | |
US7193739B2 (en) | Real time fax-over-packet for broadband access gateways | |
US7336604B2 (en) | Network access module for supporting a stand alone multi-media terminal adapter | |
JPH07250100A (en) | Mutual communication system between lans using wide area network and mutual connection device used therefor | |
US20030167338A1 (en) | System and method to provide PPPoE connectivity to non-PPPoE clients | |
EP1303976B1 (en) | Distributed modem | |
EP1303955A1 (en) | A method of and a system for data exchange over a data network such as the public internet | |
JPH0964937A (en) | Communication controller, communication control method and communication system using the controller | |
JPH10117215A (en) | Inter-network connection method and its system | |
AU2003234533B8 (en) | Device for modem relay channel termination | |
JP4143479B2 (en) | Communication system between subscriber terminals |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA JP |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: JP Ref document number: 1998540542 Format of ref document f/p: F |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: CA |