Source: https://patents.google.com/patent/US7856012B2/en
Timestamp: 2018-04-25 22:34:35
Document Index: 473901379

Matched Legal Cases: ['art 2', 'art 2', 'art 1', 'art 1', 'Application No. 07812151', 'Application No. 07813469', 'Application No. 07777069', 'art 2', 'art 2', 'Application No. 2009']

US7856012B2 - System and methods for generic data transparent rules to support quality of service - Google Patents
System and methods for generic data transparent rules to support quality of service Download PDF
US7856012B2
US7856012B2 US11454662 US45466206A US7856012B2 US 7856012 B2 US7856012 B2 US 7856012B2 US 11454662 US11454662 US 11454662 US 45466206 A US45466206 A US 45466206A US 7856012 B2 US7856012 B2 US 7856012B2
Active, expires 2028-12-16
US11454662
US20070291780A1 (en )
Anthony P. Galluscio
Robert J. Knazik
Embodiments of the present invention provide systems and methods for facilitating communication of data. A method for prioritizing a block of data to provide content-based quality of service in a network includes receiving a block of data, selecting a selected rule from a set of available rules, processing the block of data, and prioritizing the block of data. The selected rule includes an operation and a key. The block of data is processed according to the selected rule based at least in part on the operation to determine a decision value based at least in part on the key. The block of data is prioritized based at least in part on the decision value.
The presently described technology generally relates to communications networks. More particularly, the presently described technology relates to systems and methods for generic data transparent rules to support 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. For example, 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. For example, 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. Alternatively, data may be sent as a stream. In some instances, 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.
Communication over a network typically involves multiple levels of communication protocols. 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 “lowest” layer, while the application layer is the “highest” layer. Two well-known transport layer protocols are the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). A well known network layer protocol is the Internet Protocol (IP).
At the transmitting node, 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. At each layer, 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.
One kind of communications network is a tactical data network. 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 real-time video.
An example of how a tactical data network may be employed is as follows. 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. At the command post, 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.
The various networks that may exist within a tactical data network may have many different architectures and characteristics. For example, 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. In addition, a network may include a high frequency (HF) network which allows long rang communication. A microwave network may also be used, for example. 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. In addition, 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.
In many instances the bandwidth available to a network cannot be increased. For example, the bandwidth available over a satellite communications link may be fixed and cannot effectively be increased without deploying another satellite. In these situations, bandwidth must be managed rather than simply expanded to handle demand. In large systems, 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.
In addition to bandwidth constraints, tactical data networks may experience high latency. For example, a network involving communication over a satellite link may incur latency on the order of half a second or more. For some communications 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.
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.
Often, 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.
Certain protocols do not work well over tactical data networks. For example, a protocol such as 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. For example, threat warning receivers in an aircraft may have higher priority than position telemetry information for troops on the ground miles away. As another example, 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. For example, 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. Similarly, 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.
There are several approaches to delivering data over a network. One approach, used by many communications networks, is a “best effort” approach. That is, data being communicated will be handled as well as the network can, given other demands, with regard to capacity, latency, reliability, ordering, and errors. Thus, the network provides no guarantees that any given piece of data will reach its destination in a timely manner, or at all. Additionally, no guarantees are made that data will arrive in the order sent or even without transmission errors changing one or more bits in the data.
Another approach is Quality of Service (QoS). QoS refers to one or more capabilities of a network to provide various forms of guarantees with regard to data that is carried. For example, a network supporting QoS may guarantee a certain amount of bandwidth to a data stream. As another example, 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 selected 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.
Current approaches to QoS often require every node in a network to support QoS, or, at the very least, for every node in the network involved in a particular communication to support QoS. For example, in current systems, in order to provide a latency guarantee between two nodes, every node carrying the traffic between those two nodes must be aware of and agree to honor, and be capable of honoring, the guarantee.
There are several approaches to providing QoS. One approach is Integrated Services, or “IntServ.” IntServ provides a QoS system wherein every node in the network supports the services and those services are reserved when a connection is set up. IntServ does not scale well because of the large amount of state information that must be maintained at every node and the overhead associated with setting up such connections.
Another approach to providing QoS is Differentiated Services, or “DiffServ.” 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.
As mentioned, existing QoS solutions require at least the nodes involved in a particular communication to support QoS. However, the 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.
Existing QoS solutions are often network specific and each network type or architecture may require a different QoS configuration. Due to the mechanisms existing QoS solutions utilize, messages that look the same to current QoS systems may actually have different priorities based on message content. However, data consumers may require access to high-priority data without being flooded by lower-priority data. Existing QoS systems cannot provide QoS based on message content at the transport layer. Further, current systems that look to message connect must be configured to understand a predetermined, fixed data format. That is, current QoS systems that examine message content are only able examine messages with predefined, unchanging formats. Thus, it is highly desirable to have a generic data transparent rules to support QoS.
Thus, there is a need for systems and methods providing QoS in a tactical data network. There is a need for systems and methods for providing QoS on the edge of a tactical data network. Additionally, there is a need for adaptive, configurable QoS systems and methods in a tactical data network. Further, there is a need for systems and methods for generic data transparent rules to support Quality of Service.
Certain embodiments provide a system for data communication system for providing content-based quality of service in a network including a rule, a parser component, and a prioritization component. The rule includes an operation and a key. The rule is included in a set of available rules. The parser component is adapted to process data based at least in part on the operation and to match the key to determine a decision value. The prioritization component is adapted to determine a priority for the data based at least in part on the decision value.
Certain embodiments provide a computer-readable medium including a set of instructions for execution on a computer, the set of instructions including a selection routine, a parsing routine, a prioritization routine, and a communication routine. The selection routine is configured to select a selected rule from a set of available rules. The parsing routine is configured to process data utilizing the selected rule to determine a decision value. The prioritization routine is configured to determine a priority for the data based at least in part on the decision value. The communication routine is configured to communicate the data based on the priority.
FIG. 1 illustrates a tactical communications network environment operating with an embodiment of the present invention.
FIG. 2 shows the positioning of the data communications system in the seven layer OSI network model in accordance with an embodiment of the present invention.
FIG. 3 depicts an example of multiple networks facilitated using the data communications system in accordance with an embodiment of the present invention.
FIG. 4 illustrates a data communication environment operating with an embodiment of the present invention.
FIG. 5 illustrates examples of parsing data using rules according to an embodiment of the present invention.
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 present invention. 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. The following discussion assumes a network environment 100 including more than one network 120 and more than one link 130, but it should be understood that other environments are possible and anticipated.
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.
In certain embodiments, 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. In certain embodiments, 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. By “optimizing” bandwidth, it is meant that the presently described technology can 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, “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.
In certain embodiments, 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. As mentioned above, in certain embodiments, 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.
In certain embodiments, the system 150 provides quality of service (QoS) on the edge of the network. 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.). Using 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. In certain embodiments, to accommodate capabilities beyond XML and/or to support extremely low latency requirements, 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.
In certain embodiments, 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.
In certain embodiments, the system 150 offers dynamic support for multiple operational scenarios and/or network environments via commanded profile switching. 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.
In certain embodiments, the system 150 provides a rules-based approach for optimizing bandwidth. For example, 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. That is, if a new message is provided that is not sufficiently different from an older message that has already been scheduled to be sent, but has not yet been sent, the newer message may be dropped, since the older message will carry functionally equivalent information and is further ahead in the queue. In addition, functional redundancy many include actual duplicate messages and newer messages that arrive before an older message has been sent. For example, 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. As another example, 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.
In certain embodiments, the system 150 provides fault tolerance capability to help protect data integrity and reliability. For example, 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. Additionally, the configuration may allow the user to specify a location and amount of secondary storage that may be used for queue overflow. After the memory in the queues is filled, messages may be queued in secondary storage. When the secondary storage is also full, 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.
Furthermore, in certain embodiments, 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.
FIG. 4 illustrates a data communication environment 400 operating with an embodiment of the present invention. The environment 400 includes a data communication system 410, a source nodes 460, and a destination node 470. The data communication system 410 includes a parser component 420, a prioritization component 430, a communication component 440, and one or more rules 450.
The data communication system 410 is in communication with the source node 460 and the destination node 470. The data communication system 410 may communicate with the source node 460 and/or destination node 470 over links, such as radio, satellite, network links, and/or through inter-process communication. In certain embodiments, a link is part of a tactical data network. In certain embodiments, a link is bandwidth constrained. In certain embodiments, a link is unreliable and/or intermittently disconnected.
In certain embodiments, the data communication system 410 is in communication with two or more source nodes 460. In certain embodiments, the data communication system 410 is in communication with two or more destination nodes 470.
The parser component 420 is in communication with the prioritization component 430. The prioritization component 430 is in communication with the communication component 440.
The data communication system 410 may be similar to the communication system 150, described above, for example. In certain embodiments, the data communication system 410 is adapted to receive data from the source node 460. In certain embodiments, the data communication system 410 is adapted to communicate data to the destination node 470.
In operation, data is received at the data communication system 410. The data may be received from the source node 460, for example. The data may be parsed by the data communication system 410. For example, the data may be parsed to determine a decision value regarding the data. The data may be prioritized by the data communication system 410. For example, the data may be prioritized based at least in part on the parsing of the data. The data may be communicated by the data communication system 410. For example, the data may be communicated to the destination node 470.
The data received, stored, prioritized, processed, communicated, and/or 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. For example, the data communication system 410 may receive packets of data from the source node 460. As another example, the data communication system 410 may process a stream of data from the source node 460.
In certain embodiments, the data includes a header and a payload. In certain embodiments, the data is not contiguous in memory. That is, one or more portions of the data may be located in different regions of memory. For example, header information may be stored in one region of memory while the payload is stored in another buffer.
The data may be received over one or more links, for example. For example, data may be received at the data communication system 410 from a radio over a tactical data network. As another example, data may be provided to the data communication system 410 by an application running on the same system by an inter-process communication mechanism. As discussed above, the data may be a block of data, for example.
Data is received by the data communication system 410. In certain embodiments, 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. For example, the data communication 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.
The source node 460 provides and/or generates, at least in part, data handled by the data communication system 410. The source node 460 may include, for example, an application, radio, satellite, or network. The source node 460 may communicate with the data communication system 410 over a link, as discussed above. The source node 460 may generate a continuous stream of data or may burst data, for example. In certain embodiments, the source node 460 and the data communication system 410 are part of the same system. For example, the source node 460 may be an application running on the same computer system as the data communication system 410.
The destination node 470 receives data from the data communication system 410. The destination node 470 may include, for example, an application, radio, satellite, or network. The destination node 470 may communicate with the data communication system 410 over a link, as discussed above. In certain embodiments, the destination node 470 and the data communication system 410 are part of the same system. For example, the destination node 470 may be an application running on the same computer system as the data communication system 410.
The parser component 420 is adapted to parse data. The data may be received from the source node 460, for example. The parser component 420 may examine and/or process the data. For example, the parser component 420 may examine the data to perform an operation. The result of the operation may be used by the parser component 420 to determine a decision value. For example, the parser component 420 may search the data for a particular value and if the value is found, the parser component 420 may generate a decision value indicating the value was found. Alternatively, if the value is not found, the parser component 420 may generate a decision value indicating the value was not found. The decision value may be a flag, integer, or enumerated value, for example. The decision value may represent the status or result of parsing the data, for example.
In certain embodiments, the parser component 420 is adapted to parse data based at least in part on one or more rules 450. For example, the parser component 420 may parse the data using one or more of the rules 450 in a set of available rules. A rule may include an operation and a key. An operation may direct, specify, and/or instruct the parser component 420 on how to process or examine the data, for example. For example, an operation might indicate to the parser component 420 that the value of a particular byte in the data should be examined and compared to the key value.
Operations may include offset and scan operations, for example. An offset operation indicates that the parser component 420 should examine a value, such as a byte or word, in the data offset from the current position by some amount. For example, an “offset 4” operation may indicate that the fourth byte from the present position in the data should be examined. As another example, a “scan 7” operation may indicate that the sequence of seven words from the current position in the data should be examined and compared to a particular key value.
The key value in a rule specifies a value for use in a comparison or other purpose for a given operation. For example, a rule with a “scan 7” operation may have a key value of “0x0321,” indicating that the next seven bytes of the data should be scanned to see if any match the key value “0x0321.”
As mentioned above, the parser component 420 may parse the data using one or more rules 450. The rules 450 in the set of rules used to parse the data may be processed sequentially or in parallel, for example. In certain embodiments, some or all of the rules 450 may be parsed at about the time. In certain embodiments, one or more rules 450 may be processed starting from the beginning of the data. In certain embodiments, one or more rules 450 may be processed starting from where the processing of a prior rule stopped.
In certain embodiments, the rules in the set of rules may depend on a mode or profile. For example, the rules in a particular set of rules may depend on an active mode or profile of the data communication system 410. That is, different modes may have different rules 450 associated with them. In certain embodiments, one or rules are defined at least in part by a user. In certain embodiments, rules may be written in XML and/or provided via custom DLLs, for example. In certain embodiments, to accommodate capabilities beyond XML and/or to support extremely low latency requirements, a dynamic link library may be provided with custom code to implement a rule, for example.
In certain embodiments, the parser component 420 processes the data without regard to the format of the data. That is, the parser component 420 processes the data according to the rules 450 without regard to the data source, format, or type. Thus, the data may not be in a predetermined format. The data may be viewed by the parser component 420 as an array of bytes. Alternatively, the data may be viewed by the parser component 420 as an array of bits or 16-bit, 32-bit, or 64-bit words, for example. The representation of the data by the parser component 420 does not depend on the actual format of the data.
The prioritization component 430 is adapted to prioritize and/or data. The data may be received from the parser component 420. The prioritization component 430 is adapted to prioritize the data based at least in part on a decision value for the data. The decision value may be the decision value determined by the parser component 420, described above, for example.
In certain embodiments, the prioritization component 430 may include one or more queues for storing, organizing, and/or prioritizing the data. Alternatively, other data structures may be used for storing, organizing, and/or prioritizing the data. For example, a table, tree, or linked list may be used.
In certain embodiments, the prioritization component 430 may determine a priority for a block of data. For example, a priority for a block of data may be determined based at least in part on a decision value determined by the parsing component 420. A block of data may be stored in a queue and/or may be extracted from a queue based on the priority determined for the block of data and/or for the queue.
The prioritization of the data by the prioritization component 430 may be used to provide QoS, for example. For example, the prioritization component 430 may determine a priority for data received over a tactical data network. In certain embodiments, the priority is based at least in part on content. For example, the data may be examined by the parser component 420. The priority may be based on a decision value supplied by the parser component 420, for example. For example, the parser component 420 may indicate to the prioritization component 430 that the data is a video conference between generals and, thus, should be given a higher priority. As another example, the parser component 420 may indicate that the data is position telemetry data from a ground unit far away from the aircraft receiving the data and, thus, is lower priority. 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. For example, 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 communication component 440 is adapted to communicate data. The data to be communicated may be received from the prioritization component 430. The data to be communicated may be selected based at least in part on a priority for the data, for example. For example, the communication component 440 may select a block of data from a queue in the prioritization component 430 to communicate to the destination node 470.
The data may be communicated to one or more destination nodes 470, for example. The data may be communicated over one or more links, for example. For example, the data may be communicated by the data communication system 410 over a tactical data network to a radio. As another example, data may be provided by the data communication system 410 to an application running on the same system by an inter-process communication mechanism.
In certain embodiments, 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, 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. As discussed above, 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 affecting changes in rules, modes, and/or data transports, for example. For example, different modes may have different rules 450 associated with them. That is, one set of rules 450 may be utilized by the parser component 420, for example, in mode A, and a different, although potentially overlapping, set of rules 450 may be utilized in mode B. 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-fly,” for example.
In certain embodiments, the data communication system 410 is transparent to other applications. For example, the processing, organizing, and/or prioritization performed by the data communication system 410 may be transparent to one or more source nodes 460 or other applications or data sources. For example, an application running on the same system as data communication system 410, or on a source node 460 connected to the data communication system 410, may be unaware of the prioritization of data performed by the data communication system 410.
In one embodiment, for example, a bandwidth-constrained network, such as a tactical data network, includes one or more source nodes and one or more destination nodes. The nodes may be aircraft radios, satellites, and/or software applications, for example. The data from the source node(s) is communicated to the data communication system. The data communication system may be on the same node as a source node, a destination node, or on an intermediate node. For example, the data communication system may be on a fighter aircraft, with source nodes such as an application on the aircraft, other aircraft in the squadron, a headquarters unit, and a ground unit. The data may be communicated over a link such as a satellite link, a radio link, and/or inter-process communication. The data from the source node(s) is transparently parsed according to rules, without regard to the format of the data, to determine a priority for the data. For example, the data may include XML elements in an arbitrary order. That is, in different blocks of data, an XML element indicating the sender of the block may appear in different places in the block. The data communication system may determine by parsing the data using the user-defined rules (e.g., a scan operation) that the data is a video conference between generals and, thus, should be given a higher priority. As another example, the data communication system may determine by parsing the data using the rules that the data is position telemetry data from a ground unit far away from the aircraft receiving the data and, thus, is lower priority. 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. For example, higher priority data may be placed in a queue intended to hold higher priority data, and in turn, the data communication system, in determining what data to next communicate may look first to the higher priority queue.
As discussed above, the components, elements, and/or functionality of the data communication system 410 may be implemented alone or in combination in various forms 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.
FIG. 5 illustrates examples 500 of parsing data using rules according to an embodiment of the present invention. More particularly, FIG. 5 illustrates a block of data 501, a first example 510, and a second example 510. The block of data 501 is illustrated as an array of bytes. The first example 510 includes two rules, a primary rule and a secondary rule. The second example 520 includes a primary rule. In addition, FIG. 5 illustrates the execution 511 of example 510 and the execution 521 of example 520.
The block of data 501 may be processed by the parsing component 420, for example. In each example, the block of data 501 is parsed using the rules specified in the example. For example, the execution 511 illustrates the parsing of the block of data 501 using the primary and secondary rules in the first example 510. Similarly, the execution 521 illustrates the parsing of the block of data 501 using the primary rule in the second example 520. The rules in each example may be similar to the rules 450 discussed above, for example.
Each rule includes an operation and a key. For example, in the first example 510, the primary rule has an operation of “offset 0x06” and a key of “0x02.” The secondary rule has an operation of “Search Len 0x03” and a key of “0x080A.” In the second example 520, the primary rule has an operation of “offset 0x0B” and a key of “0x0D.” That is, an operation of “offset 11” and a key of “13.”
An operation may direct, specify, and/or instruct the parser component 420 on how to process or examine the data, for example. For example, an operation might indicate to the parser component 420 that the value of a particular byte in the data should be examined and compared to the key value.
Operations may include offset and scan operations, for example. An offset operation indicates that a value, such as a byte or word, in the data offset from the current position by some amount should be examined. For example, an “offset 4” operation may indicate that the fourth byte from the present position in the data should be examined. As another example, a “scan 7” operation may indicate that the sequence of seven words from the current position in the data should be examined and compared to a particular key value.
The rules in the set of rules used to parse the data may be processed sequentially or in parallel, for example. In certain embodiments, some or all of the rules may be parsed at about the time. In certain embodiments, one or more rules may be processed starting from the beginning of the data. In certain embodiments, one or more rules may be processed starting from where the processing of a prior rule stopped.
In the first example 510, the primary rule is used to parse the block of data 501. The primary rule has an operation specifying an offset of six bytes. The sixth byte is examined and its value is compared to the key. Here, the value of the sixth byte it “0x02,” which matches the key for the primary rule of “0x02.” Thus, the secondary rule will be processed. The secondary rule has an operation specifying a search operation over three bytes looking for the key of “0x080A.” Here, the block of data 501 continues to be processed from the stopping point of the last operation and up to the next three bytes are examined looking for a match to the specified key. As illustrated, the key is matched. Thus, the block of data 501 has been parsed using the rules in the first example 501. The parsing component 420 may generated a decision value based on the outcome of this processing. For example, a decision value may indicate that the rules were successfully processed. The decision value may then been interpreted by the priority component 430 to determine a priority for the block of data 501, for example.
In the second example 520, the primary rule is used to parse the block of data 501. The primary rule has an operation specifying an offset of 11 bytes. The eleventh byte is examined and its value is compared to the key. Here, the value of the eleventh byte is “0xD0,” which does not match the key for the primary rule of “0x0D.” The parsing component 420 may generate a decision value based on the outcome of this processing. For example, a decision value may indicate that the rule was not successfully processed. The decision value may then be interpreted by the priority component 430 to determine a priority for the block of data 501, for example.
As mentioned above, the block 501 is illustrated as an array of bytes. Alternatively, the block of data 501 may be viewed by the parser component 420 as an array of bits or 16-bit, 32-bit, or 64-bit words, for example. The representation of the block of data 501 by the parser component 420 does not depend on the actual format of the data.
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. At step 610, data is received. At step 620, a rule is selected. At step 630, data is processed. At step 640, data is prioritized. At step 650, data is communicated. The method 600 is described with reference to elements of systems described above, but it should be understood that other implementations are possible.
At step 610, data is received. Data may be received at the data communication system 410, for example. As another example, data may be received at the parser component 420. 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 460, for example. For example, data may be received at the parser component 420 from a radio over a tactical data network. As another example, data may be provided to the data communication system 410 by an application running on the same system by an inter-process communication mechanism. As discussed above, the data may be a block of data, for example.
In certain embodiments, not all of the data may be received. For example, some of the data may be stored in a buffer and only header information and a pointer to the buffer are received. For example, the data communication 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.
At step 620, a rule is selected. The selected rule may be similar to the rule 450, described above, for example. The rule may be selected from a set of available rules, for example. The rule may be selected by a parsing component. The parsing component may be similar to the parsing component 420, described above, for example.
Each rule includes an operation and a key. An operation may direct, specify, and/or instruct the parser component 420 on how to process or examine the data, for example. For example, an operation might indicate to the parser component 420 that the value of a particular byte in the data should be examined and compared to the key value.
At step 630, data is processed. The data to be processed may be the data received at step 610, described above, for example. The data may be processed by a parser component. The parser component may be similar to the parser component 420, described above, for example. The data may be processed based at least in part on one or more rules. The rule(s) may include the rule selected at step 620, described above, for example. That is, the data may be processed according to the selected rule, selected at step 620, for example. The rules may be similar to the rules 450, described above, for example.
As mentioned above, a rule may include an operation and a key. An operation may be used to direct, specify, and/or instruct how to process or examine the data, for example. For example, an operation might indicate that the value of a particular byte in the data should be examined and compared to the key value.
The operation specified in a rule may be similar to those operations discussed above, for example. Operations may include offset and scan operations, for example. An offset operation indicates that a value, such as a byte or word, in the data offset from the current position by some amount should be examined. For example, an “offset 4” operation may indicate that the fourth byte from the present position in the data should be examined. As another example, a “scan 7” operation may indicate that the sequence of seven words from the current position in the data should be examined and compared to a particular key value.
The key value may be similar to the key values discussed above, for example. The key value in a rule specifies a value for use in a comparison or other purpose for a given operation. For example, a rule with a “scan 7” operation may have a key value of “0x0321,” indicating that the next seven bytes of the data should be scanned to see if any match the key value “0x0321.”
The processing of the data may be used to determine a decision value. For example, the processing of the data may include searching the data for a particular value and if the value is found, a decision value indicating the value was found may be generated. Alternatively, if the value is not found, a decision value indicating the value was not found may be generated. The decision value may be a flag, integer, or enumerated value, for example. The decision value may represent the status or result of parsing the data, for example.
In certain embodiments, the processing of the data occurs without regard to the format of the data. That is, the data may be processed according to the rules 450 without regard to the data source, format, or type. Thus, the data may not be in a predetermined format.
The processing of the data may be done sequentially or in parallel, for example. In certain embodiments, some or all of the processing occurs at about the time. For example, some or all of the rules 450 may be used process the data at about the same time. In certain embodiments, some or all of the processing may begin starting from the beginning of the data. In certain embodiments, some of the processing may start from where prior processing stopped.
At step 640, data is prioritized. The data may be prioritized and/or organized by a prioritization component such as the prioritization component 430, described above, for example. The data to be prioritized may be the data that is received at step 610, for example. As another example, the data to be prioritized may be the data processed at step 630.
In certain embodiments, a priority may be determined for the data. For example, a priority for the data may be determined based at least in part on a decision value determined by the parsing component 420. The data may be stored in a queue and/or may be extracted from a queue based on the priority determined for the data and/or for the queue.
In certain embodiments, one or more queues may be used to store, organize, and/or prioritize the data. Alternatively, other data structures may be used for storing, organizing, and/or prioritizing the data. For example, a table, tree, or linked list may be used.
The data may be prioritized to provide QoS, for example. For example, a priority for data received over a tactical data network may be determined. In certain embodiments, the priority is based at least in part on content. In certain embodiments, the priority is based at least in part on a decision value determined by processing the data. The decision value may be determined by the processing at step 630, described above, for example. For example, the processing may indicate to the prioritization component 430 that the data is a video conference between generals and, thus, should be given a higher priority. As another example, the processing may indicate that the data is position telemetry data from a ground unit far away from the aircraft receiving the data and, thus, is lower priority. The priority may be used to determine which of a plurality of queues the data should be placed into for subsequent communication. For example, higher priority data may be placed in a queue intended to hold higher priority data, and in turn, in determining what data to next communicate, data may first be extracted from the higher priority queue.
The data may be prioritized based at least in part on one or more rules. As discussed above, the rules may be user defined and/or programmed based on system and/or operational constraints, for example. In certain embodiments, rules may be written in XML and/or provided via custom DLLs, for example.
In certain embodiments, the data to be prioritized is not dropped. That is, although data may be low priority, it is not dropped. 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, 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. As discussed above, 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 affecting changes in rules, modes, and/or data transports, for example. For example, different modes may have different rules 450 associated with them. That is, one set of rules 450 may be utilized by the parser component 420, for example, in mode A, and a different, although potentially overlapping, set of rules 450 may be utilized in mode B. 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-fly,” for example. In certain embodiments, the rule selected at step 620 may be selected based at least in part on the mode or profile.
In certain embodiments, the prioritization of data is transparent to other applications. For example, the processing, organizing, and/or prioritization performed by certain embodiments is transparent to one or more source nodes 460 or other applications or data sources. For example, an application running on the same system as data communication system 410, or on a source node 460 connected to the data communication system 410, may be unaware of the prioritization of data performed by the data communication system 410.
At step 650, data is communicated. The data communicated may be the data received at step 610, for example. That data communicated may be the data processed at step 630, for example. The data communicated may be the data prioritized at step 640, for example. Data may be communicated from the data communication system 410, for example. The data may be communicated by the communication component 440, for example. The data may be communicated to one or more destination nodes 470, for example. The data may be communicated over one or more links, for example. For example, the data may be communicated by the communication component 440 over a tactical data network to a radio. As another example, data may be provided by the data communication system 410 to an application running on the same system by an inter-process communication mechanism.
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.
Thus, certain embodiments of the present invention provide systems and methods for protocol filtering for QoS. Certain embodiments provide a technical effect of protocol filtering for QoS.
1. A method for prioritizing a block of data to provide content-based quality of service in a network, the method including:
receiving a block of data;
using at least one processing device to perform the steps of:
selecting a selected rule from a set of available rules, wherein the selected rule includes an operation to be performed on the block of data and a key used in performing the operation on the block of data;
processing the block of data according to the selected rule based at least in part on the operation to determine a decision value based at least in part on the key;
prioritizing the block of data, wherein the block of data is prioritized based at least in part on the decision value.
2. The method of claim 1, wherein the block of data is received at least in part over a tactical data network.
3. The method of claim 1, wherein a format of the block of data is not predetermined.
4. The method of claim 1, wherein the processing step is transparent to the format of the block of data.
5. The method of claim 1, wherein the processing step occurs at the transport layer of a protocol stack.
6. The method of claim 1, wherein the prioritizing step includes inserting the block of data in a queue.
7. The method of claim 1, wherein at least one rule in the set of available rules is user defined.
8. The method of claim 1, wherein the at least one rule in the set of available rules is based at least in part on a mode.
9. The method of claim 1, wherein the operation includes at least one of an offset operation and a scan operation.
10. The method of claim 1, further including the step of communicating the block of data based at least in part on the prioritization of the block of data.
11. The method of claim 10, wherein the communicating step includes transmitting the block of data over a tactical data network.
12. The method of claim 10, wherein the communicating step includes passing the block of data to an application program.
13. A data communication system for providing content-based quality of service in a network, the system including:
a rule, wherein the rule includes an operation to be performed on a block of data and a key used in performing the operation on the block of data, wherein the rule is included in a set of available rules; and
at least one processing device comprising:
a parser component, wherein the parser component is adapted to process data based at least in part on the operation and to match the key to determine a decision value; and
a prioritization component, wherein the prioritization component is adapted to determine a priority for the data based at least in part on the decision value.
14. The system of claim 13, wherein the block of data is received over a tactical data network.
15. The system of claim 13, wherein the block of data is not in a predetermined format.
16. The system of claim 13, wherein the parser component operates as part of a transport layer of a protocol stack.
17. The system of claim 13, further including one or more queues, wherein the prioritization component is adapted to insert the block of data into the one or more queues based at least in part on the determined priority for the block of data.
18. The system of claim 13, including a mode indicator, wherein the mode indicator indicates a current mode, wherein the set of available rules is based at least in part on the current mode, and wherein the prioritization component is adapted to prioritize the block of data based at least in part on the current mode.
19. The system of claim 13, wherein the operation includes at least one of an offset operation and a scan operation.
20. A non-transitory computer-readable medium encoded with a set of instructions for execution on a computer, the set of instructions including:
a selection routine, wherein the selection routine is configured to select a selected rule from a set of available rules after a block of data is received, wherein the selected rule includes an operation to be performed on the block of data and a key used in performing the operation on the block of data;
a parsing routine, wherein the parsing routine is configured to process the block of data utilizing the selected rule based at least in part on the operation to determine a decision value based at least in part on the key;
a prioritization routine, wherein the prioritization routine is configured to determine a priority for the data based at least in part on the decision value; and
a communication routine, wherein the communication routine is configured to communicate the data based on the priority.
US11454662 2006-06-16 2006-06-16 System and methods for generic data transparent rules to support quality of service Active 2028-12-16 US7856012B2 (en)
US11454662 US7856012B2 (en) 2006-06-16 2006-06-16 System and methods for generic data transparent rules to support quality of service
CA 2655374 CA2655374A1 (en) 2006-06-16 2007-06-14 Systems and methods for generic data transparent rules to support quality of service
EP20070798528 EP2039083A1 (en) 2006-06-16 2007-06-14 Systems and methods for generic data transparent rules to support quality of service
KR20097000902A KR101026911B1 (en) 2006-06-16 2007-06-14 Systems and Methods for Generic Data Transparent Rules to Support Quality of Service
JP2009515639A JP2009542048A (en) 2006-06-16 2007-06-14 The system and method of transparent rules to the general data to support the quality of service
PCT/US2007/071159 WO2007147025A1 (en) 2006-06-16 2007-06-14 Systems and methods for generic data transparent rules to support quality of service
CN 200780022539 CN101473610A (en) 2006-06-16 2007-06-14 Systems and methods for generic data transparent rules to support quality of service
US20070291780A1 true US20070291780A1 (en) 2007-12-20
US7856012B2 true US7856012B2 (en) 2010-12-21
ID=38596259
US11454662 Active 2028-12-16 US7856012B2 (en) 2006-06-16 2006-06-16 System and methods for generic data transparent rules to support quality of service
US (1) US7856012B2 (en)
EP (1) EP2039083A1 (en)
JP (1) JP2009542048A (en)
KR (1) KR101026911B1 (en)
CN (1) CN101473610A (en)
CA (1) CA2655374A1 (en)
WO (1) WO2007147025A1 (en)
US8265089B2 (en) * 2009-09-04 2012-09-11 Everis, Inc. Network gateway with enhanced requesting
US9348927B2 (en) * 2012-05-07 2016-05-24 Smart Security Systems Llc Systems and methods for detecting, identifying and categorizing intermediate nodes
US9065763B2 (en) 2013-03-15 2015-06-23 Schweitzer Engineering Laboratories, Inc. Transmission of data over a low-bandwidth communication channel
US9270109B2 (en) 2013-03-15 2016-02-23 Schweitzer Engineering Laboratories, Inc. Exchange of messages between devices in an electrical power system
US9620955B2 (en) 2013-03-15 2017-04-11 Schweitzer Engineering Laboratories, Inc. Systems and methods for communicating data state change information between devices in an electrical power system
Citations (263)
US6170075A (en)
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
US5671224A (en) 1992-10-05 1997-09-23 Nokia Telecommunications Oy Method for interconnecting local area networks or network segments and a local area network bridge
EP0853404A2 (en) 1997-01-14 1998-07-15 Digital Vision Laboratories Corporation Device and method for data relay
US5949758A (en) 1996-06-27 1999-09-07 International Business Machines Corporation Bandwidth reservation for multiple file transfer in a high speed communication network
US5960035A (en) 1995-09-29 1999-09-28 Motorola Inc. Method and apparatus for load balancing for a processor operated data communications device
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
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
US6067557A (en) 1996-09-06 2000-05-23 Cabletron Systems, Inc. Method and system for allocating CPU bandwidth by prioritizing competing processes
US6075770A (en) * 1996-11-20 2000-06-13 Industrial Technology Research Institute Power spectrum-based connection admission control for ATM networks
US6170075B1 (en) 1997-12-18 2001-01-02 3Com Corporation Data and real-time media communication over a lossy 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
US6233248B1 (en) 1997-10-14 2001-05-15 Itt Manufacturing Enterprises, Inc. User data protocol for internet data communications
US6247058B1 (en) 1998-03-30 2001-06-12 Hewlett-Packard Company Method and apparatus for processing network packets using time stamps
US20020009060A1 (en) 2000-05-05 2002-01-24 Todd Gross Satellite transceiver card for bandwidth on demand applications
US6343085B1 (en) 1997-08-28 2002-01-29 Microsoft Corporation Adaptive bandwidth throttling for individual virtual services supported on a network server
EP1180882A2 (en) 2000-08-17 2002-02-20 Nippon Telegraph and Telephone Corporation Packet classification search device and method
EP1193938A1 (en) 2000-09-29 2002-04-03 Telefonaktiebolaget Lm Ericsson Method and system for transmitting data
WO2002030066A1 (en) 2000-10-03 2002-04-11 U4Ea Technologies Limited Packet sequence control
US20020062395A1 (en) 2000-01-21 2002-05-23 David Thompson Browser and network optimization systems and methods
US6401117B1 (en) 1998-06-15 2002-06-04 Intel Corporation Platform permitting execution of multiple network infrastructure applications
US6407998B1 (en) 1997-10-02 2002-06-18 Thomson Licensing S.A. Multimedia decoder for prioritized bi-directional communication in a broadcast system
US20020091802A1 (en) 1999-11-08 2002-07-11 Thanabalan Paul Generic quality of service protocol and architecture for user applications in multiple transport protocol environments
US20020122387A1 (en) 2001-03-02 2002-09-05 Broadcom Corporation Algorithm for time based queuing in network traffic engineering
US20020122395A1 (en) 2001-03-05 2002-09-05 Yair Bourlas Method and apparatus for implementing a mac coprocessor in a communication system
US20020141338A1 (en) 2001-02-22 2002-10-03 Snowshore Networks, Inc. Minimizing latency with content-based adaptive buffering
US20020143948A1 (en) 2001-03-28 2002-10-03 Maher Robert Daniel Policy gateway
US20020160805A1 (en) 2001-02-27 2002-10-31 Nokia Corporation Push content filtering
US6490249B1 (en) 1998-12-01 2002-12-03 Nortel Networks Limited Adaptive connection admission control scheme for packet networks
US20020191253A1 (en) 2000-10-26 2002-12-19 Dah Yang Toy Industrial Co., Ltd. Method and apparatus for remote control
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
US20030004952A1 (en) 1999-10-18 2003-01-02 Mark Nixon Accessing and updating a configuration database from distributed physical locations within a process control system
US6507864B1 (en) 1996-08-02 2003-01-14 Symbol Technologies, Inc. Client-server software for controlling data collection device from host computer
US20030016625A1 (en) 2001-07-23 2003-01-23 Anees Narsinh Preclassifying traffic during periods of oversubscription
US20030021291A1 (en) 2001-07-26 2003-01-30 White James Douglas Multi-broadcast bandwidth control system
US6542593B1 (en) * 1999-06-02 2003-04-01 Accenture Llp Rules database server in a hybrid communication system architecture
EP1300991A1 (en) 2001-10-02 2003-04-09 Lucent Technologies Inc. A method for filtering redundant data packets
US20030067877A1 (en) 2001-09-27 2003-04-10 Raghupathy Sivakumar Communication system and techniques for transmission from source to destination
US6556982B1 (en) 2000-04-28 2003-04-29 Bwxt Y-12, Llc Method and system for analyzing and classifying electronic information
US6557053B1 (en) 2000-01-04 2003-04-29 International Business Machines Corporation Queue manager for a buffer
US20030097481A1 (en) * 2001-03-01 2003-05-22 Richter Roger K. Method and system for performing packet integrity operations using a data movement engine
US20030110286A1 (en) 2001-12-12 2003-06-12 Csaba Antal Method and apparatus for segmenting a data packet
US20030112802A1 (en) 2001-11-16 2003-06-19 Nec Corporation Packet transfer method and apparatus
US20030118107A1 (en) 2001-11-12 2003-06-26 Eisaburo Itakura Data communication system, data transmission apparatus, data receiving apparatus, data communication method, data transmission method, received-data processing method, and computer program
US6587875B1 (en) 1999-04-30 2003-07-01 Microsoft Corporation Network protocol and associated methods for optimizing use of available bandwidth
US6587435B1 (en) 1998-03-05 2003-07-01 Kdd Corporation Apparatus for high speed communication on asymmetric line
US6600744B1 (en) * 1999-03-23 2003-07-29 Alcatel Canada Inc. Method and apparatus for packet classification in a data communication system
US20030158963A1 (en) 2002-02-20 2003-08-21 Sturdy James T. Smartbridge for tactical network routing applications
US6611522B1 (en) * 1998-06-19 2003-08-26 Juniper Networks, Inc. Quality of service facility in a device for performing IP forwarding and ATM switching
US20030189935A1 (en) 2002-04-09 2003-10-09 Warden Gary G. Systems and methods for providing quality of service (QoS) in an environment that does not normally support QoS features
US20030189940A1 (en) * 2001-07-02 2003-10-09 Globespan Virata Incorporated Communications system using rings architecture
US20030195983A1 (en) 1999-05-24 2003-10-16 Krause Michael R. Network congestion management using aggressive timers
US6668175B1 (en) 1999-07-15 2003-12-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for providing radio access bearer services
US20030236828A1 (en) 2002-01-04 2003-12-25 Klaus Rock Method for reducing the latency time for interactive data communication via a satellite network
US6671732B1 (en) 2000-07-24 2003-12-30 Comverse Ltd. Method and apparatus for control of content based rich media streaming
US6691168B1 (en) 1998-12-31 2004-02-10 Pmc-Sierra Method and apparatus for high-speed network rule processing
US20040038685A1 (en) 2002-08-26 2004-02-26 Sumie Nakabayashi QoS control method for transmission data for radio transmitter and radio receiver using the method
US6700871B1 (en) 1999-05-04 2004-03-02 3Com Corporation Increased throughput across data network interface by dropping redundant packets
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
US20040057437A1 (en) 2002-09-24 2004-03-25 Daniel Wayne T. Methods and systems for providing differentiated quality of service in a communications system
US20040077345A1 (en) 2002-08-02 2004-04-22 Turner R. Brough Methods and apparatus for network signal aggregation and bandwidth reduction
US20040076161A1 (en) * 1999-01-08 2004-04-22 Lavian Tal I. Dynamic assignment of traffic classes to a priority queue in a packet forwarding device
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
WO2004036845A1 (en) 2002-10-18 2004-04-29 Telefonaktiebolaget Lm Ericsson (Publ) Arrangements and method for controlling transmission of data bits
US6732228B1 (en) * 2001-07-19 2004-05-04 Network Elements, Inc. Multi-protocol data classification using on-chip CAM
US6741562B1 (en) 2000-12-15 2004-05-25 Tellabs San Jose, Inc. Apparatus and methods for managing packets in a broadband data stream
US6748070B2 (en) 1998-08-04 2004-06-08 At&T Corp. Method for allocating network resources
US20040125815A1 (en) 2002-06-24 2004-07-01 Mikio Shimazu Packet transmission apparatus and method thereof, traffic conditioner, priority control mechanism and packet shaper
US6760309B1 (en) 2000-03-28 2004-07-06 3Com Corporation Method of dynamic prioritization of time sensitive packets over a packet based network
US20040131014A1 (en) 2003-01-03 2004-07-08 Microsoft Corporation Frame protocol and scheduling system
US6772223B1 (en) * 2000-04-10 2004-08-03 International Business Machines Corporation Configurable classification interface for networking devices supporting multiple action packet handling rules
US6771609B1 (en) 1998-05-11 2004-08-03 Caterpillar Inc Method and apparatus for dynamically updating representation of a work site and a propagation model
US6778530B1 (en) * 1999-11-08 2004-08-17 Juniper Networks, Inc. Method and apparatus for multiple field matching in network device
US6778546B1 (en) 2000-02-14 2004-08-17 Cisco Technology, Inc. High-speed hardware implementation of MDRR algorithm over a large number of queues
US20040172476A1 (en) 2003-02-28 2004-09-02 Chapweske Justin F. Parallel data transfer over multiple channels with data order prioritization
US20040174898A1 (en) 1999-03-17 2004-09-09 Broadcom Corporation Network switch memory interface configuration
US20040190451A1 (en) 2003-03-26 2004-09-30 Dacosta Behram M. Performance of data transmission using adaptive technique
US20040218532A1 (en) 2003-04-29 2004-11-04 Stanislav Khirman Method and system for transport protocol reconstruction and timer synchronization for non-intrusive capturing and analysis of packets on a high-speed distributed network
US6819681B1 (en) 1999-08-06 2004-11-16 Shrikumar Hariharasubrahmanian Systems and methods for predicting data fields in layered protocols
US6819655B1 (en) 1998-11-09 2004-11-16 Applied Digital Access, Inc. System and method of analyzing network protocols
US20040228363A1 (en) * 2003-05-15 2004-11-18 Maria Adamczyk Methods, computer program products, and systems for managing quality of service in a communication network for applications
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
US6826627B2 (en) 2002-09-03 2004-11-30 Burnbag, Ltd. Data transformation architecture
US6832239B1 (en) 2000-07-07 2004-12-14 International Business Machines Corporation Systems for managing network resources
US6832118B1 (en) 2000-09-29 2004-12-14 Rockwell Automation Technologies, Inc. Programmable network control component and system of components
US20040252698A1 (en) * 2003-05-15 2004-12-16 Anschutz Thomas Arnold Methods, systems, and computer program products for modifying bandwidth and/or quality of service for a user session in a network
US6839768B2 (en) 1997-06-13 2005-01-04 At&T Corp. Startup management system and method for rate-based flow and congestion control within a network
US6839731B2 (en) 2002-05-20 2005-01-04 Vigilos, Inc. System and method for providing data communication in a device network
US20050021806A1 (en) 2001-12-15 2005-01-27 Richardson John William System and method for delivering data streams of multiple data types at diffferent priority levels
US6854069B2 (en) 2000-05-02 2005-02-08 Sun Microsystems Inc. Method and system for achieving high availability in a networked computer system
US20050030952A1 (en) 2003-03-31 2005-02-10 Elmasry George F. Call admission control/session management based on N source to destination severity levels for IP networks
US20050041669A1 (en) * 1999-09-13 2005-02-24 Verizon Laboratories, Inc. Variable-strength error correction in ad-hoc 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
US20050060427A1 (en) 2003-04-15 2005-03-17 Sun Microsystems, Inc. Object-aware transport-layer network processing engine
US6870812B1 (en) 1998-12-18 2005-03-22 Cisco Technology, Inc. Method and apparatus for implementing a quality of service policy in a data communications network
US6873600B1 (en) 2000-02-04 2005-03-29 At&T Corp. Consistent sampling for network traffic measurement
US6879590B2 (en) 2002-04-26 2005-04-12 Valo, Inc. Methods, apparatuses and systems facilitating aggregation of physical links into logical link
US20050078672A1 (en) 2003-10-09 2005-04-14 Alaattin Caliskan Ad Hoc wireless node and network
US6882642B1 (en) 1999-10-14 2005-04-19 Nokia, Inc. Method and apparatus for input rate regulation associated with a packet processing pipeline
US6885643B1 (en) 1999-09-30 2005-04-26 Kabushiki Kaisha Toshiba Method and device for facilitating efficient data transfer via a wireless communication network
US6888806B1 (en) 2000-11-22 2005-05-03 Motorola, Inc. Method and system for scheduling packets for transmission from a wireless communication platform
US6891854B2 (en) 1997-06-26 2005-05-10 Cisco Technology, Inc. System and method for transporting a compressed video and data bit stream over a communication channel
US6891842B2 (en) 2001-09-21 2005-05-10 Nokia Corporation System and method for enabling mobile edge services
US6901484B2 (en) 2002-06-05 2005-05-31 International Business Machines Corporation Storage-assisted quality of service (QoS)
US6904054B1 (en) 2000-08-10 2005-06-07 Verizon Communications Inc. Support for quality of service and vertical services in digital subscriber line domain
US6904058B2 (en) 2002-09-20 2005-06-07 Intel Corporation Transmitting data over a general packet radio service wireless network
US6907462B1 (en) 1999-06-07 2005-06-14 Nortel Networks Limited Network gatekeeper prioritizing method and system
US6907243B1 (en) 1999-06-09 2005-06-14 Cisco Technology, Inc. Method and system for dynamic soft handoff resource allocation in a wireless network
US6910074B1 (en) 2000-07-24 2005-06-21 Nortel Networks Limited System and method for service session management in an IP centric distributed network
US6914882B2 (en) 2001-03-30 2005-07-05 Nokia, Inc. Method and apparatus for improved queuing
US6917622B2 (en) 2000-05-19 2005-07-12 Scientific-Atlanta, Inc. Allocating access across a shared communications medium in a carrier network
US6920145B2 (en) 2000-01-12 2005-07-19 Fujitsu Limited Packet switch device and scheduling control method
US20050157660A1 (en) * 2002-01-23 2005-07-21 Davide Mandato Model for enforcing different phases of the End-to-End Negotiation Protocol (E2ENP) aiming QoS support for multi-stream and multimedia applications
US20050169257A1 (en) 2002-05-16 2005-08-04 Keijo Lahetkangas Routing data packets through a wireless network
US20050171932A1 (en) 2000-02-24 2005-08-04 Nandhra Ian R. 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
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
WO2005076539A1 (en) 2004-01-30 2005-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Packet scheduling for data stream transmission
US6934250B1 (en) 1999-10-14 2005-08-23 Nokia, Inc. Method and apparatus for an output packet organizer
US6934795B2 (en) * 1999-09-23 2005-08-23 Netlogic Microsystems, Inc. Content addressable memory with programmable word width and programmable priority
US6937154B2 (en) 2001-08-21 2005-08-30 Tabula Rasa, Inc. Method and apparatus for facilitating personal attention via wireless links
US6937591B2 (en) 2003-02-27 2005-08-30 Microsoft Corporation Quality of service differentiation in wireless networks
US6940808B1 (en) 2000-04-13 2005-09-06 Nortel Networks Limited Adaptive rate traffic recovery mechanism for communication networks
US6940832B2 (en) 2003-01-17 2005-09-06 The Research Foundation Of The City University Of New York Routing method for mobile infrastructureless network
EP1575224A1 (en) 2004-03-09 2005-09-14 Matsushita Electric Industrial Co., Ltd. Packet output-controlling device
US6947378B2 (en) 2001-02-28 2005-09-20 Mitsubishi Electric Research Labs, Inc. Dynamic network resource allocation using multimedia content features and traffic features
US6947996B2 (en) 2001-01-29 2005-09-20 Seabridge, Ltd. Method and system for traffic control
US6947943B2 (en) 2001-10-26 2005-09-20 Zeosoft Technology Group, Inc. System for development, management and operation of distributed clients and servers
US6950400B1 (en) 2000-04-27 2005-09-27 Cisco Technology, Inc. Method and apparatus for performing high-speed traffic shaping
US6952416B1 (en) 1998-06-22 2005-10-04 Nortel Networks Limited Treatments in a distributed communications system
US20050226233A1 (en) 2004-03-31 2005-10-13 Kryuchkov Sergey V Method and system for facilitating network troubleshooting
US20050232153A1 (en) 2004-04-16 2005-10-20 Vieo, Inc. Method and system for application-aware network quality of service
US6975647B2 (en) 2001-11-13 2005-12-13 Ems Technologies Canada, Ltd Enhancements for TCP performance enhancing proxies
WO2006001155A1 (en) 2004-06-25 2006-01-05 Aruze Corp. Hanging scroll support device
US20060036906A1 (en) 2004-08-10 2006-02-16 International Business Machines Corporation System and method for detecting errors in a network
US20060039381A1 (en) * 2004-08-20 2006-02-23 Anschutz Thomas Arnold Methods, systems, and computer program products for modifying bandwidth and/or quality of service in a core network
US7023851B2 (en) * 2000-10-12 2006-04-04 Signafor, Inc. Advanced switching mechanism for providing high-speed communications with high Quality of Service
US20060104287A1 (en) 2002-07-25 2006-05-18 Volker Rogasch Method, communication arrangement, and communication device for transmitting message cells via a packet-oriented communication network
US20060106753A1 (en) 2004-11-17 2006-05-18 Samsung Electro-Mechanics Co., Ltd. Method for discovery reply packet transmission in communication network
US20060109857A1 (en) 2004-11-19 2006-05-25 Christian Herrmann System, method and computer program product for dynamically changing message priority or message sequence number in a message queuing system based on processing conditions
US20060140121A1 (en) 2004-12-29 2006-06-29 Kakani Naveen K Optimization of a TCP connection
WO2006071155A1 (en) 2004-12-29 2006-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Priority bearers in a mobile telecommunication network
US20060165051A1 (en) 2004-11-12 2006-07-27 International Business Machines Corporation Determining availability of a destination for computer network communications
US20060215593A1 (en) 2002-05-13 2006-09-28 Kiyon, Inc. Distributed Multichannel Wireless Communication
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
US20060286993A1 (en) 2005-06-20 2006-12-21 Motorola, Inc. Throttling server communications in a communication network
US20070060045A1 (en) 2005-02-02 2007-03-15 Prautzsch Frank R System and technique for situational awareness
US20070058561A1 (en) 2005-07-18 2007-03-15 Starent Networks, Corp. Method and system for quality of service renegotiation
US20070133582A1 (en) 2005-12-12 2007-06-14 Banerjee Dwip N Efficient send socket call handling by a transport layer
US20070153798A1 (en) 2006-01-04 2007-07-05 Alcatel System and method for prioritization of traffic through internet access network
US20070171910A1 (en) 2005-10-05 2007-07-26 Ravi Kumar Peer-to-peer communication in ad hoc wireless network
US7251242B2 (en) 2001-10-04 2007-07-31 Siemens Aktiengesellschaft Distributed transmission of traffic flows in communication networks
US20070189327A1 (en) 2006-02-13 2007-08-16 Praveen Konda Apparatus and method for increasing reliability of data sensitive to packet loss
US20070206506A1 (en) 2006-03-03 2007-09-06 Purpura William J Supporting effectiveness of applications in a network environment
EP0886454B1 (en) 1997-06-20 2007-10-24 Hewlett-Packard Development Company, L.P. Method and apparatus to expand an on-chip FIFO into a local memory
US7289498B2 (en) * 2002-06-04 2007-10-30 Lucent Technologies Inc. Classifying and distributing traffic at a network node
US20070253412A1 (en) 2006-04-27 2007-11-01 Lucent Technologies Inc. Method and apparatus for SIP message prioritization
US20070263616A1 (en) 2006-05-15 2007-11-15 Castro Paul C Increasing link capacity via traffic distribution over multiple WI-FI access points
WO2007130414A2 (en) 2006-05-02 2007-11-15 Harris Corporation Method and system for qos by proxy
WO2007130415A2 (en) 2006-05-02 2007-11-15 Harris Corporation Systems and methods for protocol filtering for quality of service
US20070275728A1 (en) 2004-06-15 2007-11-29 Matsushita Electric Industrial Co., Ltd. Scheduling Mode Dependent Data Transmissions
US20070291766A1 (en) 2006-06-16 2007-12-20 Harris Corporation Method and system for inbound content-based QoS
US20070291751A1 (en) 2006-06-20 2007-12-20 Harris Corporation Method and system for compression based quality of service
US20070291656A1 (en) 2006-06-16 2007-12-20 Harris Corporation Method and system for outbound content-based QoS
WO2007147040A2 (en) 2006-06-16 2007-12-21 Harris Corporation Method and system for network-independent qos
WO2007149805A2 (en) 2006-06-20 2007-12-27 Harris Corporation Systems and methods for dynamic mode-driven link management
WO2008008865A2 (en) 2006-07-14 2008-01-17 Harris Corporation Methods for providing quality of service by applying back-pressure in sequencing
WO2008016845A1 (en) 2006-07-31 2008-02-07 Harris Corporation Systems and methods for dynamically customizable quality of service on the edge of a network
WO2008016846A2 (en) 2006-07-31 2008-02-07 Harris Corporation Systems and methods for sar-capable quality of service
WO2008016850A2 (en) 2006-07-31 2008-02-07 Harris Corporation Systems and methods for assured communications with quality of service
WO2008016848A2 (en) 2006-07-31 2008-02-07 Harris Corporation Method and system for stale data detection based quality of service
WO2007147032A3 (en) 2006-06-16 2008-02-21 Harris Corp Systems and methods for a protocol transformation gateway for quality of service
US7337236B2 (en) 2002-07-02 2008-02-26 International Business Machines Corporation Application prioritization in a stateless protocol
US20080065808A1 (en) 1997-12-31 2008-03-13 Hoese Geoffrey B Storage router and method for providing virtual local storage
US7349422B2 (en) 2003-06-03 2008-03-25 Microsoft Corporation Providing contention free quality of service to time constrained data
US7359321B1 (en) 2002-01-17 2008-04-15 Juniper Networks, Inc. Systems and methods for selectively performing explicit congestion notification
US7376829B2 (en) 2002-12-04 2008-05-20 Irdeto Access B.V. Terminal, data distribution system comprising such a terminal and method of re-transmitting digital data
US20080144493A1 (en) 2004-06-30 2008-06-19 Chi-Hsiang Yeh Method of interference management for interference/collision prevention/avoidance and spatial reuse enhancement
EP1648125B1 (en) 2004-10-18 2008-07-23 AT&amp;T Corp. Queuing method for multiple sources and priorities
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
WO2007149166A3 (en) 2006-06-16 2008-09-04 Harris Corp Content-based differentiation and sequencing for prioritization
US20080293413A1 (en) 2005-06-06 2008-11-27 Mobidia, Inc. System and Method of Registering with an Access Point
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
US7477651B2 (en) 2005-07-01 2009-01-13 Cisco Technology, Inc. System and method for implementing quality of service in a backhaul communications environment
US7489666B2 (en) 2003-12-26 2009-02-10 Electronics And Telecommunications Research Institute Media access control apparatus and method for guaranteeing quality of service in wireless LAN
US7499457B1 (en) 2005-04-22 2009-03-03 Sun Microsystems, Inc. Method and apparatus for enforcing packet destination specific priority using threads
US20090161741A1 (en) 2006-05-01 2009-06-25 George Ginis Methods and Apparatus to Combine Data from Multiple Sources to Characterize Communication Systems
KR100406091B1 (en) * 1999-11-18 2004-01-31 가부시끼가이샤 도시바 Semiconductor device
JP2006031063A (en) * 2004-07-12 2006-02-02 Hitachi Ltd Priority control system
Patent Citations (277)
US6408341B1 (en) 1996-10-22 2002-06-18 International Business Machines Corporation Multi-tasking adapter for parallel network applications
EP1052816A3 (en) 1999-05-14 2004-07-21 Nortel Networks Limited Backpressure mechanism for a network device
US6941341B2 (en) 2000-05-30 2005-09-06 Sandraic Logic, Llc. Method and apparatus for balancing distributed applications
EP1191751B1 (en) 2000-09-20 2005-04-20 Alcatel Method and data communication switch for quality of service shaping
US7103008B2 (en) * 2001-07-02 2006-09-05 Conexant, Inc. Communications system using rings architecture
WO2007149165A2 (en) 2006-06-16 2007-12-27 Harris Corporation Method and system for outbound content- based qos
WO2007149769A2 (en) 2006-06-20 2007-12-27 Harris Corporation Method and system for compression based quality of service
WO2007149805A3 (en) 2006-06-20 2008-03-20 Harris Corp Systems and methods for dynamic mode-driven link management
WO2008008865A3 (en) 2006-07-14 2008-03-06 Harris Corp Methods for providing quality of service by applying back-pressure in sequencing
WO2008016848A3 (en) 2006-07-31 2008-03-20 Harris Corp Method and system for stale data detection based quality of service
WO2008016850A3 (en) 2006-07-31 2008-04-10 Harris Corp Systems and methods for assured communications with quality of service
WO2008016846A3 (en) 2006-07-31 2008-03-20 Harris Corp Systems and methods for sar-capable quality of service
Non-Patent Citations (158)
"CCSDS File Delivery Protocol (CFDP) Part 2-Implementers Guide" (CCSDS 720:2-G-2, Green Book, Sep. 2003).
"CCSDS File Delivery Protocol (CFDP) Part 2—Implementers Guide" (CCSDS 720:2-G-2, Green Book, Sep. 2003).
"CCSDS File Delivery Protocol (CFDP)-Part 1-Introduction and Overview" (CCSDS 720.1-G-2-Green Book, Sep. 2003).
"CCSDS File Delivery Protocol (CFDP)—Part 1—Introduction and Overview" (CCSDS 720.1-G-2—Green Book, Sep. 2003).
Advisory Action dated Apr. 13, 2010 for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Advisory Action dated Aug. 23, 2010 for U.S. Appl. No. 11/454,517 filed Jun. 16, 2006, pp. 1-2.
Advisory Action dated Jan. 12, 2010, for U.S. Appl No. 11/454,206, filed Jun. 16, 2006.
Advisory Action dated Jul. 23, 2010 for U.S. Appl. No. 11/424,635 filed Jun. 16, 2006, pp. 1-2.
Advisory Action dated May 13, 2010 for U.S. Appl. No. 11/454,220, filed Jun. 16, 2006.
Advisory Action dated Sep. 30, 2010 for U.S. Appl. No. 11/461,082, filed Jul. 31, 2006, pp. 1-2.
Akimeka, "LLC- Mobile Modular Command Center (M2C2) Advanced Technologies Training Program (ATTP) Final Analysis Report," 2004.
Akimeka, "LLC— Mobile Modular Command Center (M2C2) Advanced Technologies Training Program (ATTP) Final Analysis Report," 2004.
Ali et al., "Solider Network Extension (SNE) On-The-Move Satellite Communications (SATCOM) for Army Tactical Battalion-Level Network Healing and Thickening," Oct. 2007.
Applecore, "What are APIs, why use them, how to use them, and how to find out more," pp. 1-3, May 2005.
Bakre A. V. et al: "Implementation and Performance Evaluation of Indirect TCP" IEEE Transactions on Computers, vol. 46, No. 3, Mar. 1997.
Barker, "Overcoming the Data-Scale Management Challenge in Large Dynamic Networks," Military Communications Conference, MILCOM 2005, IEEE; pp. 1-7, Oct. 2005.
Chan, "Precedence Based Admission Control and Preemption in IP Networks," Military Communications Conference, 2006, MILCOM 2006, IEEE, pp. 1-7, Oct. 2006.
Chao, H-L, et al.: "Fair Scheduling with QoS Support in Wireless Ad Hoc Networks," IEEE Transactions on Wireless Communications, vol. 3, No. 6, Nov. 2004.
Communication Pursuant to Article 94(3) EPC, Application No. 07812151.4, dated Jan. 21, 2010.
Communication Pursuant to Article 94(3) EPC, Application No. 07813469.9, dated Nov. 17, 2009.
Communication Pursuant to Rule 62 EPC, Application No. 07777069.1, dated Mar. 16, 2010.
Consultative Committee for Space Data Systems, "CCSDS File Delivery Protocol (CFDP)-Part 2-Implementers Guide," CCSDS 720.2-G-2-Green Book, Sep. 2003.
Consultative Committee for Space Data Systems, "CCSDS File Delivery Protocol (CFDP)—Part 2—Implementers Guide," CCSDS 720.2-G-2—Green Book, Sep. 2003.
Dong et al., "APV: A Highly Efficient Transport Protocol for Low Bit Rate Multimedia Connections," Multimedia Tools and Applications, pp. 187-216, 2005.
Examiner's Answer to Appeal Brief dated Jul. 8, 2010 for U.S. Appl. No. 11/454,206, filed Jun. 16, 2006.
Extended European Search Report for PCTUS2007010558 dated Apr. 12, 2009.
Floyd et al., "Link-sharing and Resource Management Models for Packet Networks," IEEE/ACM Transactions on Networking, vol. 3, No. 4, all pages, Aug. 1995.
Gao et al., "Performance Evaluation of the CCSDS File Delivery Protocol-Latency and Storage Requirement", Dec. 10, 2004.
Gao et al., "Performance Evaluation of the CCSDS File Delivery Protocol—Latency and Storage Requirement", Dec. 10, 2004.
Information Sciences Institute, "Internet Protocol Darpa Internet Program Protocol Specification," pp. 1-46, Sep. 1981.
Information Sciences Institute, University of Southern California, "Internet Protocol DARPA Internet Program Protocol Specification," IETF Standard, Internet Engineering Task Force, IETF, CH, Sep. 1981.
International Preliminary Report for PCT/US2007/071159 dated Dec. 16, 2008, pp. 1-7.
International Preliminary Report for PCTUS200707/436 dated Oct. 10, 2008.
International Preliminary Report on Patentability dated Feb. 6, 2008 for International Application No. PCT/ US2007/071269 filed Jun. 14, 2007.
International Search Report and Written Opinion dated Apr. 28, 2008 for International Application No. PCT/ US07/10559 filed May 1, 2007.
International Search Report and Written Opinion dated Apr. 28, 2008 for International Application No. PCT/ US07/11650 filed May 15, 2007.
International Search Report and Written Opinion dated Apr. 29, 2008 for International Application No. PCT/ US07/10558 filed May 15, 2007.
International Search Report and Written Opinion dated Jun. 5, 2008 for International Application No. PCT/US07/11651 filed May 15, 2007.
International Search Report and Written Opinion, dated Dec. 12, 2007, for International Application No. PCT/ US2007/071177, Filed Jun. 14, 2007.
International Search Report and Written Opinion, dated Dec. 12, 2007, for International application No. PCT/ US2007/071440, filed Jun. 18, 2007.
International Search Report and Written Opinion, dated Feb. 6, 2008, for International Application No. PCT/ US2007/074592, filed Jul. 27, 2007.
International Search Report and Written Opinion, dated Jan. 15, 2008 for International Application No. PCT/ US2007/074577, filed Jul. 27, 2007.
International Search Report and Written Opinion, dated Jan. 15, 2008, for International application No. PCT/ US2007/074577, filed Jul. 27, 2007.
International Search Report and Written Opinion, dated Jan. 17, 2008, for International Application No. PCT/ US2007/071273, filed Jun. 14, 1997.
International Search Report and Written Opinion, dated Jan. 17, 2008, for International application No. PCT/ US2007/071273, filed Jun. 14, 2007.
International Search Report and Written Opinion, dated Jan. 2, 2008 for International Application No. PCT/ US2007/073301, filed Jul. 12, 2007.
International Search Report and Written Opinion, dated Jan. 2, 2008, for International Application No. PCT/ US2007/073301, filed Jul. 12, 2007.
International Search Report and Written Opinion, dated Jan. 22, 2008, for International application No. PCT/ US2007/074599, filed Jul. 27, 2007.
International Search Report and Written Opinion, dated Jan. 24, 2008, for International Application No. PCT/ US2007/074587, filed Jul. 27, 2007.
International Search Report and Written Opinion, dated Jan. 29, 2008, for International application No. PCT/ US2007/071191, filed Jun. 14, 2007.
International Search Report and Written Opinion, dated Jan. 29, 2008, for International Application No. PCT/ US2007/071191. filed Jun. 14, 1997.
International Search Report and Written Opinion, dated Mar. 14, 2008, for International Application No. PCT/ US2007/011649 filed May 15, 2007.
International Search Report and Written Opinion, dated Mar. 14, 2008, for International application No. PCT/ US2007/011649, filed May 15, 2007.
International Search Report for PCTUS2007011651 dated Mar. 16, 2010.
ISR for PCT/US2007/071159 dated Oct. 31, 2007, pp. 1-2.
ISR for PCTUS200707/436 dated Nov. 9, 2007.
Korean Office Action mailed Jul. 27, 2010, in Appl. No. 10-2009-7000812, pp. 3-1 to 3-3.
Laurie, "DLL Files in Windows—What Are They?," pp. 1-2, 2004.
Lee et al., "Expected File-Delivery Time of Deferred NAK ARQ in CCSDS File-Delivery Protocol," IEEE Transactions on Communications, vol. 52, Issue 8, pp. 1408-1416, Aug. 2004.
Lee, Et Al., "Expected File-Delivery Time of Deferred NAK ARQ in CCSDS File-Delivery Protocol", Aug. 2004, IEEE Transactions on Communications, vol. 52 Issue 8. pp. 1408-1416.
Madubata, C., "Prioritization Of The Joint Battle Space Infosphere (JBI) Traffic And Priority With Reciprocity CAC Protocol For The JBI Network," System Theory, 2006 Proceeding of the Thirty-Eighth Southeastern Symposium, USA, IEEE; pp. 477-481, Mar. 5, 2006.
Madubata, C.D.: "Prioritization of the Joint Battle Space Infosphere (JBI) Traffic and Priority with Reciprocity CAC Protocol for the JBI Network," System Theory, 2006 Proceeding of the Thirty-Eighth Southeastern Symposium on Mar. 5, 2006.
Notice of Panel Decision from Pre-Appeal Brief Review dated Jul. 7, 2010 for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Notice of Panel Decision from Pre-Appeal Brief Review dated Mar. 26, 2010 for U.S. Appl. No. 11/454,206, filed Jun. 16, 2006.
Notice of Panel Decision from Pre-Appeal Brief Review, dated Jun. 2, 2010 for U.S. Appl. No. 11/436,912,3 filed May 18, 2006.
Office Action dated Apr. 1, 2009, for U.S. Appl. No. 11/454,206, filed Jun. 16, 2006.
Office Action dated Apr. 2, 2008, for U.S. Appl. No. 11/415,914, filed May 5, 2006.
Office Action dated Apr. 2, 2008, for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action dated Apr. 2, 2009, for U.S. Appl. No. 11/415,914, filed May 5, 2006.
Office Action dated Apr. 20, 2010 for U.S. Appl. No. 11/425,281, filed Jun. 20, 2006.
Office Action dated Apr. 21, 2009, for U.S. Appl. No. 11/454,220, filed Jun. 16, 2006.
Office Action dated Apr. 23, 2008, for U.S. Appl. No. 11/416,043, filed May 2, 2006.
Office Action dated Apr. 27, 2009 for U.S. Appl. No 11/416,043.
Office Action dated Apr. 27, 2010 for U.S. Appl. No. 11/424,635, filed Jun. 16, 2006.
Office Action dated Apr. 27, 2010 for U.S. Appl. No. 11/461,082, filed Jul. 31, 2006.
Office Action dated Aug. 24, 2010 for U.S. Appl. No. 11/425,021 filed Jun. 19, 2006, pp. 1-19.
Office Action dated Aug. 31, 2009 for U.S. Appl. No. 11/415,914, filed May 2, 2006.
Office Action dated Dec. 10, 2009 for U.S. Appl. No. 11/424,635, filed Jun. 16, 2006.
Office Action dated Dec. 11, 2008, for U.S. Appl. No. 11/454,206, filed Jun. 16, 2006.
Office Action dated Dec. 15, 2008, for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Office Action dated Dec. 15, 2009 for U.S. Appl. No. 11/461,052, filed Jul. 31, 2006.
Office Action dated Dec. 22, 2008, for U.S. Appl. No. 11/425,021, filed Jun. 19, 2006.
Office Action dated Dec. 29, 2008, for U.S. Appl. No. 11/457,662, filed Jul. 14, 2006.
Office Action dated Dec. 30, 2009 for U.S. Appl. No. 11/454,519, filed Jun. 16, 2006.
Office Action dated Dec. 30, 2009 for U.S. Appl. No. 11/457,662, filed Jul. 14, 2006.
Office Action dated Dec. 30, 2009 for U.S. Appl. No. 11/461,242, filed Jul. 31, 2006.
Office Action dated Dec. 30, 2009, for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action dated Dec. 4, 2008, for U.S. Appl. No. 11/454,662, filed Jun. 16, 2006.
Office Action dated Feb. 5, 2009, for U.S. Appl. No. 11/436,912, filed May 18, 2006.
Office Action dated Feb. 9, 2009, for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action dated Jan. 28, 2010 for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Office Action dated Jan. 30, 2009, for U.S. Appl. No. 11/425,289, filed Jun. 20, 2006.
Office Action dated Jan. 5, 2009, for U.S. Appl. No. 11/425,281, filed Jun. 20, 2006.
Office Action dated Jan. 5, 2010 for U.S. Appl. No. 11/454,517, filed Jun. 16, 2006.
Office Action dated Jan. 6, 2010 for U.S. Appl. No. 11/436,912, filed May 18, 2006.
Office Action dated Jul. 1, 2009 for U.S. Appl. No. 11/436,912, filed May 18, 2006.
Office Action dated Jul. 1, 2009, for U.S. Appl. No. 11/425,281, filed Jun. 20, 2006.
Office Action dated Jul. 15, 2009, for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Office Action dated Jul. 21, 2009 for U.S. Appl. No. 11/457,662, filed Jul. 14, 2006.
Office Action dated Jun. 1, 2009 for U.S. Appl. No. 11/461,242, filed Jul. 31, 2006.
Office Action dated Jun. 10, 2009 for U.S. Appl. No. 11/425,289, filed Jun. 20, 2006.
Office Action dated Jun. 10, 2009 for U.S. Appl. No. 11/454,519, filed Jun. 16, 2006.
Office Action dated Jun. 10, 2009, for U.S. Appl. No. 11/454,517, filed Jun. 16, 2006.
Office Action dated Jun. 10, 2010 for U.S. Appl. No. 11/457,662, filed Jul. 14, 2006.
Office Action dated Jun. 15, 2009 for U.S. Appl. No. 11/425,021, filed Jun. 19, 2006.
Office Action dated Jun. 25, 2009 for U.S. Appl. No. 11/461,082, filed Jul. 31, 2006.
Office Action dated Jun. 5, 2009, for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action dated Mar. 12, 2010 for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action dated Mar. 15, 2010 for U.S. Appl. No. 11/454,519, filed Jun. 16, 2006.
Office Action dated Mar. 15, 2010 for U.S. Appl. No. 11/454,662, filed Jun. 16, 2006.
Office Action dated Mar. 16, 2010 for U.S. Appl. No. 11/454,220, filed Jun. 16, 2006.
Office Action dated Mar. 16, 2010 for U.S. Appl. No. 11/461,242, filed Jul. 31, 2006.
Office Action dated Mar. 18, 2010 for U.S. Appl. No. 11/496,107, filed Jul. 31, 2006.
Office Action dated Mar. 31, 2010 for U.S. Appl. No. 11/454,517, filed Jun. 16, 2006.
Office Action dated Mar. 6, 2009, for U.S. Appl. No. 11/471,923, filed Jun. 21, 2006.
Office Action dated May 1, 2009 for U.S. Appl. No. 11/461,052, filed Jul. 31, 2006.
Office Action dated May 11, 2010 for U.S. Appl. No. 11/425,289, filed Jun. 20, 2006.
Office Action dated May 13, 2009 for U.S. Appl. No. 11/424,635, filed Jun. 16, 2006.
Office Action dated May 20, 2010 for U.S. Appl. No. 11/454,517, filed Jun. 16, 2006.
Office Action dated May 21, 2008, for U.S. Appl. No. 11/436,912, filed May 18, 2009.
Office Action dated May 27, 2009, for U.S. Appl. No. 11/454,662, filed Jun. 16, 2006.
Office Action dated May 30, 2008, for U.S. Appl. No. 11/454,206, filed Jun. 16, 2006.
Office Action dated May 30, 2008, for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Office Action dated May 6, 2010 for U.S. Appl. No. 11/425,021, filed Jun. 19, 2006.
Office Action dated Nov. 13, 2008, for U.S. Appl. No. 11/461,082, filed Jul. 31, 2006.
Office Action dated Nov. 25, 2008, for U.S. Appl. No. 11/454,220, filed Jun. 16, 2006.
Office Action dated Oct. 13, 2009 for U.S. Appl. No. 11/416,043, filed May 2, 2006.
Office Action dated Oct. 13, 2009 for U.S. Appl. No. 11/471,923, filed Jun. 21, 2006.
Office Action dated Oct. 13, 2009, for U.S. Appl. No. 11/454,219, filed Jun. 16, 2006.
Office Action dated Oct. 15, 2009, for U.S. Appl. No. 11/425,281, filed Jun. 20, 2006.
Office Action dated Oct. 16, 2008, for U.S. Appl. No. 11/436,912, filed May 18, 2006.
Office Action dated Oct. 17, 2008, for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action dated Oct. 20, 2008, for U.S. Appl. No. 11/415,914, filed May 5, 2006.
Office Action dated Oct. 20, 2008, for U.S. Appl. No. 11/416,043, filed May 2, 2006.
Office Action dated Oct. 26, 2009 for U.S. Appl. No. 11/454,206, filed Jun. 16, 2006.
Office Action dated Oct. 28, 2009 for U.S. Appl. No. 11/461,082, filed Jul. 31, 2006.
Office Action dated Oct. 5, 2009, for U.S. Appl. No. 11/496,107, filed Jul. 31, 2006.
Office Action dated Sep. 13, 2010 for U.S. Appl. No. 11/416,057 filed May 2, 2006, pp. 1-14.
Office Action dated Sep. 14, 2010 for U.S. Appl. No. 11/461,242, filed Jun. 31, 2006, pp. 1-31.
Office Action dated Sep. 15, 2009 for U.S. Appl. No. 11/454,220, filed Jun. 16, 2006.
Office Action dated Sep. 17, 2010 for U.S. Appl. No. 11/454,519, filed Jun. 16, 2006, pp. 1-16.
Office Action dated Sep. 18, 2009 for U.S. Appl. No. 11/454,662, filed Jun. 16, 2006.
Office Action dated Sep. 30, 2010 for U.S. Appl. No. 11/425,281 filed Jun. 20, 2006, pp. 1-13.
Office Action, dated Apr. 2, 2008, for U.S. Appl. No. 11/416,057, filed May 2, 2006.
Office Action, dated Apr. 4, 2008, for U.S. Appl. No. 11/415,914, filed May 5, 2006.
Orda, A. et al.,: "Routing with Packet Duplication and Elimination in Computer Networks," IEEE Transactions on Communications, vol. 36, No. 7, Jul. 1988.
Orda, A. et al: "Routing with Packet Duplication and Elimination in Computer Networks," IEEE Transactions on Communications, vol. 36, No. 7, Jul. 1988.
Pancha, P. et al.: "A Delay-Minimizing Service Policy with Guaranteed Bandwidth for Real-Time Traffic," Internet Article, Aug. 23, 1995.
Pancha, P., et al.: "A Delay-Minimizing Service Policy with Guaranteed Bandwidth for Real-Time Traffic," Internet Article, Aug. 23, 1995.
Perkins, Charles E., et al.: "Quality of Service for Ad hoc On-Demand Distance Vector Routing draft-perkins-manet-aodvqos-01.txt," IETF Standard-Working-Draft, Internet Engineering Task Force, IETF, Ch. No. 1, Oct. 14, 2003.
Robles, Tomas et al.: "QoS Support for an AII-IP System Beyond 3G," IEEE Communications Magazine, vol. 39, No. 8, Aug. 2001.
Robles, Tomas, et al.: "QoS Support for an All-IP System Beyond 3G," IEEE Communications Magazine, vol. 39, No. 8, Aug. 2001.
Schoenwaelder, J., "Overview of the 2002 IAB Network Management Workshop," IETF Standard, Internet Engineering Task Force, May 2003.
Tactical Data Network (TDN). USMC Concepts+Programs 2003. p. 140.
Translation of Japan Office Action for Patent Application No. 2009-509667, mailed Aug. 10, 2010, pp. 1-2.
Written Opinion of ISR for PCTUS200707/436 dated Nov. 9, 2007.
Xue, Jianbo, et al.: "ASAP: An Adaptive QoS Protocol for Mobile Ad Hoc Networks," Personal, Indoor and Mobile Radio Communications, 2003. PIMRC 203. 14th IEEE Proceedings on Sep. 7-10, 2003, vol. 2, Sep. 7, 2003.
Zheng et al., "Group-Mobility-Aware Spectrum Management for Future Digital Battlefields," Military Communications Conference, 2006, MILCOM 2006, IEEE; pp. 1-7, Oct. 2006.
KR20090069262A (en) 2009-06-30 application
WO2007147025A1 (en) 2007-12-21 application
EP2039083A1 (en) 2009-03-25 application
US20070291780A1 (en) 2007-12-20 application
JP2009542048A (en) 2009-11-26 application
CN101473610A (en) 2009-07-01 application
CA2655374A1 (en) 2007-12-21 application
KR101026911B1 (en) 2011-04-04 grant
US20020186661A1 (en) 2002-12-12 System and method for hierarchical policing of flows and subflows of a data stream
US20060187836A1 (en) 2006-08-24 Communication device and method of prioritizing transference of time-critical data
US20030219014A1 (en) 2003-11-27 Communication quality assuring method for use in packet communication system, and packet communication apparatus with transfer delay assurance function
US20050195821A1 (en) 2005-09-08 Method and apparatus for dynamically controlling traffic in wireless station
US20040057437A1 (en) 2004-03-25 Methods and systems for providing differentiated quality of service in a communications system
US20020150115A1 (en) 2002-10-17 Time based packet scheduling and sorting system
US20070280111A1 (en) 2007-12-06 Method and system for adaptive queue and buffer control based on monitoring and active congestion avoidance in a packet network switch
US7260102B2 (en) 2007-08-21 Traffic switching using multi-dimensional packet classification
US6304552B1 (en) 2001-10-16 Memory and apparatus for input based control of discards in a lossy packet network
US20050021806A1 (en) 2005-01-27 System and method for delivering data streams of multiple data types at diffferent priority levels
US6628610B1 (en) 2003-09-30 Methods and apparatus for managing a flow of packets using change and reply signals
US20050175013A1 (en) 2005-08-11 Method for transmitting high-priority packets in an IP transmission network
US20050169172A1 (en) 2005-08-04 System and method for controlling packet transmission in a communication network
US7269752B2 (en) 2007-09-11 Dynamically controlling power consumption within a network node
US20100150164A1 (en) 2010-06-17 Flow-based queuing of network traffic
US20070086347A1 (en) 2007-04-19 Data packet node, and method of operating a data packet network
US20020176361A1 (en) 2002-11-28 End-to-end traffic management and adaptive multi-hop multimedia transmission
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SMITH, DONALD L.;GALLUSCIO, ANTHONY P.;KNAZIK, ROBERT J.;REEL/FRAME:018009/0464;SIGNING DATES FROM 20060524 TO 20060531
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SMITH, DONALD L.;GALLUSCIO, ANTHONY P.;KNAZIK, ROBERT J.;SIGNING DATES FROM 20060524 TO 20060531;REEL/FRAME:018009/0464