|Publication number||CA2451947 A1|
|Application number||CA 2451947|
|Publication date||15 Jun 2005|
|Filing date||15 Dec 2003|
|Priority date||15 Dec 2003|
|Publication number||CA 2451947, CA 2451947 A1, CA 2451947A1, CA-A1-2451947, CA2451947 A1, CA2451947A1|
|Inventors||Arefzadeh S. A. Shahin|
|Applicant||Arefzadeh S. A. Shahin|
|Export Citation||BiBTeX, EndNote, RefMan|
|Referenced by (5), Classifications (9), Legal Events (1)|
|External Links: CIPO, Espacenet|
Right now the two biggest OSS inventory leaders of the market Granite and Cramer need more than 6 months to implement their projects in Tier-1 environment. Most of the time is being consumed by data validation and take over of existing data in the new environment. After the implementation the data needs to be kept accurate. For this purpose most of the companies have such a synchronization tool, which tries to keep the data up to date (ca. 70%). Other companies are able to feed the inventory system with accurate data out of network with regards to Chassis Cards Ports Power supplies Fans Hardware, software and firmware Logical service components .
Hereby the emphasis is still the physical asset management. The support for logical service is built rudimentary. In reality such an extended project for auto-reconciliation would take another 3 months to get implemented.
The described scenario would apply for old fashioned SDHISONET networks. As most companies are moving toward IP based network in a fully dynamic environment, the mentioned scenario is getting more complex. The modeling phase is not a one-time approach, rather than ongoing.
The auto-reconciliation is ideally being run once-a-day.
The Zerp-Touch Inventory is a fully automated, 1009 zero-error-prone approach, to model the inventory data based on the data fed directly by the network. There is no human interaction required in order to keep the data loaded out of the network(s). The data will be gathered and then compiled in order to generate new data e.g. to see who is running VoIP from node A to node Z. This approach is not only covering ISO/OSi model Layer1 to Layer 3, but furthermore the application layer. As situation changes rapidly in dynamic IP environment, a smart rule based engine needs to be developed to compile the data constantly and provide the user with up to date and accurate data. The rule based engine needs to be self configurable in order to minimize the maintenance cost.
Zero-Touch inventory ultimately will provide the user with an exact snapshot of the current configuration of the network(s).
The sources to load data out of networks) could be the following:
- Telnet module o Queries data from IOS-based Cisco equipments - Corba module o Queries data from Cisco VPN SC
o Receives notifications from Cisco VPN SC
- SNMP module o Queries data from SNMP-based equipments o Receives traps from equipments HP OpenVisw Once the data are loaded and compiled into useful inventory data, a complete path consisting of equipment, links in between can be displayed and visualized. The following example explains the goal of the invention. In the frgure 2 a simple network consisting of 4 Cisco 15414 network is displaced.
Furthermore we assume that Cisco 7502 Router is being used to transfer IP
networks directly this backbone. In this case the Zero-Touch-Inventory module v~rould capture the equipment with regards to chassis, cards, ports. The MPLS LSP (Label Switching Paths, the logical services) are then gathered in the next step. Once all the information is gathered, the Rule Based Engine can be run to sort the data and build the inventory output data. The data flow is being shown in the figure 3.
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7729286||22 Nov 2005||1 Jun 2010||Amdocs Systems Limited||Method, system and apparatus for telecommunications service management|
|US7797425||3 Mar 2006||14 Sep 2010||Amdocs Systems Limited||Method, system and apparatus for communications circuit design|
|US8082335||16 Feb 2006||20 Dec 2011||Amdocs Systems Limited||Method and system for telecommunications network planning and management|
|US8380833||22 Jun 2006||19 Feb 2013||Amdocs Systems Limited||Method of configuring devices in a telecommunications network|
|US8650101||3 Oct 2011||11 Feb 2014||Tsn Llc||Internal material system for facilitating material and asset movement within organizational infrastructures|
|International Classification||H04L12/26, H04L12/24, G06F13/00|
|Cooperative Classification||H04L43/00, H04L41/16, H04L41/50|
|European Classification||H04L41/50, H04L43/00, H04L12/26M|