Communications system for identifying remote digital subscriber line (DSL) customer premises equipment (CPE) devices during a discovery phase

A method and system for use in identifying customer premises equipment (CPE) in a distributed network are presented. The method utilizes a unique identifier provided by a CPE device to a host server during the discovery stage of PPPoE communications in a distributed network. The server receives the unique identifier and stores the identifier for use in identifying and managing CPE devices attached to a service provider's network. The host server is configured to receive an active discovery packet from a communications device. The active discovery packet has a tag comprising a device identifier field. The device identifier includes chipset and firmware information regarding remote DSL CPE.

BACKGROUND

1. Field of the Invention

The present disclosure relates to identifying characteristics of customer premise equipment using point-to-point-over-Ethernet (PPPOE) service.

2. Description of the Related Art

Broadband service providers for distributed computing network services such as digital subscriber line (DSL) service typically require the end user, e.g., the home or business DSL subscriber, to employ a router, switch, or other customer premises equipment (CPE) to terminate the DSL connection at the residence or business location. The router or other CPE serves to terminate the Asynchronous Transfer Mode (ATM) connection, and generally utilizes point-to-point-over-Ethernet (PPPoE) enabled software to complete the user authentication process.

When a DSL subscriber encounters a problem with their DSL connection, the DSL service provider has no way to automatically determine the specific make and/or model of a particular CPE device being utilized by the DSL subscriber. In this situation, telephone inquiries to the subscriber are made to attempt to discover what type of equipment is being utilized at the CPE location, or a service technician is dispatched to “eyeball” the equipment when the customer does not know what type of CPE device is at their location. Consider a typical case of tens of thousands (or even millions, in some cases) of DSL subscribers and their respective CPE devices, and the support problems presented to the DSL service provider become evident.

In addition, when a service provider wishes to upgrade DSL transport services in their service area(s), e.g., the provision of Point to Point Protocol Termination and Aggregation (PTA), it may be difficult to cost-effectively deploy the new service plan if the service provider does not know what types of CPE devices are currently deployed. For example, if a new transport service is scheduled for deployment in a specific geographic region, but it is determined that a large number of CPE devices may not support the new service, delays in deployment result. Such delays lead to increased provider costs, which are typically passed along to the subscribers, resulting in higher rates.

Accordingly, there is a need for a system or method which is capable of automatically identifying CPE devices and their equipment type in a service provider's service area.

DESCRIPTION OF THE DRAWINGS

The present disclosure provides a method, system, and apparatus for use in identifying customer premises equipment (CPE) in a distributed network. The method utilizes a unique device identifier that is provided by a CPE device during the discovery stage of point-to-point over Ethernet (PPPOE) communications in a distributed network. A host server collects this CPE-provided information, which may be used by a broadband service provider to identify, and thus manage, the CPE devices which form a part of the service provider's network domain. An example of a distributed network system including a collection of domains with one or more networks is illustrated inFIG. 1. An exemplary device identifier includes chipset and firmware information regarding the DSL CPE and is illustrated inFIG. 9.

FIG. 1is a simplified example of a distributed network, and is referred to as distributed network system100. Distributed network system100can include numerous routing domains103and105, which are connected to a backbone network101. In a hierarchically arranged network system, backbone101is the central connection path shared by the nodes and networks connected to it. The backbone101administers the bulk of traffic between communicating nodes to provide end-to-end service between one user, for example, source node121in domain103, and another user, for example destination node142.

Each routing domain103,105in distributed network system100is a collection of one or more local networks that are attached to the backbone101through one or more routers123,124,125,130,132,134, and135. A router is a specialized computer for processing Internet protocol (IP) data and forwarding IP data along respective network paths. In the following discussion, the term local network shall be used to refer to all types of networks that may be included in a domain. Routing domains103and105are also referred to as autonomous systems (AS). An autonomous system is a set of nodes and routers that operate under the same administration. The domains103and105may be operated by the same service provider (same administration) or by different service providers. The networks in routing domains103and105may be residence/subscribers' home networks, local area networks (LAN), wide area networks (WAN), metropolitan area networks (MAN), or the like.

In a point-to-point (PPP) connectivity network, various types and models of CPE devices such as CPE devices124and125, or130,140, and135are used to terminate the point-to-point (PPP) connections. One type of point-to-point connectivity communications is point-to-point over Ethernet (PPPoE). With various types of broadband access, e.g. digital subscriber line (DSL) service, connectivity may be provided via PPPoE within the domains103and105. It will be appreciated that the numbers of networks, routers, CPE devices, and nodes (nodes are depicted by a circle with ‘N’ inscribed within the circle) have been constrained in the example ofFIG. 1to avoid clutter.

