WO2010081369A1

WO2010081369A1 - Method and system for obtaining identification information of peer client, peer client and access device

Info

Publication number: WO2010081369A1
Application number: PCT/CN2009/075841
Authority: WO
Inventors: 王妍; 陈国义; 李春秀
Original assignee: 华为技术有限公司
Priority date: 2009-01-17
Filing date: 2009-12-22
Publication date: 2010-07-22

Abstract

In the field of communication, a method for obtaining identification information of a peer client to locate the peer client is provided. The method obtains the identification information of the peer client by receiving and analyzing a message which carries the identification information of the peer client. The method resolves a location problem of the peer client effectively, so as to optimize the selection of peer sequences. A system for obtaining the identification information of the peer client, an access device and a peer client are also provided.

Description

Title of Invention: Method, system, and peer client, access device for obtaining peer client identification information

[1] This application claims the priority of the following two Chinese patent applications:

[2] Chinese Patent Application 1. Submitted to the Chinese Patent Office on January 17, 2009, the application number is 200910105098.6

The invention name is "method, system, and peer client, access device for obtaining peer-to-peer client identification information";

[3] Chinese patent application 2. Submitted to the Chinese Patent Office on April 10, 2009, application number is 200910127874.2

[4] The entire contents of the above-mentioned two Chinese patent applications are incorporated herein by reference.

[5] Technical field

The present invention relates to the field of communications, and in particular to the acquisition of peer (peer-to-peer) client identification information in P2P technology (Peer to Peer).

[7] Background of the invention

[8] At present, the Internet is a client/server approach. In this way, to set up a server on the Internet, the server can process data on the Internet to provide services to clients on the Internet. Information must be passed through the server. However, with the development of the network, the demand for large-capacity information such as music and video files is growing. The traditional client/server architecture restricts the transmission and sharing of network information.

[9] The emergence of P2P technology has broken the traditional client/server architecture. In a P2P network, there is no client or server concept, only equal peer nodes, and each peer acts as both a client and a server. Because P2P technology uses peer-to-peer computing and randomly selects peers, it not only makes full use of each peer's resources, but also speeds up the transmission and sharing of network resources, and greatly reduces the cost of servers.

[10] However, in the process of implementing the present invention, the inventors have found that in the prior art, the peer sequence cannot be located, resulting in a peer sequence (which may also be referred to as a P2P client sequence or a peer sequence). of The choice is unreasonable. For example, a Beijing-based user needs to exchange file fragments over a P2P network. Since the P2P technology randomly selects the peer sequence, the Beijing user is likely to exchange file fragments with the peer located abroad, which will generate excessive cross-domain traffic, and a large amount of network bandwidth is Occupied, resulting in degraded network performance.

[11] Summary of the invention

[12] In view of this, the embodiment of the present invention provides a method, a system, and a related device for acquiring peer client identification information, to locate a peer client.

[13] A method for obtaining peer-to-peer client identification information, including:

[14] The peer client receives the packet, and the packet carries the identification information of the peer client;

[15] The packet is parsed to obtain the identification information of the peer client carried in the packet.

[16] A peer client, including:

[17] The first receiving module is configured to receive a packet, where the packet carries the identifier information of the peer client; [18] a parsing module, configured to parse the packet received by the first receiving module, and obtain the packet The identification information of the peer client carried in the middle.

[19] An access device, comprising:

[20] The first information adding module is configured to add the identifier information of the peer client in the first DHCP message, where the first DHCP message is from the peer client;

[21] The second sending module is configured to provide the first DHCP message processed by the first information adding module to the DH

CP server;

[22] a third sending module, configured to provide a response from the DHCP server to the peer client, where

The response from the DHCP server carries the identification information of the peer client.

[23] A broadband remote access server, including:

[24] a second receiving module, configured to receive a first X bearer point-to-point protocol PPPoX message from the peer client;

[25] The third information adding module is configured to add the identifier information of the peer client in the second PPPoX packet, where the second PPPoX packet is the broadband remote access server The response of the first PPP oX message;

[26] The fifth sending module is configured to: carry the second PPPoX report that carries the identity information of the peer client The text is sent to the peer client.

[27] A system for obtaining peer-to-peer client identification information, including a peer client, an access device, and a D HCP server, where:

[28] The peer client is configured to communicate with the DHCP server through the access device, and obtain the identification information of the peer client by using the DHCP message relayed by the access device;

[29] The access device is configured to provide a relay for the communication between the peer client and the DHCP server, and add the identifier information of the peer client to the DHCP message.

