WO2003041325A2 - Systeme de gestion d'inventaire de reseau - Google Patents

Systeme de gestion d'inventaire de reseau Download PDF

Info

Publication number
WO2003041325A2
WO2003041325A2 PCT/GB2002/005080 GB0205080W WO03041325A2 WO 2003041325 A2 WO2003041325 A2 WO 2003041325A2 GB 0205080 W GB0205080 W GB 0205080W WO 03041325 A2 WO03041325 A2 WO 03041325A2
Authority
WO
WIPO (PCT)
Prior art keywords
network
database
data
utilisation
tree
Prior art date
Application number
PCT/GB2002/005080
Other languages
English (en)
Other versions
WO2003041325A3 (fr
Inventor
Robert Frederick Abineri
Terry Shackle
Matthew Jackson
Original Assignee
British Telecommunications Public Limited Company
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by British Telecommunications Public Limited Company filed Critical British Telecommunications Public Limited Company
Priority to AU2002339130A priority Critical patent/AU2002339130A1/en
Publication of WO2003041325A2 publication Critical patent/WO2003041325A2/fr
Publication of WO2003041325A3 publication Critical patent/WO2003041325A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]

Definitions

  • the invention relates to a network inventory management system, typically an inventory network management and planning system.
  • a known basic network management system is shown in Figure 1 and includes a network inventory database 1 1 , a network forecasting or modelling tool 12 and an order handling arrangement including a handling processor 13 and a handling system 19 with its own data storage. Provisioning 14 is provided following orders raised by handling system 1 9. Additional network requirements are input to the provisioning system from requirements block 1 5 providing requirements capture.
  • the network 16 will have been constructed based on a vendor's configuration, information thereon being held within an element manager block 17 including structure and traffic information. This can be made available to the inventory system.
  • the inventory database 1 1 holds information on the existing network 16, which information will have been entered previously, typically manually.
  • the stored information will relate to network sites, switches and shelves, slots or cards relating to those switches as well as port information.
  • Network management can be dealt with under a management protocol (e.g. SNMP2 - simple network management protocol 2).
  • a management protocol e.g. SNMP2 - simple network management protocol 2.
  • the network forecasting or modelling tool 12 accesses the data stored in the inventory 1 1 to allow modelling of the network to be achieved also taking into account market forecasts and strategic growth.
  • the inventory database 1 1 will also contain information on what physical components of the network are being utilised and this allows the modelling tool to provide an output (e.g. in spreadsheet form) of areas which may have spare capacity.
  • new equipment or other provisioning are passed to the provisioning system 14 from requirements process block 1 5 via order handling process 13 and system 19. New equipment is ordered by manual selection of the appropriate network availability (having considered the availability determined from the output of forecasting system 12).
  • the present invention is concerned with improving this situation.
  • a network inventory management system including: database storage means configured to store network inventory data including preset allowable utilisation data, currently provisioned network facility data and planned network facility data, access means for selectively accessing data within the storage means, means for determining actual and/or forecast utilisation levels, computation means for comparing actual and/or forecast utilisation levels with stored preset utilisation data, and display means for indicating utilisation availability.
  • a method of managing a network inventory including the steps of storing network inventory data including preset allowable utilisation data, currently provisioned network facility data and planned network facility data in a database, selectively accessing data within the database, determining actual and/or forecast utilisation levels, comparing actual and/or forecast utilisation levels with stored preset utilisation data, and displaying the results to indicate utilisation availability.
  • Figure 1 shows a known example of an inventory system incorporated into a network management system
  • Figure 2 shows part of the network with customer and switch traffic
  • Figures 3A and 3B shows network components represented in an object tree
  • Figure 4 shows an enhanced network inventory and planning system incorporating the object oriented inventory database with associated devices including a display;
  • Figure 5 shows equipment modelling on associated classes
  • Figure 6 illustrates component class types
  • Figure 7 shows navigation data set mechanisms
  • Figure 8 shows display indicia with associated values
  • Figure 9 shows both a tree view and a list view displayed simultaneously
  • Figure 10 shows a portion of the graphical display interface to allow entry of usage type values
  • Figure 1 1 shows a screen view associated with the search facility
  • Figure 12 shows a screen view associated with selection or a slot or port record
  • Figure 13 shows a flowchart concerned with network allocation and reservation.
  • the Figure 1 arrangement whilst providing a basic network management approach, is inflexible, because the inventory database will have been built to accommodate a single vendor's equipment only.
  • the file listing would not identify where in a particular switch, for example, the spare capacity was located.
  • the planner therefore would need to take the information and investigate in more detail what allocation ports were appropriate. Further the planner would need to review switch location positions in the network to ensure traffic requirements were not exceeded for switches or ports on the switches, which switches would typically have to cope with a mixture of network to network interface (NNI) traffic and user to network interface (UNI) traffic.
  • NNI network to network interface
  • UNI user to network interface
  • FIG 2 a portion of a typical network is shown.
  • the network includes a number of switches A, B, C connected as shown.
  • a customer D has access to the network via switch B.
  • This user traffic or (UNI) ingress has to be accommodated as well as switch traffic (NNI) ingress.
  • the switch B output is entirely NNI traffic to switch C.
  • the egress will be entirely NNI. Therefore, dependent on the position in the network, the database is arranged to incorporate presets on the UNI to NNI ratio, with a default typically 50% and with a traffic maximum (switch fill) preset typically 80%.
  • Switches for example will be structured to include shelves, cards and ports and the layers can be represented by the tree structure of Figure 3A. However, not all switches are constructed identically and, as shown, can include sub-shelves for example which can give rise to errors in the correct identification of ports within the structure when trying to construct an object oriented database where standard object tree rules require that each class of object in the tree adds to the overall object identifier.
  • port Pm in Figure 3A will have the object identifier 21 21 2 as its path from the root in Figure 3A is switch 2, shelf 1 , slot 2, card 1 , port 2.
  • the modified identifier in combination with the switch name (i.e. Coventry) forms the unique key in the other filing system.
  • the card at 2121 (previously shown in the Figure 3A view) can be associated with slot at 21 2 so that this object (card) is accommodated by the slot (and is now 'hidden' in the tree view). This then gives an identifier 21 22. Also, the half shelf at 21 does not contribute to the object identifier leaving a modified object identifier of 222.
  • This computer indexing method adds a virtual dimension to the database so instead of merely referencing up or down the tree, a different path for parallel referencing is introduced, the second object identifier determines the contribution to the tree structure.
  • the first object identifier is 2121 2 and the second object identifier is 222. If desired, more than two object identifiers can be utilised to enable multiple index references to be provided.
  • This mechanism allows us to incorporate the vendor's index as we build the tree and so avoids the need for a separate object identifier and vendor identifier scheme. This also allows a new vendor's equipment to be added to the inventory system by building that vendor's identifiers into the object identifier.
  • This method of indexing a flat file (i.e. a non object oriented file) to an object orientated database by defining classes and 'accommodating' objects provides a powerful tool to provide a more accurate database, so that the network can be more realistically utilised.
  • the system including the network equipment allocation tool (NEAT) which employs an object oriented inventory database 20 for network 26 is built with data received from the vendor's data available from the element manager 25 by employing the modified object tree procedure described above.
  • Other defining data is provided from forecasting/modelling process block 22 to preset UNI/NNI levels and other site information such as switch fill maxima.
  • the database 20 is now arranged such that the requirements processor 24 is intrinsically linked to the database so that actual inventory data in database 20 is also updated with planned inventory data, even before the additional utilisation is installed, so that the database 20 provides a more current appraisal of the network utilisation than heretofore due to the presence of inventory portions associated with currently provisioned network facilities and with planned network facilities.
  • This allows the forecasting device 22 to provide a more accurate model of network structure and utilisation as it receives actual and planned inventory data from database 20.
  • any planner with access to the system will have all requisite information for further planning.
  • the inventory 20 now provides network information to the order handling processor 28 to ensure accurate provisioning so as to drive the order handling system 23.
  • This provisioning process utilising the inventory 20 as an output to the order handling process maintains accurate operation and the order handling output from system 19 allows physical provision implementation.
  • the system can cope with more than one vendor's equipment and element managers 31 , 32 also provide information on the network for receipt by the database 20.
  • a unique display 27 allows utilisation and network structure information held in database 20 to be displayed via generator 34.
  • the site information i.e. Coventry
  • the linear indicia bar type display 35 with portions 35a, 35b is configurable to represent capacities (e.g. ingress/egress) and their utilisation on the network. Its generation is described with reference to Figure 8 below. The darker the shade of the display, the greater the amount of egress already utilised relative to the preset value. If a colour display is provided the linear indicia of the display could change from green to red with intermediate colours when some way beyond minimum towards the maximum.
  • the displays 40 to 43 show availability on shelves P1 to P4 respectively.
  • Figure 9 shows the tree view together with the bar display 36 associated with slots 1 -6 and display 37 for slots 7-12 on shelf P3 to indicate how many slots are populated.
  • the report generator 30 produces further information such as trend analysis, platform health, planning rule observance and planning listings.
  • a user interface 38 which may be web-based allows access to planners and allocation administrators with appropriate security mechanisms in place.
  • the object identifier is a value which represents a unique position in a tree derived from the node positions at each level of the tree.
  • objects are assigned to a class which cause a described object to behave differently in a tree as follows:
  • the Object identifier contribution for the described object may be switched off.
  • the Object class defines that the described object is able to parent.
  • the Object class defines that the described object is able to accommodate.
  • the child when an object in a tree has only one child, the child can be accommodated by the parent and the accommodated child can be removed from the tree and the accommodating object adopts the attributes of the accommodated child.
  • Site attributes are stored in a site table (see Figure 7). This could define the Coventry site referred to in Figure 4.
  • the equipment classes are user defined and are used to control the generic relationships between various network equipment object types as described above.
  • the class name can specify whether an equipment type can parent or accommodate or whether a port identifier is required.
  • the port identifier (PID) value is not included for either the class switch or card. This is because when created, the PID needs to correspond to the PID from the vendor's report.
  • the port identifier (PID) discussed above is essential in identifying either a port or a slot, the element manager (from the vendor's database) will identify a specific slot or port using the switch name and the PID alone. Hence, for example, P1 -2 would locate slot 2 in shelf 1 or P1 -5-1 locates port 1 in slot 5 of shelf 1 (see also Figure 5), Some pieces of network equipment do not add to the PID value (card, for example) and the offsets of the various values of the PID can change depending on the build used. This allows the correct identification of ports or slots to be made.
  • the values for site, class and type are taken from their definitions.
  • the Name identifies the equipment and appears in the navigation tree.
  • the Alt Name is the five digit number used by the vendor element manager to identify the switch. The preset UNI/NNI ratio and the Access Fill are entered as shown.
  • Floor to Rack is concerned with location of the switch fabric. The columns relate to information chosen from the class shelf. As the switch class is defined as 'parent of shelf then only shelf types will be altered.
  • the Alt Name and Address fields will be empty at the time of creation of the planned switch process. All attributes from this point cascade down the tree to the ports. As shown in the display of Figure 4, the navigational view using an object tree approach gives rapid and clear information on the site information and switch build.
  • the mechanisms associated with the navigation data set are shown in Figure 7.
  • the inventory is built using object oriented data in the modified tree form unique to the system.
  • the navigation through the network includes network site and the components within that site.
  • the class is created under the control of editor with the three attributes set by the rules and these variable classes are then attributed types.
  • each type will always be in a class (e.g. slot or card) generic to the network equipment that may be used by an operator.
  • the variable type is selected for the specific build to identify the actual component within the context of their location and use.
  • NEAT enables the system operators to create a database which can reflect the format of any vendor's element manager output thereby enabling the population and comparison of data within the database with the element manager data. Due to the flexibility of the tree many element manager data formats may be represented thereby allowing NEAT to support multiple equipment makes and types.
  • Empty slots may be populated with planned data which may be simultaneously available to a number of planners in various locations within an operator's business.
  • OSS service and support tools
  • Customer circuit ID will be concerned with customer details in the lookup circuit ID.
  • the graphical representation displayed is the navigational view of the object oriented database in relation to the relevant object, used to represent the state of the database or the data contained within the database and as shown in Figure 4 includes visual indicia in the form of an indicator or gauge via the display generator.
  • the indicator will change colour and/or shape to indicate that a threshold set within the range of the gauge has been reached, exceeded or has fallen below the threshold.
  • At least four values are required which may be either operator defined or derived from values or results of calculations performed on one or more values within the database and may include operator defined data.
  • the four values required to generate the gauge or indicator are: RANGE (the extent of the indicator)
  • THRESHOLD the value used to trigger a change in the display of the indicator or gauge when the current value either equals, exceeds or does not exceed the THRESHOLD value, the behaviour can be defined by a user
  • additional THRESHOLDS can be used to activate different animations of the gauge or indicator display (e.g. green, amber, red)
  • SCALE the granularity of the indicator
  • the display is constructed using the same number of image parts or a multiple of SCALE and some coloured or changed to represent the CURRENT VALUE based on the value in Result.
  • the displays shown on the right column show a scale with either 10 or 15 segments.
  • the result (using the formula) will, in the first display instance, cause 5 segments to be darkened. Other combinations are illustrated including alarm function.
  • a list view can be provided to produce a one line record for every instance of the level below the current navigation level. Hence, if the navigational view selected is at shelf level, the list display will show the list of cards.
  • the list view relate to the slots and will be as shown in Figure 9. Both the tree and list view can be viewed simultaneously on the display, if required. Under mouse control by double-clicking on the screen, the display can show the next level both for tree and list view as appropriate. Hence, selecting the slot information of Figure 9 will produce port information for display.
  • the list view can be set to show all ports from the point selected in the navigational tree view and below.
  • the expansion or collapsing of the views is therefore possible to provide the degree of information required with availability shown in the tree view by the bar display.
  • Table 4 shows the hierarchy based on the switch used in the example described.
  • the Notes/Use dialog will be available to Planner/Builders and Allocation Administrators. As shown in Figure 10, the usage type value is settable by the system administrator from a selected on-screen display.
  • Additional screen views allow access to the data within the database.
  • GUI graphical user interface
  • Figure 1 1 shows the screen view associated with a comprehensive search facility to enable administrators to search both the card records and the port (Link End) records data, which will be displayed as a list view.
  • the output would also be printed or saved to file in a comma separated variable length text file format (CSV format).
  • CSV format variable length text file format
  • Figure 12 shows the screen view associated with selection of either a slot record or a port record. Users can edit the port allocation or change the cards in the slot in this view.
  • the display will generate a warning to the user so that they will be aware of the possibility of losing all port information. Any allocations made will carry identification information regarding user name and allocation date.
  • Allocations will carry an expiry date and will be preset, typically for a three month period. This allows allocations to be removed automatically if not used by the expiry date to free up network space.
  • Figure 13 shows a flowchart showing the process employed concerned with verifying and, if necessary, adjusting NNI reservations of network switches.
  • a non-network inventory could be constructed for use with ISBN publications for example.
  • different tree representations could be generated using the method described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

L'invention concerne un système de gestion d'inventaire de réseau comprenant une base de données orientée objet (20), destinée à un réseau (26) qui reçoit des données à partir de gestionnaires d'éléments (25, 31 et 32) et des données d'attribution préréglées à partir d'un processeur (22), pour établir une base de données précise d'exigences réelles et planifiées, ainsi qu'un mécanisme d'approvisionnement destiné à des ordres futurs. Un écran (27) fournit un affichage de réseau sous forme d'arbre, associé à des affichages de type barre concernant la disponibilité des composants de réseau associés affichés, de sorte à fournir une compréhension rapide du statut des parties appropriées du réseau.
PCT/GB2002/005080 2001-11-09 2002-11-11 Systeme de gestion d'inventaire de reseau WO2003041325A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002339130A AU2002339130A1 (en) 2001-11-09 2002-11-11 System and method for network inventory management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP01309485 2001-11-09
EP01309485.9 2001-11-09

Publications (2)

Publication Number Publication Date
WO2003041325A2 true WO2003041325A2 (fr) 2003-05-15
WO2003041325A3 WO2003041325A3 (fr) 2003-11-13

Family

ID=8182442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2002/005080 WO2003041325A2 (fr) 2001-11-09 2002-11-11 Systeme de gestion d'inventaire de reseau

Country Status (2)

Country Link
AU (1) AU2002339130A1 (fr)
WO (1) WO2003041325A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7797425B2 (en) 2005-12-22 2010-09-14 Amdocs Systems Limited Method, system and apparatus for communications circuit design

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0820203A2 (fr) * 1996-07-15 1998-01-21 AT&T Corp. Procédé et dispositif pour l'usage efficace des ressources d'un réseau de télécommunication

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0820203A2 (fr) * 1996-07-15 1998-01-21 AT&T Corp. Procédé et dispositif pour l'usage efficace des ressources d'un réseau de télécommunication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SUZUKI K: "Information Engineering Architecture for Strategic Network Operations and Management Platforms" PROCEEDINGS OF NOMS '94, 14 - 18 February 1994, pages 268-277, XP002198730 Kissimmee,FL,USA *
YAMAMURO M ET AL: "Strategic Network Resource Inventory Management" PROCEEDINGS OF NOMS '94, 14 - 18 February 1994, pages 508-518, XP002198729 Kissimmee,FL,USA *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7797425B2 (en) 2005-12-22 2010-09-14 Amdocs Systems Limited Method, system and apparatus for communications circuit design

Also Published As

Publication number Publication date
WO2003041325A3 (fr) 2003-11-13
AU2002339130A1 (en) 2003-05-19

Similar Documents

Publication Publication Date Title
US7308454B2 (en) Data integration
US6854091B1 (en) Method of displaying nodes and links
US6473762B1 (en) System and method to automatic equipment placement at remote sites
US6141680A (en) Method and apparatus for providing and facilitating interaction with distributed manager information of a network
US10983891B2 (en) Method and system for implementing a data center operating system
CA2457878A1 (fr) Outil de modelisation et de gestion de projets
US20080222098A1 (en) Methods, systems, and computer program products for providing consolidated order information
CN101026497A (zh) 用于与作为分组的多属性系统资源交互的装置和方法
US20100325019A1 (en) System and process for documenting network assets
CN110838944A (zh) 一种云中心租户维度拓扑图的实现方法
US7386539B2 (en) System, method, and user interface providing customized document portfolio management
US20050044079A1 (en) Visual representation of data within a database
CN108762748A (zh) 一种基于数据中心的数据展示方法及系统
CN110989891B (zh) 一种图表编辑器中组件部署方法、图表编辑器及相关设备
CN111400332A (zh) 项目进度的监控方法及装置
EP1296270A1 (fr) Dispositif à aider à la gestion de contrats
US20050182601A1 (en) Rack configuration determination support system
WO2003041325A2 (fr) Systeme de gestion d'inventaire de reseau
CN110705228A (zh) 可自定义的能源管理平台数据图表展示方法和装置
US9769036B1 (en) Port assignment of network devices reference and management
CN108073624A (zh) 业务数据处理系统及方法
JP2004303188A (ja) ライセンス管理システム及び方法
Mitropoulos et al. A prototype network monitoring information system: modelling, design, implementation and evaluation
CN117520166A (zh) 基于pict测试的案例生成方法、装置、设备及介质
KR100706948B1 (ko) 단순 네트워크 관리 프로토콜 시스템에서의관리정보베이스 구성 및 관리 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP