Browse Prior Art Database

Application of system level quality of service in response to business criteria

IP.com Disclosure Number: IPCOM000201643D
Publication Date: 2010-Nov-17
Document File: 2 page(s) / 64K

Publishing Venue

The IP.com Prior Art Database

Abstract

Traditional quality of service (QoS) is expressed at the level of the individual event or quantum of data, usually be the entity that generates the data. For example in message oriented middleware (MOM) a message is sent with QoS of "Persistent", and the decision is made by the sender of the message. In the traditional postal service the Sender of a letter chooses to send it as 1st Class or 2nd Class and in email systems the sender of an email decides whether the email is Urgent, Confidential or Encrypted. Similarly a passenger booking a flight chooses whether to fly standard class, business or first class. While this approach is able to satisfy a number of scenarios it has a number of key weaknesses. Such QoS policies are unable to take into account the wider context in which the data exists, for example at points of data storage or changes in the usage pattern of the application for which the data is intended. Furthermore it is common for the Sender to nominate a higher QoS than might strictly be necessary as a result of the limited view that they have of the system, such as sending an MOM Message with the strongest persistence setting and setting it to never expire. The system describes here demonstrates an approach to QoS that acknowledges the wider technical and business context of the system.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 01 of 2

Application of system level quality of service in response to business criteria

This system described here provides added flexibility in quality of service options by describing the concept of applying a separate QoS policy that acts across a system or set of data items to apply a set of business level constraints (hereafter called 'business/system policy' or BSP) which may override the QoS of an individual quantum of data for the greater benefit of the system as a whole.

    There are various real world scenarios in which this kind of BSP concept is applied;

A passenger buys a ticket to fly on an airplane at a particular time, and they assume that they have a confirmed seat, but airlines routinely take more bookings than there are seats because a percentage of people never turn up. If more people turn up than there are seats then the QoS for a number of bookings is modified either by moving to a later flight, upgrading the passenger to business class, downgrading a business class passenger to standard class etc
Car drivers express an implicit QoS that says that they should be able to see out the front windscreen at all times in order to drive properly. That QoS is overridden in the event of a crash being detected as the air bag is inflated which obscures the driver's view
If a company takes orders from a customer and then goes into bankruptcy then any orders they accepted are no longer valid - even though they may have been sent as "persistent"

In traffic management systems the rotation of traffic lights is determined by the total set of vehicles at particular junctions, and not the QoS (eg leather interior, cd player etc) of an individual vehicle
The postal service uses a van to deliver vehicles from point A to point B - if there are more letters waiting than can be carried by the van then it is likely that some of them will be left behind, potentially resulting in a break of the original delivery time target QoS for the individual letters. Similarly if there is room in the van some 2nd class letters may be loaded in, even though doing so could result in the letter getting there faster than expected (upgrade in QoS)

Employees of a company are required to swipe their security badge as they enter or leave buildings in order to log employees movements and guarantee access to only those people who are permitted. Tailgating on entry to buildings is not permitted. However these security controls are overridden in the event of a fire alarm, where it is more important to allow all people contained in the building to exit quickly than require them to individually swipe their cards while exiting the building

    A BSP gives the ability to define the behaviour under conditions like the following;

Is it permitted to provide a graceful degredation of behaviour if the system is under heavy load? (by reducing or modifying the QoS of individual items)

What form should that degredation take?

What action do you want to take if the system is about to crash?...