[30] A system for obtaining peer-to-peer client identification information, including a peer client and a broadband remote access server, wherein

[31] the peer client is configured to communicate with the broadband remote access server, and obtain the identifier information of the peer client by using the PPPoX packet sent by the broadband remote access server;

[32] The broadband remote access server is configured to communicate with the peer client, and add the identifier information of the peer client to the PPPoX packet sent to the peer client.

[33] The beneficial effects of the embodiment of the present invention are that, by carrying the identifier information of the peer client in the packet, the peerif line can be quickly located, thereby optimizing the selection of the peer sequence.

[34] BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of a method for obtaining peer client identification information according to an embodiment of the present invention; [2] FIG. 2 to FIG. 9 are schematic diagrams of a peer client obtaining its own identifier through a DHCP packet. Schematic diagram of the process of information;

[0] FIG. 10 is a schematic diagram of a process for a peer client to obtain its own identification information through a PPPoE packet in the embodiment of the present invention;

FIG. 12 is a peer client according to an embodiment of the present invention;

FIG. 13 is a peer client according to still another embodiment of the present invention;

[40] FIG. 14 is an access device according to an embodiment of the present invention;

[15] FIG. 15 is an access device according to still another embodiment of the present invention;

[42] FIG. 16 is an access device according to still another embodiment of the present invention;

[43] FIG. 17 is an access device according to another embodiment of the present invention;

FIG. 18 is a broadband remote access server according to an embodiment of the present invention; FIG. FIG. 19 is a schematic diagram of a system for obtaining peer client identification information according to an embodiment of the present invention; [46] FIG. 20 to FIG. 26 are additional DHCP message options or multiplexing according to an embodiment of the present invention. Schematic diagram of the original DHCP message options;

FIG. 27 is a schematic diagram of another system for obtaining peer client identification information according to an embodiment of the present invention; [48] FIG. 28 to FIG. 29 are schematic diagrams of multiplexing original PPPoE packet labels according to an embodiment of the present invention; .

[49] Mode for carrying out the invention

The present invention will be further described in detail below with reference to the accompanying drawings.

[51] Each peer client belongs to an AS (Autonomous

System, autonomous system), belongs to a _peer collection, has certain location information, and has its own IP address. The peer set is a set of peers with the same attributes. For example, peers with similar geographical locations can be combined into one set, or peers in the same network segment can be combined into one set. Each set has a PID. (Peer-group Identification, peer-to-peer collection identifier).

In the embodiment of the present invention, the identifier information of the peer client is one or more of the following information: PI D, the ASID of the peer client (AS Identification), and the ISP to which the peer client belongs (internet) Service

Provider, Internet Service Provider) ID. In addition to the information, the peer client identification information may also include one or more of the following information: bandwidth between the peer client and the access device, COST between the peer client and the access device, and others. Identifies the information of the peer client.

As shown in FIG. 1 , FIG. 1 is a flowchart of a method for obtaining peer client identification information according to an embodiment of the present invention, including:

[54] 100. The peer client receives the packet, and the packet carries the identifier information of the peer client.

