WO2002019684A2 - Appareil et procede utiles pour mettre en oeuvre le protocole point-a-point sur ethernet pour des modems de bus - Google Patents

Appareil et procede utiles pour mettre en oeuvre le protocole point-a-point sur ethernet pour des modems de bus Download PDF

Info

Publication number
WO2002019684A2
WO2002019684A2 PCT/US2001/041870 US0141870W WO0219684A2 WO 2002019684 A2 WO2002019684 A2 WO 2002019684A2 US 0141870 W US0141870 W US 0141870W WO 0219684 A2 WO0219684 A2 WO 0219684A2
Authority
WO
WIPO (PCT)
Prior art keywords
host
pppoe
server
computer network
rfc
Prior art date
Application number
PCT/US2001/041870
Other languages
English (en)
Other versions
WO2002019684A3 (fr
Inventor
Ashok Doddapaneni
Mohammad Moradi
Original Assignee
Centillium Communications, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Centillium Communications, Inc. filed Critical Centillium Communications, Inc.
Priority to EP01966723A priority Critical patent/EP1317846A2/fr
Priority to AU2001287210A priority patent/AU2001287210A1/en
Publication of WO2002019684A2 publication Critical patent/WO2002019684A2/fr
Publication of WO2002019684A3 publication Critical patent/WO2002019684A3/fr

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/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2858—Access network architectures
    • H04L12/2859—Point-to-point connection between the data network and the subscribers
    • 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/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/2878—Access multiplexer, e.g. DSLAM
    • H04L12/2879—Access multiplexer, e.g. DSLAM characterised by the network type on the uplink side, i.e. towards the service provider network
    • H04L12/2881—IP/Ethernet DSLAM
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
    • H04M11/06—Simultaneous speech and data transmission, e.g. telegraphic transmission over the same conductors
    • H04M11/062—Simultaneous speech and data transmission, e.g. telegraphic transmission over the same conductors using different frequency bands for speech and other data
    • 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/6478—Digital subscriber line, e.g. DSL, ADSL, HDSL, XDSL, VDSL
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets

Definitions

  • This invention relates generally to a point-to-point protocol (PPP) implementation over the Ethernet, and, and in particular to an improved PPP implementation over the Ethernet for host computers using USB or PCI modems for communication incorporating a digital subscriber line (DSL) link.
  • PPP point-to-point protocol
  • DSL digital subscriber line
  • Digital subscriber line is a technology for high-bandwidth connectivity over ordinary copper telephone lines. Recently, broadband network applications are increasingly being implemented on various types of DSL, for example on asymmetric digital subscriber lines (ADSL).
  • DSL digital subscriber lines
  • xDSL refers to the family of DSL technologies, including DSL, ADSL, symmetric DSL (SDSL), high bit rate DSL (HDSL), very- high bit rate DSL (VDSL), and rate adaptive DSL (RADSL).
  • a DSL line allows for one line to carry both voice and data signals, and for the data part of the line to be continuously connected.
  • a DSL modem located at the phone company's central office, has a POTS splitter, which separates the voice calls from the data. Voice calls are routed to the phone company's public switched telephone network (PSTN) and proceed on their way as usual. Data coming from a PC passes from the DSL modem to a digital subscriber line access multiplexer (DSLAM).
  • PSTN public switched telephone network
  • a DSLAM is a network device, usually at a telephone company central office, that receives signals from multiple customer DSL connections and puts the signals on a high-speed backbone line using multiplexing techniques.
  • a DSLAM connects a DSL line with some combination of asynchronous transfer mode (ATM), frame relay, or IP networks.
  • ATM asynchronous transfer mode
  • a DSLAM enables a phone company to offer business or homes users a fast telephone line technology (e.g., xDSL) with a fast backbone network technology (e.g., an asynchronous transfer mode technology or an equivalent).
  • FIG. 1 illustrates one example of a prior art implementation of a connection between multiple hosts 102, 104, and 106 to an ISP/corporate server 114.
  • Host 102, 104, and 106 are connected (e.g., through the Ethernet) to CPE 108, which operates as a router to a DSL line to access multiplexer 110 in the central office of the telephone service provider.
  • Access multiplexer 110 is connected through computer network 112 to ISP/corporate server 114.
  • the DSLAM typically links many DSL lines to a single high-speed asynchronous transfer mode (ATM) line, which in turn connects to the Internet at data transfer speeds up to one gigabyte per second.
  • ATM technology is a high-performance, cell-oriented switching and multiplexing technology that utilizes fixed-length packets to carry different types of traffic.
  • ATM is a technology that enables carriers to capitalize on a number of ATM classes of services; such as high-speed local-area network (LAN) interconnection, voice, video, and future multimedia applications.
  • LAN local-area network
  • FIG. 2 illustrates a more detailed example of a prior art implementation of a connection using a DSLAM and an ATM network between multiple hosts 102, 104, and 106 to an ISP/corporate server 114.
  • Host 102, 104, and 106 are connected (e.g., through the Ethernet) to CPE 108, which operates as a router to a DSL line to DSL access multiplexer 210 in the central office of the telephone service provider.
  • DSL access multiplexer 210 is connected through ATM computer network 212 to ISP/corporate server 114.
  • ATM wide area, campus, and local area networks are used to transport IP data-grams and other connectionless traffic between hosts, routers, bridges, and other networking devices.
  • the unit of transport in ATM networks is a 53 octet fixed length Protocol Data Unit (PDU) called a cell.
  • a cell consists of a 5-octet header and a 48-octet payload. Variable length PDUs must be segmented by the transmitter to fit into the 48-octet ATM cell payload, and are reassembled by the receiver.
  • RFC 2684 describes two encapsulations methods to carry network interconnect traffic over an ATM network.
  • the first method allows multiplexing of multiple protocols over a single ATM virtual connection (VC), whereas the second method assumes that each protocol is carried over a separate ATM VC.
  • RFC 2684 is intended for implementations of ATM networks that carry multi-protocol traffic among hosts, routers, and bridges that are ATM end systems.
  • PPP point-to-point protocol
  • NCPs Network Control Protocols
  • Point-to-point protocol over Ethernet is a proposal specifying how a host personal computer (PC) interacts with a broadband modem (e.g., xDSL, cable, wireless, and equivalents) to achieve access to the growing number of high-speed data networks.
  • PC personal computer
  • broadband modem e.g., xDSL, cable, wireless, and equivalents
  • PPPoE point- to-point protocol
  • the PPPoE implementation requires more knowledge on the part of the end user than that required for standard dial-up Internet access.
  • ISPs Internet service providers
  • PPPoE The significance of PPPoE has to do with its greater ease of use versus competing approaches. PPPoE could speed the widespread adoption of high-speed access services by making high-speed access easier to use for end consumers, and more seamless to integrate into the existing infrastructure for carriers and ISPs. PPPoE also provides a major advantage for a service provider by maximizing integration with, and minimizing disruption of, the existing dial network infrastructures of the ISP. Through tight integration with existing back office automation tools that ISPs have developed for dial customers, PPPoE enables rapid service deployment and cost savings. PPPoE supports a broad range of existing applications and services, from authentication, accounting, and secure access to configuration management.
  • PPPoE The base protocol for PPPoE is described in RFC 2516 published by the Internet Engineering Task Force (IETF). Multiple hosts at a remote site can connect through the same customer premise access device. ISPs are able to provide access control and billing functionality in a manner similar to dial-up services using PPP, and therefore do not need a massive upgrade of their systems.
  • a host machine seeking access to any network uses an Ethernet card and connects to an Ethernet bridging device that also acts as DSL customer premise equipment (CPE).
  • CPE DSL customer premise equipment
  • PPPoE provides the ability to connect a network of hosts over a simple bridging access device to a remote access concentrator. With this model, each host utilizes its own PPP stack, and the user is presented with a familiar user interface. Access control, billing, and type of service can be done on a per-user, rather than a per-site, basis.
  • PPPoE To provide PPPoE, each PPP session must learn the Ethernet address of the remote peer, as well as establish a unique session identifier.
  • PPPoE includes a discovery protocol that provides this.
  • PPP provides a standard method for transporting multi-protocol data-grams over point-to- point links.
  • PPP Packet Control Protocol
  • Network- layer Control Protocols Authentication Protocol
  • the prior art can be used by multiple hosts on a shared Ethernet to open PPP sessions to multiple destinations via one or more bridging modems.
  • the prior art is used with broadband remote access technologies that provide a bridged Ethernet topology, when access providers wish to maintain the session abstraction associated with PPP.
  • the above description illustrates some of the components of PPPoE technology. What is needed is a simplified network method and apparatus for communication between a host and a server. Moreover, such a method and apparatus preferably should be less expensive than a conventional method and apparatus.
  • the present invention provides a simplified network method and apparatus for communication between a host and a server.
  • the invention provides an improved connection between a host and a server.
  • the invention can be implemented as a method, a system, an apparatus, or in a program on electronically-readable media. Several aspects of the invention are described below.
  • the invention provides a method to connect a host having an operating system to a server through a computer network.
  • the method includes installing a modem in the host; establishing a connection in the computer network between the host and the server through the modem by using a dial-up service provided by an operating system vendor that supplied the operating system of the host; and communicating information between the host and the server through the computer network.
  • the invention provides a computer network connecting a host to a server.
  • the computer network includes a host, controlled by an operating system; an xDSL PCI or USB modem that can function as a digital subscriber line customer premise equipment to said host; and a connection from the xDSL PCI or USB modem to a multiplexer, wherein the multiplexer is connected to the server, and the connection between the host and the server includes a dial-up service pro-vided by an operating system vendor that supplied the operating system to control the host.
  • the invention provides a data processing system.
  • the data processing system includes a server, connected to a network; a host, controlled by an operating system; an xDSL PCI or USB modem that can function as a digital subscriber line customer premise equipment to said host; and a connection from the xDSL PCI or USB modem to a multiplexer, wherein the multiplexer is connected to the server through the network, and the connection between the xDSL PCI or USB modem and the multiplexer includes a dial-up service provided by an operating system vendor that supplied the operating system to control the host.
  • FIG. 1 illustrates one example of a prior art implementation of a connection between multiple hosts to an ISP/corporate server.
  • FIG. 2 illustrates a more detailed example of a prior art implementation of a connection using a DSLAM and an ATM network between multiple hosts to an ISP/corporate server.
  • FIG. 3 illustrates one example of the prior art with regards to the components of the host operating system to implement PPPoE.
  • FIG. 4 illustrates one preferred embodiment of the invention with regards to the components of the host operating system to implement PPPoE.
  • FIG. 5 illustrates one preferred embodiment of a host using a DSL network interface card (NIC) to communicate by PPPoE to an ISP/corporate server.
  • FIG. 6 summarizes one preferred embodiment of the invention with regards to the software component protocols used by the host, the DSLAM, and the ISP/corporate server to implement PPPoE.
  • NIC DSL network interface card
  • FIG. 7 illustrates a prior art flow chart for the installation and connection steps required for a customer to implement PPPoE communication.
  • FIG. 8 illustrates a flow chart for the installation and connection steps required for a customer to implement PPPoE communication according to one preferred embodiment of the invention.
  • FIG. 9 illustrates a flow chart that shows the sequence of operations that happens in the driver when a packet is sent to the driver from an upper layer (the PPP driver), according to one preferred embodiment.
  • FIG. 10 illustrates a flow chart that shows the sequence of operations that happens in the driver when a packet is received from the computer network, according to one preferred embodiment.
  • PPPoE has two distinct stages. There is a discovery stage and a PPP session stage. When a Host initiates a PPPoE session, it must first enter the discovery stage to identify the Ethernet Media Access Controller (MAC) address of the peer and establish a PPPoE session identification. While PPP defines a peer-to-peer relationship, the discovery stage is inherently based on a client- server relationship.
  • MAC Media Access Controller
  • a Host (the client) discovers an Access Concentrator (e.g., a server). Based on the network topology, there may be more than one Access Concentrator with which the Host can communicate.
  • the discovery stage allows the Host to discover all Access Concentrators and then select one. When the discovery stage completes successfully, both the Host and the selected Access Concentrator have the information they will use to build their point-to-point connection over the Ethernet.
  • the discovery stage remains stateless until a PPP session is established. Once a PPP session is established, both the Host and the Access Concentrator allocate the resources for a PPP virtual interface.
  • both peers know the PPPoE session identification and the peer's Ethernet address, which together define the PPPoE session uniquely.
  • the steps consist of (1) the Host broadcasting an Initiation packet, (2) one or more Access Concentrators sending Offer packets, (3) the Host sending a unicast Session Request packet, and (4) the selected Access Concentrator sending a Confirmation packet.
  • the Host receives the Confirmation packet, it may proceed to the PPP session stage.
  • the Access Concentrator sends the Confirmation packet, it may proceed to the PPP session stage.
  • PPP data is sent as in any other PPP encapsulation. All Ethernet packets are unicast.
  • the session identification (Session_ID) does not change for that PPPoE session stage, and is the value assigned in the Discovery stage.
  • the PPPoE payload contains a PPP frame that begins with the PPP Protocol-ID.
  • PPPoE also uses various software modules for communicating across interfaces between an operating system and various software device drivers.
  • An application programming interface is a set of subroutines or functions that a program, or application, can call to tell the operating system to perform some task.
  • the Windows API consists of more than 1,000 functions that programs written in C, C++, Pascal, and other languages can call to create windows, open files, and perform other essential tasks. For example, an application that wants to display an onscreen message can call Windows' MessageBox API function.
  • NDIS Network Driver Interface Specification
  • NIC Network Interface Cards
  • the hardware implementation details for a NIC is wrapped by a "Media Access Controller” (MAC) device driver in such a way that all NICs for the same media (e.g., Ethernet media) can be accessed using a common programming interface.
  • MAC Media Access Controller
  • NDIS also provides a library of functions (sometimes called a "wrapper") that can be used by MAC drivers as well as higher-level protocol drivers (e.g., TCP/IP).
  • the wrapper functions serve to make development of both the MAC and protocol drivers easier as well as to hide (to some extent) platform dependencies.
  • Corporations such as Microsoft and 3Com Corporation jointly developed early versions of NDIS.
  • FIG. 3 illustrates one example of the prior art with regards to the components of the host operating system 300 to implement PPPoE.
  • the host operating system 300 includes the TCP/IP module 302 of the original operating system (O/S) vendor, a third party vendor PPPoE module 308, a NDIS module 304 of the original O/S vendor (that supplies an interface to the optional Ethernet module 306), and a RFC 1483 bridge mode module 310 for USB or PCI modems.
  • the Ethernet module 306 includes a device driver that implements the Ethernet protocol and drives an Ethernet NIC.
  • An Ethernet NIC in the host is frequently referred to as an Ethernet port.
  • the Ethernet Module 306 would be included in the host operating system 300 shown in FIG. 3.
  • the CPE 108 is an xDSL PCI or USB modem
  • the connections to the hosts 102, 104, and 106 are not implemented through the Ethernet. In this case, the Ethernet Module 306 would not be included in the host operating system 300 shown in FIG. 3.
  • FIG. 4 illustrates one preferred embodiment of the invention with regards to the components of the host operating system 400 to implement PPPoE.
  • the host operating system 400 includes the TCP/IP module 302 of the original operating system (O/S) vendor, the PPP module 408 of the original O/S vendor, the NDIS WAN module 404 of the original O/S vendor, and a PPPoE and RFC 1483 bridge mode module 410 for USB/PCI modems.
  • More preferred embodiments do not require an Ethernet port in the host computer to implement PPPoE, but alternative embodiments can have one or more Ethernet ports in the host computer.
  • a preferred embodiment without an Ethernet port is in contrast to the prior art, which required at least one Ethernet port in the host computer to implement PPPoE.
  • FIG. 5 illustrates one preferred embodiment, with a host 104 using an xDSL PCI or USB modem 504 to communicate by PPPoE to an ISP/corporate server 114.
  • Host 104 contains an xDSL PCI/USB modem 504, which is connected to DSL access multiplexer 210 in the central office of the telephone service provider.
  • DSL access multiplexer 210 is connected through ATM computer network 212 to ISP/corporate server 114.
  • a more preferred embodiment makes use of Microsoft's existing PPP stack and implements PPPoE on top of RFC1483 (or RFC 2684) bridge-mode LLC encapsulation software.
  • the driver needs to export the NDISWAN interface.
  • the discovery stage Before the first PPP packet (a LCP protocol packet) is sent to the remote PPP server, the discovery stage has to be finished. After the discovery stage is finished, the driver has the MAC address of the Access Concentrator and a SessionJD for the PPP session stage.
  • the PPPoE header is added with the Access Concentrator's MAC address and the SessionJD before sending packets on the network.
  • FIG. 6 summarizes one preferred embodiment of the invention with regards to the software component protocols used by the host 104, the DSLAM 210, and the ISP or corporate server 114 to implement PPPoE.
  • the host 104 uses the following protocols: TCP/IP from the original operating system (O/S) vendor, PPP from the original O/S vendor, PPPoE, Ethernet, RFC 1483 (or RFC 2684) from a third party supplier, ATM, and xDSL.
  • the DSLAM uses the following protocols: ATM and xDSL.
  • the ISP/corporate server 114 uses the following protocols: TCP/IP, PPP, PPPoE, Ethernet, RFC 1483 (or RFC 2684), ATM, and xDSL.
  • FIG. 7 illustrates a prior art flow chart 700 for the installation and connection steps required for a customer to implement PPPoE communication.
  • the method starts in operation 702.
  • the customer installs a modem in the host computer.
  • Operation 706 is next, where the customer installs the third party PPPoE software in the host computer.
  • Operation 708 is next, where the customer dials up the third party to execute the third party PPPoE software to establish a connection between the host computer and the ISP/corporate server over a computer network.
  • Operation 710 is next, where the customer starts communication.
  • Operation 712 is next, where the customer ends the communication.
  • the method ends in operation 714.
  • FIG. 8 illustrates a flow chart 800 for the installation and connection steps required for a customer to implement PPPoE communication according to one preferred embodiment.
  • the method starts in operation 802.
  • the customer installs a modem in the host computer.
  • Operation 808 is next, where the customer uses the original O/S vendor software to dial-up the original O/S vendor to establish a connection between the host computer and the
  • Operation 810 is next, where the customer starts communication.
  • Operation 812 is next, where the customer ends the communication. The method ends in operation 814.
  • FIG. 9 illustrates a flow chart 900 that shows the sequence of operations that happens in the driver (i.e., the PPPoE bridge mode module 410 shown in FIG. 4) when a packet is sent to the driver from an upper layer (the PPP driver), according to one preferred embodiment.
  • the method starts in operation 902.
  • operation 904 a PPP packet is received.
  • Operation 906 is next, where a test is made to determine if a PPPoE session was started. If the test in operation 906 determines no PPPoE session was started, then operation 908 is next.
  • the PPPoE discovery state machine is scheduled to setup a PPPoE session.
  • Operation 910 is next, where a test is made to dete ⁇ nine if a PPPoE session is established. If the test of operation 910 determines a PPPoE session was not established, then operation 908 is repeated. If the test of operation 910 determines a PPPoE session is established, then operation 912 is next. If the test of operation 904 determines a PPP packet was received, then operation 912 is next. In operation 912, PPPoE encapsulation and RFC 1483 bridge mode encapsulation are added and operation 914 is next. In operation 914 the packet is sent over the computer network. The method ends in operation 916.
  • FIG. 10 illustrates a flow chart 1000 that shows the sequence of operations that happens in the driver (i.e., the PPPoE bridge mode module 410 shown in FIG. 4) when a packet is received from the computer network, according to one preferred embodiment.
  • the method starts in operation 1002.
  • a PPPoE packet is received.
  • a test is made to determine if the received packet is of type 0x8863 for the PPPoE discovery stage. If the test in operation 1006 determines that the received packet was type 0x8863, then operation 1008 is next.
  • the PPPoE discovery state machine is scheduled to setup a PPPoE session, and the packet is passed on.
  • operation 1010 is next.
  • a test is made to determine if the received packet is of type 0x8864, indicating that a PPPoE session is established. If the test of operation 1010 determines the received packet is not type 0x8864 (a PPPoE session was not established), then operation 1012 is next, where a data error is declared and the packet is dumped. If the test of operation 1010 determines the received packet was type 0x8864 (a PPPoE session is established), then operation 1014 is next. In operation 1014, the RFC 1483 bridge mode encapsulation and PPPoE encapsulation are stripped off. Operation 1016 is next, where the packet is passed to the PPP driver. The method ends in operation 1018.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un appareil et un procédé qui permettent de mettre en oeuvre une version améliorée du protocole point-à-point sur l'Ethernet (PPPoE) pour assurer la communication par modem entre un ordinateur hôte et un ordinateur serveur. Dans une première forme de réalisation, cette invention concerne un procédé d'utilisation de PPPoE pour connecter un hôte ayant un système d'exploitation à un serveur par l'intermédiaire d'un réseau informatique. Dans une deuxième forme de réalisation, cette invention concerne un réseau informatique utilisant PPPoE pour connecter un hôte à un serveur. Dans une troisième forme de réalisation, cette invention concerne un système de traitement de données utilisant PPPoE.
PCT/US2001/041870 2000-09-01 2001-08-23 Appareil et procede utiles pour mettre en oeuvre le protocole point-a-point sur ethernet pour des modems de bus WO2002019684A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP01966723A EP1317846A2 (fr) 2000-09-01 2001-08-23 Appareil et procede utiles pour mettre en oeuvre le protocole point-a-point sur ethernet pour des modems de bus
AU2001287210A AU2001287210A1 (en) 2000-09-01 2001-08-23 Apparatus and method for implementation of pppoe for bus modems

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US23005100P 2000-09-01 2000-09-01
US60/230,051 2000-09-01
US75546501A 2001-01-04 2001-01-04
US09/755,465 2001-01-04

Publications (2)

Publication Number Publication Date
WO2002019684A2 true WO2002019684A2 (fr) 2002-03-07
WO2002019684A3 WO2002019684A3 (fr) 2002-06-13

Family

ID=26923860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/041870 WO2002019684A2 (fr) 2000-09-01 2001-08-23 Appareil et procede utiles pour mettre en oeuvre le protocole point-a-point sur ethernet pour des modems de bus

Country Status (3)

Country Link
EP (1) EP1317846A2 (fr)
AU (1) AU2001287210A1 (fr)
WO (1) WO2002019684A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003105522A1 (fr) * 2002-06-11 2003-12-18 Siemens Aktiengesellschaft Procede et multiplexeur d'acces permettant un acces rapide a des reseaux de donnees

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5142680A (en) * 1989-04-26 1992-08-25 Sun Microsystems, Inc. Method for loading an operating system through a network
WO2000038371A1 (fr) * 1998-12-18 2000-06-29 Covad Communications Company Procede et systeme permettant de decongestionner un reseau par paquets en mode connexion ayant acces a une ligne numerique d'abonne

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5142680A (en) * 1989-04-26 1992-08-25 Sun Microsystems, Inc. Method for loading an operating system through a network
WO2000038371A1 (fr) * 1998-12-18 2000-06-29 Covad Communications Company Procede et systeme permettant de decongestionner un reseau par paquets en mode connexion ayant acces a une ligne numerique d'abonne

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003105522A1 (fr) * 2002-06-11 2003-12-18 Siemens Aktiengesellschaft Procede et multiplexeur d'acces permettant un acces rapide a des reseaux de donnees
US7424023B2 (en) 2002-06-11 2008-09-09 Siemens Aktiengesellschaft Method and access multiplexer for quick access to data networks

Also Published As

Publication number Publication date
WO2002019684A3 (fr) 2002-06-13
EP1317846A2 (fr) 2003-06-11
AU2001287210A1 (en) 2002-03-13

Similar Documents

Publication Publication Date Title
US8923284B2 (en) Method and system of providing multi-user access to a packet switched network
US7154912B2 (en) System and method for provisioning broadband service in a PPPoE network using a list of stored domain names
US7047304B2 (en) System and method for provisioning broadband service in a PPPoE network using a configuration domain name
US7469298B2 (en) Method and system for enabling layer 2 transmission of IP data frame between user terminal and service provider
US6118785A (en) Point-to-point protocol with a signaling channel
US6977906B2 (en) System and method for provisioning broadband service in a PPPoE network using a random username
US7808978B2 (en) Voice over internet protocol (VoIP) telephone apparatus and communication system for carrying VoIP traffic
US20010030977A1 (en) Proxy methods for IP address assignment and universal access mechanism
US20040105444A1 (en) Auto-configuration of broadband service for one of a plurality of network communication protocols
EP2636188B1 (fr) Appareil et procédés pour une connectivité inter-réseau multimode
AU4723299A (en) Apparatus and method for a remote access server
WO2003075517A2 (fr) Configuration de passerelle ppp sans installation pour connectivite reseau local a reseau grande distance
US7228358B1 (en) Methods, apparatus and data structures for imposing a policy or policies on the selection of a line by a number of terminals in a network
US20100287287A1 (en) Network Apparatus and Method for Translating Media Access Control Addresses
EP1423940A1 (fr) Fourniture de services de communication d'utilisateur final via des connexions protocole internet point a point entre des fournisseurs de services
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Designing ISDN Internetworks
Cisco Dial Solutions Configuration Guide Cisco IOS Release 12.0

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 2001966723

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2001966723

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase in:

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: 2001966723

Country of ref document: EP