Integrated services
architecture of quality of service of computer networking
In computer networking, integrated services or IntServ is an architecture that specifies the elements to guarantee quality of service (QoS) on networks. IntServ can for example be used to allow video and sound to reach the receiver without interruption.
IntServ specifies a fine-grained QoS system, which is often contrasted with DiffServ's coarse-grained control system.
Under IntServ, every router in the system implements IntServ, and every application that requires some kind of QoS guarantee has to make an individual reservation. Flow specs describe what the reservation is for, while RSVP is the underlying mechanism to signal it across the network.
Flow specs
There are two parts to a flow spec:
What does the traffic look like? Done in the Traffic SPECification part, also known as TSPEC.
What guarantees does it need? Done in the service Request Specification part, also known as RSpec.
TSPECs include token bucket algorithm parameters. The idea is that there is a token bucket which slowly fills up with tokens, arriving at a constant rate.
“Integrated services” enters the record as architecture of quality of service of computer networking. Crown Archives preserves that source wording while asking what Integrated, services and architecture can confirm, complicate or overturn.
Why this record matters
“Integrated services” is worth following because a concise public description often conceals a longer documentary argument. Here, Integrated, services and architecture provides the most credible route into that argument.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Aug 4, 2025. The linked authority identifier is Q1665345. None of the 0 selected statements returned an explicit reference.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Integrated services”, its source revision and the description used here.
- Expand the search: follow Integrated services primary sources, Integrated services archive and Integrated research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Integrated services”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Integrated services” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.