[55] Currently in the communication network, the Ethernet access method mainly includes DHCP (Dynamic Host

The configuration protocol, the dynamic host has set up a "node", PPPoE (Point-to-Point Protocol over Ethernet), etc. Among them, the DHCP server usually provides configuration information for each Internet host, such as dynamic Assigning an IP address, etc., is also commonly used in the network structure where the peer client is connected to the access device. PPPoE is an access mode for the user to access the network, and is a mature and easy-to-manage access mode. In practical applications, User access to the network for authorization is usually done by BRAS (Broadband Remote Access Server, Broadband Remote Access Server) to achieve. Therefore, in the embodiment of the present invention, the DHCP message and the PPPoE message can be used to carry the identifier information of the peer client. Certainly, the packet carrying the peer client identification information is not limited to the foregoing two types, and the packets of other protocols are also available, such as a Point to Point Protocol over ATM (PP to Point-to-Point Protocol) message, or A PPPoX packet such as a PPPoEo (Point to Point Protocol over Ethernet over ATM) packet. For convenience of description, the embodiment of the present invention uses a DH CP message and a PPPoE message as an example for description.

[56] In this embodiment, the identifier information of the peer client is a PID. Of course, in addition to the PID, the one or more of the following may be included: the ASID of the peer client, the bandwidth between the peer client and the access device, and the peer The COST (cost) between the client and the access device, and the ISP ID to which the peer client belongs. The PID can be the access device ID or the IP address of the access device.

[57] In the application scenario of the DHCP, the access device may be a relay device that provides a relay service between the DHCP server and the DHCP client. In the application scenario of the PPPoE, the access device may be a broadband remote access server. BRAS.

[58] 110. The peer client parses the packet to obtain the identifier information of the peer client carried in the packet.

[59] The peer client can obtain the identity information of the peer client by parsing the received packet.

[60] The following describes the situation in which the DHCP client and PPPoE packets carry peer client identification information.

[61] (1) When the packet carrying the peer client identification information is a DHCP packet:

[62] It can be understood that in this scenario, the DHCP message received by the peer client comes from the DHCP server (in the process of DHCP communication, the peer client is also the DHCP client). The DHCP packet may be forwarded from the DHCP server to the peer client through the access device. Therefore, the identification information of the peer client can be pre-configured in the access device. Here, the identification information of the peer client is configured in the access device, which can be either manual static configuration or automatic configuration of the access device. In the embodiment of the present invention, when there is a relay device between the peer client and the DHCP server, the identity information of the peer client is added to the DHCP packet by the access device.

[DHCP] For the DHCPv4, in the embodiment of the present invention, the DHCP message received by the peer client may be DHCP OFFER (provided) message, or a DHCP ACK (acknowledgement) message. Therefore, the peer client can obtain its own identity information through DHCP OFFER packets, or obtain its own identity information through DHCP ACK packets. The specific process of these two cases is introduced below.

[64] When the peer client obtains its own identity information through the DHCP OFFER packet, the specific process may be as shown in Figure 2:

[65] peer client sends DHCP

In the scenario of the present embodiment, the DHCP DISCOVER packet reaches the DHCP server through the relay of the access device. Therefore, when the access device receives the DHCP DISCOVER packet from the peer client, the identification information of the peer client is added to the DHCP DISCOVER packet, and the DHCP DISCOVER packet carrying the peer client identification information is relayed. Go to the DHCP server. In this way, when the DHCP server replies to the peer client with a DHCP OFFER packet, it will carry the identity information of the peer client. Therefore, the peer client obtains its own identification information through the DHCP OFFER packet.

[66] Of course, when the peer client obtains its own identity information through the DHCP OFFER packet, the specific process may also be the process shown in FIG. 3:

[67] The peer client sends a DHCP DISCOVER packet to the DHCP server through the relay of the access device; the DHCP server returns a DHCP OFFER packet to the DHCP server. When the DHCP OFFER packet passes through the access device, the access device connects the peer. The identification information of the client is added to the DHCP OFFER packet, and then the DHCP is added.

The OFFER packet is relayed to the peer client. In this process, the peer client also obtains its own identity information through the DHCP OFFER packet.

[68] When the peer client obtains its own identity information through the DHCP ACK packet, the specific process may be as shown in Figure 4:

[69] The peer client sends a DHCP REQUEST message or DHCP to the DHCP server.

The INFORM (Notification) message, when the DHCP REQUEST message or the DHCP INFORM message passes through the access device, the access device adds the identification information of the peer client to the DHCP REQUEST message or the DHCP INFORM message, and then The DHCP REQUEST message or DHCP INFORM message is relayed to the DHCP server. In this way, when the DHCP server replies DH to the peer client After the ACK packet is received, the identifier information of the peer client is carried. Therefore, the peer client obtains its own identification information through the DHC P ACK message.

[70] Of course, when the peer client obtains its own identity information through the DHCP ACK packet, the specific process may also be as shown in Figure 5:

[71] The peer client sends a DHCP REQUEST packet or a DHCP INFORM packet to the DHCP server through the relay of the access device. The DHCP server returns a DHCP ACK packet to the DHCP server. When the DHCP ACK packet passes through the access device, the DHCP client receives the DHCP ACK packet. The inbound device adds the identifier information of the peer client to the DHCP ACK packet, and then relays the DHCP ACK packet to the peer client. In this process, the peer client also obtains its own identification information through DHCP ACK packets.

For the DHCPv6, in the embodiment of the present invention, the DHCP message received by the peer client may be a DHCP ADVERTISE message or a DHCP REPLY message. Therefore, the peer client can obtain its own identification information through the DHCP ADVERTISE packet, or obtain its own identification information through the DHCP REPLY packet. The specific process of these two cases is described below.

[73] When the peer client obtains its own identity information through the DHCP ADVERTISE packet, the specific process can be as shown in Figure 6:

The peer client sends a DHCP SOLICIT packet. When the access device receives the DHCP SOLICIT packet from the peer client, the peer client adds the identity information to the DHCP client.

In the SOLICIT message, the message is encapsulated into a DHCP RELAY-FORWARD message and forwarded to the DHCP server. In this way, when the DHCP server replies to the peer client DHCP

The RELAY-REPLY message will carry the identification information of the peer client. When the receiving device receives the DHCP RELAY-REPLY packet from the DHCP server, the packet is encapsulated and sent as a DHCP ADVERTISE packet to the peer client. Therefore, the peer client obtains its own identification information through the DHCP ADVERTISE packet.

[75] Of course, when the peer client obtains its own identity information through the DHCP ADVERTISE message, the specific process may also be the process shown in Figure 7:

[76] The peer client sends a DHCP SOLICIT message, and after being relayed by the access device, the conversion is encapsulated into DHCP. The RELAY-FORWARD packet is sent to the DHCP server. The DHCP server returns a D HCP RELAY-REPLY packet to the peer client. After the DHCP RELAY-REPLY packet passes through the access device, the access device adds the identifier information of the peer client to the packet. In this article, and transform it into DHCP

The ADVERTISE packet is sent to the peer client. In this process, the peer client also obtains its own identification information through the DH CP ADVERTISE message.

[77] When the peer client obtains its own identity information through the DHCP REPLY packet, the specific process may be as shown in Figure 8:

[78] The peer client sends a DHCP REQUST packet or a DHCP INFORMATION-REQUEST packet. When the access device receives the DHCP REQUST packet or the DHCP INFORMATION-REQUEST packet from the peer client, the peer client adds the identifier information of the peer client. To the DHCP REQUST message or DHCP

In the INFORMATION-REQUEST packet, the packet is encapsulated into a DHCP RELAY-FORWARD packet and forwarded to the DHCP server. In this way, when the DHCP server replies to the peer client with a DHCP RELAY-REPLY packet, it will carry the identity information of the peer client. When the access device receives the DHCP RELAY-REPLY packet from the DHCP server, the packet is encapsulated into a DHCP REPLY packet and sent to the peer client, so that the peer client obtains its own identification information through the DHCP REPLY packet. .

[79] Of course, when the peer client obtains its own identity information through the DHCP REPLY packet, the specific process may also be the process shown in Figure 9:

[80] The peer client sends a DHCP REQUST packet or a DHCP INFORMATION-REQUEST packet. After being relayed by the access device, the translation is encapsulated into DHCP.

The RELAY-FORWARD packet is sent to the DHCP server. The DHCP server returns a D HCP RELAY-REPLY packet to the peer client. After the DHCP RELAY-REPLY packet passes through the access device, the access device adds the identifier information of the peer client to the packet. In this paper, the packet is encapsulated into a DHCP REPLY packet and sent to the peer client. In this process, the peer client also obtains its own identification information through the DHCP REPLY message.

[81] The following describes in detail the cases where the peer client obtains the identification information through DHCP packets. In the embodiment of the present invention, the identifier information of the peer client may be that the DHCP packet is sent from the peer client to the D client. During the process of the HCP server, the access device is added to the DHCP message, such as the scenarios shown in FIG. 2, FIG. 4, FIG. 6, and FIG. The ID of the peer client may be added to the DHCP packet by the access device, for example, as shown in FIG. 3, FIG. 5, FIG. 7, and FIG. Several scenarios.

[82] (2) When the packet carrying the peer client identification information is a PPPoE packet:

[83] According to the previous introduction, PPPoE is usually authorized by the user to access the network.

BRAS is implemented (in the PPPoE communication process, the peer client is also the PPPoE client). Therefore, the identification information of the peer client can be pre-configured in the BRAS. When the peer client communicates with the BRAS, the BRAS can add the identifier information of the peer client to the PPPoE packet and send it to the peer client, thereby making the peer client The terminal obtains the identification information through the PPPoE packet.

[84] In PPPoE

In the discovery phase, in the embodiment of the present invention, the PPPoE message received by the peer client may be a PADO (PPPoE Active Discovery Offer) packet, or may be a PADS (PPPoE Active Discovery Session-confirmation). , PPPoE activates discovery session confirmation) message. Therefore, the peer client can obtain its own identification information through PADO packets, or obtain its own identification information through PADS packets. The specific process of these two cases is introduced below.

