Network Meta-Data Libraries And Related Methods
Network meta-data libraries act as repositories of evolving management information models (MIM) and management information based (MIB) models. Changes to the models may be originated using the libraries or tracked by the libraries. In addition, the libraries may be used to generate and store transformation models used by mediation units to transform changes made to network elements, such as routers, into normalized meta-data that can be understood by an operations support system.
1 . (canceled)
2 . (canceled)
3 . (canceled)
4 . (canceled)
5 . (canceled)
6 . (canceled)
7 . (canceled)
8 . (canceled)
9 . (canceled)
10 . (canceled)
11 . (canceled)
12 . (canceled)
13 . (canceled)
14 . (canceled)
15 . (canceled)
16 . (canceled)
17 . (canceled)
18 . (canceled)
19 . (canceled)
20 . (canceled)
21 . (canceled)
22 . A network meta-data library operable to:
receive at least one or more changes associated with one or more models; generate one or more transformation models associated with the received changes; and
compare the one or more generated models to one or more models associated with the received changes to ensure that the one or more generated models are substantially similar with the one or more models associated with the received changes.
23 . The meta-data library as in claim 22 further operable to:
identify parts of the generated models that are different from portions of the models associated with the received changes; and
modify the identified parts to make them substantially similar to the portions of the models associated with the received changes.
24 . The meta-data library as in claim 23 further operable to generate one or more documentation comments associated with one or more of the modified parts.
25 . (canceled)
26 . (canceled)
27 . (canceled)
28 . (canceled)
29 . (canceled)
30 . (canceled)
31 . (canceled)
32 . (canceled)
33 . (canceled)
34 . (canceled)
35 . A network meta-data library operable to determine the throughput associated with one or more of network elements using one or more transformation models.
36 . (canceled)
37 . (canceled)
38 . (canceled)
39 . (canceled)
40 . (canceled)
41 . (canceled)
42 . (canceled)
43 . (canceled)
44 . (canceled)
45 . (canceled)
46 . (canceled)
47 . (canceled)
48 . (canceled)
49 . (canceled)
50 . (canceled)
51 . (canceled)
52 . (canceled)
53 . (canceled)
54 . (canceled)
55 . (canceled)
56 . (canceled)
57 . (canceled)
58 . (canceled)
59 . (canceled)
60 . (canceled)
61 . (canceled)
62 . (canceled)
63 . A method of comparing network models in a meta-data library comprising:
receiving at least one or more changes associated with one or more models;
generating one or more transformation models associated with the received changes; and
comparing the one or more generated models to one or more models associated with the received changes to ensure that the one or more generated models are substantially similar with the one or more models associated with the received changes.
64 . The method as in claim 63 further comprising:
identifying parts of the generated models that are different from portions of the models associated with the received changes; and
modifying the identified parts to make them substantially similar to the portions of the models associated with the received changes.
65 . The method as in claim 63 further comprising generating one or more documentation comments associated with one or more of the modified parts.
66 . (canceled)
67 . (canceled)
68 . (canceled)
69 . (canceled)
70 . (canceled)
71 . (canceled)
72 . (canceled)
73 . (canceled)
74 . (canceled)
75 . (canceled)
76 . A method for determining the throughput associated with one or more of network elements, the method comprising using one or more transformation models within a meta-data library.
77 . (canceled)
78 . (canceled)
79 . (canceled)
80 . (canceled)
81 . (canceled)
82 . (canceled)