hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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. The... |
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 b... |
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 unkn... |
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 ... |
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 o... |
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 fol... |
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 ... |
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 specif... |
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 eq... |
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... |
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... |
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 alarm... |
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 tripple... |
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 th... |
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. • Fo... |
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... |
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 ve... |
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 V... |
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 th... |
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 netwo... |
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 necessar... |
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 meas... |
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 m... |
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,... |
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 r... |
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. Representat... |
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 a... |
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... |
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: Pe... |
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 n... |
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 ... |
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... |
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 dat... |
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... |
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: Administrativ... |
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 j... |
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 re... |
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 ... |
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 us... |
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... |
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... |
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. |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.1 Measurement job characteristics | |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.1.1 Measurement Function | Every measurement job collects measurement data from selected measurement types across one or more network resources of the same type. The selected measurement types shall be identical throughout all network resources observed by a measurement job. For each network resource, the related measurement types have been grou... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.1.2 Measurement schedule | The measurement schedule specifies the time frame during which the measurement job will be active. The schedule consist of a measurement start- and stoptime and one or more recording intervals which may repeat on a daily or weekly basis. The semantics of the scheduling parameters are described in subclause 3.2.1.2. ETS... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.1.3 Granularity period | The granularity period defines the periodicity of the generation of results by a measurement job within the timeframe specified in the scheduling attributes. The granularity period of a measurement job is determined by the value of the "granularityPeriod" attribute of the "simpleScanner". The present document requires,... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.1.4 Scan reports | At the end of each granularity period within the measurement schedule, the "simpleScanner" will emit a "scanReport" notification, defined in CCITT Recommendation X.738 [19], which contains the measurement results generated by the scanner at the end of that granularity period. The information in the notification shall c... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.2 Scanner state and status attributes | State and status indicators are defined for the measurement job in subclause 3.2.2 of the present document. These are modelled through appropriate attributes which reflect the state and status of the "simpleScanner" object. These attributes are: administrativeState, operationalState and availabilityStatus. administrati... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.2.3 Scanner administration | The generic CMISE services M-CREATE, M-DELETE, M-GET and M-SET or SNMP SET and GET, applied to a simpleScanner managed object instance respectively represent creation, deletion, display and modification of a measurement job. A CMISE M-ACTION primitive or SNMP SET with a specific action type for activating a scan report... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.3 Modelling of measurement results | Each measurement produces a result at the end of the granularity period or on request of the OS. Annex B provides for each measurement type a description of the expected measurement result. Annex C contains the formal definition of the attribute that represents the measurement type. |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.3.1 Characteristics of the result report | A scheduled result report is generated in the form of a "scanReport" notification. Current measurement results requested by the OS using the "activateScanReport" action will be supplied by the system in the reply to the request. All measurement attributes that are observed by a "simpleScanner" object are included in a ... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.3.2 Result report transfer control | Result reports from a "simpleScanner" object are either produced according to the measurement schedule (notification) or on receipt of an explicit request (action) from the OS. There are no mechanisms to control the forwarding of the reply to that request (action reply), or to store it in the NE. There are, however, fu... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.4 Conformance requirements | In the following subclause, conformance requirements for object classes, notifications and actions defined in CCITT Recommendation X.738 [19] are specified. In cases where requirements in the present document restrict options of CCITT Recommendation X.738 [19], like e.g. changeability of attribute values, the condition... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.4.1 Simple scanner | The following subclause lists the attributes and packages of the "simpleScanner", as defined in CCITT Recommendation X.738 [19], and those inherited from the "scanner" as defined in CCITT Recommendation X.738 [19]. It specifies which properties shall be supported to conform with the present document. MANDATORY PACKAGES... |
cdfbc793b22dba975ca2a8fa9f7f80c7 | 100 615 | 4.4.2 Scan report record | The "scanReportRecord" managed object class will be supported in the PLMN measurement system as defined in CCITT Recommendation X.738 [19] and CCITT Recommendation X.721 [14]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.