Topic
Differentiated service
About: Differentiated service is a research topic. Over the lifetime, 5539 publications have been published within this topic receiving 105225 citations.
Papers published on a yearly basis
Papers
More filters
••
21 Sep 2009TL;DR: This paper proposes an approach to create heavyweight service variants centered on a Service Kernel, which forms a common service core across tenants and provides improved governance for the provider while offering maximum flexibility for the consumers.
Abstract: Web-business platforms offer business capabilities as enterprise services hosted in a multi-tenant cloud environment. Often there is a need to create heavyweight variants of these enterprise services to support: inherent variability in the underlying business process, industry-specific requirements, globalization concerns and customer-specific requirements. These variability concerns affect both the service interface and the service provider implementation and hence are crosscutting in nature. In this paper, we use principles of aspect-oriented software development to modularize these variability concerns. We also provide an aspect specification scheme to specify these concerns. We propose an approach to create heavyweight service variants centered on a Service Kernel, which forms a common service core across tenants. Heavyweight service variants are created by weaving aspects into the service kernel. Our approach provides improved governance for the provider while offering maximum flexibility for the consumers.
28 citations
•
TL;DR: This paper summerize and present the latest development in the area of IP QoS, which is very important to the success of the Internet.
Abstract: Providing QoS in IP networks, which is very important to the success of the Internet, is becoming a key problem of the IP technology. In this paper, we summerize and present the latest development in the area of IP QoS.
28 citations
••
24 Apr 2006TL;DR: The relationship between contexts/situations and services in situation-aware service-based systems is identified and an extension of OWL-L with situation ontology, called SAW-OWL-S, incorporates SAW in service specifications is presented.
Abstract: Service-oriented architecture has the major advantage of enabling rapid composition of distributed applications from various services, and has become increasingly popular for many large-scale service-based systems in various application areas, including scientific collaboration, e-business, health care, military, and homeland security. Situation awareness (SAW) is the capability of the entities in a service-based system to be aware of the situation changes and automatically adapt themselves to such changes to satisfy user requirements, including security and privacy. The continuing evolutions of the entities and environment makes SAW one of the most desired features to support dynamic adaptive computing in service-based systems. In this paper, the relationship between contexts/situations and services in situation-aware service-based systems is identified and an extension of OWL-S with situation ontology, called SAW-OWL-S, incorporates SAW in service specifications is presented. An approach to generating service specifications for situation-aware service-based systems using SAW-OWL-S and the system diagram of situation-aware service-based systems using SAW-OWL-S are presented.
28 citations
•
13 Jul 2001
TL;DR: In this article, a cross-domain service provisioning system is proposed to automate the provisioning of services and their associated quality across the multiple networking technologies in a system of data, voice, application and video services.
Abstract: In a system of data, voice, application and video services that depend on multiple, interconnected network technologies, a management system suited for a particular networking technology manages each separate technology domain. A higher-level cross-domain system performs the task of automated service provisioning including (i) interacting with the services providers and consumers to determine the services being contracted for (130); (ii) collecting data from the multiple management systems (120); and (iii) sending instruction (140) to the multiple management systems (112, 114, 116) in order to provision the required service and the associated quality across the multiple networking technologies. The individual management systems (112, 114, 116) of the invention collect service data from their respective technology domains (110) and provide it to a service collection function. This data is then utilized by the service determination function to determine what service instruction should be sent from a service instruction function to the management systems for implementation in their respective technology domains.
28 citations
••
24 Sep 2007TL;DR: The response time of the AF class is analysed under a worst case scenario and an expression for its mean value is obtained using a queueing model, and implications on service level agreements are discussed.
Abstract: Strict priority queueing and weighted round robin are two common scheduling schemes for differentiation of services in telecommunication networks. A combination of these is the priority weighted round robin (PWRR) scheme, which serves three classes of traffic with distinct quality requirements, namely expedited forwarding (EF), assured forwarding (AF) and best effort forwarding (BF). The response time of the AF class is analysed under a worst case scenario and an expression for its mean value is obtained using a queueing model. Numerical results are validated by simulation and implications on service level agreements are discussed.
28 citations