WO2007130413A2 - Systems and methods for close queuing to support quality of service - Google Patents
Systems and methods for close queuing to support quality of service Download PDFInfo
- Publication number
- WO2007130413A2 WO2007130413A2 PCT/US2007/010557 US2007010557W WO2007130413A2 WO 2007130413 A2 WO2007130413 A2 WO 2007130413A2 US 2007010557 W US2007010557 W US 2007010557W WO 2007130413 A2 WO2007130413 A2 WO 2007130413A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- network
- node
- connection
- transport protocol
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/19—Flow control; Congestion control at layers above the network layer
- H04L47/193—Flow control; Congestion control at layers above the network layer at the transport layer, e.g. TCP related
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/33—Flow control; Congestion control using forward notification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
- H04L49/901—Buffering arrangements using storage descriptor, e.g. read or write pointers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
Definitions
- the presently described technology generally relates to communications networks. More particularly, the presently described technology relates to systems and methods for protocol filtering for Quality of Service.
- Communications networks are utilized in a variety of environments. Communications networks typically include two or more nodes connected by one or more links. Generally, a communications network is used to support communication between two or more participant nodes over the links and intermediate nodes in the communications network. There may be many kinds of nodes in the network. For example, a network may include nodes such as clients, servers, workstations, switches, and/or routers. Links may be, for example, modem connections over phone lines, wires, Ethernet links, Asynchronous Transfer Mode (ATM) circuits, satellite links, and/or fiber optic cables. A communications network may actually be composed of one or more smaller communications networks. For example, the Internet is often described as network of interconnected computer networks. Each network may utilize a different architecture and/or topology.
- ATM Asynchronous Transfer Mode
- one network may be a switched Ethernet network with a star topology and another network may be a Fiber-Distributed Data Interface (FDDI) ring.
- Communications networks may carry a wide variety of data.
- a network may carry bulk file transfers alongside data for interactive real-time conversations.
- the data sent on a network is often sent in packets, cells, or frames.
- data may be sent as a stream.
- a stream or flow of data may actually be a sequence of packets.
- Networks such as the Internet provide general purpose data paths between a range of nodes and carrying a vast array of data with different requirements.
- a protocol stack also referred to as a networking stack or protocol suite, refers to a collection of protocols used for communication. Each protocol may be focused on a particular type of capability or form of communication. For example, one protocol may be concerned with the electrical signals needed to communicate with devices connected by a copper wire. Other protocols may address ordering and reliable transmission between two nodes separated by many intermediate nodes, for example .
- Protocols in a protocol stack typically exist in a hierarchy. Often, protocols are classified into layers.
- One reference model for protocol layers is the Open Systems Interconnection ("OSI") model.
- the OSI reference model includes seven layers: a physical layer, data link layer, network layer, transport layer, session layer, presentation layer, and application layer.
- the physical layer is the
- TCP Transmission Control Protocol
- UDP User Datagram Protocol
- IP Internet Protocol
- data to be transmitted is passed down the layers of the protocol stack, from highest to lowest. Conversely, at the receiving node, the data is passed up the layers, from lowest to highest.
- the data may be manipulated by the protocol handling communication at that layer. For example, a transport layer protocol may add a header to the data that allows for ordering of packets upon arrival at a destination node . Depending on the application, some layers may not be used, or even present, and data may just be passed through.
- a tactical data network may also be referred to as a tactical communications network.
- a tactical data network may be utilized by units within an organization such as a military (e.g., army, navy, and/or air force) .
- Nodes within a tactical data network may include, for example, individual soldiers, aircraft, command units, satellites, and/or radios.
- a tactical data network may be used for communicating data such as voice, position telemetry, sensor data, and/or realtime video.
- a logistics convoy may be in-route to provide supplies for a combat unit in the field. Both the convoy and the combat unit may be providing position telemetry to a command post over satellite radio links.
- An unmanned aerial vehicle (“UAV”) may be patrolling along the road the convoy is taking and transmitting real-time video data to the command post over a satellite radio link also.
- UAV unmanned aerial vehicle
- an analyst may be examining the video data while a controller is tasking the UAV to provide video for a specific section of road. The analyst may then spot an improvised explosive device (“IED”) that the convoy is approaching and send out an order over a direct radio link to the convoy for it to halt and alerting the convoy to the presence of the IED.
- IED improvised explosive device
- a network in a command unit may include a gigabit Ethernet local area network ("LAN") along with radio links to satellites and field units that operate with much lower throughput and higher latency.
- Field units may communicate both via satellite and via direct path radio frequency (“RF") .
- Data may be sent point-to-point, multicast, or broadcast, depending on the nature of the data and/or the specific physical characteristics of the network.
- a network may include radios, for example, set up to relay data.
- a network may include a high frequency (“HF”) network which allows long rang communication.
- HF high frequency
- a microwave network may also be used, for example.
- tactical networks Due to the diversity of the types of links and nodes, among other reasons, tactical networks often have overly complex network addressing schemes and routing tables.
- some networks such as radio-based networks, may operate using bursts. That is, rather than continuously transmitting data, they send periodic bursts of data. This is useful because the radios are broadcasting on a particular channel that must -be shared by all participants, and only one radio may transmit at a time.
- Tactical data networks are generally bandwidth- constrained. That is, there is typically more data to be communicated than bandwidth available at any given point in time. These constraints may be due to either the demand for bandwidth exceeding the supply, and/or the available communications technology not supplying enough bandwidth to meet the user's needs, for example. For example, between some nodes, bandwidth may be on the order of kilobits/sec. In bandwidth-constrained tactical data networks, less important data can clog the network, preventing more important data from getting through in a timely fashion, or even arriving at a receiving node at all. In addition, portions of the networks may include internal buffering to compensate for unreliable links. This may cause additional delays. Further, when the buffers get full, data may be dropped.
- bandwidth available to a network cannot be increased.
- the bandwidth available over a satellite communications link may be fixed and cannot effectively be increased without deploying another satellite.
- bandwidth must be managed rather than simply expanded to handle demand.
- network bandwidth is a critical resource. It is desirable for applications to utilize bandwidth as efficiently as possible. In addition, it is desirable that applications avoid "clogging the pipe," that is, overwhelming links with data, when bandwidth is limited. When bandwidth allocation changes, applications should preferably react.
- Bandwidth can change dynamically due to, for example, quality of service, jamming, signal obstruction, priority reallocation, and line- of-sight. Networks can be highly volatile and available bandwidth can change dramatically and without notice.
- tactical data networks may experience high latency.
- a network involving communication over a satellite link may incur latency on the order of half a second or more.
- this may not be a problem, but for others, such as real-time, interactive communication (e.g., voice communications), it is highly desirable to minimize latency as much as possible.
- Data loss Another characteristic common to many tactical data networks is data loss. Data may be lost due to a variety of reasons. For example, a node with data to send may be damaged or destroyed. As another example, a destination node may temporarily drop off of the network. This may occur because, for example, the node has moved out of range, the communication' s link is obstructed, and/or the node is being jammed. Data may be lost because the destination node is not able to receive it and intermediate nodes lack sufficient capacity to buffer the data until the destination node becomes available. Additionally, intermediate nodes may not buffer the data at all, instead leaving it to the sending node to determine if the data ever actually arrived at the destination.
- applications in a tactical data network are unaware of and/or do not account for the particular characteristics of the network. For example, an application may simply assume it has as much bandwidth available to it as it needs. As another example, an application may assume that data will not be lost in the network. Applications which do not take into consideration the specific characteristics of the underlying communications network may behave in ways that actually exacerbate problems. For example, an application may continuously send a stream of data that could just as effectively be sent less frequently in larger bundles . The continuous stream may incur much greater overhead in, for example, a broadcast radio network that effectively starves other nodes from communicating, whereas less frequent bursts would allow the shared bandwidth to be used more effectively.
- TCP may not function well over a radio-based tactical network because of the high loss rates and latency such a network may encounter.
- TCP requires several forms of handshaking and acknowledgments to occur in order to send data. High latency and loss may result in TCP hitting time outs and not being able to send much, if any, meaningful data over such a network.
- Information communicated with a tactical data network often has various levels of priority with respect to other data in the network.
- threat warning receivers in an aircraft may have higher priority than position telemetry information for troops on the ground miles away.
- orders from headquarters regarding engagement may have higher priority than logistical communications behind friendly lines.
- the priority level may depend on the particular situation of the sender and/or receiver.
- position telemetry data may be of much higher priority when a unit is actively engaged in combat as compared to when the unit is merely following a standard patrol route.
- real-time video data from an UAV may have higher priority when it is over the target area as opposed to when it is merely in-route.
- QoS Quality of Service
- a network supporting QoS may guarantee a certain amount of bandwidth to a data stream.
- a network may guarantee that packets between two particular nodes have some maximum latency. Such a guarantee may be useful in the case of a voice communication where the two nodes are two people having a conversation over the network. Delays in data delivery in such a case may result in irritating gaps in communication and/or dead silence, for example .
- QoS may be viewed as the capability of a network to provide better service to aelected network traffic.
- the primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic) , and improved loss characteristics.
- Another important goal is making sure that providing priority for one flow does not make other flows fail. That is, guarantees made for subsequent flows must not break the guarantees made to existing flows.
- DiffServ is a class of service model that enhances the best-effort services of a network such as the Internet. DiffServ differentiates traffic by user, service requirements, and other criteria. Then, DiffServ marks packets so that network nodes can provide different levels of service via priority queuing or bandwidth allocation, or by choosing dedicated routes for specific traffic flows. Typically, a node has a variety of queues for each class of service. The node then selects the next packet to send from those queues based on the class categories.
- nodes at the "edge" of network may be adapted to provide some improvement in QoS, even if they are incapable of making total guarantees.
- Nodes are considered to be at the edge of the network if they are the participating nodes in a communication (i.e., the transmitting and/or receiving nodes) and/or if they are located at chokepoints in the network.
- a chokepoint is a section of the network where all traffic must pass to another portion. For example, a router or gateway from a LAN to a satellite link would be a choke point, since all traffic from the LAN to any nodes not on the LAN must pass through the gateway to the satellite link.
- QoS is provided for a TCP socket connection
- "open” and "close” commands are required for each connection.
- Data may be queued for a connection in order to provide QoS for that connection.
- any data that has been queued will be lost if the "close” is immediately honored.
- the close is processed right away, and data may be lost if it is not processed prior to close of the connection.
- a method includes opening a connection between a first node and a second node in a network to communicate data between the first node and the second node and holding a transport protocol command in relation to the data being communicated between the first node and the second node via the connection such that the transport protocol command is processed after communication of the data is complete.
- Holding may include enqueuing the transport protocol command behind the data such that the transport protocol command is executed with respect to the connection after the data has been communicated between the first and second nodes, for example.
- the transport protocol command may be held by manipulating a transport protocol layer of the network, for example. Additionally, data may be enqueued at a transport protocol layer to prioritize communication of the data from the first node to the second node via the connection.
- the connection may include a transmission control protocol socket connection, for example.
- the transport protocol may include a transmission control protocol, for example.
- the network may be a tactical data network, for example, having a bandwidth constrained by an environment in which the network operates.
- the transport protocol command may include a close connection command, for example.
- Certain embodiments provide a computer-readable medium having a set of instructions for execution on a processing device.
- the set of instructions includes a connection routine for establishing a transport connection between a first node and a second node to communicate data between the first node and the second node and a hold routine operating at a network transport layer for holding a transport protocol command in relation to the data being communicated between the first node and the second node via the transport connection, wherein the transport protocol command is processed after communication of the data.
- the hold routine may enqueue the transport protocol command in relation to the data being communicated between the first node and the second node via the transport connection, for example.
- the set of instructions may further include a queue routine, for example, for enqueuing the data and the transport protocol command in relation to the transport connection.
- the set of instructions may also include a prioritization routine, for example, for prioritizing communication of the data between the first node and the second node based on at least one rule.
- the transport connection may be established between the first node and the second node in a tactical data network, for example. Certain embodiments provide a method for enqueuing transport protocol commands with data in a low-bandwidth network environment.
- the method may include receiving data for transmission via a network connection, enqueuing the data, enqueuing a transport protocol command related to the network connection, transmitting the data via the network connection, and transmitting the transport protocol command after transmission of the data.
- the data and the transport protocol command may be enqueued based at least in part on manipulating a transport protocol layer of a communication network, for example.
- the data may be prioritized based on at least one rule, such as a content-based rule and/or a protocol-based rule.
- the transport protocol command includes a close connection command, for example.
- Fig. 1 illustrates a tactical communications network environment operating with an embodiment of the presently described technology.
- Fig. 2 shows the positioning of the data communications system in the seven layer OSI network model in accordance with an embodiment of the presently described technology.
- Fig. 3 depicts an example of multiple networks facilitated using the data communications system in accordance with an embodiment of the presently described technology.
- Fig. 4 illustrates a data communication environment operating with an embodiment of the present invention.
- Fig. 5 illustrates an example of a queue system for QoS operating above the transport layer in accordance with an embodiment of the presently described technology.
- Fig. 6 illustrates a flow diagram for a method for communicating data in accordance with an embodiment of the present invention.
- Fig. 1 illustrates a tactical communications network environment 100 operating with an embodiment of the presently described technology.
- the network environment 100 includes a plurality of communication nodes 110, one or more networks 120, one or more links 130 connecting the nodes and network(s), and one or more communication systems 150 facilitating communication over the components of the network environment 100.
- Communication nodes 110 may be and/or include radios, transmitters, satellites, receivers, workstations, servers, and/or other computing or processing devices, for example.
- Network (s) 120 may be hardware and/or software for transmitting data between nodes 110, for example.
- Network (s) 120 may include one or more nodes 110, for example.
- Link(s) 130 may be wired and/or wireless connections to allow transmissions between nodes 110 and/or network (s) 120.
- the communications system 150 may include software, firmware, and/or hardware used to facilitate data transmission among the nodes 110, networks 120, and links 130, for example. As illustrated in Fig. 1, communications system 150 may be implemented with respect to the nodes 110, network (s) 120, and/or links 130. In certain embodiments, every node 110 includes a communications system 150. In certain embodiments, one or more nodes 110 include a communications system 150. In certain embodiments, one or more nodes 110 may not include a communications system 150.
- the communication system 150 provides dynamic management of data to help assure communications on a tactical communications network, such as the network environment 100. As shown in Fig. 2, in certain embodiments, the system 150 operates as part of and/or at the top of the transport layer in the OSI seven layer protocol model. The system 150 may give precedence to higher priority data in the tactical network passed to the transport layer, for example. The system 150 may be used to facilitate communications in a single network, such as a local area network (LAN) or wide area network (WAN), or across multiple networks. An example of a multiple network system is shown in Fig. 3. The system 150 may be used to manage available bandwidth rather than add additional bandwidth to the network, for example.
- LAN local area network
- WAN wide area network
- the system 150 is a software system, although the system 150 may include both hardware and software components in various embodiments.
- the system 150 may be network hardware independent, for example. That is, the system 150 may be adapted to function on a variety of hardware and software platforms.
- the system 150 operates on the edge of the network rather than on nodes in the interior of the network. However, the system 150 may operate in the interior of the network as well, such as at "choke points" in the network.
- the system 150 may use rules and modes or profiles to perform throughput management functions such as optimizing available bandwidth, setting information priority, and managing data links in the network.
- optimizing bandwidth it is meant, for example, that the presently described technology may be employed to increase an efficiency of bandwidth use to communicate data in one or more networks.
- Optimizing bandwidth usage may include removing functionally redundant messages, message stream management or sequencing, and message compression, for example.
- Setting information priority may include differentiating message types at a finer granularity than Internet Protocol (IP) based techniques and sequencing messages onto a data stream via a selected rule- based sequencing algorithm, for example.
- Data link management may include rule-based analysis of network measurements to affect changes in rules, modes, and/or data transports, for example.
- a mode or profile may include a set of rules related to the operational needs for a particular network state of health or condition.
- the system 150 provides dynamic, w on- the-fly" reconfiguration of modes, including defining and switching to new modes on the fly.
- the communication system 150 may be configured to accommodate changing priorities and grades of service, for example, in a volatile, bandwidth-limited network.
- the system 150 may be configured to manage information for improved data flow to help increase response capabilities in the network and reduce communications latency. Additionally, the system 150 may provide interoperability via a flexible architecture that is upgradeable and scalable to improve availability / survivability, and reliability of communications.
- the system 150 supports a data communications architecture that may be autonomously adaptable to dynamically changing environments while using predefined and predictable system resources and bandwidth, for example.
- the system 150 provides throughput management to bandwidth-constrained tactical communications networks while remaining transparent to applications using the network.
- the system 150 provides throughput management across multiple users and environments at reduced complexity to the network.
- the system 150 runs on a host node in and/or at the top of layer four (the transport layer) of the OSI seven layer model and does not require specialized network hardware.
- the system 150 may operate transparently to the layer four interface. That is, an application may utilize a standard interface for the transport layer and be unaware of the operation of the system 150. For example, when an application opens a socket, the system 150 may filter data at this point in the protocol stack.
- the system 150 achieves transparency by allowing applications to use, for example, the TCP/IP socket interface that is provided by an operating system at a communication device on the network rather than an interface specific to the system 150.
- System 150 rules may be written in extensible markup language (XML) and/or provided via custom dynamic link libraries (DLLs), for example.
- the system 150 provides quality of service (QoS) on the edge of the network.
- QoS quality of service
- the system's QoS capability offers content-based, rule-based data prioritization on the edge of the network, for example. Prioritization may include differentiation and/or sequencing, for example.
- the system 150 may differentiate messages into queues based on user-configurable differentiation rules, for example.
- the messages are sequenced into a data stream in an order dictated by the user-configured sequencing rule (e.g., starvation, round robin, relative frequency, etc.).
- the user-configured sequencing rule e.g., starvation, round robin, relative frequency, etc.
- QoS on the edge
- data messages that are indistinguishable by traditional QoS approaches may be differentiated based on message content, for example.
- Rules may be implemented in XML, for example.
- the system 150 allows dynamic link libraries to be provided with custom code, for example.
- Inbound and/or outbound data on the network may be customized via the system 150.
- Prioritization protects client applications from high-volume, low-priority data, for example.
- the system 150 helps to ensure that applications receive data to support a particular operational scenario or constraint.
- the system when a host is connected to a LAN that includes a router as an interface to a bandwidth- constrained tactical network, the system may operate in a configuration known as QoS by proxy. In this configuration, packets that are bound for the local LAN bypass the system and immediately go to the LAN. The system applies QoS on the edge of the network to packets bound for the bandwidth-constrained tactical link.
- a profile may include a name or other identifier that allows the user or system to change to the named profile.
- a profile may also include one or more identifiers, such as a functional redundancy rule identifier, a differentiation rule identifier, an archival interface identifier, a sequencing rule identifier, a pre-transmit interface identifier, a post- transmit interface identifier, a transport identifier, and/or other identifier, for example.
- a functional redundancy rule identifier specifies a rule that detects functional redundancy, such as from stale data or substantially similar data, for example.
- a differentiation rule identifier specifies a rule that differentiates messages into queues for processing, for example.
- An archival interface identifier specifies an interface to an archival system, for example.
- a sequencing rule identifier identifies a sequencing algorithm that controls samples of queue fronts and, therefore, the sequencing of the data on the data stream.
- a pre-transmit interface identifier specifies the interface for pre-transmit processing, which provides for special processing such as encryption and compression, for example.
- a post-transmit interface identifier identifies an interface for post-transmit processing, which provides for processing such as de- encryption and decompression, for example.
- a transport identifier specifies a network interface for the selected transport.
- a profile may also include other information, such as queue sizing information, for example.
- Queue sizing information identifiers a number of queues and amount of memory and secondary storage dedicated to each queue, for example.
- the system 150 provides a rules-based "approach for optimizing bandwidth.
- the system 150 may employ queue selection rules to differentiate messages into message queues so that messages may be assigned a priority and an appropriate relative frequency on the data stream.
- the system 150 may use functional redundancy rules to manage functionally redundant messages. A message is functionally redundant if it is not different enough (as defined by the rule) from a previous message that has not yet been sent on the network, for example.
- a new message may be dropped, since the older message will carry functionally equivalent information and is further ahead in the queue.
- functional redundancy many include actual duplicate messages and newer messages that arrive before an older message has been sent.
- a node may receive identical copies of a particular message due to characteristics of the underlying network, such as a message that was sent by two different paths for fault tolerance reasons.
- a new message may contain data that supersedes an older message that has not yet been sent. In this situation, the system 150 may drop the older message and send only the new message.
- the system 150 may also include priority sequencing rules to determine a priority- based message sequence of the data stream. Additionally, the system 150 may include transmission processing rules to provide pre-transmission and post-transmission special processing, such as compression and/or encryption.
- the system 150 provides fault tolerance capability to help protect data integrity and reliability.
- the system 150 may use user-defined queue selection rules to differentiate messages into queues.
- the queues are sized according to a user-defined configuration, for example.
- the configuration specifies a maximum amount of memory a queue may consume, for example.
- the configuration may allow the user to specify a location and amount of secondary storage that may be used for queue overflow.
- messages may be queued in secondary storage.
- the system 150 may remove the oldest message in the queue, logs an error message, and queues the newest message. If archiving is enabled for the operational mode, then the de-queued message may be archived with an indicator that the message was not sent on the network.
- Memory and secondary storage for queues in the system 150 may be configured on a per-link basis for a specific application, for example. A longer time between periods of network availability may correspond to more memory and secondary storage to support network outages.
- the system 150 may be integrated with network modeling and simulation applications, for example, to help identify sizing to help ensure that queues are sized appropriately and time between outages is sufficient to help achieve steady-state and help avoid eventual queue overflow.
- the system 150 offers the capability to meter inbound (“shaping") and outbound (“policing”) data. Policing and shaping capabilities help address mismatches in timing in the network. Shaping helps to prevent network buffers form flooding with high- priority data queued up behind lower-priority data. Policing helps to prevent application data consumers from being overrun by low-priority data. Policing and shaping are governed by two parameters: effective link speed and link proportion.
- the system 150 may form a data stream that is no more than the effective link speed multiplied by the link proportion, for example. The parameters may be modified dynamically as the network changes.
- the system may also provide access to detected link speed to support application level decisions on data metering. Information provided by the system 150 may be combined with other network operations information to help decide what link speed is appropriate for a given network scenario.
- QoS may be provided to a communication network above the transport layer of the OSI protocol model.
- QoS technology may be implemented just below the socket layer of a transport protocol connection.
- the transport protocol may include a Transmission Control Protocol (TCP) , User Datagram Protocol (UDP) , or Stream Control Transmission Protocol (SCTP) , for example.
- TCP Transmission Control Protocol
- UDP User Datagram Protocol
- SCTP Stream Control Transmission Protocol
- the protocol type may include Internet Protocol (IP) , Internetwork Packet Exchange (IPX) , Ethernet, Asynchronous Transfer Mode (ATM) , File Transfer Protocol (FTP) , and/or Real-time Transport Protocol (RTP) .
- IP Internet Protocol
- IPX Internetwork Packet Exchange
- Ethernet Ethernet
- ATM Asynchronous Transfer Mode
- FTP File Transfer Protocol
- RTP Real-time Transport Protocol
- TCP Since TCP is connection-oriented, sockets are opened and closed via "open” and "close” commands to begin and end a data communication connection between nodes or other network elements.
- a TCP socket When a TCP socket is closed by an application that is utilizing QoS, prioritized data queued for transmission should be sent before the close command is executed by the network system. Otherwise, data that has been queued may be lost if the "close” is immediately honored by the system. To do this, the "close” is queued until relevant data is sent, and then the close is processed after the data has been transmitted via the connection.
- a close command may be queued with data to allow coordinated processing and transmission of data related to the open connection before the connection is terminated in response to the close command.
- a transport protocol is modified or otherwise manipulated so as to enable queuing or otherwise holding of system commands, such as close connection commands, in addition to data.
- certain embodiments queue up or otherwise hold/store the transport protocol mechanism in along with the data to maintain an order between the protocol mechanism and associated data. For example, a TCP close command is identified and queued with associated data for a
- Fig. 4 illustrates a data communication environment
- the environment 400 includes a data communication system 410, one or more source nodes 420, and one or more destination nodes 430.
- the data communication system 410 is in communication with the source node(s) 420 and the destination node(s) 430.
- the data communication system 410 may communicate with the source node(s) 420 and/or destination node(s) 430 over links, such as radio, satellite, network links, and/or through inter-process communication, for example.
- the data communication system 410 may communication with one or more source nodes 420 and/or destination nodes 430 over one or more tactical data networks .
- the data communication system 410 may be similar to the communication system 150, described above, for example.
- the data communication system 410 is adapted to receive data from the one or more source nodes 420.
- the data communication system 410 may include one or more queues for holding, storing, organizing, and/or prioritizing the data.
- other data structures may be used for holding, storing, organizing, and/or prioritizing the data. For example, a table, tree, or linked list may be used.
- the data communication system 410 is adapted to communicate data to the one or more destination nodes 430.
- the data received, stored, prioritized, processed, communicated, and/or otherwise transmitted by data communication system 410 may include a block of data.
- the block of data may be, for example, a packet, cell, frame, and/or stream of data.
- the data communication system 410 may receive packets of data from a source node 420.
- the data communication system 410 may process a stream of data from a source node 420.
- data includes a header and a payload.
- the header may include protocol information and time stamp information, for example.
- protocol information, time stamp information, content, and other information may be included in the payload.
- the data may or may not be contiguous in memory. That is, one or more portions of the data may be located in different regions of memory.
- data may include a pointer to another location containing data, for example.
- Source node(s) 420 provide and/or generate, at least in part, data handled by the data communication system 410.
- a source node 420 may include, for example, an application, radio, satellite, or network.
- the source node 420 may communicate with the data communication system 410 over a link, as discussed above.
- Source node(s) 420 may generate a continuous stream of data or may burst data, for example.
- the source node 420 and the data communication system 410 are part of the same system.
- the source node 420 may be an application running on the same computer system as the data communication system 410.
- Destination node(s) 430 receive data handled by the data communication system 410.
- a destination node 430 may include, for example, an application, radio, satellite, or network.
- the destination node 430 may communicate with the data communication system 410 over a link, as discussed above.
- the destination node 430 and the data communication system 410 are part of the same system.
- the destination node 430 may be an application running on the same computer system as the data communication system 410.
- the data communication system 410 may communicate with one or more source nodes 420 and/or destination nodes 430 over links, as discussed above.
- the one or more links may be part of a tactical data network.
- one or more links may be bandwidth constrained.
- one or more links may be unreliable and/or intermittently disconnected.
- a transport protocol such as TCP, opens a connection between sockets at a source node 420 and a destination node 430 to transmit data on a link from the source node 420 to the destination node 430.
- data is provided and/or generated by one or more data sources 420.
- the data is received at the data communication system 410.
- the data may be received over one or more links, for example.
- data may be received at the data communication system 410 from a radio over a tactical data network.
- data may be provided to the data communication system 410 by an application running on the same system by an inter-process communication mechanism.
- the data may be a block of data, for example.
- the data communication system 410 may organize and/or prioritize the data.
- the data communication system 410 may determine a priority for a block of data.
- a prioritization component of the data communication system 410 may determine a priority for that block of data.
- a block of data may be stored in a queue in the data communication system 410 and a prioritization component may extract the block of data from the queue based on a priority determined for the block of data and/or for the queue .
- the prioritization of the data by the data communication system 410 may be used to provide QoS, for example.
- the data communication system 410 may determine a priority for a data received over a tactical data network. The priority may be based on the source address of the data, for example. For example, a source IP address for the data from a radio of a member of the same platoon as the platoon the data communication system 410 belongs to may be given a higher priority than data originating from a unit in a different division in a different area of operations.
- the priority may be used to determine which of a plurality of queues the data should be placed into for subsequent communication by the data communication system 410.
- higher priority data may be placed in a queue intended to hold higher priority data, and in turn, the data communication system 410, in determining what data to next communicate may look first to the higher priority queue.
- the data may be prioritized based at least in part on one or more rules.
- the rules may be user defined.
- rules may be written in extensible markup language ("XML") and/or provided via custom dynamically linked libraries (“DLLs”), for example.
- Rules may be used to differentiate and/or sequence data on a network, for example.
- a rule may specify, for example, that data received using one protocol be favored over data utilizing another protocol.
- command data may utilize a particular protocol that is given priority, via a rule, over position telemetry data sent using another protocol.
- a rule may specify that position telemetry data coming from a first range of addresses may be given priority over position telemetry data coming from a second range of addresses.
- the first range of addresses may represent IP addresses of other aircraft in the same squadron as the aircraft with the data communication system 410 running on it, for example.
- the second range of addresses may then represent, for example, IP addresses for other aircraft that are in a different area of operations, and therefore of less interest to the aircraft on which the data communication system 410 is running.
- the data communication system 410 does not drop data. That is, although data may be low priority, it is not dropped by the data communication system 410. Rather, the data may be delayed for a period of time, potentially dependent on the amount of higher priority data that is received. In certain embodiments, data may be queued or otherwise stored, for example, to help ensure that the data is not lost or dropped until bandwidth is available to send the data.
- the data communication system 410 includes a mode or profile indicator.
- the mode indicator may represent the current mode or state of the data communication system 410, for example.
- the data communications system 410 may use rules and modes or profiles to perform throughput management , functions such as optimizing available bandwidth, setting information priority, and managing data links in the network. The different modes may affect changes in rules, modes, and/or data transports, for example.
- a mode or profile may include a set of rules related to the operational needs for a particular network state of health or condition.
- the data communication system 410 may provide dynamic reconfiguration of modes, including defining and switching to new modes "on-the-fIy, " for example.
- the data communication system 410 is transparent to other applications.
- the processing, organizing, and/or prioritization performed by the data communication system 410 may be transparent to one or more source nodes 420 or other applications or data sources.
- an application running on the same system as data communication system 410, or on a source node 420 connected to the data communication system 410 may be unaware of the prioritization of data performed by the data communication system 410.
- Data is communicated via the data communication system 410.
- the data may be communicated to one or more destination nodes 430, for example.
- the data may be communicated over one or more links, for example.
- the data may be communicated by the data communication system 410 over a tactical data network to a radio.
- data may be provided by the data communication system 410 to an application running on the same system by an inter-process communication mechanism.
- Fig. 5 illustrates an example of a queue system 500 for QoS operating above the transport layer in accordance with an embodiment of the presently described technology. While Fig. 5 is illustrated and described in terras of a queue, it is understood that alternative data structures may be used to hold data and protocol mechanisms similar to the queue system 500.
- the queue system 500 includes one or more queues 510- 515.
- the queue 510-515 includes an enqueue pointer 520 and a dequeue pointer 530.
- the queue 510-515 may also include data 540-541 and/or a close command 550, for example.
- the data 540-541 may include contiguous or noncontiguous portions of data.
- the data 540-541 may include one or more pointers to other locations containing data.
- queue 510 first illustrates an empty queue with no data enqueued. Then, one block of data 540 is enqueued in the queue 511. Next, queue 512 has two blocks of data 540-541 enqueued. Then, a close command 550 has been enqueued along with two blocks of data 540-541 in queue 513.
- the data blocks 540-541 are processed in the network while the close command 550 remains behind them in the queue 514.
- the data blocks 540-541 may be processed and transmitted in an order other than the order in which the blocks 540-541 were enqueued. Then, as shown in queue 515, the close command 550 is removed from the queue 515 and processed to close the data connection.
- a system such as data communication system 410, may manage a connection opened between a source node 420 and a destination node 430.
- System 410 may enqueue data transmitted via the connection and also enqueue protocol commands, such as transport protocol commands (e.g., "open connection” commands and "close connection” commands) .
- Protocol commands may be associated with a certain connection between nodes and with certain data.
- the system 410 helps to ensure that data associated with the connection is transmitted and/or otherwise processed before the protocol command is processed.
- data being transmitted via a TCP socket connection between source node 420 and destination node 430 is transmitted via the socket connection before a close command is processed to terminate the connection.
- the close command is enqueued behind the data for the connection, and, although the data for the connection may be processed and/or transmitted in varying orders depending upon priority and/or other rules, the close command is not processed until completion of the data processing. Once data for the connection has been processed, the close command is processed to terminate the TCP socket connection.
- a bandwidth- constrained network such as a tactical data network
- the aircraft may transmit a message to the ground radio by activating or opening a TCP socket connection, for example, between the aircraft radio and the ground radio. Transmission of data between the aircraft radio and the ground radio then begins. Data is enqueued or otherwise temporarily stored during the transmission process in order to prioritize the data based on content, protocol, and/or other criteria.
- the close command is stored or enqueued after the data to ensure that the data is prioritized and transmitted to the ground radio before the close command.
- the system helps to ensure that the communication connection is not prematurely ended, and data thereby lost, due to premature processing of the close command.
- other environment conditions may result in termination and/or interruption of the communication connection.
- queues and/or other data storage may be used to buffer data for resumed transmission in the event of an interruption in the communication connection.
- Fig. 6 illustrates a flow diagram for a method 600 for communicating data in accordance with an embodiment of the present invention.
- the method 600 includes the following steps, which will be described below in more detail.
- a connection is opened.
- data is received.
- data is enqueued.
- a close command is enqueued.
- data is dequeued and transmitted.
- the close command is dequeued and executed.
- the method 600 is described with reference to elements of systems described above, but it should be understood that other implementations are possible.
- a connection is opened.
- a connection is opened between two nodes in a communications network.
- a TCP connection may be opened between node sockets.
- Data is received.
- Data may be received at the data communication system 410, for example.
- the data may be received over one or more links, for example.
- the data may be provided and/or generated by one or more data sources 420, for example.
- data may be received at the data communication system 410 from a radio over a tactical data network.
- data may be provided to the data communication system 410 by an application running on the same system by an inter-process communication mechanism.
- the data may be a block of data, for example.
- the data communication system 410 may not receive all of the data. For example, some of the data may be stored in a buffer and the data communication system 410 may receive only header information and a pointer to the buffer.
- the data cominunication system 410 may be hooked into the protocol stack of an operating system, and, when an application passes data to the operating system through a transport layer interface (e.g., sockets), the operating system may then provide access to the data to the data communication system 410.
- a transport layer interface e.g., sockets
- Data is enqueued.
- Data may be enqueued by data communication system 410, for example.
- the data may be enqueued based on one or more rules or priorities established by the system 410, protocol used, and/or other mechanism, for example.
- the data may enqueued in the order in which it was received and/or in an alternate order, for example.
- data may be stored in one or more queues.
- the one or more queues may be assigned differing priorities and/or differing processing rules, for example.
- Data in the one or more queues may be prioritized.
- the data may be prioritized and/or organized by data communication system 410, for example.
- the data to be prioritized may be the data that is received at step 620, for example.
- Data may be prioritized before and/or after the data is enqueued, for example.
- the data communication system 410 may determine a priority for a block of data. For example, when a block of data is received by the data communication system 410, a prioritization component of the data communication system 410 may determine a priority for that block of data.
- a block of data may be stored in a queue in the data communication system 410 and a prioritization component may extract the block of data from the queue based on a priority determined for the block of data and/or for the queue.
- the priority of the block of data may be based at least in part on protocol information associated and/or included in the block of data.
- the protocol information may be similar to the protocol information described above, for example.
- the data communication system 410 may determine a priority for a block of data based on the source address of the block of data.
- the data communication system 410 may- determine a priority for a block of data based on the transport protocol used to communicate the block of data.
- Data priority may also be determined based at least in part on data content, for example.
- the prioritization of the data may be used to provide QoS, for example.
- the data communication system 410 may determine a priority for a data received over a tactical data network. The priority may be based on the source address of the data, for example. For example, a source IP address for the data from a radio of a member of the same platoon as the platoon the data communication system 410 belongs to may be given a higher priority than data originating from a unit in a different division in a different area of operations. The priority may be used to determine which of a plurality of queues the data should be placed into for subsequent communication by the data communication system 410.
- higher priority data may be placed in a queue intended to hold higher priority data, and in turn, the data communication system 410, in determining what data to next communicate, may look first to the higher priority queue.
- the data may be prioritized based at least in part on one or more rules.
- the rules may be user defined and/or programmed based on system and/or operational constraints, for example.
- rules may be written in XML and/or provided via custom DLLs, for example.
- a rule may specify, for example, that data received using one protocol be favored over data utilizing another protocol.
- command data may utilize a particular protocol that is given priority, via a rule, over position telemetry data sent using another protocol.
- a rule may specify that position telemetry data coming from a first range of addresses may be given priority over position telemetry data coming from a second range of addresses.
- the first range of addresses may represent IP addresses of other aircraft in the same squadron as the aircraft with the data communication system 410 running on it, for example.
- the second range of addresses may then represent, for example, IP addresses for other aircraft that are in a different area of operations, and therefore of less interest to the aircraft on which the data communication system 410 is running.
- the data to be prioritized is not dropped. That is, although data may be low priority, it is not dropped by the data communication system 410. Rather, the data may be delayed for a period of time, potentially dependent on the amount of higher priority data that is received.
- a mode or profile indicator may represent the current mode or state of the data communication system 410, for example.
- the rules and modes or profiles may be used to perform throughput management functions such as optimizing available bandwidth, setting information priority, and managing data links in the network.
- the different modes may affect changes in rules, modes, and/or data transports, for example.
- a mode or profile may include a set of rules related to the operational needs for a particular network state of health or condition.
- the data communication system 410 may provide dynamic reconfiguration of modes, including defining and switching to new modes "on-the-fIy, " for example.
- the prioritization of data is transparent to other applications.
- the processing, organizing, and/or prioritization performed by the data communication system 410 may be transparent to one or more source nodes 420 or other applications or data sources.
- an application running on the same system as data communication system 410, or on a source node 420 connected to the data communication system 410 may be unaware of the prioritization of data performed by the data communication system 410.
- a system or protocol command such as a transport protocol open or close command
- a protocol mechanism such as a TCP close command
- a close command for a connection may be stored in the same queue as data associated with the connection.
- the command may be stored in a different queue from associated data.
- data is dequeued.
- the data may be dequeued and transmitted, for example.
- the data dequeued may be the data received at step 620, for example.
- the data dequeued may be the data enqueued at step 630, for example.
- Data may be prioritized before and/or during transmission, as described above.
- Data may be communicated from the data communication system 410, for example.
- the data may be transmitted to one or more destination nodes 430, for example.
- the data may be communicated over one or more links, for example.
- the data may be communicated by the data communication system 410 over a tactical data network to a radio.
- data may be provided by the data communication system 410 to an application running on the same system by an inter-process communication mechanism.
- Data may be transmitted via a TCP socket connection, for ' example.
- a command is dequeued.
- the command may be the command enqueued at step 640, for example.
- the command is dequeued after data associated with the command and/or a connection associated with the command has been dequeued and transmitted.
- a close connection command may be dequeued after data associated with the connection has been dequeued and transmitted via the connection.
- One or more of the steps of the method 600 may be implemented alone or in combination in hardware, firmware, and/or as a set of instructions in software, for example.
- Certain embodiments may be provided as a set of instructions residing on a computer-readable medium, such as a memory, hard disk, DVD, or CD, for execution on a general purpose computer or other processing device. Certain embodiments of the present invention may omit one or more of these steps and/or perform the steps in a different order than the order listed. For example, some steps may not be performed in certain embodiments of the present invention. As a further example, certain steps may be performed in a different temporal order, including simultaneously, than listed above.
- certain embodiments of the present invention provide systems and methods for queuing data and protocol mechanism commands for QoS. Certain embodiments provide a technical effect of helping to ensure that a connection is not prematurely closed by a protocol command before QoS and data transmission is completed for that connection.
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2007800227460A CN101502055B (en) | 2006-05-02 | 2007-05-01 | Systems and methods for close queuing to support quality of service |
EP07776572.5A EP2022202A4 (en) | 2006-05-02 | 2007-05-01 | Systems and methods for close queuing to support quality of service |
CA2650909A CA2650909C (en) | 2006-05-02 | 2007-05-01 | Systems and methods for close queuing to support quality of service |
JP2009509666A JP4659116B2 (en) | 2006-05-02 | 2007-05-01 | Closed queue system and method for supporting quality of service |
KR1020087029016A KR101102178B1 (en) | 2006-05-02 | 2007-05-01 | Method for data communication and computer readable medium thereof |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/415,914 US7756134B2 (en) | 2006-05-02 | 2006-05-02 | Systems and methods for close queuing to support quality of service |
US11/415,914 | 2006-05-02 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2007130413A2 true WO2007130413A2 (en) | 2007-11-15 |
WO2007130413A3 WO2007130413A3 (en) | 2009-04-09 |
Family
ID=38661137
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/010557 WO2007130413A2 (en) | 2006-05-02 | 2007-05-01 | Systems and methods for close queuing to support quality of service |
Country Status (8)
Country | Link |
---|---|
US (1) | US7756134B2 (en) |
EP (1) | EP2022202A4 (en) |
JP (1) | JP4659116B2 (en) |
KR (1) | KR101102178B1 (en) |
CN (1) | CN101502055B (en) |
CA (1) | CA2650909C (en) |
TW (1) | TWI353151B (en) |
WO (1) | WO2007130413A2 (en) |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8064464B2 (en) * | 2006-06-16 | 2011-11-22 | Harris Corporation | Method and system for inbound content-based QoS |
US8195118B2 (en) | 2008-07-15 | 2012-06-05 | Linear Signal, Inc. | Apparatus, system, and method for integrated phase shifting and amplitude control of phased array signals |
US8872719B2 (en) | 2009-11-09 | 2014-10-28 | Linear Signal, Inc. | Apparatus, system, and method for integrated modular phased array tile configuration |
JP5849772B2 (en) * | 2012-02-29 | 2016-02-03 | 日本電気株式会社 | Information processing apparatus and information processing method |
CN102624926B (en) * | 2012-04-11 | 2016-02-10 | 中兴通讯股份有限公司 | The method and system that ability polymerization is open |
US20140222995A1 (en) * | 2013-02-07 | 2014-08-07 | Anshuman Razden | Methods and System for Monitoring Computer Users |
US9836047B2 (en) | 2015-06-10 | 2017-12-05 | Kespry, Inc. | Aerial vehicle data communication system |
EP3335377B1 (en) | 2015-08-13 | 2020-01-15 | BAE Systems PLC | Apparatus and method for communications management |
ES2760352T3 (en) | 2015-08-13 | 2020-05-13 | Bae Systems Plc | Apparatus and method for communications management |
EP3335333B1 (en) | 2015-08-13 | 2019-10-09 | BAE Systems PLC | Apparatus and method for communications management |
WO2017025742A1 (en) | 2015-08-13 | 2017-02-16 | Bae Systems Plc | Apparatus and method for communications management |
US10368289B2 (en) | 2015-08-13 | 2019-07-30 | Bae Systems Plc | Apparatus and method for communications management |
WO2017025713A1 (en) | 2015-08-13 | 2017-02-16 | Bae Systems Plc | Apparatus and method for communications management |
EP3335331B1 (en) * | 2015-08-13 | 2022-03-02 | BAE Systems PLC | Apparatus and method for communications management |
US10341002B2 (en) | 2015-08-13 | 2019-07-02 | Bae Systems Plc | Apparatus and method for communications management |
JP6343366B1 (en) * | 2017-04-21 | 2018-06-13 | 株式会社Aerial Lab Industries | Information transmission method at the time of disaster |
DE102020131072A1 (en) * | 2020-11-24 | 2022-05-25 | Rheinmetall Electronics Gmbh | Network module, electronic system and communication network |
Family Cites Families (254)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU4821993A (en) * | 1992-10-05 | 1994-04-26 | Nokia Telecommunications Oy | Method for interconnecting local area networks or network segments and a local area network bridge |
US5655140A (en) * | 1994-07-22 | 1997-08-05 | Network Peripherals | Apparatus for translating frames of data transferred between heterogeneous local area networks |
US5627970A (en) * | 1994-08-08 | 1997-05-06 | Lucent Technologies Inc. | Methods and apparatus for achieving and maintaining optimum transmission rates and preventing data loss in a processing system nework |
US5559999A (en) * | 1994-09-09 | 1996-09-24 | Lsi Logic Corporation | MPEG decoding system including tag list for associating presentation time stamps with encoded data units |
US5664091A (en) * | 1995-08-31 | 1997-09-02 | Ncr Corporation | Method and system for a voiding unnecessary retransmissions using a selective rejection data link protocol |
US5844600A (en) * | 1995-09-15 | 1998-12-01 | General Datacomm, Inc. | Methods, apparatus, and systems for transporting multimedia conference data streams through a transport network |
US5960035A (en) * | 1995-09-29 | 1999-09-28 | Motorola Inc. | Method and apparatus for load balancing for a processor operated data communications device |
US6507864B1 (en) | 1996-08-02 | 2003-01-14 | Symbol Technologies, Inc. | Client-server software for controlling data collection device from host computer |
US6091725A (en) * | 1995-12-29 | 2000-07-18 | Cisco Systems, Inc. | Method for traffic management, traffic prioritization, access control, and packet forwarding in a datagram computer network |
US6301527B1 (en) * | 1996-04-03 | 2001-10-09 | General Electric Company | Utilities communications architecture compliant power management control system |
US5949758A (en) * | 1996-06-27 | 1999-09-07 | International Business Machines Corporation | Bandwidth reservation for multiple file transfer in a high speed communication network |
US6205486B1 (en) * | 1996-07-26 | 2001-03-20 | Accton Technology Corporation | Inter-network bridge connector provided for dynamically prioritizing frame transmission adaptive to current network transmission-state |
US6067557A (en) * | 1996-09-06 | 2000-05-23 | Cabletron Systems, Inc. | Method and system for allocating CPU bandwidth by prioritizing competing processes |
US6072781A (en) | 1996-10-22 | 2000-06-06 | International Business Machines Corporation | Multi-tasking adapter for parallel network applications |
US6075770A (en) * | 1996-11-20 | 2000-06-13 | Industrial Technology Research Institute | Power spectrum-based connection admission control for ATM networks |
JP3213697B2 (en) | 1997-01-14 | 2001-10-02 | 株式会社ディジタル・ビジョン・ラボラトリーズ | Relay node system and relay control method in the relay node system |
US6404776B1 (en) * | 1997-03-13 | 2002-06-11 | 8 × 8, Inc. | Data processor having controlled scalable input data source and method thereof |
US6028843A (en) * | 1997-03-25 | 2000-02-22 | International Business Machines Corporation | Earliest deadline first communications cell scheduler and scheduling method for transmitting earliest deadline cells first |
US6192406B1 (en) * | 1997-06-13 | 2001-02-20 | At&T Corp. | Startup management system and method for networks |
US6078565A (en) | 1997-06-20 | 2000-06-20 | Digital Equipment Corporation | Method and apparatus to expand an on chip FIFO into local memory |
US6181711B1 (en) * | 1997-06-26 | 2001-01-30 | Cisco Systems, Inc. | System and method for transporting a compressed video and data bit stream over a communication channel |
US6937566B1 (en) * | 1997-07-25 | 2005-08-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Dynamic quality of service reservation in a mobile communications network |
US6343085B1 (en) * | 1997-08-28 | 2002-01-29 | Microsoft Corporation | Adaptive bandwidth throttling for individual virtual services supported on a network server |
WO1999013676A2 (en) * | 1997-09-12 | 1999-03-18 | Williams Wireless, Inc. | Wide area telemetry network |
US6044419A (en) * | 1997-09-30 | 2000-03-28 | Intel Corporation | Memory handling system that backfills dual-port buffer from overflow buffer when dual-port buffer is no longer full |
US6407998B1 (en) | 1997-10-02 | 2002-06-18 | Thomson Licensing S.A. | Multimedia decoder for prioritized bi-directional communication in a broadcast system |
US6363411B1 (en) * | 1998-08-05 | 2002-03-26 | Mci Worldcom, Inc. | Intelligent network |
US6233248B1 (en) * | 1997-10-14 | 2001-05-15 | Itt Manufacturing Enterprises, Inc. | User data protocol for internet data communications |
US6170075B1 (en) * | 1997-12-18 | 2001-01-02 | 3Com Corporation | Data and real-time media communication over a lossy network |
US5941972A (en) | 1997-12-31 | 1999-08-24 | Crossroads Systems, Inc. | Storage router and method for providing virtual local storage |
JP3448481B2 (en) * | 1998-03-05 | 2003-09-22 | Kddi株式会社 | TCP communication speed-up device for asymmetric line |
AU3085799A (en) * | 1998-03-12 | 1999-09-27 | Dmw Worldwide, Inc. | Operational system for operating on client defined rules |
US6560592B1 (en) * | 1998-03-19 | 2003-05-06 | Micro Data Base Systems, Inc. | Multi-model computer database storage system with integrated rule engine |
US6236656B1 (en) * | 1998-03-19 | 2001-05-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Link-efficiency based scheduling in radio data communications systems |
US6247058B1 (en) * | 1998-03-30 | 2001-06-12 | Hewlett-Packard Company | Method and apparatus for processing network packets using time stamps |
US6279035B1 (en) * | 1998-04-10 | 2001-08-21 | Nortel Networks Limited | Optimizing flow detection and reducing control plane processing in a multi-protocol over ATM (MPOA) system |
US6625135B1 (en) | 1998-05-11 | 2003-09-23 | Cargenie Mellon University | Method and apparatus for incorporating environmental information for mobile communications |
US6154778A (en) * | 1998-05-19 | 2000-11-28 | Hewlett-Packard Company | Utility-based multi-category quality-of-service negotiation in distributed systems |
US6343318B1 (en) * | 1998-05-29 | 2002-01-29 | Palm, Inc. | Method and apparatus for communicating information over low bandwidth communications networks |
US6397259B1 (en) * | 1998-05-29 | 2002-05-28 | Palm, Inc. | Method, system and apparatus for packet minimized communications |
US6590588B2 (en) * | 1998-05-29 | 2003-07-08 | Palm, Inc. | Wireless, radio-frequency communications using a handheld computer |
US6157955A (en) * | 1998-06-15 | 2000-12-05 | Intel Corporation | Packet processing system including a policy engine having a classification unit |
CN1214689C (en) | 1998-06-19 | 2005-08-10 | 杜松网络公司 | Device for performing IP forwarding and ATM switching |
US6952416B1 (en) | 1998-06-22 | 2005-10-04 | Nortel Networks Limited | Treatments in a distributed communications system |
US6625650B2 (en) | 1998-06-27 | 2003-09-23 | Intel Corporation | System for multi-layer broadband provisioning in computer networks |
US6862622B2 (en) | 1998-07-10 | 2005-03-01 | Van Drebbel Mariner Llc | Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture |
US6680922B1 (en) | 1998-07-10 | 2004-01-20 | Malibu Networks, Inc. | Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system |
US6640248B1 (en) * | 1998-07-10 | 2003-10-28 | Malibu Networks, Inc. | Application-aware, quality of service (QoS) sensitive, media access control (MAC) layer |
JP2002522962A (en) * | 1998-08-04 | 2002-07-23 | エイ・ティ・アンド・ティ・コーポレーション | Network resource allocation method |
US6618385B1 (en) * | 1998-09-23 | 2003-09-09 | Cirrus Logic, Inc. | High performance, high bandwidth, and adaptive local area network communications |
US6563517B1 (en) * | 1998-10-02 | 2003-05-13 | International Business Machines Corp. | Automatic data quality adjustment to reduce response time in browsing |
US6421335B1 (en) | 1998-10-26 | 2002-07-16 | Nokia Telecommunications, Oy | CDMA communication system and method using priority-based SIMA quality of service class |
US6819655B1 (en) * | 1998-11-09 | 2004-11-16 | Applied Digital Access, Inc. | System and method of analyzing network protocols |
US6614781B1 (en) * | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US6490249B1 (en) * | 1998-12-01 | 2002-12-03 | Nortel Networks Limited | Adaptive connection admission control scheme for packet networks |
US6643260B1 (en) | 1998-12-18 | 2003-11-04 | Cisco Technology, Inc. | Method and apparatus for implementing a quality of service policy in a data communications network |
US6691168B1 (en) | 1998-12-31 | 2004-02-10 | Pmc-Sierra | Method and apparatus for high-speed network rule processing |
DE60024228T2 (en) | 1999-01-08 | 2006-08-10 | Nortel Networks Ltd., St. Laurent | DYNAMIC ASSIGNMENT TRAFFIC CLASSES ON A PRIORITY MAINTENANCE JUMP IN A PACKAGE TRANSPORT DEVICE |
US6856627B2 (en) * | 1999-01-15 | 2005-02-15 | Cisco Technology, Inc. | Method for routing information over a network |
US6912221B1 (en) * | 1999-01-15 | 2005-06-28 | Cisco Technology, Inc. | Method of providing network services |
US6498782B1 (en) * | 1999-02-03 | 2002-12-24 | International Business Machines Corporation | Communications methods and gigabit ethernet communications adapter providing quality of service and receiver connection speed differentiation |
AU3529500A (en) | 1999-03-17 | 2000-10-04 | Broadcom Corporation | Network switch |
US7145869B1 (en) | 1999-03-17 | 2006-12-05 | Broadcom Corporation | Method for avoiding out-of-ordering of frames in a network switch |
US6600744B1 (en) | 1999-03-23 | 2003-07-29 | Alcatel Canada Inc. | Method and apparatus for packet classification in a data communication system |
US6950441B1 (en) | 1999-03-30 | 2005-09-27 | Sonus Networks, Inc. | System and method to internetwork telecommunication networks of different protocols |
US6584466B1 (en) * | 1999-04-07 | 2003-06-24 | Critical Path, Inc. | Internet document management system and methods |
US6587875B1 (en) | 1999-04-30 | 2003-07-01 | Microsoft Corporation | Network protocol and associated methods for optimizing use of available bandwidth |
US6438603B1 (en) | 1999-04-30 | 2002-08-20 | Microsoft Corporation | Methods and protocol for simultaneous tuning of reliable and non-reliable channels of a single network communication link |
US6700871B1 (en) | 1999-05-04 | 2004-03-02 | 3Com Corporation | Increased throughput across data network interface by dropping redundant packets |
US6519225B1 (en) | 1999-05-14 | 2003-02-11 | Nortel Networks Limited | Backpressure mechanism for a network device |
SE522068C2 (en) * | 1999-07-15 | 2004-01-13 | Ericsson Telefon Ab L M | Method and apparatus for providing radio access carrier services |
US20030195983A1 (en) | 1999-05-24 | 2003-10-16 | Krause Michael R. | Network congestion management using aggressive timers |
US6542593B1 (en) | 1999-06-02 | 2003-04-01 | Accenture Llp | Rules database server in a hybrid communication system architecture |
US6591301B1 (en) * | 1999-06-07 | 2003-07-08 | Nortel Networks Limited | Methods and systems for controlling network gatekeeper message processing |
US6907243B1 (en) * | 1999-06-09 | 2005-06-14 | Cisco Technology, Inc. | Method and system for dynamic soft handoff resource allocation in a wireless network |
US6628654B1 (en) * | 1999-07-01 | 2003-09-30 | Cisco Technology, Inc. | Dispatching packets from a forwarding agent using tag switching |
US6983350B1 (en) | 1999-08-31 | 2006-01-03 | Intel Corporation | SDRAM controller for parallel processor architecture |
US6715145B1 (en) * | 1999-08-31 | 2004-03-30 | Accenture Llp | Processing pipeline in a base services pattern environment |
US6332163B1 (en) * | 1999-09-01 | 2001-12-18 | Accenture, Llp | Method for providing communication services over a computer network system |
US6807648B1 (en) | 1999-09-13 | 2004-10-19 | Verizon Laboratories Inc. | Variable-strength error correction in ad-hoc networks |
US6598034B1 (en) | 1999-09-21 | 2003-07-22 | Infineon Technologies North America Corp. | Rule based IP data processing |
US6934795B2 (en) | 1999-09-23 | 2005-08-23 | Netlogic Microsystems, Inc. | Content addressable memory with programmable word width and programmable priority |
US6754185B1 (en) * | 1999-09-27 | 2004-06-22 | Koninklijke Philips Electronics N.V. | Multi link layer to single physical layer interface in a node of a data communication system |
JP3583667B2 (en) * | 1999-09-30 | 2004-11-04 | 株式会社東芝 | Wireless terminal device, data transfer method, and control information notification method |
JP2001111629A (en) * | 1999-10-12 | 2001-04-20 | Nec Corp | Access network |
US6934250B1 (en) * | 1999-10-14 | 2005-08-23 | Nokia, Inc. | Method and apparatus for an output packet organizer |
US6882642B1 (en) * | 1999-10-14 | 2005-04-19 | Nokia, Inc. | Method and apparatus for input rate regulation associated with a packet processing pipeline |
US6820117B1 (en) * | 1999-10-18 | 2004-11-16 | Sun Microsystems, Inc. | Bandwidth management |
US6687698B1 (en) * | 1999-10-18 | 2004-02-03 | Fisher Rosemount Systems, Inc. | Accessing and updating a configuration database from distributed physical locations within a process control system |
WO2001035243A1 (en) | 1999-11-08 | 2001-05-17 | Megaxess, Inc. | QUALITY OF SERVICE (QoS) NEGOTIATION PROCEDURE FOR MULTI-TRANSPORT PROTOCOL ACCESS FOR SUPPORTING MULTI-MEDIA APPLICATIONS WITH QoS ASSURANCE |
US6778530B1 (en) | 1999-11-08 | 2004-08-17 | Juniper Networks, Inc. | Method and apparatus for multiple field matching in network device |
US6650902B1 (en) * | 1999-11-15 | 2003-11-18 | Lucent Technologies Inc. | Method and apparatus for wireless telecommunications system that provides location-based information delivery to a wireless mobile unit |
US6859465B1 (en) * | 1999-11-22 | 2005-02-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for constant throughput rate adaptation |
US7149222B2 (en) * | 1999-12-21 | 2006-12-12 | Converged Access, Inc. | Integrated access point network device |
US6854009B1 (en) * | 1999-12-22 | 2005-02-08 | Tacit Networks, Inc. | Networked computer system |
US6952824B1 (en) | 1999-12-30 | 2005-10-04 | Intel Corporation | Multi-threaded sequenced receive for fast network port stream of packets |
US6557053B1 (en) | 2000-01-04 | 2003-04-29 | International Business Machines Corporation | Queue manager for a buffer |
JP3732989B2 (en) * | 2000-01-12 | 2006-01-11 | 富士通株式会社 | Packet switch device and scheduling control method |
US20020062395A1 (en) | 2000-01-21 | 2002-05-23 | David Thompson | Browser and network optimization systems and methods |
US6873600B1 (en) | 2000-02-04 | 2005-03-29 | At&T Corp. | Consistent sampling for network traffic measurement |
US6778546B1 (en) | 2000-02-14 | 2004-08-17 | Cisco Technology, Inc. | High-speed hardware implementation of MDRR algorithm over a large number of queues |
WO2001063486A2 (en) | 2000-02-24 | 2001-08-30 | Findbase, L.L.C. | Method and system for extracting, analyzing, storing, comparing and reporting on data stored in web and/or other network repositories and apparatus to detect, prevent and obfuscate information removal from information servers |
US6934752B1 (en) * | 2000-03-23 | 2005-08-23 | Sharewave, Inc. | Quality of service extensions for multimedia applications in wireless computer networks |
US6760309B1 (en) * | 2000-03-28 | 2004-07-06 | 3Com Corporation | Method of dynamic prioritization of time sensitive packets over a packet based network |
US6687735B1 (en) * | 2000-05-30 | 2004-02-03 | Tranceive Technologies, Inc. | Method and apparatus for balancing distributed applications |
US6772223B1 (en) | 2000-04-10 | 2004-08-03 | International Business Machines Corporation | Configurable classification interface for networking devices supporting multiple action packet handling rules |
US6940808B1 (en) * | 2000-04-13 | 2005-09-06 | Nortel Networks Limited | Adaptive rate traffic recovery mechanism for communication networks |
US6862265B1 (en) | 2000-04-13 | 2005-03-01 | Advanced Micro Devices, Inc. | Weighted fair queuing approximation in a network switch using weighted round robin and token bucket filter |
US6904014B1 (en) * | 2000-04-27 | 2005-06-07 | Cisco Technology, Inc. | Method and apparatus for performing high-speed traffic shaping |
US6556982B1 (en) | 2000-04-28 | 2003-04-29 | Bwxt Y-12, Llc | Method and system for analyzing and classifying electronic information |
WO2001084313A2 (en) * | 2000-05-02 | 2001-11-08 | Sun Microsystems, Inc. | Method and system for achieving high availability in a networked computer system |
US20020009060A1 (en) | 2000-05-05 | 2002-01-24 | Todd Gross | Satellite transceiver card for bandwidth on demand applications |
US6922724B1 (en) * | 2000-05-08 | 2005-07-26 | Citrix Systems, Inc. | Method and apparatus for managing server load |
US6823385B2 (en) * | 2000-05-19 | 2004-11-23 | Scientifc Atlanta, Inc. | Allocating access across a shared communications medium to user classes |
US6937561B2 (en) * | 2000-06-02 | 2005-08-30 | Agere Systems Inc. | Method and apparatus for guaranteeing data transfer rates and enforcing conformance with traffic profiles in a packet network |
US7032031B2 (en) | 2000-06-23 | 2006-04-18 | Cloudshield Technologies, Inc. | Edge adapter apparatus and method |
US6832239B1 (en) * | 2000-07-07 | 2004-12-14 | International Business Machines Corporation | Systems for managing network resources |
US20020038373A1 (en) | 2000-07-21 | 2002-03-28 | John Border | Method and system for improving network performance enhancing proxy architecture with gateway redundancy |
US6910074B1 (en) * | 2000-07-24 | 2005-06-21 | Nortel Networks Limited | System and method for service session management in an IP centric distributed network |
US6671732B1 (en) | 2000-07-24 | 2003-12-30 | Comverse Ltd. | Method and apparatus for control of content based rich media streaming |
US6904054B1 (en) * | 2000-08-10 | 2005-06-07 | Verizon Communications Inc. | Support for quality of service and vertical services in digital subscriber line domain |
US6845100B1 (en) * | 2000-08-28 | 2005-01-18 | Nokia Mobile Phones Ltd. | Basic QoS mechanisms for wireless transmission of IP traffic |
US6728749B1 (en) | 2000-09-05 | 2004-04-27 | The United States Of America As Represented By The Secretary Of The Army | Adaptive scheduling technique for mission critical systems |
US6865153B1 (en) * | 2000-09-20 | 2005-03-08 | Alcatel | Stage-implemented QoS shaping for data communication switch |
EP1193938A1 (en) | 2000-09-29 | 2002-04-03 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system for transmitting data |
US6822940B1 (en) | 2000-09-29 | 2004-11-23 | Cisco Technology, Inc. | Method and apparatus for adapting enforcement of network quality of service policies based on feedback about network conditions |
US6832118B1 (en) * | 2000-09-29 | 2004-12-14 | Rockwell Automation Technologies, Inc. | Programmable network control component and system of components |
WO2002030066A1 (en) | 2000-10-03 | 2002-04-11 | U4Ea Technologies Limited | Packet sequence control |
US7023851B2 (en) | 2000-10-12 | 2006-04-04 | Signafor, Inc. | Advanced switching mechanism for providing high-speed communications with high Quality of Service |
US20020191253A1 (en) | 2000-10-26 | 2002-12-19 | Dah Yang Toy Industrial Co., Ltd. | Method and apparatus for remote control |
US6640184B1 (en) * | 2000-11-10 | 2003-10-28 | Motorola, Inc. | Method and apparatus for providing location information |
US6888806B1 (en) | 2000-11-22 | 2005-05-03 | Motorola, Inc. | Method and system for scheduling packets for transmission from a wireless communication platform |
US6890854B2 (en) | 2000-11-29 | 2005-05-10 | Chartered Semiconductor Manufacturing, Inc. | Method and apparatus for performing nickel salicidation |
US6741562B1 (en) * | 2000-12-15 | 2004-05-25 | Tellabs San Jose, Inc. | Apparatus and methods for managing packets in a broadband data stream |
US6947996B2 (en) * | 2001-01-29 | 2005-09-20 | Seabridge, Ltd. | Method and system for traffic control |
US6671589B2 (en) | 2001-02-13 | 2003-12-30 | William Holst | Method and apparatus to support remote and automatically initiated data loading and data acquisition of airborne computers using a wireless spread spectrum aircraft data services link |
US6952407B2 (en) | 2001-02-22 | 2005-10-04 | Snowshore Networks, Inc. | Minimizing latency with content-based adaptive buffering |
US6947378B2 (en) * | 2001-02-28 | 2005-09-20 | Mitsubishi Electric Research Labs, Inc. | Dynamic network resource allocation using multimedia content features and traffic features |
US7042843B2 (en) | 2001-03-02 | 2006-05-09 | Broadcom Corporation | Algorithm for time based queuing in network traffic engineering |
US6459687B1 (en) | 2001-03-05 | 2002-10-01 | Ensemble Communications, Inc. | Method and apparatus for implementing a MAC coprocessor in a communication system |
US6928085B2 (en) * | 2001-03-12 | 2005-08-09 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for providing quality of service and contention resolution in ad-hoc communication systems |
EP1386432A4 (en) | 2001-03-21 | 2009-07-15 | John A Stine | An access and routing protocol for ad hoc networks using synchronous collision resolution and node state dissemination |
US6957258B2 (en) | 2001-03-28 | 2005-10-18 | Netrake Corporation | Policy gateway |
US6914882B2 (en) * | 2001-03-30 | 2005-07-05 | Nokia, Inc. | Method and apparatus for improved queuing |
US6944168B2 (en) * | 2001-05-04 | 2005-09-13 | Slt Logic Llc | System and method for providing transformation of multi-protocol packets in a data stream |
US6928471B2 (en) * | 2001-05-07 | 2005-08-09 | Quest Software, Inc. | Method and apparatus for measurement, analysis, and optimization of content delivery |
US20020188871A1 (en) | 2001-06-12 | 2002-12-12 | Corrent Corporation | System and method for managing security packet processing |
US7095715B2 (en) | 2001-07-02 | 2006-08-22 | 3Com Corporation | System and method for processing network packet flows |
US6732228B1 (en) | 2001-07-19 | 2004-05-04 | Network Elements, Inc. | Multi-protocol data classification using on-chip CAM |
US20030016625A1 (en) | 2001-07-23 | 2003-01-23 | Anees Narsinh | Preclassifying traffic during periods of oversubscription |
US6912231B2 (en) | 2001-07-26 | 2005-06-28 | Northrop Grumman Corporation | Multi-broadcast bandwidth control system |
US6937154B2 (en) * | 2001-08-21 | 2005-08-30 | Tabula Rasa, Inc. | Method and apparatus for facilitating personal attention via wireless links |
WO2003026319A2 (en) * | 2001-09-21 | 2003-03-27 | Nokia Corporation | System and method for enabling mobile edge services |
US7218610B2 (en) | 2001-09-27 | 2007-05-15 | Eg Technology, Inc. | Communication system and techniques for transmission from source to destination |
EP1300991A1 (en) | 2001-10-02 | 2003-04-09 | Lucent Technologies Inc. | A method for filtering redundant data packets |
US7251242B2 (en) | 2001-10-04 | 2007-07-31 | Siemens Aktiengesellschaft | Distributed transmission of traffic flows in communication networks |
US20030158963A1 (en) | 2002-02-20 | 2003-08-21 | Sturdy James T. | Smartbridge for tactical network routing applications |
US7200144B2 (en) | 2001-10-18 | 2007-04-03 | Qlogic, Corp. | Router and methods using network addresses for virtualization |
EP1456778A4 (en) * | 2001-10-26 | 2006-05-24 | Zeosoft Technology Group Inc | System for development, management and operation of distributed clients and servers |
JP2003152544A (en) | 2001-11-12 | 2003-05-23 | Sony Corp | Data communication system, data transmitter, data receiver, data-receiving method and computer program |
JP3726741B2 (en) * | 2001-11-16 | 2005-12-14 | 日本電気株式会社 | Packet transfer apparatus, method and program |
US7224703B2 (en) | 2001-12-12 | 2007-05-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for segmenting a data packet |
CN1739101A (en) | 2001-12-15 | 2006-02-22 | 汤姆森许可公司 | System and method for delivering data streams of multiple data types at diffferent priority levels |
DE10200165A1 (en) | 2002-01-04 | 2003-07-10 | Klaus Rock | Method for reducing the latency in interactive data communication via a satellite network |
US6801940B1 (en) | 2002-01-10 | 2004-10-05 | Networks Associates Technology, Inc. | Application performance monitoring expert |
US7149898B2 (en) | 2002-01-14 | 2006-12-12 | Sun Microsystems, Inc. | Self-monitoring and trending service system with a cascaded pipeline with enhanced authentication and registration |
US7359321B1 (en) | 2002-01-17 | 2008-04-15 | Juniper Networks, Inc. | Systems and methods for selectively performing explicit congestion notification |
ES2236370T3 (en) | 2002-01-23 | 2005-07-16 | Sony International (Europe) Gmbh | METHOD TO ALLOW THE NEGOTIATION OF EXTREME EXTREME SERVICE QUALITY BY USING THE EXTREME EXTREME NEGOTIATION PROTOCOL (E2ENP). |
US6892309B2 (en) | 2002-02-08 | 2005-05-10 | Enterasys Networks, Inc. | Controlling usage of network resources by a user at the user's entry point to a communications network based on an identity of the user |
US7260102B2 (en) | 2002-02-22 | 2007-08-21 | Nortel Networks Limited | Traffic switching using multi-dimensional packet classification |
WO2003088586A1 (en) | 2002-04-09 | 2003-10-23 | Next Generation Systems, Inc. | Systems and methods for providing qos environment ____________ |
US6879590B2 (en) * | 2002-04-26 | 2005-04-12 | Valo, Inc. | Methods, apparatuses and systems facilitating aggregation of physical links into logical link |
US7852796B2 (en) | 2002-05-13 | 2010-12-14 | Xudong Wang | Distributed multichannel wireless communication |
GB0211286D0 (en) | 2002-05-16 | 2002-06-26 | Nokia Corp | Routing data packets through a wireless network |
AU2003239555A1 (en) * | 2002-05-20 | 2003-12-12 | Vigilos, Inc. | System and method for providing data communication in a device network |
US7289498B2 (en) | 2002-06-04 | 2007-10-30 | Lucent Technologies Inc. | Classifying and distributing traffic at a network node |
US6901484B2 (en) * | 2002-06-05 | 2005-05-31 | International Business Machines Corporation | Storage-assisted quality of service (QoS) |
US6888807B2 (en) * | 2002-06-10 | 2005-05-03 | Ipr Licensing, Inc. | Applying session services based on packet flows |
US7272144B2 (en) | 2002-06-26 | 2007-09-18 | Arris International, Inc. | Method and apparatus for queuing data flows |
US7337236B2 (en) | 2002-07-02 | 2008-02-26 | International Business Machines Corporation | Application prioritization in a stateless protocol |
DE10233954B4 (en) | 2002-07-25 | 2008-02-28 | Nokia Siemens Networks Gmbh & Co.Kg | Method, communication arrangement and communication device for transmitting data cells via a packet-oriented communication network |
ES2427434T3 (en) | 2002-08-02 | 2013-10-30 | Nms Communications | Procedures and apparatus for grouping network signals and reducing bandwidth |
US6826627B2 (en) * | 2002-09-03 | 2004-11-30 | Burnbag, Ltd. | Data transformation architecture |
WO2004023323A1 (en) | 2002-09-03 | 2004-03-18 | Thomson Licensing S.A. | Mechanism for providing quality of service in a network utilizing priority and reserved bandwidth protocols |
US6904058B2 (en) * | 2002-09-20 | 2005-06-07 | Intel Corporation | Transmitting data over a general packet radio service wireless network |
US7321591B2 (en) | 2002-09-24 | 2008-01-22 | Efficient Networks, Inc. | Methods and systems for providing differentiated quality of service in a communications system |
SE0203104D0 (en) | 2002-10-18 | 2002-10-18 | Ericsson Telefon Ab L M | Method and apparatus for network initiated rate control for P2C services in a mobile system |
US7433307B2 (en) | 2002-11-05 | 2008-10-07 | Intel Corporation | Flow control in a network environment |
ES2269603T3 (en) | 2002-12-04 | 2007-04-01 | Irdeto Access B.V. | TERMINAL, SYSTEM OF DISTRIBUTION OF DATA THAT INCLUDES SUCH TERMINAL AND METHOD OF RETRANSMISSION OF DIGITAL DATA. |
US7792121B2 (en) | 2003-01-03 | 2010-09-07 | Microsoft Corporation | Frame protocol and scheduling system |
US6940832B2 (en) * | 2003-01-17 | 2005-09-06 | The Research Foundation Of The City University Of New York | Routing method for mobile infrastructureless network |
US6940813B2 (en) | 2003-02-05 | 2005-09-06 | Nokia Corporation | System and method for facilitating end-to-end quality of service in message transmissions employing message queues |
US7577161B2 (en) | 2003-02-26 | 2009-08-18 | Alcatel-Lucent Usa Inc. | Class-based bandwidth allocation and admission control for virtual private networks with differentiated service |
US6937591B2 (en) * | 2003-02-27 | 2005-08-30 | Microsoft Corporation | Quality of service differentiation in wireless networks |
US7555559B2 (en) | 2003-02-28 | 2009-06-30 | Onion Networks, KK | Parallel data transfer over multiple channels with data order prioritization |
US6912198B2 (en) | 2003-03-26 | 2005-06-28 | Sony Corporation | Performance of data transmission using adaptive technique |
US7616572B2 (en) | 2003-03-31 | 2009-11-10 | General Dynamics C4 Systems | Call admission control/session management based on N source to destination severity levels for IP networks |
US20040210663A1 (en) | 2003-04-15 | 2004-10-21 | Paul Phillips | Object-aware transport-layer network processing engine |
US7349400B2 (en) | 2003-04-29 | 2008-03-25 | Narus, Inc. | Method and system for transport protocol reconstruction and timer synchronization for non-intrusive capturing and analysis of packets on a high-speed distributed network |
US8521889B2 (en) | 2003-05-15 | 2013-08-27 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for modifying bandwidth and/or quality of service for a user session in a network |
US7573906B2 (en) | 2003-05-15 | 2009-08-11 | At&T Intellectual Property I, L.P. | Methods, computer program products, and systems for managing quality of service in a communication network for applications |
US7349422B2 (en) | 2003-06-03 | 2008-03-25 | Microsoft Corporation | Providing contention free quality of service to time constrained data |
US7436789B2 (en) | 2003-10-09 | 2008-10-14 | Sarnoff Corporation | Ad Hoc wireless node and network |
US7408932B2 (en) | 2003-10-20 | 2008-08-05 | Intel Corporation | Method and apparatus for two-stage packet classification using most specific filter matching and transport level sharing |
KR100590772B1 (en) | 2003-12-26 | 2006-06-15 | 한국전자통신연구원 | Apparatus and method of media access control processor for guaranteeing quality of service in wireless LAN |
EP1730899B1 (en) | 2004-01-30 | 2010-12-08 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Packet scheduling for data stream transmission |
EP1575224A1 (en) | 2004-03-09 | 2005-09-14 | Matsushita Electric Industrial Co., Ltd. | Packet output-controlling device |
US20050220115A1 (en) | 2004-04-06 | 2005-10-06 | David Romano | Method and apparatus for scheduling packets |
US20050232153A1 (en) | 2004-04-16 | 2005-10-20 | Vieo, Inc. | Method and system for application-aware network quality of service |
ATE383048T1 (en) | 2004-06-15 | 2008-01-15 | Matsushita Electric Ind Co Ltd | PRIORITY BASED TREATMENT OF DATA TRANSFERS |
US20050281277A1 (en) | 2004-06-22 | 2005-12-22 | Killian Thomas J | Establishing traffic priorities in a voice over IP network |
WO2006001155A1 (en) | 2004-06-25 | 2006-01-05 | Aruze Corp. | Hanging scroll support device |
US20080144493A1 (en) | 2004-06-30 | 2008-06-19 | Chi-Hsiang Yeh | Method of interference management for interference/collision prevention/avoidance and spatial reuse enhancement |
CA2574776A1 (en) | 2004-07-23 | 2006-02-02 | Citrix Systems, Inc. | Systems and methods for optimizing communications between network nodes |
US7545788B2 (en) | 2004-08-20 | 2009-06-09 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for modifying bandwidth and/or quality of service in a core network |
US7545815B2 (en) | 2004-10-18 | 2009-06-09 | At&T Intellectual Property Ii, L.P. | Queueing technique for multiple sources and multiple priorities |
US7543072B1 (en) | 2004-11-03 | 2009-06-02 | Stampede Technologies, Inc. | Method and system capable of performing a data stream over multiple TCP connections or concurrent interleave of multiple data streams over multiple TCP connections |
US7440453B2 (en) | 2004-11-12 | 2008-10-21 | International Business Machines Corporation | Determining availability of a destination for computer network communications |
US8458467B2 (en) | 2005-06-21 | 2013-06-04 | Cisco Technology, Inc. | Method and apparatus for adaptive application message payload content transformation in a network infrastructure element |
KR100594993B1 (en) | 2004-11-17 | 2006-07-03 | 삼성전기주식회사 | Method for discovery reply packet transmission in communication network |
US8023408B2 (en) | 2004-11-19 | 2011-09-20 | International Business Machines Corporation | Dynamically changing message priority or message sequence number |
US20060140193A1 (en) | 2004-12-29 | 2006-06-29 | Nokia Corporation | Optimization of a TCP connection |
EP1834449B1 (en) | 2004-12-29 | 2012-04-18 | Telefonaktiebolaget LM Ericsson (publ) | Priority bearers in a mobile telecommunication network |
US20060149845A1 (en) | 2004-12-30 | 2006-07-06 | Xinnia Technology, Llc | Managed quality of service for users and applications over shared networks |
US20070060045A1 (en) | 2005-02-02 | 2007-03-15 | Prautzsch Frank R | System and technique for situational awareness |
US7471689B1 (en) | 2005-04-22 | 2008-12-30 | Sun Microsystems, Inc. | Method and apparatus for managing and accounting for bandwidth utilization within a computing system |
US7499457B1 (en) | 2005-04-22 | 2009-03-03 | Sun Microsystems, Inc. | Method and apparatus for enforcing packet destination specific priority using threads |
US7590756B2 (en) | 2005-05-13 | 2009-09-15 | Itt Manufacturing Enterprises, Inc. | Method and system for transferring data in a communications network using redundant communication paths |
CA2611160A1 (en) | 2005-06-06 | 2006-12-14 | Mobidia, Inc. | System and method of controlling a mobile device using a network policy |
US20060286993A1 (en) | 2005-06-20 | 2006-12-21 | Motorola, Inc. | Throttling server communications in a communication network |
US7477651B2 (en) | 2005-07-01 | 2009-01-13 | Cisco Technology, Inc. | System and method for implementing quality of service in a backhaul communications environment |
EP1911222A1 (en) | 2005-07-18 | 2008-04-16 | Starent Networks Corporation | Method and system for quality of service renegotiation |
US8576846B2 (en) | 2005-10-05 | 2013-11-05 | Qualcomm Incorporated | Peer-to-peer communication in ad hoc wireless network |
US7571247B2 (en) * | 2005-12-12 | 2009-08-04 | International Business Machines Corporation | Efficient send socket call handling by a transport layer |
US7881199B2 (en) | 2006-01-04 | 2011-02-01 | Alcatel Lucent | System and method for prioritization of traffic through internet access network |
US7924890B2 (en) | 2006-02-13 | 2011-04-12 | Cisco Technology, Inc. | Apparatus and method for increasing reliability of data sensitive to packet loss |
US7929542B2 (en) | 2006-03-03 | 2011-04-19 | The Boeing Company | Supporting effectiveness of applications in a network environment |
US7801129B2 (en) | 2006-04-27 | 2010-09-21 | Alcatel-Lucent Usa Inc. | Method and apparatus for SIP message prioritization |
US20100166051A1 (en) | 2006-05-01 | 2010-07-01 | Seong Taek Chung | Video Streaming Diagnostics |
US20070258445A1 (en) | 2006-05-02 | 2007-11-08 | Harris Corporation | Systems and methods for protocol filtering for quality of service |
US20070258459A1 (en) | 2006-05-02 | 2007-11-08 | Harris Corporation | Method and system for QOS by proxy |
US20070263616A1 (en) | 2006-05-15 | 2007-11-15 | Castro Paul C | Increasing link capacity via traffic distribution over multiple WI-FI access points |
US20070291768A1 (en) | 2006-06-16 | 2007-12-20 | Harris Corporation | Method and system for content-based differentiation and sequencing as a mechanism of prioritization for QOS |
US8064464B2 (en) | 2006-06-16 | 2011-11-22 | Harris Corporation | Method and system for inbound content-based QoS |
US20070291767A1 (en) | 2006-06-16 | 2007-12-20 | Harris Corporation | Systems and methods for a protocol transformation gateway for quality of service |
US20070291656A1 (en) | 2006-06-16 | 2007-12-20 | Harris Corporation | Method and system for outbound content-based QoS |
US8516153B2 (en) | 2006-06-16 | 2013-08-20 | Harris Corporation | Method and system for network-independent QoS |
US8730981B2 (en) | 2006-06-20 | 2014-05-20 | Harris Corporation | Method and system for compression based quality of service |
US20070291765A1 (en) | 2006-06-20 | 2007-12-20 | Harris Corporation | Systems and methods for dynamic mode-driven link management |
US20080013559A1 (en) | 2006-07-14 | 2008-01-17 | Smith Donald L | Systems and methods for applying back-pressure for sequencing in quality of service |
US20100241759A1 (en) | 2006-07-31 | 2010-09-23 | Smith Donald L | Systems and methods for sar-capable quality of service |
US20100238801A1 (en) | 2006-07-31 | 2010-09-23 | Smith Donald L | Method and system for stale data detection based quality of service |
US8300653B2 (en) | 2006-07-31 | 2012-10-30 | Harris Corporation | Systems and methods for assured communications with quality of service |
US20080025318A1 (en) | 2006-07-31 | 2008-01-31 | Harris Corporation | Systems and methods for dynamically customizable quality of service on the edge of a network |
-
2006
- 2006-05-02 US US11/415,914 patent/US7756134B2/en not_active Expired - Fee Related
-
2007
- 2007-04-30 TW TW096115433A patent/TWI353151B/en not_active IP Right Cessation
- 2007-05-01 WO PCT/US2007/010557 patent/WO2007130413A2/en active Application Filing
- 2007-05-01 CN CN2007800227460A patent/CN101502055B/en not_active Expired - Fee Related
- 2007-05-01 JP JP2009509666A patent/JP4659116B2/en not_active Expired - Fee Related
- 2007-05-01 CA CA2650909A patent/CA2650909C/en not_active Expired - Fee Related
- 2007-05-01 EP EP07776572.5A patent/EP2022202A4/en not_active Withdrawn
- 2007-05-01 KR KR1020087029016A patent/KR101102178B1/en not_active IP Right Cessation
Non-Patent Citations (1)
Title |
---|
See references of EP2022202A4 * |
Also Published As
Publication number | Publication date |
---|---|
JP2009535989A (en) | 2009-10-01 |
CA2650909A1 (en) | 2007-11-15 |
CA2650909C (en) | 2012-10-23 |
TW200812321A (en) | 2008-03-01 |
KR101102178B1 (en) | 2012-01-02 |
EP2022202A2 (en) | 2009-02-11 |
TWI353151B (en) | 2011-11-21 |
WO2007130413A3 (en) | 2009-04-09 |
US7756134B2 (en) | 2010-07-13 |
CN101502055B (en) | 2012-03-28 |
CN101502055A (en) | 2009-08-05 |
JP4659116B2 (en) | 2011-03-30 |
KR20090012340A (en) | 2009-02-03 |
US20070258486A1 (en) | 2007-11-08 |
EP2022202A4 (en) | 2013-06-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2650909C (en) | Systems and methods for close queuing to support quality of service | |
CA2650915C (en) | Systems and methods for protocol filtering for quality of service | |
CA2655983C (en) | Systems and methods for adaptive throughput management for event-driven message-based data | |
EP2050235B1 (en) | Systems and methods for sar-capable quality of service | |
EP2039086B1 (en) | Method and system for rule-based sequencing for qos | |
CA2655375C (en) | Systems and methods for a protocol transformation gateway for quality of service | |
CA2657278C (en) | Method and system for fault-tolerant quality of service | |
US8064464B2 (en) | Method and system for inbound content-based QoS | |
US20070291768A1 (en) | Method and system for content-based differentiation and sequencing as a mechanism of prioritization for QOS | |
US20080013559A1 (en) | Systems and methods for applying back-pressure for sequencing in quality of service | |
US20070291656A1 (en) | Method and system for outbound content-based QoS | |
EP2039078A2 (en) | Systems and methods for dynamic mode-driven link management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780022746.0 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07776572 Country of ref document: EP Kind code of ref document: A2 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009509666 Country of ref document: JP Ref document number: 2650909 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020087029016 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007776572 Country of ref document: EP |