Broadband access service, such as digital subscriber line (DSL) service, entails the use of a CPE device to terminate the DSL (PPPOE) connection at the residence or business location of the DSL subscriber. This is illustrated inFIG. 2, which illustrates a simplified diagram of a point-to-point connection being established.

FIG. 2illustrates a CPE device225connected through an IP network201to an access concentrator223. In an embodiment, the access concentrator223is a broadband remote access server (BRAS).

Typically, the CPE device225terminates the asynchronous transfer mode (ATM) connection, and has point-to-point over Ethernet (PPPOE) software to complete a user authentication process. The CPE device225may be a router or a switch, or any device that terminates a PPPoE connection. The CPE device225contains a module configured to transmit a PPPoE packet including a tag to uniquely identify the CPE device225product model. Access concentrator223is connected to a database226to store the device identifier field data obtained from the CPE device225during discovery/authentication processes. The method utilizes the packet exchange during the conduct of a PPPoE discovery process.

PPPoE has two distinct stages, a discovery stage, and a PPP session stage. When a host wishes to initiate a PPPoE session, it first performs discovery to identify the Ethernet media access control (MAC) address of the peer, and establishes a PPPoE SESSION_ID. Although PPP defines a peer-to-peer relationship, discovery is a client-server relationship. That is, in the discovery process, a host (the client, or CPE device225) discovers an access concentrator223(the server), and various discovery steps are followed to permit the host and the server to have the information required to build their point-to-point connection over Ethernet. This discovery process is illustrated inFIG. 3.

The method and system disclosed herein utilizes a tag identified in Internet Engineering Task Force (IETF) RFC 2516 (A Method for Transmitting PPP over Ethernet (PPPoE)) in an innovative way to determine which CPE devices, such as CPE device225, are connected to a network. The client (CPE225) is capable of generating a device identifier code in response to receiving a PPPoE packet communicated over a distributed network. In the first step302of the discovery process, the CPE device225broadcasts a PPPoE active discovery initiation (PADI) packet. This PADI packet includes a tag that specifically identifies a product model of the CPE device225. The tag in a particular embodiment is a host-uniq tag, and the device identifier code is a binary number associated with a specific product model or type of CPE device. In a specific embodiment, the binary number is a nine bit binary number.

The access concentrator223, such as the broadband remote access server (BRAS), transmits a PPPoE active discovery offer (PADO) packet in step304. In step306, the PADO packet is received by the client225, and accepted. In response to the PADO packet receipt, an active discovery request packet (PADR) packet is generated and transmitted to the server223. The PADR packet can also include a tag that specifically identifies a product model of the CPE device225. In step308, the server receives the PADR packet, and generates and transmits a PPPoE active discovery session (PADS) confirmation packet. The session discovery process is concluded, and an Ethernet communication session is then conducted between the client225and the server223.

The host-uniq tag information may be transmitted in the PADI packet. Alternatively, the host-uniq tag information may also be transmitted in the PADR packet. Generally it is most efficient to utilize the PADI packet for device identification, however, the CPE device could return the device identifier in the tag with a PADR packet as well. Whether the tag information is contained in the PADI or PADR packets, the access concentrator223receives the PAD packet, and stores the device identifier code in a database (226,FIG. 2). After collection of the device identifier codes in the tag, the database can be used to determine the specific product model of a CPE device based on the information embedded in the tag. This information is then available to be provided to customer service representatives to diagnose and repair user problems, thereby decreasing the number of customer site visits and subscriber call requests required of service technicians.

An advantage provided by the disclosed method is that it facilitates network management based upon the product model of the CPE devices determined to be present in the network. For example, the use of the host-uniq tag and the unique device identifier allows broadband service providers to check on the CPE devices in use on the provider's network. This information could be used to target marketing efforts, or to enable surveys of existing equipment to determine if the existing equipment will work with new technologies that a broadband service provider would like to deploy. It should be noted that although the examples provided thus far have discussed primarily DSL broadband services, PPPoE is an authentication system that is not restricted to DSL.

