Browse Prior Art Database

Redefine Priority Bits to reflect the Service Level

IP.com Disclosure Number: IPCOM000033835D
Published in the IP.com Journal: Volume 5 Issue 1 (2005-01-25)
Included in the Prior Art Database: 2005-Jan-25
Document File: 1 page(s) / 71K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

In a telecommunication network (cf. Fig. 1) a provider can offer different service levels to a subscriber. According to the IEEE802.1p specification (IEEE: Institute of Electrical and Electronic Engineers), the priority information of a service (CoS: Class of Service) can be carried in a frame, so that a service with a higher priority than another service is carried out first (cf. Fig. 2). The assignment of a priority bit pattern to a certain priority level is not defined in the standard IEEE 802.1p. So, this assignment needs to get configured in every network node by the network management system. However, it is well known, which services in a telecommunication network (e.g. Voice over IP or video services) have to get which priority level. Though to guarantee the right Quality of Service (QoS) for a certain service is just a matter of jitter, reliability and latency, which can be predefined for a whole network. For this reason it is proposed to redefine the priority bits of IEEE802.1p in a way that allows carrying more than only priority information. An embodiment of this redefinition is showed in Fig. 3. The former "Priority Bits" are renamed, e.g., as "Service Level Bits" and contain information about priority, jitter, latency and reliability of a service.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 59% of the total text.

Page 1 of 1

S

Redefine Priority Bits to reflect the Service Level

Idea: Ligang Tian, CN-Beijing; Dr. Walter Kopetzky, DE-Munich

In a telecommunication network (cf. Fig. 1) a provider can offer different service levels to a subscriber. According to the IEEE802.1p specification (IEEE: Institute of Electrical and Electronic Engineers), the priority information of a service (CoS: Class of Service) can be carried in a frame, so that a service with a higher priority than another service is carried out first (cf. Fig. 2). The assignment of a priority bit pattern to a certain priority level is not defined in the standard IEEE 802.1p. So, this assignment needs to get configured in every network node by the network management system. However, it is well known, which services in a telecommunication network (e.g. Voice over IP or video services) have to get which priority level. Though to guarantee the right Quality of Service (QoS) for a certain service is just a matter of jitter, reliability and latency, which can be predefined for a whole network.

For this reason it is proposed to redefine the priority bits of IEEE802.1p in a way that allows carrying more than only priority information. An embodiment of this redefinition is showed in Fig. 3. The former "Priority Bits" are renamed, e.g., as "Service Level Bits" and contain information about priority, jitter, latency and reliability of a service.

So, for example, when a Service Level Bit aware equipment receives a frame whose Service L...