1、 ETSI TS 102 672 V1.1.1 (2009-11)Technical Specification Satellite Earth Stations and Systems (SES);Broadband Satellite Multimedia (BSM);Management Functional ArchitectureETSI ETSI TS 102 672 V1.1.1 (2009-11)2Reference DTS/SES-00289 Keywords architecture, broadband, management, multimedia, satellite
2、 ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can
3、be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the r
4、eference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI docume
5、nts is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permi
6、ssion. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Member
7、s. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owne
8、d by the GSM Association. ETSI ETSI TS 102 672 V1.1.1 (2009-11)3Contents Intellectual Property Rights 5g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 10
9、g34 Overview and Background . 12g34.1 Existing Solutions and Standards . 12g34.2 Availability of NMS/OSS solutions . 13g35 BSM network management functional requirements . 14g35.1 Management Functions 14g35.2 Management logical layered model 14g35.3 Management Plane . 16g35.4 Security 16g35.5 BSM Re
10、commendations . 16g36 BSM Network Management Scenarios 16g36.1 Management Relationships between BSM Network Actors 17g36.2 Scenarios of relationships between network actors 18g36.3 Global Network Management Architecture 20g36.4 BSM Service Management Scenarios 20g36.4.1 Residential Internet Access S
11、cenario 20g36.4.2 Enterprise Office-LAN Interconnect Scenario A 21g36.4.3 LAN Interconnect Scenario B . 22g37 BSM Management Architecture . 23g37.1 BSM Management Architecture Fundamentals 23g37.2 BSM Management Functional Architecture . 24g37.2.1 Internal Interfaces . 26g37.2.2 External Interface 2
12、6g37.2.3 Evolution to Web-based Network Management Architectures . 27g37.2.3.1 Browser-Based Management of SNMP-based BSM 27g37.2.3.2 Browser-Based Management with modified SNMP Elements . 27g37.2.3.3 Multiple http/IP/SNMP management protocols 28g37.3 BSM Management Data Models 29g37.3.1 Data Model
13、Structure 29g3Annex A (informative): Overview of Existing Network Management Architectures 30g3A.1 Overview 30g3A.1.1 Network Management Architecture Classification 30g3A.1.2 Data Model . 30g3A.1.3 Organisational Model . 31g3A.2 SNMP (IETF) . 31g3A.2.1 SNMP Versions 32g3A.2.2 SNMP architecture . 32g
14、3A.2.3 MIBs . 33g3A.2.3.1 DVB-RCS . 34g3A.2.3.2 MIB Views 35g3ETSI ETSI TS 102 672 V1.1.1 (2009-11)4A.2.3.3 SNMP Traps/Notifications . 35g3A.2.3.4 RMON 36g3A.3 TMN (ITU) . 37g3A.3.1 FCAPS Model 37g3A.3.2 CMIP (ISO) 37g3A.3.3 NGN Network Management. 38g3A.4 NGOSS, OSS/J and TOM/eTOM (TMF) . 38g3A.4.1
15、 OSS/J 38g3A.4.2 TOM . 39g3A.4.3 eTOM business process framework . 39g3A.5 CORBA and OMA (OMG) 41g3A.6 CIM and WBEM (DMTF) . 41g3A.7 TISPAN (ETSI) 41g3A.8 Java/RMI 42g3History 44g3ETSI ETSI TS 102 672 V1.1.1 (2009-11)5Intellectual Property Rights IPRs essential or potentially essential to the presen
16、t document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in resp
17、ect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the
18、 existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SE
19、S). Introduction The focus of the present document is on the functional architecture of network management for BSM systems, including the management of IP-based services. Network Management of IP-based broadband satellite multimedia (BSM) systems may be chosen to be similar in many ways to that of t
20、errestrial networks. However there are important differences in emphasis, for example in that the management traffic overhead across a satellite system should be minimised. Also the scalability of satellite networks interconnecting potential many terminals must be considered. Furthermore, integrated
21、 management of satellite and terrestrial IP networks has not been widely implemented and a standardised approach is considered desirable. The BSM network management system (BNMS) should also be designed to cope with the latency and bandwidth asymmetry that are characteristic of satellite links. Howe
22、ver the timescale of management operations is usually of an order that does not impose tight time constraints or high data rates. ETSI ETSI TS 102 672 V1.1.1 (2009-11)61 Scope The present document defines an open specification dealing with scenarios and functional network architectures for the manag
23、ement plane (M-plane) of Broadband Satellite Multimedia (BSM) systems, including any potential interfaces with external or higher level network management functions. The BSM management functions should include, for example, performance management, security management and QoS management, including th
24、e associated management functions of Service Level Agreements (SLAs) and Policies. The BSM management functional architecture will take into account requirements for emerging IP-centric (Internet Protocol) broadband multi-service satellite-based networks, integrated with fixed and wireless (broadban
25、d) access networks on one side, and backbone networks on the other. This internetworking and service interoperability scenario is generally within the scope of Next Generation Networks. The boundaries of the BNMS will be defined as well as the interfaces, protocols and message types on the internal
26、and external interfaces. The specification will include, where appropriate, the BSM SI-SAP protocol stack interface including its interactions with higher and lower layers. The architecture specified will be concerned mainly with the lower layers of the management functional layers, particularly the
27、 service management, network layer management and network element management, which will allow maximum flexibility for compatibility and mediation with OSS equipment as well as for Operators in building functionality as they see fit. 2 References References are either specific (identified by date of
28、 publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use al
29、l future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in t
30、his clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific reference
31、s, the latest edition of the referenced document (including any amendments) applies. 1 IETF RFC 1213: “Management Information Base for Network Management of TCP/IP-based internets: MIB-II“. 2 IETF RFC 1445: “Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)“. 3 IE
32、TF RFC 2578: “Structure of Management Information Version 2 (SMIv2)“. ETSI ETSI TS 102 672 V1.1.1 (2009-11)74 IETF RFC 3411: “An Architecture for Describing SNMP Management Frameworks“. 5 ITU-T Recommendation M.3010: “Principles for a telecommunications management network“. 6 ITU-T Recommendation M.
33、3400: “TMN management functions“. 2.2 Informative references The following referenced documents are not essential to the use of the ETSI deliverable but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (includin
34、g any amendments) applies. i.1 ETSI TR 101 984: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Services and architectures“. i.2 ETSI TS 102 429-4: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Regenerative Satellite Mesh - B (R
35、SM-B); DVB-S/DVB-RCS family for regenerative satellites; Part 4 : Specific Management Information Base“. i.3 ETSI TS 188 001: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Management; Operations Support Systems Architecture“. i.4 “Web-based M
36、anagement of IP Networks and Systems“. J-P Martin-Flatin, Wiley. i.5 “On the Evolution of Management Approaches, Frameworks and Protocols: A Historical Perspective“. George Pavlou, J. Netw Syst Manage (2007) 15:425-445, Springer Science+Business Media, LLC 2007. i.6 IETF RFC 1155: “Structure and Ide
37、ntification of Management Information for TCP/IP-based internets“. i.7 IETF RFC 1156: “Management information base for network management of TCP/IP-based internets“. i.8 IETF RFC 1157: “Simple Network Management Protocol“. i.9 IETF RFC 1451: “Manager-To-Manager MIB“. i.10 IETF RFC 1901: “Introductio
38、n to Community-based SNMPv2“. i.11 IETF RFC 1902: “Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)“. i.12 IETF RFC 2741: “Agent Extensibility (AgentX) Protocol Version 1“. i.13 IETF RFC 3415: “View-based Access Control Model“. i.14 IETF RFC 3418:
39、“Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)“. i.15 IETF RFC 3444: “On the Difference between Information Models and Data Models“. i.16 IETF RFC 3584: “Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framewor
40、k“. i.17 IETF RFC 4741: “NETCONF Configuration Protocol“. i.18 ETSI TR 101 790: “Digital Video Broadcasting (DVB); Interaction channel for Satellite Distribution Systems; Guidelines for the use of EN 301 790“. i.19 draft-combes-ipdvb-mib-rcs-05.txt: “DVB-RCS MIB“. ETSI ETSI TS 102 672 V1.1.1 (2009-1
41、1)8i.20 SatLabs System Recommendations Part 3:“Management it deals with the signalling necessary to set up, supervise and release calls and connections Customer Premise Network (CPN): customers private network NOTE: In the simplest case, the CPN is just a single end-host or TE. data link layer: seco
42、nd layer of the OSI model it provides connectivity between segments of the network (bridging); in addition the data link may perform session control and some configuration data model: description of a specific data structure, with the way the data elements (in the structure) are defined and the rela
43、tionship to each other NOTE: It is normally used in software engineering to describe how data is represented and accessed (see also RFC 3444 i.15). eTOM: business process model or framework that has the objective of describing and classifying the business processes required for a Service Provider; i
44、t analyses the processes to different levels of detail according to their significance and priority for the business NOTE: eTOM uses hierarchical decomposition to structure the business processes according to which all of the processes of the enterprise are successively decomposed. Process elements
45、are formalized by means of a name, a description, inputs/outputs, etc. flow: flow of packets is the traffic associated with a given connection or connectionless stream having the same source host, destination host, class of service, and session identification information model: formal representation
46、 of real-world objects and concepts, with associated relationships, constraints, rules, and operations, used to specify semantics in a given domain NOTE: It includes things of interest (entities), relationships between these entities (associations), and details/characteristics of these entities (att
47、ributes). An information model provides formalism to the description of a problem domain without constraining how that description is mapped to an actual implementation in software. The possible mappings of the information model are the data models (see also RFC 3444 i.15). ETSI ETSI TS 102 672 V1.1
48、.1 (2009-11)10management plane: provides two types of functions, namely layer management and plane management functions: plane management functions: performs management functions related to a system as a whole and provides co-ordination between all the planes. Plane management has no layered structu
49、re. layer management functions: performs management functions (e.g. meta-signalling) relating to resources and parameters residing in its protocol entities. Layer Management handles the Operation And Maintenance (OAM) of information flows specific to the layer concerned. Management Information Base (MIB): virtual information store containing managed objects NOTE: Objects in the MIB (identified by their OIDs) are essentially variables, and are typically defined using Abstract Syntax Notation One format (ASN.1). M
