US20070180073A1 - Generic quality of service protocol and architecture for user applications in multiple transport protocol environments - Google Patents
Generic quality of service protocol and architecture for user applications in multiple transport protocol environments Download PDFInfo
- Publication number
- US20070180073A1 US20070180073A1 US11/672,713 US67271307A US2007180073A1 US 20070180073 A1 US20070180073 A1 US 20070180073A1 US 67271307 A US67271307 A US 67271307A US 2007180073 A1 US2007180073 A1 US 2007180073A1
- Authority
- US
- United States
- Prior art keywords
- qos
- information
- protocol
- client
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/15—Flow control; Congestion control in relation to multipoint traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/803—Application aware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/805—QOS or priority aware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/325—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the network layer [OSI layer 3], e.g. X.25
Definitions
- This invention relates generally to a generic quality of service (“QoS”) protocol for user applications communicating via a network connected between a client machine and a server machine. More specifically, the invention provides a generic QoS protocol and architecture for ensuring user applications with a desired level of QoS, regardless of the underlying processors, operating systems, network hardware, and transport protocols utilized by the user applications.
- QoS quality of service
- ATM Asynchronous Transfer Mode
- IP Internet Protocol
- the G-QoS negotiators analyze a variety of network and application parameters including network bandwidth, transport protocols utilized, physical network architectures, and processor types to calculate an acceptable QoS level, and communicate with each other using the G-QoS protocol. Additionally, the G-QoS protocol includes a QoS profile that can be accessed by a variety of network architectures, operating systems, processor architectures, and transport protocols, so that each can establish the desired QoS level.
- a Dynamic Profile Management Algorithm (“DPMA”) allows the G-QoS negotiators to negotiate, establish, and maintain the desired QoS level.
- a proprietary API allows the G-QoS protocol, G-QoS negotiators, and DPMA to be easily implemented and maintained by network personnel.
- the G-QoS protocol, API, negotiators, and DPMA form a generic QoS architecture that provides applications running in multiple transport protocol environments with a guaranteed level of QoS.
- FIG. 1 is a diagram showing the G-QoS architecture of the present invention.
- FIG. 2 is a diagram showing in detail the components of the G-QoS protocol.
- FIG. 3 is a diagram showing transport QoS profile and client information blocks of the G-QoS protocol of the present invention.
- FIG. 4 is a diagram showing QoS negotiation procedures between a client and a server using the G-QoS protocol of the present invention.
- FIG. 5 is a peer-to-peer entity diagram showing the G-QoS protocol of the present invention.
- FIG. 6 a is a state diagram showing the DPMA algorithm of the present invention implemented in a client machine.
- FIG. 6 b is a state diagram showing the DPMA algorithm of the present invention implemented in a server machine.
- FIG. 1 is a diagram showing the generic quality of service (“G-QoS”) architecture 10 of the present invention.
- G-QoS architecture 10 comprises a variety of components, each of which operate in conjunction to provide a desired level of QoS for applications running in multiple transport protocol environments.
- a client application 15 can communicate with a server application 20 using a communications channel that has a guaranteed QoS level.
- a user client application 15 desiring to communicate with a server application 20 first transfers application data to a G-QoS negotiator 25 , installed on the client machine.
- client application 15 in addition to server application 20 , can be any network-ready computer applications presently known in the art.
- Server application 20 also transfers application data to a second G-QoS negotiator 30 , residing on the same server as server application 20 .
- Both G-QoS negotiator 25 and second G-QoS negotiator 30 analyze the respective application data and network parameters, and communicate with each other over a network.
- both G-QoS negotiators 25 , 30 communicate with each other using out-of-band Internet Control Message Protocol (“ICMP”) messages.
- ICMP Internet Control Message Protocol
- G-QoS negotiators 25 , 30 Communication between G-QoS negotiators 25 , 30 is effectuated through G-QoS protocol 28 .
- G-QoS negotiators 25 , 30 Upon communicating with each other, G-QoS negotiators 25 , 30 then negotiate an acceptable level of QoS that can be utilized by both the user client application 15 and server application 20 , taking into account network and application parameters at the time of negotiation.
- DPMA Dynamic Profile Management Algorithm
- the G-QoS protocol allows the G-QoS negotiators to communicate with each other, and further allows the DPMAs residing therein to negotiate, establish, and maintain the desired QoS level.
- G-QoS negotiators 25 , 30 store application data, network data, and QoS information in G-QoS protocol 28 .
- Application data originating from user client application 15 and server application 20 is then forwarded to socket layers 35 and 40 , respectively, whereupon communication between socket layers 35 , 40 can be effectuated across a network in any fashion presently known in the art.
- Socket layers 35 , 40 include, but are not limited to, a variety of transport protocols such as Transmission Control Protocol (“FCP”), User Datagram Protocol (“UDP”).
- FCP Transmission Control Protocol
- UDP User Datagram Protocol
- G-QoS negotiators 25 , 30 and G-QoS protocol 28 can be implemented and maintained using a G-QoS API 32 .
- G-QoS API 32 is available in both the client machine and the server machine, and allows network administrators and other personnel to easily install, configure, and maintain the G-QoS protocol. Further, G-QoS API 32 can be implemented in two embodiments.
- G-QoS API 32 is implemented as an application-based API, wherein applications can be connected to the network using connection-oriented or connectionless transport services.
- G-QoS protocol 28 G-QoS negotiators 25 , 30 are controlled by the API to establish a desired level of QoS for the application and to synchronize the client and server so that the desired QoS level is maintained therebetween.
- G-QoS API 32 can be configured in a second embodiment, whereby the API utilizes G-QoS protocol 28 to define sockets that are necessary to support a QoS level for the application.
- G-QoS protocol 28 in conjunction with sockets, may be utilized to maintain a desired QoS level for IP-based traffic, such as IP and Virtual Private Network (“VPN”) tunneling.
- IP-based traffic such as IP and Virtual Private Network (“VPN”) tunneling.
- VPN Virtual Private Network
- FIG. 2 is a diagram showing in detail the components of the G-QoS protocol 28 of the present invention.
- G-QoS protocol 28 is used to exchange messages between the G-QoS negotiators 25 , 30 of FIG. 1 , and to store application profile, client profile, transport profile, and QoS information for usage by both the G-QoS negotiators and the DPMAs residing therein to negotiate, establish, and maintain the desired QoS level.
- G-QoS protocol 28 contains a variety of fields of information, and can be expanded to incorporate additional profiles, protocols, and other parameters as they are developed.
- G-QoS protocol 28 comprises a series of discreet units, each representing application-specific, network-specific, and QoS-specific information.
- the first unit, ICMP header unit 41 contains information utilized by the G-QoS negotiators to communicate with each other via ICMP messages.
- the first field, “ICMP msg type,” stores the type of ICMP message that the G-QoS negotiators use to communicate.
- the second field, “code,” stores information further defining the ICMP message type stored in the first field.
- the third field, “checksum,” stores checksum information utilized to verify data integrity during transmission.
- the fourth field, “process id,” identifies the process residing on both the client and the server responsible for QoS negotiation.
- the fifth field, “final profile,” is set by a G-QoS negotiator residing at a server, and indicates whether the server G-QoS negotiator has selected a profile type, protocol, and transport medium to use for communication with the client machine.
- the sixth field, “class,” stores the final profile class type resulting from negotiation between the G-QoS negotiators.
- the seventh field, “validity,” stores validity information pertaining to the “final profile” and “class” fields. This field can vary according to the type of G-QoS message.
- the eighth field, “version,” stores the current version of the G-QoS protocol.
- the final field, “Total msg length,” stores the total length of the ICMP message.
- ICMP header unit 41 is accessible by both the client and server G-QoS negotiators, and serves as a common repository for exchanging ICMP message information between the client and the server.
- the field is set to “client.”
- the next field, “PC type,” indicates the type of processor of the client machine.
- the next two fields, “OS type, ver,” store information about the operating system and version of the client machine.
- the next field, “ethernet,” stores information about the client's Ethernet connection, if the client is connected via an Ethernet network.
- the field “DSL” stores information about the client's Digital Subscriber Loop (“DSL”) connection, if the client is connected via a DSL connection.
- the field “OC3/12” stores information about any underlying OC3/12 connections existing between the client and the server.
- the field “max speed avail” stores information about the maximum transmission speed of the underlying wide-area network.
- the above fields form part of client information unit 42 , are set by the client-side G-QoS negotiator, and are utilized by both the client- and server-side G-QoS negotiators in calculating a QoS level.
- G-QoS protocol 28 further comprises proxy information unit 43 .
- Proxy information unit 43 stores information about any proxy servers utilized by the client or the server, if such proxy servers exist.
- the first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted in FIG. 2 as being set to “proxy,” thereby indicating that proxy information will follow. For this unit, the field is set to “proxy.”
- the second field, “proxy IP addr,” represent the IP address of the proxy server.
- the final field, “proxy port no,” represents the TCP or UDP port number utilized by the proxy server. Either client- or server-side G-QoS negotiators can determine proxy information, store such information in proxy information unit 43 , and later use the information in determining a desired QoS level.
- G-QoS protocol 28 further comprises application profile unit 44 .
- Application profile unit 44 stores information about either the client or server application. Both the client-side and the server-side G-QoS negotiators, upon analyzing either the client or server applications, generate application profile information and store same in application profile unit 44 .
- the first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted in FIG. 2 as being set to “Appl. type,” thereby indicating that application type information will follow.
- the field “from web” contains application source information indicating whether the application was generated over the web or in a traditional client/server environment. This information is critical if the application does not require a communication with a peer end.
- the “validity” field specifies whether or not the application profile unit is valid, and can be used when the G-QoS message is generated.
- the “App. Class” field denotes the profile class required by specific applications.
- the “data rate” field record data transmission rates, if known at the time of transmission.
- the “name” field stores the generic name of the application that can be used by the server to find the correct profile requirement.
- the field “BW reqd.” stores bandwidth requirements for the application, and can be set to a minimum or optimum value for a given application.
- the field “new appl. name” can be used to store information about the application if the application does not fit within the client/server model, or if it is a new application that does not match any of the defined profile categories.
- G-QoS protocol 28 further comprises transport QoS profile unit 45 .
- the first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted in FIG. 2 as being set to “QoS profile,” thereby indicating that QoS profile information will follow.
- the remaining fields “TCP” through “SS7” contain information identifying the available protocols at the client, in addition to the protocol grants allowed by the server. Such protocols can include, but are not limited to, TCP, UDP, ATM, T1, E1, FR, VPN, MPLS, RSVP, DTM, DWDM, GSM, TDMA, and SS7.
- G-QoS protocol 28 further comprises per-protocol QoS profile unit 46 .
- the first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted in FIG. 2 as being set to “QoS sub-profile,” thereby indicating that QoS sub-profile information will follow.
- the “validity” field indicates the validity of QoS profile unit 46 .
- the fields “tr.sub1” and “tr.sub2” are dependent upon information stored in Transport QoS profile unit 45 , and may contain any available sub-protocol profile information. For example, the field “tr.sub1” may store the ATM address or BHLI information of any available servers.
- G-QoS protocol 28 further comprises QoS map unit 47 .
- the first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted in FIG. 2 as being set to “MAP seq.,” thereby indicating that QoS mapping sequence information will follow.
- the information stored in QoS map unit 47 indicates QoS server profile orders that are determined by the G-QoS negotiators. Using this information, the client can choose a specific server to which it can then connect. For example, if the first field of the map order contains information such as “3.1,” the third protocol stored in transport QoS profile 45 and the first sub-protocol stored in per-protocol unit 46 will be utilized to set up a connection between the client and the server.
- the G-GoSN negotiator will then utilize the above pseudocode to store pertinent network information in the G-QoS protocol.
- a series of transport-and protocol-specific flags in the G-QoS protocol are then set.
- the “client_has” and “sub_profile” fields of the transport QoS profile unit of the G-QoS protocol, described above, are set to boolean “true.”
- fields of the per-protocol QoS profile unit of the G-QoS protocol, also described above, are set.
- the “validity” field is set to boolean “true”
- the “tr.subl” field is set to “3.1”
- the tr.subl.parameter field is set to the PVC connection values calculated by the G-QoS negotiator.
- the G-GoSN negotiator will then utilize the above pseudocode to store pertinent network information in the G-QoS protocol.
- the transport-and protocol-specific flags in the G-QoS protocol are set.
- the “client_has” and “sub_profile” fields of the transport QoS profile unit of the G-QoS protocol are set to boolean “true.”
- fields of the per-protocol QoS profile unit of the G-QoS protocol are set. Specifically, the “validity” field is set to boolean “true,” the “tr.sub2” field is set to “3.2,” and the tr.sub2. parameter field is set to either the ATM address or BHLI information calculated by the G-QoS negotiator.
- FIG. 4 depicted is a diagram showing the QoS negotiation procedures between G-QoS negotiators residing at client and server machines.
- Negotiation allows the G-QoS negotiators to properly map a given client machine to a server machine, to acquire knowledge of the client platform, access network, operating system, local gateway, network access support information, application type, and multi-service requirements.
- the G-QoS negotiators calculate an acceptable QoS level for both the client and the server, and identify information rates, response times, security levels, and acceptable error levels for the data to be transmitted from the client to the server.
- the QoS negotiation procedures allow the architecture of the present invention to adjust to connection-oriented versus connection-less services, variations in bandwidth, delays in transmission, and variance/channel errors.
- the entire architecture of the present invention can dynamically adjust to a variety of changing data and network parameters.
- FIG. 4 Depicted in FIG. 4 is the exchange of messages, similar to the message illustrated in Table 2, achieved by the architecture 10 of the present invention.
- Four distinct, communicating elements are depicted; namely, client application 15 , client G-QoS negotiator 25 , server application 10 , and server G-QoS negotiator 30 .
- client application 15 client G-QoS negotiator 25
- server application 10 server G-QoS negotiator 30
- the client application and the server applications 15 , 20 communicate with each other using a channel having a desired QoS level. Prior to such communication, however, an exchange of messages must occur.
- connection request is received by the client G-QoS negotiator 25 , thereby prompting client G-QoS negotiator 25 to operate in conjunction with server G-QoS negotiator 30 to establish an end-to-end connection between client application 15 and server application 20 .
- server G-QoS negotiator 30 Prior to establishing the end-to-end connection, and upon receiving the connection request from client G-QoS negotiator 25 , server G-QoS negotiator 30 transmits and receives connection indication and confirmation messages with server application 20 . Then, using the QoS profile and transport information already negotiated by client and server G-QoS negotiators 25 , 30 , both the client application 15 and the server application 20 may begin communicating with each other.
- the communication between client application 15 and server application 20 represents an end-to-end connection that has a desired QoS level achieved by the QoS negotiation procedures.
- FIG. 5 is a peer-to-peer entity diagram showing the G-QoS protocol of the present invention 10 . Shown are the peer-to-peer relationships for both a client G-QoS negotiator 50 and a server G-QoS negotiator 60 , both of which are responsible for the G-QoS negotiation process. Further shown are three relationships existing at application layer 52 , G-QoS protocol layer 66 , and transport protocol layer 68 . Depicted are only a few transport protocol methods at transport protocol layer 68 , it being understood that additional protocols may be include.
- the G-QoS protocol of the present invention 10 is positioned at G-QoS protocol layer 66 , below application layer 52 , and is responsible for negotiating the correct QoS profile needed for a particular application.
- G-QoS protocol layer 66 comprises message queue layer 54 , dynamic cache layer 56 , resource management layer 58 , application QoS profile layer 60 , mapping function layer 62 , and transport QoS profile layer 64 .
- G-QoS protocol layer 66 maps the application profile to the transport profile using a mapping function in mapping function layer 62 . The mapping function is accomplished by automatically extracting the client information from the client machine and formulating appropriate messages for the G-QoS message exchanges.
- FIG. 6 a is a state diagram showing the DPMA algorithm of the present invention implemented in a G-QoS negotiator at a client machine.
- the client and server G-QoS negotiators are responsible for negotiating, establishing, and maintaining a desired QoS level for client and server applications by communicating with each other using the G-QoS protocol of the present invention.
- the negotiation procedures, described above, are enabled by the DPMA of the present invention.
- the DPMA may be embodied in two forms, each specifically tailored for client and server G-QoS negotiators.
- the DPMA provides the logic necessary for the G-QoS negotiators to negotiate, establish, and maintain the QoS level.
- FIG. 6 a Depicted in FIG. 6 a is the DPMA of the G-QoS architecture 10 of the present invention, as implemented in a client G-QoS negotiator.
- This state diagram shows a variety of states of operation, each of which are executed by the client to effectuate QoS negotiation with a server G-QoS negotiator.
- initial state 100 an application request message is received by the client G-QoS negotiator from a client application.
- Initial state 100 gathers the application name and other parameters, and forwards same to state 105 .
- QoS negotiation is effectuated between the client and the server.
- State 105 retrieves the application information gathered by state 100 , including, but not limited to, application name, application type, bandwidth requirements, and data rate requirements, and converts same into a QoS request message. Additionally, state 105 stores client information, application QoS profile requirements, and client-side protocol availability information in the G-QoS protocol. State 105 then sends the QoS request message to the server G-QoS negotiator, and waits for a response. Importantly, while state 105 waits for the response, it may also construct and send additional QoS profile requests to the server G-QoS negotiator in the manner described.
- a QoS request message can be configured in the manner depicted in block 110 to contain application type data, resource identification data, and desired application QoS profile information.
- a QoS response message is received by state 105 , in can be processed in the manner depicted in block 115 , wherein remote resources are identified and application QoS profile identifiers are confirmed.
- both of the exemplary procedures depicted by blocks 110 , 115 can be performed by state 105 .
- State 120 represents a resource setting state, wherein local resources are configured according to the QoS profile information negotiated in state 105 . Specifically, in response to such information, state 120 sets up application queues, configures transport buffer and cache policies, and dimensions parameters that are utilized to maintain the agreed-upon QoS level. Importantly, the client application profile is mapped by state 120 to a transport profile negotiated in step 105 .
- Depicted in block 125 are procedures accomplished by state 120 to set local resources in response to the negotiated QoS profile and transport parameters. Specifically, application queues are set, transport buffer and cache parameters are configured, policies are set, application QoS profiles are mapped to transport QoS profiles, and monitoring parameters are dimensioned. Once these procedures have been completed, state 120 then invokes state 135 .
- state 135 dynamic profile management of the QoS parameters is accomplished.
- client parameters are monitored, including buffer and cache management status. Specifically, the buffer and caches are monitored and compared to a pre-determined threshold, X. min . If the measured values of the buffer and the cache are the same as the predetermined threshold, no information is sent to the server G-QoS negotiator. However, if the measured values fall below the predetermined threshold, as indicated in state 140 , the buffers and caches are set to a higher value, specifically X min +Delta. The higher value is monitored by state 140 so that it does not exceed a second predetermined threshold. Additionally, state 140 sends a QoS request message to the server G-QoS negotiator.
- Procedures for doing so are depicted in block 130 , wherein the application type, resource identification, profile change, and current application QoS profile identification information are gathered and sent to the server G-QoS negotiator.
- the server G-QoS negotiator adjusts its buffer and cache values, such that the adjusted values do not exceed the second predetermined threshold.
- States 135 and 140 continue to loop until the client application has terminated, thereby dynamically adjusting local and remote buffer and cache parameters as the application executes. This thereby allows the QoS for the application to be adjusted dynamically, in response to changing network and application conditions.
- state 145 is invoked, wherein resources utilized by all of the states and procedures of FIG. 6 a are released future use. Further, state 145 then re-invokes state 100 , so that the DPMA can then be applied to another client application.
- FIG. 6 b is a state diagram showing the DPMA algorithm of the present invention implemented in a G-QoS negotiator at a server machine.
- the DPMA algorithm executed on a server is similar in concept to the DPMA algorithm executed on the client, with certain differences. Specifically, a variety of states 200 , 205 , 220 , 235 , 240 , and 245 are executed in the server G-QoS negotiator, but according to different procedures.
- This information is stored in a QoS response message by state 205 , and sent to the client G-QoS negotiator.
- the QoS response may be set by state 205 according to the procedure depicted in block 215 , wherein local resources are identified, and application QoS profile identifications are confirmed, both of which are sent in the QoS response message to the client machine.
- state 220 is invoked, wherein local resources are set according to the QoS response message.
- server G-QoS negotiator can adjust a variety of server parameters according to the procedures depicted in block 225 . For example, application queues are set, transport buffer and cache parameters set, local policies set, application QoS profiles mapped to transport QoS profiles, and monitoring parameters are set for dynamic buffer and cache management.
- state 220 then invokes state 235 .
- state 235 dynamic profile management of the QoS parameters is accomplished.
- client parameters are monitored, including buffer and cache management status. Such parameters are adjusted in response to a QoS request message sent by the client.
- the server G-QoS negotiator can dynamically adjust local buffer and cache values in response. First, local buffer and cache values are measured and compared to a predetermined threshold, X min . If the values do not exceed the predetermined threshold, or if no QoS request message is received at the server, no action is taken.
- a QoS request message is received, it is processed by state 235 according to the procedure depicted in block 230 , wherein application type, resource identification, profile change, and application QoS identification information is obtained. Further, if the measured values of the buffer and cache fall below the predetermined threshold, or if a QoS request message is received, the server buffer and cache values can be adjusted in state 240 to a value min +Delta, such that the newly adjusted value does not exceed a second predetermined threshold.
- state 235 is re-invoked. States 235 and 240 loop throughout the duration of the application, so that the QoS parameters of the server can be dynamically adjusted according to changing application and network conditions.
Abstract
Description
- This application claims the benefit of and is a continuation-in-part of U.S. patent application Ser. No. 09/435,549, filed Nov. 8, 1999 by Vaman, et al., the entire disclosure of which is expressly incorporated herein by reference.
- 1. Field of the Invention
- This invention relates generally to a generic quality of service (“QoS”) protocol for user applications communicating via a network connected between a client machine and a server machine. More specifically, the invention provides a generic QoS protocol and architecture for ensuring user applications with a desired level of QoS, regardless of the underlying processors, operating systems, network hardware, and transport protocols utilized by the user applications.
- 2. Related Art
- Establishing guaranteed QoS for user applications communicating over a network represents a highly-desired goal in the electronic communications art. There is presently a need to provide individuals, including applications developers, software engineers, and network users, with a simple and efficient QoS protocol that allows a given application running on a client machine to communicate with another application running on a server machine while guaranteeing a desired QoS level throughout the entire period of communication. Applications using the communications network should be able to exchange data across a channel having guaranteed bandwidth and QoS policies, regardless of the underlying processors, operating systems, and network architectures across which the data may traverse. Present QoS solutions, however, are limited to specific transport protocol types and network architectures, and lack the ability to span a variety of such protocol types and architectures.
- Accordingly, what is desired, but has not heretofore been provided, is a generic quality of service protocol and architecture that provides user applications running over a network with a desired QoS level regardless of the processor architectures, operating systems, network architectures, and transport protocols used by the applications. What is also desired is a means for maintaining the desired QoS level by performing real-time monitoring and management of network and application parameters including bandwidth, buffer, and cache status, and which can be easily implemented and managed using an Application Programmer Interface (“API”).
- The Multimedia Communications Forum presented a QoS interoperability model for promoting the use of heterogeneous broadband access networks to support end-user applications. This model supports connection of broadband access networks via switches or combinations of enterprise and backbone networks. According to this model, QoS interoperability is achieved provided that applications running on the network can communicate with a desired QoS.
- U.S. patent application Ser. No. 09/435,549 to Vaman. et al., filed Nov. 8, 1999 and currently pending, discloses a method of QoS negotiation between client and server machines for facilitating simultaneous use of and access to Asynchronous Transfer Mode (“ATM”) and Internet Protocol (“IP”) -based networks, wherein desired QoS levels are supported for user applications communicating thereon.
- Efforts by the Internet Engineering Task Force (“IETF”), IEEE 802, and ASC T1 are currently formulating a specification for QoS for transport protocols only. These efforts, however, do not define a generic QoS protocol and maintenance procedures thereof.
- None of the previous efforts, either alone or in combination, disclose or teach the benefits of the method and apparatus of the present invention, nor do they teach or suggest all of the elements thereof.
- It is a primary object of this invention to provide a generic QoS protocol and architecture for applications running over networks.
- It is also an object of the present invention to provide a generic QoS protocol and architecture that can be implemented across various processor architectures, network architectures, operating systems, and communications protocols.
- It is a further object of the invention to provide a generic QoS protocol and architecture that supports multiple transport protocol environments.
- It is still another object of the present invention to provide real-time monitoring and management of network and application parameters, including bandwidth, buffer, and cache status information.
- It is yet another object of the present invention to establish and maintain a desired QoS level for applications communicating over a network using a dynamic profile management algorithm.
- It is an object of the present inventions provide an Application Programmer Interface (“API”) for easily implementing, monitoring, and maintaining the generic QoS protocol and architecture.
- It is a further object of the present invention to provide an API that can be implemented at the application or transport level.
- It is an object of the present invention to provide a generic QoS protocol and architecture that can be implemented without requiring modification to an operating system kernel.
- It is yet another object of the present invention to provide a generic QoS protocol that can be implemented as an out-of-band, peer-to-peer protocol.
- It is still another object of the present invention to provide a generic QoS protocol that can be implemented between an application and a socket layer.
- The present invention relates to a generic quality of service (“G-QoS”) protocol and architecture for user applications operating in multiple transport protocol environments. The G-QoS protocol and architecture allows applications communicating over a network to utilize a desired QoS level throughout the entire period of communication, independent of the processor architectures, operating systems, network architectures, and transport protocols utilized by the application. The protocol can be implemented between a client application and the socket layer of a communications channel, stores network and application data provided by G-QoS negotiators residing at both a client machine and a server machine, and can be implemented using out-f-band Internet Control Message Protocol (“ICMP”) messages. The G-QoS negotiators analyze a variety of network and application parameters including network bandwidth, transport protocols utilized, physical network architectures, and processor types to calculate an acceptable QoS level, and communicate with each other using the G-QoS protocol. Additionally, the G-QoS protocol includes a QoS profile that can be accessed by a variety of network architectures, operating systems, processor architectures, and transport protocols, so that each can establish the desired QoS level. A Dynamic Profile Management Algorithm (“DPMA”) allows the G-QoS negotiators to negotiate, establish, and maintain the desired QoS level. A proprietary API allows the G-QoS protocol, G-QoS negotiators, and DPMA to be easily implemented and maintained by network personnel. The G-QoS protocol, API, negotiators, and DPMA form a generic QoS architecture that provides applications running in multiple transport protocol environments with a guaranteed level of QoS.
- Other important objects and features of the invention will be apparent from the following Detailed Description of the Invention, taken in connection with the accompanying drawings, in which:
-
FIG. 1 is a diagram showing the G-QoS architecture of the present invention. -
FIG. 2 is a diagram showing in detail the components of the G-QoS protocol. -
FIG. 3 is a diagram showing transport QoS profile and client information blocks of the G-QoS protocol of the present invention. -
FIG. 4 is a diagram showing QoS negotiation procedures between a client and a server using the G-QoS protocol of the present invention. -
FIG. 5 is a peer-to-peer entity diagram showing the G-QoS protocol of the present invention. -
FIG. 6 a is a state diagram showing the DPMA algorithm of the present invention implemented in a client machine. -
FIG. 6 b is a state diagram showing the DPMA algorithm of the present invention implemented in a server machine. -
FIG. 1 is a diagram showing the generic quality of service (“G-QoS”)architecture 10 of the present invention. G-QoS architecture 10 comprises a variety of components, each of which operate in conjunction to provide a desired level of QoS for applications running in multiple transport protocol environments. Generally speaking, aclient application 15 can communicate with aserver application 20 using a communications channel that has a guaranteed QoS level. - A
user client application 15 desiring to communicate with aserver application 20 first transfers application data to a G-QoS negotiator 25, installed on the client machine. It is to be understood thatclient application 15, in addition toserver application 20, can be any network-ready computer applications presently known in the art.Server application 20 also transfers application data to a second G-QoS negotiator 30, residing on the same server asserver application 20. Both G-QoS negotiator 25 and second G-QoS negotiator 30 analyze the respective application data and network parameters, and communicate with each other over a network. In a preferred embodiment, both G-QoS negotiators - Communication between G-QoS
negotiators protocol 28. Upon communicating with each other, G-QoSnegotiators user client application 15 andserver application 20, taking into account network and application parameters at the time of negotiation. Negotiation, establishment, and maintenance of the acceptable QoS level is effectuated by a Dynamic Profile Management Algorithm (“DPMA”), illustrated inFIGS. 6 a, 6 b, and described in detail below. Importantly, the G-QoS protocol allows the G-QoS negotiators to communicate with each other, and further allows the DPMAs residing therein to negotiate, establish, and maintain the desired QoS level. - Once a desired QoS level has been established, G-
QoS negotiators QoS protocol 28. Application data originating fromuser client application 15 andserver application 20 is then forwarded tosocket layers - Once communication between socket layers 35, 40 has begun, an acceptable QoS level has been negotiated and stored in G-
QoS protocol 28. Throughout the period of communication between socket layers 35, 40, G-QoS protocol 28 is used by G-QoS negotiators - G-
QoS negotiators QoS protocol 28 can be implemented and maintained using a G-QoS API 32. G-QoS API 32 is available in both the client machine and the server machine, and allows network administrators and other personnel to easily install, configure, and maintain the G-QoS protocol. Further, G-QoS API 32 can be implemented in two embodiments. - In a first embodiment, G-
QoS API 32 is implemented as an application-based API, wherein applications can be connected to the network using connection-oriented or connectionless transport services. In this arrangement, G-QoS protocol 28 G-QoS negotiators - Attentively, G-
QoS API 32 can be configured in a second embodiment, whereby the API utilizes G-QoS protocol 28 to define sockets that are necessary to support a QoS level for the application. According to this implementation, G-QoS protocol 28, in conjunction with sockets, may be utilized to maintain a desired QoS level for IP-based traffic, such as IP and Virtual Private Network (“VPN”) tunneling. -
FIG. 2 is a diagram showing in detail the components of the G-QoS protocol 28 of the present invention. As mentioned earlier, G-QoS protocol 28 is used to exchange messages between the G-QoS negotiators FIG. 1 , and to store application profile, client profile, transport profile, and QoS information for usage by both the G-QoS negotiators and the DPMAs residing therein to negotiate, establish, and maintain the desired QoS level. G-QoS protocol 28 contains a variety of fields of information, and can be expanded to incorporate additional profiles, protocols, and other parameters as they are developed. - G-
QoS protocol 28 comprises a series of discreet units, each representing application-specific, network-specific, and QoS-specific information. The first unit,ICMP header unit 41, contains information utilized by the G-QoS negotiators to communicate with each other via ICMP messages. The first field, “ICMP msg type,” stores the type of ICMP message that the G-QoS negotiators use to communicate. The second field, “code,” stores information further defining the ICMP message type stored in the first field. The third field, “checksum,” stores checksum information utilized to verify data integrity during transmission. The fourth field, “process id,” identifies the process residing on both the client and the server responsible for QoS negotiation. The fifth field, “final profile,” is set by a G-QoS negotiator residing at a server, and indicates whether the server G-QoS negotiator has selected a profile type, protocol, and transport medium to use for communication with the client machine. The sixth field, “class,” stores the final profile class type resulting from negotiation between the G-QoS negotiators. The seventh field, “validity,” stores validity information pertaining to the “final profile” and “class” fields. This field can vary according to the type of G-QoS message. The eighth field, “version,” stores the current version of the G-QoS protocol. The final field, “Total msg length,” stores the total length of the ICMP message. As can be easily recognized,ICMP header unit 41 is accessible by both the client and server G-QoS negotiators, and serves as a common repository for exchanging ICMP message information between the client and the server. - G-
QoS protocol 28 further comprisesclient information unit 42.Client information unit 42 stores information about the client machine, and is utilized by the G-QoS negotiators and DPMAs to calculate a desired QoS level for the client and server applications. A client-side G-QoS negotiator analyzes the client machine, gathers information about that machine, and then stores the information inclient information unit 42, where it is later accessible by a server-side G-QoS negotiator. The first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted inFIG. 2 as being set to “client,” thereby indicating that client information will follow. For this unit, the field is set to “client.” The next field, “PC type,” indicates the type of processor of the client machine. The next two fields, “OS type, ver,” store information about the operating system and version of the client machine. The next field, “ethernet,” stores information about the client's Ethernet connection, if the client is connected via an Ethernet network. The field “DSL” stores information about the client's Digital Subscriber Loop (“DSL”) connection, if the client is connected via a DSL connection. The field “OC3/12” stores information about any underlying OC3/12 connections existing between the client and the server. Finally, the field “max speed avail” stores information about the maximum transmission speed of the underlying wide-area network. The above fields form part ofclient information unit 42, are set by the client-side G-QoS negotiator, and are utilized by both the client- and server-side G-QoS negotiators in calculating a QoS level. - G-
QoS protocol 28 further comprisesproxy information unit 43.Proxy information unit 43 stores information about any proxy servers utilized by the client or the server, if such proxy servers exist. The first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted inFIG. 2 as being set to “proxy,” thereby indicating that proxy information will follow. For this unit, the field is set to “proxy.” The second field, “proxy IP addr,” represent the IP address of the proxy server. The final field, “proxy port no,” represents the TCP or UDP port number utilized by the proxy server. Either client- or server-side G-QoS negotiators can determine proxy information, store such information inproxy information unit 43, and later use the information in determining a desired QoS level. - G-
QoS protocol 28 further comprisesapplication profile unit 44.Application profile unit 44 stores information about either the client or server application. Both the client-side and the server-side G-QoS negotiators, upon analyzing either the client or server applications, generate application profile information and store same inapplication profile unit 44. The first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted inFIG. 2 as being set to “Appl. type,” thereby indicating that application type information will follow. The field “from web” contains application source information indicating whether the application was generated over the web or in a traditional client/server environment. This information is critical if the application does not require a communication with a peer end. The “validity” field specifies whether or not the application profile unit is valid, and can be used when the G-QoS message is generated. The “App. Class” field denotes the profile class required by specific applications. The “data rate” field record data transmission rates, if known at the time of transmission. The “name” field stores the generic name of the application that can be used by the server to find the correct profile requirement. The field “BW reqd.” stores bandwidth requirements for the application, and can be set to a minimum or optimum value for a given application. The field “new appl. name” can be used to store information about the application if the application does not fit within the client/server model, or if it is a new application that does not match any of the defined profile categories. The “validity” field indicates the validity of the “new appl. Name” field. The “response time” field may be used to store minimum response time requirements or DPMA dynamic monitoring parameters if an application is delay-sensitive. Finally, the second “validity” field, located next to the “response time” field, identifies the validity of the “response time” field. - G-
QoS protocol 28 further comprises transportQoS profile unit 45. The first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted inFIG. 2 as being set to “QoS profile,” thereby indicating that QoS profile information will follow. The remaining fields “TCP” through “SS7” contain information identifying the available protocols at the client, in addition to the protocol grants allowed by the server. Such protocols can include, but are not limited to, TCP, UDP, ATM, T1, E1, FR, VPN, MPLS, RSVP, DTM, DWDM, GSM, TDMA, and SS7. - G-
QoS protocol 28 further comprises per-protocolQoS profile unit 46. The first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted inFIG. 2 as being set to “QoS sub-profile,” thereby indicating that QoS sub-profile information will follow. The “validity” field indicates the validity ofQoS profile unit 46. The fields “tr.sub1” and “tr.sub2” are dependent upon information stored in TransportQoS profile unit 45, and may contain any available sub-protocol profile information. For example, the field “tr.sub1” may store the ATM address or BHLI information of any available servers. - Finally, G-
QoS protocol 28 further comprisesQoS map unit 47. The first field, “IE id,” is an information element identifier, and for illustrative purposes, is depicted inFIG. 2 as being set to “MAP seq.,” thereby indicating that QoS mapping sequence information will follow. The information stored inQoS map unit 47 indicates QoS server profile orders that are determined by the G-QoS negotiators. Using this information, the client can choose a specific server to which it can then connect. For example, if the first field of the map order contains information such as “3.1,” the third protocol stored intransport QoS profile 45 and the first sub-protocol stored in per-protocol unit 46 will be utilized to set up a connection between the client and the server. - Referring to
FIG. 3 , depicted is a diagram showing further detail of transport QoS 5profile unit 45 andclient information unit 42 of the G-QoS protocol 28 of the present invention. TransportQoS profile unit 45 further comprises block 45 a, which stores at least three fields. The first field, “client has,” indicates whether the client has a particular protocol available at its end. The next field, “grant by server,” stores a boolean value indicating whether the particular protocol exists and whether a decision was made for the particular protocol to be used to communicate with a server listed in the map order, described above. The “sub-profile” field indicates whether the particular protocol has the sub-profile per-protocol QoS profile information settings recorded in per-protocolQoS profile unit 46 ofFIG. 2 , described above. Additionally,client information unit 42 of G-QoS protocol 28 is capable of storing further information pertaining to the client machine, as depicted inblocks block 42 a, information pertaining to the operating system of the client machine is stored. Exemplary entries include various versions of the Windows operating system by Microsoft, but can also include other operating system types, such as UNIX. Other information, such as server or workstation configurations, can be stored inblock 42 b. Further, the processor architecture of the client can be stored in 42 c, including such architectures as MIPS by MIPS Technologies, Inc., Alpha by Compaq, PowerPC by Motorola, and other processor architectures. Additionally, information pertaining to the network interface of the client machine can be stored inblock 42 d, including physical network information such as 10-Base-T, 100-Base-T, or Gigabit Ethernet. All of the information depicted inFIG. 3 forms part of the G-QoS protocol 28, and can be utilized in achieving a desired QoS level by the architecture of the present invention. - In a preferred embodiment of the present invention, G-
QoS protocol 28 is utilized to effectuate negotiation of a desired QoS level by the G-QoS negotiators, and to store application information, network information, and QoS information to establish and maintain the QoS level during the period of communication. To achieve QoS-negotiation, such information must first be stored in the G-QoS protocol 28 of the present invention by a G-QoS negotiator residing at either a client or a server machine. Storage of such information may be accomplished by an algorithm, listed below in pseudocode:TABLE 1 If ATM present { check if PVC present or SVC present} If PVC present { Set Transport_QoS_profile -> ATM.client_has = TRUE; Set Transport_QoS_profile -> ATM.sub_profile = TRUE; Set Per_Protocol_QoS_profile -> validity = TRUE; Set Per_Protocol_QoS_profile -> tr.sub1 = 3.1; Set Per_Protocol_QoS_profile -> tr.sub1.parameter = PVC connection values; } If SVC present { Set Transport_QoS_profile -> ATM.client_has = TRUE; Set Transport_QoS_profile -> ATM.sub_profile = TRUE; Set Per_Protocol_QoS_profile -> validity = TRUE; Set Per_Protocol_QoS_profile -> tr.sub2 = 3.2; Set Per_Protocol_QoS_profile -> tr.sub2 = ATM addres or BHLI info } - According to the pseudocode of Table 1, a G-QoS negotiator residing at a client machine first checks to determine if the client is connected to an Asynchronous Transfer Mode (“ATM”) network. If so, a check is the performed to determine whether the ATM network is configured in Permanent Virtual Circuit (“PVC”) mode or Switched Virtual Circuit (“SVC”) mode.
- If a PVC connection is preset, the G-GoSN negotiator will then utilize the above pseudocode to store pertinent network information in the G-QoS protocol. A series of transport-and protocol-specific flags in the G-QoS protocol are then set. First, the “client_has” and “sub_profile” fields of the transport QoS profile unit of the G-QoS protocol, described above, are set to boolean “true.” Then, fields of the per-protocol QoS profile unit of the G-QoS protocol, also described above, are set. Specifically, the “validity” field is set to boolean “true,” the “tr.subl” field is set to “3.1,” and the tr.subl.parameter field is set to the PVC connection values calculated by the G-QoS negotiator.
- Similarly, if an SVC connection is present, the G-GoSN negotiator will then utilize the above pseudocode to store pertinent network information in the G-QoS protocol. The transport-and protocol-specific flags in the G-QoS protocol are set. First, the “client_has” and “sub_profile” fields of the transport QoS profile unit of the G-QoS protocol are set to boolean “true.” Then, fields of the per-protocol QoS profile unit of the G-QoS protocol are set. Specifically, the “validity” field is set to boolean “true,” the “tr.sub2” field is set to “3.2,” and the tr.sub2. parameter field is set to either the ATM address or BHLI information calculated by the G-QoS negotiator.
- It is to be understood that the above pseudocode can be modified to apply to other network architectures, such as Ethernet. The information stored using the algorithm of Table 1 will be utilized by the G-QoS negotiator to negotiate a desired QoS level with another G-QoS negotiator, and to maintain the desired QoS level once it has been established.
- Turning now to
FIG. 4 , depicted is a diagram showing the QoS negotiation procedures between G-QoS negotiators residing at client and server machines. Negotiation allows the G-QoS negotiators to properly map a given client machine to a server machine, to acquire knowledge of the client platform, access network, operating system, local gateway, network access support information, application type, and multi-service requirements. Using this information, the G-QoS negotiators calculate an acceptable QoS level for both the client and the server, and identify information rates, response times, security levels, and acceptable error levels for the data to be transmitted from the client to the server. Further, the QoS negotiation procedures allow the architecture of the present invention to adjust to connection-oriented versus connection-less services, variations in bandwidth, delays in transmission, and variance/channel errors. Thus, using QoS negotiation, the entire architecture of the present invention can dynamically adjust to a variety of changing data and network parameters. - In a preferred embodiment of the present invention, the QoS negotiation procedures comprise the exchange of G-QoS messages between the client and server G-QoS negotiators. These messages allow each of the G-QoS negotiators to arrive at a desired QoS level prior to establishing a connection between the client and the server. Such messages include, but are not limited to, the following types: profile request messages, profile response messages, profile indication messages, profile conformation messages, connection request messages, connection response messages, connection indication messages, and connection confirmation messages. The transmission of such messages can be regulated by adjusting various parameters of the G-QoS protocol, either in response to network conditions or a network administrator's initiative.
- For illustrative purposes, a sample profile request message is shown below:
TABLE 2 G-QoS->ApplType.i_appl_InformationElement = IE_QOS_APPL PROFILE; G-QoS->ClientInfo.i_cl_InformationElement = IE_CLIENT; G-QoS->MapSequence.i_map_InformationElement = IE_MAP ORDER; G-QoS->ProxyInfo.i_pxy_InformationElement = IE_PROXY; G-QoS->SubHeader.i_InformationElement = IE_SUBHEADER; G-QoS->TransportProfile.i_tr_InformationElement = IE_QOS_TRANSPORT_PROFILE; G-QoS->TransportSubProfile.i_trsub_InformationElement = IE_QOS_SUBPROFILE; G-QoS->ApplType.i_appl_validity = ENABLE; G-QoS->ClientInfo.i_c1_validity = ENABLE; G-QoS->MapSequence.i_map_validity = DISABLE; G-QoS->SubHeader.final_profile.i_validity = DISABLE; G-QoS->TransportProfile.i_tr_validity = ENABLE; - The message depicted in Table 2 represents a sample profile request sequence achieved by the present invention. The message sequence is utilized to set a variety of the parameter of the G-QoS protocol, described in detail above and illustrated in
FIGS. 2,3 . The messages created by the G-QoS negotiators set specific G-QoS protocol parameters, which in turn are used by the client and server machines to effectuate a connection therebetween. For example, the first line of Table 2 illustrates an application type message which sets the “IE id” field of theapplication profile unit 44 ofFIG. 2 to “IE_QoS_APPL_PROFILE.” This designation can then be utilized by the client or the server to extract application profile information from the G-QoS protocol and thereafter establish a connection with a selected server. It is to be understood that additional profile request messages and settings not illustrated in Table 2 can be include in the invention. - Depicted in
FIG. 4 is the exchange of messages, similar to the message illustrated in Table 2, achieved by thearchitecture 10 of the present invention. Four distinct, communicating elements are depicted; namely,client application 15, client G-QoS negotiator 25,server application 10, and server G-QoS negotiator 30. It is to be noted that, ultimately, the client application and theserver applications - First,
client application 15 sends a profile request message to client G-QoS negotiator 25. Then, upon receiving the message, G-QoS negotiator 25 sends a QoS negotiation request message to server G-QoS negotiator 30. The QoS negotiation request message contains information about the client, such information being derived from the client information stored in the G-QoS protocol fields, described above. Upon receiving the QoS negotiation request message, server G-QoS negotiator 30 receives an application initiation profile request fromserver application 20, which it utilizes in forming an appropriate response to the QoS negotiation request. Server G-QoS negotiator 30 then formulates a QoS negotiation response message, which contains a server map order determined by the server G-QoS negotiator 30, and ranked according to the QoS profiles of available servers. Further, the QoS negotiation response message contains QoS profile information that will be utilized in establishing an end-to-end connection between the client and server applications. Once the QoS negotiation response message has been formulated, server G-QoS negotiator 30 communicates withserver application 20 by exchanging application profile indication and confirmation messages. These messages can then be utilized by server G-QoS negotiator 30 to formulate the QoS negotiation response message. - The QoS negotiation response message is then sent back to client G-
QoS negotiator 25 by server G-QoS negotiator 30. It is important to note that the QoS negotiation response message contains transport profile setting information calculated by the server G-QoS negotiator. This information will then be utilized by client G-QoS negotiator 25 to communicate to establish an end-to-end connection betweenclient application 15 andserver application 20. Thus, when client G-QoS negotiator 25 receives the QoS negotiation response message, it forwards information toclient application 15 in the form of an application profile response message.Client application 15 then utilizes this information to initiate a connection request, based upon the QoS profile and transport information stored in the application profile response message. The connection request is received by the client G-QoS negotiator 25, thereby prompting client G-QoS negotiator 25 to operate in conjunction with server G-QoS negotiator 30 to establish an end-to-end connection betweenclient application 15 andserver application 20. - Prior to establishing the end-to-end connection, and upon receiving the connection request from client G-
QoS negotiator 25, server G-QoS negotiator 30 transmits and receives connection indication and confirmation messages withserver application 20. Then, using the QoS profile and transport information already negotiated by client and server G-QoS negotiators client application 15 and theserver application 20 may begin communicating with each other. The communication betweenclient application 15 andserver application 20 represents an end-to-end connection that has a desired QoS level achieved by the QoS negotiation procedures. -
FIG. 5 is a peer-to-peer entity diagram showing the G-QoS protocol of thepresent invention 10. Shown are the peer-to-peer relationships for both a client G-QoS negotiator 50 and a server G-QoS negotiator 60, both of which are responsible for the G-QoS negotiation process. Further shown are three relationships existing atapplication layer 52, G-QoS protocol layer 66, andtransport protocol layer 68. Depicted are only a few transport protocol methods attransport protocol layer 68, it being understood that additional protocols may be include. The G-QoS protocol of thepresent invention 10 is positioned at G-QoS protocol layer 66, belowapplication layer 52, and is responsible for negotiating the correct QoS profile needed for a particular application. G-QoS protocol layer 66 comprisesmessage queue layer 54,dynamic cache layer 56,resource management layer 58, applicationQoS profile layer 60,mapping function layer 62, and transportQoS profile layer 64. G-QoS protocol layer 66 maps the application profile to the transport profile using a mapping function inmapping function layer 62. The mapping function is accomplished by automatically extracting the client information from the client machine and formulating appropriate messages for the G-QoS message exchanges. The mapping function locates the correct profile, sets up the resources needed for the application, and dynamically manages the resources, cache, queues of the client or server. In a preferred embodiment, the mapping function of the G-QoS protocol is accomplished by the DPMA algorithm of the present invention, discussed below. -
FIG. 6 a is a state diagram showing the DPMA algorithm of the present invention implemented in a G-QoS negotiator at a client machine. As mentioned earlier, the client and server G-QoS negotiators are responsible for negotiating, establishing, and maintaining a desired QoS level for client and server applications by communicating with each other using the G-QoS protocol of the present invention. The negotiation procedures, described above, are enabled by the DPMA of the present invention. The DPMA may be embodied in two forms, each specifically tailored for client and server G-QoS negotiators. Importantly, the DPMA provides the logic necessary for the G-QoS negotiators to negotiate, establish, and maintain the QoS level. - Depicted in
FIG. 6 a is the DPMA of the G-QoS architecture 10 of the present invention, as implemented in a client G-QoS negotiator. This state diagram shows a variety of states of operation, each of which are executed by the client to effectuate QoS negotiation with a server G-QoS negotiator. Beginning ininitial state 100, an application request message is received by the client G-QoS negotiator from a client application.Initial state 100 gathers the application name and other parameters, and forwards same tostate 105. Instate 105, QoS negotiation is effectuated between the client and the server.State 105 retrieves the application information gathered bystate 100, including, but not limited to, application name, application type, bandwidth requirements, and data rate requirements, and converts same into a QoS request message. Additionally,state 105 stores client information, application QoS profile requirements, and client-side protocol availability information in the G-QoS protocol.State 105 then sends the QoS request message to the server G-QoS negotiator, and waits for a response. Importantly, whilestate 105 waits for the response, it may also construct and send additional QoS profile requests to the server G-QoS negotiator in the manner described. - Depicted in
blocks state 105. In one embodiment, a QoS request message can be configured in the manner depicted inblock 110 to contain application type data, resource identification data, and desired application QoS profile information. Further, when a QoS response message is received bystate 105, in can be processed in the manner depicted inblock 115, wherein remote resources are identified and application QoS profile identifiers are confirmed. Importantly, both of the exemplary procedures depicted byblocks state 105. - When a QoS response message is received from the server G-QoS negotiator in
state 105, it is then processed, and QoS profile map order information is retrieved therefrom. Additionally, remote resources are identified, andstate 105 then invokesstate 120.State 120 represents a resource setting state, wherein local resources are configured according to the QoS profile information negotiated instate 105. Specifically, in response to such information,state 120 sets up application queues, configures transport buffer and cache policies, and dimensions parameters that are utilized to maintain the agreed-upon QoS level. Importantly, the client application profile is mapped bystate 120 to a transport profile negotiated instep 105. - Depicted in
block 125 are procedures accomplished bystate 120 to set local resources in response to the negotiated QoS profile and transport parameters. Specifically, application queues are set, transport buffer and cache parameters are configured, policies are set, application QoS profiles are mapped to transport QoS profiles, and monitoring parameters are dimensioned. Once these procedures have been completed,state 120 then invokesstate 135. - In
state 135, dynamic profile management of the QoS parameters is accomplished. In this state, client parameters are monitored, including buffer and cache management status. Specifically, the buffer and caches are monitored and compared to a pre-determined threshold, X.min. If the measured values of the buffer and the cache are the same as the predetermined threshold, no information is sent to the server G-QoS negotiator. However, if the measured values fall below the predetermined threshold, as indicated instate 140, the buffers and caches are set to a higher value, specifically Xmin+Delta. The higher value is monitored bystate 140 so that it does not exceed a second predetermined threshold. Additionally,state 140 sends a QoS request message to the server G-QoS negotiator. Procedures for doing so are depicted inblock 130, wherein the application type, resource identification, profile change, and current application QoS profile identification information are gathered and sent to the server G-QoS negotiator. In response to this message, the server G-QoS negotiator adjusts its buffer and cache values, such that the adjusted values do not exceed the second predetermined threshold. -
States state 145 is invoked, wherein resources utilized by all of the states and procedures ofFIG. 6 a are released future use. Further,state 145 thenre-invokes state 100, so that the DPMA can then be applied to another client application. -
FIG. 6 b is a state diagram showing the DPMA algorithm of the present invention implemented in a G-QoS negotiator at a server machine. The DPMA algorithm executed on a server is similar in concept to the DPMA algorithm executed on the client, with certain differences. Specifically, a variety ofstates - Starting with
state 200, the server G-QoS negotiator awaits for a QoS request message from the server G-QoS negotiator. When a QoS request message is received,state 200 invokesstate 205. Instate 205, the QoS request message is analyzed according to the procedure described inblock 210, wherein client application type, resource identification, and application QoS profile identification information is extracted. Further, the application name and additional parameters are extracted and analyzed. Based upon this information, and the available QoS and transport profiles,state 205 constructs a QoS map order, which represents the various QoS profile sequences available for the client application to use. This information, along with local resource identification information, is stored in a QoS response message bystate 205, and sent to the client G-QoS negotiator. In one embodiment, the QoS response may be set bystate 205 according to the procedure depicted inblock 215, wherein local resources are identified, and application QoS profile identifications are confirmed, both of which are sent in the QoS response message to the client machine. - Once the QoS response message is constructed and sent in
state 205,state 220 is invoked, wherein local resources are set according to the QoS response message. Specifically, server G-QoS negotiator can adjust a variety of server parameters according to the procedures depicted inblock 225. For example, application queues are set, transport buffer and cache parameters set, local policies set, application QoS profiles mapped to transport QoS profiles, and monitoring parameters are set for dynamic buffer and cache management. Once resources are set,state 220 then invokesstate 235. - In
state 235, dynamic profile management of the QoS parameters is accomplished. In this state, client parameters are monitored, including buffer and cache management status. Such parameters are adjusted in response to a QoS request message sent by the client. If a QoS request message is received instate 235, the server G-QoS negotiator can dynamically adjust local buffer and cache values in response. First, local buffer and cache values are measured and compared to a predetermined threshold, Xmin. If the values do not exceed the predetermined threshold, or if no QoS request message is received at the server, no action is taken. If a QoS request message is received, it is processed bystate 235 according to the procedure depicted inblock 230, wherein application type, resource identification, profile change, and application QoS identification information is obtained. Further, if the measured values of the buffer and cache fall below the predetermined threshold, or if a QoS request message is received, the server buffer and cache values can be adjusted instate 240 to a value min+Delta, such that the newly adjusted value does not exceed a second predetermined threshold. - When
state 240 has finished adjusting local buffer and cache values,state 235 is re-invoked.States state 245 is invoked. Further profile requests and server resource configurations can occur according to the following equation:
[Y max−(X 1,max +X 2,max +. . . +X (n−1),max)]>−X n,max (1)
where Xn,max=Xmin+Δm, Δm=Δ1+Δ2+. . . ΔN, X=application, buffer, cache, bandwidth, and profile requirements, and Y =server G-QoS negotiator buffer, channel, cache, bandwidth, and profile availability. - Having thus described the invention in detail, it is to be understood that the foregoing description is not intended to limit the spirit and scope thereof. What is desired to be protected by Letters Patent is set forth in the appended claims.
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/672,713 US20070180073A1 (en) | 1999-11-08 | 2007-02-08 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US43554999A | 1999-11-08 | 1999-11-08 | |
US09/841,972 US7185070B2 (en) | 1999-11-08 | 2001-04-25 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
US11/672,713 US20070180073A1 (en) | 1999-11-08 | 2007-02-08 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/841,972 Continuation US7185070B2 (en) | 1999-11-08 | 2001-04-25 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070180073A1 true US20070180073A1 (en) | 2007-08-02 |
Family
ID=23728842
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/841,972 Expired - Lifetime US7185070B2 (en) | 1999-11-08 | 2001-04-25 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
US09/847,039 Expired - Lifetime US7293094B2 (en) | 1999-11-08 | 2001-05-01 | Method and apparatus for providing end-to-end quality of service in multiple transport protocol environments using permanent or switched virtual circuit connection management |
US11/382,221 Abandoned US20060195581A1 (en) | 1999-11-08 | 2006-05-08 | Method and apparatus for providing end-to-end quality of service in multiple transport protocol environments using permanent or switched virtual circuit connection management |
US11/672,713 Abandoned US20070180073A1 (en) | 1999-11-08 | 2007-02-08 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/841,972 Expired - Lifetime US7185070B2 (en) | 1999-11-08 | 2001-04-25 | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments |
US09/847,039 Expired - Lifetime US7293094B2 (en) | 1999-11-08 | 2001-05-01 | Method and apparatus for providing end-to-end quality of service in multiple transport protocol environments using permanent or switched virtual circuit connection management |
US11/382,221 Abandoned US20060195581A1 (en) | 1999-11-08 | 2006-05-08 | Method and apparatus for providing end-to-end quality of service in multiple transport protocol environments using permanent or switched virtual circuit connection management |
Country Status (3)
Country | Link |
---|---|
US (4) | US7185070B2 (en) |
AU (1) | AU2752201A (en) |
WO (1) | WO2001035243A1 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070297450A1 (en) * | 2006-06-21 | 2007-12-27 | Motorola, Inc. | Method and apparatus for passing an application description to lower layer packet data protocol |
US20080247326A1 (en) * | 2007-04-04 | 2008-10-09 | Research In Motion Limited | Method, system and apparatus for dynamic quality of service modification |
US20090063683A1 (en) * | 2007-08-31 | 2009-03-05 | Nokia Corporation | Information distribution in a dynamic multi-device environment |
US20090100152A1 (en) * | 2007-10-11 | 2009-04-16 | At&T Knowledge Ventures, L.P. | System for selecting a network element |
US20090141692A1 (en) * | 2007-11-30 | 2009-06-04 | Mika Kasslin | Optimized ad hoc networking |
US20100260067A1 (en) * | 2007-11-08 | 2010-10-14 | Nokia Corporation | Connectivity architecture for service discovery |
US20100318599A1 (en) * | 2009-06-15 | 2010-12-16 | Lg Electronics Inc. | Method for remotely controlling terminal device |
US20110002344A1 (en) * | 2008-02-27 | 2011-01-06 | Nokia Corporation | Buffer control for multi-transport architectures |
US20110004886A1 (en) * | 2008-02-27 | 2011-01-06 | Nokia Corporation | Transport independent architecture |
US20110299410A1 (en) * | 2010-06-04 | 2011-12-08 | Wael William Diab | Method and system for managing quality of service via a broadband gateway |
US20120033573A1 (en) * | 2009-06-12 | 2012-02-09 | Cygnus Broadband, Inc. | Systems and methods for intelligent discard in a communication network |
US9043853B2 (en) | 2009-06-12 | 2015-05-26 | Wi-Lan Labs, Inc. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US9112802B2 (en) | 2009-06-12 | 2015-08-18 | Wi-Lan Labs, Inc. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US9538132B2 (en) * | 2013-07-22 | 2017-01-03 | Tencent Technology (Shenzhen) Company Limited | Methods, devices, and systems for controlling audio and video transmission |
US20190123965A1 (en) * | 2013-03-15 | 2019-04-25 | Sony Interactive Entertainment Inc. | Profile generation for bandwidth management |
Families Citing this family (118)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7689857B2 (en) * | 2000-07-13 | 2010-03-30 | Computer Associates Think, Inc. | Method and apparatus for monitoring and maintaining user-perceived quality of service in a communications network |
US7290028B2 (en) * | 2000-08-24 | 2007-10-30 | International Business Machines Corporation | Methods, systems and computer program products for providing transactional quality of service |
US7089294B1 (en) * | 2000-08-24 | 2006-08-08 | International Business Machines Corporation | Methods, systems and computer program products for server based type of service classification of a communication request |
US6981263B1 (en) * | 2001-06-29 | 2005-12-27 | Bellsouth Intellectual Property Corp. | Methods and systems for converged service creation and execution environment applications |
US7103644B1 (en) * | 2001-06-29 | 2006-09-05 | Bellsouth Intellectual Property Corp. | Systems for an integrated data network voice-oriented service and non-voice-oriented service converged creation and execution environment |
US6980820B2 (en) * | 2001-08-20 | 2005-12-27 | Qualcomm Inc. | Method and system for signaling in broadcast communication system |
US6731936B2 (en) * | 2001-08-20 | 2004-05-04 | Qualcomm Incorporated | Method and system for a handoff in a broadcast communication system |
JP3852752B2 (en) * | 2001-11-16 | 2006-12-06 | パイオニア株式会社 | Apparatus and method for bandwidth control of communication information |
US20030101117A1 (en) * | 2001-11-29 | 2003-05-29 | International Business Machines Coproation | Generating contract requirements for software suppliers based upon assessing the quality levels of quality attributes of the suppliers |
US7305469B2 (en) * | 2001-12-18 | 2007-12-04 | Ebay Inc. | Prioritization of third party access to an online commerce site |
KR100547852B1 (en) * | 2002-01-09 | 2006-02-01 | 삼성전자주식회사 | Method for admitting call in mobile communication system |
EP1335535A1 (en) * | 2002-01-31 | 2003-08-13 | BRITISH TELECOMMUNICATIONS public limited company | Network service selection |
AU2003249115A1 (en) * | 2002-07-16 | 2004-02-02 | Nokia Corporation | Method for enabling packet transfer delay compensation in multimedia streaming |
FR2849313B1 (en) * | 2002-12-20 | 2005-03-11 | Cit Alcatel | DEVICE FOR MONITORING TREATMENTS ASSOCIATED WITH FLOWS WITHIN A COMMUNICATIONS NETWORK |
US6940813B2 (en) * | 2003-02-05 | 2005-09-06 | Nokia Corporation | System and method for facilitating end-to-end quality of service in message transmissions employing message queues |
US20050169305A1 (en) * | 2003-04-04 | 2005-08-04 | Masaru Mori | Mobile terminal and radio access point in radio access system |
US7206846B1 (en) * | 2003-04-29 | 2007-04-17 | Cisco Technology, Inc. | Method and apparatus for adaptively coupling processing components in a distributed system |
US7539741B2 (en) * | 2003-04-30 | 2009-05-26 | Nokia Siemens Networks Oy | System, apparatus and method for supporting constraint based routing for multi-protocol label switching traffic engineering in policy-based management |
US8521889B2 (en) * | 2003-05-15 | 2013-08-27 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for modifying bandwidth and/or quality of service for a user session in a network |
US8204042B2 (en) * | 2003-05-15 | 2012-06-19 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for establishing VoIP service in a network |
US7519916B1 (en) * | 2003-06-16 | 2009-04-14 | Microsoft Corporation | Methods for tailoring a bandwidth profile for an operating environment |
US8108520B2 (en) * | 2003-06-19 | 2012-01-31 | Nokia Corporation | Apparatus and method for providing quality of service for a network data connection |
US7613835B2 (en) * | 2003-09-08 | 2009-11-03 | Sony Corporation | Generic API for synchronization |
US7912485B2 (en) * | 2003-09-11 | 2011-03-22 | Qualcomm Incorporated | Method and system for signaling in broadcast communication system |
US7925790B2 (en) * | 2003-09-17 | 2011-04-12 | Sony Corporation | Middleware filter agent between server and PDA |
US20050060370A1 (en) * | 2003-09-17 | 2005-03-17 | Sony Corporation | Version based content distribution and synchronization system and method |
EP1668797B1 (en) * | 2003-09-30 | 2018-11-28 | Thomson Licensing | Quality of service control in a wireless local area network |
US7720948B2 (en) * | 2003-11-12 | 2010-05-18 | International Business Machines Corporation | Method and system of generically specifying packet classification behavior |
US7454496B2 (en) * | 2003-12-10 | 2008-11-18 | International Business Machines Corporation | Method for monitoring data resources of a data processing network |
US9323571B2 (en) * | 2004-02-06 | 2016-04-26 | Intel Corporation | Methods for reducing energy consumption of buffered applications using simultaneous multi-threading processor |
US8046464B2 (en) * | 2004-03-10 | 2011-10-25 | The Boeing Company | Quality of service resource management apparatus and method for middleware services |
US7478160B2 (en) * | 2004-04-30 | 2009-01-13 | International Business Machines Corporation | Method and apparatus for transparent negotiations |
US20050246187A1 (en) * | 2004-04-30 | 2005-11-03 | Reed Maltzman | System and method to facilitate differentiated levels of service in a network-based marketplace |
US7340258B2 (en) * | 2004-07-27 | 2008-03-04 | Lucent Technologies Inc. | Mobile phone combined with satellite radio capability |
US7359710B2 (en) * | 2004-07-27 | 2008-04-15 | Lucent Technologies Inc. | Satellite TV derivative programming via mobile phone |
US8570880B2 (en) * | 2004-08-05 | 2013-10-29 | Qualcomm Incorporated | Method and apparatus for receiving broadcast in a wireless multiple-access communications system |
US8024483B1 (en) | 2004-10-01 | 2011-09-20 | F5 Networks, Inc. | Selective compression for network connections |
US20060088034A1 (en) * | 2004-10-26 | 2006-04-27 | Nortel Networks Limited | Network service classes |
EP1814267B8 (en) * | 2004-11-11 | 2012-08-29 | Mitsubishi Electric Corporation | Ip packet relay method and gateway device in communication network |
US20060168288A1 (en) * | 2004-12-16 | 2006-07-27 | Michele Covell | Identifying failure of a streaming media server to satisfy quality-of-service criteria |
US7496653B2 (en) * | 2005-01-31 | 2009-02-24 | International Business Machines Corporation | Method, system, and computer program product for providing quality of service guarantees for clients of application servers |
EP1849099B1 (en) | 2005-02-03 | 2014-05-07 | Apple Inc. | Recommender system for identifying a new set of media items responsive to an input set of media items and knowledge base metrics |
US7440407B2 (en) * | 2005-02-07 | 2008-10-21 | At&T Corp. | Method and apparatus for centralized monitoring and analysis of virtual private networks |
US20060203722A1 (en) * | 2005-03-14 | 2006-09-14 | Nokia Corporation | System and method for managing performance of mobile terminals via remote diagnostics |
US9137330B2 (en) * | 2005-03-16 | 2015-09-15 | Alcatel Lucent | Method of dynamically adjusting quality of service (QoS) targets |
US20090040925A1 (en) * | 2005-03-21 | 2009-02-12 | Jarl Tomas Holmstrom | DEVICE HAVING QUALITY OF SERVICE (QoS) CONFIRMATION AND METHOD FOR CONFIGURING QoS |
US9401934B2 (en) * | 2005-06-22 | 2016-07-26 | Microsoft Technology Licensing, Llc | Establishing sessions with defined quality of service |
CN1905517A (en) * | 2005-07-30 | 2007-01-31 | 华为技术有限公司 | Control system and method for selecting for warding path for media stream in NGN network |
US7894815B2 (en) * | 2005-10-21 | 2011-02-22 | Electronics And Telecommunications Research Institute | Device for providing hand-off quality of service of inter-access systems and method thereof |
US7471664B2 (en) * | 2005-11-02 | 2008-12-30 | Intel Corporation | Network management policy and compliance in a wireless network |
US20070124485A1 (en) * | 2005-11-30 | 2007-05-31 | Microsoft Corporation | Computer system implementing quality of service policy |
US7979549B2 (en) * | 2005-11-30 | 2011-07-12 | Microsoft Corporation | Network supporting centralized management of QoS policies |
WO2007068119A1 (en) * | 2005-12-13 | 2007-06-21 | Audio Pod Inc. | Segmentation and transmission of audio streams |
WO2007075622A2 (en) | 2005-12-19 | 2007-07-05 | Strands, Inc. | User-to-user recommender |
US8170021B2 (en) | 2006-01-06 | 2012-05-01 | Microsoft Corporation | Selectively enabled quality of service policy |
US7873065B1 (en) | 2006-02-01 | 2011-01-18 | F5 Networks, Inc. | Selectively enabling network packet concatenation based on metrics |
BRPI0621315A2 (en) * | 2006-02-10 | 2011-12-06 | Strands Inc | dynamic interactive entertainment |
CN101496387B (en) * | 2006-03-06 | 2012-09-05 | 思科技术公司 | System and method for access authentication in a mobile wireless network |
WO2007103923A2 (en) | 2006-03-06 | 2007-09-13 | La La Media, Inc | Article trading process |
US7715562B2 (en) * | 2006-03-06 | 2010-05-11 | Cisco Technology, Inc. | System and method for access authentication in a mobile wireless network |
US7676628B1 (en) | 2006-03-31 | 2010-03-09 | Emc Corporation | Methods, systems, and computer program products for providing access to shared storage by computing grids and clusters with large numbers of nodes |
CN100495981C (en) * | 2006-04-28 | 2009-06-03 | 华为技术有限公司 | Method for negotiating quality of service |
US20070258459A1 (en) * | 2006-05-02 | 2007-11-08 | Harris Corporation | Method and system for QOS by proxy |
US7756134B2 (en) | 2006-05-02 | 2010-07-13 | Harris Corporation | Systems and methods for close queuing to support quality of service |
US7894509B2 (en) * | 2006-05-18 | 2011-02-22 | Harris Corporation | Method and system for functional redundancy based quality of service |
US20070291767A1 (en) * | 2006-06-16 | 2007-12-20 | Harris Corporation | Systems and methods for a protocol transformation gateway for quality of service |
US8064464B2 (en) * | 2006-06-16 | 2011-11-22 | Harris Corporation | Method and system for inbound content-based QoS |
US7990860B2 (en) | 2006-06-16 | 2011-08-02 | Harris Corporation | Method and system for rule-based sequencing for QoS |
US8516153B2 (en) * | 2006-06-16 | 2013-08-20 | Harris Corporation | Method and system for network-independent QoS |
US7856012B2 (en) | 2006-06-16 | 2010-12-21 | Harris Corporation | System and methods for generic data transparent rules to support quality of service |
US20070291768A1 (en) * | 2006-06-16 | 2007-12-20 | Harris Corporation | Method and system for content-based differentiation and sequencing as a mechanism of prioritization for QOS |
US7916626B2 (en) | 2006-06-19 | 2011-03-29 | Harris Corporation | Method and system for fault-tolerant quality of service |
US20070291765A1 (en) * | 2006-06-20 | 2007-12-20 | Harris Corporation | Systems and methods for dynamic mode-driven link management |
US8730981B2 (en) * | 2006-06-20 | 2014-05-20 | Harris Corporation | Method and system for compression based quality of service |
US7769028B2 (en) | 2006-06-21 | 2010-08-03 | Harris Corporation | Systems and methods for adaptive throughput management for event-driven message-based data |
US8473566B1 (en) * | 2006-06-30 | 2013-06-25 | Emc Corporation | Methods systems, and computer program products for managing quality-of-service associated with storage shared by computing grids and clusters with a plurality of nodes |
US20080013559A1 (en) * | 2006-07-14 | 2008-01-17 | Smith Donald L | Systems and methods for applying back-pressure for sequencing in quality of service |
US20080025318A1 (en) * | 2006-07-31 | 2008-01-31 | Harris Corporation | Systems and methods for dynamically customizable quality of service on the edge of a network |
US20100238801A1 (en) * | 2006-07-31 | 2010-09-23 | Smith Donald L | Method and system for stale data detection based quality of service |
US20100241759A1 (en) * | 2006-07-31 | 2010-09-23 | Smith Donald L | Systems and methods for sar-capable quality of service |
US8300653B2 (en) * | 2006-07-31 | 2012-10-30 | Harris Corporation | Systems and methods for assured communications with quality of service |
US20080049648A1 (en) * | 2006-08-28 | 2008-02-28 | Motorola, Inc. | Method and apparatus for policy management for an internet protocol multimedia subsystem based wireless communication system |
US20080082670A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Resilient communications between clients comprising a cloud |
US8503453B2 (en) * | 2006-11-20 | 2013-08-06 | Cisco Technology, Inc. | Adaptive quality of service in an easy virtual private network environment |
JP4996929B2 (en) | 2007-01-17 | 2012-08-08 | 株式会社日立製作所 | Virtual computer system |
GB2449954A (en) * | 2007-01-23 | 2008-12-10 | Symbian Software Ltd | Mobility in a Protocol Stack |
JP4479761B2 (en) * | 2007-08-07 | 2010-06-09 | セイコーエプソン株式会社 | Conference system, connection method |
US9313108B2 (en) * | 2007-12-14 | 2016-04-12 | Ericsson Ab | Flexible and scalable method and apparatus for dynamic subscriber services configuration and management |
US7852849B2 (en) * | 2008-03-04 | 2010-12-14 | Bridgewater Systems Corp. | Providing dynamic quality of service for virtual private networks |
US8612572B2 (en) * | 2008-05-30 | 2013-12-17 | Microsoft Corporation | Rule-based system for client-side quality-of-service tracking and reporting |
US8902821B2 (en) * | 2008-06-12 | 2014-12-02 | Motorola Mobility Llc | Method and system for intermediate node quality of service negotiations |
US7996526B2 (en) | 2009-06-08 | 2011-08-09 | Comcast Cable Communications, Llc | Management of shared access network |
US8996659B2 (en) * | 2009-07-24 | 2015-03-31 | Plumchoice, Inc. | Systems and methods for providing remote services using a cross-device database |
US8213337B2 (en) * | 2009-09-23 | 2012-07-03 | Via Telecom, Inc. | IP multimedia subsystem for a multimode wireless device |
US8972551B1 (en) * | 2010-04-27 | 2015-03-03 | Amazon Technologies, Inc. | Prioritizing service requests |
EP2493139A1 (en) * | 2011-02-22 | 2012-08-29 | Voipfuture GmbH | VoIP quality measurement enhancements using the internet control message protocol |
CN102204209B (en) * | 2011-05-06 | 2014-01-22 | 华为技术有限公司 | Method, system and network device for quality of service (qos) negotiation in cross-medium networks |
US9167480B2 (en) * | 2011-05-17 | 2015-10-20 | At&T Intellectual Property I, L.P. | Methods and systems for managing device bandwidth usage |
US8972537B2 (en) * | 2011-08-16 | 2015-03-03 | Comcast Cable Communications, Llc | Prioritizing local and network traffic |
US8908531B2 (en) * | 2011-08-25 | 2014-12-09 | At&T Mobility Ii Llc | Communication gateway for facilitating communications with a supervisory control and data aquisition system |
CN102984189B (en) * | 2011-09-07 | 2017-04-19 | 华为技术有限公司 | Wireless network and implementation method and terminal thereof |
US9179381B2 (en) | 2011-09-29 | 2015-11-03 | Qualcomm Incorporated | Reducing network-initiated QoS interruption time when radio and core networks are out of synchronization due to different underlying technologies |
US8983905B2 (en) | 2011-10-03 | 2015-03-17 | Apple Inc. | Merging playlists from multiple sources |
US9961021B2 (en) | 2012-04-19 | 2018-05-01 | Cisco Technology, Inc. | Enabling applications in a multi-transport stack environment |
US20140156339A1 (en) * | 2012-12-03 | 2014-06-05 | Bank Of America Corporation | Operational risk and control analysis of an organization |
US9602398B2 (en) | 2013-09-15 | 2017-03-21 | Nicira, Inc. | Dynamically generating flows with wildcard fields |
US9674087B2 (en) | 2013-09-15 | 2017-06-06 | Nicira, Inc. | Performing a multi-stage lookup to classify packets |
US9569368B2 (en) | 2013-12-13 | 2017-02-14 | Nicira, Inc. | Installing and managing flows in a flow table cache |
US9996467B2 (en) * | 2013-12-13 | 2018-06-12 | Nicira, Inc. | Dynamically adjusting the number of flows allowed in a flow table cache |
US9686200B2 (en) | 2014-03-31 | 2017-06-20 | Nicira, Inc. | Flow cache hierarchy |
US11178051B2 (en) | 2014-09-30 | 2021-11-16 | Vmware, Inc. | Packet key parser for flow-based forwarding elements |
US9900725B2 (en) | 2015-07-29 | 2018-02-20 | Intel Corporation | Technologies for an automated application exchange in wireless networks |
US10021589B2 (en) | 2016-01-26 | 2018-07-10 | Sprint Communications Company L.P. | Wireless data system that associates internet protocol ports with quality-of-service for user applications |
US10621125B2 (en) * | 2016-06-28 | 2020-04-14 | Nec Corporation | Identifier-based packet request processing |
CN107203392B (en) * | 2017-04-01 | 2020-07-14 | 宁波三星医疗电气股份有限公司 | Multi-protocol implementation method of small system terminal product |
US10674409B2 (en) | 2017-06-09 | 2020-06-02 | At&T Intellectual Property I, L.P. | System and method for fine grained service management using SDN-NFV networks |
US10608944B2 (en) | 2018-04-27 | 2020-03-31 | Teridion Technologies Ltd | Device selection for providing an end-to-end network connection |
US11496601B2 (en) * | 2021-01-13 | 2022-11-08 | Dell Products, L.P. | Client driven cloud network access system and method |
Citations (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US15583A (en) * | 1856-08-19 | thickins | ||
US15590A (en) * | 1856-08-19 | breckenridge | ||
US32265A (en) * | 1861-05-07 | Andrew mouse | ||
US95504A (en) * | 1869-10-05 | Together the different parts of bureaus | ||
US101263A (en) * | 1870-03-29 | Improvement in the manufacture op iron and steel | ||
US170178A (en) * | 1875-11-23 | Improvement in dental polishing-tools | ||
US5530698A (en) * | 1993-08-25 | 1996-06-25 | Hitachi, Ltd. | ATM switching system and cell control method |
US5539884A (en) * | 1993-05-20 | 1996-07-23 | Bell Communications Research, Inc. | Intelligent broadband communication system and method employing fast-packet switches |
US5548726A (en) * | 1993-12-17 | 1996-08-20 | Taligeni, Inc. | System for activating new service in client server network by reconfiguring the multilayer network protocol stack dynamically within the server node |
US5581544A (en) * | 1993-12-24 | 1996-12-03 | Fujitsu Limited | Method and apparatus for evaluating QOS in ATM multiplexing apparatus in which priority control is performed and for controlling call admissions and optimizing priority control on the basis of the evaluation |
US5742772A (en) * | 1995-11-17 | 1998-04-21 | Lucent Technologies Inc. | Resource management system for a broadband multipoint bridge |
US5751698A (en) * | 1996-03-15 | 1998-05-12 | Network General Technology Corporation | System and method for automatically identifying and analyzing active channels in an ATM network |
US5774656A (en) * | 1994-05-06 | 1998-06-30 | Hitachi, Ltd. | Information processing system and method and service supplying method for use within a network |
US5944795A (en) * | 1996-07-12 | 1999-08-31 | At&T Corp. | Client-server architecture using internet and guaranteed quality of service networks for accessing distributed media sources |
US5982748A (en) * | 1996-10-03 | 1999-11-09 | Nortel Networks Corporation | Method and apparatus for controlling admission of connection requests |
US5999532A (en) * | 1996-08-13 | 1999-12-07 | Nec Corporation | ATM line concentration apparatus |
US6021263A (en) * | 1996-02-16 | 2000-02-01 | Lucent Technologies, Inc. | Management of ATM virtual circuits with resources reservation protocol |
US6046981A (en) * | 1997-02-28 | 2000-04-04 | Nec Usa, Inc. | Multi-class connection admission control method for Asynchronous Transfer Mode (ATM) switches |
US6055239A (en) * | 1997-03-18 | 2000-04-25 | Fujitsu Limited | Control method for establishing a permanent virtual connection in an ATM network |
US6078953A (en) * | 1997-12-29 | 2000-06-20 | Ukiah Software, Inc. | System and method for monitoring quality of service over network |
US6081845A (en) * | 1997-03-18 | 2000-06-27 | Fujitsu Limited | ARP server |
US6105068A (en) * | 1998-02-10 | 2000-08-15 | 3Com Corporation | Method and apparatus for determining a protocol type on a network connection using error detection values stored within internetworking devices |
US6128649A (en) * | 1997-06-02 | 2000-10-03 | Nortel Networks Limited | Dynamic selection of media streams for display |
US6154778A (en) * | 1998-05-19 | 2000-11-28 | Hewlett-Packard Company | Utility-based multi-category quality-of-service negotiation in distributed systems |
US6167445A (en) * | 1998-10-26 | 2000-12-26 | Cisco Technology, Inc. | Method and apparatus for defining and implementing high-level quality of service policies in computer networks |
US6189033B1 (en) * | 1998-07-16 | 2001-02-13 | Hewlett-Packard Company | Method and system for providing performance guarantees for a data service system of a data access network system |
US6195697B1 (en) * | 1999-06-02 | 2001-02-27 | Ac Properties B.V. | System, method and article of manufacture for providing a customer interface in a hybrid network |
US6212163B1 (en) * | 1996-06-18 | 2001-04-03 | Nippon Telegraph And Telephone Corporation | Method and device for multi-class ATM connection admission control |
US6240462B1 (en) * | 1997-10-14 | 2001-05-29 | At&T | System for providing enhanced grade of service for connections over a large network |
US6286052B1 (en) * | 1998-12-04 | 2001-09-04 | Cisco Technology, Inc. | Method and apparatus for identifying network data traffic flows and for applying quality of service treatments to the flows |
US6366577B1 (en) * | 1999-11-05 | 2002-04-02 | Mci Worldcom, Inc. | Method for providing IP telephony with QoS using end-to-end RSVP signaling |
US6400722B1 (en) * | 1997-10-14 | 2002-06-04 | Lucent Technologies Inc. | Optimum routing system |
US6405251B1 (en) * | 1999-03-25 | 2002-06-11 | Nortel Networks Limited | Enhancement of network accounting records |
US6487168B1 (en) * | 1999-05-27 | 2002-11-26 | 3Com Corporation | Static switched virtual circuits in a connection oriented network |
US6516350B1 (en) * | 1999-06-17 | 2003-02-04 | International Business Machines Corporation | Self-regulated resource management of distributed computer resources |
US6529950B1 (en) * | 1999-06-17 | 2003-03-04 | International Business Machines Corporation | Policy-based multivariate application-level QoS negotiation for multimedia services |
US6594699B1 (en) * | 1997-10-10 | 2003-07-15 | Kasenna, Inc. | System for capability based multimedia streaming over a network |
US6597689B1 (en) * | 1998-12-30 | 2003-07-22 | Nortel Networks Limited | SVC signaling system and method |
US6598080B1 (en) * | 1994-08-31 | 2003-07-22 | Kabushiki Kaisha Toshiba | Network interconnection apparatus network node apparatus and packet transfer method for high speed large capacity inter-network communication |
US6631122B1 (en) * | 1999-06-11 | 2003-10-07 | Nortel Networks Limited | Method and system for wireless QOS agent for all-IP network |
US6691148B1 (en) * | 1998-03-13 | 2004-02-10 | Verizon Corporate Services Group Inc. | Framework for providing quality of service requirements in a distributed object-oriented computer system |
US6700890B1 (en) * | 1997-12-22 | 2004-03-02 | Cisco Technology, Inc. | Method and apparatus for configuring permanent virtual connection (PVC) information stored on network devices in an ATM network logically configured with subnetworks |
US6707820B1 (en) * | 1999-12-16 | 2004-03-16 | Intervoice Limited Partnership | Virtual circuit network dynamic channel management |
US6708034B1 (en) * | 1999-09-13 | 2004-03-16 | Nortel Networks Ltd. | End-to-end quality of service guarantee in a wireless environment |
US6728365B1 (en) * | 1999-09-13 | 2004-04-27 | Nortel Networks Limited | Method and system for providing quality-of-service on packet-based wireless connections |
US6781996B1 (en) * | 1998-04-16 | 2004-08-24 | Samsung Electronics Co., Ltd. | System and method in an ATM switch for dynamically routing data cells using quality of service data |
US6788696B2 (en) * | 2000-03-10 | 2004-09-07 | Nortel Networks Limited | Transparent QoS using VC-merge capable access modules |
US6822963B1 (en) * | 1997-10-22 | 2004-11-23 | Telia Ab | Telecommunications |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB9501378D0 (en) * | 1995-01-24 | 1995-03-15 | Ibm | A system and method for establishing a communication channel over a heterogeneous network between a source node and a destination node |
DE69636158T2 (en) * | 1996-01-29 | 2006-09-28 | Agilent Technologies, Inc. (n.d.Ges.d.Staates Delaware), Palo Alto | A method and arrangement for performing quality of service measurements on a connection over a network |
US6108304A (en) * | 1996-03-08 | 2000-08-22 | Abe; Hajime | Packet switching network, packet switching equipment, and network management equipment |
US6304549B1 (en) * | 1996-09-12 | 2001-10-16 | Lucent Technologies Inc. | Virtual path management in hierarchical ATM networks |
US6134589A (en) * | 1997-06-16 | 2000-10-17 | Telefonaktiebolaget Lm Ericsson | Dynamic quality control network routing |
US6188671B1 (en) * | 1997-07-03 | 2001-02-13 | At&T Corp | Traffic management for frame relay switched data service |
JP3075248B2 (en) * | 1998-01-19 | 2000-08-14 | 日本電気株式会社 | Asynchronous transfer mode switch |
CA2229577A1 (en) * | 1998-02-12 | 1999-08-12 | Newbridge Networks Corporation | Method and apparatus for controlling traffic flows in a packet-switched network in order to guarantee service performance |
US6363053B1 (en) * | 1999-02-08 | 2002-03-26 | 3Com Corporation | Method and apparatus for measurement-based conformance testing of service level agreements in networks |
US6608814B1 (en) * | 1999-03-12 | 2003-08-19 | Lucent Technologies Inc. | Session resource manager and method for enhancing visibility and control of a broadband network |
US7668956B2 (en) * | 1999-10-19 | 2010-02-23 | Netzero, Inc. | Intelligent autodialer |
US6954739B1 (en) * | 1999-11-16 | 2005-10-11 | Lucent Technologies Inc. | Measurement-based management method for packet communication networks |
US7320034B2 (en) * | 2000-03-20 | 2008-01-15 | International Business Machines Corporation | System and method for reserving a virtual connection in an IP network |
JP2001298481A (en) * | 2000-04-13 | 2001-10-26 | Nec Corp | Communication control method, communication controller and recording medium |
US7519695B2 (en) * | 2000-05-26 | 2009-04-14 | Ipass Inc. | Service quality monitoring process |
EP1211842A1 (en) * | 2000-11-30 | 2002-06-05 | BRITISH TELECOMMUNICATIONS public limited company | Network management apparatus |
JP2002208941A (en) * | 2001-01-12 | 2002-07-26 | Nec Corp | Pvc switching control method for atm network |
-
2000
- 2000-11-08 WO PCT/US2000/042007 patent/WO2001035243A1/en active Application Filing
- 2000-11-08 AU AU27522/01A patent/AU2752201A/en not_active Abandoned
-
2001
- 2001-04-25 US US09/841,972 patent/US7185070B2/en not_active Expired - Lifetime
- 2001-05-01 US US09/847,039 patent/US7293094B2/en not_active Expired - Lifetime
-
2006
- 2006-05-08 US US11/382,221 patent/US20060195581A1/en not_active Abandoned
-
2007
- 2007-02-08 US US11/672,713 patent/US20070180073A1/en not_active Abandoned
Patent Citations (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US15583A (en) * | 1856-08-19 | thickins | ||
US15590A (en) * | 1856-08-19 | breckenridge | ||
US32265A (en) * | 1861-05-07 | Andrew mouse | ||
US95504A (en) * | 1869-10-05 | Together the different parts of bureaus | ||
US101263A (en) * | 1870-03-29 | Improvement in the manufacture op iron and steel | ||
US170178A (en) * | 1875-11-23 | Improvement in dental polishing-tools | ||
US5539884A (en) * | 1993-05-20 | 1996-07-23 | Bell Communications Research, Inc. | Intelligent broadband communication system and method employing fast-packet switches |
US5530698A (en) * | 1993-08-25 | 1996-06-25 | Hitachi, Ltd. | ATM switching system and cell control method |
US5548726A (en) * | 1993-12-17 | 1996-08-20 | Taligeni, Inc. | System for activating new service in client server network by reconfiguring the multilayer network protocol stack dynamically within the server node |
US5581544A (en) * | 1993-12-24 | 1996-12-03 | Fujitsu Limited | Method and apparatus for evaluating QOS in ATM multiplexing apparatus in which priority control is performed and for controlling call admissions and optimizing priority control on the basis of the evaluation |
US6094674A (en) * | 1994-05-06 | 2000-07-25 | Hitachi, Ltd. | Information processing system and information processing method and quality of service supplying method for use with the system |
US5774656A (en) * | 1994-05-06 | 1998-06-30 | Hitachi, Ltd. | Information processing system and method and service supplying method for use within a network |
US6598080B1 (en) * | 1994-08-31 | 2003-07-22 | Kabushiki Kaisha Toshiba | Network interconnection apparatus network node apparatus and packet transfer method for high speed large capacity inter-network communication |
US5742772A (en) * | 1995-11-17 | 1998-04-21 | Lucent Technologies Inc. | Resource management system for a broadband multipoint bridge |
US6021263A (en) * | 1996-02-16 | 2000-02-01 | Lucent Technologies, Inc. | Management of ATM virtual circuits with resources reservation protocol |
US5751698A (en) * | 1996-03-15 | 1998-05-12 | Network General Technology Corporation | System and method for automatically identifying and analyzing active channels in an ATM network |
US6212163B1 (en) * | 1996-06-18 | 2001-04-03 | Nippon Telegraph And Telephone Corporation | Method and device for multi-class ATM connection admission control |
US5944795A (en) * | 1996-07-12 | 1999-08-31 | At&T Corp. | Client-server architecture using internet and guaranteed quality of service networks for accessing distributed media sources |
US5999532A (en) * | 1996-08-13 | 1999-12-07 | Nec Corporation | ATM line concentration apparatus |
US5982748A (en) * | 1996-10-03 | 1999-11-09 | Nortel Networks Corporation | Method and apparatus for controlling admission of connection requests |
US6046981A (en) * | 1997-02-28 | 2000-04-04 | Nec Usa, Inc. | Multi-class connection admission control method for Asynchronous Transfer Mode (ATM) switches |
US6081845A (en) * | 1997-03-18 | 2000-06-27 | Fujitsu Limited | ARP server |
US6055239A (en) * | 1997-03-18 | 2000-04-25 | Fujitsu Limited | Control method for establishing a permanent virtual connection in an ATM network |
US6128649A (en) * | 1997-06-02 | 2000-10-03 | Nortel Networks Limited | Dynamic selection of media streams for display |
US6594699B1 (en) * | 1997-10-10 | 2003-07-15 | Kasenna, Inc. | System for capability based multimedia streaming over a network |
US6400722B1 (en) * | 1997-10-14 | 2002-06-04 | Lucent Technologies Inc. | Optimum routing system |
US6240462B1 (en) * | 1997-10-14 | 2001-05-29 | At&T | System for providing enhanced grade of service for connections over a large network |
US6822963B1 (en) * | 1997-10-22 | 2004-11-23 | Telia Ab | Telecommunications |
US6714972B1 (en) * | 1997-12-22 | 2004-03-30 | Cisco Technology, Inc. | Method and apparatus for configuring network devices with subnetworks in an ATM environment and retrieving permanent virtual channel (PVC) configuration information from network devices |
US6700890B1 (en) * | 1997-12-22 | 2004-03-02 | Cisco Technology, Inc. | Method and apparatus for configuring permanent virtual connection (PVC) information stored on network devices in an ATM network logically configured with subnetworks |
US6078953A (en) * | 1997-12-29 | 2000-06-20 | Ukiah Software, Inc. | System and method for monitoring quality of service over network |
US6105068A (en) * | 1998-02-10 | 2000-08-15 | 3Com Corporation | Method and apparatus for determining a protocol type on a network connection using error detection values stored within internetworking devices |
US6691148B1 (en) * | 1998-03-13 | 2004-02-10 | Verizon Corporate Services Group Inc. | Framework for providing quality of service requirements in a distributed object-oriented computer system |
US6781996B1 (en) * | 1998-04-16 | 2004-08-24 | Samsung Electronics Co., Ltd. | System and method in an ATM switch for dynamically routing data cells using quality of service data |
US6154778A (en) * | 1998-05-19 | 2000-11-28 | Hewlett-Packard Company | Utility-based multi-category quality-of-service negotiation in distributed systems |
US6189033B1 (en) * | 1998-07-16 | 2001-02-13 | Hewlett-Packard Company | Method and system for providing performance guarantees for a data service system of a data access network system |
US6167445A (en) * | 1998-10-26 | 2000-12-26 | Cisco Technology, Inc. | Method and apparatus for defining and implementing high-level quality of service policies in computer networks |
US6286052B1 (en) * | 1998-12-04 | 2001-09-04 | Cisco Technology, Inc. | Method and apparatus for identifying network data traffic flows and for applying quality of service treatments to the flows |
US6597689B1 (en) * | 1998-12-30 | 2003-07-22 | Nortel Networks Limited | SVC signaling system and method |
US6405251B1 (en) * | 1999-03-25 | 2002-06-11 | Nortel Networks Limited | Enhancement of network accounting records |
US6487168B1 (en) * | 1999-05-27 | 2002-11-26 | 3Com Corporation | Static switched virtual circuits in a connection oriented network |
US6195697B1 (en) * | 1999-06-02 | 2001-02-27 | Ac Properties B.V. | System, method and article of manufacture for providing a customer interface in a hybrid network |
US6631122B1 (en) * | 1999-06-11 | 2003-10-07 | Nortel Networks Limited | Method and system for wireless QOS agent for all-IP network |
US6529950B1 (en) * | 1999-06-17 | 2003-03-04 | International Business Machines Corporation | Policy-based multivariate application-level QoS negotiation for multimedia services |
US6516350B1 (en) * | 1999-06-17 | 2003-02-04 | International Business Machines Corporation | Self-regulated resource management of distributed computer resources |
US6708034B1 (en) * | 1999-09-13 | 2004-03-16 | Nortel Networks Ltd. | End-to-end quality of service guarantee in a wireless environment |
US6728365B1 (en) * | 1999-09-13 | 2004-04-27 | Nortel Networks Limited | Method and system for providing quality-of-service on packet-based wireless connections |
US6366577B1 (en) * | 1999-11-05 | 2002-04-02 | Mci Worldcom, Inc. | Method for providing IP telephony with QoS using end-to-end RSVP signaling |
US6707820B1 (en) * | 1999-12-16 | 2004-03-16 | Intervoice Limited Partnership | Virtual circuit network dynamic channel management |
US6788696B2 (en) * | 2000-03-10 | 2004-09-07 | Nortel Networks Limited | Transparent QoS using VC-merge capable access modules |
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070297450A1 (en) * | 2006-06-21 | 2007-12-27 | Motorola, Inc. | Method and apparatus for passing an application description to lower layer packet data protocol |
US20080247326A1 (en) * | 2007-04-04 | 2008-10-09 | Research In Motion Limited | Method, system and apparatus for dynamic quality of service modification |
US8184637B2 (en) * | 2007-04-04 | 2012-05-22 | Research In Motion Limited | Method, system and apparatus for dynamic quality of service modification |
US20090063683A1 (en) * | 2007-08-31 | 2009-03-05 | Nokia Corporation | Information distribution in a dynamic multi-device environment |
US9417934B2 (en) | 2007-08-31 | 2016-08-16 | Core Wireless Licensing S.A.R.L. | Information distribution in a dynamic multi-device environment |
US20090100152A1 (en) * | 2007-10-11 | 2009-04-16 | At&T Knowledge Ventures, L.P. | System for selecting a network element |
US20100260067A1 (en) * | 2007-11-08 | 2010-10-14 | Nokia Corporation | Connectivity architecture for service discovery |
US8493888B2 (en) | 2007-11-08 | 2013-07-23 | Nokia Corporation | Connectivity architecture for service discovery |
US20090141692A1 (en) * | 2007-11-30 | 2009-06-04 | Mika Kasslin | Optimized ad hoc networking |
US9825863B2 (en) | 2008-02-27 | 2017-11-21 | Nokia Technologies Oy | Buffer control for multi-transport architectures |
US20110004886A1 (en) * | 2008-02-27 | 2011-01-06 | Nokia Corporation | Transport independent architecture |
US9119180B2 (en) | 2008-02-27 | 2015-08-25 | Nokia Corporation | Transport independent architecture |
US20110002344A1 (en) * | 2008-02-27 | 2011-01-06 | Nokia Corporation | Buffer control for multi-transport architectures |
US9413673B2 (en) | 2009-06-12 | 2016-08-09 | Wi-Lan Labs, Inc. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US9876726B2 (en) | 2009-06-12 | 2018-01-23 | Taiwan Semiconductor Manufacturing Co., Ltd. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US9020498B2 (en) | 2009-06-12 | 2015-04-28 | Wi-Lan Labs, Inc. | Systems and methods for intelligent discard in a communication network |
US9043853B2 (en) | 2009-06-12 | 2015-05-26 | Wi-Lan Labs, Inc. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US9112802B2 (en) | 2009-06-12 | 2015-08-18 | Wi-Lan Labs, Inc. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US20120033573A1 (en) * | 2009-06-12 | 2012-02-09 | Cygnus Broadband, Inc. | Systems and methods for intelligent discard in a communication network |
US9253108B2 (en) | 2009-06-12 | 2016-02-02 | Wi-Lan Labs, Inc. | Systems and methods for prioritization of data for intelligent discard in a communication network |
US9264372B2 (en) | 2009-06-12 | 2016-02-16 | Wi-Lan Labs, Inc. | Systems and methods for intelligent discard in a communication network |
US8320930B2 (en) * | 2009-06-12 | 2012-11-27 | Cygnus Broadband, Inc. | Systems and methods for intelligent discard in a communication network |
US20100318598A1 (en) * | 2009-06-15 | 2010-12-16 | Lg Electronics Inc. | Method for remotely controlling terminal device |
US20100318599A1 (en) * | 2009-06-15 | 2010-12-16 | Lg Electronics Inc. | Method for remotely controlling terminal device |
US9577881B2 (en) * | 2010-06-04 | 2017-02-21 | Broadcom Corporation | Method and system for managing quality of service via a broadband gateway |
US20110299410A1 (en) * | 2010-06-04 | 2011-12-08 | Wael William Diab | Method and system for managing quality of service via a broadband gateway |
US20190123965A1 (en) * | 2013-03-15 | 2019-04-25 | Sony Interactive Entertainment Inc. | Profile generation for bandwidth management |
US10985988B2 (en) * | 2013-03-15 | 2021-04-20 | Sony Interactive Entertainment Inc. | Profile generation for bandwidth management |
US11916743B2 (en) | 2013-03-15 | 2024-02-27 | Sony Interactive Entertainment Inc. | Profile generation for bandwidth management |
US9538132B2 (en) * | 2013-07-22 | 2017-01-03 | Tencent Technology (Shenzhen) Company Limited | Methods, devices, and systems for controlling audio and video transmission |
Also Published As
Publication number | Publication date |
---|---|
US20060195581A1 (en) | 2006-08-31 |
US20020091802A1 (en) | 2002-07-11 |
US7293094B2 (en) | 2007-11-06 |
US7185070B2 (en) | 2007-02-27 |
AU2752201A (en) | 2001-06-06 |
WO2001035243A1 (en) | 2001-05-17 |
US20020055990A1 (en) | 2002-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7185070B2 (en) | Generic quality of service protocol and architecture for user applications in multiple transport protocol environments | |
US7965637B1 (en) | Network proxy with asymmetric connection connectivity | |
US6888807B2 (en) | Applying session services based on packet flows | |
JP3225924B2 (en) | Communication quality control device | |
US6154776A (en) | Quality of service allocation on a network | |
US7193968B1 (en) | Sample netflow for network traffic data collection | |
EP1926245B1 (en) | Method and system for obtaining ssh host key of managed device | |
US6662223B1 (en) | Protocol to coordinate network end points to measure network latency | |
US6456603B1 (en) | Method of supporting communications mobility in a telecommunications system | |
US20160006695A1 (en) | Secure Remote Computer Network | |
US20030079144A1 (en) | Service control network, server, network device, service information distribution method, and service information distribution program | |
WO1997028505A9 (en) | Improved method and apparatus for dynamically shifting between routing and switching packets in a transmission network | |
WO1997028505A1 (en) | Improved method and apparatus for dynamically shifting between routing and switching packets in a transmission network | |
JPH08204778A (en) | Compression of tcp/ip header in x.25 network | |
US7561587B2 (en) | Method and system for providing layer-4 switching technologies | |
US20050165885A1 (en) | Method and apparatus for forwarding data packets addressed to a cluster servers | |
US20070121833A1 (en) | Method of Quick-Redial for Broadband Network Users and System Thereof | |
WO2021135419A1 (en) | Method and apparatus for updating routing information, computer device, and storage medium | |
US20200322418A1 (en) | Secure remote computer network | |
JP2001168915A (en) | Ip packet transfer system | |
CN112910704B (en) | Local area network system, method and device supporting dynamic self-adaptive network configuration | |
JP4465497B2 (en) | Dynamic modification of subscriber connections | |
EP3414877A1 (en) | Technique for transport protocol selection and setup of a connection between a client and a server | |
KR100506182B1 (en) | A vpn system supporting a multitunnel ipsec and operation method thereof | |
JP2001358771A (en) | Device for controlling communication quality |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: BOYLE PHOSPHORUS LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CHERYL E. ROSE, CHAPTER 7 TRUSTEE FOR THE ESTATE OF MEGAXESS, INC.;REEL/FRAME:025602/0168 Effective date: 20041026 Owner name: MEGAXESS, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VAMAN, DHADESUGOOR R.;BYUN, JOONBUM;KIM, DONGSOO S.;REEL/FRAME:025602/0066 Effective date: 19991112 |
|
AS | Assignment |
Owner name: INTELLECTUAL VENTURES I LLC, DELAWARE Free format text: MERGER;ASSIGNOR:BOYLE PHOSPHORUS LLC;REEL/FRAME:027684/0292 Effective date: 20120206 |