ETSI ETS 300 623-1996 Digital Cellular Telecommunication System (Phase 2) Network Management (NM) Procedures and Messages on the A-bis Interface (GSM 12 21 Version 4 5 3)《数字蜂窝通信系统(_1.pdf

1、ETSI ETS*300*b23 b 3400855 01314bL 374 = EUROPEAN w 1 ELECOMMUNICATION STANDARD ETS 300 623 June 1996 Source: ETSI TC-SMG Reference: DE/SMG-O61221 P ICs: 33.060.50 Key words: Digital cellular telecommunications system, Global System for Mobile Communications (GSM) GLOBAL SYSTEM FOR MOBILE COMMUNICAT

2、IONS Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages on the A-bis interface (GSM 12.21) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Off ice address: Route des Lucioles

3、 - Sophia Antipolis - Valbonne - FRANCE Tel.: +33 92 94 42 O0 - Fax: +33 93 65 47 16 Copyright Notification: No part may be reproduced except as authorized bywritten permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecornmunications Standards

4、Institute 1996. All rights reserved. ETSI ETS*300*623 96 3400855 OL3L462 200 9 Page 2 ETS 300 623: June 1996 (GSM 12.21 version 4.5.4) _ Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comment

5、s concerning its accuracy, please write to “ETSI Editing and Committee Support Dept.“ at the address shown on the title page. ETSI ETS*300*623 96 = 3400855 0131463 I147 Page 3 ETS 300 623: June 1996 (GSM 12.21 version 4.5.4) Contents Foreword . 7 Introduction 7 1 . 2 . 3 . 4 . 5 . 6 . Scope 9 Normat

6、ive References . 9 Definitions and Abbreviations 10 3.1. Definitions . 10 3.2. Abbreviations 10 Functional Split between BSC and BTS . 11 Information Model . 12 5.1 . Managed Objects 12 5.2. Addressing of Objects . 14 5.3. State Management of Objects 15 5.3.1. Administrative State 15 5.3.2. Operatio

7、nal State and Availability Status 16 Elementary Procedures . 18 6.1. 6.2. 6.3. 6.4. 6.5. 6.6. 6.7. Definition of the Procedures . 18 SW Download Management Procedures . 19 6.2.1. Load Data Initiate . 19 6.2.2. Load Data Segment . 19 6.2.3. Load Data Abort 19 6.2.4. Load Data End . 20 6.2.5. SW Activ

8、ate Request 20 6.2.6. Activate SW . 20 6.2.7. SW Activated Report 20 A-bis Interface Management Procedures 21 6.3.1. Establish TE1 . 21 6.3.2. Connect Terrestrial Signalling 21 6.3.3. Disconnect Terrestrial Signalling 21 6.3.4. Connect Terrestrial Traffic 22 6.3.5. Disconnect Terrestrial Traffic 22

9、Transmission Management Procedures . 22 6.4.1. Connect Multi-drop Link 22 6.4.2. Disconnect Multi-drop Link 22 6.5.1. Set BTS Attributes . 23 6.5.2. Set Radio Carrier Attributes 23 6.5.3. Set Channel Attributes 23 Test Management Procedures . 23 6.6.1. Perform Test . 23 6.6.2. Test Report . 24 6.6.3

10、. Send Test Report . 24 6.6.4. Stop Test 24 State Management and Event Report Procedures . 25 6.7.1. State Changed Event Report . 25 6.7.2. Failure Event Report . 25 6.7.3. Stop Sending Event Reports . 25 6.7.4. Restart Sending Event Reports . 26 Air Interface Management Procedures 23 ETSI ETS*300*b

11、23 96 m 3400855 OL3L4b4 083 m Page 4 ETC 300 623: June 1996 (GSM 12.21 version 4.5.4) 6.7.5. Change Administrative State 26 6.7.6. Change Administrative State Request 26 Equipment Management Procedures . 26 6.8.1. Change-over 26 6.8.2. Opstart 27 6.8.3. Reinitialize 27 6.8.4. Set Site Outputs . 27 6

12、.9. Miscellaneous Procedures . 28 6.9.1. Get Attributes 28 6.9.2. Set Alarm Threshold . 28 6.8. 7 . Structured Procedures . 29 8 . Message Details . 29 8.1 . Message Categories . 29 8.1 .i. Formatted O Abbreviations and acronyms“. GSM 04.06 (ETS 300 555): “Digital cellular telecommunication system (

13、Phase 2); Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification“. GSM 04.08 (ETS 300 557): “Digital cellular telecommunication system (Phase 2); Mobile radio interface layer 3 specification“. GSM 05.02 (ETS 300 574): “Digital cellular telecommunication system (

14、Phase 2); Multiplexing and multiple access on the radio path“. GSM 05.05 (ETS 300 577): “Digital cellular telecommunication system (Phase 2); Radio transmission and reception“. GSM 05.08 (ETS 300 578): “Digital cellular telecommunication system (Phase 2); Radio subsystem link control“. GSM 08.51 (ET

15、S 300 592): “Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) interface General aspects“. GSM 08.52 (ETS 300 593): “Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) i

