deploying and managing ip over wdm networks - Index of

Recommendations

Info

96 Deploying and Managing IP over WDM Networks operations map (TOM) is the framework for accomplishing this mission. The TOM defines the business processes and their interactions used by service providers in the customer, service, and network management areas. The TOM decomposition of business processes has been adopted by WINMAN, followed by the proper adaptation and customization. Also, the requirements capture following in the next section will be based in the TOM business process decomposition. 6.2.4 High-Level Management Architecture In this context the WINMAN scope can be defined through a model following the TMN architecture. Specifically, WINMAN focuses on the network management layer of the TMN OSFs pyramid. The reference points for interactions with the outer world are the northbound interface towards other service management function systems (such as those providing VPN-IP, VoIP, and MoIP) and the southbound to the element management function systems (such as those managing IP, ATM, SDH, and WDM network elements). Although the WINMAN solution is valid for any of the earlier mentioned technology, only IP and WDM will be considered in detail for implementation purposes. Finally, a presentation function system or workstation function in TMN terms is provided to the WINMAN operator as a mean of controlling and monitoring the WINMAN functionality. Although WINMAN is essentially focused on the network layer, light service layer functionality is also provided for testing and demonstration purposes. This is summarized in Figure 6.2. 6.3 Requirements Specification The approach adopted in WINMAN is to link the actors of the business model with the requirements of the WINMAN solution. In other words, the actors of the business model pose their requirements as external actors to WINMAN, and then the WINMAN system requirements will derive from the needs of the WINMAN actors. The WINMAN actors are also present in the UCs, which will lead to the WINMAN system functionality and functional architecture. The UCs are coupled with the appropriate set of requirements. Figure 6.3 depicts the WINMAN actors. The WINMAN requirements will be captured according to needs of these four external actors—the service management system, the WINMAN operator, and the IP and WDM element management systems. For this reason, the system will be treated like a black box, where the internal structure and system components are irrelevant at this stage.
Workstation reference point 6.3.1 Requirements Classification The WINMAN Management System Concept 97 Interdomain management function WDM management function Service Management Function Service management function Northbound reference point IP management function Southbound reference points Element Element Management management function Function Element Element Management management function Function Figure 6.2 The WINMAN high-level management architecture. WINMAN operator WDM EMS IP EMS The system requirements are divided into several groups, each one of them addressing a different business case. Each requirement is identified with a unique identifier (ID) so it can be easily addressed in any other document. SMS WINMAN solution Figure 6.3 Actors identified in the WINMAN business model.
Page 3 and 4:
Deploying and Managing IP over WDM
Page 5 and 6:
Deploying and Managing IP over WDM
Page 7 and 8:
Contents Foreword xv Preface xix Ac
Page 9 and 10:
Contents vii 4.2 The WDM Network El
Page 11 and 12:
Contents ix 8 Management System Des
Page 13 and 14:
Contents xi 10.3 The WINMAN Testbed
Page 15:
Contents xiii 13.4.1 Adoption of Op
Page 18 and 19:
xvi Deploying and Managing IP over
Page 21 and 22:
Preface The integration of the Inte
Page 23:
Coauthors of the IST-OPTIMIST proje
Page 27 and 28:
1 Introduction 1.1 The Importance o
Page 29 and 30:
communications. These legacy networ
Page 31:
Within these programs, consortia of
Page 34 and 35:
8 Deploying and Managing IP over WD
Page 36 and 37:
10 Deploying and Managing IP over W
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73: 46 Deploying and Managing IP over W
Page 81 and 82: 4 Management of the WDM Network Lay
Page 83 and 84: λ1λ 2 ··· λ w λ1λ 2 ···
Page 85 and 86: Management of the WDM Network Layer
Page 87 and 88: • Lightpaths that may be protecte
Page 89 and 90: • Wavelength continuity. Two conn
Page 95 and 96: 4.4.4 Management Interfaces Managem
Page 99 and 100: 5 IP Over WDM Integration Mechanism
Page 101 and 102: STM1/ATM interface requirements. Fo
Page 103 and 104: IP router OLA The version of IP ove
Page 105 and 106: Gigabit Ethernet interface GbE prov
Page 107 and 108: the IETF extended the MPLambdaS fra
Page 109 and 110: ASON/ASTN. ITU-T will try to push t
Page 111 and 112: The proposed management solution is
Page 113: IP Over WDM Integration Mechanisms
Page 126 and 127: 100 Deploying and Managing IP over
Page 165 and 166: 8 Management System Design and Impl
Page 167 and 168: Management System Design and Implem
Page 169 and 170: checking is done at the very beginn
Page 171 and 172: 8.4.1 The Inventory Model The inven
Page 173 and 174:
for any of the three WINMAN NMSs. T
Page 175 and 176:
Management System Design and Implem
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185:
Page 188 and 189:
162 Deploying and Managing IP over
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 225 and 226:
11 Evaluation of IP over WDM Manage
Page 227 and 228:
Evaluation of IP over WDM Managemen
Page 229 and 230:
system will still perform without i
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
11.5.3.1 General Remarks The manage
Page 243 and 244:
12 Integration of IP over WDM: The
Page 245 and 246:
domains with different management t
Page 247 and 248:
Integration of IP over WDM: The LIO
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
ClientCTP Integration of IP over WD
Page 257 and 258:
AstnTrail AstnTTP NL resource Integ
Page 259 and 260:
12.4.1.1 TILAB Equipment Integratio
Page 261 and 262:
12.4.1.3 Tellium Equipment Integrat
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
At least two other possible solutio
Page 269 and 270:
13 Future Developments and Challeng
Page 271 and 272:
Future Developments and Challenges
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 303:
About the Editors Joan Serrat recei
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314:
show all

deploying and managing ip over wdm networks - Index of

Create successful ePaper yourself

Delete template?

Save as template?