Wireless Future - Telenor

More documents

Recommendations

Info

152 The functionality describing the network TTP creation for a CMIP interface is spread across a number of constructs, e.g. the MO class definition, the conditional packages, the name bindings and the error parameters. It is not readily separable from other functional elements and is not presented here for that reason. 2.5 The Technology Viewpoint The Technology Viewpoint is concerned with implementation issues only and will not be discussed here. 3 Existing Functionality Following the approval of the enhanced RM- ODP framework in 1996, a range of recommendations applicable to technologies such as SDH, WDM and, to a certain extent ATM, were approved in 1999. The functional areas covered were: • Topology management (creation and deletion of topological resources such as subnetworks, links and access groups) [17, 18, 19]. • Pre-provisioned adaptation management (interlayer adaptation including the multiple client layer case) [20, 21, 22]; • Pre-provisioned link connection management (resource reservation) [23, 24, 25]; • Pre-provisioned link management (management of links with and without server layer support) [26, 27, 28]; • Trail management (set-up, modification and release of trails, creation and deletion of trail termination points, a number of associations between elements) [29, 30, 31]. Work is in progress to include partitioning, protection, routing, and failure propagation and also completing the model for ATM. When assessing the applicability of a technology for the model, the specific requirements of the technology are analyzed. In some cases the nonmatching requirements may be modeled on the NE level, while others may lead to technology specific extensions on the network level. For example, the assessment of ATM resulted in two major changes, the redefinition of link capacity to be either bandwidth or the number of link connections, and secondly, the notion of dynamic creation of termination points during connection setup. The applicability of the model to WDM technology was demonstrated in the ACTS project Mephisto and shown at the public presentation in October 1999 [32]. The setup of a protected trail in the OCH layer on a prototype system consisting of three OADMs in a ring structure was shown. The network model used in Mephisto is based on the generic network model. The Configuration Manager developed provides the operator with one operation for each action in the communities supported, that is, topology management, pre-provisioned link connection management, subnetwork connection management and trail management. It is argued in the Mephisto project [33] that the generic model may be utilized for the management of SDH over WDM, provided that an enhanced version of the route discovery function is used in the OCH layer. An alternative solution to limit noise accumulation is the introduction of a digital frame like the digital wrapper on top of the OCH layer combined with FEC inside each network operator domain involved. 4 Functionality under Development; Connectionless Communication So far, only technologies for the core network have been considered. There are, however, increasing concerns to provide an end-to-end network view including access network technologies as well. A combined network and network element model for ATM PONs is under approval in ITU-T [34]. The current versions of G.805 and the technology specific extensions all presume connection – oriented communication, that is, prior to traffic flowing, a connection has to exist. With connectionless communication there is no connection setup in advance. To cope with that, a novel network architecture with the working title “g.cls” [35] is currently being defined in SG.13. The scope is not limited to connectionless technologies, so there is a potential for g.cls to become the replacement of G.805 rather than a complement. Developing a network model for connectionless technologies is part of the work plan for Q.18/4. If IP is to become the major network technology of the future, enhancements in the routers as well as in the hosts are necessary. A comprehensive network model is a powerful tool for analyzing as well as managing such an enhanced IP based network. One of the major enhancements necessary relates to the communication paradigm. It is widely agreed that the current “Best Effort” approach should not be the only level supported. Traffic Engineering is a toolbox that is being proposed to provide differentiation to the com- Telektronikk 1.2001
munication paradigm and thus to the QoS 6) , utilizing mechanisms such as RSVP [36], IntServ [37], DiffServ [38], MPLS [39], and COPS [40]. In addition, a control framework is necessary to verify compliance between planned and actual traffic and also for specifying how to deal with excess traffic. At the same time, one is trying to preserve the structural simplicity of the existing Internet. Differentiated service quality should lead to differentiated charging. Consequently, new charging models must be developed to complement the existing flat rate charging scheme. The second argument for an extension of the model is the interworking between IP and other technologies. Primarily, client-server schemes with IP in the client role are foreseen, but peerto-peer configurations are expected too. A variety of interworking schemes need to be considered, ranging from gateways supporting one specific management function to the full interworking between IP and other technologies. Another concern is that of handling the vast forecast increase in traffic as discussed in papers by Anderson [41] and others . This traffic will be aggregated and handled by large capacity routers. Unfortunately, data traffic on the one hand and voice and video traffic on the other pose quite different requirements to the network in terms of packet loss, delay and delay variation. This makes the traffic grooming function more complex. There are also issues relating to the work split between routing on the client level (IP) and the server level (OTN/WDM). 5 Conclusion The development of the generic network level model in Q.18/4 is based on two major foundations: • The Generic Network Architecture defined in G.805; • The Enhanced Reference Model for Open Distributed Processing (RM-ODP) defined in G.851.1. The modeling methodology is described in Chapter 2. The model for the creation of a trail termination point is provided as an example to illustrate the usage of the various modeling constructs available throughout the three viewpoints constituting the protocol neutral part of the model. The functionality provided by the existing model is described in Chapter 3 and the future extensions, the access network and connection-less communication, i.e. IP, are discussed in Chapter 4. To the knowledge of the author, the main application of the model so far has been to serve as the basis for the development of generic as well as technology specific models in fora such as the Tele Management Forum (TMF), the ETSI TMN, the SONET Interoperability Forum (SIF) and the ATM Forum. It is expected, though, that the inclusion of technologies for the access network and connectionless communication will open up for wider application, in particular when end-to-end issues, i.e. QoS, in combination with requirements for an abstract, high level network view are important. 6 References 1 ITU-T. Generic functional architecture of transport networks. Geneva, 11/95. (ITU-T rec. G.805.) 2 ITU-T. Management of the transport network- application of the RM-ODP framework. Geneva, 03/99. (ITU-T rec. G.851.1.) 3 ITU-T. Basic reference model for Open Distributed Processing – Part 1: Overview. (ITU-T rec. X.901.) 4 ITU-T. Basic reference model for Open Distributed Processing – Part 2: Foundations. (ITU-T rec. X.902.) 5 ITU-T. Basic reference model for Open Distributed Processing – Part 3: Architecture. (ITU-T rec. X.903.) 6 ITU-T. Basic reference model for Open Distributed Processing – Part 4: Architectural Semantics. (ITU-T rec. X.904.) 7 Henriksen, T. The generic network model – an ITU approach for interoperability. In: Proceedings of the 5th IFIP TC6 International Symposium, Interworking 2000, Bergen, Norway, October 2000. Rao, S et al (eds). Berlin, Springer, 2000. 8 IUT-T. Management of transport network – Enterprise viewpoint description of transport network resource model. Geneva, 03/99. (ITU-T rec. G.852.2.) 6) QoS should be interpreted broadly including every kind of parameter affecting the perception of the end user of the service provided. Telektronikk 1.2001 153
Page 2 and 3:
Telektronikk Volume 97 No. 1 - 2001
Page 4 and 5:
Per Hjalmar Lehne (42) obtained his
Page 6 and 7:
Stein Svaet (41) is Senior Research
Page 8 and 9:
Pbit/day 6 150 125 100 75 50 25 0 F
Page 10 and 11:
8 Video communication as a utility
Page 12 and 13:
10 The idea of reconfigurable mobil
Page 14 and 15:
12 Switched lobe Dynamically phased
Page 16 and 17:
Figure 10 The All IP vision Figure
Page 18 and 19:
16 The IP world has some problems t
Page 20 and 21:
18 Abbreviations and acronyms less
Page 22 and 23:
Jorge Pereira (40) obtained his Eng
Page 24 and 25:
(Millions) Figure 1 Exponential gro
Page 26 and 27:
24 Defining Generation based upon D
Page 28 and 29:
Multi-mode Terminal by Software Rad
Page 30 and 31:
distribution layer possible return
Page 32 and 33:
30 A Co-Ordinated Approach to 4G As
Page 34 and 35:
Figure 2 Applications will grow fas
Page 36 and 37:
Figure 5 Evolution from multi-mode
Page 38 and 39:
Operator/Provider download librarie
Page 40 and 41:
Radio network subsystem - service c
Page 42 and 43:
Dr. Techn. Jørgen Bach Andersen (6
Page 44 and 45:
Figure 3 Two arrays with M and N el
Page 46 and 47:
Figure 5 Cumulative probability dis
Page 48 and 49:
Figure 8 As in Figure 5, but with F
Page 50 and 51:
48 Conclusion The challenge of prov
Page 52 and 53:
50 models are described simply by a
Page 54 and 55:
52 ping intervals or “quantizatio
Page 56 and 57:
Figure 3 ASE as a function of the a
Page 58 and 59:
56 7 Conclusion and Further Researc
Page 60 and 61:
Dave Wisely (39) graduated in 1982
Page 62 and 63:
Figure 2 Business case study Figure
Page 64 and 65:
Figure 6 BRAIN QoS architecture 62
Page 66 and 67:
64 4 BRAIN homepage. (2001, March 6
Page 68 and 69:
Figure 2 The Bluetooth protocol sta
Page 70 and 71:
Figure 5 A Bluetooth radio module i
Page 72 and 73:
70 • Instant postcard: A Bluetoot
Page 74 and 75:
72 work visions come true, it is ne
Page 76 and 77:
Table 1 Allocated HiperLAN bands (i
Page 78 and 79:
Figure 4 Basic MAC frame structure
Page 80 and 81:
78 Preamble BCH FCH ACHs Preamble S
Page 82 and 83:
throughput bit/s 80 3 2.5 2 1.5 1 0
Page 84 and 85:
82 5 References 1 CEPT. ERC Decisio
Page 86 and 87:
84 IETF Internet Engineering Task F
Page 88 and 89:
Figure 2-3 Mobile IPv6 architecture
Page 90 and 91:
88 domain, it attaches to a new lea
Page 92 and 93:
90 Domain GFA/MAP Figure 3-3 Archit
Page 94 and 95:
Geir Gylterud (35) is Research Scie
Page 96 and 97:
94 Framework Resource Resource Int
Page 98 and 99:
Figure 6 SCSs and network functiona
Page 100 and 101:
Figure 9 The new business model. Fr
Page 102 and 103:
100 A strong consortium backs up th
Page 104 and 105: 102 Music Company Figure 3 Service
Page 106 and 107: Figure 4 OSA architecture service c
Page 108 and 109: Do van Thanh (43) obtained his MSc
Page 110 and 111: Figure 2 The first use case diagram
Page 112 and 113: 110 Box 1 - The Open Service Archit
Page 114 and 115: 112 X:User 1:Device 2:Device 3:Devi
Page 116 and 117: Figure 10 Initiating call from PSTN
Page 118 and 119: Figure 13 Splitting the incoming st
Page 120 and 121: Figure 17 A set of communication de
Page 122 and 123: 120 Box 3 continued Session Descrip
Page 124 and 125: Figure 21 A laptop and peripheral d
Page 126 and 127: 124 Box 4 - Bluetooth Bluetooth is
Page 128 and 129: 126 6 The ICEBERG project. (2001, M
Page 130 and 131: 128 new door towards the upcoming f
Page 132 and 133: ? Figure 1 The Mobile Service Platf
Page 134 and 135: Figure 2 Needs and Related Services
Page 136 and 137: 134 Telektronikk 1.2001
Page 138 and 139: 136 Telektronikk 1.2001
Page 140 and 141: Anne Lise Lillebø (52) is Adviser
Page 142 and 143: 140 with other SDOs (Standards Deve
Page 144 and 145: 142 Box 2 - ETNO Declaration We, th
Page 146 and 147: Arve Meisinset (52) is Senior Resea
Page 148 and 149: 146 In ITU-T we have seen needs to
Page 150 and 151: 148 Each viewpoint constitutes a se
Page 152 and 153: Figure 2 UML class diagrams for tra
Page 156 and 157: 154 9 Potter, B et al. An introduct
show all

Wireless Future - Telenor

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?