Message forwarding method, system, and relay agent device

US9331939B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9331939-B2
Application numberUS-201414444554-A
CountryUS
Kind codeB2
Filing dateJul 28, 2014
Priority dateMar 29, 2011
Publication dateMay 3, 2016
Grant dateMay 3, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

The present disclosure provides a message forwarding method and system, and a relay agent device. The forwarding method includes: receiving a first DHCPv6 message from a DHCPv6 client through a layer-3 interface; generating a Relay-forward message, where the first DHCPv6 message is encapsulated into the Relay-forward message and an identifier of the layer-3 interface is added therein; and sending the Relay-forward message to a DHCPv6 server.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for forwarding message, comprising: receiving, by a relay agent device, a first Dynamic Host Configuration Protocol for Internet Protocol version 6 (DHCPv6) packet from a user device through an interface on the relay agent device; generating, by the relay agent device, a Relay-forward message comprising a Relay-message Option, a first Interface-ID Option and a second Interface-ID Option, wherein both the first Interface-ID Option and the second Interface-ID Option are in compliance to Option 18 defined in Request For Comments (RFC) 3315, and the first and second Interface-ID Options are respectively in two separate fields of the Relay-forward message; wherein the Relay-message Option encapsulates the first DHCPv6 packet, the first Interface-ID Option indicates an identifier of a port on the relay agent device on which the first DHCPv6 packet is received, and the second Interface-ID Option indicates an identifier of the interface through which the first DHCPv6 packet is received; and sending, by the relay agent device, the Relay-forward message to a DHCPv6 server. 2. The method according to claim 1 , further comprising: receiving, by the relay agent device, a Relay-reply message from the DHCPv6server, wherein the Relay-reply message encapsulates a second DHCPv6 packet and the identifier of the interface; and forwarding, by the relay agent device, the second DHCPv6 packet to the user device according to the identifier of the interface. 3. The method according to claim 1 , wherein the relay agent device comprises an Access Node. 4. The method for forwarding message according to claim 1 , wherein the port is a physical port. 5. The method for forwarding message according to claim 1 , wherein the identifier of the interface is Virtual Local Access Network identifier (VLAN ID) of the interface on the relay agent device. 6. The method for forwarding message according to claim 1 , wherein the identifier of the interface is an Internet Protocol (IP) address of the interface on the relay agent device. 7. A relay agent device, comprising: a receiver, configured to receive a first Dynamic Host Configuration Protocol for Internet Procotol version 6 (DHCPv6) packet from a user device through an interface on the relay agent device; a processor coupled to the receiver, configured to generate a Relay-forward message comprising a Relay-message Option, a first Interface-ID Option and a second Interface-ID Option, wherein both the first Interface-ID Option and the second Interface-ID Option are in compliance with Option 18 defined in Request For Comments (RFC) 3315, and the first and second Interface-ID Options are respectively in two separate fields of the Relay-forward message; wherein the Relay-message Option encapsulates the first DHCPv6 packet, the first Interface-ID Option indicates an identifier of a port on the relay agent device on which the first DHCPv6 packet is received, and the second Interface-ID Option indicates an identifier of the interface through which the first DHCPv6 packet is received; and a transmitter coupled to the processor, configured to send the Relay-forward message to a DHCPv6 server. 8. The relay agent device according to claim 7 , wherein the relay agent device comprises an Access Node. 9. The relay agent device according to claim 7 , wherein the port is a physical port. 10. The relay agent device according to claim 7 , wherein the identifier of the interface is Virtual Local Access Network identifier (VLAN ID) of the interface on the relay agent device. 11. The relay agent device according to claim 7 , wherein the identifier of the interface is an Internet Protocol (IP) address of the interface on the relay agent device. 12. A system for forwarding message, comprising a relay agent device and a Dynamic Host Configuration Protocol for Internet Protocol version 6 (DHCPv6) server, wherein the relay agent device is configured to: receive a first DHCPv6 packet through an interface on the relay agent device; generate a Relay-forward message comprising a Relay-message Option, a first Interface-ID Option and a second Interface-ID Option, wherein both the first Interface-ID Option and the second Interface-ID Option are in compliance with Option 18 defined in Request For Comments (RFC) 3315, and the first and second Interface-ID Options are respectively in two separate fields of the Relay-forward message; wherein the Relay-message Option encapsulates the first DHCPv6 packet, the first Interface-ID Option indicates an identifier of a port on the relay agent device on which the first DHCPv6packet was received, and the second Interface-ID Option indicates an identifier of the interface through which the first DHCPv6 packet is received; and send the Relay-forward message to the DHCPv6 server; and the DHCPv6 server is configured to receive the Relay-forward message. 13. The system according to claim 12 , wherein the relay agent device comprises an Access Node. 14. The system for forwarding message according to claim 12 , wherein the port is a physical port. 15. The system for forwarding message according to claim 12 , wherein the identifier of the interface is Virtual Local Access Network identifier (VLAN ID) of the interface on the relay agent device. 16. The system for forwarding message according to claim 12 , wherein the identifier of the interface is an Internet Protocol (IP) address of the interface on the relay agent device.

Assignees

Inventors

Classifications

  • H04L45/74Primary

    Address processing for routing · CPC title

  • using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP] · CPC title

  • Electricity · mapped topic

  • Flow control; Congestion control · CPC title

  • Electricity · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9331939B2 cover?
The present disclosure provides a message forwarding method and system, and a relay agent device. The forwarding method includes: receiving a first DHCPv6 message from a DHCPv6 client through a layer-3 interface; generating a Relay-forward message, where the first DHCPv6 message is encapsulated into the Relay-forward message and an identifier of the layer-3 interface is added therein; and sendi…
Who is the assignee on this patent?
Huawei Tech Co Ltd
What technology area does this patent fall under?
Primary CPC classification H04L45/74. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 03 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).