Browse Prior Art Database

Automatic determination of possible service end/demarcation point upon subnetwork connection creation

IP.com Disclosure Number: IPCOM000132012D
Published in the IP.com Journal: Volume 5 Issue 12A (2005-12-25)
Included in the Prior Art Database: 2005-Dec-25
Document File: 4 page(s) / 565K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

Different network technologies are used for different tasks since no technology can fit all cases. Therefore the interworking between networks has to be assured (see Fig. 1). To this end, the network nodes at the boundary between (different technology) networks have to be identified. These nodes are also called demarcation points. Usually the number of possible end/demarcation points is finite and operators can use a Telecommunication Management Network (TMN) application which enables them to establish a connection between different network technologies. At present, if the operator uses a graphical managing application, he has to select both the starting and the end points (i.e. the node, slot, port) of the subnetwork connection. Depending on the network topology and the subnetwork connection type to be created, possibly only few demarcation points have connectivity with the chosen start point. In addition, possibly only a subset of those connectable end points represents acceptable paths according to the service characteristics to be created (i.e. bandwidth, QoS - Quality of Service, protection, etc.). Operators often select the boundary points (e.g. nodes, ports) from a graphical topology map by dragging and dropping them to the network connection wizard. Although drag and drop is intuitive, it might take time and is also error-prone since not connectable end points or a non optimized connection may be selected. This means that the provisioning of network connections is not optimized, since it could be faster, more user friendly, and less error-prone.

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 45% of the total text.

Page 1 of 4

S

Automatic determination of possible service end/demarcation point upon subnetwork connection creation

Idea: Jorge Veiga, PT-Alfragide

Different network technologies are used for different tasks since no technology can fit all cases. Therefore the interworking between networks has to be assured (see Fig. 1). To this end, the network nodes at the boundary between (different technology) networks have to be identified. These nodes are also called demarcation points. Usually the number of possible end/demarcation points is finite and operators can use a Telecommunication Management Network (TMN) application which enables them to establish a connection between different network technologies.

At present, if the operator uses a graphical managing application, he has to select both the starting and the end points (i.e. the node, slot, port) of the subnetwork connection. Depending on the network topology and the subnetwork connection type to be created, possibly only few demarcation points have connectivity with the chosen start point. In addition, possibly only a subset of those connectable end points represents acceptable paths according to the service characteristics to be created (i.e. bandwidth, QoS - Quality of Service, protection, etc.).

Operators often select the boundary points (e.g. nodes, ports) from a graphical topology map by dragging and dropping them to the network connection wizard. Although drag and drop is intuitive, it might take time and is also error-prone since not connectable end points or a non optimized connection may be selected. This means that the provisioning of network connections is not optimized, since it could be faster, more user friendly, and less error-prone.

The suggested solution is to give the operator a list for selection with connectable nodes (or even the slots and ports) only according to the topology and connection type. These nodes (e.g. BRAS - Broadband Remote Access Server, MPLS LERs - Multi Protocol Label Switching Label Edge Routers, VGWs - Voice Gate Ways, etc.) have to fulfill certain criteria according to topology and connection type.

An example is shown in Fig. 2. An operator using the suggested solution would automatically be given only the BRAS 1 possibility at network connection creation upon selection of an entry connection point for Customer 1. Fig. 3 shows a principal sketch of how such a list can be created. Here, End-A refers to a connection starting point and End-Z to an end point. The returned End-Zs depend on the service to be created, i.e. type, bandwidth, QoS parameters, etc.

A possible embodiment uses a search algorithm, e.g. a modified breadth or depth search, which provides all possible solutions. The TMN application would run the search algorithm in background and would return all or, if desired, a limited number of connectable boundary nodes (or ports/links) with the unsuitable nodes eliminated.

In general the algorithm would have the following behavior (without optimi...