FIG. 4is a block diagram of an ADSL bridge/router board400incorporating a module415configured to transmit a point-to-point over Ethernet (PPPOE) active discovery packet including a tag. In a particular embodiment, the tag comprises a device identifier field that uniquely identifies a CPE product model. It will be appreciated that, with the exception of module415, the block diagram ofFIG. 4is provided as a generic example of an integrated microprocessor designed to meet the needs of communications applications, and as such does not represent the only architecture possible for CPE devices.

CPE board400includes a memory control module409with connecting Flash411and SDRAM410memory components. Other components in board400include a universal serial bus (USB) controller419and a USB device connector420; an ATM segmentation and reassembly (SAR) controller module414; a DSL chipset412and DSL connector413; a 10/100 Mbps Ethernet controller module416, transceiver417, and connector418. ATM controller module414and Ethernet controller module415have been integrated into the board400as network interfaces.

During a PPPoE discovery process, module415sends a PPPoE active discovery (PAD) packet. The PAD packet includes a tag comprising a device identifier field that uniquely identifies a CPE product model. The device identifier field can also be generated in response to receiving a PAD packet. The PAD packet containing the tag/device identifier can be a PADI packet, or alternately, a PADR packet. In one embodiment, the tag is a host-uniq tag, and the device identifier field comprises a predefined binary number embedded in the host-uniq tag. This predefined binary number can be a nine-bit binary device identifier code.

FIG. 5illustrates a data packet500for use in a distributed network. The data packet500includes a destination address field (DESTINATION_ADDR)502which typically contains either a unicast Ethernet destination address, or the Ethernet broadcast address (0xffffffff). For discovery packets, the field502value is either a unicast or a broadcast address. For PPP session traffic, the field502value contains the peer's unicast address as determined from the discovery stage.

A source address field (SOURCE_ADDR)504is also contained in data packet500. This field504contains the Ethernet media access control (MAC) address of the source device. The ETHER_TYPE field506is set to a first value during the discovery stage, or to a second value during the PPP session stage. The payload field508contains the Ethernet payload for PPPoE, and is discussed in detail inFIG. 6. The checksum field510serves to verify packet integrity.

FIG. 6illustrates an illustrative Ethernet payload that may be used with PPPoE. The VERSION field602is four bits, and identifies the version number of the PPPoE specifications, e.g., 0x1. The TYPE field604is four bits, and identifies the Ethernet type for a given version of PPPoE specifications. The CODE field606is eight bits, and the CODE field value depends upon whether discovery stage or PPP stage is in effect.

The SESSION_ID field612is 16 bits, and is an unsigned value in network byte order. For a given PPP session, the field612is fixed, and defines a PPP session along with the Ethernet source address (504inFIG. 5) and destination address (502inFIG. 5). In the discovery stage, the SESSION_ID field612has a different value depending upon the type of discovery packet in which field612is contained. The LENGTH field610is 16 bits having a value, in network byte order, that indicates the length of the PPPoE payload608.

A PPPoE payload508contains zero or more tags. A tag is a type-length-value (TLV) construct, and an example tag is shown inFIG. 7. The sample tag includes a TAG_TYPE field702that is a 16 bit field in network byte order. A list of tag types that may be present in the field702includes tag types end-of-list, service-name, AC-name, host-uniq, and AC-cookie tags. The TAG_LENGTH field704is 16 bits, and is an unsigned number in network byte order which indicates the length in octets of the TAG_VALUE706.

ETF RFC 2516 defines the host-uniq tag as follows: “This tag is used by a host to uniquely associate an access concentrator response (PADO or PADS) to a particular host request (PADI or PADR). The TAG_VALUE is binary data of any value and length that the host chooses. It is not interpreted by the access concentrator. The host may include a host-uniq tag in a PADI or PADR. If the access concentrator receives this tag, it must include the tag unmodified in the associated PADO or PADS response.” From the foregoing IETF definition, it should be clear that although the present disclosure utilizes a predefined tag, the tag is utilized in a unique way to identify CPE devices, as well as to collect CPE device information at the access concentrator or database server attached to the access concentrator, for network management purposes.

An example of a nine bit binary CPE device identifier code embedded in a host-uniq tag is illustrated inFIG. 8. The CPE device identifier code uses numbers in the standard binary number system to produce any particular CPE device number between 0 and 512. In Example 1 ofFIG. 8, an Efficient Networks 5861 Router has the binary number 000000001, making its device binary number equal to 1. In Example 2, a Netopia 3546 Router has the binary number 111111111, making its device binary number equal to 512. Using the examples ofFIG. 8, when a device identifier code transmitted to the access concentrator/database from the CPE device is 111111111, the determination would be that this CPE device model type is a Netopia 3546 Router. Similarly, when the identifier code received is 000000001, the access concentrator would determine that the CPE device model type is an Efficient Networks 5861 Router.

