3GPP TS 52.021 V7.0.0 (08)

1、3gpp ts 52.021 v7.0.0 (2007-08)technical specification3rd generation partnership project;technical specification group gsm/edgeradio access network;network management (nm) procedures and messageson the a-bis interface;(release 7)the present document has been developed within the 3rd generation partn

2、ership project (3gpp tm) and may be further elaborated for the purposes of 3gpp. the present document has not been subject to any approval process by the 3gpp organizational partners and shall not be implemented. this specification is provided for future development work within 3gpp only. the organi

3、zational partners accept no liability for any use of this specification.specifications and reports for implementation of the 3gpp tm system should be obtained via the 3gpp organizational partners' publications offices.3gpp ts 52.021 v7.0.0 (2007-08)66release 7keywordsgsm, management3gpppostal ad

4、dress3gpp support office address650 route des lucioles - sophia antipolisvalbonne - francetel.: +33 4 92 94 42 00 fax: +33 4 93 65 47 16internetcopyright notificationno part may be reproduced except as authorized by written permission.the copyright and the foregoing restriction ext

5、end to reproduction in all media.© 2007, 3gpp organizational partners (arib, atis, ccsa, etsi, tta, ttc).all rights reserved.contentsforeword7introduction71scope82references83definitions and abbreviations93.1definitions93.2abbreviations94functional split between bsc and bts95information model10

6、5.1managed objects105.2addressing of objects135.3state management of objects135.3.1administrative state135.3.2operational state and availability status146elementary procedures156.1definition of the procedures166.2sw download management procedures166.2.1load data initiate166.2.2load data segment166.2

7、.3load data abort176.2.4load data end176.2.5sw activate request176.2.6activate sw186.2.7sw activated report186.3abis interface management procedures186.3.1establish tei186.3.2connect terrestrial signalling186.3.3disconnect terrestrial signalling196.3.4connect terrestrial traffic196.3.5disconnect ter

8、restrial traffic196.4transmission management procedures196.4.1connect multi-drop link196.4.2disconnect multi-drop link206.5air interface management procedures206.5.1set bts attributes206.5.2set radio carrier attributes206.5.3set channel attributes206.6test management procedures216.6.1perform test216

9、.6.2test report216.6.3send test report216.6.4stop test226.7state management and event report procedures226.7.1state changed event report226.7.2failure event report226.7.3stop sending event reports236.7.4restart sending event reports236.7.5change administrative state236.7.6change administrative state

10、 request236.7.7report outstanding alarms246.8equipment management procedures246.8.1change-over246.8.2opstart246.8.3reinitialize246.8.4set site outputs256.9measurement management procedures256.9.1measurement result request256.9.2measurement result response256.9.3stop measurement256.9.4start measureme

11、nt266.10miscellaneous procedures266.10.1get attributes266.10.2set alarm threshold266.10.3get attributes response267structured procedures268message details278.1message categories278.1.1formatted o&m messages278.1.2mmi transfer278.1.3trau o&m messages288.1.4manufacturer-defined o&m message

12、s288.2structure of formatted o&m messages298.3sw download management messages308.3.1load data initiate308.3.2load data segment308.3.3load data abort308.3.4load data end308.3.5sw activate request318.3.6activate sw318.3.7sw activated report318.4abis interface management messages318.4.1establish te

13、i318.4.2connect terrestrial signalling318.4.3disconnect terrestrial signalling328.4.4connect terrestrial traffic328.4.5disconnect terrestrial traffic328.5transmission management messages328.5.1connect multi-drop link328.5.2disconnect multi-drop link338.6air interface management messages338.6.1set bt

14、s attributes338.6.2set radio carrier attributes348.6.3set channel attributes348.7test management messages348.7.1perform test348.7.2test report358.7.3send test report358.7.4stop test358.8state management and event report messages358.8.1state changed event report358.8.2failure event report368.8.3stop

15、sending event reports368.8.4restart sending event reports378.8.5change administrative state378.8.6change administrative state request378.8.7report outstanding alarms378.9equipment management messages388.9.1changeover388.9.2opstart388.9.3reinitialize388.9.4set site outputs388.9.5change hw configurati

16、on398.10measurement management messages398.10.1measurement result request398.10.2measurement result response398.10.3start measurement398.10.4stop measurement398.11miscellaneous messages408.11.1get attributes408.11.2set alarm threshold408.11.3get attribute response409coding409.1message type419.2objec

17、t class449.3object instance449.4attributes and parameters459.4.1abis channel479.4.2additional info489.4.3additional text489.4.4administrative state489.4.5arfcn list489.4.6autonomously report499.4.7availability status499.4.8bcch arfcn499.4.9bsic499.4.10bts air timer509.4.11ccch load indication period