[85] When the peer client obtains its own identification information through the PADO packet, the specific process may be as shown in Figure 10:

[86] The peer client sends a PADI (PPPoE Active Discovery Initialization) packet. In actual applications, multiple BRASs may receive the PADI packet. In the embodiment of the present invention, each BRAS that receives the PADI message adds the identification information of the peer client to the PADO message that is replied to the peer client. In this way, when the peer client receives PADO packets from multiple BRASs and selects one of the PADO packets, it can obtain its own identification information. It should be noted that, in the foregoing description, in the identification information of the peer client, the PID may be the identification information of the access device, such as the access device ID, or the IP address of the access device, and therefore, in this application scenario. The identification information of the peer client added by the different BRAS in the PADO message replied to the peer client may also be different.

[87] Of course, in the PPPoE Discovery phase, the peer client can also obtain its own through PADS packets. Identification information, the specific process may be the process shown in Figure 11:

The peer client sends PADI packets. In actual applications, multiple BRASs may receive the PADI packets. Each BRAS that receives the PADI message will reply to the peer client with a PADO message. The peer client selects a BRAS from multiple BRASs that reply to the PADO message and sends a unicast PADR (PPPoE).

The Active Discovery Request (PPPoE activates the discovery request) packet. The BRAS that receives the PADR packet adds the identification information of the peer client to the PADS packet that is replied to the peer client. In this way, when the peer client receives the PADS packet from the BRAS, it can obtain its own identification information. In the PPPoE Session (session) phase, it is mainly LCP (Link Control Protocol), authentication protocol, and NCP (Network Control Protocol).