16、nterface Interface principles“. GSM 08.56 (ETS 300 595): “Digital cellular telecommunication system (Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 2 specification“. GSM 08.58 (ETS 300 596): “Digital cellular telecommunication system (Phase2); Base Station C

17、ontroller - Base Transceiver Station (BSC - BTS) interface Layer 3 specification“. - ETSI ETS*300*b23 96 3400855 0131470 387 Page 10 ETS 300 623: June 1996 (GSM 12.21 version 4.5.4) i 31 i 41 GSM 12.00 (ETS 300 61 2-1): “Digital cellular telecommunication system (Phase 2); Objectives and structure o

18、f Network Management (NM)“. GSM 12.01 (ETS 300 612-2): “Digital cellular telecommunication system (Phase 2); Common aspects of GSM Network Management (NM)“. GSM 12.06 (ETS 300 61 7): “Digital cellular telecommunication system (Phase 2); GSM Network Configuration Management and Administration“. GSM 1

19、2.20 (ETS 300 622): “Digital cellular telecommunication system (Phase 2); Base Station System (BSS) Management Information“. GSM 12.22 (ETS 300 624): “Digital cellular telecommunication system (Phase 2); Interworking of GSM Network Management (NM) procedures and messages at the Base Station Controll

20、er (BSC)“. 3. Definitions and Abbreviations 3.1. Definitions Definitions of terms used within this ETS may be found mostly in clause5 in text context. 3.2. Abbreviations For the purpose of this ETS the following abbreviations apply. ASN.l BSC BSS BTS Hw LSB MMI MSB MSC NE NM O X = Function exists; =

21、 Function non-exists; Abbreviations: req = request; ex =execution rpt = report ETSI ETS*300*623 lb 3400855 O333472 L5T Page 12 ETS 300 623: June 1996 (GSM 12.21 version 4.5.4) 5. Information Model 5.1. Managed Objects The BCF mentioned in GSM 08.52 and GSM 08.56 is the agent at the BTS end of the A-

22、bis O SW Configuration -_._ _ - _ - _ Administrative State Availability Status BCCH ARFCN BSIC BTS Air Timer CCCH Load Ind. Period CCCH Load Threshold Connection Failure Criterion GSM Time HW Configuration Intave Parameter Interterference Level Boundaries Manufacturer Dependent State Max Timing Adva

23、nce NY1 Operational State !Overload Period I RACH Busy Threshold RACH Load Averaging Slots SW Configuration 11200 _ I Administrative State 1 Availability Status HW Configuration I Manufacturer Dependent State I Manufacturer Id I Operational State Power Class I RF Max Power Reduction ! SW Configurati

24、on Abis Channel* Administrative State Availability Status l HW Configuration Manufacturer Dependent State Manufacturer Id operational State I SW Configuration ARFCN List - ._ - .- - _ - _ - Equipment Management 1 Establish TE1 IGet Attributes !Set Site Outputs IState Management and Event Report /SW

25、Download Management ;Test Management Procedures Equipment Management IGet Attributes IRepori Procedures Set BTS Attributes l State Management and Event Report SW Download Management Test Management I - I Equipment Management iGet Attributes Set RadioCarrier Attributes State Management and Event Repo

26、rt SW Download Management 1 Test Management Connect Terrestrial Signalling , Disconnect Terrestrial Signalling I Equipment Management iGet Attributes /State Management and Event Report kW Download Management Test Management ETSI ETS*300*623 9b W 3400855 0333474 T22 Page 14 ETS 300 623: June 1996 (GS

27、M 12.21 version 4.5.4) Table ZGSM 12.21 (continued): Objects, attributes and procedures seen across A-bis interface - - , Object class Attributes Procedures 1 Channel I Abis Channel Connect Terrestrial Traffic I Administrative State Disconnect Terrestrial Traffic _ - _ _ - I ARFCN List I Availabilit

28、y Status iGet Attributes I Channel Combination 1 HW Configuration HSN* SW Download Management j MAIO* Test Management ,Operational State SW Configuration Equipment Management Set Channel Attributes State Management and Event Report I l I TSC l NOTE: If more than one layer 2 link is defined to handle

29、 this information model, the actual implementation may affect on which layer 2 link attributes concerning frequency hopping and front-end switch are sent. Equipment used to implement frequency hopping can be common to several radio carriers or located inside one radio carrier. Front-end switch is ha

30、ndled by Site Manager, therefore all Abis Channel attributes must be sent to it. Those attributes that need a link identifier in BSC data structures are marked with an asterisk (*). 5.2. Addressing of Objects It is a GSM requirement that the BSC is capable of operating with BTSs from different manuf

31、acturers. So, it is necessary that the differences between BTSs, as seen by the BSC, are minimised as much as possible. This is achieved by addressing NM messages by the Managed Object Class and Managed Object Instance. There must be in the BSC an object model with a complete layer 2 link descriptio

32、n for each object instance in the BTS (e.g., Baseband Transceiver 1, Baseband Transceiver 2, Baseband Transceiver 3, .). When a message has to be sent to an object instance this mapping is used to find the correct link. The first connection shall be established from the BTS site by using a (semi-) p

33、ermanently programmed default TEI. Subsequent to the establishment of the default connection to the site, further initial connections to other objects shall be established using TEls provided by procedures in Subclause 6.3.1. Possible additional TEls to an object already having an initial TE1 are as

34、signed with a GSM 12.21 message found in Subclause 6.3.1. through an already assigned signalling link. Object instances also have a layer 3 address. The instance number is used to address the object instance. Regardless of whether the layer 2 address uniquely identifies the object instance or not, t

35、he layer 3 address must also be provided so that it can be used by management agent to determine which object instance is being addressed. This combination of layer 2 and layer 3 addressing accommodates BTS sites with either single or multiple physical links. Specific equipment configuration informa

36、tion is manufacturer dependent. However, for interoperability, link configuration, default TE1 assignment and instance numbering must be known by both manager and agent. This, as well as supported functions, is considered as Shared Management Knowledge. ETSI ETS*300*623 76 3400855 0131475 969 Page 1

37、5 ETS 300 623: June 1996 (GSM 12.21 version 4.5.4) 5.3. State Management of Objects State management in this ETS is generally in line with CCITT X.731. How state values are applied is explained below. CCITT X.731 states that “the management state of a managed object represents the instantaneous cond

38、ition of availability and operability of the associated resources from the point of view of management.“ In this ETS there are two different factors (CCITT X.731 defines usage state in addition to these two) that are considered to affect the management state of a managed object. They are: - - Admini

39、stration: permission to use or prohibition against using the resource, imposed through the management services; Operability: whether or not the resource is physically installed and working. This ETS defines the following three state management attributes to represent the management state of a manage

40、d object: - Administrative state; - Operational state; - 5.3.1. Administrative State Availability status (this elaborates the operational state). Administrative states of the managed objects can be controlled only -y the BSC. In fact, the control of resource usage comes from the MSC). Setting the ad