18、509.4.12ccch load threshold509.4.13channel combination509.4.14connection failure criterion519.4.15destination519.4.16event type519.4.17file data529.4.18file id529.4.19file version529.4.20gsm time529.4.21hsn529.4.22hw configuration539.4.23hw description539.4.24intave parameter539.4.25interference lev

19、el boundaries549.4.26list of required attributes549.4.27maio549.4.28manufacturer dependent state549.4.29manufacturer dependent thresholds559.4.30manufacturer id559.4.31max timing advance559.4.32measurement result559.4.33measurement type559.4.34multi-drop bsc link569.4.35multi-drop next bts link569.4

20、.36nack causes569.4.37ny1589.4.38operational state589.4.39overload period589.4.40physical config589.4.41power class589.4.42power output thresholds599.4.43probable cause599.4.44rach busy threshold599.4.45rach load averaging slots609.4.46radio sub channel609.4.47rf max power reduction609.4.48site inpu

21、ts609.4.49site outputs619.4.50source619.4.51specific problems619.4.52starting time619.4.53t200629.4.54tei629.4.55test duration629.4.56test no629.4.57test report info639.4.58vswr thresholds639.4.59window size639.4.60tsc639.4.61sw configuration649.4.62sw description649.4.63perceived severity649.4.64ge

22、t attribute response info649.4.65outstanding alarm sequence659.4.66hw conf change info65annex a (informative):change history66forewordthis technical specification has been produced by the 3rd generation partnership project (3gpp).the contents of the present document are subject to continuing work wi

23、thin 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 date and an increase in version number as follows:version x.y.zwhere:xthe first digit:1presented to tsg for i

24、nformation;2presented to tsg for approval;3or greater indicates tsg approved document under change control.ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when editorial only changes have been incor

25、porated in the document.introduction(background)the use and general aspects of the abis interface are given in specification 3gpp ts 48.051. the split of telecommunications functions and management procedures between bsc and bts are defined in specification 3gpp ts 48.052. specification 3gpp ts 48.0

26、56 defines layer 2 of the signalling messages.the general aspects of nm are defined in specification gsm 12.00. qx interface and protocol stack are defined in specification gsm 12.01. gsm 12.06 provides the functional requirements supported by the present document. the nm procedures and messages to

27、support these operations over the abis interface are specified here. specification gsm 12.20 provides the information model as seen on the omc-bsc interface. interworking between this model and the nm messages and procedures provided here is specified in gsm 12.22.1scopethe present document addresse

28、s the network management messages and procedures across the a-bis interface, which is defined as qx in gsm. the information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities.there is a requirement for the a-bis interface to be op

29、en to allow interoperation between btss of different manufacturers working to the same bsc. the present document addresses this requirement from o&m point of view, which allows this interworking to take place. it shows the split of nm functions between bsc and bts. the procedures and coding of t

30、he messages are specified in detail. in practice, in addition to the present document it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality.it is essential for operation that a bsc can handle the functions used by all its btss. theref

31、ore, all items in the present document are considered mandatory unless otherwise indicated in the present document.2referencesthe following documents contain provisions which, through reference in this text, constitute provisions of the present document.· references are either specific (identif

32、ied by date of publication, edition number, version number, etc.) or nonspecific.· for a specific reference, subsequent 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-specifi

33、c reference implicitly refers to the latest version of that document in the same release as the present document.13gpp tr 21.905: "vocabulary for 3gpp specifications".23gpp ts 44.006: "mobile station - base stations system (ms - bss) interface data link (dl) layer specification".

34、33gpp ts 24.008: "mobile radio interface layer 3 specification; core network protocols; stage 3".43gpp ts 45.002: "multiplexing and multiple access on the radio path".53gpp ts 45.005: "radio transmission and reception".63gpp ts 45.008: "radio subsystem link control

35、".73gpp ts 48.051: "base station controller - base tranceiver station (bsc-bts) interface general aspects".83gpp ts 48.052: "base station controller - base tranceiver station (bsc-bts) interface - interface principles".93gpp ts 48.056: "bsc-bts layer 2 specification&quo

36、t;.103gpp ts 48.058: "base station controler - base transceiver station (bcs-bts) interface layer 3 specification".11gsm 12.00 (gsm phase 2): "objectives and structure of network management (nm)".12gsm 12.01 (gsm phase 2): "common aspects of gsm network management (nm)"

37、.13gsm 12.06 (gsm phase 2): "gsm network configuration management and administration".14gsm 12.20 (gsm phase 2): "base station system (bss) management information".15gsm 12.22 (gsm phase 2): "interworking of gsm network management (nm) procedures and messages at the base sta