Authentication Protocol, Password Authentication Protocol) and CHAP (Challenge-Handshake

[90] The same principle as the PPPoE Discovery phase, the process of providing identification information for the peer client can also be completed in the PPP Session phase. The BRAS can reply to the LCP packet or the authentication packet of the peer client (for example, the RAP packet). The identifier information of the peer client is added to the text and the NCP packet. When the peer client receives the packets from the BRAS, the peer client can obtain its own identification information.

[91] The following describes in detail the cases where the peer client obtains the identification information through DHCP packets and PPPoE packets. Regardless of the implementation manner, in the embodiment of the present invention, the peer client can obtain the identification information of the peer client.

[92] The method for obtaining the peer client identification information provided by the embodiment of the present invention, the peer client can obtain its own identification information in the process of communicating with the DHCP server or the BRAS. Therefore, when the peer client starts the P2P application, the acquired identity information is provided to the P2P application server. Therefore, after selecting the peer sequence for the peer client, the P2P application server can preferentially select the peer client in the same peer set as the peer client. Further, the identifier information of the peer client may further include an ASID. Therefore, if there is no suitable peer client in the same peer set, the range of the selection may be expanded, and the peer in the same autonomous system as the peer client may be selected. Client. Of course, other identification information and the like can also be referred to to determine the optimal peer sequence. P2P application server The peer sequence that is optimized and selected is sent to the peer client, and the peer client performs resource delivery and sharing with the peer client on the peer sequence.

[93] Of course, in this embodiment, when the peer client obtains the identification information through the DHCP packet, the access device and the DHCP server may be two different devices; in actual situations, the DHCP server may also be deployed. On the device. In this case, the embodiment can also be implemented in the same manner, and the basic principle is similar to the previous description, and is not mentioned here.

[94] It can be seen that the method for obtaining the peer client identification information provided by an embodiment of the present invention can quickly locate the peerit line, thereby optimizing the selection of the peer sequence.

Another embodiment of the present invention provides a peer client. As shown in FIG. 12, the peer client includes:

[96] The first receiving module 200 is configured to receive a packet, where the packet carries the identifier information of the peer client.

[97] The parsing module 210 is configured to parse the packet received by the first receiving module 200, and obtain the identifier information of the peer client carried in the packet.

[98] Further, as shown in FIG. 13, on the basis of the peer client shown in FIG. 12, the peer client provided by another embodiment of the present invention may further include:

[99] The first sending module 220 is configured to send the identifier information of the peer client acquired by the parsing module 210 to the P2P application server.

[100] In this embodiment, the packet carrying the peer client identification information may be a DHCP packet or a PPP oE packet. The DHCP packet can be: a DHCP OFFER packet, or a DHCP ACK packet, or a DHCP ADVERTISE packet, or DHCP.

REPLY message. The PPPoE packet can be a PADO packet, or a PADS packet, or an LCP packet, or an authentication packet, or an NCP packet.

[101] It can be seen that the peer client provided by one embodiment of the present invention can quickly locate the peer

, thus providing information for the P2P application server to optimize the selection of the peer sequence.

[102] A further embodiment of the present invention provides an access device. As shown in FIG. 14, the access device includes: [103] a first information adding module 300, configured to be first in a peer client. Add the identifier information of the peer client to the DHCP packet.

[104] The second sending module 310 is configured to: submit the first DHCP message that is processed by the first information adding module 300. Supply to a DHCP server;

[105] The third sending module 320 is configured to provide a response from the DHCP server to the peer client, where the

The response of the DHCP server carries the identification information of the peer client.

[106] Optionally, on the basis of the access device shown in FIG. 14, in another embodiment of the present invention, as shown in FIG. 15, the second sending module 310 includes:

[107] The forwarding unit 311 is configured to directly forward the first DHCP message processed by the first information adding module 300 to the DHCP server.

[108] The third sending module 320 includes:

[109] The response unit 321 is configured to send the second DHCP message from the DHCP server to the peer client, where the second DHCP message is a response of the DHCP server to the first DHCP message, and the second DHCP message is carried. There is identification information of the peer client.

[110] Optionally, on the basis of the access device shown in FIG. 14, in another embodiment of the present invention, as shown in FIG. 16, the second sending module 310 includes:

[111] The packet forwarding unit 312 is configured to encapsulate the first DHCP message processed by the first information adding module 300 into a third DHCP message, and send the third DHCP message to the DHCP server.

[112] The third sending module 320 includes:

[113] The encapsulating response unit 322 is configured to encapsulate the fourth DHCP message from the DHCP server into a fifth DHC P message, and send the fifth DHCP message to the peer client. The fourth DHCP message is DHCP. The server responds to the third DHCP message, and the fourth DHCP message carries the identification information of the peer client.

[114] A further embodiment of the present invention provides an access device. As shown in FIG. 17, the access device includes: [115] a second information adding module 400, configured to be in the sixth from the DHCP server. Add the identification information of the peer client in the DHCP message;

[116] The fourth sending module 410 is configured to directly forward the sixth DHCP packet processed by the second information adding module 400 to the peer client, or the sixth DHCP packet processed by the second information adding module 400. The packet is encapsulated into a seventh DHCP packet, and the seventh DHCP packet is sent to the peer client.

The access device provided by the embodiment of the present invention can provide the peer client with identification information during the communication process between the peer client and the DHCP server, so that the peer client can quickly locate the peer® line. [118] A further embodiment of the present invention provides a broadband remote access server, as shown in FIG. 18, including:

[119] The second receiving module 500 is configured to receive a first PPPoE packet from the peer client.

[120] The third information adding module 510 is configured to add the identifier information of the peer client in the second PPPoE packet.

The second PPPoE packet is a response of the broadband remote access server to the first PPPoE packet. [121] The fifth sending module 520 is configured to send the second PPPoE packet carrying the identifier information of the peer client to the second PPPoE packet. The peer client.

[122] A further embodiment of the present invention provides a system for obtaining peer client identification information, as shown in FIG. The system includes a peer client, an access device, and a DHCP server, where:

[123] The peer client is configured to communicate with the DHCP server through the access device, and obtain the identifier information of the peer client by using the DHCP message relayed by the access device.

[124] The access device is configured to provide a relay for the communication between the peer client and the DHCP server, and add the identification information of the peer client in the DHCP message.

In the embodiment of the present invention, the access device adds the identifier information of the peer client to the DHCP packet, and may add an Option (option) to the DHCP packet, or may reuse the original Option. .

[126] For example, for DHCPv4, an Option can be added to a DHCP message to carry the identity information of the peer client. The Option format can include fields such as Code, Len, and Value. Code and Len are both 1 byte length, Code identifies the type value of the option; Len identifies the length of the Option, that is, the total length of the Option including Code, Len, and Value fields; Value identifies the Option to carry Information, ie ASID, PID and other identification information. In an embodiment of the present invention, the format of the Option may be as shown in FIG.

[127] In this format, the Value value is divided into 4-byte units, which store the ASID, PID, bandwidth value between the peer client and the access server, COST value, and peer of the peer client's ISP ID. The identification information of the client, the embodiment of the present invention does not limit the specific storage order. Since the ASID and PID can use the format of the IP address, the bandwidth value or COST value between the peer client and the access server can also be stored in the 4-byte format of the IP address, and the 4-byte length can satisfy the maximum value. Requirements.

[128] Of course, in the actual situation, the identification information of the peer client may not be uniformly expressed in a 4-byte format. Therefore, the Option may use the format shown in FIG. 21. The Value field carries multiple sub-options, and each sub-option stores different identification information, and the code value corresponding to each sub-option can be Pre-defined or negotiated. In this case, the sub-option may be in the format as shown in FIG.

[129] Of course, the embodiment of the present invention can also be implemented by multiplexing the original Option in the DHCP message. For example, the original Vendor Specific Information Option in the DHCP message is reused. The format is basically similar to the case of Fig. 21 and Fig. 22 described above, and will not be described here.

[130] For DHCPv6, an Option can also be added to the DHCP message to carry the identity information of the peer client. This option includes fields such as opt-code, option-len, and option-data. The opt-code field identifies the type value of the option, the option-len identifies the length of the option including the opt-code, option-len, and option-data fields, and the option-data identifies the information carried by the option, that is, A. SID, PID and other identification information. In an embodiment of the present invention, the format of the Option may be as shown in FIG.

[131] In this format, the option-data value is divided into 16-byte units, which store the ASID, PID, bandwidth value between the client and the access server, the COST value, and the ISP to which the peer client belongs. Peer client identification information such as ID, and embodiments of the present invention do not limit the specific storage order. Since the format of information such as ASID and PID is generally less than 16 bytes in length, in order to maintain consistency, the 16-byte format is used; and the bandwidth value or COST value between pe e _r and the access server can also use the IP address. The 16-byte format is stored, so the length of 16 bytes can fully meet the maximum requirement.

[132] Of course, similar to the case of DHCPV4, the identification information of the peer client may not be uniformly expressed in a 16-byte format. Therefore, option-data can still be stored in an indefinite format. As shown in Figure 24. The option-data field carries multiple sub-options, and each sub-option stores different identification information, and the opt-code value corresponding to each sub-option can be predefined or negotiated. In this case, the suboption can be in the format shown in Fig. 25.

[133] In DHCPv6, you can also reuse existing options, such as the Vendor Specific Information Option, as shown in Figure 26. In this case, the various identification information of the peer client is carried by the option-data field, and the enterprise-number field can be filled in with a specific default value, which can be determined according to the specific implementation. Similarly, the l-n byte option-data field can be represented by multiple sub-options, and the opt-code value corresponding to each sub-option can be predefined or negotiated. The format of the specific sub-options is similar to the situation described in Figure 25 above, and is not mentioned here.

[134] In another embodiment of the present invention, another system for obtaining peer client identification information is provided, as shown in FIG. 27 As shown, the system includes a peer client and a broadband remote access server, where:

[135] The peer client is configured to communicate with the broadband remote access server, and obtain the identification information of the peer client by using the PPPoE packet sent by the broadband remote access server;

[136] Broadband remote access server, used to communicate with the peer client and sent to the peer client.

Add the identification information of the peer client to the PPoE packet.

[137] It can be known to those skilled in the art that PPPoE packets are encapsulated in an Ethernet frame format, and the payload portion of PPPoE can be formatted as shown in FIG. Where VER field is 4 bytes, TYPE field is 4 bytes, CO

The DE field is 8 bytes, the SESSION_ID field is 16 bytes, and the LENGTH field is 16 bytes. CODE can identify different messages, for example: in PPPoE

In the Discovery phase, the PADI message is 0x09, the PADO message is 0x07, the PADR message is 0x19, and the PAD S message is 0x65. In the PPPoE Session phase, the CODE is set to 0x00. SESSION_ID identifies a different session and is a fixed value for a given session. LENGTH identifies the PAYLOAD length of PPPoE (excluding the length of the Ethernet header and PPPoE header).

[138] Among them, the PAYLOAD part of the PPPoE message contains 0 or more TAGs. Therefore, in the embodiment of the present invention, the broadband remote access server adds the identity information of the peer client to the PPPoE packet, and may add a TAG to the PPPoE packet or multiplex the original TAG.

[139] Reuse the original TAG as shown in Figure 29. The TAG can include fields such as TAG_TYPE, TAG_LEN GTH, and TAG-VALUE. Where TAG_TYPE identifies the type value of the TAG; TA G-LENGTH

The length of the TAG is identified, and in the TAG_VALUE, the peer ID information such as the ASID, the PID, the bandwidth value or the COST value between the peer client and the access server may be stored, and the embodiment of the present invention does not perform the specific storage order. limit. The more common, reusable TAGs are: Vendor-Specific TAG, Relay-Session-Id TAG, etc.

[140] The method of adding a TAG to carry the peer client identification information is similar to the above method, and is not mentioned here.

Through the description of the above embodiments, those skilled in the art can clearly understand that the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on the understanding, the technical solution of the embodiment of the present invention may be in the form of a software product. The computer software product can be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including instructions for causing a computer device, or server, or other network device to perform various embodiments of the present invention or The method described in certain sections of the examples.

The above are only the preferred embodiments of the present invention and are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

[Claim 1] A method for obtaining the identity information of the peer client, the method comprising: receiving, by the peer client, the packet, where the packet carries the identification information of the peer client;

Parsing the packet, and obtaining the identifier of the peer client carried in the packet

Ι π Λ∑! ,.

[Claim 2] The method according to claim 1, wherein the identification information of the peer client includes at least one of the following information: an autonomous system identifier to which the peer client belongs, the pair The peer set identifier to which the peer client belongs, and the Internet service provider ID to which the peer client belongs.

[Claim 3] The method according to claim 2, wherein the identification information of the peer client further includes at least one of the following information:

The bandwidth between the peer client and the access device, and the cost COST between the peer client and the access device.

[Claim 4] The method according to claim 2 or 3, wherein the message is a dynamic host configuration protocol DHCP message, or X carries a point-to-point protocol PPPoX message; when the message is DHCP The DHCP message is: a DHCP OFFER message, or a DHCP ACK message, or a DHCP ADVERTISE message, or a DHCP REPLY message;

When the packet is an Ethernet bearer point-to-point protocol PPPoE packet in the PPPoX packet, the PPPoE packet is: PPPoE activation discovery provides PADO packet or PPPoE activation discovery session confirmation PADS packet, or data Link control protocol LCP message, or authentication message, or network control protocol NCP packet.

[Claim 5] The method according to claim 4, wherein, when the packet is a DHCP packet, the identifier information of the peer client is carried in a new option of the DHCP packet, or The original option of the DHCP message is carried; when the message is a PPPoX message, the identity information of the peer client is carried in the newly added TAG of the PPPoX message, or is carried in the PPPoX The original TAG of the message. The method of claim 1 or 2 or 3, further comprising: providing the peer-to-peer client identification information to the peer when the peer client initiates a point-to-point P2P application P2P application server.

A peer-to-peer client, comprising:

a first receiving module, configured to receive a packet, where the packet carries identifier information of the peer client;

The parsing module is configured to parse the packet received by the first receiving module, and obtain the identifier information of the peer client carried in the packet.

The peer client according to claim 7, wherein the peer client further includes:

The first sending module is configured to send the identifier information of the peer client acquired by the parsing module to the point-to-point P2P application server.

An access device, comprising:

a first information adding module, configured to add, to the first dynamic host configuration protocol, the DHCP message, the identifier information of the peer client, where the first DHCP message is from the peer client;

a second sending module, configured to provide the first DHCP message processed by the first information adding module to a DHCP server;

And a third sending module, configured to provide a response from the DHCP server to the peer client, where the response carries the identifier information of the peer client.

The access device according to claim 9, wherein the second sending module comprises:

a forwarding unit, configured to forward the first DH CP packet processed by the first information adding module to the DHCP server directly;

The third sending module includes:

a response unit, configured to send a second DHCP message from the DHCP server to the peer client, where the second DHCP message is the DHCP server that is configured by the DHCP server In response, the second DHCP message carries the pair The identification information of the client.

[Claim 11] The access device according to claim 9, wherein the second sending module comprises:

a packet forwarding unit, configured to encapsulate the first DHCP message processed by the first information adding module into a third DHCP message, and send the third DHCP message to the DHCP server;

The third sending module includes:

The encapsulating response unit is configured to encapsulate the fourth DHCP message from the DHCP server into a fifth DHCP message, and send the fifth DHCP message to the peer client; The DHCP message is the response of the DHCP server to the third DHCP message, and the fourth DHCP message carries the identity information of the peer client.

[Claim 12] A broadband remote access server, comprising:

a second receiving module, configured to receive a first X bearer point-to-point protocol PPPoX message from the peer client;

a third information adding module, configured to add the identifier information of the peer client in the second PPPoX packet, where the second PPPoX packet is the broadband remote access server to the first The second sending module is configured to send the second PPPoX packet carrying the identifier information of the peer client to the peer client.

[Claim 13] A system for obtaining peer-to-peer client identification information, comprising: a peer client, an access device, and a DHCP server, wherein:

The peer client is configured to communicate with the dynamic host configuration protocol DHCP server by using the access device, and obtain the identifier of the peer client by using the DHCP message relayed by the access device. Information

The access device is configured to provide a relay for the communication between the peer client and the DHCP server, and add the identifier information of the peer client in the DHCP message. [Claim 14] A system for obtaining peer-to-peer client identification information, comprising: a peer-to-peer client and a broadband remote access server, wherein

The peer client is configured to communicate with the broadband remote access server, and obtain the identifier information of the peer client by using the PPPoX packet sent by the broadband remote access server;

The broadband remote access server is configured to communicate with the peer client, and add the identifier information of the peer client to the PPPoX packet sent to the peer client.