| Platform SDK: Quality of Service |
In order for the RSVP SP to act on behalf of an application, the RSVP SP must be provided with QOS-specific parameters. These parameters come in the form of the following structures:
The QOS structure is the all-encompassing structure for QOS-specific parameters, and is comprised of three parameters, two of which are FLOWSPEC structures (one for sending, one for receiving).
The FLOWSPEC structure includes flow members, which are TokenRate, TokenBucketSize, PeakBandwidth, Latency, DelayVariation, ServiceType, MaxSduSize (maximum packet size permitted in the traffic flow), and MinimumPolicedSize. When the application provides values for these parameters, the RSVP SP can characterize the service quality being requested; this enables the RSVP SP to make appropriate requests to corresponding components of QOS.
The third parameter of the QOS structure is the ProviderSpecific buffer, which is used for additional provider-specific QOS parameters that cannot be specified in the FLOWSPEC structures. For more information about the ProviderSpecific buffer, see Using the ProviderSpecific Buffer.
QOS parameters for the FLOWSPEC structure may be common among certain application types. This commonality lends itself to the establishment of standardized QOS parameters for a given type of transmission. The RSVP SP provides such standardization, and the ease of implementation that comes with prescribed service types, through the use of QOS templates. These templates are described in detail in the QOS Templates section.
Further details of the QOS structureand the FLOWSPEC structure can be found in their respective API entries.