with zero.
+- d) Each measurement is an integer value.
+- e) RRC.IratIncMobility.LAI
+where LAI identifies the LAI of the RAT’s coverage the UE comes from.
+- f) EUTranCellFDD
+EUTranCellTDD
+- g) Valid for packet switched traffic
+- h) EPS
+
+## 4.10 RF Measurements
+
+### 4.10.1 CQI Distribution
+
+#### 4.10.1.0 General
+
+In CA, in case the CQI of SCell is reported to PCell via PUCCH, the CQI is counted to the reported SCell (but not to the PCell).
+
+#### 4.10.1.1 Wideband CQI distribution
+
+- a) This measurement provides the distribution of the Wideband CQI (Channel Quality Indicator) reported by UEs in the cell.
+- b) CC.
+- c) This measurement is obtained by incrementing the appropriate measurement bin when a wideband CQI value is reported by a UE in the cell. When spatial multiplexing is used, CQI for both code words should be considered.
+- d) A single integer value.
+- e) CARR.WBCQIDist.BinX
+where X represents the CQI value (0 to 15).
+- f) EUTranCellFDD
+EUTranCellTDD
+- g) Valid for packet switching.
+- h) EPS
+
+#### 4.10.1.2 Average sub-band CQI
+
+- a) This measurement provides the average value of the sub-band CQI (Channel Quality Indicator) reported by UEs in the cell.
+
+A subband is a set of k contiguous PRBs where k is a function of system bandwidth. Note the last subband in set S may have fewer than k contiguous PRBs depending on $N_{RB}^{DL}$ . The number of subbands for system bandwidth given by $N_{RB}^{DL}$ is defined by $N = \lceil N_{RB}^{DL} / k \rceil$ . The subbands shall be indexed in the order of increasing frequency and non-increasing sizes starting at the lowest frequency.
+
+- b) CC
+- c) This measurement is obtained by computing the average value of the sub-band CQI reported by UEs in the cell within the measurement granularity period. One value is produced for each sub-band. The number of sub-bands
+
+depends on the bandwidth used, as specified in [18]. When spatial multiplexing is used, CQI for both code words should be considered.
+
+- d) Float value.
+- e) CARR.AvgSubCQI.SubbandX
+where SubbandX represents the sub-band index, as specified in [18].
+- f) EUTranCellFDD
+EUTranCellTDD
+- g) Valid for packet switching.
+- h) EPS
+
+### 4.10.2 Timing Advance Distribution
+
+- a) This measurement provides the distribution of the Timing Advance ( $T_A$ ) values transmitted by the eNB to UEs in the cell.
+- b) CC.
+- c) This measurement is obtained by incrementing the appropriate measurement bin when a Timing Advance Command is sent to a UE in the cell. For Timing Advance Command see [16] clause 6.1.3.5.
+- d) A single integer value.
+- e) CARR.TADist.BinX
+where X represents the $T_A$ value (0 to 63).
+- f) EUTranCellFDD
+EUTranCellTDD
+- g) Valid for packet switching.
+- h) EPS
+
+# --- 5 Measurements related to Relay Node
+
+## 5.1 DeNB Reconfiguration related measurements
+
+### 5.1.1 RN Reconfiguration
+
+#### 5.1.1.1 Number of RNReconfiguration attempts
+
+- a) This measurement provides the number of RNReconfiguration attempts sent by DeNB.
+- b) CC
+- c) On transmission by the DeNB of a RNReconfiguration message to RN. Each RNReconfiguration message received is added to the relevant measurement. The message is included in 3GPP TS 36.331 [8].
+- d) Each measurement is an integer value.
+- e) The measurement name has the form RRC.RNReconAttNbr.
+- f) DeNBCapability
+- g) Valid for packet switched traffic
+- h) EPS
+
+#### 5.1.1.2 Number of RNReconfiguration Completed
+
+- a) This measurement provides the number of RNReconfiguration completed received by DeNB
+- b) CC
+- c) On receipt by the DeNB of a RNReconfigurationComplete message from RN. Each RNReconfigurationComplete message received is added to the relevant measurement. The message is included in 3GPP TS 36.331 [8].
+- d) Each measurement is an integer value.
+- e) The measurement name has the form RRC.RNReconCmptNbr
+- f) DeNBCapability
+- g) Valid for packet switched traffic
+- h) EPS
+
+# --- Annex A (informative): Use cases for performance measurements definition
+
+This annex provides the concrete use cases for the E-UTRAN performance measurements defined in clause 4.
+
+Without particular constraint, the following use cases defined for eNodeB apply to following scenarios
+
+- 1) eNodeB serving one or more Relay Nodes
+- 2) eNodeB without serving any Relay Node
+- 3) eNodeB or Relay Node supporting Carrier Aggregation
+- 4) eNodeB or Relay Node not supporting Carrier Aggregation
+
+If the specific constraint is present, which one of the above scenarios the subject use case applies to, is following the constraint.
+
+## --- A.1 Monitor of call(/session) setup performance
+
+Call(/session) setup is one of most important step to start delivering services by the networks to users.
+
+The success or failure of a call(/session) setup directly impacts the quality level for delivering the service by the networks, and also the feeling of the end user. So the success or failure of call(/session) setup needs be monitored, this can be achieved by the calculation of call setup success rate which gives a direct view to evaluate the call setup performance, and the analysis of the specific reason causing the failure to find out the problem and ascertain the solutions.
+
+In addition, the time duration of the call(/session) setup need to be monitored as it impacts the end user experience, and by comparison with operator's benchmark requirements, the optimization may be required according the performance.
+
+And due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each service type and OoS level.
+
+To complete the call(/session) setup procedure, E-UTRAN is mainly responsible for the establishment of radio and S1 signaling connection and service bearer by the RRC connection establishment (See 3GPP TS 36.331[8]), RRC connection reestablishment after RRC connection dropped due to some reasons like radio link failure or handover failure etc (See 3GPP TS 36.331[8]) E-RAB setup (See 3GPP TS 36.413[9]) and Initial UE Context Setup (See 3GPP TS 36.413[9]) procedure.
+
+To support the monitor of success or failure of the call(/session) setup, the performance measurements related to RRC connection establishment (See 3GPP TS 36.331[8]), RRC connection reestablishment (See 3GPP TS 36.331[8]) procedure, and the performance measurements related to E-RAB setup (See 3GPP TS 36.413[9]) and Initial UE Context Setup (See 3GPP TS 36.413[9]) procedure for each QoS level are required To support the monitor of time duration of setup call(/session) setup, the performance measurements related to RRC connection setup time and E-RAB setup time are required.
+
+## --- A.2 Monitor of E-RAB release
+
+E-RAB is the key and limited resource for E-UTRAN to deliver services. The release of the E-RAB needs to be monitored as:
+
+- an abnormal release of the E-RAB will cause the call(/session) drop, which directly impacts the QoS delivered by the networks, and the satisfaction degree of the end user;
+- a successfully released E-RAB can be used to setup other requested calls(/sessions). The E-RAB failed to be released will still occupy the limited resource and hence it can not be used to admit other requested calls(/sessions).
+
+From a retainability measurement aspect, E-RABs do not need to be released because they are inactive, they can be kept to give fast access when new data arrives.
+
+To define (from an E-RAB release measurement point of view) if an E-RAB is considered active or not, the E-RABs can be divided into two groups:
+
+- a. Continuous flow, E-RABs that are always considered active, i.e. independent of if there is ongoing traffic or not at the moment. Examples: VoIP sessions, Real-time sessions, Live streaming sessions.
+- b. Bursty flow, E-RABs that are only considered active when there is data in UL/DL buffer. Example: Web sessions.
+
+How to decide for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this document.
+
+The specific reason causing the abnormal and failed release of the E-RAB is required in order to find out the problem and ascertain the solutions. And due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each service type with OoS level.
+
+The E-RAB can be released by E-RAB Release procedure (See 3GPP TS 36.413[9]), UE Context Release procedure (See 3GPP TS 36.413[9] and 3GPP TS 36.423[10]) procedure, Reset procedure (See 3GPP TS 36.413[9]) either initiated by eNodeB or MM, Path Switch procedure (See 3GPP TS 36.413[9]) and Intra-eNB HO procedure (See 3GPP TS 36.331[8])E.
+
+So performance measurements related to E-RAB Release (See 3GPP TS 36.413[9]) and UE Context Release (See 3GPP TS 36.413[9]) procedure for each service type with QoS level are necessary to support the monitor of E-RAB release.
+
+## A.3 Monitor of E-RAB level QoS modification
+
+When an E-RAB has been established, the QoS it experiences in the E-UTRAN is dependent upon the E-RAB level QoS parameters established for the bearer, together with settings of other bearers established in the same cell. If the QoS experienced by a bearer does not meet the expected performance, or the resource need be reassigned for other bearers, the E-RAB level QoS may be adjusted (typically with a knock-on effect onto other bearers).
+
+So the modification of E-RAB level QoS parameters needs to be monitored, and due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each target service type with OoS level.
+
+The E-RAB level QoS can be modified by E-RAB Modify procedure (see 3GPP TS 36.413[9]), in which the MME entity instructs the eNodeB to change one or more QoS parameters on an E-RAB using the E-RAB MODIFY REQUEST message. The eNodeB typically makes the adjustments as instructed (and adjusts the RRM applied to the bearer appropriately) but in some circumstances the bearer modification can fail. The eNodeB returns an E-RAB MODIFY RESPONSE message that tells the MME whether the modification was successful or not – for an unsuccessful modification a cause value is included. It is important for OAM to measure the failure rate of the bearer modifications, this information can be used, for example, to make adjustments to OAM CM settings.
+
+## A.4 Overview handover related Use Cases
+
+| Use Case | PM KPI / elementary object |
+|----------|----------------------------|
+|----------|----------------------------|
+
+| | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Continuous Network Supervision: Supervision of overall handover performance. It is essential in network operations to follow the success rate of various handover. Low handover success rate will impact user experience, therefore it is important to define measurements to follow handover success rate.
| - - outgoing Intra RAT HO Success Rate (cell) *1
- - outgoing Inter RAT HO Success Rate (cell) *1
- - outgoing Inter System HO Success Rate (cell) *1 *3
- - outgoing Intra Frequency HO Success Rate (cell) *1
- - outgoing Inter Frequency HO Success Rate (cell) *1
- - outgoing Intra eNB/RN HO Success Rate (cell) *2 *2.1
- - outgoing Inter eNB HO Success Rate (cell) *2 *2.2
- - outgoing HO to the cells outside the RN
*1: It is expected that the HO success rate may vary depending on the respective scenarios : intra-RAT, inter-RAT, inter System, intra frequency, inter frequency
*2: it is expected that the HO success rate may vary depending on the used external interfaces
*2.1: For the intra-DeNB handover, the handover from a DeNB cell to an RN under the same DeNB shall be counted separately as the handover happens between E-UTRAN and RN.
*2.2: For the handover from the DeNB to another eNB/DeNB, the forwarded handovers for RN in the source DeNB shall not be counted as these handovers are controlled by RN so cannot directly reflect DeNB handover performance.
*3: inter system : LTE- non 3GPP HO
|
+| Continuous Network Supervision: Supervision of the signal strength when handovers are triggered. This information is useful for evaluating the customer experience (e.g. throughput) at the cell edge and during handover as well for network planning purposes (e.g. signal strength at the cell edge).
Troubleshooting: detect a "bad" configuration/neighbor in a particular direction by analyzing abnormal measurement report causing HO.
| Signal strength of the serving and neighbouring cell reported by the UE in handover triggering measurement reports in EUtranRelation..
|
+| Troubleshooting: Detection of bad handover relation. The first use case provides the overall performance of handover success rate on E-UTRAN cell level, but it is essential to get a knowledge between which cell pairs the handover success rate is low. Therefore it is important to know the success rate on neighbor cell relation basis.
| - - HO Success Rate (neighbourcell)
|
+| Troubleshooting: Reason for started handover
To go for further analysis of handover failures, it is essential to know what causes the handovers. For this we need to know the success rate of handovers per HO reason.
| - - outgoing HO Success Rate per HO reason ( neighbor cell) *4
*4 different results expected e.g. emergency or normal HO
|
+| Troubleshooting: Reason for failed handover. To go for further detailed analysis for handover failure it is important to know what the reason for handover failure was, or whether the handover was assisted by measurement gaps or was with DRX.
| - - outgoing HO Failure Distribution Rate (cell+neighbourcell)
- - HO Path Switching Failure Distribution Rate (cell or Interface)
- - HO Failure Rate DRX / Non DRX (cell) *5
- - Inter frequency HO Failure Rate Meas gap assisted / not assisted (cell) *5
|
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| It is also important to know if measurement gaps and DRX are helping in handover procedure or not. (i.e. what is the handover failure rate if measurement gaps are switched on. Measurement gaps and DRX can cause more load and battery consumption to the UE, therefore if these are not causing any changes in handover failure rate, operators may not use them) | *5: measurement only on cell basis and not per neighbourcell
due to amount of counters as mentioned above. |
+| Network Planning: Traffic flow analysis
or
Network Planning: Handover traffic optimization | - outgoing Intra RAT HO Success Rate (neighbour cell)
- outgoing Inter RAT HO Success Rate (cell)
- outgoing Inter System HO Success Rate (cell) |
+
+## A.5 Monitor of cell level QoS and radio resource utilisation
+
+In an E-UTRAN cell the quality of service achieved is directly influenced by a number of factors, including:
+
+- Loading of users on the cell
+- Traffic loading and characteristics
+- UE locations and mobility
+- RRM policies
+ - Scheduling
+ - congestion control
+ - admission control
+ - layer 2 protocol configuration
+- Mapping of traffic to QCI
+- Setting of QoS parameters other than the QCI.
+
+It is very important to be able to monitor the QoS to determine whether the combined effect of these policies, algorithms and external factors is satisfactory. Unsatisfactory QoS may be rectified by adjusting policies and RRM settings, for instance.
+
+### Cell bit-rate
+
+A fundamental measure of QoS is the throughput (data rate) of the cell. The total cell throughput measured across all radio bearers gives an indication of the loading and activity in the cell. Adding a per QCI counter allows the loading on the different QCIs to be measured. For example, if QCI 1 is used exclusively for VoIP then the loading of conversational speech can be directly determined. Finally, the maximum throughput can indicate to the operator whether there is enough capacity in the network; for example, is the backhaul sufficient. Separate counters should be configured on the downlink and uplink. Complexity may be reduced by performing the counters at layer 3, giving the ingress bit-rate to the eNB on the downlink and the egress bit-rate from the eNB on the uplink.
+
+Cell throughput includes both User Plane data and Control Plane data. To support the User Plane data, necessary Control Plane data also need to be transmitted. This Control Plane data although required, will not be perceived (felt) by the User. The total cell throughput helps to evaluate the usage of bandwidth and radio resource.
+
+Operators ideally want to see the Control Plane data as small as possible when compared to the User Plane data without compromising on the service.
+
+Hence it is important to monitor the total cell throughput as well as how much is occupied by Control Plane Data.
+
+### Number of active UEs
+
+It is also of interest to determine how many users are enjoying the throughput numbers determined for each QCI. Therefore, we may count the number of users that are active for each QCI – here active users have data queued pending transmission. A simple division of the throughput (data rate) of a QCI by the number of active users on the QCI indicates the throughput per user on the QCI. For example, taking QCI 1 this metric could indicate the typical codec rate being employed in the cell. Alternatively, for QCI 9 supporting low priority TCP-based traffic it can indicate the typical bandwidth pipe size for a user when he has data to send / receive.
+
+### DL packet delay
+
+Latency is of prime concern for some services, particularly conversational services like speech and instant messaging. A counter is added to measure the mean delay for IP packets incurred within the eNodeB. Separate counters are provided per QCI which are particularly useful when the QCI is used by very few services and the packet sizes vary little. It is only practical to measure packet delays on the downlink.
+
+In case of the eNodeB serving one or more RN, the packet delay includes both the internal processing delay at eNB) and UE/RN as well as the packet transferring delay on the radio link. As RN UE's packets need to be transferred via between E-UTRAN and RN while packets for UEs directly connected to eNB need to pass through only Uu interface, packet delay optimization mechanism may be different for RN UEs and eNB UEs. Therefore it is beneficial to have measurements on packet delay separately for packets transmitted between the eNodeB and UEs and for packets transmitted between the E-UTRAN and RNs.
+
+### DL packet drop rate
+
+When a cell is heavily loaded congestion can take place. When congestion is not severe, the impact is typically the incurrence of additional delay for non-GBR radio bearers. However, when congestion is severe the eNodeB may be forced to discard packets. It is important for the operator to have visibility of packet discard so that corrective action can be instigated (for example, by adjusting admission control settings in the network). It is only practical to measure packet discards on the downlink. Packet discards on handover should not be included in the count.
+
+### PRB Usage
+
+The resource utilisation, measured in terms of physical resource blocks (PRBs), is a useful measure of whether a cell is lightly loaded or not. Loading is a key input to network capacity planning and load balancing. Furthermore, when resource utilisation per QCI is reported the distribution of resources between different services can be estimated.
+
+For a RN that requires subframe configuration, the RN can only be scheduled by the eNodeB within subframes configured for RN, while macro UE can be scheduled in any subframe. Therefore in certain scenario it may be possible that the PRB usage is different for the subframe configured for the RN and for any other subframe. For example, in case there are many RNs in the network and only a few UEs connected directly to the eNodeB, it may happen that the PRB usage in the subframe configured for RN is quite high, while the subframes used for UEs is low. Therefore it is beneficial to measure the PRB usage separately for RN and the total PRB usage. The total PRB usage includes the PRB usage for RN traffic and UE traffic, while the RN PRB usage includes only PRB usage for RN traffic.
+
+### Resource Full Utilisation
+
+Resource congestion is a critical situation in the network that needs to be monitored closely in order to be assessed and addressed immediately (e.g. by expanding related resources). Measurements reflecting the time during which the resources are fully used are needed to properly assess the congestion. Congestion affects PRB so appropriate congestion measurements are needed.
+
+### Transport Resource Usage
+
+Transport resource utilisation provides information on the overall traffic of an eNodeB with the rest of the network, together with information on the traffic of the individual cells it gives the ability to localise bottlenecks. On the other hand it is a key input for planning of timely expansion of transport (backhaul) resources in the network provides. Measurements enabling to track the transport resource utilisation are therefore useful.
+
+### Hardware Resource Usage
+
+Hardware resource utilisation provides information on the overall load of an eNodeB, together with the information on the individual loads it gives the ability to localise bottlenecks. On the other hand it is a key input for planning of timely
+
+expansion of hardware resources in the network. Measurements enabling to track the hardware resource utilisation are therefore useful.
+
+### Downlink Air interface packet loss rate
+
+The downlink air interface packet loss can be directly compared with the PELR value of a QCI to see if the packet loss (over the air interface) aspect of quality of service is being met within the cell (see [12] for more details on PELR). On the downlink this measurement can be added to the congestion losses (see DL packet drop rate) to determine the total packet loss rate at the eNodeB. Consequently, the downlink useful bit-rate can be estimated by scaling the measurement of the downlink PDCP ingress bit-rate by $(1 - \text{DL packet drop rate}) (1 - \text{air interface packet loss rate})$ .
+
+In case of RN deployment the communication between the E-UTRAN and RN is going through the air interface. It is possible that the radio conditions are bad, which can lead also to high packet loss rate, which can contribute also whether the packet loss aspect of the quality of service is met or not. Therefore it is beneficial to have separate packet loss rate measurement for RN traffic and for the traffic connected directly to the eNodeB.
+
+### Uplink packet loss rate
+
+The uplink air interface packet loss rate (per QCI) can be compared directly with the PELR defined for that QCI. An estimate of the uplink air interface packet loss may be provided by the “Uplink PDCP SDU loss rate”. This uplink measurement is based on PDCP sequence numbers and cannot precisely measure the air interface losses. Any packets discarded by the UE within the protocol stack (i.e. at layer 2) are also counted since they will have been given a PDCP sequence number. Discards at layer 3 are not counted.
+
+In case of RN deployment the communication between the E-UTRAN and RN is going through the air interface. It is possible that the radio conditions are bad, which can lead also to high packet loss rate, which can contribute also whether the packet loss aspect of the quality of service is met or not. Therefore it is beneficial to have separate packet loss rate measurement for RN traffic and for the traffic connected directly to the eNodeB.
+
+### RACH Usage
+
+The RACH plays a vital role in the following procedures:
+
+- Initial access from RRC\_IDLE;
+- Initial access after radio link failure;
+- Handover requiring random access procedure;
+- DL data arrival during RRC\_CONNECTED requiring random access procedure;
+- UL data arrival during RRC\_CONNECTED requiring random access procedure;
+
+Furthermore, the random access procedure takes two distinct forms:
+
+- Contention based using a randomly selected preamble (applicable to all five events);
+- Non-contention based using a dedicated preamble (applicable to only handover and DL data arrival).
+
+In the use-case of RACH configuration optimization, received Random Access Preambles and a contention indicator are signalled across an OAM interface.
+
+Monitoring of the preamble usage in a cell allows the operator to determine if the resources allocated to the RACH by the eNodeB are appropriate for the number of random access attempts. If the resources are underutilised then the operator may reconfigure the eNodeB (via CM) to allocate less resource to RACH thereby freeing up resource for other uplink transmissions. Alternatively, if the resources are heavily utilised then this is indicative of RACH congestion leading to increased latency for the procedures listed above. To this effect, measurements directly reflecting RACH congestion experienced by the eNodeB and by the UEs are useful.
+
+The eNodeB can partition the RACH resource between dedicated preambles, randomly selected preambles in group A and randomly selected preambles in group B. This partitioning can be evaluated when usage measurements are made on each set separately.
+
+To further monitor and analyze the latency of the procedures listed above created at the RACH level, the measurement of the number of RACH preambles sent per RACH attempt is useful.
+
+RACH optimisation function optimises RACH related configurations to achieve minimizing of access delays and random access collision probability for all the UEs. eNB may request the UEs to report the number of attempts to access the network (numberOfPreamblesSent in TS 36.331 [8]). Based on the attempting number of random access of all the UEs, the eNB can know the distribution of RACH preambles sent by UEs and calculate the access probability (AP) of a cell accurately. The eNB may also request the UEs to report contention detected while attempting to access the network (contentionDetected in TS 36.331 [8]). Based on the estimated time per random access and the estimated contention level in the network, the eNB can estimate the access delay probability (ADP) of a cell.
+
+## --- A.6 Monitor of the number of connected users
+
+The number of the connected users in each cell is valuable information for operators to know how many users are connecting to E-UTRAN per cell basis. This kind of information can help operator to tune the admission control parameters for the cell and to do load balancing between cells to ensure that the target percentage or number of users admitted achieve the target QoS.
+
+## --- A.7 Monitoring of interference situation
+
+In the LTE radio technology interference has to be coordinated on the basis uplink and downlink i.e. in a coordinated usage of the UL resources (Physical Resource Blocks, PRBs) and DL Transmitted Power, which lead to improve SIR and corresponding throughput. These are achieved by means of mechanisms employing channel quality indicators in support of scheduling/radio resource allocation functions.
+
+These RRM functions in the eNB require the setting of frequency / power restrictions and preferences for the resource usage in the different cells. Setting and updating these parameters is the task of a network optimisation (done by operator or automatically by SON).
+
+Use cases for the related interference measurements are e.g. optimisation of ICIC related RRM functionality, the detection of long distance interferer and the interference due to spurious emissions of neighbour cells. The later case is assumed only in high load scenarios or unsufficient ICIC functionality due to the the fact that ICIC functionality would minimise interference autonomously if sufficient bandwidth is available.
+
+The necessary measurements to identify and analyse the interference situation as input for optimisation tasks has to be defined.
+
+## --- A.8 Monitor of ARQ and HARQ performance
+
+Reliable Packet Delivery is one of the important Performance factor for a better User experience. HARQ retransmissions at the MAC layer ensure reliable packet delivery
+
+In addition, RLC can be configured to operate in acknowledged mode for those applications that need very low packet drops and can tolerate a slightly higher delay from RLC retransmissions.
+
+If a MAC PDU is not delivered, HARQ takes care of retransmitting (upto a maximum configurable number). If all the retransmissions fail at MAC layer, and if RLC is configured to operate in acknowledged mode, RLC's ARQ mechanism will take care of any residual packet errors.
+
+It is important to
+
+a) maintain the block error rate or packet error rate within tolerable limits
+
+b) ensure that HARQ retransmissions take care of most packet errors, instead of relying on RLC layer retransmissions (which would increase the delay).
+
+So, it is important to monitor the performance of these schemes.
+
+ARQ Performance if viewed at QCI level can help in monitoring the distribution for each of the services.
+
+HARQ Performance if viewed at MCS (Modulation Coded Scheme) can help in monitoring the MCS Performance also.
+
+## --- A.9 Monitoring of RF performance
+
+RF Performance reflects the cell loading levels and abnormal conditions.
+
+In the Downlink, Power Resources are managed by the EUTRAN Cell(RAN).
+
+More Power Resources may help in increasing the Capacity of the System. Hence, there the power resources could be effectively used to optimize the Capacity of the System.
+
+Hence there is a need to keep monitoring the Power Resource Utilization in % and also in absolute terms.
+
+Monitoring of the quality of RF signal in the cell is useful for the purpose of NW planning and overall service quality assessment. Measurements of Channel Quality Indicator (CQI) reported by UEs is a useful metric reflecting RF signal quality and service quality.
+
+Timing advance measurements reflect the distance of the UE from the cell antenna. This information reflects the optimality of the cell antenna location with respect to the cell traffic and is useful in the NW planning process.
+
+Monitoring interference, both uplink and downlink, is an important aspect of monitoring RF performance. For this purpose, monitoring of UL interference power is useful.
+
+Interference signals in a number of different ways, including frequency, frequency band, direction of interfering signals, etc. can also be classified by System internal interference and External interference. By efficient frequency planning and careful
+
+Selection of base station locations, the impact of interference signal can be effectively controlled within an acceptable scope. uplink interference disturbs the base station receiver. Once the base station receiver is compromised, it leads to receiving code errors for the whole base station and the site's entire service area is degraded including its network and service. Of course, customer satisfaction is negatively impacted. So it is very useful to monitor uplink interference of communication system to do network optimization.
+
+## --- A.10 Monitor of paging performance
+
+In EUTRAN, Paging is under the control of the MME. When the MME wants to page a UE it has to page it in all cells that belong to the TA(s) to which the UE is registered.
+
+The paging load per cell is an important measure for the operator as it allows the operator to properly dimension the resources for paging in the E-UTRAN Cell .
+
+At an E-UTRAN Cell it makes sense to measure the number of discarded paging messages if this is due to some problem in the eNodeB, such as paging occasion overflow. In that scenario the periodicity of paging occasions can be reconfigured in order to ensure that all paging messages are transmitted by the eNodeB in the first available paging occasion, thereby avoiding paging delays and extended call setup delay.
+
+Operators need to know when such an event occurs, in order to identify if the problem is at the E-UTRAN cell level or not.
+
+In addition to discarded paging records measurement, it is important to know total paging records received so that discarded paging records ratio can be derived.
+
+Total number of paging records received is important in the sense that, it may be fine if the discarded paging records are high if discarded paging records ratio is small. On the other hand, it may be problematic if discarded paging records are low, if discarded paging records ratio turn out to be high.
+
+## --- A.11 Use case of eNodeB processor usage
+
+When network is very busy, for example on important holiday or emergency events happened, the traffic of one eNodeB is very heavy. So eNodeB processor usage measurements are very important to indicate eNodeB processor load capability. If eNodeB processor usage is too high, operator must take action to avoid network paralysis.
+
+## --- A.12 Monitor of simultaneous E-RABs
+
+E-RAB is one of the EUTRAN Cell resources which are limited in number.
+
+Hence along with the E-RAB Setup Success Rate, there is a need to keep monitoring the simultaneous E-RABs and having them at QCI level can help in learning the service distribution in time periods.
+
+Average / Maximum simultaneous E-RABs, can help to know the average / maximum utilization of the resources in time periods, thereby helping to do necessary resource capacity engineering.
+
+## --- A.13 Monitoring of Mobility Robustness Optimization (MRO)
+
+The following measurement is defined specifically to monitor the performance of handover optimisation:
+
+- Number of handover failures for MRO.
+
+The measurement examines “handover related events” in which the serving cell of a RRC connected UE is changed. Handover related events are either normal successful handovers, or they are failures. Different failure modes are possible and the measurement provides counts for the occurrences of the failure modes related with MRO, “too early”, “too late” and “to wrong cell”. The detailed definitions of these modes are captured in [12]. The counters provide visibility of the mix of failure problems that the handover optimisation function is tackling.
+
+In addition to event-based (i.e. reactive) optimization of handover performance, a pro-active optimization is possible by monitoring the dynamics of handover triggering from UE measurement reports.
+
+## --- A.14 Monitor of BLER performance
+
+The TB Error Rate in UL/DL can directly reflect the BLER, and has an influence on MCS selection and user throughput. It can be helpful to estimate the performance of radio resource management like radio resource scheduling in transport layer and be helpful in trouble shooting. Furthermore, they should be taken into account to optimize the system performance. To obtain TB Error Rate by calculating, the number of total and error TBs transmitted in a cell should be monitored.
+
+## --- A.15 Monitoring of common LAs of overlapping target RAT's coverage
+
+For CS fallback in EPS, as defined in section 5.1A of 3GPP TS 23.272 [17], the fallback procedure is likely to be faster if the network can allocate a Location Area to the UE that is the LA of the overlapping target RAT's coverage. For this situation, the MME should avoid allocating TAI lists that span multiple Location Areas of the target RAT, this can be achieved by:
+
+- configuring the E-UTRAN cell's TAI to align the LA boundary of the target RAT;
+- the MME being configured to know which TAIs are within which LA; and
+- the MME using the TAI of the current E-UTRAN cell to derive the LAI.
+
+Also as specified in section 4.3.4 of 3GPP TS 23.272 [17], to facilitate the alignment of TA boundaries with LA boundaries, the E-UTRAN can gather statistics (from the inbound inter-RAT mobility events of all UEs) of the most common LAs indicated in the RRC signalling.
+
+From such measurements per E-UTRAN cell basis, operators 1) can know the common LA(s) of the overlapping target RAT's coverage for each TA, which is useful to configure the TAI list within which LA boundary to MME, operators can also 2) detect the case that TA spans multiple LAs if different most common LA(s) is/are reported from the E-UTRAN cells in the same TA, operators may take actions to rectify it if needed.
+
+---
+
+## A.16 Monitoring of Energy Saving
+
+Beside monitoring of the energy consumption it is also important to differentiate if the cell unavailability or the failure of the RRC connection establishment happens because of Energy Saving as Energy Saving Management feature is by the Operator on purpose. Therefore such failures should be distinguishable from other network failures, therefore should be counted separately. With the separate cell unavailability counter due to Energy Saving makes it possible to deduct the cell downtime due to Energy Savings from the total cell outage.
+
+---
+
+## A.17 Monitoring of RNReconfiguration
+
+The purpose of RNReconfiguration related procedure is to configure/reconfigure the RN subframe configuration and/or to update the system information relevant for the RN in RRC\_CONNECTED.
+
+The system information and subframe configuration is very important for RN, but the RN does not need to apply the system information acquisition and change monitoring procedures, if configured with an RN subframe configuration. Upon change of any system information relevant to an RN, E-UTRAN provides the system information blocks containing the relevant system information to RNs with an RN subframe configuration via dedicated signalling using the *RNReconfiguration* message. This dedicated signalling replaces any stored system information acquired through the system information acquisition procedure.
+
+Because the RN is semi-duplex, to avoid the transmission conflict between access link (between UE and RN) and backhaul link (between RN and DeNB), the subframe of RN is semi-statically assigned (see TR 36.814) and the configuration information is included in the RNReconfiguration message.
+
+During the RN operation, failures of backhaul link will cause unsuccessful RN reconfiguration. In that case, RN will not get any response from DeNB. The defined performance counter will help to compute how many response messages are missing. Depending on this result, operators could easily make network planning to consider fix or optimize the backhaul link quality.
+
+---
+
+## A.18 Monitoring of E-RAB setup for incoming HOs
+
+The E-RAB needs to be established in the target cell during HO, the success or failure of E-RAB establishment in the target cell during HO results in if the services beared on the E-RABs can continue or not after HO, thus whether or not the E-RAB can be successfully established for incoming HO impacts the user experience.
+
+The unsuccessful setup of E-RABs with different QCIs could lead to different user experience, thus the E-RAB setup for incoming HOs needs to be monitored per QCI.
+
+---
+
+## Annex B (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------------------------------------|-----|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| Mar 2009 | SP-43 | SP-090143 | -- | -- | Presentation to SA for information and approval | -- | 1.0.0 | 8.0.0 |
+| Jun 2009 | SP-44 | SP-090408 | 002 | -- | Add missing E-UTRAN measurement for paging discards at the eNodeB - Align with 36.304 and 32.426 | F | 8.0.0 | 8.1.0 |
+| Jun 2009 | SP-44 | SP-090290 | 001 | -- | Addition of eNodeB processor usage related measurements | B | 8.1.0 | 9.0.0 |
+| Sep 2009 | SP-45 | SP-090542 | 004 | -- | Correction on the IP latency and additional SAE Bearers setup measurements | A | 9.0.0 | 9.1.0 |
+| Sep 2009 | SP-45 | SP-090542 | 006 | -- | Alignment of PRB usage related measurements with 36.314 | A | 9.0.0 | 9.1.0 |
+| Sep 2009 | SP-45 | SP-090627 | 007 | -- | Add SAE Bearer number related measurements | B | 9.0.0 | 9.1.0 |
+| Mar 2010 | SP-47 | SP-100035 | 010 | -- | Add RRC connection release as a PM counter | F | 9.1.0 | 9.2.0 |
+| Mar 2010 | SP-47 | SP-100035 | 011 | -- | Introduction of handover failure PM counters for handover optimisation | F | 9.1.0 | 9.2.0 |
+| Mar 2010 | SP-47 | SP-100035 | 012 | -- | Add a PM counter of RRC connection establishments per failure cause | F | 9.1.0 | 9.2.0 |
+| Mar 2010 | SP-47 | SP-100036 | 008 | -- | Incorrect section numbering | D | 9.2.0 | 10.0.0 |
+| Mar 2010 | SP-47 | SP-100036 | 009 | -- | Add TB related measurements | B | 9.2.0 | 10.0.0 |
+| Jun 2010 | SP-48 | SP-100264 | | -- | | D | 10.0.0 | 10.1.0 |
+| Jun 2010 | SP-48 | SP-100259 | 013 | -- | Editorial changes to clause References | A | 10.0.0 | 10.1.0 |
+| Jun 2010 | SP-48 | SP-100412 | 022 | -- | Correct L3 messages in measurement definitions | A | 10.0.0 | 10.1.0 |
+| Jun 2010 | SP-48 | SP-100262 | 018 | -- | Add IP Throughput measurements | A | 10.0.0 | 10.1.0 |
+| Jun 2010 | SP-48 | SP-100262 | 015 | -- | Missing Measurement related to common LAs to support faster CS fallback in EPS | A | 10.0.0 | 10.1.0 |
+| Jun 2010 | SP-48 | SP-100262 | 019 | -- | Add the missing reference of causes in HO measurements | A | 10.0.0 | 10.1.0 |
+| Sep 2010 | SP-49 | SP-100488 | | -- | | | 10.1.0 | 10.2.0 |
+| Sep 2010 | SP-49 | SP-100489 | 023 | -- | Correction of intra-RAT HO measurements | A | 10.1.0 | 10.2.0 |
+| Sep 2010 | SP-49 | SP-100489 | 024 | -- | Modification of E-RAB release related measurements | C | 10.1.0 | 10.2.0 |
+| Sep 2010 | SP-49 | SP-100489 | 025 | -- | Addition of measurements for pagings received | B | 10.1.0 | 10.2.0 |
+| Sep 2010 | SP-49 | SP-100493 | 026 | -- | Modifying RRC establishment failure and Cellunavailability measurements due to Energy Saving | C | 10.1.0 | 10.2.0 |
+| Dec 2010 | SP-50 | SP-100878 | | 1 | | | 10.2.0 | 10.3.0 |
+| Mar 2011 | SP-51 | SP-110095 | 030 | 1 | Correcting L3 messages and cleanup | A | 10.2.0 | 10.3.0 |
+| Mar 2011 | SP-51 | SP-110095 | 031 | 1 | Apply the RRC connection setup related measurements to RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 032 | 2 | Apply the RRC connection reestablishment related measurements to RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 033 | 1 | Apply the E-RAB setup related measurements to RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 034 | 2 | Apply the abnormal E-RAB release related measurements to RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 035 | 1 | Addition of HO related measurements to RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 036 | 1 | Apply the eNB measurements to DeNB as well | C | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 044 | 1 | Adding measurements on power utilization | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110093 | 048 | - | Change counter for RACH usage from 'Cumulative Counter' to 'Gauge' | A | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 053 | 1 | Add measurements for maximum PRB usage | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 054 | 1 | Add measurements for radio coverage | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 055 | 9 | Add measurements for radio coverage, handover triggering, RACH performance | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 058 | 1 | Add RRC connection setup and UE context release related measurements of RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 059 | 1 | Add E-RAB release and modification related measurements of RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 060 | - | Add inter-RAT HO related measurements of RN | B | 10.3.0 | 10.4.0 |
+
+| | | | | | | | | |
+|------------|-------|-----------|------|----|--------------------------------------------------------------------------------|---|--------|--------|
+| Mar 2011 | SP-51 | SP-110095 | 061 | - | Add cell level radio bearer QoS related measurements of RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 062 | - | Add Radio resource utilization related measurements of RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 063 | - | Add paging related measurements of RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 064 | - | Add equipment resources related measurements of RN | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 065 | 2 | Adding separate counters for Un link and Uu link L2 measurements in DeNB. | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 066 | 2 | Add RNReconfiguration related measurements to DeNB - Align with RAN2 TS 36.331 | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110098 | 067 | 1 | Introduction of PM counters on distribution of RACH preambles sent | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 068 | 1 | Add HO to RN in intro-eNB HO measurements | B | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110095 | 069 | 1 | Exclude HOs from RN in inter-eNB HO measurements | C | 10.3.0 | 10.4.0 |
+| Mar 2011 | SP-51 | SP-110094 | 071 | 2 | Correct CSFB measurements to exclude inapplicable scenarios | A | 10.3.0 | 10.4.0 |
+| May 2011 | SP-52 | SP-110287 | 074 | - | Correct measurement of released active E-RABs | A | 10.4.0 | 10.5.0 |
+| May 2011 | SP-52 | SP-110285 | 077 | 2 | Remove the inconsistency with RAN wrt RNs | F | 10.4.0 | 10.5.0 |
+| May 2011 | SP-52 | SP-110288 | 079 | - | Correction of HO measurements names at EUTranRelation level | A | 10.4.0 | 10.5.0 |
+| Sep 2011 | SP-53 | SP-110634 | 081 | 2 | Add missing measurements for unnecessary HOs for Inter-RAT MRO | B | 10.5.0 | 11.0.0 |
+| Dec 2011 | SP-54 | SP-110707 | 0089 | 1 | Distinguish trigger in MRO measurements of too late handovers | B | 11.0.0 | 11.1.0 |
+| March 2012 | SP-55 | SP-120043 | 0093 | - | Correction of E-RAB release related measurements | A | 11.1.0 | 11.2.0 |
+| June 2012 | SP-56 | SP-120355 | 0106 | 1 | Include path switch and HO in E-RAB release measurements | A | 11.2.0 | 11.3.0 |
+| June 2012 | SP-56 | SP-120356 | 0109 | -- | Correction of IP throughput measurements | A | 11.2.0 | 11.3.0 |
+| June 2012 | SP-56 | SP-120358 | 0110 | 2 | Correction of E-RAB activity measurements used by Retainability KPI | F | 11.2.0 | 11.3.0 |
+| June 2012 | SP-56 | SP-120358 | 0111 | 1 | Add number of E-RABs by incoming HOs | B | 11.2.0 | 11.3.0 |
+| Dec-2012 | SP-58 | SP-120790 | 0083 | 5 | Statement for handover related measurements in CA | B | 11.3.0 | 11.4.0 |
+| | | SP-120790 | 0090 | 3 | Add statement about applicability of measurements to CA | B | | |
+| | | SP-120790 | 0094 | 3 | Statement for CQI related measurements in CA | B | | |
+| | | SP-120790 | 0114 | 3 | Clarify measured object for E-RAB related measurements for CA | B | | |
\ No newline at end of file
diff --git a/marked/Rel-11/32_series/32436/raw.md b/marked/Rel-11/32_series/32436/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3128c70559e46bc2ec18548a98b657f25255dbd1
--- /dev/null
+++ b/marked/Rel-11/32_series/32436/raw.md
@@ -0,0 +1,333 @@
+
+
+
+
+
+
+# --- Contents
+
+| | |
+|------------------------------------------------------------------------------|----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Mapping ..... | 6 |
+| 5 ASN.1 file format definition ..... | 7 |
+| Annex A (informative): Example of ASN.1 Measurement Report File ..... | 9 |
+| Annex B (informative): Change history..... | 10 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document is part of a TS-family covering the 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
+
+- TS 32.432: "Performance measurement; File format definition";
+- TS 32.435: "Performance measurement; eXtensible Markup Language (XML) file format definition";
+- TS 32.436: "Performance measurement; Abstract Syntax Notation 1 (ASN.1) file format definition".**
+
+The present document is part of a set of specifications, which describe the requirements and information model necessary for the standardised Operation, Administration and Maintenance (OA&M) of a multi-vendor 3G PLMN.
+
+During the lifetime of a PLMN, its logical and physical configuration will undergo changes of varying degrees and frequencies in order to optimise the utilisation of the network resources. These changes will be executed through network configuration management activities and/or network engineering, see 3GPP TS 32.600 [4].
+
+Many of the activities involved in the daily operation and future network planning of a PLMN network require data on which to base decisions. This data refers to the load carried by the network and the grade of service offered. In order to produce this data performance measurements are executed in the NEs, which comprise the network. The data can then be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation. The purpose of the present document and the other related 3GPP TSs listed above is to describe the mechanisms involved in the collection of the data.
+
+# --- 1 Scope
+
+The present document defines the ASN.1 file format definition for performance measurement results collection whose semantics is defined in 3GPP TS 32.432 [5].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
+- [4] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
+- [5] 3GPP TS 32.432: "Performance Measurement: File format definition".
+- [6] ITU-T Recommendation X.680: "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**network Element Manager (EM):** provides a package of end-user functions for management of a set of closely related types of Network Elements. These functions can be divided into two main categories:
+
+- Element Management Functions for management of Network Elements on an individual basis. These are basically the same functions as supported by the corresponding local terminals.
+- Sub-Network Management Functions that are related to a network model for a set of Network Elements constituting a clearly defined sub-network, which may include relations between the Network Elements. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning).
+
+**Network Manager (NM):** provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the Network Elements. All communication with the network is based on open and well-standardised interfaces supporting management of multi-vendor and multi-technology Network Elements.
+
+**Operations System (OS):** generic management system, independent of its location level within the management hierarchy.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|-----------------------------------------|
+| 3G | 3 rd Generation |
+| ASN.1 | Abstract Syntax Notation 1 |
+| BER | Basic Encoding Rules |
+| EM | Element Manager |
+| GSM | Global System for Mobile communications |
+| IRP | Integration Reference Point |
+| NE | Network Element |
+| NM | Network Manager |
+| PM | Performance Management |
+
+# 4 Mapping
+
+Table 4.1 maps the file content items in the 3GPP TS 32.432 [5] to those used in the ASN.1 (see [6]) file format definitions.
+
+**Table 4.1 Mapping of File Content Items to ASN.1 types**
+
+| File Content Item | ASN.1 Type | Description |
+|---------------------|---------------------|-----------------------------------------------------------------------------------------------------------------|
+| measDataCollection | MeasDataCollection | |
+| measFileHeader | MeasFileHeader | |
+| measData | MeasData | |
+| measFileFooter | MeasFileFooter | |
+| fileFormatVersion | FileFormatVersion | |
+| senderName | SenderName | For ASN.1 format, the string may be empty (i.e. string size =0) in case the DN is not configured in the sender. |
+| senderType | SenderType | |
+| vendorName | VendorName | |
+| collectionBeginTime | CollectionBeginTime | |
+| neId | NEId | |
+| neUserName | NEUserName | |
+| neDistinguishedName | NEDistinguishedName | |
+| neSoftwareVersion | NESoftwareVersion | |
+| measInfo | MeasInfo | |
+| measInfoId | MeasInfoId | |
+| measTimeStamp | MeasTimeStamp | |
+| jobId | JobId | |
+| granularityPeriod | GranularityPeriod | |
+| reportingPeriod | ReportingPeriod | |
+| measTypes | MeasTypes | |
+| measValues | MeasValues | |
+| measObjInstId | MeasObjInstId | |
+| measResults | MeasResults | |
+| suspectFlag | SuspectFlag | |
+| timeStamp | TimeStamp | ASN.1 GeneralizedTime format. |
+
+# 5 ASN.1 file format definition
+
+The ASN.1 file format definitions implement the measurement result structure and parameters defined in clauses 5.2 and 5.3 of 3GPP TS 32.401 [3].
+
+For ASN.1 formatted files, BER encoding rules shall apply. Embedded comments are integral parts of the standard format; i.e. any implementation-claiming conformance to this annex shall also conform to the comments.
+
+PM-File-Description
+
+DEFINITIONS AUTOMATIC TAGS::= BEGIN
+
+MeasDataCollection::= SEQUENCE
+
+```
+{
+ measFileHeader MeasFileHeader,
+ measData SEQUENCE OF MeasData,
+ measFileFooter MeasFileFooter
+}
+```
+
+MeasFileHeader::= SEQUENCE
+
+```
+{
+ fileFormatVersion PrintableString (SIZE (0..15)),
+ senderName PrintableString (SIZE (0..400)),
+ senderType SenderType,
+ vendorName PrintableString (SIZE (0..32)),
+ collectionBeginTime Timestamp,
+ ...
+}
+```
+
+-- The sole purpose of the ellipsis notation used in the file header is to facilitate inter-release compatibility, vendor specific additions are not allowed in implementations claiming conformance to the TS. However, it is acknowledged that this feature does enable the use of non-standard extensions to the file header without loosing compatibility to the file format specified in the present document.
+
+SenderType::= PrintableString (SIZE (0..8))
+
+Timestamp::= GeneralizedTime
+
+MeasData::= SEQUENCE
+
+```
+{
+ nEId NEId,
+ measInfo SEQUENCE OF MeasInfo
+}
+```
+
+NEId::= SEQUENCE
+
+```
+{
+ nEUserName PrintableString (SIZE (0..64)),
+ nEDistinguishedName PrintableString (SIZE (0..400)),
+ nESoftwareVersion PrintableString (SIZE (0..64)) OPTIONAL
+}
+```
+
+MeasInfo::= SEQUENCE
+
+```
+{
+ measTimeStamp Timestamp,
+ granularityPeriod INTEGER,
+ measTypes SEQUENCE OF MeasType,
+ measValues SEQUENCE OF MeasValue,
+ reportingPeriod INTEGER OPTIONAL,
+ jobId INTEGER OPTIONAL,
+ measInfoId PrintableString (SIZE (0..64)) OPTIONAL,
+}
+```
+
+MeasType::= PrintableString (SIZE (1..64))
+
+MeasValue::= SEQUENCE
+
+```
+{
+ measObjInstId MeasObjInstId,
+ measResults SEQUENCE OF MeasResult,
+ suspectFlag BOOLEAN DEFAULT FALSE
+}
+```
+
+MeasObjInstId::= PrintableString (SIZE (0..400))
+
+-- The size of the concatenated measObjInstId and neDistinguishedName must not exceed 400.
+
+MeasResult::= CHOICE
+
+```
+{
+```
+
+```
+ iValue INTEGER,
+ rValue REAL,
+ noValue NULL,
+ ...
+}
+```
+
+-- Normal values are INTEGERs and REALs. The NULL value is reserved to indicate that the measurement item is not applicable or could not be retrieved for the object instance. The sole purpose of the ellipsis notation used in the MeasResult choice is to facilitate inter-release compatibility in case the choice needs to be extended in future releases.
+
+```
+MeasFileFooter::= TimeStamp
+```
+
+```
+END
+```
+
+# Annex A (informative): Example of ASN.1 Measurement Report File
+
+For readability, a kind of pseudo ASN.1 was used instead of the BER encoding.
+
+```
+MeasDataCollection ::= {
+ measFileHeader {
+ fileFormatVersion ::= "32.436 V6.1",
+ senderName ::=
+ "DC=a1.companyNN.com,SubNetwork=1,IRPAgent=1,SubNetwork=CountryNN,MeContext=MEC-Gbg-
+ 1,ManagedElement=RNC-Gbg-1",
+ senderType ::= "RNC",
+ vendorName ::= "Company NN",
+ collectionBeginTime ::= 20000301140000
+ },
+ measData {
+ nEId {
+ nEUserName ::= "RNC Telecomville",
+ nEDistinguishedName ::=
+ "DC=a1.companyNN.com,SubNetwork=1,IRPAgent=1,SubNetwork=CountryNN,MeContext=MEC-Gbg-
+ 1,ManagedElement=RNC-Gbg-1",
+ nESoftwareVersion ::= "2.1"
+ },
+ measInfo {
+ measInfoId ::= Category A
+ measTimeStamp ::= 20000301141430,
+ jobId ::= "1231",
+ granularityPeriod ::= 900,
+ reportingPeriod ::= 1800,
+ measTypes {
+ "attTCHSeizures",
+ "succTCHSeizures",
+ "attImmediateAssignProcs",
+ "succImmediateAssignProcs"
+ },
+ measValues {
+ {
+ measObjInstId ::= "RncFunction=RF-1,UtranCell=Gbg-997",
+ measResults {
+ iValue ::= 234,
+ iValue ::= 345,
+ iValue ::= 567,
+ iValue ::= 789
+ },
+ suspectFlag ::= FALSE
+ },
+ {
+ measObjInstId ::= "RncFunction=RF-1,UtranCell=Gbg-998",
+ measResults {
+ iValue ::= 890,
+ iValue ::= 901,
+ iValue ::= 123,
+ iValue ::= 234
+ },
+ suspectFlag ::= FALSE
+ },
+ {
+ measObjInstId ::= "RncFunction=RF-1,UtranCell=Gbg-999",
+ measResults {
+ iValue ::= 456,
+ iValue ::= 567,
+ iValue ::= 678,
+ iValue ::= 789
+ },
+ suspectFlag ::= TRUE
+ }
+ }
+ }
+ },
+ measFileFooter ::= 20000301141500
+}
+```
+
+# --- Annex B (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------|-----|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| 2004-09 | SA-25 | SP-040580 | -- | -- | Draft created based on 32.401 V6.1.0 and submitted to SA#25 for Information | -- | 1.0.0 | |
+| 2004-12 | SA-26 | SP-040788 | -- | -- | Submitted to SA#26 for Approval | -- | 2.0.0 | 6.0.0 |
+| 2005-09 | SA-29 | SP-050585 | 0001 | -- | Enhance PM ASN.1 file with measInfo | C | 6.0.0 | 7.0.0 |
+| 2008-12 | SA-42 | -- | -- | -- | Upgrade to Release 8 | -- | 7.0.0 | 8.0.0 |
+| 2009-12 | SA-46 | -- | -- | -- | Upgrade to Release 9 | -- | 8.0.0 | 9.0.0 |
+| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | -- | 9.0.0 | 10.0.0 |
+| 2012-09 | SA-57 | - | - | - | Automatic upgrade from previous Release version 10.0.0 | - | 10.0.0 | 11.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/32_series/32441/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-11/32_series/32441/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ea49c8b85f55c735550677c4e2486c04d813474
--- /dev/null
+++ b/marked/Rel-11/32_series/32441/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54b22b8649fc3be331908ff0e6b99a09f3af0b231e3dc2348506e2cb504e06f2
+size 51808
diff --git a/marked/Rel-11/32_series/32441/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-11/32_series/32441/78ffccd66df9bafd96e3e081110d09dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acf04d936a8a9b76d6c96de3b35d15cd9283ca5e
--- /dev/null
+++ b/marked/Rel-11/32_series/32441/78ffccd66df9bafd96e3e081110d09dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f4a18de97e2b411a446efff90f2dded11c8ca6605027787c4988c8ed4d3b06f
+size 37250
diff --git a/marked/Rel-11/32_series/32441/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Rel-11/32_series/32441/a26e142d3df5bef41a84a9dd099d7825_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1cd3954a4370231b22bdb51a3b46e6410e2662c0
--- /dev/null
+++ b/marked/Rel-11/32_series/32441/a26e142d3df5bef41a84a9dd099d7825_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a16102ecd5d1d95a8e7a02c48ffe82392af690187485c81efbf53b8436cf9971
+size 53073
diff --git a/marked/Rel-11/32_series/32441/raw.md b/marked/Rel-11/32_series/32441/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e22c20ba39b6a1550b87dfe191e3f5668a92d649
--- /dev/null
+++ b/marked/Rel-11/32_series/32441/raw.md
@@ -0,0 +1,374 @@
+
+
+
+
+
+
+# --- Contents
+
+| | |
+|-------------------------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Trace Concepts..... | 6 |
+| 5 Trace Requirements ..... | 7 |
+| 5.1 Trace Management and Itf-N..... | 7 |
+| 5.2 Managing Trace Sessions..... | 8 |
+| 5.3 Management of trace record files..... | 9 |
+| 5.3.1 General ..... | 9 |
+| 5.3.2 Managing trace records for roaming cases (inter-operator cases)..... | 9 |
+| 5.3A Void..... | 9 |
+| 5.4 Overview of IRPs related to Trace..... | 9 |
+| 6 Requirements specific for managing MDT..... | 10 |
+| 7 Requirements specific for managing RLF reporting..... | 11 |
+| Annex A (informative): Use Cases..... | 12 |
+| A.1 General..... | 12 |
+| A.2 Use case #1: Centralized place for Trace Session Activation in case of Management Based Activation..... | 12 |
+| A.3 Use case #2: Centralized place to collect trace records in case of Signalling Based Activation..... | 13 |
+| A.4 Use case #3: Centralized place to collect trace records in case of Signalling Based Activation..... | 14 |
+| Annex B (informative): Change history..... | 15 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.441 "Trace Management Integration Reference Point (IRP); Requirements".**
+- 32.442 "Trace Management Integration Reference Point (IRP); Information Service (IS)".
+- 32.446 "Trace Management Integration Reference Point (IRP); Solution Set (SS) definitions".
+
+The present document is part of a TS-family which describes the requirements and information model necessary for the Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 [2] and 3GPP TS 32.102 [3].
+
+Trace provides very detailed information on call level for a specific subscriber or MS. This data is an additional information source to Performance Measurements and allows deeper investigations in problems solving or in case of optimization.
+
+# --- 1 Scope
+
+The present document specifies the overall requirements for the Trace Management Integration Reference Point (TraceIRP) as it applies to Itf-N.
+
+The Trace IRP supports the operations that are required for the Subscriber and Equipment trace the Cell Traffic Trace, Minimization of Drive Tests (MDT) functionalities across UMTS networks or EPS networks and Radio Link Failure (RLF) reporting functionalities across EPS networks GSM Trace is outside of the scope of this specification..
+
+All functions (trace, MDT etc.) specified in this specification supports Network Sharing, with the following condition:
+
+1. It is accepted that the recorded information from the shared network can be sent to any of the operators sharing the network, taking user consent into account. Operators must also agree on sharing the information, but how that agreement is done is outside the scope of this specification. The mapping of TCE IP addresses and TCE addresses must be coordinated among the operators that shares the network. How that coordination is done is outside the scope of this specification..
+2. For signalling based activation, the operators that share a network must coordinate the TCE IP addresses and the TCE address mapping must be coordinated. How that coordination is done, is outside the scope of this specification.
+3. The 3GPP Management reference model, 3GPP TS 32.101 [2] is followed.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [3] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [4] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
+- [5] void.
+- [6] 3GPP TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management".
+- [7] 3GPP TS 32.341: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Requirements".
+- [8] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
+- [9] void.
+- [10] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [11] 3GPP TS 32.301: "Notification Integration Reference Point (IRP): Requirements".
+
+- [12] 3GPP TS 32.302: "Notification Integration Reference Point (IRP): Information Service (IS)".
+- [13] void.
+- [14] void
+- [15] 3GPP TS 32.346: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [16] 3GPP TS 32.306: "Notification Integration Reference Point (IRP): Solution Set (SS) definitions"..
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] apply.
+
+NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Trace Concepts
+
+Trace Concepts are defined in 3GPP TS 32.421 [4].
+
+# --- 5 Trace Requirements
+
+## 5.1 Trace Management and Itf-N
+
+The Itf-N may connect the Network Management system to the EM, which can be located in either the DM (system context A) or in the NE (system context B). This is done by means of Integration Reference Points (IRPs).
+
+This clause describes the properties of an interface enabling a NM to monitor a 3G-telecommunication network including - if necessary - the managing EMs. To provide to the NM the Trace Management capability for the network implies that the NM and the EM have to agree on the following:
+
+- The identification of the NEs and UE where the Trace Session Activation is requested.
+- The identification of the files containing the trace records for retrieval by a Trace Collection Entity.
+- The identification of the subscriber or equipment shall be provided in the trace record files in case of subscriber and equipment trace. In case of Cell Traffic trace the cell identity shall be provided in the trace record file. In the case of trace in E-UTRAN, as neither the subscriber identity nor the equipment identity are provided to eNodeB, none of these identifiers are provided in the trace record files from the eNodeB. The connection to which subscriber or equipment is traced is made by the node that triggers the trace recording session to a Trace Collection Entity which collects the trace logs (indicated by the IP address in the Trace Session's configuration parameters). The connection is done by the triggering node providing the identifier of the subscriber or equipment together with the Trace Reference and the Trace Recording Session Reference in a trace log file or a notification (as the Trace Reference and the Trace Recording Session Reference are included in the trace record files from the eNodeBs).
+- Notification of available files containing trace records for retrieval by a collection point indicated by an IP address. The Trace Collection Entity may be part of the NM.
+- The network configuration (see the NRM IRPs in 3GPP TS 32.6xy and 32.7xy).
+
+## 5.2 Managing Trace Sessions
+
+The IRPManager shall be able to request the IRPAgent to:
+
+- Activate a Trace Session for a specific subscriber or equipment in a specific NE. The trace session activation shall be possible both for management based activation and for signalling based activation. The NM may schedule the activation. Note that no scheduling functionality is supported by the IRPAgent. The trace session activation shall also be possible for for cell traffic trace.
+- Make the Trace Records in a file available to a Trace Collection Entity. The data format of the file shall be specified in the 3GPP defined trace specifications (See 3GPP TS 32.423 [6]).
+- Emit a notification when a Trace Session is activated from the EM directly.
+- Emit a notification when a Trace Recording Session was not started in the NE for any reason.
+- Interrogate the configuration parameters and other information of a specific Trace Session.
+- Interrogate the list of activated Trace Sessions in a specific NE. The Trace Session is identified by the Trace Reference. In case of cell traffic trace the activated Trace Session can be requested for a Trace Reference or a cell identity.
+- Deactivate a Trace Session for a specific subscriber or equipment for a specific Trace Session. The trace session deactivation shall be possible for both management based activation and for signalling based activation. The NM may schedule the deactivation. Note that no scheduling functionality is supported by the IRPAgent. The Trace Session deactivation shall also be possible for for cell traffic trace.
+
+The Trace Session Deactivation shall target the same NE as the Trace Session Activation. If the trace session is activated in more than one NE, the trace session shall be deactivated in all those NEs. During Trace Session deactivation the Trace Reference and shall be given. In case of a failed Trace Session Deactivation there shall be a mechanism to ensure that unnecessary Trace Sessions will nor remain active in the network (i.e. send Trace Session Deactivation multiple times, etc.).
+
+The Trace Reference must be unique within the PLMNs where trace is requested when a Trace Session is activated.
+
+It shall be possible that an IRPManager activates/deactivates a Trace Session to multiple NEs for multiple subscribers or equipments.
+
+The IRPManager is responsible for scheduling the Trace Session Activation and Deactivation, i.e. there is no requirement on Itf-N due to scheduling the Trace Session Activation/Deactivation.
+
+## 5.3 Management of trace record files
+
+### 5.3.1 General
+
+The IRPManager shall be able to:
+
+- Request a list of available files.
+- Request the IRPAgents to emit a notification announcing the availability of the Trace Record files.
+
+For information:
+
+- The requirements for trace record file management may be satisfied by a separate File Transfer IRP.
+
+NOTE: In case of Signalling Based Activation the trace record files may be transferred from a different EM than the Trace Session Activation is sent to! In order to find always the appropriate collection point the IP address of Trace Collection Entity shall be part of the trace control and configuration parameter that needs to be propagated during Trace Session activations.
+
+### 5.3.2 Managing trace records for roaming cases (inter-operator cases)
+
+It is possible that Trace Session Activation/Deactivation goes across Operator's boundaries. Trace Records may contain sensible information therefore the exchange of trace records between operators are subject to agreements between operators, therefore this case is out of the scope of the present document.
+
+## 5.3A Void
+
+The requirements for managing MDT are in clause 6.
+
+## 5.4 Overview of IRPs related to Trace
+
+The Itf-N is built up by a number of IRPs. The basic structure of the IRPs is defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.150 [10].
+
+For the purpose of Trace the following IRPs are needed:
+
+- Trace Management IRP (TraceIRP), i.e. 3GPP TS 32.44x (the present TS-family).
+- File Transfer IRP (3GPP TS 32.34x [7], [8], [15]).
+- Notification IRP (3GPP TS 32.30x [11], [12], [16]).
+
+# 6 Requirements specific for managing MDT
+
+All requirements are valid for Logged MDT and Immediate MDT functionality if not mentioned otherwise:
+
+REQ-MDTMGMT-FUN-01 The IRPManager shall be able to configure MDT data collection for one or more IMEI(SV) number.
+
+REQ-MDTMGMT-FUN-02 The IRPManager shall be able to configure MDT data collection for one or more IMSI number.
+
+REQ-MDTMGMT-FUN-03 Each UE measurement result shall be linked to a time stamp. Accuracy of time information (absolute time, relative time) is FFS in RAN. (Editor's Note: FFS in RAN)
+
+REQ-MDTMGMT-FUN-04 The solutions for collecting UE measurements for the purpose of minimization of drive tests shall be able to work independently from SON support in the network.
+
+REQ-MDTMGMT-FUN-05 The IRPManager shall be able to configure MDT data collection in one or more cells or TA/RA/LA.
+
+REQ-MDTMGMT-FUN-06 The IRPManager shall be able to configure MDT data collection for one or more IMSI in one or more cells or TA/RA/LA.
+
+REQ-MDTMGMT-FUN-07 The IRPManager shall be able to configure MDT data collection for one or more IMEI(SV) in one or more cells or TA/RA/LA.
+
+REQ-MDTMGMT-FUN-08 The IRPManager shall be able to configure UE measurement types, and triggering conditions under which UE measurements would be collected for MDT.
+
+**Editor's note: The detailed list of triggering conditions is FFS.**
+
+REQ-MDTMGMT-FUN-09 The IRPManager shall be able to configure the condition of MDT data collection based on certain device capability information (e.g. required free memory, battery status, etc.) .
+
+**Editor's Note: the detailed list of device capabilities for MDT is FFS.**
+
+REQ-MDTMGMT-FUN-10 The IRPManager shall be able to configure the condition of MDT data collection based on certain device capability information in one or more cells or in TA/RA/LA.
+
+REQ-MDTMGMT-FUN-11 The IRPManager shall be able to configure MDT data collection based on one or more IMSI in one or more cells or TA/RA/LA with a set of device capability information.
+
+REQ-MDTMGMT-FUN-12 The IRPManager shall be able to configure MDT data collection based on one or more IMEI(SV) in one or more cells or TA/RA/LA with a set of device capability information.
+
+REQ-MDTMGMT-FUN-13 The IRPManager shall be able to configure MDT data collection based on one or more IMEI(SV) with a set of device capability information.
+
+REQ-MDTMGMT-FUN-14 The IRPManager shall be able to configure MDT data collection based on one or more IMSI with a set of device capability information.
+
+REQ-MDTMGMT-FUN-15 The IRPManager shall be able to configure the periodicity for collecting UE measurements to a centralized collection entity.
+
+REQ-MDTMGMT-FUN-16 The IRPManager shall have the capability allowing the IRPManager to activate combined tracing and UE MDT measurement collection within the same Trace Session.
+
+REQ-MDTMGMT-FUN-17 The IRPManager shall be able to deactivate MDT data collection by Trace Reference.
+
+REQ-MDTMGMT-FUN-18 The IRPManager shall be able to initiate MDT data collection independently from other mobility related performance measurement and call trace collection.
+
+REQ-MDTMGMT-FUN-19 It shall be possible for the IRPManager to notify the IRPManager if the UE selection can't fulfil operators' expectation.
+
+REQ-MDTMGMT-FUN-20 For area based MDT data collection, the IRPManager shall be able to configure the desired minimums over period of time for the amount of MDT data and for the number of UEs.
+
+REQ-MDTMGMT-FUN-21 For area based MDT data collection, the IRPManager shall be able to configure the desired maximums over period of time for the amount of MDT data and for the number of UEs.
+
+# --- 7 Requirements specific for managing RLF reporting
+
+REQ-RLFMTGMT-FUN-1 The IRPAgent shall provide the capability to allow the IRPManager to collect RLF reports independently from MDT or call trace collection.
+
+REQ-RLFMTGMT-FUN-2 The IRPAgent shall provide the capability to allow the IRPManager to collect RLF reports in one or more eNodeB(s).
+
+# Annex A (informative): Use Cases
+
+## A.1 General
+
+The use cases presented in the present document provides the usability of the Trace IRP. These use cases are different from those ones that are presented in 3GPP TS 32.421 [4].
+
+## A.2 Use case #1: Centralized place for Trace Session Activation in case of Management Based Activation
+
+Figure A.2-1 illustrates an example where Operator would like to activate a trace session in the 6 RNCs (example for system context A). The activation method required is Management Based Activation.
+
+
+
+```
+graph TD; NM[NM] -- Itf-n --> EM1[EM1]; NM -- Itf-n --> EM2[EM2]; NM -- Itf-n --> EM3[EM3]; EM1 --> RNC1[RNC1]; EM1 --> RNC2[RNC2]; EM2 --> RNC3[RNC3]; EM2 --> RNC4[RNC4]; EM3 --> RNC5[RNC5]; EM3 --> RNC6[RNC6];
+```
+
+Diagram illustrating Trace Session Activation for Management Based Activation. A Network Manager (NM) is connected to three Element Managers (EM1, EM2, EM3) via interfaces labeled 'Itf-n'. EM1 is connected to RNC1 and RNC2. EM2 is connected to RNC3 and RNC4. EM3 is connected to RNC5 and RNC6.
+
+**Figure A.2-1: Trace Session Activation for Management Based Activation**
+
+Using the trace IRP operator has to give the Trace Session Activation command in the Network Manager only. The Operator has to specify in which NEs trace is required and also has to give the trace control and configuration parameters. The NM (Trace IRP Manager) can initiate the Trace Session Activation to the EMs (Trace IRP Agents). The EMs can send the Trace Session Activation commands to the RNCs.
+
+As shown in this example Trace IRP helps the operator in managing trace in the network.
+
+## A.3 Use case #2: Centralized place to collect trace records in case of Signalling Based Activation
+
+Figure A.3-1 shows an example (assuming system context A) where trace records are generated in many different NEs which are managed by different EMs.
+
+
+
+```
+
+graph TD
+ NM[NM] -- "Trace Session Activation" --> EM1[EM1]
+ EM1 -- "Trace reporting" --> NM
+ EM2[EM2] -- "Trace reporting" --> NM
+ EM3[EM3] -- "Trace reporting" --> NM
+ EM1 --> MSC-S[MSC-S]
+ MSC-S --> MGW[MGW]
+ MSC-S --> RNC1[RNC1]
+ RNC1 --> RNC2[RNC2]
+ NM -- "Trace parameter propagation" --> EM1
+ EM1 --> MSC-S
+ EM1 --> MGW
+ EM1 --> RNC1
+ RNC1 --> RNC2
+
+```
+
+Diagram illustrating Trace Record Collection in case of Signalling Based Activation. The diagram shows a Network Management (NM) system at the top, connected to three Element Managers (EM1, EM2, EM3). EM1 is connected to an MSC-S, which is connected to an MGW and an RNC1. RNC1 is connected to an RNC2. Trace Session Activation is shown from NM to EM1. Trace reporting is shown from EM1, EM2, and EM3 to NM. Trace parameter propagation is shown from NM to EM1, then to MSC-S, MGW, and RNC1, and finally to RNC2.
+
+**Figure A.3-1: Trace Record Collection in case of Signalling Based Activation**
+
+In the example above the trace session is activated from the NM to the MSC-S via EM1. If the subscriber or MS that is being traced starts a call then the trace parameters are propagated to the MGW and to the RNC1.
+
+If during the call the subscriber makes a handover to RNC2, the trace parameters will also be propagated to RNC2.
+
+In this example all the NEs (MSC-S, MGW, RNC1 and RNC2) generate their own trace records and these trace records are sent to the NEs own EMs.
+
+There are three different EMs shown in the figure. Each of them will get the trace records from the NEs they manage. The EMs (traceIRPAgents) can then send the trace records to the NM (traceIRPManager).
+
+By using the TraceIRP the Operator can retrieve all the trace records generated in the network in one place at the NM.
+
+Without the trace IRP the trace records are stored only in the EM level, which in this case is distributed in 3 different boxes and locations.
+
+## A.4 Use case #3: Centralized place to collect trace records in case of Signalling Based Activation
+
+Figure A.4-1 shows an example (assuming system context A) where trace records are generated in many different NEs which are managed by different EMs.
+
+
+
+```
+
+graph TD
+ TCE[Trace Collection Entity]
+ EM1[EM]
+ EM2[EM]
+ EM3[EM3]
+ MME[MME]
+ eNB1[eNodeB1]
+ eNB2[eNodeB2]
+
+ TCE -.-> EM1
+ TCE -.-> EM2
+ TCE -.-> EM3
+ EM1 -.-> TCE
+ EM2 -.-> TCE
+ EM3 -.-> TCE
+ MME -.-> TCE
+ eNB1 -.-> TCE
+ eNB2 -.-> TCE
+
+ TCE --> MME : Trace Session Activation
+ MME --> eNB1 : Trace parameter propagation
+ MME --> eNB2 : Trace parameter propagation
+
+```
+
+Diagram illustrating Trace Record Collection in case of Signalling Based Activation. The diagram shows a Trace Collection Entity at the top, connected to three EMs (EM, EM, EM3) via dashed arrows labeled 'Trace reporting'. Below the EMs are network elements: MME, eNodeB1, and eNodeB2. Solid arrows show 'Trace Session Activation' from the Trace Collection Entity to the MME, and 'Trace parameter propagation' from the MME to eNodeB1 and eNodeB2. Dashed arrows show 'Trace reporting' from the EMs and network elements to the Trace Collection Entity.
+
+**Figure A.4-1: Trace Record Collection in case of Signalling Based Activation**
+
+In the example above the trace session is activated from the NM to the MME via EM2 -> EM1. If the subscriber or UE that is being traced starts a call then the trace parameters are propagated to the MME and to the eNodeB1. In the Trace configuration parameters is a Trace Collection Entity IP Address included.
+
+If during the call the subscriber makes a handover to eNodeB2, the trace parameters will also be propagated to eNodeB2.
+
+In this example all the NEs (MME, eNodeB1, eNodeB2) generate their own trace records and these trace records are sent to the NEs own EM.
+
+There are three different EMs shown in the figure. Each of them will get the trace records from the NEs they manage. The EMs (traceIRPAgents) can then send the trace records to the Trace Collection Entity which will be identified by the IP address which is included in the Trace configuration parameters (traceIRPManager). The Trace Collection entity may be located in the NM, EM or in another entity. The Trace files may also be sent directly from the nodes to the Trace Collection Entity.
+
+By using the TraceIRP the Operator can retrieve all the trace records generated in the network in one place, regardless of how many IRPManagers exist.
+
+Without the Trace Collection Entity in the Trace IRP the trace records are stored only in the EM level, which in the above example is distributed in 3 different nodes, or they might be sent to different IRPManagers in the NM.
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| Mar 2005 | SA_32 | SP-060256 | -- | -- | Submitted to SA#32 for Information | -- | 1.0.0 | |
+| Mar 2007 | SA_35 | SP-070063 | -- | -- | Submitted to SA#35 for Approval | -- | 2.0.0 | 7.0.0 |
+| Dec 2007 | SA_38 | SP-070735 | 0001 | 1 | R7 CR 32.441-700 Correction of Trace IRP | F | 7.0.0 | 7.1.0 |
+| Jun 2008 | SA_40 | SP-080329 | 0002 | -- | Introduction of EPC and E-UTRAN in Trace IRP | C | 7.1.0 | 8.0.0 |
+| Sep 2008 | SA_41 | SP-081261 | 0003 | -- | Inclusion of Notification IRP | C | 8.0.0 | 8.1.0 |
+| Dec 2009 | - | - | - | - | Update to Rel-9 version (MCC) | -- | 8.1.0 | 9.0.0 |
+| Sep 2010 | SA_49 | SP-100492 | 0004 | -- | Adding requirements for managing UE based network performance measurements | B | 9.0.0 | 10.0.0 |
+| Mar 2011 | SA_51 | SP-110102 | 0005 | -- | Change "UE based network performance measurements" to "MDT" - Align cross-3GPP terminology on MDT work | F | 10.0.0 | 10.1.0 |
+| Dec 2011 | SA_54 | SP-110716 | 0008 | 1 | Super CR combination for: Add RLF reporting use case and requirements, restructure MDT clause and Add requirements for MDT UE selection notification | B | 10.1.0 | 11.0.0 |
+| Mar 2012 | SA_55 | SP-120054 | 0009 | 1 | Add MDT data collection criteria requirements | B | 11.0.0 | 11.1.0 |
+| Sep 2012 | SA_57 | SP-120571 | 0010 | 1 | Clarify requirements on counting of distinct UEs | F | 11.1.0 | 11.2.0 |
+| Dec-2012 | SA_58 | SP-120795 | 0011 | 1 | Correction on the scope and reference related to MDT and RLF | F | 11.2.0 | 11.3.0 |
+| | | SP-120796 | 0012 | 1 | Addition of Network Sharing | C | | |
+| Jun 2015 | SA_68 | SP-150316 | 0018 | - | Remove IMS Service Level Trace | F | 11.3.0 | 11.4.0 |
\ No newline at end of file
diff --git a/marked/Rel-11/32_series/32446/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg b/marked/Rel-11/32_series/32446/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45f6091705d008803c6a469de571363c259060c3
--- /dev/null
+++ b/marked/Rel-11/32_series/32446/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ef4aab2b2594c9767f06a3b6c83fefff8214ea5c63ec41654f29d8b3564fb59
+size 63086
diff --git a/marked/Rel-11/32_series/32446/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/32_series/32446/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49f44f90363215fc7aa62fbeecaaca92290b6821
--- /dev/null
+++ b/marked/Rel-11/32_series/32446/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:551e748ef5d83e5a8726463d04b16796d0e60ee9454e202bb2809d23b202b038
+size 64583
diff --git a/marked/Rel-11/32_series/32446/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-11/32_series/32446/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b4a1217b63ebe79d68b429e0b16702c945da2c9
--- /dev/null
+++ b/marked/Rel-11/32_series/32446/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a2a4addefe18493fb5e1d7d7fdfb5318bc490a19eca6c57823ae6406a9f286d
+size 44082
diff --git a/marked/Rel-11/32_series/32446/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-11/32_series/32446/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82fd163b8521212f56c9098f72498f7e5456b146
--- /dev/null
+++ b/marked/Rel-11/32_series/32446/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b64890477c4df37522b4c595259e3c53d2565609cca6304476a7f71ee0791ee
+size 74021
diff --git a/marked/Rel-11/32_series/32446/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-11/32_series/32446/e90987faabad6a6665cd8ed1151dc474_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..312bcf2aec398f4e330d81e1e3b3098567576ab3
--- /dev/null
+++ b/marked/Rel-11/32_series/32446/e90987faabad6a6665cd8ed1151dc474_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d7385554bc736040d39d3b8ebde925ca5f0a261db6700aaec02cc864d56ec40
+size 27252
diff --git a/marked/Rel-11/32_series/32446/raw.md b/marked/Rel-11/32_series/32446/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f9db0456379f8db7ed63d513098856b6165406d6
--- /dev/null
+++ b/marked/Rel-11/32_series/32446/raw.md
@@ -0,0 +1,2180 @@
+
+
+
+
+Error! No
+text of
+
+Error! No text of specified style in
+document.
+
+# Contents
+
+| | |
+|-----------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Solution Set definitions ..... | 8 |
+| Annex A (normative): CORBA Solution Set..... | 9 |
+| A.1 Architectural features..... | 9 |
+| A.1.1 Syntax for Distinguished Names..... | 9 |
+| A.1.2 Notification Services..... | 9 |
+| A.1.3 Push and Pull Style..... | 9 |
+| A.1.4 Support multiple notifications in one push operation ..... | 9 |
+| A.1.5 Trace Management Notification Interface ..... | 9 |
+| A.1.5.1 Method push (M)..... | 9 |
+| A.2 Mapping ..... | 10 |
+| A.2.1 Operation and Notification mapping..... | 10 |
+| A.2.2 Operation parameter mapping..... | 10 |
+| A.2.3 Notification parameter mapping..... | 12 |
+| A.3 Solution Set definitions ..... | 17 |
+| A.3.1 IDL definition structure..... | 17 |
+| A.3.2 IDL specification (file name "TraceIRPConstDefs.idl") ..... | 18 |
+| A.3.3 IDL specification (file name "TraceIRPSystem.idl") ..... | 21 |
+| A.3.4 IDL specification (file name "TraceIRPNotifications.idl") ..... | 23 |
+| Annex B (normative): XML definitions..... | 25 |
+| B.1 Architectural Features..... | 25 |
+| B.1.1 Syntax for Distinguished Names..... | 25 |
+| B.1.2 Notification Services..... | 25 |
+| B.1.3 IOC definitions..... | 25 |
+| B.2 Mapping ..... | 25 |
+| B.3 Solution Set definitions ..... | 25 |
+| B.3.1 XML definition structure ..... | 25 |
+| B.3.2 Graphical Representation ..... | 26 |
+| B.3.3 XML Schema "tMIRPNotif.xsd"..... | 28 |
+| B.3.4 XML Schema "tMIRPIOCs.xsd"..... | 30 |
+| Annex C (normative): SOAP Solution Set..... | 35 |
+| C.1 Architectural features..... | 35 |
+| C.1.1 Syntax for Distinguished Names..... | 35 |
+| C.1.2 Notification Services..... | 35 |
+| C.1.3 Supported W3C specifications..... | 35 |
+| C.1.4 Prefixes and namespaces..... | 35 |
+| C.2 Mapping ..... | 36 |
+| C.2.1 Operation and notification mapping..... | 36 |
+| C.2.2 Operation parameter mapping..... | 36 |
+| C.2.3 Notification parameter mapping..... | 38 |
+| C.3 Solution Set definitions ..... | 39 |
+| C.3.1 WSDL definition structure ..... | 39 |
+
+C.3.2 Graphical Representation ..... 39
+C.3.3 WSDL specification “TraceIRPSystem.wsdl” ..... 40
+Annex D (informative): Change history..... 46
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+ - 1 presented to TSG for information;
+ - 2 presented to TSG for approval;
+ - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.441 "Trace Management Integration Reference Point (IRP): Requirements".
+- 32.442 "Trace Management Integration Reference Point (IRP): Information Service (IS)".
+- 32.446 "Trace Management Integration Reference Point (IRP): Solution Set (SS) definitions".**
+
+The present document is part of a TS-family which describes the information service necessary for the Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 [2] and 3GPP TS 32.102 [3].
+
+Trace provides very detailed information on call level for a specific subscriber or MS. This data is an additional information source to Performance Measurements and allows deeper investigations in problems solving or in case of optimization.
+
+# --- 1 Scope
+
+The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Trace Management IRP: Information Service (3GPP TS 32.442 [5]). This specification is applicable to UMTS networks and EPS networks. GSM Trace is outside of the scope of this specification.
+
+The conditions for supporting Network Sharing are stated in 3GPP TS 32.441 [6].
+
+This Solution Set specification is related to 3GPP TS 32.442 V11. 5.X.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [3] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [4] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [5] 3GPP TS 32.442: "Telecommunication management; Trace Management Integration Reference Point (IRP): Information Service (IS)".
+- [6] void.
+- [7] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP): Requirements".
+- [8] void.
+- [9] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+- [10] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions".
+- [11] void.
+- [12] OMG TC Document telecom/98-11-01: "OMG Notification Service".
+
+- [13] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
+- [14] W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
+- [15] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
+- [16] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
+- [17] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
+
+- [18] void.
+ - [19] void.
+ - [20] void.
+ - [21] W3C SOAP 1.1 specification ()
+ - [22] W3C XPath 1.0 specification ()
+ - [23] W3C WSDL 1.1 specification ()
+ - [24] W3C SOAP 1.2 specification ()
+-
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], 3GPP TS 32.101 [2], 3GPP TS 32.102 [3], 3GPP TS 32.150 [4] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**IRP document version number string (or "IRPVersion"):** See 3GPP TS 32.311 [7].
+
+**IRP:** See 3GPP TS 32.101 [2].
+
+**IRP Agent:** See 3GPP TS 32.102 [3].
+
+**IRP Manager:** See 3GPP TS 32.102 [3].
+
+**XML file:** file containing an XML document
+
+**XML document:** composed of the succession of an optional XML declaration followed by a root XML element, see [14].
+
+**XML declaration:** it specifies the version of XML being used, see [14].
+
+**XML element:** has a type, is identified by a name, may have a set of XML attribute specifications and is either composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements, see [14].
+
+**empty XML element:** having an empty XML content; an empty XML element still possibly has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag, see [14].
+
+**XML content (of an XML element):** empty if the XML element is simply composed of an XML empty-element tag; otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag, see [14].
+
+**XML start-tag:** the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML element, see [14].
+
+**XML end-tag:** the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element, see [14].
+
+**XML empty-element tag:** composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element, see [14].
+
+**XML attribute specification:** has a name and a value, see [14].
+
+**DTD:** defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD, see [14].
+
+**XML schema:** more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document to conform with this XML schema; through the use of XML namespaces several XML schemas
+
+can be used together by a single XML document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas, see [15], [16] and [17].
+
+**XML namespace:** enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas, see [15], [16] and [17].
+
+**XML complex type:** defined in an XML schema; cannot be directly used in an XML document; can be the concrete type or the derivation base type for an XML element type or for another XML complex type; ultimately defines constraints for an XML element on its XML attribute specifications and/or its XML content, see [15], [16] and [17].
+
+**XML element type:** declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type, see [15], [16] and [17].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1], in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3], 3GPP TS 32.150 [4], and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+| | |
+|-------|-------------------------------------------|
+| CM | Configuration Management |
+| CORBA | Common Object Request Broker Architecture |
+| DN | Distinguished Name |
+| EM | Element Manager |
+| IDL | Interface Definition Language |
+| IRP | Integration Reference Point |
+| Itf-N | Interface N |
+| IS | Information Service |
+| MDT | Minimization of Drive Tests |
+| MOC | Managed Object Class |
+| NE | Network Element |
+| OMG | Object Management Group |
+| RLF | Radio Link Failure |
+| SS | Solution Set |
+| TS | Technical Specification |
+
+# --- 4 Solution Set definitions
+
+This specification defines the following 3GPP Trace Management IRP Solution Set definitions:
+
+Annex A provides the CORBA Solution Set.
+
+Annex B provides the XML definitions.
+
+Annex C provides the SOAP Solution Set.
+
+# Annex A (normative): CORBA Solution Set
+
+This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Trace Management IRP: Information Service (3GPP TS 32.442 [5]).
+
+## A.1 Architectural features
+
+The overall architectural feature of Trace Management IRP is specified in 3GPP TS 32.442 [5].
+
+### A.1.1 Syntax for Distinguished Names
+
+The format of a Distinguished Name is defined in 3GPP TS 32.300 [9].
+
+The version of this IRP is represented as a string (see also clause 3 for versions).
+
+### A.1.2 Notification Services
+
+Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.306 [10]).
+
+The contents of the TraceIRP notifications are defined in the present document.
+
+### A.1.3 Push and Pull Style
+
+OMG Notification Service defines two styles of interaction. One is called push style. In this style, IRP Agent pushes notifications to IRP Manager as soon as they are available. The other is called pull style. In this style, IRP Agent keeps the notifications till IRP Manager requests for them.
+
+This CORBA SS specifies that support of Push style is Mandatory (M) and that support of Pull style is Optional (O).
+
+### A.1.4 Support multiple notifications in one push operation
+
+For efficiency reasons, IRP Agent may send multiple notifications using one single push operation. To pack multiple notifications into one push operation, IRP Agent may wait and not invoke the push operation as soon as notifications are available. To avoid IRP Agent to wait for an extended period of time that is objectionable to IRP Manager, IRP Agent shall implement an IRP Agent wide timer configurable by administrator. On expiration of this timer, IRP Agent shall invoke push if there is at least one notification to be conveyed to IRP Manager. This timer is re-started after each push invocation.
+
+### A.1.5 Trace Management Notification Interface
+
+OMG CORBA Notification push operation is used to realise the notification of TraceIRP Notifications. All the notifications in this interface are implemented using this `push_structured_event` method.
+
+#### A.1.5.1 Method `push` (M)
+
+```
+module CosNotifyComm {
+...
+Interface SequencePushConsumer : NotifyPublish {
+void push_structured_events(
+in CosNotification::EventBatch notifications)
+raises( CosEventComm::Disconnected);
+...
+}; // SequencePushConsumer
+...
+}; // CosNotifyComm
+```
+
+- NOTE 1: The push\_structured\_events method takes an input parameter of type EventBatch as defined in the OMG CosNotification module (OMG Notification Service [12]). This data type is the same as a sequence of Structured Events. Upon invocation, this parameter will contain a sequence of Structured Events being delivered to IRPManager by IRPAgent to which it is connected.
+- NOTE 2: The maximum number of events that will be transmitted within a single invocation of this operation is controlled by IRPAgent wide configuration parameter.
+- NOTE 3: The amount of time the supplier (IRPAgent) of a sequence of Structured Events will accumulate individual events into the sequence before invoking this operation is controlled by IRPAgent wide configuration parameter as well.
+- NOTE 4: IRPAgent may push EventBatch with only one Structured Event..
+
+## A.2 Mapping
+
+### A.2.1 Operation and Notification mapping
+
+TraceIRP: IS 3GPP TS 32.442 [5] defines semantics of operation and notification visible across the TraceIRP. Table A.2.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
+
+**Table A.2.1: Mapping from IS Operations and Notification to SS equivalents**
+
+| IS Operations/ notification 3GPP TS 32.442 [5] | SS Method | Qualifier |
+|------------------------------------------------|------------------------------------------------|-----------|
+| activateTraceJob | activate_trace_job | M |
+| deactivateTraceJob | deactivate_trace_job | M |
+| listTraceJob | list_trace_job | M |
+| listActivatedTraceJob | list_activitated_trace_job | M |
+| notifyTraceRecordingSessionFailure | push_structured_events(See subclause A.1.5.1) | O |
+| notifyTraceSessionLocalActivation | push_structured_events (See subclause A.1.5.1) | O |
+
+### A.2.2 Operation parameter mapping
+
+The TraceIRP: IS 3GPP TS 32.442 [5] defines semantics of parameters carried in operations across the TraceIRP. The following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table A.2.2.1: Mapping from IS activateTraceJob parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iocInstance | KernelCmConstDefs::DN molInstance | M |
+| listOfInterfaces | TraceIRPConstDefs::ListOfInterfaces list_of_interfaces | O |
+| listOfNeTypes | TraceIRPConstDefs::ListOfNeTypes list_of_ne_types | CM |
+| traceDepth | TraceIRPConstDefs::TraceDepth trace_depth | M |
+| traceReference | TraceIRPConstDefs::TraceReference trace_reference | M |
+| traceTarget | TraceIRPConstDefs::TraceTarget trace_target | M |
+| triggeringEvent | TraceIRPConstDefs::TriggeringEvent triggering_event | CO |
+| traceCollectionEntityAddresses | TraceIRPConstDefs::TraceCollectionEntityAddress trace_collection_entity_address | CM |
+| jobType | TraceIRPConstDefs::JobType job_type | M |
+| areaScope | TraceIRPConstDefs::DNSet | CM |
+| listOfMeasurements | TraceIRPConstDefs::ListOfMeasurements list_of_measurements | CM |
+| reportingTrigger | TraceIRPConstDefs::ReportingTrigger reporting_trigger | CM |
+| reportInterval | TraceIRPConstDefs::ReportInterval report_interval | CM |
+| reportAmount | TraceIRPConstDefs::ReportAmount report_amount | CM |
+| eventThreshold | TraceIRPConstDefs::EventThreshold event_threshold | CM |
+| loggingInterval | TraceIRPConstDefs::LoggingInterval logging_interval | CM |
+| loggingDuration | TraceIRPConstDefs::LoggingDuration logging_duration | CM |
+| anonymizationOfMDTData | TraceIRPConstDefs::AnonymizationOfMDTData anonymization_Of_MDT_Data | CM |
+| measurementQuantity | TraceIRPConstDefs::MeasurementQuantity measurement_quantity | CM |
+| measurementPeriodLTE | TraceIRPConstDefs::MeasurementPeriodLTE measurement_period_lte | CM |
+| measurementPeriodUMTS | TraceIRPConstDefs::MeasurementPeriodUMTS measurement_period_umts | CM |
+| collectionPeriodRrmUmts | TraceIRPConstDefs::CollectionPeriodRrmUmts collection_period_rrm_umts | CM |
+| collectionPeriodRrmLte | TraceIRPConstDefs::CollectionPeriodRrmLte collection_period_rrm_lte | CM |
+| positioningMethod | TraceIRPConstDefs::PositioningMethod positioning_method | CO |
+| unsupportedList | TraceIRPConstDefs::UnsupportedList unsupportedList | M |
+| status | Return value of type TraceIRPConstDefs::Result
Exception:
ActivateTraceJob, InvalidTraceDepth, InvalidTraceTarget,
NotUniqueTraceReference
ManagedGenericIRPSystem::InvalidParameter,
ManagedGenericIRPSystem::ParameterNotSupported | M |
+| pLMNTarget | TraceIRPConstDefs::PLMNTarget pLMN_target | CM |
+
+**Table A.2.2.2: Mapping from IS deactivateTraceJob parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|--------------------------------|-------------------------------------------------------------------------------------------------------------|-----------|
+| traceReference | TraceIRPConstDefs::TraceReference trace_reference | M |
+| traceTarget | TraceIRPConstDefs::TraceTarget trace_target | M |
+| status | Return value of type TraceIRPConstDefs::Result
Exception:
DeactivateTraceJob, NotUniqueTraceReference | M |
+| traceRecordingSessionReference | TraceIRPConstDefs::TraceRecordingSessionReference trace_recording_session_reference | CM |
+
+**Table A.2.2.3: Mapping from IS listTraceJob parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|--------------------------------|-------------------------------------------------------------------------------------------------------|-----------|
+| traceReference | TraceIRPConstDefs::TraceReference trace_reference | M |
+| status | Return value of type TraceIRPConstDefs::Result
Exception:
ListTraceJob, NotUniqueTraceReference | M |
+| ioInstance | KernelCmConstDefs::DN ioInstance | M |
+| listOfInterfaces | TraceIRPConstDefs::ListOfInterfaces list_of_interfaces | O |
+| traceDepth | TraceIRPConstDefs::TraceDepth trace_depth | M |
+| traceRecordingSessionReference | TraceIRPConstDefs::TraceRecordingSessionReference
trace_recording_session_reference | CM |
+| traceTarget | TraceIRPConstDefs::TraceTarget trace_target | M |
+| jobType | TraceIRPConstDefs::JobType job_type | M |
+| areaScope | TraceIRPConstDefs::DNSet | CM |
+| listOfMeasurements | TraceIRPConstDefs::ListOfMeasurements list_of_measurements | CM |
+| reportingTrigger | TraceIRPConstDefs::ReportingTrigger reporting_trigger | CM |
+| reportInterval | TraceIRPConstDefs::ReportInterval report_interval | CM |
+| reportAmount | TraceIRPConstDefs::ReportAmount report_amount | CM |
+| eventThreshold | TraceIRPConstDefs::EventThreshold event_threshold | CM |
+| loggingInterval | TraceIRPConstDefs::LoggingInterval logging_interval | CM |
+| loggingDuration | TraceIRPConstDefs::LoggingDuration logging_duration | CM |
+| triggeringEvent | TraceIRPConstDefs::TriggeringEvent triggering_event | O |
+| traceCollectionEntityAddress | TraceIRPConstDefs::TraceCollectionEntityAddress
trace_collection_entity_address | CM |
+| anonymizationOfMDTData | TraceIRPConstDefs::AnonymizationOfMDTData
anonymization_of_mdt_data | CM |
+| measurementQuantity | TraceIRPConstDefs::MeasurementQuantity measurement_quantity | CM |
+| measurementPeriodLTE | TraceIRPConstDefs::MeasurementPeriodLTE measurement_period_lte | CM |
+| measurementPeriodUMTS | TraceIRPConstDefs::MeasurementPeriodUMTS measurement_period_ umts | CM |
+| collectionPeriodRrmUmts | TraceIRPConstDefs::CollectionPeriodRrmUmts
collection_period_rrm_umts | CM |
+| collectionPeriodRrmLte | TraceIRPConstDefs::CollectionPeriodRrmLte collection_period_rrm_lte | CM |
+| positioningMethod | TraceIRPConstDefs::PositioningMethod positioning_method | CO |
+| pLMNTarget | TraceIRPConstDefs::PLMNTarget pLMN_target | CM |
+
+**Table A.2.2.4: Mapping from IS listActivatedTraceJobs parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------|-----------|
+| traceReferenceList | TraceMIRPConstDefs::TraceReferenceList trace_reference_list | M |
+| status | Return value of type TraceIRPConstDefs::Result | M |
+
+### A.2.3 Notification parameter mapping
+
+The TraceIRP: IS 3GPP TS 32.442 [5] defines semantics of parameters carried in notifications. The following table indicates the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification Service [12]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [12], is:
+
+```
+Header
+ Fixed Header
+ domain_name
+ type_name
+ event_name
+ Variable Header
+```
+
+Body
+
+filterable\_body\_fields
+remaining\_body
+
+The following tables list all OMG Structured Event attributes in the second column. The first column identifies the TraceIRP: IS 3GPP TS 32.442 [5] defined notification parameters.
+
+Table A.2.3.1: Mapping for **notifyTraceRecordingSessionFailure**
+
+| IS Parameters | OMG CORBA Structured Event attribute | Qualifier | Comment |
+|-----------------------------------------|---------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| There is no corresponding IS attribute. | domain_name | M | It carries the IRP document version number string. See subclause 3.1.
It indicates the syntax and semantics of the Structured Event as defined by the present document. |
+| notificationType | type_name | M | This is constant string "notifyTraceRecordingSessionFailure". |
+| There is no corresponding IS attribute. | event_name | M | It carries no information. |
+| There is no corresponding IS attribute. | Variable Header | | |
+| objectClass, objectInstance | One NV pair of filterable_body_fields | M | NV stands for name-value pair. Order arrangement of NV pairs is not significant. The name of NV-pair is always encoded in string.
Name of this NV pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| notificationId | One NV pair of remaining_body | M | Name of NV pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a long. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| eventTime | One NV pair of filterable_body_fields | M | Name of NV pair is the EVENT_TIME of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is IRPTime. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| systemDN | One NV pair of filterable_body_fields | M | Name of NV pair is the SYSTEM_DN of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| traceRecordingSessionReference | One NV pair of remaining_body | O | Name of NV pair is the TRACE_RECORDING_SESSION_REFERENCE of TraceIRPNotifications::notifyTraceRecordingSessionFailure.
Value of NV pair is TraceRecordingSessionReference of module TraceIRPConstDefs. |
+| traceReference | One NV pair of filterable_body_fields | M | Name of NV pair is the TRACE_REFERENCE of TraceIRPNotifications::notifyTraceRecordingSessionFailure.
Value of NV pair is TraceReference of module TraceIRPConstDefs. |
+| reason | One NV pair of remaining_body | O | Name of NV pair is the REASON of traceIRPNotifications:: notifyTraceRecordingSessionFailure.
Value of NV pair is a string. |
+
+Table A.2.3.2: Mapping for **notifyTraceSessionLocalActivation**
+
+| IS Parameters | OMG CORBA Structured Event attribute | Qualifier | Comment |
+|-----------------------------------------|---------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| There is no corresponding IS attribute. | domain_name | M | It carries the IRP document version number string. See subclause 3.1.
It indicates the syntax and semantics of the Structured Event as defined by the present document. |
+| notificationType | type_name | M | This is constant string "notifyThresholdMonitorObjectCreation". |
+| There is no corresponding IS attribute. | event_name | M | It carries no information. |
+| There is no corresponding IS attribute. | Variable Header | | |
+| objectClass, objectInstance | One NV pair of filterable_body_fields | M | NV stands for name-value pair. Order arrangement of NV pairs is not significant. The name of NV-pair is always encoded in string.
Name of this NV pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| notificationId | One NV pair of remaining body | M | Name of NV pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a long. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| eventTime | One NV pair of filterable_body_fields | M | Name of NV pair is the EVENT_TIME of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is IRPTime. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| systemDN | One NV pair of filterable_body_fields | M | Name of NV pair is the SYSTEM_DN of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| traceReference | One NV pair of filterable_body_fields | M | Name of NV pair is the TRACE_REFERENCE of module TraceIRPNotifications::notifyTraceSessionLocalActivation.
Value of NV pair is TraceReference of module TraceIRPConstDefs. |
+| traceTarget | One NV pair of filterable_body_fields | M | Name of NV pair is the TRACE_TARGET of module TraceIRPNotifications::notifyTraceSessionLocalActivation.
Value of NV pair is TraceTarget of module TraceIRPConstDefs. |
+| iOCInstance | One NV pair of filterable_body_fields | M | Name of NV pair is the IOC_INSTANCE of module TraceIRPNotifications::notifyTraceSessionLocalActivation.
Value of NV pair is MOClassName of module TraceIRPConstDefs. |
+
+Table A.2.3.3: Mapping for notifyTraceSessionIdentities
+
+| IS Parameters | OMG CORBA Structured Event attribute | Qualifier | Comment |
+|-----------------------------------------|---------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| There is no corresponding IS attribute. | domain_name | M | It carries the IRP document version number string. See subclause 3.1.
It indicates the syntax and semantics of the Structured Event as defined by the present document. |
+| notificationType | type_name | M | This is constant string "notifyTraceSessionIdentities". |
+| There is no corresponding IS attribute. | event_name | M | It carries no information. |
+| There is no corresponding IS attribute. | Variable Header | | |
+| objectClass, objectInstance | One NV pair of filterable_body_fields | M | NV stands for name-value pair. Order arrangement of NV pairs is not significant. The name of NV-pair is always encoded in string.
Name of this NV pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| notificationId | One NV pair of remaining body | M | Name of NV pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a long. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| eventTime | One NV pair of filterable_body_fields | M | Name of NV pair is the EVENT_TIME of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is IRPTime. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| systemDN | One NV pair of filterable_body_fields | M | Name of NV pair is the SYSTEM_DN of interface AttributeNameValue of module NotificationIRPConstDefs.
Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [10]). |
+| traceReference | One NV pair of filterable_body_fields | M | Name of NV pair is the TRACE_REFERENCE of module TraceIRPNotifications::notifyTraceSessionLocalActivation .
Value of NV pair is TraceReference of module TraceIRPConstDefs. |
+| traceRecordingSessionReference | One NV pair of filterable_body_fields | M | Name of NV pair is the TRACE_RECORDING_SESSION_REFERENCE of TraceIRPNotifications::notifyTraceSessionIdentities
Value of NV pair is TraceReference of module TraceIRPConstDefs. |
+| traceTarget | One NV pair of filterable_body_fields | M | Name of NV pair is the TRACE_TARGET of module TraceIRPNotifications::notifyTraceSessionIdentities.
Value of NV pair is TraceTarget of module TraceIRPConstDefs. |
+| iOCInstance | One NV pair of filterable_body_fields | M | Name of NV pair is the IOC_INSTANCE of module TraceIRPNotifications::notifyTraceSessionIdentities.
Value of NV pair is MOClassName of module TraceIRPConstDefs. |
+
+## --- A.3 Solution Set definitions
+
+### A.3.1 IDL definition structure
+
+Clause A.3.2 defines the constants and types used by the Trace Management IRP.
+
+Clause A.3.3 defines the operations which are performed by the Trace Management IRP agent.
+
+Clause A.3.4 defines the notifications which are emitted by the Trace Management IRP agent.
+
+### A.3.2 IDL specification (file name "TraceIRPConstDefs.idl")
+
+```
+
+//File: TraceIRPConstDefs.idl
+#ifndef _Trace_IRP_CONST_DEFS_IDL_
+#define _Trace_IRP_CONST_DEFS_IDL_
+#include
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: TraceIRPConstDefs
+This module contains commonly used definitions for Trace IRP
+=====
+*/
+module TraceIRPConstDefs
+{
+
+ enum Result Enum {OK, FAILURE, PARTIAL_SUCCESS};
+
+ typedef struct TraceReference
+ {
+ short mcc;
+ short mnc;
+ unsigned long traceId;
+ };
+ typedef sequence TraceReferenceList;
+
+ typedef unsigned long TraceRecordingSessionReference;
+
+ typedef string TraceCollectionEntityAddress;
+
+ /* the values of the InterfaceBitmap is coming from the ListOfInterfaces trace parameter definition
+in 3GPP TS 32.422. The InterfaceBitmap shall carry the decimal value that is calculated from the
+bitmap, defined in TS 32.422.*/
+ typedef struct Interfaces
+ {
+ NeType NetworkElement;
+ Integer InterfaceBitmap;
+ };
+ typedef sequence ListOfInterfaces;
+
+ /*
+ListOfInterfacesOptional is a type carrying a conditional parameter.
+The boolean shall be TRUE, if the operation request uses this parameter. In this case the value is
+present. Otherwise the value is absent.
+*/
+ union ListOfInterfacesOptional switch (boolean)
+ {
+ case TRUE: ListOfInterfaces value;
+ };
+
+ enum NeType {MSC_SERVER, MGW, RNC, SGSN, GGSN, BM_SC, eNB, MME, SGW, PGW };
+
+ typedef sequence ListOfNeTypes;
+
+ enum TraceDepth {MINIMUM, MEDIUM, MAXIMUM, VENDORMINIMUM, VENDORMEDIUM, VENDORMAXIMUM};
+
+ enum TraceTargetType {IMSI, IMEI, IMEISV, PUBLIC_ID, UTRAN_CELL, E-UTRAN_CELL, eNB, RNC};
+
+ typedef struct TraceTarget
+ {
+ TraceTargetType typeFlag;
+ String traceTargetId;
+ };
+
+ enum JobType {IMMEDIATE_MDT_ONLY, LOGGED_MDT_ONLY, TRACE_ONLY, IMMEDIATE_MDT_TRACE, RLF_REPORT_ONLY,
+RCEF_REPORT_ONLY };
+ typedef sequence DNSet;
+
+```
+
+```
+enum ReportAmount {1,2,4,8,16,32,64,INFINITY};
+enum ReportInterval
+{250ms, 500ms, 1000ms, 2000ms, 3000ms, 4000ms, 6000ms, 8000ms, 12000ms, 16000ms, 20000ms, 24000ms, 28000ms, 32000
+ms, 64000ms, 120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 60000ms, 360000ms, 720000ms, 1800000ms,
+3600000ms};
+enum LoggingInterval {1.28s, 2.56s, 5.12s, 10.24s, 20.48s, 30.72s, 40.96s, 61.44s};
+enum LoggingDuration {600s, 1200s, 2400s, 3600s, 5400s, 7200s};
+enum AnonymizationOfMDTData {NO_Identity, TAC_of_IMEI};
+
+/* the values of the EventBitmap is coming from the TriggeringEvent trace parameter definition in
+3GPP TS 32.422. The EventBitmap shall carry the decimal value that is calculated from the
+triggering event bitmap as defined in TS 32.422.*/
+
+typedef struct Events
+{
+ NeType NetworkElement;
+ Integer EventBitmap;
+};
+typedef sequence TriggeringEvent;
+
+/*
+MeasurementsBitMap is used for MDT measurements item selection. Define it as a type of Integer means
+the selection is mapped into each bit of total 16 bit, as defined in 32.422 Claus 5.
+*/
+
+/* the values of the MeasurementsBitMap is coming from the TriggeringEvent trace parameter
+definition in 3GPP TS 32.422. The MeasurementsBitMap shall carry the decimal value that is
+calculated from the MDT Measurements bitmap as defined in TS 32.422.*/
+
+enum MobileTechType {UMTS, LTE};
+typedef struct Measurements
+{
+ MobileTechType MobilityTech;
+ Integer MeasurementsBitMap;
+};
+typedef sequence ListOfMeasurements;
+
+/* Event threshold parameter carries the threshold values used to event triggered MDT reporting. In
+LTE case either the EventThreshold RSRP or EventThresholdRSRQ is selected, in UMTS either
+EventThreshold1F or EventThreshold1I is selected. */
+
+union EventThreshold switch (long)
+{
+ case 0:
+ integer EventThresholdRSRP;
+ case 1:
+ integer EventThresholdRSRQ;
+ case 2:
+ integer EventThreshold1F;
+ case 3:
+ integer EventThreshold1I;
+}
+
+/* the values of the MeasurementQuantity is coming from the MeasurementQuantity MDT parameter
+definition in 3GPP TS 32.422. The MeasurementsQuantity shall carry the decimal value that is
+calculated from the MDT Measurement Quantity bitmap as defined in TS 32.422.*/
+
+Integer MeasurementQuantity;
+
+/*
+ReportingTriggerBitMap is used for MDT measurements reporting. Define it as a type of Integer means
+the reporting mechanism is mapped into each bit of total 8 bit, as defined in 32.422 Claus 5.
+*/
+
+/* the values of the ReportingTriggerBitMap is coming from the TriggeringEvent trace parameter
+definition in 3GPP TS 32.422. The ReportingTriggerBitMap shall carry the decimal value that is
+calculated from the MDT Measurements bitmap as defined in TS 32.422.*/
+
+typedef struct ReportingTrigger
+{
+ MobileTechType MobilityTech;
+ Integer ReportingTriggerBitMap;
+};
+
+/*
+TriggeringEventConditional is a type carrying a conditional parameter.
+```
+
+-----
+
+-----
+
+The boolean shall be TRUE, if the operation the condition is fulfilled and the request uses this parameter. In this case the value is present. Otherwise the value is absent.
+
+\*/
+
+union TriggeringEventConditional switch (boolean)
+
+{
+case TRUE: TriggeringEvent value;
+};
+
+enum measurementPeriodLTE {1024ms, 1280ms, 2048ms, 2560ms, 5120ms, 10240ms, 1min};
+
+enum measurementPeriodUMTS {250ms, 500ms, 1000ms, 2000ms, 3000ms, 4000ms, 6000ms, 8000ms, 12000ms, 16000ms, 20000ms, 24000ms, 28000ms, 32000ms, 64000ms};
+
+enum collectionPeriodRrmUmts {250ms, 500ms, 1000ms, 2000ms, 3000ms, 4000ms, 6000ms, 8000ms, 12000ms, 16000ms, 20000ms, 24000ms, 28000ms, 32000ms, 64000ms};
+
+enum collectionPeriodRrmLte {1024ms, 1280ms, 2048ms, 2560ms, 5120ms, 10240ms, 1min};
+
+/\*
+
+PositioningMethod is used for MDT measurements reporting. Define it as a type of Integer means the reporting mechanism is mapped into each bit of total 8 bit, as defined in 32.422 Clause 5.
+
+\*/
+
+Integer PositioningMethod;
+
+enum UnsupportedItem {MANAGED\_ENTITY, TRACE\_DEPTH, LIST\_OF\_INTERFACES, TRACE\_TARGET, MDT\_AREA\_SCOPE, LIST\_OF\_MEASUREMENTS, REPORTING\_TRIGGER, REPORT\_INTERVAL, REPORT\_AMOUNT, EVENT\_THRESHOLD, LOGGING\_INTERVAL, LOGGING\_DURATION, ANONYMIZATION\_OF\_MDT\_DATA, MEASUREMENT\_PERIOD\_LTE, MEASUREMENT\_PERIOD\_UMTS, COLLECTION\_PERIOD\_RRM\_UMTS, COLLECTION\_PERIOD\_RRM\_LTE, POSITIONING\_METHOD, REASON};
+
+typedef sequence UnsupportedList;
+
+/\*\*
+
+\* This block identifies attributes which are included as part of the
+\* notifications defined within TraceIRP. These attribute values should not
+\* clash with those defined for the attributes of notification
+\* header (see IDL of Notification IRP).
+\*/
+
+interface AttributeNameValue
+
+{
+const string TRACE\_RECORDING\_SESSION\_REFERENCE = "TRACE\_RECORDING\_SESSION\_REFERENCE";
+const string TRACE\_REFERENCE = "TRACE\_REFERENCE";
+const string TRACE\_TARGET = "TRACE\_TARGET";
+const string MO\_INSTANCE = "MO\_INSTANCE";
+const string REASON = "REASON";
+};
+
+};
+
+### A.3.3 IDL specification (file name “TraceIRPSystem.idl”)
+
+```
+
+//File: TraceIRPSystem.idl
+#ifndef _TRACE_IRP_SYSTEM_IDL_
+#define _TRACE_IRP_SYSTEM_IDL_
+
+#include
+#include
+#include #include
+
+//This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* Module: TraceIRPSystem
+This module contains the specification of all operations of Trace IRP Agent.
+=====
+*/
+module TraceIRP
+{
+ exception ActivateTraceJob { string reason; };
+ exception NotUniqueTraceReference { string reason; };
+ exception DeactivateTraceJob { string reason; };
+ exception ListTraceJob { string reason; };
+ exception ListActivatedTraceJob { string reason; };
+
+ interface TraceIRP
+ {
+ /**
+ * Request to activate a TraceJob through Itf-N.
+ **/
+ TraceIRPConstDefs::ResultEnum activateTraceJob (
+ in KernelCmConstDefs::DN moInstance,
+ in TraceIRPConstDefs::ListOfInterfacesOptional listOfInterfaces,
+ in TraceIRPConstDefs::ListOfNeTypes listOfNeTypes,
+ in TraceIRPConstDefs::TraceDepth traceDepth,
+ in TraceIRPConstDefs::TraceReference traceReference,
+ in TraceIRPConstDefs::TraceTarget traceTarget,
+ in TraceIRPConstDefs::TriggeringEventConditional triggeringEvent,
+ in TraceIRPConstDefs::TraceCollectionEntityAddress traceCollectionEntityAddress,
+ in TraceIRPConstDefs::JobType jobType,
+ in TraceIRPConstDefs::DNSet areaScope,
+ in TraceIRPConstDefs::ListOfMeasurements listOfMeasurements,
+ in TraceIRPConstDefs::ReportingTrigger reportingTrigger,
+ in TraceIRPConstDefs::ReportInterval reportInterval,
+ in TraceIRPConstDefs::ReportAmount reportAmount,
+ in TraceIRPConstDefs::EventThreshold eventThreshold,
+ in TraceIRPConstDefs::LoggingInterval loggingInterval,
+ in TraceIRPConstDefs::LoggingDuration loggingDuration,
+ in TraceIRPConstDefs::AnonymizationOfMDTData anonymizationOfMDTData,
+ in TraceIRPConstDefs::MeasurementQuantity measurementQuantity,
+ in TraceIRPConstDefs::MeasurementPeriodLTE measurementPeriodLTE,
+ in TraceIRPConstDefs::MeasurementPeriodUMTS measurementPeriodUMTS,
+ in TraceIRPConstDefs::CollectionPeriodRrmUmts collectionPeriodRrmUmts,
+ in TraceIRPConstDefs::CollectionPeriodRrmLte collectionPeriodRrmLte,
+ in TraceIRPConstDefs::PositioningMethod positioningMethod,
+ in TraceIRPConstDefs::PLMNTarget pLMNTarget,
+ out TraceIRPConstDefs::UnsupportedList unsupportedList
+ )
+ raises (ActivateTraceJob,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported,
+ NotUniqueTraceReference);
+
+ /**
+ * Request to deactivate a TraceJob through Itf-N.
+ **/
+
+ TraceIRPConstDefs::ResultEnum deactivateTraceJob (
+ in TraceIRPConstDefs::TraceReference traceReference,
+ in TraceIRPConstDefs::TraceTarget traceTarget,
+ out TraceIRPConstDefs::TraceRecordingSessionReference traceRecordingSessionReference)
+ raises (DeactivateTraceJob,
+ NotUniqueTraceReference,
+ GenericIRPManagementSystem::InvalidParameter,
+ );
+ }
+}
+
+```
+
+-----
+
+-----
+
+```
+
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported);
+
+ /**
+ * Request to list the parameters of a specific TraceJob through Itf-N.
+ */
+ TraceIRPConstDefs::ResultEnum listTraceJob (
+ in TraceIRPConstDefs::TraceReference traceReference,
+ out KernelCmConstDefs::DN moInstance,
+ out TraceIRPConstDefs::ListOfInterfaces listOfInterfaces,
+ out TraceIRPConstDefs::TraceDepth traceDepth,
+ out TraceIRPConstDefs::TraceRecordingSessionReference traceRecordingSessionReference,
+ out TraceIRPConstDefs::TraceTarget traceTarget,
+ out TraceIRPConstDefs::TriggeringEvent triggeringEvent,
+ out TraceIRPConstDefs::TraceCollectionEntityAddress traceCollectionEntityAddress,
+ out TraceIRPConstDefs::JobType jobType,
+ out TraceIRPConstDefs::DNSet areaScope,
+ out TraceIRPConstDefs::ListOfMeasurements listOfMeasurements,
+ out TraceIRPConstDefs::ReportingTrigger reportingTrigger,
+ out TraceIRPConstDefs::ReportInterval reportInterval,
+ out TraceIRPConstDefs::ReportAmount reportAmount,
+ out TraceIRPConstDefs::Integer eventThreshold,
+ out TraceIRPConstDefs::LoggingInterval loggingInterval,
+ out TraceIRPConstDefs::LoggingDuration loggingDuration,
+ out TraceIRPConstDefs::AnonymizationOfMDTData, anonymizationOfMDTData,
+ out TraceIRPConstDefs::MeasurementQuantity measurementQuantity)
+ out TraceIRPConstDefs::MeasurementPeriodLTE, measurementPeriodLTE,
+ out TraceIRPConstDefs::MeasurementPeriodUMTS measurementPeriodUMTS,
+ out TraceIRPConstDefs::CollectionPeriodRrmUmts, collectionPeriodRrmUmts,
+ out TraceIRPConstDefs::CollectionPeriodRrmLte, collectionPeriodRrmLte,
+ out TraceIRPConstDefs::PositioningMethod positioningMethod,
+ out TraceIRPConstDefs::PLMNTarget pLMNTarget,
+ )
+
+ raises (ListTraceJob,
+ NotUniqueTraceReference,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported);
+
+ /**
+ * Request to list the activated TraceJobs through Itf-N.
+ */
+ TraceIRPConstDefs::ResultEnum listActivatedTraceJob (
+ out TraceIRPConstDefs::TraceReferenceList traceReferenceList)
+ raises (ListActivatedTraceJob,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported);
+ );
+};
+
+#endif // _TRACE_IRP_SYSTEM_IDL_
+
+```
+
+### A.3.4 IDL specification (file name “TraceIRPNotifications.idl”)
+
+```
+
+//File: TraceIRPNotifications.idl
+#ifndef _TRACE_IRP_NOTIFICATIONS_IDL_
+#define _TRACE_IRP_NOTIFICATIONS_IDL_
+
+#include
+#include
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* Module: TraceIRPNotifications
+This module contains the specification of all notifications of Trace IRP Agent.
+=====
+*/
+module TraceIRPNotifications
+{
+
+ /**
+ * Constant definitions for the notifyTraceRecordingSessionFailure notification
+ */
+
+ interface NotifyTraceRecordingSessionFailure: NotificationIRPNotifications::Notify
+ {
+ const string EVENT_TYPE = "notifyTraceRecordingSessionFailure";
+
+ /**
+ * This constant defines the name of the TraceRecordingSessionReference property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceRecordingSessionReference.
+ */
+
+ const string TRACE_RECORDING_SESSION_REFERENCE =
+TraceIRPConstDefs::AttributeNameValue::TRACE_RECORDING_SESSION_REFERENCE;
+
+ /**
+ * This constant defines the name of the TraceReference property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceReference.
+ */
+
+ const string TRACE_REFERENCE = TraceIRPConstDefs::AttributeNameValue::TRACE_REFERENCE;
+
+ /**
+ * This constant defines the name of the reason property.
+ * The data type for the value of this property is string.
+ */
+
+ const string REASON = TraceIRPConstDefs::AttributeNameValue::REASON;
+ };
+
+ /**
+ * Constant definitions for the notifyTraceSessionLocalActivation notification
+ */
+
+ interface NotifyTraceSessionLocalActivation: NotificationIRPNotifications::Notify
+ {
+ const string EVENT_TYPE = "notifyTraceSessionLocalActivation";
+
+ /**
+ * This constant defines the name of the TraceReference property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceReference.
+ */
+
+ const string TRACE_REFERENCE = TraceIRPConstDefs::AttributeNameValue::TRACE_REFERENCE;
+
+ /**
+ * This constant defines the name of the TraceTarget property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceTarget.
+ */
+
+ const string TRACE_TARGET = TraceIRPConstDefs::AttributeNameValue::TRACE_TARGET;
+ };
+}
+
+```
+
+```
+/**
+ * This constant defines the name of the Managed Entity Object Instance property.
+ * The data type for the value of this property is string.
+ */
+const string MO_INSTANCE = TraceIRPConstDefs::AttributeNameValue::MO_INSTANCE;
+};
+
+/**
+ * Constant definitions for the notifyTraceSessionIdentities notification
+ */
+interface NotifyTraceSessionIdentities: NotificationIRPNotifications::Notify
+{
+ const string EVENT_TYPE = "notifyTraceSessionIdentities";
+
+ /**
+ * This constant defines the name of the TraceReference property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceReference.
+ */
+ const string TRACE_REFERENCE = TraceIRPConstDefs::AttributeNameValue::TRACE_REFERENCE;
+
+ /**
+ * This constant defines the name of the TraceRecordingSessionReference property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceRecordingSessionReference.
+ */
+ const string TRACE_RECORDING_SESSION_REFERENCE =
+ TraceIRPConstDefs::AttributeNameValue::TRACE_RECORDING_SESSION_REFERENCE;
+
+ /**
+ * This constant defines the name of the TraceTarget property.
+ * The data type for the value of this property is
+ * TraceIRPConstDefs::TraceTarget.
+ */
+ const string TRACE_TARGET = TraceIRPConstDefs::AttributeNameValue::TRACE_TARGET;
+
+ /**
+ * This constant defines the name of the Managed Entity Object Instance property.
+ * The data type for the value of this property is string.
+ */
+ const string MO_INSTANCE = TraceIRPConstDefs::AttributeNameValue::MO_INSTANCE;
+};
+
+#endif // _TRACE_IRP_NOTIFICATIONS_IDL_
+```
+
+# --- Annex B (normative): XML definitions
+
+This annex contains the XML definitions for the Trace Management IRP for the IRP whose semantics is specified in Trace Management IRP: Information Service (3GPP TS 32.442 [5]).
+
+This XML definitions specification defines the XML syntax of the Trace Management IRP XML Data File.
+
+## --- B.1 Architectural Features
+
+The overall architectural feature of Trace Management IRP is specified in 3G TS 32.442 [5]. This clause specifies features that are specific to the XML definitions.
+
+### B.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [9].
+
+### B.1.2 Notification Services
+
+This annex defines the XML syntax of Trace Management IRP notifications that is to be used for the Trace Management IRP SOAP Solution Set and in conjunction with Notification Log IRP XML definitions for Notification Log IRP XML Data File and the NL IRP XML Notification Format.
+
+### B.1.3 IOC definitions
+
+This annex defines the XML syntax for the IOC definitions of the Trace Management IRP IS [5], which are used by the XML definitions for the Trace Management IRP notifications and the Trace Management IRP IS operations.
+
+## --- B.2 Mapping
+
+Not present in the current version of this specification.
+
+## --- B.3 Solution Set definitions
+
+### B.3.1 XML definition structure
+
+Clause B.3.2 provides a graphical representation of the XML elements.
+
+Clause B.3.3 provides XML definitions of Trace Management IRP notifications as defined in [5]. These definitions are to be used for the Trace Management IRP SOAP Solution Set. For Trace IRP XML File Name Conventions the generic file name definitions as specified by the FT IRP apply (see [13]).
+
+Clause B.3.4 provides XML definitions of Trace Management IOC as defined in [5].
+
+### B.3.2 Graphical Representation
+
+
+
+Diagram illustrating the graphical representation of the **NotifyTraceRecordingSessionFailure** message structure:
+
+The message structure is defined by the **tr:NotifyTraceRecordingSessionFailure** type. It contains a **tr:body** element, which is a sequence of three elements:
+
+- tr:TraceRecordingSessionRef...** (indicated by a dashed box)
+- tr:TraceReference** (indicated by a solid box)
+- tr:Reason** (indicated by a dashed box)
+
+The **tr:TraceReference** element contains the following sub-elements:
+
+- tr:MCC**
+- tr:MNC**
+- tr:TRACE\_ID**
+
+ASN.1 diagram for NotifyTraceRecordingSessionFailure. The message structure includes a 'tr:body' containing 'tr:TraceRecordingSessionRef...', 'tr:TraceReference', and 'tr:Reason'. 'tr:TraceReference' contains 'tr:MCC', 'tr:MNC', and 'tr:TRACE\_ID'.
+
+
+
+Diagram illustrating the graphical representation of the **NotifyTraceSessionLocalActivation** message structure:
+
+The message structure is defined by the **tr:NotifyTraceSessionLocalActivation** type. It contains a **tr:body** element, which is a sequence of three elements:
+
+- tr:TraceReference** (indicated by a solid box)
+- tr:TraceTarget** (indicated by a solid box)
+- tr:IOCInstance** (indicated by a solid box)
+
+The **tr:TraceReference** element contains the following sub-elements:
+
+- tr:MCC**
+- tr:MNC**
+- tr:TRACE\_ID**
+
+The **tr:TraceTarget** element contains the following sub-elements:
+
+- tr:INSI**
+- tr:INEI**
+- tr:INEISV**
+- tr:PUBLIC\_ID**
+- tr:UTRAN\_CELL**
+- tr:E-UTRAN\_CELL**
+- tr:eNB**
+- tr:RNC**
+
+ASN.1 diagram for NotifyTraceSessionLocalActivation. The message structure includes a 'tr:body' containing 'tr:TraceReference', 'tr:TraceTarget', and 'tr:IOCInstance'. 'tr:TraceReference' contains 'tr:MCC', 'tr:MNC', and 'tr:TRACE\_ID'. 'tr:TraceTarget' contains 'tr:INSI', 'tr:INEI', 'tr:INEISV', 'tr:PUBLIC\_ID', 'tr:UTRAN\_CELL', 'tr:E-UTRAN\_CELL', 'tr:eNB', and 'tr:RNC'.
+
+
+
+```
+sequenceDiagram
+ participant NE as NotifyTraceSessionIdentification
+ Note right of NE: tr:body
+ Note right of tr:body: tr:TraceReference
+ Note right of tr:TraceReference: tr:MCC, tr:MNC, tr:TRACE_ID
+ Note right of tr:body: tr:TraceTarget
+ Note right of tr:TraceTarget: tr:IMSI, tr:IMEI, tr:IMEISV, tr:PUBLIC_ID, tr:UTRAN_CELL, tr:E-UTRAN_CELL, tr:eNB, tr:RNC
+```
+
+UML sequence diagram for NotifyTraceSessionIdentification. The diagram shows a 'tr:body' element containing 'tr:TraceReference' and 'tr:TraceTarget' components. 'tr:TraceReference' is linked to a 'tr:TraceReference' box containing 'tr:MCC', 'tr:MNC', and 'tr:TRACE\_ID'. 'tr:TraceTarget' is linked to a 'tr:TraceTarget' box containing 'tr:IMSI', 'tr:IMEI', 'tr:IMEISV', 'tr:PUBLIC\_ID', 'tr:UTRAN\_CELL', 'tr:E-UTRAN\_CELL', 'tr:eNB', and 'tr:RNC'.
+
+
+
+```
+sequenceDiagram
+ participant TE as TriggeringEvent
+ Note right of TE: xti:Events 0..∞
+ Note right of xti:Events: xti:NetworkElement 0..∞
+ Note right of xti:Events: xti:EventBitmap 0..∞
+```
+
+UML sequence diagram for TriggeringEvent. The diagram shows a 'TriggeringEvent' element linked to an 'xti:Events' box with a 0..∞ multiplicity. Inside the 'xti:Events' box are 'xti:NetworkElement' and 'xti:EventBitmap' elements, both with 0..∞ multiplicities.
+
+### B.3.3 XML Schema "tMIRPNotif.xsd"
+
+```
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+