1、 ETSI TS 128 680 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Wireless Local Area Network (WLAN) management; Concepts and requirements (3GPP TS 28.680 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 128 680 V14.0.0 (2017-04)1
2、3GPP TS 28.680 version 14.0.0 Release 14Reference RTS/TSGS-0528680ve00 Keywords LTE,UMTS 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
3、de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modif
4、ied without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Us
5、ers 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 documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please sen
6、d your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission
7、 of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETS
8、I logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered
9、and owned by the GSM Association. ETSI ETSI TS 128 680 V14.0.0 (2017-04)23GPP TS 28.680 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is
10、 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 from the ETSI Secretariat. Latest updates are available on the
11、 ETSI Web server (https:/ipr.etsi.org/). 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 ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be
12、, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. Th
13、ese should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should no
14、t“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 128
15、680 V14.0.0 (2017-04)33GPP TS 28.680 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Concepts and backg
16、round 6g34.1 Overview 6g34.2 Mapping Function 6g34.3 WLAN alarm notification 6g35 Requirements 10g3Annex A (informative): Change history . 11g3History 12g3ETSI ETSI TS 128 680 V14.0.0 (2017-04)43GPP TS 28.680 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rd
17、Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release
18、date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. tech
19、nical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project Technical Specification Group Services and Syste
20、m Aspects, Telecommunication management; as identified below: TS 28.680: Telecommunication management; Wireless Local Area Network (WLAN) management; Concepts and requirements TS 28.681: Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Referen
21、ce Point (IRP); Requirements. TS 28.682: Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS). TS 28.683: Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM)
22、 Integration Reference Point (IRP); Solution Set (SS) definitions. ETSI ETSI TS 128 680 V14.0.0 (2017-04)53GPP TS 28.680 version 14.0.0 Release 141 Scope The present document describes the concepts and requirements of WLAN management that focus on WLAN performance monitoring and alarm notifications.
23、 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subse
24、quent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR
25、 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.150: “Telecommunication management; IRP Concept and definitions“. 4 IETF RFC 2863: “The Interfaces Group MIB“. 5 3GPP TS 32.111-2: “Fault Management;
26、Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 6 IETF RFC 3877: “Alarm Management Information Base (MIB)“, September, 2004. 7 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present doc
27、ument, the terms and definitions given in 3GPP TR 21.905 1, 3GPP TS 32.101 2, 3GPP TS 32.102 7, and 3GPP TS 32.150 3 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. 3.2 Abbreviations For the purposes of the present doc
28、ument, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. AC Access Controller AP Access Point IOC Information Object Class IRP Integration Re
29、ference Point NE Network Element ETSI ETSI TS 128 680 V14.0.0 (2017-04)63GPP TS 28.680 version 14.0.0 Release 14WLAN Wireless Local Access Network 4 Concepts and background 4.1 Overview The architecture for management of WLAN AP is conformant to the Management reference model as defined in Figure 1
30、of TS 32.101 2 where the WLAN AP is depicted as NE. The system context of the WLAN management is in compliance with the System Context A, defined in Figure 4.7.1 in TS 32.150 3. 4.2 Mapping Function Figure 4.2-1 provides an example of 3GPP WLAN mapping function. The mapping function is to map the re
31、levant management data produced by WLAN AP in a form suitable for distribution via the Type-2 interface to IRPManager(s). The mapping function is a logical function. Its location, as well as its internal and external interfaces, if any, are out the scope of 3GPP specification. Figure 4.2-1: Example
32、of 3GPP WLAN Mapping Function 4.3 WLAN alarm notification WLAN AP alarms can be generated from ifOperStatus (RFC 2863 4) object. The following examples extracted from RFC 3877 6 shows that the WLAN AP embeds the ifOperStatus object in the linkUp/linkDown notifications to report the WLAN AP alarms. “
33、6.1. Alarms Based on linkUp/linkDown Notifications linkDown NOTIFICATION-TYPE OBJECTS ifIndex, ifAdminStatus, ifOperStatus STATUS current DESCRIPTION “ := snmpTraps 3 linkUp NOTIFICATION-TYPE ETSI ETSI TS 128 680 V14.0.0 (2017-04)73GPP TS 28.680 version 14.0.0 Release 14OBJECTS ifIndex, ifAdminStatu
34、s, ifOperStatus STATUS current DESCRIPTION “ := snmpTraps 4 “ alarmModelIndex 3 alarmModelState 1 alarmModelNotificationId linkUp alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription “linkUp“ alarmModelSpecificPointer ituAlarmEntry.3.1 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1
35、.2.2.1.1) alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType communicationsAlarm (2) ituAlarmPerceivedSeverity cleared (1) ituAlarmGenericModel alarmModelEntry.3.1 alarmModelIndex 3 alarmModelState 3 alarmModelNotificationId linkDown alarmModelVarbindIndex 2 alarmModelVarb
36、indValue up (1) alarmModelDescription “linkDown - confirmed problem“ alarmModelSpecificPointer ituAlarmEntry.3.3 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType communicationsAlarm (2) ituAlarmPerceivedSeverity crit
37、ical (3) ituAlarmGenericModel alarmModelEntry.3.3“ WLAN AP will send a notification when ifOperStatus object changes its value. The value of ifOperStatus object is shown below (see RFC 2863 4). ifOperStatus OBJECT-TYPE SYNTAX INTEGER up(1), - ready to pass packets down(2), testing(3), - in some test
38、 mode unknown(4), - status can not be determined - for some reason. dormant(5), notPresent(6), - some component is missing lowerLayerDown(7) - down due to state of - lower-layer interface(s) MAX-ACCESS read-only STATUS current DESCRIPTION “The current operational state of the interface. The testing(
39、3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(
40、5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missi
41、ng (typically, hardware) components.“ := ifEntry 8 The following tables show that IRPAgent, together with the mapping function will map the IETF alarm notification attributes for down(2) and up(1) to the 3GPP alarm parameters as defined in TS 32.111-2 5. For each table, it also includes the example
42、of on what conditions the 3GPP alarm notification will be sent. 1) notifyNewAlarm ETSI ETSI TS 128 680 V14.0.0 (2017-04)83GPP TS 28.680 version 14.0.0 Release 14IETF alarm notification attribute Value 3GPP AlarmInformation Attribute Legal Value objectClass Carry the object class name of the IOC obje
43、ctInstance Carrying the Distinguished Name (DN) of this object instance notificationId Carry the identifier for the notification alarmActiveDateAndTime DateAndTime (It indicates the local date and time when the alarm occurred) eventTime Convey the same sematic as DateAndTime systemDN Carry either (1
44、) the IRPAgent instance containing that Interface IRP instance, or (2) the DN of that particular Interface IRP instance responsible for the emission of the notification alarmModelVarbindValue down (2) notificationType “notifyNewAlarm“ probableCause Communication Subsystem Failure ituAlarmPerceivedSe
45、verity ituAlarmPerceivedSeverity (It indicates the alarm severity as defined in ITU Recommendation X.733)perceivedSeverity Convey the same sematic as ituAlarmPerceivedSeverity ituAlarmEventType communicationsAlarm (2) alarmType “Communications Alarm “ specificProblem Absent correlatedNotifications A
46、bsentbackedUpStatus AbsentbackUpObject AbsenttrendIndication Absent thresholdInfo AbsentstateChangeDefinition AbsentmonitoredAttributes AbsentproposedRepairActions Absent additionalText AbsentadditionalInformation AbsentalarmId Mapping function allocates the alarm ID It there exists no AlarmInformat
47、ion 5 in AlarmList 5 corresponding to IETF alarm notification, and the IETF alarm notification is down (2), then the IRPAgent will send notifyNewAlarm to the IRPManager, who has a subscription with NotificationIRP. 2) notifyChangedAlarm ETSI ETSI TS 128 680 V14.0.0 (2017-04)93GPP TS 28.680 version 1
48、4.0.0 Release 14IETF alarm notification attribute Value 3GPP AlarmInformation Attribute Legal Value objectClass Carry the object class name of the IOC objectInstance Carrying the Distinguished Name (DN) of this object instance notificationId Carry the identifier for the notification alarmActiveDateA
49、ndTime DateAndTime (It indicates the local date and time when the alarm occurred) eventTime Convey the same sematic as DateAndTime systemDN Carry either (1) the IRPAgent instance containing that Interface IRP instance, or (2) the DN of that particular Interface IRP instance responsible for the emission of the notification alarmModelVarbindValue down (2)
