1、 ETSI TS 102 675-2 V1.1.1 (2009-11)Technical Specification Satellite Earth Stations and Systems (SES);Broadband Satellite Multimedia (BSM);Part 2: Performance Management Information BaseETSI ETSI TS 102 675-2 V1.1.1 (2009-11)2Reference DTS/SES-00293 Keywords architecture, broadband, management, mult
2、imedia, satellite 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 pres
3、ent document can 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
4、of dispute, the reference 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
5、other ETSI documents 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
6、 by written permission. 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 bene
7、fit of its Members. 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 re
8、gistered and owned by the GSM Association. ETSI ETSI TS 102 675-2 V1.1.1 (2009-11)3Contents Intellectual Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2
9、 Abbreviations . 7g34 Background 7g34.1 QID elementary attributes 8g34.2 QID-level Parameters (at an ST) 8g34.3 SI-SAP-level Performance parameters (at an ST) 8g34.4 IP-level Performance parameters (BSM-wide) 8g35 BSM MIB Definition 9g35.1 MIB Structure and groups 9g35.2 Database parameters . 11g35.
10、2.1 QID Elementary Attributes . 11g35.2.2 QID-level Performance Parameters 12g35.2.3 SI-SAP-level Performance Parameters . 13g35.2.4 BSM IP Performance Parameters . 14g35.2.4.1 Two-MPs BSM IP Performance Parameters . 14g35.2.4.2 Single-MP BSM IP Performance Parameters . 15g36 Access policy 16g3Annex
11、 A (informative): MIB Syntax . 19g3Annex B (informative): Access rights . 20g3Annex C (informative): Bibliography . 21g3History 22g3ETSI ETSI TS 102 675-2 V1.1.1 (2009-11)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The
12、 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 respect of ETSI standards“, which is available fro
13、m 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 existence of other IPRs not referenced in ETS
14、I 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 (SES). The present document is part 2 of a multi-
15、part deliverable covering Performance Management aspects in “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM)“, as identified below: Part 1: “Performance Management at the SI-SAP“; Part 2: “Performance Management Information Base“. Introduction The ETSI BSM Technical
16、Reports i.1, i.2 and i.3 outlined the general requirements for performance. Technical Specifications 1, 2 and 3 have subsequently defined the BSM Management Functional Architecture, the BSM Performance Parameters and Performance Management respectively. As a result of these documents, the focus of t
17、he present document is on the definition of a set of performance-related managed objects that can be used to manage a BSM sub-network. ETSI ETSI TS 102 675-2 V1.1.1 (2009-11)51 Scope The present document defines the requirements for management interfaces relating to Performance Management in BSM net
18、works, by providing an overview and guidelines for deriving a formal set of parameters (or managed objects) for one or more databases or MIB modules. These requirements are based on the concepts defined in 3. These parameters may be applied to one or more SNMP MIBs, for example. 2 References Referen
19、ces are either specific (identified by date of 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
20、is accepted that it will be possible to use all 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/Refer
21、ence. NOTE: While any hyperlinks included in this 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 edi
22、tion cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI TS 102 672: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Management Functional Architecture“. 2 ETSI TS 102 673: “Satellite
23、Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Performance Parameters“. 3 ETSI TS 102 675-1: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Performance Management at the SI-SAP“. 4 IETF RFC 2578: “Structure of Management Information Versio
24、n 2 (SMIv2)“. 5 IETF RFC 2579: “Textual Conventions for SMIv2“. 6 IETF RFC 2213: “Integrated Services Management Information Base using SMIv2“. ETSI ETSI TS 102 675-2 V1.1.1 (2009-11)62.2 Informative references The following referenced documents are not essential to the use of the present document b
25、ut they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ETSI TR 101 984: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Services and archit
26、ectures“. i.2 ETSI TR 101 985: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia; IP over Satellite“. i.3 ETSI TR 102 157: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia; IP Interworking over satellite; Performance, Availability and Quality of S
27、ervice“. i.4 ITU-T Recommendation M.3400: “TMN management functions“. i.5 IETF RFC 4181: “Guidelines for Authors and Reviewers of MIB Documents“. i.6 SatLabs System Recommendations Part 3 - Management it deals with the signalling necessary to set up, supervise and release calls and connections data
28、model: description of a specific data structure, with the way the data elements (in the structure) are defined and the relationship to each other NOTE: It is normally used in software engineering to describe how data is represented and accessed (see also RFC 3444 i.8). information model: formal repr
29、esentation 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 ent
30、ities (attributes). 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.8). ETSI ETSI TS 102
31、 675-2 V1.1.1 (2009-11)7management plane: this 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 NOTE: Plane management ha
32、s no layered structure. layer Management functions: performs management functions (e.g. meta-signalling) relating to resources and parameters residing in its protocol entities NOTE: Layer Management handles the Operation And Maintenance (OAM) of information flows specific to the layer concerned. Man
33、agement Information Base (MIB): virtual information store containing managed objects NOTE: Objects in the MIB (identified by their OIDs) are essentially variables, and are defined using the mechanisms defined in the SMI 4, typically using Abstract Syntax Notation One format (ASN.1). network control
34、centre: equipment at OSI Layer 2 that controls the access of terminals to a satellite network, including element management and resource management functionality 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: BNMS BSM Network Management System B-NMS BS
35、M Network Management System BSM Broadband Satellite Multimedia IP Internet Protocol IPFIX IP Flow Information Export ITU International Telecommunications Union MIB Management Information Base NMC Network Management CentreOAM Operation And Maintenance OID Object Identification OSI Open Standards Inst
36、itute QID Queue Identifier QoS Quality of Service RFC Request For Comments RMON Remote Network Monitoring SI-SAP Satellite Independent-Service Access Point SLA Service Level Agreement SMIv2 Structure of Management Information version 2 SNMP Simple Network Management Protocol ST Satellite Terminal 4
37、Background BSM performance parameters have been defined in 2 and these are used as the basis for the database objects defined in the present document. The performance parameters identified in 2 need to be calculated, in some cases, from QID elementary attributes, as it was described in 3. The locati
38、on of BSM databases and the way in which they may be accessed is described in 1 and 3. Figure 1 shows the overall management architecture. A database (MIB) in the ST stores parameter values as objects. Typically the BNMS would use SNMPv2c commands to obtain the parameter values from the ST MIB. An S
39、NMP agent in the ST responds to commands from an SNMP client in the BNMS. The ST MIB should support local management (through typically a user Ethernet interface) and remote management via the satellite. ETSI ETSI TS 102 675-2 V1.1.1 (2009-11)8BSMNMCBSMST/GW/NCC/OBPBNMSSM: Service ManagerNM: Network
40、 ManagerEM: Element ManagerMF: Management FunctionXIA: External I/F AdaptorD/B: DatabaseMFExternalManagement I/FXIASNMP agenthttp serverIP ES/hostSNMP mgerhttp clientIP ES/hostASN.1/MIBhttps/XMLPrivate DataSMNMEMD/BD/BTo OSSFigure 1: BSM Management Functional Architecture A BSM Performance database
41、(e.g. one or more MIBs) will allow: 1) Performance of individual STs to be monitored by accessing their MIBs. 2) Performance of the BSM from end-to-end to be monitored by accessing MIB parameters available in a central location such as the B-NMS (BSM Network Management System), and for these BSM per
42、formance MIB objects to be made available to other systems. The QID elementary attributes and the BSM performance parameters are further described below. 4.1 QID elementary attributes These are very basic QID attributes (such as packet counters and queue lengths) which can be used in practice to com
43、pute the QID-level and SI-SAP-level parameters, as described in 3. 4.2 QID-level Parameters (at an ST) These are the basic parameters which are related to the virtual queues at an SI-SAP, and can be extracted directly from measurements thereon or used to control them. Some of these parameters can be
44、 measured directly, some of them can be derived from more elementary QID attributes (described above). 4.3 SI-SAP-level Performance parameters (at an ST) These are parameters referring to the complete interface. Some of them need to be extracted from local measurements, some of them may be derived l
45、ocally or remotely form the QID-level parameters. 4.4 IP-level Performance parameters (BSM-wide) The BNMS may also create a database for access by other or higher level systems. This database contains end-to-end performance parameters derived from ST measurement parameters. These are termed IP perfo
46、rmance parameters below. The way in which these end-to-end BSM parameters may be measured and calculated is described in 3 and for example, could use IPFIX or RMON protocols. ETSI ETSI TS 102 675-2 V1.1.1 (2009-11)95 BSM MIB Definition 5.1 MIB Structure and groups The MIB-II 3 definition is taken as
47、 the basis for a BSM MIB. For BSM, two different MIB modules could be considered for location of the OIDs: A private MIB module (under iso.org.dod.internet.private.enterprises branch). MIB-II standard “interfaces“ module (under iso.org.dod.internet.mgnt.mib-2.interfaces branch). In MIB-II the interf
48、aces group defines a generic set of managed objects such that any lower-layer network interface to IP can be managed in an interface-independent manner through these managed objects. The interfaces group provides the means for additional managed objects specific to particular types of network interf
49、ace (e.g. the BSM SISAP) to be defined as extensions to the interfaces group for media-specific management. At this stage in the BSM specification, a private MIB only is considered, but it should be capable of compatibility with an interface MIB module. The location of the BSM vendor-specific MIB (vendor-specific RFC) within the MIB-II is shown diagrammatically as follows. enterprises(1)private (4)dod(6)internet(1)org(3)iso(1)Figure 2: Private MIB location (OIDs in brackets) Four sub-groups, syste