38、tion controller (bsc)".16itu-t recommendation x.731: "information technology - open systems interconnection - systems management: state management function".3definitions and abbreviations3.1definitionsdefinitions of terms used within the present document may be found mostly in clause5

39、 in text context.3.2abbreviationsfor the purpose of the present document, the following abbreviations apply:asn.1(ccitt) abstract syntax notation onebscbase station controllerbssbase station systembtsbase transceiver stationcont.continuedhwhardwarelsbleast significant byteman. dep.manufacturer depen

40、dent (with upper and lower case adjusted as appropriate) mmimanmachine interfacemsbmost significant bytemscmobileservices switching centrenenetwork elementnmnetwork managemento&moperations and maintenanceomcoperations and maintenance centrerfradio frequencysapiservice access point indicatorswsof

41、twareteiterminal end-point identifiertmntelecommunications management networktsctraining sequence codefurther gsm related abbreviations may be found in 3gpp ts 21.905 1.4functional split between bsc and btsfunctional split of management functions between bsc and bts is shown in table 1.table 1/gsm 1

42、2.2: split of management functions between bsc and btsbscbtsfault managementbts test requestx-test execution-xtest analysisns-fault detection-xfault localizationx (note)xfault reportingxxlinktesting (req,ex,rpt)ns-fault detectionxxfault localizationxxfault reportingxxconfiguration managementhardware

43、control/monitorcontrolsoftwarecontrol/monitormonitorstatecontrol/monitorcontrol/monitorparameterscontrol/monitormonitorperformance managementcollectionxx (radio path only)reportingxx (radio path only)administrationx-security management (access control to bts) bts)control-xmonitoring-xnote:when fault

44、 localisation is not possible at the bts it must be deduced at the bsc.legend:abbreviations:ns= not specified;req = request;x= function exists;ex = execution-= function non-exists;rpt= report5information model5.1managed objectsthe bcf mentioned in 3gpp ts 48.052 and 3gpp ts 48.056 is the agent at th

45、e bts end of the a-bis o&m interface. it has four different descriptions depending on the object that is managed: site manager, bts, radio carrier and baseband transceiver.this model describes how objects are managed across a-bis interface, but it doesn't specify how information is transferr

46、ed inside the site. that is, the manner of communication between an object and objects under it is not specified in the present document.as shown in figure 1, the object classes used on the a-bis interface are a subset of those found under site manager on the omc-bsc interface. the object classes ar

47、e listed below and the functionalities that describe them are found in table 2.site manager: manages common control functions of several btss and transceivers on one site. these can include managing external alarms, front-end switch, etc. this model describes logical sites. there can be multiple log

48、ical sites in one physical site. communication between entities within a logical site is manufacturer dependent.bts: is associated with one cell. btss are typically created at installation phase by connecting transceivers to antennas thus forming cells from the air interface point of view. the bts c

49、an also contain control functions common to various transceivers. the way btss are formed from transceivers and how corresponding bts numbers are determined is configuration dependent information, which is stored during installation.radio carrier: represents manageable properties pertaining to radio

50、 transmission and reception of one carrier.baseband transceiver: represents functions common to eight radio time slots.channel: is a physical channel in air interface, which can contain several logical channels depending on channel combination. a channel is described with radio time slot and frequen

51、cy hopping attributes (see 3gpp ts 45.002).note:site manager and bts don't necessarily require separate equipment. for example, the site manager and a baseband transceiver can be associated with the same physical equipment.figure 1/gsm 12.21: object model seen across a-bis interfacetable 2/gsm 1

52、2.21: objects, attributes and procedures seen across a-bis interfaceobject classattributesproceduressitemanagerabis channelavailability statushw configurationmanufacturer dependent statemanufacturer idoperational statesite inputssite outputssw configurationequipment managementestablish teiget attrib

53、utesmeasurement managementset site outputsstate management and event reportsw download managementtest managementbtsadministrative stateavailability statusbcch arfcnbsicbts air timerccch load ind. periodccch load thresholdconnection failure criteriongsm timehw configurationintave parameterinterterfer

54、ence level boundariesmanufacturer dependent statemax timing advanceny1operational stateoverload periodrach busy thresholdrach load averaging slotssw configurationt200equipment managementget attributesmeasurement managementreport proceduresset bts attributesstate management and event reportsw downloa

55、d managementtest managementradio carrieradministrative statearfcn listavailability statushw configurationmanufacturer dependent statemanufacturer idoperational statepower classrf max power reductionsw configurationequipment managementget attributesmeasurement management set radiocarrier attributesstate management and event reportsw download managementtest managementbasebandtransceiverabis channel*administrative stateavailability statushw configurationmanufacturer dependent statemanufact