Referring toFIG. 9, another embodiment of a host-uniq tag900is illustrated. The host-uniq tag900includes a first set of data (bits1–8)908, a second set of data (bits9–16)910, and a third set of data (bits17–24)912. The first set of data908forms a first field902that includes a device firmware description. The second set of data910includes a second field904that includes chipset information, and the third set of the data912forms a third field906that includes chipset code or firmware information. The device firmware field902includes a unique identifier for a particular type of firmware for a CPE device, such as a router for a DSL modem. Similarly, the chipset field904includes a unique identity of the chipset type used by the CPE device. The chipset code or firmware field906identifies the chipset code or firmware used by the chipset of the particular CPE device identified by the host-uniq tag900. By identifying the particular type of equipment for the CPE device, technical support operators and customer support personnel may receive further information regarding the particular type of CPE devices and their equipment configurations throughout the network.

Referring toFIG. 10, an illustrative system that may use the host-uniq tag900is shown. The system includes a broadband access server1008, a computer network such as the internet1010, a customer service terminal1004, and a technical staff and operations systems1006. The technical staff and operations system1006is coupled to a report generation module1012. The operations system includes an operation station for use by operations personnel to access device information for the remote DSL CPE devices. The broadband server1008includes a memory1002that stores the host-uniq tag900. The host uniq-tag900is stored in the memory1002upon retrieval from remote CPE devices using the point-to-point over Ethernet protocol during the discovery phase. The host-uniq tag900may be retrieved and distributed to either the customer service terminal1004or the operation system1006via the internet1010.

The customer service terminal1004provides a display screen for customer help desk personnel that are assisting far end customers such as DSL subscribers with connectivity and other service issues. The customer service terminal1004may display to the customer support personnel information regarding the remote CPE device such as a particular device's firmware, chipset or chipset code firmware as determined by the host-uniq tag900. Similarly, the technical staff and operations system1006may retrieve the host-uniq tag900and evaluate the tag900to determine CPE equipment information throughout the network. The technical staff may use such information for troubleshooting and operations personnel may use such information for providing technical support as well as equipment updates and other technical deployments. For example, when the operations staff evaluates network performance and errors, the staff may characterize CPE equipment failures based on the particular information within the host-uniq tag, such as the particular device firmware, chipset, and chipset codes in use. A network report of the various distributed CPE units may then be prepared and presented by the report generation module1012. In such manner, operations personnel and technical staff may evaluate performance of the CPE devices and different equipment types as well as chipsets and firmware deployed within the network to provide enhanced technical performance and capabilities.

Referring toFIG. 11, a method of communicating the host-uniq tag is illustrated. A PPPoE (Point-to-Point over Ethernet) active discovery initiation (PADI) packet including a host-uniq tag from a DSL customer premise equipment (CPE) device is communicated to a broad-band remote access server (BRAS), at1102. A device identifier that includes a firmware identifier, a chipset identifier, and a chipset firmware code from the host-uniq tag is then retrieved for the particular DSL CPE identified, at1104. The DSL CPE device identifier is stored in a memory either locally or at an external database, at1106. A PPPoE active discovery offer (PADO) packet is then communicated to the DSL CPE, at1108. A PPPoE active discovery request (PADR) packet is communicated to the BRAS, at1110, and a PPPoE active discovery session confirmation (PADS) packet is communicated, at1112. The point-to-point connection is then established over the Ethernet between the DSL CPE and the BRAS, at1114.

Referring toFIG. 12, a method of retrieving and using the host-uniq tag that provides a CPE device identifier is illustrated. Device identity information from a DSL CPE is communicated to an equipment host, at1202. The DSL CPE device identity is then retrieved at a customer support terminal, at1204. The DSL CPE device identity is retrieved in an operations and technical support system and reports are prepared based on the DSL CPE device identity, at1206. A device type of the DSL CPE is then determined within the network based on the device identity, at1208, and surveys may be performed on the existing CPE devices within the network to determine suitability of such equipment with respect to updated technology deployments, at1210.

Thus, a system that uniquely identifies a device identity and equipment types including device firmware, chipset types, and chipset codes or firmwares for particular DSL CPE deployments may be retrieved from a variety of units deployed within a distributed network. A technical operations system customer service terminal may receive access to such device identifying information to provide for improved service and support of the network.