Source: http://www.google.com.tw/patents/US7817636
Timestamp: 2013-05-25 14:18:54
Document Index: 577710160

Matched Legal Cases: ['Application No. 257', 'Application No. 05820894', 'application No. 200580031604', 'Application No. 05820894', 'Application No. 200580045932', 'application No. 200580031604', 'Application No. 200580045932']

�M�Q US7817636 - Obtaining information on forwarding decisions for a packet flow - Google �M�Q�j�M �Ϥ� �a�� Play YouTube �s�D Gmail ���ݵw�� ��h »�i���M�Q�j�M | �������� | �n�J�i���M�Q�j�M�M�QIn one embodiment, an apparatus comprises one or more forwarding logic components and logic coupled to a plurality of network interfaces. The logic is operable to: receive address information that identifies a packet flow; generate a synthetic packet based on the address information; provide the synthetic...http://www.google.com.tw/patents/US7817636?utm_source=gb-gplus-share�M�Q US7817636 - Obtaining information on forwarding decisions for a packet flow���}��US7817636 B2�X���������v�ӽЮѽs��12/054,287�o�G���2010�~10��19���ӽФ��2008�~3��24�� �u���v���2008�~1��30����L���}�M�Q��US20090190591�o��HGanesh Chennimalai Sankaran��M�Q�v�HCisco Technology, Inc. ���M�Q������370/392709/235370/352709/218370/394370/389709/239��ڱM�Q������H04L12/56 �X�@����H04L45/00H04L47/20H04L47/10H04L47/2441H04L45/38 �ڬw������H04L45/00H04L47/10H04L45/38H04L47/20H04L47/24D�ѦҤ��m�M�Q�ޥ� (108)�D�M�Q�ޥ� (22)�~���s�����M�Q�ӼЧ� ���M�Q�ӼЧ��M�Q����T�� �ڬw�M�Q��Obtaining information on forwarding decisions for a packet flowUS 7817636 B2�K�n In one embodiment, an apparatus comprises one or more forwarding logic components and logic coupled to a plurality of network interfaces. The logic is operable to: receive address information that identifies a packet flow; generate a synthetic packet based on the address information; provide the synthetic packet to the one or more forwarding logic components; retrieve forwarding information that indicates one or more forwarding decisions for the synthetic packet made by the one or more forwarding logic components; and report the forwarding information. Each of the one or more forwarding logic components is operable to make a forwarding decision for the synthetic packet as part of processing packets in the packet flow, and to store, as part of the forwarding information, data indicating the forwarding decision for the synthetic packet that is made by that forwarding logic component.
PRIORITY CLAIM This application claims the benefit of priority under 35 U.S.C. ��119 from India Patent Application No. 257/DEL/2008, entitled ��OBTAINING INFORMATION ON FORWARDING DECISIONS FOR A PACKET FLOW,�� filed by Ganesh Chennimalai Sankaran on Jan. 30, 2008, the entire contents of which is hereby incorporated by reference for all purposes as if fully set forth herein.
5.1 Structural Details 5.2 Functional Details 6.0 Implementation Mechanisms�XHardware Overview 7.0 Extensions and Alternatives 1.0 General Overview Obtaining information on forwarding decisions for packet flows is described. In one embodiment, an apparatus comprises a plurality of network interfaces, one or more forwarding logic components coupled to the plurality of network interfaces, and logic coupled to the plurality of network interfaces. The plurality of network interfaces are operable to communicatively connect to one or more packet-switched networks. The logic is encoded in one or more tangible media and is operable to: receive address information that identifies a packet flow, where the packet flow is received at an incoming network interface and is to be forwarded through an outgoing network interface; generate a synthetic packet based on the address information, where the synthetic packet includes header data indicating that the synthetic packet is not to be forwarded to any next-hop network element; provide the synthetic packet to the one or more forwarding logic components; retrieve forwarding information that indicates one or more forwarding decisions for the synthetic packet made by the one or more forwarding logic components; and report the forwarding information. The one or more forwarding logic components are encoded in one or more tangible media and are operable to receive packet flows and to forward the packet flows. In addition, each forwarding logic component is operable to: make a forwarding decision for the synthetic packet as part of processing packets in the packet flow; and store, as part of the forwarding information, data indicating the forwarding decision for the synthetic packet that is made by that forwarding logic component.
As used herein, ��network infrastructure element�� (also referred to hereinafter as ��network element��) refers to a networking device that is operable to manage network traffic transmitted in one or more networks. Typically, a network element is operable to receive packets on network interfaces communicatively connected to other network elements, make a routing or forwarding decision regarding the received packets, and transmit the received packets on the network interfaces based on the forwarding decision. Examples of network elements include, but are not limited to, routers, switches, bridges, and hubs.
As used herein, ��packet flow�� refers to a sequence of packets that are sent from a particular source to a particular destination. The packets in a packet flow may be sent from a source to a destination over a variety of protocols including, but not limited to, Layer 2 data link protocols (e.g., Frame Relay protocol), Layer 3 network protocols (e.g., the Internet Protocol (IP)), and a variety of other protocols that may be tunneled over an IP protocol (e.g., protocols that are supported by a Multi-Protocol Label Switching (MPLS) architecture). Further, the packets in a packet flow may carry data units of one or more Layer 4-Layer 7 protocols including, but not limited to, transport layer protocols (e.g., Transmission Control Protocol (TCP) and User Datagram Protocol (UDP)), and application layer protocols (e.g., Hypertext Transfer Protocol (HTTP) and Simple Network Management Protocol (SNMP)).
The techniques described herein provide for logic that is operable to receive address information that identifies a packet flow. As used herein, ��address information�� refers to a set of data that collectively identifies a packet flow that is sent from a particular source to a particular destination. In various embodiments, the logic at a network element may receive through various mechanisms address information that identifies packet flows processed by the network element. Examples of such mechanisms include, without limitation, Command Line Interface (CLI) commands submitted by a user logged in at the network element and SNMP messages that are sent from SNMP management stations to an SNMP agent executing on the network element. In addition, in various embodiments the logic may respond to user requests submitting address information as well as to requests with address information sent by automatic diagnostic utilities. The techniques described herein are not in any way limited to receiving address information identifying packet flows from any particular type of entity or through any particular type of mechanism, logic, module or component.
In some embodiments, the address information that identifies a packet flow may include an identifier of the incoming interface on which the packet flow is received at the network element being diagnosed. Depending on the type and architecture of the network element, the incoming interface identifier may indicate the number and type of the interface. For example, the identifier ��GigabitEthernet3/16�� may indicate the third of sixteen interfaces that operate over a gigabit Ethernet protocol, the identifier ��EOBC0/0�� may indicate an interface that operates over an Ethernet Out-of-Band channel, and the identifier ��Port-channel1.2�� may indicate the second logical interface of a particular EtherChannel interface that comprises multiple physical interfaces with common network address. Identifying a packet flow through an incoming network interface provides for diagnosing whether a multi-homed network element (e.g., a network element that is configured to receive packet flows from the same source on multiple incoming interfaces) correctly forwards packets received on a particular incoming interface from a particular source.
As used herein, ��forwarding information�� refers to a set of data which indicates one or more forwarding decisions respectively made by one or more forwarding components of a network element for packets of a particular packet flow. ��Forwarding decision�� refers to data indicating a result of processing a packet at a network element. Various types of forwarding decisions may be made depending on the type of forwarding implemented by a network element and the type of packet being processed and forwarded by the network element. For example, a forwarding decision made for a particular packet by a network element may include dropping the packet because the packet fails to satisfy one or more routing policies or Access Control Lists (ACLs). In another example, a forwarding decision made for a particular packet by a network element may include a Quality-of-Service (QoS) decision that determines how the particular packet is treated within the network element, such as, for example whether the particular packet is queued in high priority or low priority queues which expedite or delay transmission of the particular packet. In another example, a forwarding decision made for a particular packet by a network element may include determining a next-hop network element to which the packet is to be forwarded, where the next-hop network element is a particular network element that is the next-hop on the route to the packet destination.
In some embodiments, the forwarding information returned by the logic of a network element may include an identifier of the outgoing network interface through which the network element forwards the packets of a particular packet flow. Outgoing network interfaces in a network element are identified in a similar manner as incoming network interfaces. (The network interfaces in a network element are typically configurable for both transmitting and receiving packets; thus, the distinction between ��incoming�� and ��outgoing�� network interfaces made herein is purely illustrative, and it is noted that the same network interface may be ��incoming�� for some packet flows and ��outgoing�� for other packet flows.) By providing the identifier of the outgoing network interface, in these embodiments the techniques described herein provide for diagnosing whether a network element forwards packets of the packet flow through the correct outgoing network interface.
In some embodiments, the forwarding information returned by the logic of a network element may include the Layer 2 (e.g., data link) address of a next-hop network element to which the network element routes the packets of a particular packet flow. In addition, the forwarding information may also include an adjacency record, which associates the Layer 2 address of the next-hop network element with an identifier of the interface of the network element that is connected to that next-hop network element. (Network elements in a packet-switched network are said to be ��adjacent�� if they can reach each other with a single hop across a data link layer.) By providing the Layer 2 address of the next-hop network element for the packet flow and/or any corresponding adjacency records, in these embodiments the techniques described herein provide for diagnosing whether a network element forwards packets of the packet flow to the next-hop network element over the correct and/or optimal outgoing network interface.
As used herein, ��synthetic packet�� refers to a packet that is generated at a network element, is not received from another network element, and is not to be forwarded to another network element. According to the techniques described herein, a synthetic packet is marked as ��internal�� or ��debug�� which indicates to the packet-processing network element components that that packet is not be forwarded to any other network element and that any forwarding decisions for that packet are to be recorded. For example, a synthetic packet may include header data (e.g., one or more flags, options, etc.) indicating that: a packet-processing network element component needs to record its forwarding decision after processing the synthetic packet; and the synthetic packet is not to be forwarded to any other network element. According to the techniques described herein, the forwarding logic components of a network element process a synthetic packet like any other packet of a packet flow�Xfor example, by examining the synthetic packet, making a forwarding decision for the synthetic packet, and facilitating the transfer of the synthetic packet from the receive queue of an incoming network interface to the transmit queue of an outgoing network interface. The synthetic packet is examined in the transmit queue of the outgoing network interface and, based on the flags in the header data, is dropped from the transmit queue prior to transmission.
In operation, according to the techniques described herein a management Application Programming Interface (API) logic of a network element receives address information that identifies a packet flow that is received at an incoming network interface of the network element. As used herein, ��API logic�� broadly refers to a set of components operable to perform the techniques described herein, and is not limited to any particular types of modules, interfaces, libraries, elements, or any particular types of mechanisms, services, or application programs. Based on the received address information, the API logic generates a synthetic packet. The API logic then determines the incoming network interface for the packet flow identified in the address information, and stores the synthetic packet into the receive queue of that incoming network interface. Thereafter, one or more forwarding logic components of the network element process and make forwarding decisions for the synthetic packet as part of processing the packets in the identified packet flow. When processing the synthetic packet each of the one or more forwarding logic components stores, as part of the forwarding information associated with the synthetic packet and correspondingly with the packet flow, data indicating the forwarding decision for the synthetic packet that is made by that forwarding logic component. After the forwarding logic components are finished with processing the synthetic packet, the synthetic packet would be transferred to an outgoing network interface of the network element where it will be examined and dropped based on the packet's header data. The forwarding decisions made for the synthetic packet, which are in effect the forwarding decisions made for packets of the packet flow identified in the received address information, are recorded in the forwarding information. The API logic of the network element retrieves the forwarding information and may provide this information to a user.
In operation, forwarding logic components 108 examine (in parallel or sequentially) packets that are received and stored in the receive queues of the network interfaces of network element 102. Based on information from the packets and on routing information stored and maintained at network element 102, forwarding logic components 108 determine to which outgoing network interface of network element 102 to transfer the packets, and cause the transfer of the packets to the transmit queue of that outgoing network interface. According to the techniques described herein, each of forwarding logic components 108 is operable to determine whether it is processing a normal or a synthetic packet. For example, a forwarding logic component is able to determine whether a packet header includes ��debug�� flag (which would indicate that the packet is a synthetic packet), or whether the packet is a normal packet that needs to be forwarded. When a forwarding logic component determines that it is processing a synthetic packet, the forwarding logic component records the forwarding decision it makes for that packet along with any other additional data that would be helpful in interpreting the forwarding decision being recorded.
In an operational example, suppose that a network administrator needs to troubleshoot a problem with the forwarding of packets of a particular packet flow. The network administrator would log into network element 102, and would issue a CLI command to API 110. The CLI command specifies address information that identifies the packet flow. In response to the command, API logic 110 creates and initializes a data structure in storage area 112 for storing forwarding information 114. Based on the received address information, API logic 110 determines the incoming network interface on which packets of the packet flow are received, for example, network interface 104A. API logic 110 generates a synthetic packet based on the address information, where the synthetic packet includes a ��debug�� flag in its header which indicates that forwarding decisions for this packet are to be recorded and that this packet is not to be forwarded to any next-hop network element. Apart from the ��debug�� flag, the synthetic packet has the same headers as the headers of other packets in the packet flow identified in the received address information. After generating the synthetic packet, API logic 110 writes this packet into the receive queue 105A of network interface 104A.
Thereafter, one or more of forwarding logic components 108 processes the synthetic packet as part of processing the packets stored in receive queue 105A of network interface 104A. According to the techniques described herein, each forwarding logic component examines the headers of the packets it processes to determine whether any packet includes a ��debug�� flag. When a forwarding logic component determines that a packet header includes a ��debug�� flag, the forwarding logic component records the forwarding decision that it makes for that packet. Thus, when a forwarding logic component processes the synthetic packet, the forwarding logic component would record any forwarding decision it makes into forwarding information 114 along with any additional routing and/or configuration data that would be helpful to interpret the forwarding decision being recorded.
The processing of the synthetic packets by forwarding logic components 108 may result in one of several outcomes. In one outcome, one or more of the forwarding logic components may determine that the synthetic packet must be dropped (for example, because the packet does not conform to one or more access policies); thus, in this outcome the synthetic packet would be dropped and would not be forwarded to an outgoing network interface of network element 102. In another outcome, the one or more forwarding logic components that process the synthetic packet would determine to which outgoing network interface of network element 102 to transfer the synthetic packet; thus, in this outcome the synthetic packet would be transferred to the transmit queue of that outgoing network interface (for example, transmit queue 106B of network interface 104B). When placed in the transmit queue of outgoing network interface 104B, the synthetic packet would be examined and, based on the ��debug�� flag in the packet header, would be dropped prior to being transmitted to any next-hop network element. In either outcome, any forwarding decision made by any forwarding logic component would be recorded in forwarding information 114.
After forwarding logic components 114 have processed the synthetic packet and have recorded their respective forwarding decisions in forwarding information 114, API logic 110 retrieves forwarding information 114 from storage area 112 and provides the retrieved forwarding information 114 to the network administrator through the CLI. Since apart from being tagged as ��debug�� the synthetic packet has the same headers as any of the packets of the packet flow identified by the address information submitted by the network administrator, the forwarding decisions for the synthetic packet recorded in forwarding information 114 would be the same as the forwarding decisions made for the packets of the packet flow. As a result, the network administrator would be able to troubleshoot the problem with the forwarding of the packet flow by examining forwarding information 114.
In step 204, a synthetic packet is generated at the network element based on the received address information. The synthetic packet includes header data which indicates that the synthetic packet is not to be forwarded to any next-hop network element and that any forwarding decisions made for the synthetic packet must be recorded. For example, the received address information may be a source address, a destination address, and an inbound MPLS label that identifies an MPLS-over-IP packet flow. The synthetic packet would be generated to include the source address, the destination address, and the inbound MPLS label. In addition, the header of the packet would include a ��debug�� flag to indicate that this is a synthetic packet.
Thereafter, in step 210 one or more forwarding logic components of the network element process the synthetic packet as part of processing packets of the identified packet flow that are stored in the receive queue of the incoming network interface. As part of processing the packets of the identified packet flow, the one or more forwarding logic components examine each packet to determine whether this packet is a synthetic packet the forwarding decisions for which must be recorded. Thus, when processing the synthetic packet, a forwarding logic component examines the header of the synthetic packet, finds the ��debug�� flag, and performs steps 210A and 210B. In step 210A, the forwarding logic component makes a forwarding decision for the synthetic packet and causes the synthetic packet to be transferred to an outgoing network interface of the network element. For example, a MTR forwarding logic component may use the inbound MPLS label to look up in a memory table a corresponding outbound MPLS label and an interface identifier of the outgoing network interface. The MTR forwarding logic component would then swap the inbound MPLS label in the packet with the determined outbound MPLS label, and would cause the synthetic packet to be transferred to the identified outgoing network interface. Then, in step 210B the MTR forwarding logic component would record the forwarding decision (e.g., the inbound MPLS label, the outbound MPLS label, and the interface identifier of outgoing network interface) for the synthetic packet in the forwarding information that is associated with, and being recorded for, the synthetic packet.
6.0 Implementation Mechanisms�XHardware Overview FIG. 5 is a block diagram that illustrates a computer system 500 upon which an embodiment of the techniques described herein may be implemented. Example embodiments may be implemented using one or more computer programs and/or one or more ASICs that are executable on a network infrastructure element such as a router or switch. Thus, in one embodiment the computer system 500 is a router. In some embodiments, the techniques described herein may be implemented on a line card that is coupled as a blade to the backplane of a router in which one or more Route Processors (RPs) and multiple line cards are coupled over a crossbar switch fabric. In these embodiments, each line card is a computer system that includes its own network interface(s), processor(s), and ASIC(s), and is capable of independently forwarding inbound packets by switching the packets to an outgoing interface of the same line card and/or by switching the packets across the crossbar switch fabric to a different line card of the router.
The term ��computer-readable medium�� as used herein refers to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using computer system 500, various computer-readable media are involved, for example, in providing instructions to processor 504 for execution. Such a medium may take many forms, including but not limited to storage media and transmission media. Storage media includes both non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 510. Volatile media includes dynamic memory, such as main memory 506. Transmission media includes coaxial cables, copper wire, and fiber optics, including the wires that comprise bus 502. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications. All such media must be tangible to enable the instructions carried by the media to be detected by a physical mechanism that reads the instructions into a machine such as, for example, a computer system.
�M�Q�ޥ� �ޥΪ��M�Q�ӽФ���o�G��� �ӽЪ��M�Q�W��US60555751998�~1��26��2000�~4��25��Ascend Communications, Inc.Virtual private network system and methodUS61153781997�~6��30��2000�~9��5��Sun Microsystems, Inc.Multi-layer distributed network elementUS61253911998�~10��16��2000�~9��26��Commerce One, Inc.Market makers using documents for commerce in trading partner networksUS62266751998�~10��16��2001�~5��1��Commerce One, Inc.Participant server which process documents for commerce in trading partner networksUS62723411997�~9��16��2001�~8��7��Motient Services Inc.Network engineering/systems engineering system for mobile satellite communication systemUS63212641998�~8��28��2001�~11��20��3Com CorporationNetwork-performance statistics using end-node computer systemsUS63378561998�~5��20��2002�~1��8��Steelcase Development CorporationMultimedia data communications systemUS64118062000�~7��6��2002�~6��25��Mobile Satellite Ventures LpVirtual network configuration and management system for satellite communications systemUS64184721999�~1��19��2002�~7��9��Intel CorporationSystem and method for using internet based caller ID for controlling access to an object stored in a computerUS64738631999�~10��28��2002�~10��29��International Business Machines CorporationAutomatic virtual private network internet snoop avoiderUS65021352000�~2��15��2002�~12��31��Science Applications International CorporationAgile network protocol for secure communications with assured system availabilityUS65295131999�~2��4��2003�~3��4��Alcatel Canada Inc.Method of using static maps in a virtual private networkUS65394832000�~1��12��2003�~3��25��International Business Machines CorporationSystem and method for generation VPN network policiesUS66115262000�~5��8��2003�~8��26��Adc Broadband Access Systems, Inc.System having a meshed backplane and process for transferring data therethroughUS66118632000�~6��5��2003�~8��26��Intel CorporationAutomatic device assignment through programmable device discovery for policy based network managementUS66147911999�~5��11��2003�~9��2��Nortel Networks LimitedSystem, device, and method for supporting virtual private networksUS66649781997�~11��17��2003�~12��16��Fujitsu LimitedClient-server computer network management architectureUS66838811999�~5��28��2004�~1��27��Ericsson Inc.Interface between an SS7 gateway and an IP networkUS66938781999�~10��15��2004�~2��17��Cisco Technology, Inc.Technique and apparatus for using node ID as virtual private network (VPN) identifiersUS67659002003�~1��16��2004�~7��20��Utstarcom, Inc.Virtual home agent service using software-replicated home agentsUS67716462000�~6��30��2004�~8��3��Hi/Fn, Inc.Associative cache structure for lookups and updates of flow records in a network monitorUS67722112002�~4��30��2004�~8��3��Transtech Networks Usa, Inc.Content-aware web switch without delayed binding and methods thereofUS67722262000�~8��15��2004�~8��3��Avaya Technology Corp.VPN device clustering using a network flow switch and a different mac address for each VPN device in the clusterUS67857282000�~3��23��2004�~8��31��Redleaf Group, Inc.Distributed administration of access to informationUS68136902001�~10��16��2004�~11��2��Network Appliance, Inc.Caching media data using content-sensitive identifiersUS68622702000�~7��14��2005�~3��1��At&T Corp.Architectural reference model for QoS-driven wireless LANsUS68684262000�~7��7��2005�~3��15��Mankoff Jeffrey W.Virtual document organizer system and methodUS69441832000�~6��12��2005�~9��13��AlcatelObject model for network policy managementUS69446782001�~6��18��2005�~9��13��Transtech Networks Usa, Inc.Content-aware application switch and methods thereofUS69508222002�~11��25��2005�~9��27��Oracle International CorporationTechniques for increasing efficiency while servicing requests for database servicesUS70313142002�~4��19��2006�~4��18��Bytemobile, Inc.Systems and methods for providing differentiated services within a network communication systemUS70589732000�~3��3��2006�~6��6��Symantec CorporationNetwork address translation gateway for local area networks using local IP addresses and non-translatable port addressesUS71340752001�~4��26��2006�~11��7��International Business Machines CorporationConversion of documents between XML and processor efficient MXML in content based routing networksUS71853652002�~3��27��2007�~2��27��Intel CorporationSecurity enabled network access controlUS72156372001�~12��14��2007�~5��8��Juniper Networks, Inc.Systems and methods for processing packetsUS72456202002�~10��11��2007�~7��17��Broadcom CorporationMethod and apparatus for filtering packet data in a network deviceUS73215562002�~10��28��2008�~1��22��Ipolicy Networks, IncApplication prioritization policy engineUS73627632003�~9��4��2008�~4��22��Samsung Electronics Co., Ltd.Apparatus and method for classifying traffic in a distributed architecture routerUS74155122001�~5��24��2008�~8��19��Cisco Technology, Inc.Method and apparatus for providing a general purpose computing platform at a router on a networkUS74693002003�~1��16��2008�~12��23��Mobitv, Inc.System and method for storage and retrieval of arbitrary content and application dataUS74751082004�~6��16��2009�~1��6��International Business Machines CorporationSlow-dynamic load balancing methodUS74834212004�~3��29��2009�~1��27��Sony United Kingdom LimitedRouting dataUS74967502004�~12��7��2009�~2��24��Cisco Technology, Inc.Performing security functions on a message payload in a network elementUS75094312004�~11��17��2009�~3��24��Cisco Technology, Inc.Performing message and transformation adapter functions in a network element on behalf of an applicationUS75515672005�~1��5��2009�~6��23��Cisco Technology, Inc.Interpreting an application message at a network element using sampling and heuristicsUS76062672004�~12��10��2009�~10��20��Cisco Technology, Inc.Reducing the sizes of application layer messages in a network elementUS76648792004�~11��23��2010�~2��16��Cisco Technology, Inc.Caching content and state data at a network elementUS200100085252001�~1��4��2001�~7��19��AlcatelProcess, exchange, service computer, program module and interface device for transmitting telecommunications service data between an exchange and a service computerUS200100474222001�~1��22��2001�~11��29��Mcternan Brennan J.System and method for using benchmarking to account for variations in client capabilities in the distribution of a media presentationUS200200328712001�~5��15��2002�~3��14��The Regents Of The University Of MichiganMethod and system for detecting, tracking and blocking denial of service attacks over a computer networkUS200200692792000�~12��29��2002�~6��6��Hewlett-Packard Development Company L.P.Apparatus and method for routing a transaction based on a requested level of serviceUS200200808192001�~1��18��2002�~6��27��Industrial Technology Research InstitutePacket tunneling method in mobile data communication networkUS200200838172001�~10��12��2002�~7��4��Hoshino Gakki Kabushiki KaishaSnare strainer for a snare drumUS200201059112001�~5��23��2002�~8��8��Niksun, Inc.Apparatus and method for collecting and analyzing communications dataUS200201079512001�~9��7��2002�~8��8��Nasdaq Omx Group, Inc., TheReport group managementUS200201142742001�~9��19��2002�~8��22��Packetup CorporationPacket based network for supporting real time applicationsUS200201240662000�~12��15��2002�~9��5��International Business Machines CorporationMethod and system for unambiguous addressability in a distributed application framework in which duplicate network addresses exist across multiple customer networksUS200201336182001�~8��8��2002�~9��19��Desai Bhavesh N.Tunneling system for a cable data serviceUS200201439812001�~4��3��2002�~10��3��International Business Machines CorporationQuality of service improvements for network transactionsUS200201639332001�~11��2��2002�~11��7��Benveniste MathildeTiered contention multiple access (TCMA): a method for priority-based shared channel accessUS200201659572001�~10��2��2002�~11��7��Garage Securities, Inc.Intelligent dynamic route selection based on active probing of network operational characteristicsUS200201916222001�~6��18��2002�~12��19��Ericsson Inc.System for and method of differentiated queuing in a routing systemUS200300051172001�~6��29��2003�~1��2��Kang Amy H.Pluggable authentication and access control for a messaging systemUS200300187262002�~4��29��2003�~1��23��Low, Sydney GordonInstant messagingUS200300262682002�~3��11��2003�~2��6��Siemens Technology-To-Business Center, LlcCharacteristic routingUS200300286162002�~6��28��2003�~2��6��Aoki HideoCongestion control and avoidance methodUS200300368792001�~8��17��2003�~2��20��Koninklijke Philips Electronics N.V.System and method for detecting and correcting incorrect hand position of a computer userUS200300558182002�~3��26��2003�~3��20��Sun Microsystems, Inc.Method and system of routing messages in a distributed search networkUS200300699752000�~12��22��2003�~4��10��Abjanic John B.Network apparatus for transformationUS200300780312002�~3��28��2003�~4��24��Masuda HiroyoCommunication systemUS200300864222001�~12��28��2003�~5��8��Netvmg, Inc.System and method to provide routing control of information over networksUS200300935302001�~10��26��2003�~5��15��Syed MajidArbitrator system and method for national and local content distributionUS200300955692002�~11��6��2003�~5��22��Credit Suisse AgDistributed integration of legacy PBX system with SIP networksUS200300992322002�~3��25��2003�~5��29��Kudou HideyukiRouter having a function to prevent a packet sequence inversionUS200301080412001�~12��7��2003�~6��12��Nortell Networks LimitedTunneling scheme optimized for use in virtual private netwoksUS200301128092002�~8��23��2003�~6��19��Juniper Networks, Inc.Efficient method and system for automatic discovery and verification of optimal paths through a dynamic multi-point meshed overlay networkUS200301154482002�~10��29��2003�~6��19��Omtool, Ltd.Methods and apparatus for securely communicating a messageUS200301401402003�~1��16��2003�~7��24��Stonesoft CorporationMonitoring the flow of a data streamUS200301589622002�~2��21��2003�~8��21��Corente, Inc.Methods and systems for resolving addressing conflicts based on tunnel informationUS200301635392003�~2��25��2003�~8��28��Piccinelli GiacomoApparatus and method for data transferUS200301636032002�~11��26��2003�~8��28��Oracle International CorporationSystem and method for XML data bindingUS200301771832002�~3��15��2003�~9��18��Microsoft CorporationTime-window-constrained multicast using connection schedulingUS200301881922002�~3��27��2003�~10��2��Liu Hsin-YuoSecurity enabled network access controlUS200301899352003�~4��8��2003�~10��9��Warden Gary G.Systems and methods for providing quality of service (QoS) in an environment that does not normally support QoS featuresUS200302046262002�~4��24��2003�~10��30��Microsoft CorporationMethod and apparatus for efficiently matching responses to requests previously passed by a network nodeUS200302047192003�~5��28��2003�~10��30��Kavado, Inc.Application layer security method and systemUS200302171712003�~5��17��2003�~11��20��Von Stuermer Wolfgang R.Self-replicating and self-installing software apparatusUS200302171762003�~3��27��2003�~11��20��Sap AktiengesellschaftContent-based routing system and methodUS200302368832002�~9��4��2003�~12��25��Hitachi, Ltd.Proxy server apparatus and method for providing service using the sameUS200400066132002�~7��3��2004�~1��8��Telefonaktiebolaget L M Ericsson (Publ)Quality of service (QoS) mechanism in an internet protocol (IP) networkUS200400222502002�~7��31��2004�~2��5��Allen Keith JosephResource reservation protocol based guaranteed quality of service internet protocol connections over a switched networkUS200400222552002�~7��31��2004�~2��5��Allen Keith JosephEnhancement of resource reservation protocol enabling short-cut internet protocol connections over a switched networkUS200400248812002�~7��31��2004�~2��5��Elving Christopher H.System and method for sticky routing of requests within a server farmUS200400328812002�~8��16��2004�~2��19��Mitsubishi Electric Research Laboratories, Inc.Distributed application layer protocol converter for communications networkUS200400399402002�~8��23��2004�~2��26��Koninklijke Philips Electronics N.V.Hardware-based packet filtering acceleratorUS200400645812003�~7��7��2004�~4��1��Sony CorporationData forwarding controller communication terminal apparatus, data communication system and method, and computer programUS200401283602002�~12��31��2004�~7��1��Delley FredericChannel serverUS200401628712003�~2��13��2004�~8��19��Sun Microsystems, Inc.Infrastructure for accessing a peer-to-peer network environmentUS200401679862003�~2��26��2004�~8��26��International Business Machines CorporationDynamic data-driven application integration adaptersUS200402053362003�~4��12��2004�~10��14��Cavium, Inc.Transparent IPSec processing inline between a framer and a network componentUS200402644812003�~9��8��2004�~12��30��Microsoft CorporationNetwork load balancing with traffic routingUS200402679202003�~6��30��2004�~12��30��Microsoft CorporationFlexible network load balancingUS200402679302004�~6��16��2004�~12��30��International Business Machines CorporationSlow-dynamic load balancing method and systemUS200501658342005�~3��22��2005�~7��28��Cisco Technology, Inc.Method and apparatus for controlled access of requests from virtual private network devices to managed information objects using simple network management protocol and multi-topology routingUS200501907582004�~3��1��2005�~9��1��Cisco Technology, Inc.Security groups for VLANsUS200602882082006�~4��5��2006�~12��21��Cisco Technology, Inc.Method and apparatus for adaptive application message payload content transformation in a network infrastructure elementUS200701129752007�~1��10��2007�~5��17��Cassar ChristianRedirecting network traffic through a multipoint tunnel overlay network using distinct network address spaces for the overlay and transport networksUS200702533462006�~5��1��2007�~11��1��Cisco Technology, Inc.Detection of potential forwarding loops in bridged networks�D�M�Q�ޥ��ѦҤ��m1Amended Claims, Application No. 05820894.3.2211/1812870, 6 pages.2Chiu, Kenneth, et al., "Investigating the Limits of SOAP Performance for Scientific Computing", Nov. 7, 2002, IEEE Computer Society, 8 pages.3Claims, application No. 200580031604.1, 6 pages.4Claims, application No. EP 05820894, 6 pages.5Claims, filing No. 200580031571.0, 8 pages.6Claims, filing No. 200580045932.7, 8 pages.7Claims, International application No. PCT/US05/46149, 10 pages.8Current Claims, PCT/US2006/024375, 6 pages.9Decasper, Dan et al., "Router Plugins: A Software Architecture for Next-Generation Routers," IEEE ACM Transactions on Networking, vol. 9, No. 1, Feb. 2000, XP011038838, 14 pages.10E. Rosen et al., "BGP/MPLS VPNs," Mar. 1999, pp. 1-25.11European Patent Office, "Communication pursuant to Article 94(3) EPC", Application No. 05820894.3.2211/1812870, dated May 28, 2009, 9 pages.12European Patent Office, "European Search Report", application No. EP 05820894, Feb. 6, 2009, 8 pages.13Harrington, D. et al., "An Architecture for Describing SNMP Management Frameworks", RFC 2571, Apr. 1999, pp. 1-58.14International Searching Authority, "Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration", International application No. PCT/US05/46149, dated Jul. 20, 2007, 9 pages.15International Searching Authority, "Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration," PCT/US2006/024375, dated Oct. 17, 2006, 10 pages.16Pending Claims, Application No. 200580045932.7, 8 pages.17State Intellectual Property Office of the People's Republic of China, "The First Office Action", application No. 200580031604.1, Dated Jun. 27, 2008, 15 pages.18State Intellectual Property Office of the People'S Republic of China, "The First Office Action", filing No. 200580031571.0, Dated Dec. 19, 2008, 9 pages.19State Intellectual Property Office of the People'S Republic of China, "The First Office Action", filing No. 200580045932.7, Dated Nov. 28, 2008, 8 pages.20The Patent Office of the People's Republic of China, "The Second Office Action", Application No. 200580045932.7, dated May 8, 2009, 9 pages.21Wijnen, B. et al., View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), RCF 2575, Apr. 1999, pp. 1-36.22Yakov Rekhter et al., "Use of PE-PE GRE or IP in RFC2547 VPNs," Expiration Date: Aug. 2002, pp. 1-6.������l�Ϥ�Google ���� - Sitemap - USPTO �j�q�U�� - ���p�v�F�� - �A�ȱ�� - ���� Google �M�Q - �N���^�X��ƬO�Ѭ��ӷ~�M�Q��Ʈw (IFI CLAIMS Patent Services) ����©2012 Google