hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.7 Availability Status
|
Attribute Identifier 1 Length 2-3 Availability Status 4 (cont.) (cont.) N Availability Status may contain one or more octets. Each octet shall have a single status value, which shall be coded as follows: In test 0 Failed 1 Power off 2 Off line 3 <not used> 4 Dependency 5 ETSI 49 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Degraded 6 Not installed 7
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.8 BCCH ARFCN
|
Attribute Identifier 1 BCCH ARFCN (MSB) 2 BCCH ARFCN (LSB) 3 BCCH ARFCN (see GSM 05.05) <1-3FF>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.9 BSIC
|
Attribute Identifier 1 BSIC 2 BSIC (see GSM 03.03) <0-3F> (BS colour code: bit 0-2) (PLMN colour code: bit 3-5)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.10 BTS Air Timer
|
Attribute Identifier 1 T3105 2 T3105 shall be coded as a binary presentation of 10 ms in the range of <0-FF>.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.11 CCCH Load Indication Period
|
Attribute Identifier 1 CCCH Load Indication Period 2 CCCH Load Indication Period shall be coded as a binary presentation of seconds in the range of <0-FF>.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.12 CCCH Load Threshold
|
Attribute Identifier 1 CCCH Load Threshold 2 CCCH Load Threshold shall be coded as a binary presentation of maximum (maximum is manufacturer dependent) percentage in the range of <0-64>.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.13 Channel Combination
|
Attribute Identifier 1 Channel Combination 2 Channel Combination shall be coded as follows: tCHFull TCH/F + FACCH/F + SACCH/TF 00 tCHHalf TCH/H(0,1) + FACCH/H(0,1) + SACCH/TH(0,1) 01 ETSI 50 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) tCHHalf2 TCH/H(0) + FACCH/H(0) + SACCH/TH(0) + TCH/H(1) 02 sDCCH SDCCH/8 + SACCH/C8 03 mainBCCH FCCH + SCH + BCCH + CCCH 04 bCCHCombined FCCH + SCH + BCCH + CCCH + SDCCH/4 + SACCH/C4 05 bCH BCCH + CCCH 06 bCCHwithCBCH combination of 05 with CBCH as GSM 05.02 07 1) sDCCHwithCBCH combination of 03 with CBCH as GSM 05.02 08 1) NOTE: These two channel combinations are created by replacing the SDCCH number 2 in channel combination 05 and channel combination 03 by the logical channel. See GSM 05.02 for meaning and usage of channel combinations.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.14 Connection Failure Criterion
|
Attribute Identifier 1 Length 2-3 Connection Failure Criterion 4 Criteria Value 5 (cont.) (cont.) N Connection Failure Criterion shall be coded as follows: Based upon uplink SACCH error rate (RADIO_LINK_TIMEOUT) 01 Based upon RXLEV/RXQUAL measurements 02 If connection failure criterion is based on SACCH error rate, the Criteria Value shall be one octet binary presentation of the number of SACCH multiframes used in the procedure. If connection failure criterion is based on RXLEV/RXQUAL measurements, coding of the Criteria Value field will be operator/manufacturer dependent. See GSM 05.08 subclauses 5.2 and 5.3 and GSM 04.08 subclause 3.5.2.2.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.15 Destination
|
Attribute Identifier 1 Length 2-3 Destination 4 (cont.) (cont.) N Destination identifies a unit of equipment that shall be the destination to be "changed to" on a Change-over operation. How to identify a type of equipment and how to identify a specific unit of this type is manufacturer dependent.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.16 Event Type
|
Attribute Identifier 1 Event Type 2 ETSI 51 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Event Type shall be coded as follows: communication failure 00 quality of service failure 01 processing failure 02 equipment failure 03 environment failure 04 <reserved for future use> <05-0F> <man.dep.> <10-FF>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.17 File Data
|
Attribute Identifier 1 Length 2-3 File Data <man.dep.> 4 (cont.) (cont.) N File Data is manufacturer dependent, but must be consistent with the associated GSM 12.20 attribute.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.18 File Id
|
Attribute Identifier 1 Length 2-3 File Id <man.dep.> 4 (cont.) (cont.) N File Id is manufacturer dependent, but must be consistent with the associated GSM 12.20 attribute.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.19 File Version
|
Attribute Identifier 1 Length 2-3 File Version <man.dep.> 4 (cont.) (cont.) N File Version is manufacturer dependent, but must be consistent with the associated GSM 12.20 attribute.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.20 GSM Time
|
Attribute Identifier 1 Current Frame No (MSB) 2 Current Frame No (LSB) 3 Current Frame No shall be a binary presentation of FN in Modulus 42432. ETSI 52 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.21 HSN
|
Attribute Identifier 1 HSN 2 HSN (see GSM 05.02) <0-3F>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.22 HW Configuration
|
Attribute Identifier 1 Length 2-3 HW Description 1 4 ... HW Description n N HW Configuration shall consist of a list of HW Descriptions related to a managed object.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.23 HW Description
|
Attribute Identifier 1 Equipment Id Length 2-3 Equipment Id (cont.) Equipment Type Length Equipment Type (cont.) Equipment Version Length Equipment Version (cont.) Location Length Location (cont.) Man. Dep. Info Length Man. Dep. Info (cont.) N All fields are manufacturer dependent variable length character strings. They must be consistent with associated GSM 12.20 attributes. Equipment Id distinguishes a piece of equipment out of others of same type. Equipment Type codes the type of piece of equipment (e.g., Baseband Transceiver Unit). Equipment Version codes the version of the piece of equipment. Location codes the place where the piece of equipment is found (e.g., row -rack - shelf - slot). Man. Dep. Info shall codes additional manufacturer dependent information.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.24 Intave Parameter
|
Attribute Identifier 1 Intave Parameter 2 Intave Parameter (see GSM 05.08) <1-1F> ETSI 53 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.25 Interference level Boundaries
|
Attribute Identifier 1 Interf Boundary 0 2 Interf Boundary 1 3 Interf Boundary 2 4 Interf Boundary 3 5 Interf Boundary 4 6 Interf Boundary 5 7 Interf Boundary 0 <0-FF> Interf Boundary X1 <0-FF> Interf Boundary X2 <0-FF> Interf Boundary X3 <0-FF> Interf Boundary X4 <0-FF> Interf Boundary X5 <0-FF> All boundaries shall be coded as a binary presentation of -x dBm (normal values are -115 to -85). For example, an interference boundary of -105 dBm will be represented as integer “105”.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.26 List of Required Attributes
|
Attribute Identifier 1 Length 2-3 Attribute Id 4 (cont.) (cont.) N Each Attribute Id is one octet.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.27 MAIO
|
Attribute Identifier 1 MAIO 2 MAIO (see GSM 05.02) <0-3F>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.28 Manufacturer Dependent State
|
Attribute Identifier 1 Manufacturer Dependent State 2 Manufacturer Dependent State <0-FF> This is optional to be used in addition to Operational State in accordance with GSM 12.20. ETSI 54 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.29 Manufacturer Dependent Thresholds
|
Attribute Identifier 1 Length 2-3 Manufacturer Dependent Thresholds 4 (cont.) (cont.) N The content of Manufacturer Dependent Thresholds is manufacturer dependent.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.30 Manufacturer Id
|
Attribute Identifier 1 Length 2-3 Manufacturer Id 4 (cont.) (cont.) N The content of Manufacturer Id is manufacturer dependent.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.31 Max Timing Advance
|
Attribute Identifier 1 Max Timing Advance 2 Max Timing Advance (see GSM 08.58) <0-7F>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.32 Measurement Result
|
Attribute Identifier 1 Length of measurement result (N) 2-3 Result (MSB) 4 (cont.) Result (LSB) N+3
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.33 Measurement Type
|
Attribute Identifier 1 Measurement Number 2 Measurement Number shall be coded as follows: <reserved> <00-3F> <man.dep.> <40-FF>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.34 Multi-drop BSC Link
|
Attribute Identifier 1 BTS Port Number 2 Timeslot Number 3 BTS Port Number <0-FF> Timeslot Number ETSI 55 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Time slot in 2 Mbps link <0-1F>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.35 Multi-drop next BTS Link
|
Attribute Identifier 1 BTS Port Number 2 Timeslot Number 3 BTS Port Number <0-FF> Timeslot Number Time slot in 2 Mbps link <0-1F>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.36 Nack Causes
|
Attribute Identifier 1 NACK Cause 2 Nack Causes shall be coded as follows: General Nack Causes: Incorrect message structure 01 Invalid message type value 02 <reserved> 03 <reserved> 04 Invalid Object class value 05 Object class not supported 06 BTS no. unknown 07 Baseband Transceiver no. unknown 08 Object Instance unknown 09 <reserved> <0A-0B> Invalid attribute identifier value 0C Attribute identifier not supported 0D Parameter value outside permitted range 0E Inconsistency in attribute list 0F 1) Specified implementation not supported 10 Message cannot be performed 11 2) <reserved> <12-18> Specific Nack Causes: Resource not implemented 19 Resource not available 1A Frequency not available 1B ETSI 56 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Test not supported 1C Capacity restrictions 1D Physical configuration cannot be performed 1E Test not initiated 1F Physical configuration cannot be restored 20 No such test 21 Test cannot be stopped 22 Message inconsistent with physical config. 23 3) Complete file not received 25 File not available at destination 26 File cannot be activated 27 Request not granted 28 Wait 29 Nothing reportable existing 2A Measurement not supported 2B Measurement not started 2C <reserved> <2D-7F> <man.dep.> <80-FE> NULL FF NOTE 1: This Nack cause shall apply to conflicting or incomplete data in the attribute list which prevents the BTS from performing the message. NOTE 2: This Nack cause shall apply when the message is valid and is supported by the BTS, but cannot be performed correctly for reasons not covered by other general or special Nack causes. NOTE 3: This Nack cause shall apply to the case where the data in attribute list is valid, but is beyond the capabilities of the particular BTS implementation.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.37 Ny1
|
Attribute Identifier 1 Ny1 2 Ny1 shall be a binary presentation of maximum number of repetitions of PHYSICAL INFORMATION (see GSM 04.08, subclause 3.4.4.2.2).
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.38 Operational State
|
Attribute Identifier 1 Operational State 2 ETSI 57 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Operational States are in accordance with GSM 12.20 and shall be coded as follows: Disabled 01 Enabled 02 <reserved for future use> <03-FE> NULL(Operat. state not supported) FF
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.39 Overload Period
|
Attribute Identifier 1 Length 2-3 Overload Period 4 (cont.) (cont.) N
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.40 Physical Config
|
Attribute Identifier 1 Length 2-3 Required Test Config <man.dep.> 4 (cont.) (cont.) N Required Test Config is manufacturer dependent.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.41 Power Class
|
Attribute Identifier 1 Power Class 2 Power Class is a binary presentation of transceiver power class as defined in GSM 05.05.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.42 Power Output Thresholds
|
Attribute Identifier 1 Output Power Fault Threshold 2 Reduced Output Power Threshold 3 Excessive Output Power Threshold 4 When the carrier output power of the transmitter, including power amplifier and transmitter combiner, is below or above a power level, a fault shall be generated. There are two thresholds below the output power to indicate two different levels of fault severity, and one for threshold above. The range of Output Power Fault Threshold and Reduced Output Power Threshold is from -10 to -1 dB . The values shall be coded in 1 dB steps such that -10 dB is expressed with 0 and -1 dB with 9. Output Power Threshold <00-09> Reduced Output Power Threshold <00-09> The range of Excessive Output Power Threshold is from 2 dB to 5 dB. The value shall be coded in 1 dB steps such that 2 dB is expressed with binary value 0 and 5 dB with binary value 3. Excessive Output Power Threshold <00-03> ETSI 58 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.43 Probable Cause
|
Attribute Identifier 1 Probable Cause Type 2 Probable Cause Value 3 Probable Cause Value (cont.) 4 Probable Cause Type shall be coded as follows: ISO/CCITT values (X.721) 01 GSM specific values 02 Manufacturer specific values 03 <reserved for future use> <04-FF> For Probable Cause Value coding, the last numeric value of the object identifier value specified in ASN.1 syntax coding shall be used if Probable Cause Type is either 01 or 02.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.44 RACH Busy Threshold
|
Attribute Identifier 1 RACH Busy Threshold 2 RACH Busy Threshold shall be a binary presentation of -x dBm in the range <0-FF>.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.45 RACH Load Averaging Slots
|
Attribute Identifier 1 RACH Load Averaging Slots (MSB) 2 RACH Load Averaging Slots (LSB) 3 RACH Load Averaging Slots shall be a binary presentation of number of RACH burst periods in the range <0-FFFF>.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.46 Radio Sub Channel
|
Attribute Identifier 1 Radio Sub Channel 2 Radio Sub Channel shall be coded as follows: Half rate channel 0 00 Half rate channel 1 01
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.47 RF Max Power Reduction
|
Attribute Identifier 1 RF Max Power Reduction 2 RF Max Power Reduction shall be a binary presentation of the number of 2 dB power reduction steps as defined in GSM 05.05. This represents "Pn" as used in GSM 08.58. ETSI 59 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.48 Site Inputs
|
Attribute Identifier 1 Length 2-3 Site Input 4 (cont.) (cont.) N If Site Inputs are requested from Site Manager with message Get Attributes, all inputs shall be listed. Each octet from 4 to N controls one Site input. Each of these octets contain the input number and the state of the input and they shall be coded as follows. 8 7 6 5 4 3 2 1 State Input number State shall be a binary presentation of the input state, 0 or 1. Input number shall be a binary presentation of input number. Note that maximally 128 binary inputs can be supported.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.49 Site Outputs
|
Attribute Identifier 1 Length 2-3 Site Output 4 (cont.) (cont.) N If Site Outputs are sent to Site Manager with message Set Site Outputs, the site outputs shall be generated as indicated by the message. Coding of this information element shall be the same as for Site Inputs. Note that maximally 128 binary site outputs can be supported.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.50 Source
|
Attribute Identifier 1 Length 2-3 Source 4 (cont.) (cont.) N Source identifies a unit of equipment that shall be "changed from" on a Change-over operation. How to identify a type of equipment and how to identify a specific unit of this type is manufacturer dependent.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.51 Specific Problems
|
Attribute Identifier 1 Specific Problems 2 Specific Problems <reserved for future use> <00-0F> <man.dep.> <10-FF> ETSI 60 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.52 Starting Time
|
Attribute Identifier 1 Current Frame No (MSB) 2 Current Frame No (LSB) 3 Current Frame No shall be a binary presentation FN Modulus 42432.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.53 T200
|
Attribute Identifier 1 SDCCH ( 5 ms) 2 FACCH/Full rate ( 5 ms) 3 FACCH/Half rate ( 5 ms) 4 SACCH with TCH SAPI0 (10 ms) 5 SACCH with SDCCH (10 ms) 6 SDCCH SAPI3 ( 5 ms) 7 SACCH with TCH SAPI3 (10 ms) 8 Each field shall be a binary presentation of time units mentioned in brackets. NULL (FF) means the value is not specified (see GSM 04.06).
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.54 TEI
|
Attribute Identifier 1 TEI 2 TEI (see GSM 08.56): Initial TEI <00-3F> Additional TEI <40-7E> <not used> <7F-FF>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.55 Test Duration
|
Attribute Identifier 1 Test Duration 2-3 Test Duration shall be a binary presentation of seconds in range <01-FFFF>indicating the time the test should last.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.56 Test No
|
Attribute Identifier 1 Test Number 2 Test Number shall be coded as follows: Radio loop test via antenna 00 Radio loop test via transceiver 01 BTS functional object self test 02 <reserved> <03-3F> ETSI 61 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) <man.dep.> <40-FF>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.57 Test Report Info
|
Attribute Identifier 1 Length 2-3 Test Result Info 4 (cont.) (cont.) N If the test was either radio loop test via antenna or radio loop test via transceiver, octets 3 and 4 are defined. Octet 3 shall include a binary presentation of RXLEV value in the range of 0-3F such that value 0 equals to -110 dBm or less and 3F equals to -48 dBm or more. Octet 4 shall express bit error rate (BER) of received bit stream in 0,1% steps in the range 0,0% - 12,8% such that 0 equals to 0,0% BER and 128(dec) equals to 12,8% BER or more. If the test was BTS functional object self test, octet 3 shall indicate pass or fail for the test of the functional object on the BTS by value 1 or 0 where 0 is the code for fail. In the defined test cases Test Result Info may also contain manufacturer dependent information in subsequent octets. In other tests, Test Result Info is manufacturer dependent.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.58 VSWR Thresholds
|
Attribute Identifier 1 Faulty Antenna Threshold 2 Antenna Not Adjusted Threshold 3 VSWR Thresholds shall be used in association with the "faulty receiver (transmitter) antenna" or "receiver (transmitter) antenna not adjusted" Probable Cause. The VSWR range for both thresholds is 1,2 - 3,0. The value shall be coded in 0,1 steps such that 1,2 is expressed with 0 and 3,0 with 12(hex). Faulty Antenna Threshold <00-12> Antenna Not Adjusted Threshold <00-12>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.59 Window Size
|
Attribute Identifier 1 Window Size 2 Window Size shall be a binary presentation of the number of layer 3 Load Data Segment messages to be sent before a layer 3 acknowledgment needs to be issued. Value 0 is not used.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.60 TSC
|
Attribute Identifier 1 Training Sequence Code 2 For details of Traing Sequence Codes, see GSM 05.02. TSC values <00-07> <not used> <08-FE> ETSI 62 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.61 SW Configuration
|
Attribute Identifier 1 Length 2-3 SW Description 1 4 ... SW Description n N SW Configuration shall contain a list of SW Descriptions related to the managed object.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.62 SW Description
|
Attribute Identifier 1 File Id 2 File Version N
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.63 Perceived Severity
|
Attribute Identifier 1 Severity Value 2 Severity Value shall be coded as follows: failure ceased 00 critical failure 01 major failure 02 minor failure 03 warning level failure 04 indeterminate failure 05 <reserved> <06-3F> <man, dep.> <40-FF>
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.64 Get Attribute Response Info
|
Attribute Identifier 1 Length 2-3 Count of not-reported attributes 4 (Each not-reported atttribute id) (cont.) (cont.) ...... (Each reported attribute id and its value) (cont.) (cont.) N ETSI 63 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) The BTS shall make a best effort to report on all the attributes requested by the associated Get Attributes message. The Length indicates the length of the entire Get Attribute Response Info which may possibly go over a single segment message and should not be confused with the length of the data put in one single message frame (see subclause 8.1.1). The Count of not reported attributes entry shall indicate the binary integer coded value of the count of the attributes requested but the BTS could not report on because the attributes are either not supported or not yet defined. In case of a non-zero value of the above counter, the Each not- reported attribute id entry shall list the Id of each attrute not reported and shall continue as many as indicated by the above counter. The Each reported attribute id and its value entry shall list each reported attribute id and its value pair coded and formatted for every applicable attribute or parameter as specified in this subclause (subclause 9.4) and shall continue until all reported attributes are included in the response.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.65 Outstanding Alarm Sequence
|
Attribute Identifier 1 Pending Reports 2 The integer coded Pending Reports field indicates the number of pending Failure Event Report messages to follow the current message as a response to the associated Report Outstanding Alarms message. This value being 0 signals that it is the last message for the outstanding alarms.
|
e59ea8dcad939b2b08179091ad5f515d
|
100 623
|
9.4.66 HW Conf Change Info
|
Attribute Identifier 1 Length 2-3 HW Description Position Index 1 4 Operation Code 1 5 Modification Data 1 (only if needed) ...... HW Description Position Index K Operation Code K Modification Data K (only if needed) N HW Description Position Index, Operation Code, and Modification Data constitute an associated tripplet for each HW Description change operation. The triplet may be repeated as many as needed. All the changes indicated in one Change HW Configuration message must be successfully conducted or the procedure must fail otherwise. The HW Description Position Index, an octet coded integer, indicates the HW Description’s position in the HW Configuration attribute to which the change operation indicated by the associated Operation Code must be applied. In case of multiple entries, all the position indices shall be interpreted against the initial HW Configuration sequence. There are three possible operations as listed below: deletion 00 insertion 01 modification 02 By a deletion operation, the indexed HW Description is deleted from the HW Configuration attribute. A deletion operation requires no associated Modification Data. An insertion or modification operation requires an associated Modification Data which specifies the new data for the operation. By a modification operation, the indexed HW Description in the HW Configuration attribute is replaced with the provided Modification Data. Deletion and modification operations are mutually exclusive at one position. By an insertion operation, the provided Modification Data is inserted immediately after the indexed HW Description in the HW Configuration attribute. An insertion at a position indexed zero (0) is interpreted as prepending to the very beginning. More than one insertion operation at one identically indexed position shall produce a HW Configuration sequence in which the inserted Descriptions are ordered the way as they appear in the HW Conf Change Info field. ETSI 64 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) History Document history V5.0.0 May 2000 Publication
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
1 Scope
|
The present document describes the requirements for the management of performance measurements and the collection of performance measurement data across a Public Land Mobile Network (PLMN). It defines the administration of measurement schedules, the generation of measurement results in the Network Elements (NEs) and the transfer of these results to the Operations System (OS). It also describes how the various requirements can be modelled as part of the generic PLMN information model. A set of measurements available for collection by NEs are described in annex B, effort has been made to ensure consistency in the definition of measurements between different NEs. The following is beyond the scope the present document: - how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user; - the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges. The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate. The objectives of the present documentisation are: to normalise the description of each measurement; and to produce a common description of the management technique for result accumulation and transmission across a management interface. The normalisation is intended to result in comparability of measurement data produced in a multi-vendor PLMN. As far as possible, existing standardisation in the area of performance management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised. Field of application The present document considers all aspects of performance management for a PLMN and its NEs defined in the GSM core Technical Specifications. However, only those aspects which are GSM specific and particular to PLMN operation are included in the present document. Other performance measurement aspects of described NEs and performance measurement aspects of NEs not described by the GSM core Technical Specifications are included for information purposes in annex E or may be found in referenced documents.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
1.1 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, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 02.16: "Digital cellular telecommunication system (Phase 2+); International Mobile station Equipment Identities (IMEI)". [2] GSM 04.08: "Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 specification". ETSI ETSI TS 100 615 V7.0.0 (2000-02) 20 (GSM 12.04 version 7.0.0 Release 1998) [3] GSM 04.11: "Digital cellular telecommunication system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [4] GSM 05.08: "Digital cellular telecommunication system (Phase 2+); Radio subsystem link control". [5] GSM 08.08: "Digital cellular telecommunication system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". [6] GSM 08.58: "Digital cellular telecommunication system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 3 specification". [7] GSM 09.02: "Digital cellular telecommunication system (Phase 2+); Mobile Application Part (MAP) specification". [8] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunication system (Phase 2); Objectives and structure of Network Management (NM)". [9] GSM 12.01 (ETS 300 612-2): "Digital cellular telecommunication system (Phase 2); Common aspects of GSM Network Management (NM)". [10] GSM 12.06 (ETS 300 617): "Digital cellular telecommunication system (Phase 2); GSM Network Configuration Management ". [11] GSM 12.30 (ETR 128): "Digital cellular telecommunication system (Phase 2); ETSI Object Identifier tree; Common domain; Mobile domain; Operation and Maintenance (O&M), managed object registration definition". [12] CCITT Recommendation E.880: "Field data collection and evaluation on the performance of equipment, network and services". [13] CCITT Recommendation X.710: "Common management information service definition for CCITT applications". [14] CCITT Recommendation X.721: "Information technology - Open Systems Interconnection - Structure of management information: Definition of management information". [15] CCITT Recommendation X.730: "Information technology - Open Systems Interconnection - Systems Management: Object management function". [16] CCITT Recommendation X.731: "Information technology - Open Systems Interconnection - Systems Management: State management function". [17] CCITT Recommendation X.734: "Information technology - Open Systems Interconnection - Systems Management: Event report management function". [18] CCITT Recommendation X.735: "Information technology - Open Systems Interconnection - Systems Management: Log control function". [19] CCITT Recommendation X.738: "Information technology - Open Systems Interconnection - Systems management: Summarization function". [20] CCITT Recommendation X.739: "Information technology - Open Systems Interconnection - Systems Management: Metric objects and attributes". [21] ISO 8571: "File Transfer, Access and Management". [22] GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 2". [23] GSM 04.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol". ETSI ETSI TS 100 615 V7.0.0 (2000-02) 21 (GSM 12.04 version 7.0.0 Release 1998) [24] GSM 04.64: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Logical Link Control (LLC)". [25] GSM 04.65: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Subnetwork Dependent Convergence Protocol (SNDCP)". [26] GSM 08.16: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Network Service". [27] GSM 09.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". [28] IETF RFC 959 File Transfer Protocol (FTP) [29] IETF RFC 783 Trivial File Transfer Protocol (TFTP) revision 2 [30] IETF RFC 1157 A Simple Network Management Protocol (SNMP) ETSI ETSI TS 100 615 V7.0.0 (2000-02) 22 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
1.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AGCH Access Grant Channel APN Access Point Name AuC Authentication Centre BSC Base Station Controller BSS Base Station System BSSAP BSS Application Part BTS Base Transceiver Station CBCH Cell Broadcast Channel CCCH Common Control Channel CCITT The International Telegraph and Telephone Consultative Committee CMIP Common Management Information Protocol CMIS Common Management Information Service CMISE Common Management Information Service Element DCCH Dedicated Control Channel DCN Data Communication Network EIR Equipment Identity Register ETSI European Telecommunications Standards Institute FACCH Fast Associated Control Channel FTAM File Transfer Access and Management FTP File Transfer Protocol GMSC Gateway Mobile Services Switching Centre GGSN Gateway GPRS Service Node GPRS General Packet Radio Service GSN GPRS Service Node HLR Home Location Register HO Handover HPLMN Home PLMN IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity ISDN Integrated Service Digital Network ISO International Standards Organisation LLC Logical Link Control LR Location Register MMI Man-Machine Interface MML Man-Machine Language MOC Managed Object Class MOI Managed Object Instance MS Mobile Station MSC Mobile Services Switching Centre MSRN Mobile Subscriber Roaming Number MTP Message Transfer Part NE Network Element NMC Network Management Centre NSS Network Sub System (including EIR, HLR, SMS-IWMSC, MSC and VLR) OACSU Off Air Call Set Up OA&M Operation, Administration and Maintenance OMAP (CCITT) Operations, Maintenance and Administration Part OMC Operations and Maintenance Centre OS Operations System OSI Open System Interconnection O&M Operations and Maintenance PCCCH Packet Common Control Channel PCCH Packet Paging Channel PCH Paging Channel PLMN Public Land Mobile Network (including BSS and NSS) PM Performance Management ETSI ETSI TS 100 615 V7.0.0 (2000-02) 23 (GSM 12.04 version 7.0.0 Release 1998) PTCH Packet Traffic Channel PVLR Previous VLR QOS Quality of Service RACH Random Access Channel Rec. Recommendation Ref. Reference RF Radio Frequency RR Radio Resource RXLEV Reception Level RXQUAL Reception Quality ROSE Remote Operation Service Element SACCH Slow Associated Control Channel SDCCH Stand alone Dedicated Control Channel SCCP (CCITT) Signalling Connection Control Part SGSN Serving GPRS Service Node SNDCP Sub Network Dependency Control Protocol SNMP Simple Network Management Protocol SMS-IWMSC Short Message Service Inter Working MSC Spec. Specification SS Supplementary Service TCAP (CCITT) Transaction Capabilities Application Part TCH Traffic Channel TMSI Temporary Mobile Subscriber Identity TMN Telecommunications Management Network TS Technical Specification VLR Visitors Location Register ETSI ETSI TS 100 615 V7.0.0 (2000-02) 24 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2 Performance measurement concept
|
Any evaluation of PLMN system behaviour will require performance data collected and recorded by its NEs according to a schedule established by the OS. This aspect of the management environment is termed Performance Management. The purpose of any performance management activity is to collect data which can be used to verify the physical and logical configuration of the PLMN and to localise potential problems as early as possible. The type of data to be collected is defined by the equivalent measurements, refer to annex B. The present document concentrates on the requirements of PLMN management to produce this data. Any management actions performed at the OS subsequently to analyse the performance data are not considered in the present document. Data is required to be produced by the NEs to support the following areas of performance evaluation: - traffic levels within the PLMN, including the level of both the user traffic and the signalling traffic; - verification of the network configuration; - resource access measurements; - Quality of Service (e.g. delays during call set-up); and - resource availability (e.g. the recording of begin and end times of service unavailability). The production of the measurement data by the NEs also needs to be administered by the OS. Several phases of administration of performance measurements can be distinguished: - the management of the performance measurement collection process; - the generation of performance measurement results; - the local storage of measurement results in the NE; - the transfer of measurement results from the NE to an OS; and - the storage, preparation and presentation of results to the operating personnel. It is not the task of the present document to describe the last phase mentioned above, viz. the preparation and presentation of the results to operating personnel: this is regarded as being specific to each PLMN Operator.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.1 Measurement data requirements
|
This subclause describes the typical requirements for performance data to be produced by the NEs which comprise a PLMN. It is important to note that an actual measurement value collected from the PLMN may be used to satisfy requirements in more than one category of measurement as described below. ETSI ETSI TS 100 615 V7.0.0 (2000-02) 25 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.1.1 Traffic measurements
|
Traffic measurements provide the data from which, among other uses, the planning and operation of the network can be carried out. The types of traffic evaluations for which PLMN specific measurements may be used include: - traffic load on the radio interface (signalling and user traffic); - usage of resources within the network nodes; - user activation and use of Supplementary services, etc. Examples of measured values may include: - Pages per Location area per hour; - Busy Hour Call Attempts per BSC, MSC; - Handovers per BSC per hour, etc.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.1.2 Network configuration evaluation
|
Once a network plan, or changes to a network plan, have been implemented it is important to be able to evaluate the effectiveness of the plan or planned changes. Typically, the measurements required to support this activity will indicate the traffic levels with particular relevance to the way the traffic uses the network.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.1.3 Resource access
|
For accurate evaluation of resource access, each count would need to be produced for regular time intervals across the network, or for a comparable part of the network.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.1.4 Quality Of Service (QOS)
|
The user of a PLMN views the provided service from outside the network. That perception can be described in observed QOS terms. QOS can indicate the PLMN performance expected to be experienced by the user, for further detail see CCITT Recommendation E.880 [12].
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.1.5 Resource availability
|
The availability performance is dependent on the defined objectives, i.e. the availability performance activities carried out during the different phases of the life cycle of the system, and on the physical and administrative conditions, for further detail see CCITT Recommendation E.880 [12].
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.2 Measurement administration
|
The range of measurements which will be available from the NEs are expected to cover all of the requirements described in subclause 2.1. However, not all of these measurements will be required all of the time, from every occurrence, of every relevant NE. With a highly distributed network like a PLMN it is also necessary to gather the measurement data so as to perform consistent analysis of the results and to evaluate the interactions between the NEs. This subclause describes the requirements for the various areas of administration of measurements.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.2.1 Measurement job administration
|
Measurement jobs, i.e. the processes which accumulate the data and assemble it for collection and/or inspection, will need to be scheduled for the period or periods for which gathering of data should be performed. ETSI ETSI TS 100 615 V7.0.0 (2000-02) 26 (GSM 12.04 version 7.0.0 Release 1998) The administration of measurement jobs comprise the following actions: 1) create/delete a measurement job; 2) modifying a measurement job; 3) definition of measurement job scheduling; 4) reporting and routing of results (to one or more OSs); 5) Suspend/Resume an active measurement job; 6) retrieval of information related to measurement jobs.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.2.2 Measurement result collection method
|
Each measurement job will be collecting result data at a particular frequency, known as the granularity of the measurement. The measurement data can be collected in each NE of the PLMN in a number of ways: - cumulative incremental counters triggered by the occurrence of the measured event; - status inspection (i.e. a mechanism for high frequency sampling of internal counters at pre-defined rates); - gauges (i.e. high tide mark, low tide mark); - discrete event registration, where data related to a particular event is captured. These are described in the following paragraphs. Cumulative counters: The NE maintains a running count of the event being counted. Status inspection: Network elements maintain internal counts for resource management purposes. These counts are read at a predetermined rate, the rate is usually based upon the expected rate of change of the count value. Gauges: Gauges represent dynamic variables that may change in either direction. Gauges can be integer or real valued. Discrete Event Registration: This is a measurement of a specified event where every Nth event would be taken into account. The value of N is dependant on the frequency of occurrence of the event being measured.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.2.3 Local storage of results at the Network Element
|
It shall be possible for the NE to retain measurement data it has produced until they are retrieved by the OS. This data will be retained at the NE as an explicit request from the OS. The storage capacity and the duration for which the data will be retained at the NE will be PLMN Operator and implementation dependent.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.2.4 Measurement result transfer
|
The results of the measurement job can be forwarded to the OS when available or be stored in the NE and retrieved by the OS when required. Additionally, the measurement result can be retrieved from the NE by the OS on request, this will return the current value of the measurement job with any other related information, but will not affect the scheduled execution of this or any other measurement jobs actively reporting that same data item. In a network with more than one OS, the data produced may also be required by other OSs, it is, therefore, necessary to support the possibility for multiple destinations for transfer of data.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.2.5 Performance data presentation
|
The performance data presentation is considered to be a PLMN Operator concern. ETSI ETSI TS 100 615 V7.0.0 (2000-02) 27 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.3 Measurement definition
|
This subclause looks at the requirements for the definition of the individual measurements.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.3.1 Nature of the result
|
The measurements defined for the PLMN have to be collected in the NEs. As each NE has its own role to play in the provision of the mobile telephony service then each will have a different perspective on the performance of the network. The measurement definitions shall, therefore, contain a description of the intended result of the measurement in terms of what is being measured.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.3.2 Perceived accuracy
|
The accuracy of measurements can be seen in three ways: - whether the result produced represents all occurrences of the defined event; - whether related measurements produced for the same period refer to the same events; or, - whether a measurement result refers to the whole or part of a granularity period. Representation of all occurrences: The definition of a measurement needs to accurately reflect which types of events are to be included in the collection of the data. If a general event description can be characterised by several Sub-types then the measurement definition will have to be precise as to which Sub-types are included or specifically excluded from that measurement. Same period for the same two event: Consider two events being counted which refer to the same allocation attempt, falling on either side of a granularity period boundary. i.e. the attempt is counted in one period while the termination with a successful cause is counted in the subsequent period. This will lead to discrepancies appearing in the actual figures when trying to compare attempts and successes for the same period. The discrepancy may be statistically insignificant if the expected use of the procedure is high. If the expected use is low then it may prove more acceptable to count the procedure termination by causes, e.g. successful termination, unsuccessful termination for all reasons. (If the definition of a measurement refers to specific unsuccessful termination causes then care should be taken to assess whether all causes are included - the sum of which can provide the total number of unsuccessful termination's - or whether the total is defined as well as the specific causes). Measurement collection periods: A typical measurement collection period can be interrupted by system events. These interruptions can be one or more of the following: - failure of the resource; - failure of procedure being measured; - resource only becomes available after the measurement period has commenced; - procedure only becomes available after the measurement period has commenced. In these cases the measurement result should highlight such interruptions to indicate that the result is suspect. Any actions to be taken subsequently with regards to the usefulness of the data will depend on the circumstances and the requirements of individual PLMN Operators. ETSI ETSI TS 100 615 V7.0.0 (2000-02) 28 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.3.3 Comparability of measurement data
|
In a multi-vendor network it can be important to know that measurement data produced by a NE from one supplier is equivalent to the measurement data being produced by the equivalent NE from a another supplier. This is particularly important when analysing data across the whole Network. The measurement definitions (in annex B), while not being explicit about precisely where a measurement should be performed, shall use a common understanding of the events being measured so as to produce comparable results.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
2.3.4 Measurement identification
|
In complex Networks it is easy to generate large amounts of performance data. It is essential that all data is recognisable in respect of each request made. As all the required information which can distinguish each request already exists (part of the request), it makes sense to use this information, rather than create anything new.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3 Performance management requirements
| |
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.1 Introduction
|
This subclause describes all basic functions to allow the system operator to collect measurement data from the NEs and to forward the results to the OS. All functions are gathered to provide the system operator with the means to administer, plan, execute measurements and to store and evaluate the measurement results.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.1.1 Basic functions
|
The performance management concept as applicable in this specification is outlined in figure 1 and is based on the general framework for PLMN management as outlined in GSM 12.00 [8] and GSM 12.01 [9]. OS NE NE NE NE DCN Measurement result presentation Measurement result transfer Measurement data collection Figure 1: Performance management concept The basic requirement from an NE for measurements is to collect data according to the definition of the measurements and to return results to the OS. The OS shall be able to administer the measurements and to receive and store the collected data. The measurements that will generate this data are defined in annex B. This data may be used in its original form or processed according to the system operator requirements. The data collected in the NE will be made available according to measurement parameters (scheduled reports), or on request from the OS (request current results). ETSI ETSI TS 100 615 V7.0.0 (2000-02) 29 (GSM 12.04 version 7.0.0 Release 1998) Using OSI standardised mechanisms, the OS can control: - the transfer of scheduled reports from the NE to the OS; - the storage of scheduled reports in the NE; and - deferred retrieval of scheduled reports stored in the NE. The present document does not address the latter aspects in full detail, as general and generic functions apply. It does, however, describe the use of these functions in the PLMN measurement system. As mentioned in subclause 2.2.5, measurement result presentation is considered to be a PLMN Operator concern. It is therefore not a subject of the present document. The format of the returned measurement results from OS point of view, however, will be ASN.1 using basic encoding rules.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.1.2 Measurement administration
|
(Performance) measurement administration functions allow the system operator to determine measurement data collection and forwarding to an OS. A (performance) measurement concept covers: 1) measurement data collection requirements: - Measurement types. Corresponds to the measurements as defined in annex B; - Measured network resources. The resource(s) to which the measurement types shall be applied have to be specified, e.g. one or more BTS(s); - Measurement recording, consisting of periods of time at which the NE is collecting (that is, making available in the NE) measurement data. 2) measurement reporting requirements: - the measurement related information to be reported and the layout of this report have to be specified as part of the measurement. The frequency at which scheduled result reports shall be generated has to be defined. 3) measurement result transfer requirements: - measurement results can be transferred from the NE to the OS according to the measurement parameters, and/or they are stored in the NE and can be retrieved by the OS when required. Current measurement results can be transferred from the NE to the OS on explicit OS request. A (performance) measurement job, covers the measurement data collection and measurement reporting requirements, as described in points 1 and 2 above. A measurement job can be created, modified, displayed or deleted in the OS. In addition, measurement job activities can be suspended and resumed, and, if the measurement job is not suspended, the current values of the measurements that are included in the measurement job can be requested by the OS at any time, independent of the measurement parameters. The system operator shall specify the required measurement parameters on initiation of a measurement job. These parameters consist of, among others, recording schedule, granularity, and measurement type(s).
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2 Measurement jobs
|
When defining a measurement job, the following aspects have to be considered: ETSI ETSI TS 100 615 V7.0.0 (2000-02) 30 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.1 Measurement job characteristics
| |
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.1.1 Measurement types
|
Every measurement job consists of one or more measurement types (defined in annex B), for which it collects measurement data. The measurement type(s) contained in a job may apply to one or more network resources of the same type, e.g. a measurement job may be related to one or several BTSs. A measurement job will only produce results for the measurement type(s) it contains.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.1.2 Measurement schedule
|
The measurement schedule specifies the time frame during which the measurement job will be active. The measurement job is active as soon as the starttime - if supplied in the schedule - is reached. The system shall support a job starttime of up to at least 90 days from the job creation date. If no starttime is provided, the measurement job shall become active immediately. The measurement job remains active until the stoptime - if supplied in the schedule - is reached. If no job stoptime is specified the measurement job will run indefinitely and can only be stopped by manual intervention. The time frame defined by the measurement schedule may contain one or more recording intervals. These recording intervals may repeat on a daily and/or weekly basis and specify the time periods during which the measurement data is collected within the NE. A recording interval is identified by an interval starttime and an interval endtime which lie between 00.00 and 24.00 hours, aligned on granularity period boundaries. Thus the length of a recording interval will be a multiple of the granularity period (if non-zero). For a single measurement type it shall be possible to specify several measurement jobs with different recording intervals as long as these intervals do not overlap. If it is required that a measurement type be observed by multiple measurement jobs with overlapping schedules than the system shall support multiple instances of that measurement type.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.1.3 Granularity period
|
The granularity period is the time between the initiation of two successive gatherings of measurement data. Required values for the granularity period are 5 minutes, 15 minutes, 30 minutes, 1 hour. The minimum granularity period is 5 minutes in most cases, but for some measurements it may only make sense to collect data in a larger granularity period. The granularity period shall be synchronised on the full hour and its value is not required to be changeable during the lifetime of the job. If the specified granularity period is zero then the measurement data can only be gathered on request from the OS.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.1.4 Measurement reporting
|
Scheduled measurement reports are produced at the end of each granularity period. All reports generated by a particular measurement job have the same layout and contain the information requested by the system operator. This information may consist of: - an identification of the measurement job that generated the report; - an identification of the involved measurement type(s) and the measured network resource(s) (e.g. BTS); - a time stamp, referring to the end of the granularity period; - for each measurement type, the result value and an indication of the validity of the result value; - an indication that the scan is not complete, and the reason why the scan could not be completed. Whatever method of data compression is selected, the returned measurement result shall not be compromised, i.e. it shall not result in loss of any necessary information. Some flexibility is provided in order to limit the information that is to be reported by the NE, reducing the amount of data to be transferred between NE and OS. Options that can be selected are: - suppressing the reporting of the identification of the observed network resource; - reporting the measurement results in an agreed order, so an explicit identification of the associated measurement type is not required in the measurement reports; ETSI ETSI TS 100 615 V7.0.0 (2000-02) 31 (GSM 12.04 version 7.0.0 Release 1998) - suppressing multiple reporting of measurement results when they are the same across all observed network resources.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.2 Measurement job state and status attributes
|
According to the OSI systems management concept, the state of a resource is reflected in indicators (attributes). Status attributes are provided to qualify these state attributes. Full details are provided in CCITT Recommendation X.731 [16]. As for a measurement job, the following information is provided: Administrative state: The administrative state attribute allows the system operator to permit or prohibit administratively the execution of the measurement job. Operational state: The operational state attribute reflects the operability of the measurement job. Availability status: The availability status attribute denotes particular conditions applicable to the measurement job. It indicates: - whether or not the measurement job is collecting measurement data according to its schedule; - if, for whatever reason, some of the requested measurement data cannot be collected by the measurement job, in particular whether the measurement schedule inhibits the collection of measurement data.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.2.3 Measurement job administration
|
Creating a measurement job: On creation of a measurement job, all information has to be supplied in order to collect the required data from the selected network resources as specified by the measurement job characteristics (see subclause 3.2.1). Modifying a measurement job: In general, the modification of measurement job parameters may be requested by the OS during the lifetime of a measurement job when the job is suspended (explained below). Displaying a measurement job: The system operator shall be able to get a list of all measurements that are currently defined, together with all available actual information as stored in the NE. This information consists of the data that is supplied on creation/modification and the actual state and status information of the measurement job. Deleting a measurement job: A measurement job is automatically deleted by the system when it reaches the job endtime and all scheduled or explicitly requested measurement reports have been generated. A created measurement job can also be deleted by manual intervention at any time. When deleted, the measurement process associated with the job is stopped, and all allocated resources are freed. Suspending/resuming a measurement job: On normal operation, the measurement job collects measurement data within the NE according to the actual values of the measurement job parameters. However, the system operator may decide for some reason to discard temporarily the collection of measurement data (e.g. in case of system overload or congestion, measurement results not used, ...). The system operator therefore is able to suspend a defined measurement job at any time, using the Administrative State. This implies that the measurement job definition remains in the system, but that no measurement gathering activities are performed for this job. When the measurement job is resumed, measurement data collection is started again at the next granularity period within the measurement schedule. Requesting the current measurement result values of a measurement job: The system operator may for some reason be interested in the current values of the measurement results of a particular measurement job, independently of the scheduled data collection and subsequent reporting, e.g. for tracing the increment of some of the counters. To this aim, the system operator is able to request the actual values of the measurement results for the same network resources as defined in the measurement job. The current results are returned in the reply message for this request in a format which is identical to scheduled reports that are generated by the measurement job at the end of the granularity period. Any such request does not affect the measurement job, and may only be issued when the measurement job is active and not suspended, otherwise an error will be returned. ETSI ETSI TS 100 615 V7.0.0 (2000-02) 32 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.3 Measurement results
| |
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.3.1 Measurement result characteristics
|
Each measurement produces a result at the end of the granularity period or on request of the OS, see above. Annex B provides for each measurement type a description of the expected measurement result. Scheduled reports: Measurement results for all measurements of a particular measurement job are gathered in a single report at the end of the granularity period. The system operator may to some extent determine in what format the measurement results are to be reported, since reporting requirements can be included in the measurement job definition. The report may contain, in addition to the specific measurement results, fixed information that is global for all measurement results associated with that measurement job, such as an identification of the involved network resources and a time stamp referring to the time at which the NE started collecting the measurement results. Request current results: On receipt of the request, the appropriate result values are produced, and a reply to the request is generated. The measurement job specific information contained in the reply and its format is identical to scheduled reports.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
3.3.2 Transfer of measurement results
|
The measurement results are contained in scheduled reports and are generated by the measurement job according to the measurement job definition parameters, or they are sent to the OS as a result of a "request current results"-operation. Scheduled measurement reports: Are generated at the end of each granularity period if the measurement job is not suspended. They can be transferred to the OS in two ways: 1) immediate notifications: The reports are automatically forwarded to the OS at the end of the granularity period. 2) deferred retrieval: The reports are stored locally in the NE, where they can be retrieved when required. For each individual report, the transfer of measurement results in either one or both ways is to be established by the system operator. These requirements are covered completely by OSI standardised functions (Event Report Management Functions CCITT Recommendation X.734 [17], Log Control Functions CCITT Recommendation X.735 [18], CMIS, CCITT Recommendation X.710 [13], FTAM, ISO 8571 [21], SNMP Recommendation IETF RFC 1157 [24], FTP Recommendation IETF RFC 959 [28] ), Common Management Functions that are provided in GSM 12.00 [8] and the generic services that are provided in annex D of the present document. Request current results: Upon receipt of the request, the NE will generate an appropriate reply and send it immediately to the OS. There is no further control of the forwarding of the reply and no storage of the reply in the NE. 4 Detailed description of the measurement system for a PLMN
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
4.1 Introduction
|
Clause 3 of the present document describes the required functions for the administration of performance measurements and the retrieval of their results. For this purpose, the characteristics of measurement jobs and measurement results have been defined. This part of the ETS explains how these requirements can be met using standard OSI systems management functions or SNMP management operations and, where necessary, tailoring them for PLMN use. In the following, managed object classes and their properties (attributes, notifications, etc.) to be used on the object oriented interface between OS and NEs for the execution of performance management functions are specified. ETSI ETSI TS 100 615 V7.0.0 (2000-02) 33 (GSM 12.04 version 7.0.0 Release 1998)
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
4.1.1 Basic measurement system functions
|
Before measurement data from the NEs can be collected and the results be forwarded to the OS, the measurement jobs that generate the required data shall be activated in the system. In object oriented terms, this corresponds to the instantiation of managed objects which model the measurement process. In order to control the measurement process, appropriate attributes of these objects shall be defined and have to be set to the required/desired values, either when the objects are created or during the lifetime of the objects. The specific attributes and their values will determine the measurement schedule, the measured network resources, the measurement types and the generation of scheduled result reports as well as the layout of the reports. Scheduled results can be forwarded to the OS using a notification that is defined specifically for this purpose as a part of the measurement object class definitions. A dedicated action will be used for requesting current results of active measurements.
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
4.1.2 Measurement Object Administration
|
The management of objects in an open system is performed utilising the internationally standardised "Common Management Information Service Element" (CMISE CCITT Recommendation X.710 [13] or IETF RFC 1157 A Simple Network Management Protocol (SNMP) [30]). Managed objects for the execution of PLMN performance measurement functions can be instantiated and deleted using the M-CREATE and M-DELETE services or SNMP SET and GET operations. Reading and modifying attributes of these objects can be achieved employing the M-GET and M-SET services of CMISE or SET and GET operations of SNMP. The CMISE M-EVENT-REPORT service and SNMP TRAP is defined for the emission of notifications, while actions can be executed using the M-ACTION service. Specific notifications defined in the OSI object management function (see CCITT Recommendation X.730 [15]) are used to notify the OS of the creation and deletion of managed objects and of the change of attribute values. For the formal definition of the PLMN performance management object model, refer to annex C. The measurement job can be ideally modelled by the managed object class "simpleScanner" as defined in CCITT Recommendation X.738 [19]. The "simpleScanner" is derived from the "homogeneousScanner" object class (see CCITT Recommendation X.738 [19]), which in turn is a specialisation of the "scanner" class of managed objects (see CCITT Recommendation X.738 [19]). The "simpleScanner" object has attributes to determine: - the measurement types; - the measured network resources; - the recording periods; and - the reporting requirements; of the measurement job. The "simpleScanner" generates measurement result reports in the form of notifications, according to the attributes that prescribe the reporting requirements. The measurement transfer requirements are not modelled in the scanner objects, since generic and general services are used (see subclause 4.3.2 and annex D).
|
cdfbc793b22dba975ca2a8fa9f7f80c7
|
100 615
|
4.2 Modelling of measurement jobs
|
A measurement job is represented by a "simpleScanner" object. The following subclauses define how the measurement job characteristics are mapped onto the properties of the "simpleScanner" managed object class, and how the measurement types of a measurement job are modelled in the PLMN performance measurement system.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.