IPC분류정보
국가/구분 |
United States(US) Patent
등록
|
국제특허분류(IPC7판) |
|
출원번호 |
UP-0169417
(2005-06-29)
|
등록번호 |
US-7602778
(2009-10-28)
|
발명자
/ 주소 |
- Guichard, James N.
- Davie, Bruce S.
- Rosen, Eric C.
- Mullooly, John J.
- Wieser, Gerhard
|
출원인 / 주소 |
|
대리인 / 주소 |
Brinks Hofer Gilson & Lione
|
인용정보 |
피인용 횟수 :
31 인용 특허 :
5 |
초록
▼
An MPLS router operable for labeled switch path (LSP) operation defines a compression index for identifying a decompression context between other MPLS LSP routers. The compression index allows a multipoint-to-point link between MPLS routers, thereby avoiding an exhaustive mesh of point-to-point link
An MPLS router operable for labeled switch path (LSP) operation defines a compression index for identifying a decompression context between other MPLS LSP routers. The compression index allows a multipoint-to-point link between MPLS routers, thereby avoiding an exhaustive mesh of point-to-point links between each of the MPLS routers. The originator ID identifies each of the multipoint originating endpoints at a common destination, and maintains the context of each compressed header to match incoming compressed headers to the corresponding header values. The originator ID, typically the IP address of the originator, operates as the compression index on the multipoint-to-point connection, operable to distinguish multiple originators of the multipoint-to-point connection and provide header compression for each.
대표청구항
▼
What is claimed is: 1. A method for transporting message packets across a multipoint-to-point network, the method comprising: compressing a message header of a message in a set of messages, the messages defined as packets, the compression operable for identifying deterministic fields recreatable in
What is claimed is: 1. A method for transporting message packets across a multipoint-to-point network, the method comprising: compressing a message header of a message in a set of messages, the messages defined as packets, the compression operable for identifying deterministic fields recreatable in successive messages; determining a context ID indicative of the compressed message header; computing a originator ID, the originator ID indicative of an originator of the set of messages on a multipoint-to-point link, the originator ID being operable to distinguish decompression context for the set of messages originating from the originator from decompression context for messages originating from other originators on the multipoint-to-point link; appending the context ID and the originator ID to each of the messages in the set; sending a first message of the set, the first message having the originator ID, context ID and corresponding uncompressed header fields; and sending successive messages with the originator ID and the context ID, the originator ID and context ID collectively operable to indicate the originator of the message and the compression header context, sending the successive messages further comprising: omitting a destination based header field from the message header, the destination based header field operable for destination based routing; and routing the packet based on a label indicative of particular router hops independent of the destination, such that the packet is not decompressed to determine routing information before the packet reaches the destination. 2. The method of claim 1 further comprising: receiving the label from a destination, the label indicative of the compressed nature of the header; and appending the label to each of the messages in the set. 3. The method of claim 2 wherein computing the originator ID further comprises determining the label, the label corresponding to the multipoint-to-point link, the determined label operable to indicate the routing path along the multipoint-to-point link. 4. The method of claim 1 further comprising inserting a compression label indicative of the compressed nature of the header, the compression label recognizable by the receiver, the receiver responsive to the compression label for performing header decompression. 5. The method of claim 4 further comprising: identifying a particular type of compression to be performed; and selectively appending a compression label based on the type of compression to be performed. 6. The method of claim 4 wherein the compression label is indicative of the ability of the sender to employ header compression, further comprising defining a packet type indicator indicative of a type of header compression in packets accompanying the appended compression label. 7. The method of claim 6 further comprising storing the packet type indicator in a preexisting field in the compressed header. 8. A method for sending messages having compressed message headers comprising: identifying compressible header fields in a message header; and associating the compressible header fields with a context ID; identifying a set of messages, the set of messages adapted for header compression via a compression context; assembling a compressed message header having an originator ID, the originator ID corresponding to a sender of a message; sending the message via a multipoint-to-point link, the originator ID operable to distinguish the sender of the message from other senders over the multipoint-to-point link; and decompressing the message header of the message using the originator ID, the originator ID operable to distinguish decompression context for messages originating from the sender from decompression context for messages originating from other senders on the multipoint-to-point link, sending the message further comprising: sending the message with a context ID corresponding to the compression context, the context ID and originator ID operable to distinguish the set of messages in the compression context from other messages; omitting a destination based header field from the compressed message header, the destination based header field operable for destination based routing; and routing the message based on a label indicative of particular router hops independent of the destination, such that the message does not have to be decompressed prior to determine routing information before the message reaches the destination. 9. The method of claim 8 wherein sending further comprises sending via a labeled path indicative of the recipient of the multipoint-to-point link, the labeled path defined according to operative from a predetermined protocol adapted for identifying a routing path. 10. The method of claim 9 where the multipoint-to-point link is a label switched path (LSP) indicative of intermediate routing hops through the network. 11. A method of compressing message headers over a multipoint-to-point link comprising: identifying a set of messages adaptable for header compression, adaptable messages having headers with deterministic information predictable from a predecessor message from the set of messages; associating the deterministic information with a context ID, the context ID indicative of the header information for each of the messages in the set of messages; appending the context ID to each of the messages in the set of messages; inserting an originator identifier, indicative of the sender of the message, in a message header having the context ID, the combination of the originator identifier and the context ID operable to distinguish decompression context for messages originating from the sender from decompression context for messages originating from other senders on the multipoint-to-point link; omitting a destination based header field from the message header, the destination based header field operable for destination based routing; and routing the packet based on a label the label indicative of particular router hops independent of the destination, such that the packet does not have to be decompressed prior to determine routing information before the packet reaches the destination, wherein the sender is a first sender, the method further comprising a second sender operable to access the multipoint-to-point link, the second sender having a second set of messages adapted for header compression via the multipoint-to-point link, and identifying compressible header fields of the second set of messages; building a header corresponding to the second set of messages; computing a context ID indicative of the compressed header information; and determining an originator ID indicative of the second sender, wherein the context ID and the originator ID are different from the context ID and originator ID of the set of messages sent by the first sender. 12. The method of claim 11 further comprising: computing a compression label field, the compression label field indicative of the compressed nature of the header and the type of uncompression to be performed; and appending the compression label field to the messages in the set of messages, the compression label indicative of the header compression performed and operable to inform the receiver of corresponding decompression to be applied. 13. The method of claim 11 wherein the compression label is indicative of the ability of the sender to employ header compression, further comprising defining a packet type indicator indicative of a type of header compression in packets accompanying the appended compression label. 14. The method of claim 11 further comprising: omitting a destination based header field, the destination based header field operable in conjunction with a routing table for computing a sequence of hops via table lookup; appending a path label indicative of at least one specific router, the path label operable to define the path through the network to the destination; and employing the path label at each hop across the network, the path label obviating a routing lookup and enabling the compressed header for transport across the entire path to the destination. 15. A method of receiving header compressed messages over a multipoint-to-point link comprising: receiving a message header indicative of a set of messages, the set of messages defined as packets and adapted for header compression via a compression context, the message header having deterministic information applicable to the set of messages; identifying, from the message header, a context ID corresponding to the compression context and an originator ID, the compression context and originator ID indicative of the header information, the context ID and originator ID operable to distinguish the set of messages in the compression context from other messages; omitting a destination based header field from the message header, the destination based header field operable for destination based routing; routing the packet based on a label, the label indicative of particular router hops independent of the destination, such that the packet does not have to be decompressed prior to determine routing information before the packet reaches the destination; and decompressing the message header using the compression context and the originator ID to retrieve the header information, the originator ID operable to distinguish decompression context for messages originating from an originator from decompression context for messages originating from other originators on the multipoint-to-point link, the compression context indicative of the deterministic information applicable to the set of messages. 16. The method of claim 15 further comprising: receiving a compression label field, the compression label field indicative of the compressed nature of the header and the type of uncompression to be performed; and identifying, from the compression label field in received compressed headers, a compression label indicative of the compressed nature of the header and the type of uncompression to be performed. 17. A data communications device for transporting message packets comprising: a processor operable to execute instructions; a network interface responsive to the processor for performing the instructions, a memory coupled to the processor operable to store encoded instructions executable by the processor, the encoded instructions operable for: compressing a message header of a message in a set of messages, the messages defined as packets, the compression operable for identifying deterministic fields recreatable in successive messages; determining a context ID indicative of the compressed message header; computing a originator ID, the originator ID indicative of the originator of the set of messages; appending the context ID and the originator ID to each of the messages in the set; sending a first message of the set, the first message having the originator ID, context ID and corresponding uncompressed header fields; and sending successive messages with the originator ID and the context ID, the originator ID and context ID collectively operable to indicate the originator of the message and the compression header context, sending the successive messages further comprising: omitting a destination based header field from the message header, the destination based header field operable for destination based routing; and routing the packet based on a label indicative of particular router hops independent of the destination, such that the packet does not have to be decompressed to determine routing information before the packet reaches the destination, wherein the processor is further operable to compute the originator ID by determining a label corresponding to a multipoint-to-point link, the originator ID operative to identify a source of the multipoint-to-point link and the determined label operable to indicate the routing path along the multipoint-to-point link. 18. The data communications device of claim 17 wherein: the interface is operable to receive a label from a destination, the label indicative of the compressed nature of the header; and the processor is operable to append the label to each of the messages in the set. 19. The data communications device of claim 17 wherein the memory further comprises instructions for: omitting a destination based header field from the message header, the destination based header field operable for destination based routing; and routing the packet based on a label field, the label indicative of particular router hops independent of the destination. 20. The method of claim 17 where the multipoint-to-point link is a label switched path (LSP) having a label operative indicative of intermediate routing hops through the network. 21. A computer program product having a computer readable storage medium operable to store computer program logic embodied in computer program code that, when executed by a processor, perform a method for sending messages having compressed message headers comprising: identifying compressible header fields in a message header; and associating the compressible header fields with a context ID; identifying a set of messages, the set of messages adapted for header compression via a compression context; assembling a compressed message header having an originator ID, the originator ID corresponding to the sender of the message; sending the message via a multipoint to point link, the originator ID operable to distinguish decompression context for the set of messages originating from the sender from decompression context for messages originating from other senders on the multipoint-to-point link, sending occurring via a labeled path indicative of the recipient of the multipoint-to-point link, the labeled path defined according to a predetermined protocol adapted for identifying a routing path, sending the message further comprising: sending the message with a context ID corresponding to the compression context, the context ID and originator ID operable to distinguish the set of messages in the compression context from other messages; omitting a destination based header field from the compressed message header, the destination based header field operable for destination based routing; and routing the packet based on a label indicative of particular router hops on the identified routing path independent of the destination, such that the packet does not have to be decompressed prior to determine routing information before the packet reaches the destination; and computer program code for decompressing the message header of the message using the originator ID, the originator ID indicative of a decompression context applicable to a set of messages. 22. A method for header compression in a label switched path (LSP) network comprising: receiving a message in a set of messages, the message being a Real Time Protocol message that includes an multi protocol label switching label; compressing a message header of the message in the set of messages, the compression applied to deterministic fields recreatable in successive messages, to generate a compressed message header; determining a context ID indicative of the compressed message header; computing an originator ID, the originator ID indicative of an originator of the set of messages and operable to distinguish decompression context for messages originating from the originator from decompression context for messages originating from other originators on the multipoint-to-point link; appending the context ID and the originator ID to each of the messages in the set; computing a predetermined label switched path (LSP), the LSP defining a path through the network; and transmitting each message in the set of messages on the computed LSP independently of routing information in the compressed header fields, the LSP routing avoiding intermediate decompression to identify the destination, transmitting via the LSP further including sending a first message of the set, the first message having the originator ID, context ID and corresponding uncompressed header fields; and sending successive messages with the originator ID and the context ID, the originator ID and context ID collectively operable to indicate the originator of the message and the compression header context such that the uncompressed header fields are omitted, sending successive messages further comprising omitting a destination based header from the message header, the destination based header field operable of destination based routing. 23. The method of claim 22 further comprising computing a compression label for distinguishing each message in the set of messages as an LSP message employing compression, and transmitting each message with the computed compression label.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.