41、ministrative state of a Channel to locked means that it has to discontinue all transmission and reception of information on Air interface and all telecommunication (traffic and signalling) information transmission on A-bis interface. Setting the administrative state of a Radio Carrier to locked mean

42、s that it has to discontinue all RF emission on Air interface for the frequencies it is responsible. Setting the administrative state of a Baseband Transceiver to locked means that it has to discontinue all telecommunication tramissions and the Channels which are affected should indicate that they a

43、re Disabled or Degraded. Setting the administrative state of a BTS to locked means it has to discontinue all RF emission on all Radio Carriers and all telecommunication transmissions on all Channels of all Baseband Transceivers, .e., Radio Carriers, Channels and Baseband Transceivers are in Disabled

44、, Dependency state. The administrative state at the BTS site is also used to provide information e.g., for a local MMI user at a BTS site. The locked state of a 12.21 managed object means that BSC has disconnected all the calls that go through the resource that is represented by the managed object.

45、No new traffic is connected through this resource any more. The shutting down state means that no new traffic is connected through this resource any more. The on-going calls remain. The unlocked state means that new traffic is allowed through the resource represented by the managed object. ETSI ETS*

46、300*b23 b m 3400855 OL3L47b 8T5 m Page 16 ETS 300 623: June 1996 (GSM 12.21 version 4.5.4) 5.3.2. Operational State and Availability Status CCIlT X.731 gives the following definitions for the values of the operational state attribute: - - disabled: the resource is totally inoperable and unable to pr

47、ovide service to the user(s); enabled: the resource is partially or fully operable and available for use. In this ETS the value Disabled represents the following conditions that the resources could have: - - power is turned off: - failure has occurred; - hardware or software is not installed: radio

48、parameters has not yet been set by elementary procedures, therefore, the resource is off line. The availability status elaborates the operational state attribute. In this ETS the following values are used (availability status is a set value): In test: The resource is undergoing a test procedure. Fai

49、led: The resource has an internal fault that prevents it from operating. The operational state is disabled. Power off: The resource requires power to be applied and is not powered on. The operational state is disabled. Off line: The resource requires some manual and/or automatic operation(s) to be performed to make it available for the use. Dependency: The resource cannot operate because some other resource on which it depends is unavailable. The operational state is disab