Browse Prior Art Database

Generic Rule Engine for Ethernet based Application and Service

IP.com Disclosure Number: IPCOM000033832D
Original Publication Date: 2005-Jan-25
Included in the Prior Art Database: 2005-Jan-25

Publishing Venue

Siemens

Related People

Other Related People:

Abstract

In telecommunication networks, most of the Ethernet based access products have only limited feature sets which assure a certain Quality of Service (QoS). For this reason, the access area very often is a bottleneck of the whole network. Till now it has been difficult or expensive to reduce the problem for all existing Ethernet based access products. To solve the problem, a so called Generic Rule Engine for Ethernet based Applications and Services (GREASe) can be utilized. This generic rule engine is a software (SW) module which comprises an algorithm deciding about the hardware (HW) components configuration settings. The GREASe provides all possible application bundles and service bundles including a reusable management interface, a Message Sequence Chart (MSC) catalogue, SNMP (Simple Network Management Protocol) and MIB (Management Information Base). Due to the hardware adaptation layer and the operating system (OS) adaptation layer, this software-package is HW- or OS-independent. How to utilize an embodiment of the GREASe in combination with a DSLAM (Digital Subscriber Line Access Multiplexer) is shown exemplary in Figure 1 and Figure 2. For example, a subscriber A applies for 64Kbit/s VoIP (Voice over IP, Internet Protocol), 20Mbit/s fast internet access and gaming discarding service. To meet this requirement, the rule engine can be integrated in an access product for configuration of the HW-switching components to support the required services. In the example, three applications and service bindings have to be configured - one for VoIP, one for fast internet and one for gaming. The SNMP interface receives a SNMP message from the SNMP agent and calls the Generic Rule Engine to translate these bindings into rules and to configure then the switching HW via the HW adaptation layer.