Add files using upload-large-folder tool

marked/Rel-10/32_series/32103/raw.md

@@ -0,0 +1,888 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                            |           |
+|----------------------------------------------------------------------------|-----------|
+| Foreword .....                                                             | 4         |
+| Introduction .....                                                         | 4         |
+| 1 Scope.....                                                               | 5         |
+| 2 References.....                                                          | 5         |
+| 3 Definitions and abbreviations .....                                      | 5         |
+| 3.1 Definitions.....                                                       | 5         |
+| 3.2 Abbreviations .....                                                    | 5         |
+| 4 IRP Framework.....                                                       | 6         |
+| 4.1 Introduction .....                                                     | 6         |
+| 4.2 IRP Framework Highlights .....                                         | 6         |
+| 4.2.1 IRP Concept.....                                                     | 6         |
+| 4.2.2 Interface IRP vs. NRM IRP.....                                       | 7         |
+| 4.2.3 IRP Development Principles .....                                     | 7         |
+| 4.2.4 IRP Specification Structure .....                                    | 8         |
+| 4.2.5 Essential IRP Definitions [2].....                                   | 8         |
+| 4.3 IRP related High-level Requirements & Architecture Specifications..... | 9         |
+| 5 Interface IRP's.....                                                     | 10        |
+| 5.1 Interface IRP Overview.....                                            | 10        |
+| 5.2 Generic/Common Interface IRP's .....                                   | 10        |
+| 5.3 FM related Interface IRP's .....                                       | 11        |
+| 5.4 CM related Interface IRP's .....                                       | 11        |
+| 5.5 PM & Trace related Interface IRP's .....                               | 12        |
+| 5.6 Special-purpose related Interface IRP's .....                          | 12        |
+| 6 NRM IRP's.....                                                           | 13        |
+| 6.1 NRM IRP Overview.....                                                  | 13        |
+| 6.2 Common NRM IRP's .....                                                 | 13        |
+| 6.3 Access Network (AN) related NRM IRP's.....                             | 14        |
+| 6.4 Core/IMS related NRM IRP's .....                                       | 14        |
+| 6.5 H(e)NB related NRM IRP's .....                                         | 14        |
+| 6.6 Service Management related NRM IRP's and UDC specifications .....      | 15        |
+| 6.7 Special-purpose related NRM IRPs .....                                 | 16        |
+| 7 Measurement & Trace Definitions.....                                     | 17        |
+| 7.1 Performance Measurements.....                                          | 17        |
+| 7.1.1 Overview and relationships to IRP Framework .....                    | 17        |
+| 7.1.2 Performance Measurement Specifications .....                         | 18        |
+| 7.2 Trace Specifications.....                                              | 20        |
+| 7.2.1 Overview and relationships to IRP Framework .....                    | 20        |
+| 7.2.2 Trace Specifications .....                                           | 20        |
+| 8 Relationships between IRPs.....                                          | 21        |
+| 9 SON Functions.....                                                       | 22        |
+| <b>Annex A (Informative): IRP Packaging Suggestions .....</b>              | <b>25</b> |
+| A.1 Overview & Purpose .....                                               | 25        |
+| Annex B (informative): Change history.....                                 | 26        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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
+
+This specification provides the IRP Overview for 3GPP specifications, addressing Interface IRPs, NRM IRPs, Measurement / Trace /SON specifications, as well as their relationships with each other.
+
+# --- 1 Scope
+
+The present document gives an overview about 3GPP's management interface capabilities and related functionality. It provides high-level information about IRP Framework, available IRP's as well as their relationship with each other. This document is intended to be a guide into the world of 3GPP management specifications, enabling also non-subject matter experts to gain an understanding about 3GPP's management solutions.
+
+In addition Annex A provides IRP packaging suggestions, intended to guide service providers as well as equipment and solutions providers to identify and choose suitable standardized management interface capabilities.
+
+# --- 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.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [3] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [4] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [5] 3GPP TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".
+- [6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [7] 3GPP TS 32.111-6: "Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [8] 3GPP TS 32.121: "Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements".
+- [9] 3GPP TS 32.122: "Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS)".
+- [10] 3GPP TS 32.126: "Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [11] 3GPP TS 32.140: "Telecommunication management; Subscription Management (SuM) requirements".
+- [12] 3GPP TS 32.141: "Telecommunication management; Subscription Management (SuM) architecture".
+- [13] 3GPP TS 32.151: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template".
+- [14] 3GPP TS 32.152: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire".
+
+- [15] 3GPP TS 32.153: "Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines".
+- [16] 3GPP TS 32.154: "Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions".
+- [17] 3GPP TS 32.155: "Telecommunication management; Requirements template".
+- [18] 3GPP TS 32.171: "Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+- [19] 3GPP TS 32.172: "Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
+- [20] 3GPP TS 32.176: "Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) definitions".
+- [21] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+- [22] 3GPP TS 32.301: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements".
+- [23] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)".
+- [24] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [25] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
+- [26] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [27] 3GPP TS 32.316: "Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions".
+- [28] 3GPP TS 32.321: "Telecommunication management; Test management Integration Reference Point (IRP); Requirements".
+- [29] 3GPP TS 32.322: "Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS) ".
+- [30] 3GPP TS 32.326: "Telecommunication management; Test management Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [31] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements",
+- [32] 3GPP TS 32.332: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS)".
+- [33] 3GPP TS 32.336: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [34] 3GPP TS 32.341: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements".
+- [35] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS)".
+- [36] 3GPP TS 32.346: "Telecommunication management; File Transfer (FT) Integration ReferencePoint (IRP): Solution Set (SS) definitions".
+
+- [37] 3GPP TS 32.351: "Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Requirements".
+- [38] 3GPP TS 32.352: "Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS)".
+- [39] 3GPP TS 32.356: "Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [40] 3GPP TS 32.361: "Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements".
+- [41] 3GPP TS 32.362: "Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS)".
+- [42] 3GPP TS 32.366: "Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [43] 3GPP TS 32.381: "Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Requirements".
+- [44] 3GPP TS 32.382: "Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Information Service (IS)".
+- [45] 3GPP TS 32.386: "Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [46] 3GPP TS 32.391: "Telecommunication management; Delta synchronization Integration Reference Point (IRP); Requirements".
+- [47] 3GPP TS 32.392: "Telecommunication management; Delta synchronization Integration Reference Point (IRP); Information Service (IS)".
+- [48] 3GPP TS 32.396: "Telecommunication management; Delta synchronization Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [49] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
+- [50] 3GPP TS 32.405: "Telecommunication management; Performance Management (PM); Performance measurements; Universal Terrestrial Radio Access Network (UTRAN)".
+- [51] 3GPP TS 32.406: "Telecommunication management; Performance Management (PM); Performance measurements; Core Network (CN) Packet Switched (PS) domain".
+- [52] 3GPP TS 32.407: "Telecommunication management; Performance Management (PM); Performance measurements; Core Network (CN) Circuit Switched (CS) domain; UMTS and combined UMTS/GSM".
+- [53] 3GPP TS 32.408: "Telecommunication management; Performance Management (PM); Performance measurements; Teleservice".
+- [54] 3GPP TS 32.409: "Telecommunication management; Performance Management (PM); Performance measurements; IP Multimedia Subsystem (IMS)".
+- [55] 3GPP TS 32.410: "Telecommunication management; Key Performance Indicators (KPI) for UMTS and GSM".
+- [56] 3GPP TS 32.411: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); Requirements".
+- [57] 3GPP TS 32.412: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); Information Service (IS)".
+- [58] 3GPP TS 32.416: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+
+- [59] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
+- [60] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
+- [61] 3GPP TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management
+- [62] 3GPP TS 32.425: "Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)".
+- [63] 3GPP TS 32.426: "Telecommunication management; Performance Management (PM); Performance measurements Evolved Packet Core (EPC) network".
+- [64] 3GPP TS 32.432: "Telecommunication management; Performance measurement: File format definition".
+- [65] 3GPP TS 32.435: "Telecommunication management; Performance measurement; eXtensible Markup Language (XML) file format definition".
+- [66] 3GPP TS 32.436: "Telecommunication management; Performance measurement: Abstract Syntax Notation 1 (ASN.1) file format definition".
+- [67] 3GPP TS 32.441: "Telecommunication management; Trace Management Integration Reference Point (IRP); Requirements".
+- [68] 3GPP TS 32.442: "Telecommunication management; Trace Management Integration Reference Point (IRP); Information Service (IS)".
+- [69] 3GPP TS 32.446: "Telecommunication management; Trace Management Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [70] 3GPP TS 32.451: "Telecommunication management; Key Performance Indicators (KPI) for Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Requirements".
+- [71] 3GPP TS 32.452: "Telecommunication management; Performance Management (PM); Performance measurements Home Node B (HNB) Subsystem (HNS)".
+- [72] 3GPP TS 32.453: "Telecommunication management; Performance Management (PM); Performance measurements Home enhanced Node B (HeNB) Subsystem (HeNS)".
+- [73] 3GPP TS 32.454: "Telecommunication management; Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS); Definitions".
+- [74] 3GPP TS 32.455: "Telecommunication management; Key Performance Indicators (KPI) for the Evolved Packet Core (EPC); Definitions".
+- [75] 3GPP TS 32.500: "Telecommunication management; Self-Organizing Networks (SON); Concepts and requirements".
+- [76] 3GPP TS 32.501: "Telecommunication management; Self-configuration of network elements; Concepts and requirements".
+- [77] 3GPP TS 32.502: "Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Information Service (IS)".
+- [78] 3GPP TS 32.506: "Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [79] 3GPP TS 32.511: "Telecommunication management; Automatic Neighbour Relation (ANR) management; Concepts and requirements".
+- [80] 3GPP TS 32.521: "Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+
+- [81] 3GPP TS 32.522: "Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+- [82] 3GPP TS 32.526: "Telecommunication management; Self-Organizing Networks (SON); Policy Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [83] 3GPP TS 32.531: "Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements".
+- [84] 3GPP TS 32.532: "Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS)".
+- [85] 3GPP TS 32.536: "Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [86] 3GPP TS 32.541: "Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements".
+- [87] 3GPP TS 32.551: "Telecommunication management; Energy Saving Management (ESM); Concepts and requirements".
+- [88] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
+- [89] 3GPP TS 32.601: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements".
+- [90] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS)".
+- [91] 3GPP TS 32.606: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [92] 3GPP TS 32.611: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Requirements".
+- [93] 3GPP TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Information Service (IS)".
+- [94] 3GPP TS 32.616: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [95] 3GPP TS 32.621: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+- [96] 3GPP TS 32.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+- [97] 3GPP TS 32.626: "Telecommunication management; State management data definition Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [98] 3GPP TS 32.631: "Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements".
+- [99] 3GPP TS 32.632: "Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM)".
+- [100] 3GPP TS 32.636: "Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Solution Set (SS) Definitions".
+- [101] 3GPP TS 32.641: "Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements".
+- [102] 3GPP TS 32.642: "Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM)".
+
+- [103] 3GPP TS 32.646: "Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [104] 3GPP TS 32.651: "Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements".
+- [105] 3GPP TS 32.652: "Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM)".
+- [106] 3GPP TS 32.656: "Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [107] 3GPP TS 32.661: "Telecommunication management; Configuration Management (CM); Kernel CM Requirements".
+- [108] 3GPP TS 32.662: "Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS)".
+- [109] 3GPP TS 32.671: "Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Requirements".
+- [110] 3GPP TS 32.672: "Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS)".
+- [111] 3GPP TS 32.673: "Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
+- [112] 3GPP TS 32.690: "Telecommunication management; Inventory Management (IM); Requirements".
+- [113] 3GPP TS 32.691: "Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Requirements".
+- [114] 3GPP TS 32.692: "Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM)".
+- [115] 3GPP TS 32.696: "Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [116] 3GPP TS 32.711: "Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+- [117] 3GPP TS 32.712: "Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+- [118] 3GPP TS 32.716: "Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [119] 3GPP TS 32.721: "Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Requirements".
+- [120] 3GPP TS 32.722: "Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); information Service (IS)".
+- [121] 3GPP TS 32.726: "Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [122] 3GPP TS 32.731: "Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+- [123] 3GPP TS 32.732: "Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+
+- [124] 3GPP TS 32.736: "Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [125] 3GPP TS 32.741: "Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) IntegrationReference Point (IRP); Requirements".
+- [126] 3GPP TS 32.742: "Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+- [127] 3GPP TS 32.746: "Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [128] 3GPP TS 32.751: "Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+- [129] 3GPP TS 32.752: "Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+- [130] 3GPP TS 32.756: "Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) Definitions".
+- [131] 3GPP TS 32.761: "Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements".
+- [132] 3GPP TS 32.762: "Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+- [133] 3GPP TS 32.766: "Telecommunication management; Evolved Universal Terrestrial RadioAccess Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [134] 3GPP TS 32.771: "Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements".
+- [135] 3GPP TS 32.772: "Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Information Service (IS)".
+- [136] 3GPP TS 32.776: "Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [137] 3GPP TS 32.781: "Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements".
+- [138] 3GPP TS 32.782: "Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Information Service (IS)".
+- [139] 3GPP TS 32.786: "Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [140] 3GPP TS 32.402: "Telecommunication management; Performance Management (PM); Performance measurements – GSM".
+- [141] 3GPP TS 32.181: "Telecommunication management; User Data Convergence (UDC); Framework for Model Handling and Management".
+- [142] 3GPP TS 32.182: "Telecommunication management; User Data Convergence (UDC); Common baseline information model (CBIM)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 32.150 [2].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply.
+
+# 4 IRP Framework
+
+## 4.1 Introduction
+
+For the purpose of management interface development 3GPP has developed an interface concept known as Integration Reference Point (IRP) to promote the wider adoption of standardized management interfaces in telecommunication networks. The IRP concept and associated methodology employs model-driven development, protocol and technology neutral modelling methods as well as protocol specific solution sets to achieve its goals.
+
+IRP Framework and Methodology related 3GPP specifications:
+
+- 32.150 [2]: Integration Reference Point (IRP) Concept and definitions
+- 32.151 [13]: IRP Information Service (IS) template
+- 32.152 [14]: IRP IS Unified Modeling Language (UML) repertoire
+- 32.153 [15]: IRP technology specific templates, rules and guidelines
+- 32.154 [16]: Backward and Forward Compatibility Concept and definitions
+- 32.155[17]: Requirements template
+
+## 4.2 IRP Framework Highlights
+
+### 4.2.1 IRP Concept
+
+IRP specifications are specified using a 3-level approach: Requirements, IS-level and SS-level.
+
+![Diagram of the IRP 3-Level Specifications Approach](704082cc3e11776bda29595c76411362_img.jpg)
+
+The diagram illustrates the IRP 3-Level Specifications Approach, showing three levels of specifications and their relationship to three IRP categories.
+
+**Level 1: Requirements / Use Cases** (Top level, green background). It contains three categories: **Interface IRP's**, **NRM IRP's**, and **Data Definition IRP's**. A blue arrow points to this level with the text "Relative stable over long period of time".
+
+**Level 2: Information Service Definitions (UML)** (Middle level, green background). It contains three categories: **Interface IRP's**, **NRM IRP's**, and **Data Definition IRP's**. A blue arrow points to this level with the text "Changes only with respect to addition and extensions".
+
+**Level 3: Solution Set Definitions (CORBA, SOAP, XML, CMIP)** (Bottom level, green background). It contains three categories: **Interface IRP's**, **NRM IRP's**, and **Data Definition IRP's**. A blue arrow points to this level with the text "Changes with new/better Technologies".
+
+**Information Service Definitions (UML) details:**
+
+- Interface IRP's:** Notification IRP, Alarm IRP, BulkCM IRP, KernelCM IRP, BasicCM IRP, etc.
+- NRM IRP's:** Generic NRM, CoreNW NRM, UMTS NRM's, CDMA NRM's, Inventory NRM, etc.
+- Data Definition IRP's:** State Mgmt IRP, etc.
+
+**Solution Set Definitions (other/future e.g. JAVA, SNMP)** (Bottom-most level, green background).
+
+Diagram of the IRP 3-Level Specifications Approach
+
+Figure 4.2-1: The IRP 3-Level Specifications Approach combined with the three IRP categories [2].
+
+#### Requirements-level:
+
+The "Requirements-level" intends to provide conceptual and use cases definitions for a specific management interface aspect as well as defining subsequent requirements for this IRP.
+
+#### IS-level:
+
+- The "IS-level" provides the technology independent specification of an IRP.
+
+#### SS-level:
+
+The "SS-level" finally provides the mapping of IS definitions into one or more technology-specific Solution Sets. This concept provides support for multiple interface technologies as applicable on a vendor and/or network type basis and also enables accommodation of future interface technologies - without the need to redefine requirements and IS-level definitions.
+
+### 4.2.2 Interface IRP vs. NRM IRP
+
+There are three categories of IRP specifications:
+
+- Interface IRPs
+- NRM IRPs
+- Data Definition IRPs
+
+Each category is partitioned into Requirements, IS-level and SS-level specifications.
+
+![Diagram illustrating the relationship between Interface IRP and NRM IRP. At the top, a yellow oval labeled 'Network Management' contains icons of a person at a computer, a laptop, and a server. Below it, a central 'Itf-N' interface is shown. To the left, a blue oval labeled 'NRM IRP's' (Defining WHAT can be managed (Object Models)) points to an 'EMS' box, which is connected to a 'Core/IM NW' oval containing server icons. To the right, a green oval labeled 'Interface IRP's' (Defining HOW Information is shared (Operations & Notifications)) points to the 'Itf-N' interface. Below the 'Itf-N' interface, another 'EMS' box is connected to a 'Radio Access NW' oval containing a radio tower icon. Further right, a third 'EMS' box is connected to a 'User Equipment' oval containing mobile device icons. A dashed green line connects the 'Itf-N' interface to the third 'EMS' box. A third blue oval labeled 'NRM IRP's' points to this third 'EMS' box.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg)
+
+Diagram illustrating the relationship between Interface IRP and NRM IRP. At the top, a yellow oval labeled 'Network Management' contains icons of a person at a computer, a laptop, and a server. Below it, a central 'Itf-N' interface is shown. To the left, a blue oval labeled 'NRM IRP's' (Defining WHAT can be managed (Object Models)) points to an 'EMS' box, which is connected to a 'Core/IM NW' oval containing server icons. To the right, a green oval labeled 'Interface IRP's' (Defining HOW Information is shared (Operations & Notifications)) points to the 'Itf-N' interface. Below the 'Itf-N' interface, another 'EMS' box is connected to a 'Radio Access NW' oval containing a radio tower icon. Further right, a third 'EMS' box is connected to a 'User Equipment' oval containing mobile device icons. A dashed green line connects the 'Itf-N' interface to the third 'EMS' box. A third blue oval labeled 'NRM IRP's' points to this third 'EMS' box.
+
+Figure 4.2-2: Relationship Interface IRP vs NRM IRP
+
+### 4.2.3 IRP Development Principles
+
+**NRM IRP Extensibility** - Enabling Technology, Organizational & Vendor-specific NRM extensions via
+
+- Rule-based NRM Extensions (e.g. Sub-classing)
+- vsDataContainer
+
+**Interface IRP Flexibility** - Enabling: wide applicability, phased introduction capabilities & broad industry adoption (not just for wireless) via
+
+- Flexible use of qualifiers "mandatory", "optional", "conditional" for operation, notifications and/or parameters
+- NRM/Technology-neutrality & avoiding competing procedures
+
+### 4.2.4 IRP Specification Structure
+
+All IRP's follow a uniform specification structure:
+
+- xx1: xyz IRP Requirements
+- xx2: xyz IRP IS
+- xx3: xyz IRP CORBA SS (*merged into xx6 after R9*)
+- xx4: xyz IRP CMIP SS (*retired after R6*)
+- xx5: xyz IRP XML Definitions (*applicable for NRM's & notification emitting IRP's - merged into xx6 after R9*)
+- xx6: xyz IRP SS (since R10, containing all technology specific Solution Set definitions)
+- xx7: xyz IRP SOAP SS (*merged into xx6 after R9*)
+
+### 4.2.5 Essential IRP Definitions [2]
+
+**Data Definition IRP:** 3GPP publishes IRP specifications relating to commonly used data definitions that can be imported for use by Interface IRP and/or NRM IRP. This term represents all such specifications. An example of a Data Definition IRP is the State Management IRP (32.671 [109], 32.672 [110], 32.673 [111], etc).
+
+**Integration Reference Point (IRP):** An architectural concept that is described by a set of specifications for definition of a certain aspect of a management interface, comprising a **Requirements** specification, an **Information Service** specification, and one or more **Solution Set** specifications.
+
+**Interface IRP:** 3GPP publishes a number of IRP specifications each of which is related to a set of operations and notifications for a specific telecom management domain such as alarm management, configuration management, etc. Interface IRPs also contain definitions of Support IOCs. This term represents all such specifications. An example of an Interface IRP is the Basic CM IRP (the set of TSs 32.601 [894], 32.602 [90], 32.606 [91], etc.).
+
+**IRP Agent:** Encapsulates a well-defined subset of network (element) functions. It interacts with IRPManagers using one or more IRPs. From the IRPManager's perspective, the IRP Agent behaviour is only visible via the IRP(s).
+
+**Information Service (IS):** an IRP Information Service describes the information related to the entities (either network resources or support objects) to be managed and the way that the information may be managed for a certain functional area (e.g. the Alarm IRP Information Service in the fault management area). Information Services are defined for all IRPs.
+
+**IRP Manager:** Models a user of IRP Agent(s) and it interacts directly with the IRP Agent(s) using IRP(s). Since the IRP Manager represents an IRP Agent user, it gives a clear picture of what the IRP Agent is supposed to do. From the IRP Agent perspective, the IRP Manager behaviour is only visible via the IRP.
+
+**Network Resource Model (NRM):** An Information Service describing Information Object Classes representing the manageable aspects of network resources, e.g. an RNC or NodeB.
+
+**NRM IRP:** 3GPP publishes a number of IRP specifications each of which is related to a particular NRM (Network Resource Model) as defined in 3GPP TS 32.101 [3]. NRM IRPs do not define any operations or notifications. This term represents all such specifications. Note: In some NRM IRP titles, for historic reasons, they are named "...network resources IRP"). An example of an NRM IRP is the Generic NRM IRP (32.621 [95], 32.622 [96], 32.623 [97], etc.).
+
+**Solution Set (SS):** contains a mapping of the IRP Information Service (IS) defined entities (that are technology-agnostic) to technology specific termed entities. It does not contain specification of the entities' semantics. The semantics can be found in the corresponding IS. It is noted that one IS can be mapped to one or several SSs.
+
+## 4.3 IRP related High-level Requirements & Architecture Specifications
+
+The IRP Framework has been developed in response to management requirements documented in the following specifications:
+
+- 32.101 [3]: Principles and high level requirements
+- 32.102[4]: Architecture
+- 32.111-1 [5]: 3G fault management requirements
+- 32.140 [11], 32.141 [12]: SuM requirements / SuM architecture
+- 32.300 [21]: Name convention for Managed Objects
+- 32.401[49]: PM Concept and requirements
+- 32.500 [75]: SON Concepts and requirements
+- 32.511 [79]: ANR management Concepts and requirements
+- 32.521 [80]: Self-optimization Concepts and requirements
+- 32.541 [86]: Self-healing Concepts and requirements
+- 32.551 [87]: Energy Saving Management (ESM) Concepts and requirements
+- 32.600 [88]: CM Concept and high-level requirements
+
+# 5 Interface IRP's
+
+## 5.1 Interface IRP Overview
+
+![Diagram showing the overview of Interface IRP's in 3GPP R10, categorized into Common, FM-related, CM-related, PM-related, Supporting, and Other IRP's.](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+```
+graph TD; Common[Common IF IRP's: Notification IRP (32.30x), Generic IRP (32.31x)]; FM[FM-related IF IRP's: Alarm IRP (32.111-x), AAM IRP (32.12x), Test Mgmt IRP (32.32x)]; CM[CM-related IF IRP's: Basic CM IRP (32.60x), Bulk CM IRP (32.61x), Kernel CM IRP (32.66x), SC IRP (32.50x), SWM IRP (32.53x)]; PM[PM-related IF IRP's: PM IRP (32.41x), Trace Mgmt (32.44x)]; Support[Supporting IF IRP's: NL IRP (32.33x), FT IRP (32.34x), CS IRP (32.35x), EP IRP (32.35x)]; Other[Other IF IRP's: Partial Suspension of Itf-N IRP (32.38x), Delta synchronization (32.39x)];
+```
+
+**Common IF IRP's:**
+
+- Notification IRP (32.30x)
+- Generic IRP (32.31x)
+
+**FM-related IF IRP's:**
+
+- Alarm IRP (32.111-x)
+- AAM IRP (32.12x)
+- Test Mgmt IRP (32.32x)
+
+**CM-related IF IRP's:**
+
+- Basic CM IRP (32.60x)
+- Bulk CM IRP (32.61x)
+- Kernel CM IRP (32.66x)
+- SC IRP (32.50x)
+- SWM IRP (32.53x)
+
+**PM-related IF IRP's:**
+
+- PM IRP (32.41x)
+- Trace Mgmt (32.44x)
+
+**Supporting IF IRP's:**
+
+- NL IRP (32.33x)
+- FT IRP (32.34x)
+- CS IRP (32.35x)
+- EP IRP (32.35x)
+
+**Other IF IRP's:**
+
+- Partial Suspension of Itf-N IRP (32.38x)
+- Delta synchronization (32.39x)
+
+Diagram showing the overview of Interface IRP's in 3GPP R10, categorized into Common, FM-related, CM-related, PM-related, Supporting, and Other IRP's.
+
+Figure 5.1-1: Interface IRP's 3GPP R10
+
+## 5.2 Generic/Common Interface IRP's
+
+**Notification IRP – 32.300 [21], 32.301[22], 32.302[23], 32.306[24]**
+
+The purpose of the Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications, manage these subscriptions, and optionally set filters.
+
+**Generic IRP – 32.311 [25], 32.312 [26], 32.316 [27]**
+
+This IRP defines common services supported by all IRPs such as AlarmIRP. With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP name-contained by an IRPAgent. An IRPManager can also retrieve the IRPVersions supported by a given IRP.
+
+## 5.3 FM related Interface IRP's
+
+### **Alarm IRP – 32.111-1 [5], 32.111-2 [6], 32.111-6[7]**
+
+The Alarm (IRP) addresses the alarm surveillance aspects of Fault Management (FM), applied to Itf-N. It defines alarm semantics & syntax as well as alarm management related operations and notifications.
+
+### **Advanced Alarm Management IRP – 32.121 [8], 32.122 [9], 32.126 [10]**
+
+The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications. It defines, for the purpose of categorizing alarm notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+### **Test management IRP – 32.321 [28], 32.322 [29], 32.326[30]**
+
+The purpose of the Test management IRP is to define an interface through which an IRPManager can manage and monitor tests in NE's, as well as methods to receive test results.
+
+## 5.4 CM related Interface IRP's
+
+### **Self-Configuration IRP – 32.500 [75], 32.501 [76], 32.502 [77], 32.506 [78]**
+
+The Self-Configuration provides methods to allow automatic configuration of eNBs, which are brought newly into a network.
+
+### **Software Management IRP – 32.531 [83], 32.532 [84], 32.536 [85]**
+
+The Software Management IRP provides an IRPManager with capabilities to automate software management via Itf-N.
+
+### **Basic CM IRP – 32.600 [88], 32.601[89], 32.602 [90], 32.606 [91]**
+
+Using this IRP, an IRPAgent can communicate basic Configuration Management related information to one or several IRPManagers. The function of this Basic CM IRP Information Service is to define an interface for the retrieval and modification of Configuration Management Information.
+
+### **Bulk CM IRP – 32.611 [92], 32.612 [93], 32.616 [94]**
+
+Using the Bulk CM IRP an IRPAgent can communicate CM related information to one or several IRPManagers using bulk data transfer methods.
+
+- BulkCM SimpleUpload, enabling upload of resource information by the IRPManager without explicit session control
+- BulkCM Controlled Upload, enabling a session controlled upload of resource information by the IRPManager
+- BulkCM Controlled Upload & Provisioning, enabling a session controlled upload and provisioning of resource information by the IRPManager
+
+### **Kernel CM IRP – 32.661 [107], 32.662 [108]**
+
+The function of this Kernel CM IRP Information Service is to define an interface that provides essential CM notification services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capabilities, the Kernel CM IRP is expected to provide the common supporting CM notifications required for other CM IRPs such as the Basic CM IRP or the Bulk CM IRP, each of which require the Kernel CM IRP.
+
+## 5.5 PM & Trace related Interface IRP's
+
+### **Performance Management IRP – 32.410 [55], 32.411[56], 32.412 [57], 32.416 [58]**
+
+The Performance Management IRP is defines an interface through which an IRPManager can manage measurement jobs as well threshold values.
+
+### **Trace Management IRP – 32.441 [67], 32.442 [68], 32.446 [69]**
+
+The Trace Management IRP is defines an interface through which an IRPManager can activate and manage equipment and subscriber trace jobs.
+
+## 5.6 Special-purpose related Interface IRP's
+
+### **Notification Log IRP – 32.331[31], 32.332[32], 32.336[33]**
+
+The purpose of the Notification Log IRP is to define an interface through which an IRPManager can manage a Notification Log, as well as methods for retrieval of logged notifications.
+
+### **File Transfer IRP – 32.341[34], 32.342[35], 32.346[36]**
+
+The purpose of the File Transfer IRP is to define a generic tools set supporting the management of file transfers between IRPManager and IRPAgent. Currently the following management data types are supported by this IRP:
+
+- performance data files
+- configuration & inventory files
+- test result files
+- call trace files
+- notification log files
+- charging files
+
+### **Communication Surveillance IRP – 32.351 [37], 32.352 [38], 32.356[39]**
+
+The purpose of the Communication Surveillance IRP is to provide an IRPManager with the capability to monitor the health of the communications link towards an IRPAgent.
+
+### **Entry Point IRP – 32.361 [40], 32.362[41], 32.366 [42]**
+
+The purpose of the Entry Point IRP is to provide an IRPManager with discovery and entry point capabilities towards an IRPAgent and its supported IRP's.
+
+### **Partial Suspension of Itf-N IRP – 32.381 [43], 32.382 [44], 32.386 [45]**
+
+The purpose of Partial Suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+### **Delta synchronization IRP – 32.391 [46], 32.392 [47], 32.396 [48]**
+
+The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data that have changed (i.e. changed, were created or deleted) from a synchronization point onwards.
+
+# 6 NRM IRP's
+
+## 6.1 NRM IRP Overview
+
+![Diagram showing the overview of NRM IRP's in 3GPP R10, categorized into Common, Services related, 3GPP AN, 3GPP Core NW, 3GPP H(e)NS, and Supporting NRM IRP's.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg)
+
+```
+graph TD; Common[Common NRM IRP's] --- CommonList[Generic NRM IRP (32.62x)]; Services[Services related NRM IRP's] --- ServicesList[SuM NRM IRP (32.17x), UDC CBIM NRM IRP IS (32.182)]; AN[3GPP AN NRM IRP's] --- ANList[UTRAN NRM IRP (32.64x), GERAN NRM IRP (32.65x), E-UTRAN NRM IRP (32.76x)]; Core[3GPP Core NW NRM IRP's] --- CoreList[Core NRM IRP (32.63x), IMS NRM IRP (32.73x), Evolved Packet Core NRM IRP (32.75x)]; HNS[3GPP H(e)NS NRM IRP's] --- HNSList[HNS NRM IRP (32.77x), HeNS NRM IRP (32.78x)]; Supporting[Supporting NRM IRP's] --- SupportingList[Inventory Management NRM IRP (32.69x), Transport Network NRM IRP (32.71x), Repeater NRM IRP (3.72x), Signalling Transport NW IF NRM IRP (32.74x), SON Policy NRM IRP (32.52x)];
+```
+
+**Common NRM IRP's:**
+
+- Generic NRM IRP (32.62x)
+
+**Services related NRM IRP's:**
+
+- SuM NRM IRP (32.17x)
+- *UDC CBIM NRM IRP IS (32.182)*
+
+**3GPP AN NRM IRP's:**
+
+- UTRAN NRM IRP (32.64x)
+- GERAN NRM IRP (32.65x)
+- E-UTRAN NRM IRP (32.76x)
+
+**3GPP Core NW NRM IRP's:**
+
+- Core NRM IRP (32.63x)
+- IMS NRM IRP (32.73x)
+- Evolved Packet Core NRM IRP (32.75x)
+
+**3GPP H(e)NS NRM IRP's:**
+
+- HNS NRM IRP (32.77x)
+- HeNS NRM IRP (32.78x)
+
+**Supporting NRM IRP's:**
+
+- Inventory Management NRM IRP (32.69x)
+- Transport Network NRM IRP (32.71x)
+- Repeater NRM IRP (3.72x)
+- Signalling Transport NW IF NRM IRP (32.74x)
+- SON Policy NRM IRP (32.52x)
+
+Diagram showing the overview of NRM IRP's in 3GPP R10, categorized into Common, Services related, 3GPP AN, 3GPP Core NW, 3GPP H(e)NS, and Supporting NRM IRP's.
+
+Figure 6.1-1: NRM IRP's 3GPP R10
+
+## 6.2 Common NRM IRP's
+
+Generic NRM IRP – 32.621 [95], 32.622 [96], 32.626 [97]
+
+The Generic NRM IRP provides the generic network resources information that can be communicated between an IRP Agent and one or several IRP Managers for network management purposes.
+
+## 6.3 Access Network (AN) related NRM IRP's
+
+### **UTRAN NRM IRP – 32.641 [101] , 32.642 [102], 32.646 [103]**
+
+The UTRAN NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning UTRAN specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **GERAN NRM IRP – 32.651 [104], 32.652 [105], 32.656 [106]**
+
+The GERAN NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning GERAN specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **EUTRAN NRM IRP – 32.761 [131], 32.762 [132], 32.766 [133]**
+
+The EUTRAN NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning EUTRAN specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+## 6.4 Core/IMS related NRM IRP's
+
+### **Core NRM IRP – 32.631 [98], 32.632 [99], 32.636 [100]**
+
+The Core NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning core network specific resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **IMS NRM IRP – 32.731 [122], 32.732 [123], 32.736 [124]**
+
+The IMS NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning IP MultiMedia Subsystem specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **EPC NRM IRP – 32.751 [128], 32.752 [129], 32.756 [130]**
+
+The EPC NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Evolved Packet Core specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+## 6.5 H(e)NB related NRM IRP's
+
+### **HNS NRM IRP – 32.771 [134], 32.772 [135], 32.776 [136]**
+
+The HNS NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Home NodeB Subsystem specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **HeNS NRM IRP – 32.781 [137], 32.782 [138], 32.786 [139]**
+
+The HeNS NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Home enhanced NodeB Subsystem specific network resource, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+## 6.6 Service Management related NRM IRP's and UDC specifications
+
+### **SuM NRM IRP – 32.171 [18], 32.172 [19], 32.176 [20]**
+
+Subscription Management is a feature that permits Service Providers, Value Added Service Providers and Mobile Operators to provision services for a specific subscriber. The SuM NRM IRP defines the Subscription Management specific network resource information between an IRP Agent and one or several IRP Managers.
+
+### **UDC – 32.181 [141], 32.182 [142]**
+
+User Data Convergence (UDC) presents a layered architecture where user data is accessible at a logically unique repository called User Data Repository (UDR). The UDC CBIM defines a Common Baseline Information Model for UDC, which denotes an abstract, formal representation of entity types that are common to many applications using the UDR.
+
+## 6.7 Special-purpose related NRM IRPs
+
+### **Inventory Management NRM IRP – 32.690 [112], 32.691[113], 32.692 [114], 32.696 [115]**
+
+Inventory Management (IM) provides the operator with the ability to assure correct and effective operation of the telecom network as it evolves. IM actions have the objective to monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs). The Inventory Management NRM IRP defines the inventory specific network resource information between an IRP Agent and one or several IRP Managers.
+
+### **SON Policy NRM IRP – 32.521 [80], 32.522 [81], 32.526 [82]**
+
+The SON Policy NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Self-Organizing Networks Policies. Currently the following SON use cases are supported by this NRM IRP:
+
+- SON Self-Optimization Management (requirements determined by TS 32.521[80])
+- SON Self-Healing Management (requirements determined by TS 32.541[86])
+- Energy Saving Management (requirements determined by TS 32.551[87])
+
+### **Transport Network NRM IRP – 32.711 [116], 32.712 [117], 32.716 [118]**
+
+The Transport Network NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Transport resources, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **Repeater NRM IRP – 32.721 [119], 32.722 [120], 32.726 [121]**
+
+The Repeater NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Repeater resources, by reusing relevant parts of the Generic NRM IRP in 32.621 [95], 32.622 [96], 32.626 [97] series.
+
+### **Signalling Transport NW IF NRM IRP – 32.741 [125], 32.742 [126], 32.746 [127]**
+
+The Signalling Transport NW IF NRM IRP defines an IRP through which an IRP Agent can communicate Configuration Management information to one or several IRP Managers concerning Signalling Transport resources, by reusing relevant parts of the Generic NRM IRP in 32.621[95], 32.622 [96], 32.626 [97] series.
+
+# 7 Measurement & Trace Definitions
+
+## 7.1 Performance Measurements
+
+### 7.1.1 Overview and relationships to IRP Framework
+
+![Diagram showing PM-related Specifications 3GPP R10. It consists of five boxes: 'Requirements and templates' (blue border), 'Core measurement specifications' (yellow border), 'Radio measurement specifications' (yellow border), 'KPI specifications' (yellow border), and 'PM File Format (32.43x)' (yellow border).](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg)
+
+**Requirements and templates:**
+
+- Concept and requirements (32.401)
+- Definitions and template (32.404)
+
+**Core measurement specifications**
+
+- CS core (32.407)
+- PS core (32.406)
+- IMS (32.409)
+- EPC (32.426)
+- Services (32.408)
+
+**Radio measurement specifications**
+
+- GSM (52.402)
+- UTRAN (32.405)
+- E-UTRAN (32.425)
+- HNB (32.452)
+- HeNB (32.453)
+
+**KPI specifications**
+
+- UMTS and GSM (32.410)
+- E-UTRAN – (32.450/451)
+- IMS (32.454)
+- EPC (32.455)
+
+**PM File Format (32.43x)**
+
+Diagram showing PM-related Specifications 3GPP R10. It consists of five boxes: 'Requirements and templates' (blue border), 'Core measurement specifications' (yellow border), 'Radio measurement specifications' (yellow border), 'KPI specifications' (yellow border), and 'PM File Format (32.43x)' (yellow border).
+
+Figure 7.1.1-1: PM-related Specifications 3GPP R10
+
+### 7.1.2 Performance Measurement Specifications
+
+#### **PS core Performance Measurements – 32.406 [51]**
+
+The purpose of this specification is to define performance measurements specific to Core Network Packet Switched Domain in a UMTS network or combined UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **CS core Performance Measurements – 32.407 [52]**
+
+The purpose of this specification is to define performance measurements specific to Core Network Circuit Switched Domain in a UMTS network or combined UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **Services Performance Measurements – 32.408 [53]**
+
+The purpose of this specification is to define performance measurements specific to teleservices(categorized by Multimedia Messaging Service, Short Message Service, Multimedia Calls, Voice Call and Intelligent Services) in a UMTS network or combined UMTS/GSM network, . The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **IMS Performance Measurements – 32.409 [54]**
+
+The purpose of this specification is to define performance measurements specific to an IMS (IP Multimedia Subsystem) network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **EPC Performance Measurements – 32.426 [63]**
+
+The purpose of this specification is to define performance measurements specific to an EPC network or combined EPC/UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **GSM Performance Measurements – 52.402 [140]**
+
+The purpose of this specification is to define performance measurements specific to a GSM system. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.**UTRAN Performance Measurements – 32.405 [50]**
+
+The purpose of this specification is to define performance measurements specific to a UTRAN in UMTS network or combined UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **E-UTRAN Performance Measurements – 32.425 [62]**
+
+The purpose of this specification is to define performance measurements specific to an E-UTRAN network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.**HNB Performance Measurements – 32.452 [71]**
+
+The purpose of this specification is to define performance measurements specific to Home NodeB Subsystem(consists of HNB and HNB-GW). The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **HeNB Performance Measurements – 32.453 [72]**
+
+The purpose of this specification is to define performance measurements specific to Home enhanced NodeB Subsystem(consists of HeNB and optionally HeNB-GW). The standardized measurements result in comparability of measurement data produced in a multi-vendor network.
+
+#### **UMTS & GSM KPI's – 32.410 [55]**
+
+The purpose of this specification is to define Key Performance Indicators (KPIs) for GSM and UMTS. KPI definitions include high level KPIs that are a) common across GSM and UMTS networks; and b) **specific** to network techniques such as GSM and UMTS networks.
+
+#### **E-UTRAN KPI's – 32.451 [70]**
+
+This specification defines requirements (business level requirements, specification level requirements and use case descriptions) related to KPIs for E-UTRAN.
+
+#### **IMS KPI's – 32.454 [73]**
+
+This specification defines KPIs for the IP Multimedia Subsystem (IMS).
+
+#### **EPC KPI's – 32.455 [74]**
+
+This specification defines KPIs for the Evolved Packet Core(EPC).network.
+
+#### **PM File Format – 32.432 [64], 32.435 [65], 32.436 [66]**
+
+This set of specifications describe the general semantics of performance measurement result and collection. It defines the report file format, report file conventions, and the file transfer procedure.
+
+## 7.2 Trace Specifications
+
+### 7.2.1 Overview and relationships to IRP Framework
+
+![A yellow-bordered box titled 'Trace specifications:' containing a bulleted list of three items: 'Concept and requirements (32.421)', 'Trace control and configuration management (32.422)', and 'Trace data definition (32.423)'.](759c7d62402f0b4651ddce292be5bdef_img.jpg)
+
+Trace specifications:
+
+- Concept and requirements (32.421)
+- Trace control and configuration management (32.422)
+- Trace data definition (32.423)
+
+A yellow-bordered box titled 'Trace specifications:' containing a bulleted list of three items: 'Concept and requirements (32.421)', 'Trace control and configuration management (32.422)', and 'Trace data definition (32.423)'.
+
+**Figure 7.2.1-2: Trace-related Specifications 3GPP R10**
+
+### 7.2.2 Trace Specifications
+
+#### **Trace Control & Configuration – 32.422 [60]**
+
+This specification describes the mechanisms used for the control and configuration of the Trace functionality at the EMs, NEs and UEs. It covers the triggering events for starting/stopping of subscriber/UE activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of Trace results in the Network Elements (NEs) and User Equipment (UE) and the transfer of these results to one or more EM(s) and/or Network Manager(s) (NM(s)).
+
+#### **Trace Data Definitions – 32.423 [61]**
+
+This specification describes Trace data definition and management. It covers the trace records content, their format and transfer.
+
+# --- 8 Relationships between IRPs
+
+Relationships between Interface IRP's:
+
+- All Interface IRP's utilizing the functionality of the Generic IRP
+- All Notification emitting Interface IRP's utilizing the functionality of the Notification IRP
+
+Relationships between NRM IRP's:
+
+- All NRM IRP's utilizing the functionality of the Generic NRM IRP
+- All function-specific NRM IRP (e.g. Core NRM IRP) utilizing the functionality of the Inventory NRM IRP
+
+# 9 SON Functions
+
+In order to reduce the operating expenses (OPEX) associated with the management of increasing number of nodes from more than one vendor the concept of the Self-Organizing Network (SON) was introduced. Automation of some network planning, configuration and optimisation processes via the use of SON functions can help the network operator to reduce OPEX by reducing manual involvement in such tasks.
+
+TS 32.500 [75] identifies the following SON use cases in context of LTE network for standardization:
+
+- Self-establishment of an eNodeB: Related requirements are defined in TS 32.501 [76];
+- Automatic Neighbour Relation Management: Related requirements are defined in TS 32.511 [79];
+- Self-Optimisation Management: Related requirements are defined in TS 32.521 [80];
+- Self-Healing Management: Related requirements are defined in TS 32.541 [86];
+- Energy Saving Management: Related requirements are defined in TS 32.551 [87];
+- Minimization of Drive Tests: Related requirements are defined in TS 32.421 [59] and TS 32.441 [67].
+
+Each SON use case can involve multiple IRPs when corresponding management scenarios are applied. The IRP relationships of SON functions are addressed case by case as follows,
+
+## Self-establishment of an eNodeB
+
+- Generic IRP (32.311[25], 32.312 [26], 32.316 [27] )
+- Alarm IRP (32.111-1 [5], 32.111-2 [6], 32.111-6 [7])
+- Test Management IRP (32.321[28], 32.322[29], 32.326 [30] )
+- Basic CM IRP (32.600 [88], 32.601 [89], 32.602 [90], 32.606 [91]) or Bulk CM IRP (32.611 [92], 32.612 [93], 32.616 [94])
+- Kernel CM IRP (32.661 [107], 32.662 [108] )
+- SC IRP (32.500 [75], 32.501 [76], 32.502 [77], 32.506 [78] )
+- Software Management IRP (32.531 [83], 32.532 [84], 32.536 [85])
+- Notification IRP (32.300 [21], 32.301[22], 32.302 [23], 32.306 [24] )
+- File Transfer IRP (for ARCF data download) (32.341[34], 32.342[35], 32.346[36])
+- Generic NRM IRP (32.621 [95], 32.622 [96], 32.626 [97])
+- EUTRAN NRM IRP (32.761 [131], 32.762 [132], 32.766 [133])
+
+## Automatic Neighbour Relation Management
+
+- Alarm IRP (32.111-1 [5], 32.111-2 [6], 32.111-6 [5])
+- Basic CM IRP (32.600 [88], 32.601 [89], 32.602 [90], 32.606 [91]) or Bulk CM IRP (32.611 [92], 32.612 [93], 32.616 [94])
+- Kernel CM IRP (32.661 [107], 32.662 [108])
+- Notification IRP (32.300 [21], 32.301 [22], 32.302 [23], 32.306 [24] )
+- Generic NRM IRP (32.621 [95], 32.622 [96], 32.626 [97]) EUTRAN NRM IRP (32.761 [131], 32.762 [132], 32.766 [133])
+
+## Self-Optimisation Management
+
+- Alarm IRP (32.111-1 [5], 32.111-2 [6], 32.111-6 [7] )
+
+- PM IRP (32.410 [55], 32.411 [56], 32.412 [57], 32.416 [58] )
+- File Transfer IRP (for PM data upload) (32.341[34], 32.342[35], 32.346[36] Basic CM IRP (32.600 [88], 32.601 [89], 32.602 [90], 32.606 [91]) or Bulk CM IRP (32.611 [92], 32.612 [93], 32.616 [94])
+- Kernel CM IRP (32.661 [107], 32.662 [108])
+- Notification IRP (32.300 [21], 32.301 [22], 32.302 [23], 32.306 [24]) NRM IRP (32.521[80], 32.522 [81], 32.526 [82] )
+- Generic NRM IRP (32.621 [95], 32.622 [96], 32.626 [97])
+- EUTRAN NRM IRP (32.761 [131], 32.762 [132], 32.766 [133])
+- EUTRAN Performance Measurements (32.425 [62])
+
+## **Self-Healing Management**
+
+- Alarm IRP (32.111-1 [5], 32.111-2 [6], 32.111-6 [7])
+- Basic CM IRP (32.600 [88], 32.601 [89], 32.602 [90], 32.606 [91] ) or Bulk CM IRP (32.611 [92], 32.612 [93], 32.616 [94])
+- Kernel CM IRP (32.661 [107], 32.662 [108])
+- Notification IRP (32.300 [21], 32.301 [22], 32.302 [23], 32.306 [24] )
+- SON Policy NRM IRP (32.521[80], 32.522 [81], 32.526 [82] Generic NRM IRP (32.621 [95], 32.622 [96], 32.626 [97])
+- EUTRAN NRM IRP (32.761 [131], 32.762 [132], 32.766 [133])
+
+## **Energy Saving Management**
+
+- PM IRP (32.410 [55], 32.411 [56], 32.412 [57], 32.416 [58] )
+- File Transfer IRP (for PM data upload) (32.341[34], 32.342[35], 32.346[36])
+- Basic CM IRP (32.600 [88], 32.601 [89], 32.602 [90], 32.606 [91]) or Bulk CM IRP (32.611 [92], 32.612 [93], 32.616 [94])
+- Kernel CM IRP (32.661 [107], 32.662 [108])
+- Notification IRP (32.300 [21], 32.301 [22], 32.302 [23], 32.306 [24] )
+- SON Policy NRM IRP (32.521 [80], 32.522 [81], 32.526 [82])
+- Generic NRM IRP (32.621 [95], 32.622 [96], 32.626 [97])
+- EUTRAN NRM IRP (32.761 [131], 32.762 [132], 32.766 [133]) EUTRAN Performance Measurements (32.425 [62])
+
+## **Minimization of Drive Tests**
+
+- Basic CM IRP (32.600 [88], 32.601 [89], 32.602 [90], 32.606 [91]) or Bulk CM IRP (32.611 [92], 32.612 [93], 32.616 [94])
+- Kernel CM IRP (32.661 [107], 32.662 [108])
+- Trace Management IRP (32.441 [67], 32.442 [68], 32.446 [69] )
+- Trace Control and Configuration Management IRP (32.421 [59], 32.422 [60], 32.423 [61])
+- Generic NRM IRP (32.621[95], 32.622 [96], 32.626 [97] )
+- UTRAN NRM IRP (32.641[101], 32.642 [102], 32.646 [103] )
+- EUTRAN NRM IRP (32.761 [131], 32.762 [132], 32.766 [133])
+
+# --- Annex A (Informative): IRP Packaging Suggestions
+
+## A.1 Overview & Purpose
+
+This Annex provides IRP packaging suggestions, intended to guide service providers as well as equipment and solutions providers to identify and choose suitable standardized management interface capabilities.
+
+Note: No IRP Packaging Suggestions are identified for the present document.
+
+# Annex B (informative): Change history
+
+| Change history |       |           |    |     |                                    |  |  |       |        |
+|----------------|-------|-----------|----|-----|------------------------------------|--|--|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                    |  |  | Old   | New    |
+| 2010-12        | SP-50 | SP-100764 | -- | --  | Submitted to SA#50 for Information |  |  | 0.1.0 | 1.0.0  |
+| 2011-05        | SP-52 | SP-110272 | -- | --  | Submitted to SA#52 for Approval    |  |  | 1.2.0 | 2.0.0  |
+| 2011-06        | SP-52 | --        | -- | --  | Publication                        |  |  | 2.0.0 | 10.0.0 |
+
+| Change history |         |           |      |     |     |                                                                            |  |             |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------|--|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                            |  | New version |
+| 2020-09        | SA#89E  | SP-200728 | 0019 | -   | F   | Correction of reference list and adding references throughout the document |  | 10.1.0      |

marked/Rel-10/32_series/32111-1/raw.md

@@ -0,0 +1,623 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Fault Management; Part 1: 3G fault management requirements (Release 10)** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in bold lowercase letters with a red signal icon above the "l", and the word "ADVANCED" in smaller uppercase letters to the right. A trademark symbol (TM) is at the bottom right.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold font with a red signal icon below the "P", and a trademark symbol (TM) at the top right.
+
+3GPP logo
+
+Keywords  
+UMTS, management, alarm
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2015, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                              |    |
+|------------------------------------------------------------------------------|----|
+| Foreword .....                                                               | 4  |
+| Introduction .....                                                           | 4  |
+| 1 Scope.....                                                                 | 6  |
+| 2 References.....                                                            | 6  |
+| 3 Definitions and abbreviations .....                                        | 7  |
+| 3.1 Definitions.....                                                         | 7  |
+| 3.2 Abbreviations .....                                                      | 8  |
+| 4 Fault Management concept and requirements .....                            | 8  |
+| 4.0 Introduction .....                                                       | 8  |
+| 4.1 Faults and alarms.....                                                   | 8  |
+| 4.1.0 Introduction .....                                                     | 8  |
+| 4.1.1 Fault detection .....                                                  | 9  |
+| 4.1.2 Generation of alarms .....                                             | 10 |
+| 4.1.3 Clearing of alarms .....                                               | 10 |
+| 4.1.4 Alarm forwarding and filtering .....                                   | 11 |
+| 4.1.5 Storage and retrieval of alarms in/from the NE.....                    | 12 |
+| 4.1.6 Fault Recovery.....                                                    | 12 |
+| 4.1.7 Configuration of Alarms.....                                           | 13 |
+| 4.1.8 Correlation of Alarms and Events .....                                 | 13 |
+| 4.1.9 Root Cause Analysis.....                                               | 13 |
+| 4.2 State Management.....                                                    | 14 |
+| 4.2.0 Introduction .....                                                     | 14 |
+| 4.2.1 Propagation of state change.....                                       | 14 |
+| 4.3 Test management.....                                                     | 15 |
+| 5 Fault Management over Itf-N .....                                          | 15 |
+| 5.1 Fault Management concept .....                                           | 15 |
+| 5.2 Management of alarm event reports.....                                   | 16 |
+| 5.2.1 Mapping of alarm and related state change event reports .....          | 16 |
+| 5.2.2 Real-time forwarding of event reports.....                             | 16 |
+| 5.2.3 Alarm clearing .....                                                   | 16 |
+| 5.3 Retrieval of alarm information .....                                     | 17 |
+| 5.3.0 Introduction .....                                                     | 17 |
+| 5.3.1 Retrieval of current alarm information on NM request.....              | 17 |
+| 5.3.2 Logging and retrieval of alarm history information on NM request ..... | 17 |
+| 5.4 Co-operative alarm acknowledgement on the Itf-N.....                     | 18 |
+| 5.5 Overview of IRPs related to Fault Management (FM) .....                  | 18 |
+| Annex A (informative): Change history.....                                   | 19 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+**32.111-1 "Fault Management; Part 1: 3G fault management requirements".**
+
+32.111-2 "Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+
+32.111-3 "Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
+
+32.111-6 "Fault Management; Part 6: Alarm 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].
+
+A 3G system is composed of a multitude of Network Elements (NE) of various types and, typically, different vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users' communication requirements. The occurrence of failures in a NE may cause a deterioration of this NE's function and/or service quality and will, in severe cases, lead to the complete unavailability of the respective NE. In order to minimize the effects of such failures on the Quality of Service (QoS) as perceived by the network users it is necessary to:
+
+- detect failures in the network as soon as they occur and alert the operating personnel as fast as possible;
+- isolate the failures (autonomously or through operator intervention), i.e. switch off faulty units and, if applicable, limit the effect of the failure as much as possible by reconfiguration of the faulty NE/adjacent NEs;
+- if necessary, determine the cause of the failure using diagnosis and test routines; and,
+- repair/eliminate failures in due time through the application of maintenance procedures.
+
+This aspect of the management environment is termed "Fault Management" (FM). The purpose of FM is to detect failures as soon as they occur and to limit their effects on the network Quality of Service (QoS) as far as possible. The latter is achieved by bringing additional/redundant equipment into operation, reconfiguring existing equipment/NEs, or by repairing/eliminating the cause of the failure.
+
+Fault Management (FM) encompasses all of the above functionalities except commissioning/decommissioning of NEs and potential operator triggered reconfiguration (these are a matter of Configuration Management (CM), cf. [1]). FM also includes associated features in the Operations System (OS), such as the administration of a pending alarms list, the presentation of operational state information of physical and logical devices/resources/functions, and the provision and analysis of the alarm and state history of the network.
+
+# --- 1 Scope
+
+The present document specifies the overall requirements for 3G Fault Management (FM) as it applies to the Network Elements (NE), Element Manager (EM) and Network Manager (NM).
+
+Clause 4 defines the FM concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardization of these functions across the different vendors' equipment is not required. The functional areas specified in the present document cover:
+
+- fault surveillance and detection in the NEs;
+- notification of alarms (including alarm cease) and operational state changes;
+- retrieval of current alarms from the NEs;
+- fault isolation and defence mechanisms in the NEs;
+- alarm filtering;
+- management of alarm severity levels;
+- alarm and operational state data presentation and analysis at the Operations System (OS);
+- retention of alarm and operational state data in the NEs and the OS; and
+- the management of tests.
+
+Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of the present document. These are described in [1].
+
+Clause 5 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3G networks, as seen from the Network Manager (NM). The Itf-N is fully standardized so as to connect systems of any vendor to the NM via this interface.
+
+# --- 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.601: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements".
+- [2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [3] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [4] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
+- [5] ITU-T Recommendation X.710: "Information technology - Open Systems Interconnection - Common Management Information Service".
+
+- [6] ITU-T Recommendation X.711: "Managed objects for diagnostic information of public switched telephone network connected V-series modem DCE's".
+- [7] ITU-T Recommendation X.721: "Information technology - Open Systems Interconnection - Structure of management information: Definition of management information".
+- [8] ITU-T Recommendation X.731: "Information technology - Open Systems Interconnection - Systems Management: State management function".
+- [9] ITU-T Recommendation X.733: "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function".
+- [10] ITU-T Recommendation X.734: "Information technology - Open Systems Interconnection - Systems Management: Event report management function".
+- [11] ITU-T Recommendation X.735: "Information technology - Open Systems Interconnection - Systems Management: Log control function".
+- [12] ITU-T Recommendation X.745: "Information technology - Open Systems Interconnection - Systems Management: Test management function".
+- [13] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP); Information Service (IS)".
+- [14] 3GPP TS 32.111-3: "Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
+- [15] Void.
+- [16] ISO 8571: "File Transfer, Access and Management".
+- [17] 3GPP TS 32.111-7: "Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP); SOAP Solution Set (SS)".
+- [18] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3], 3GPP TS 21.905 [18] and the following apply:
+
+**active alarm:** an alarm that has not been cleared and which is active until the fault that caused the alarm is corrected and a "clear alarm" is generated.
+
+**ADAC Faults:** faults that are "Automatically Detected and Automatically Cleared" by the system when they occur and when they are repaired.
+
+**ADMC Faults:** faults that are Automatically Detected by the system when they occur and Manually Cleared by the operator when they are repaired.
+
+**alarm:** abnormal network entity condition, which categorizes an event as a fault.
+
+**alarm notification:** notification used to inform the recipient about the occurrence of an alarm.
+
+**clear alarm:** alarm where the severity value is set to "cleared".
+
+**event:** this is a generic term for any type of occurrence within a network entity.
+
+NOTE: A notification or event report may be used to inform one or more OS(s) about the occurrence of the event.
+
+**fault:** a deviation of a system from normal operation, which may result in the loss of operational capabilities of the element or the loss of redundancy in case of a redundant configuration.
+
+**Itf-N:** Management interface defined in 3GPP TS 32.101 [2] subclause 5.1.2.2 and 3GPP TS 32.102 [3] subclause 7.3.2.
+
+**notification:** information message originated within a network entity to inform one or more OS(s) about the occurrence of an event.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3], 3GPP TS 21.905 [18] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 21.905 [18], in that order.
+
+|      |                                                  |
+|------|--------------------------------------------------|
+| ADAC | Automatically Detected and Automatically Cleared |
+| ADMC | Automatically Detected and Manually Cleared      |
+| CM   | Configuration Management                         |
+| EM   | Element Manager                                  |
+| FM   | Fault Management                                 |
+| ISO  | International Standards Organisation             |
+| IRP  | Integration Reference Point                      |
+| MMI  | Man-Machine Interface                            |
+| MOC  | Managed Object Class                             |
+| MOI  | Managed Object Instance                          |
+| NE   | Network Element                                  |
+| NM   | Network Manager                                  |
+| OS   | Operations System                                |
+| QoS  | Quality of Service                               |
+| TMN  | Telecommunications Management Network            |
+
+# --- 4 Fault Management concept and requirements
+
+## 4.0 Introduction
+
+Any evaluation of the NEs' and the overall network health status require the detection of faults in the network and, consequently, the notification of alarms to the OS (EM and/or NM). Depending on the nature of the fault, it may be combined with a change of the operational state of the logical and/or physical resource(s) affected by the fault.
+
+Detection and notification of these state changes is as essential as it is for the alarms. A list of active alarms in the network and operational state information as well as alarm/state history data are required by the system operator for further analysis. Additionally, test procedures can be used in order to obtain more detailed information if necessary, or to verify an alarm or state or the proper operation of NEs and their logical and physical resources.
+
+The following clauses explain the detection of faults, the handling of alarms and state changes and the execution of tests.
+
+Only those requirements covered by clause 5 and related IRPs shall be considered as valid requirements for compliance to the standard defined by the present document.
+
+## 4.1 Faults and alarms
+
+### 4.1.0 Introduction
+
+Faults that may occur in the network can be grouped into one of the following categories:
+
+- Hardware failures, i.e. the malfunction of some physical resource within a NE.
+- Software problems, e.g. software bugs, database inconsistencies.
+
+- Functional faults, i.e. a failure of some functional resource in a NE and no hardware component can be found responsible for the problem.
+- Loss of some or all of the NE's specified capability due to overload situations.
+- Communication failures between two NEs, or between NE and OS, or between two OSs.
+
+In any case, as a consequence of faults, appropriate alarms related to the physical or logical resource(s) affected by the fault(s), shall be generated by the network entities.
+
+The following clauses focus on the aspects of fault detection, alarm generation and storage, fault recovery and retrieval of stored alarm information.
+
+### 4.1.1 Fault detection
+
+When any type of fault described above occurs within a 3G network, the affected network entities shall be able to detect them immediately.
+
+The network entities accomplish this task using autonomous self-check circuits/procedures, including, in the case of NEs, the observation of measurements, counters and thresholds. The threshold measurements may be predefined by the manufacturer and executed autonomously in the NE, or they may be based on performance measurements administered by the EM, cf. [4]. The fault detection mechanism as defined above shall cover both active and standby components of the network entities.
+
+The majority of the faults should have well-defined conditions for the declaration of their presence or absence, i.e. fault occurrence and fault clearing conditions. Any such incident shall be referred to in the present document as an ADAC fault. The network entities should be able to recognize when a previously detected ADAC fault is no longer present, i.e. the clearing of the fault, using similar techniques as they use to detect the occurrence of the fault. For some faults, no clearing condition exists. For the purpose of the present document, these faults shall be referred to as ADMC faults. An example of this is when the network entity has to restart a software process due to some inconsistencies, and normal operation can be resumed afterwards. In this case, although the inconsistencies are cleared, the cause of the problem is not yet corrected. Manual intervention by the system operator shall always be necessary to clear ADMC faults since these, by definition, cannot be cleared by the network entity itself.
+
+For some faults there is no need for any short-term action, neither from the system operator nor from the network entity itself, since the fault condition lasted for a short period of time only and then disappeared. An example of this is when a NE detects the crossing of some observed threshold, and in the next sampling interval, the observed value stays within its limits.
+
+For each fault, the fault detection process shall supply the following information:
+
+- the device/resource/file/functionality/smallest replaceable unit as follows:
+  - for hardware faults, the smallest replaceable unit that is faulty;
+  - for software faults, the affected software component, e.g. corrupted file(s) or databases or software code;
+  - for functional faults, the affected functionality;
+  - for faults caused by overload, information on the reason for the overload;
+  - for all the above faults, wherever applicable, an indication of the physical and logical resources that are affected by the fault if applicable, a description of the loss of capability of the affected resource.
+- the type of the fault (communication, environmental, equipment, processing error, QoS) according to ITU-T Recommendation X.733 [9];
+- the severity of the fault (indeterminate, warning, minor, major, critical), as defined in ITU-T Recommendation X.733 [9];
+- the probable cause of the fault;
+- the time at which the fault was detected in the faulty network entity;
+
+- the nature of the fault, e.g. ADAC or ADMC;
+- any other information that helps understanding the cause and the location of the abnormal situation (system/implementation specific).
+
+For some faults, additional means, such as test and diagnosis features, may be necessary in order to obtain the required level of detail. See clause 4.3 for details.
+
+### 4.1.2 Generation of alarms
+
+For each detected fault, appropriate alarms shall be generated by the faulty network entity, regardless of whether it is an ADAC or an ADMC fault. Such alarms shall contain all the information provided by the fault detection process as described in clause 4.1.1.
+
+In order to ease the fault localization and repair, the faulty network entity should generate for each single fault, one single alarm, also in the case where a single fault causes a degradation of the operational capabilities of more than one physical or logical resource within the network entity. An example of this is a hardware fault, which affects not only a physical resource but also degrades the logical resource(s) that this hardware supports. In this case the network entity should generate one single alarm for the faulty resource (i.e. the resource which needs to be repaired) and a number of events related to state management (cf. clause 4.2) for all the physical/logical resources affected by the fault, including the faulty one itself.
+
+In case a network entity is not able to recognize that a single fault manifests itself in different ways, the single fault is detected as multiple faults and originates multiple alarms. In this case however, when the fault is repaired the network entity should be able to detect the repair of all the multiple faults and clear the related multiple alarms.
+
+When a fault occurs on the connection media between two NEs or between a NE and an OS, and affects the communication capability between such NE/OS, each affected NE/OS shall detect the fault as described in clause 4.1.1 and generate its own associated communication alarm toward the managing OS. In this case it is the responsibility of the OS to correlate alarms received from different NEs/OSs and localize the fault in the best possible way.
+
+Within each NE, all alarms generated by that NE shall be input into a list of active alarms. The NEs shall be able to provide such a list of active alarms to the OS when requested.
+
+### 4.1.3 Clearing of alarms
+
+The alarms originated in consequence of faults need to be cleared. To clear an alarm it is necessary to repair the corresponding fault. The procedures to repair faults are implementation dependent and therefore they are out of the scope of the present document, however, in general:
+
+- the equipment faults are repaired by replacing the faulty units with working ones;
+- the software faults are repaired by means of partial or global system initializations, by means of software patches or by means of updated software loads;
+- the communication faults are repaired by replacing the faulty transmission equipment or, in case of excessive noise, by removing the cause of the noise;
+- the QoS faults are repaired either by removing the causes that degraded the QoS or by improving the capability of the system to react against the causes that could result in a degradation of the QoS;
+- Solving the environmental problem repairs the environment faults (high temperature, high humidity, etc.).
+
+It is also possible that an ADAC fault is spontaneously repaired, without the intervention of the operator (e.g. a threshold crossed fault). In this case the NE behaves as for the ADAC faults repaired by the operator.
+
+In principle, the NE uses the same mechanisms to detect that a fault has been repaired, as for the detection of the occurrence of the fault. However, for ADMC faults, manual intervention by the operator is always necessary to clear the fault. Practically, various methods exist for the system to detect that a fault has been repaired and clear alarms and the faults that triggered them. For example:
+
+- The system operator implicitly requests the NE to clear a fault, e.g. by initializing a new device that replaces a faulty one. Once the new device has been successfully put into service, the NE shall clear the fault(s). Consequently, the NE shall clear all related alarms.
+- The system operator explicitly requests the clearing of one or more alarms. Once the alarm(s) has/have been cleared, the fault management system (within EMS and/or NE) should reissue those alarms (as new alarms) in case the fault situation still persists.
+- The NE detects the exchange of a faulty device by a new one and initializes it autonomously. Once the new device has been successfully put into service, the NE shall clear the fault(s). Consequently, the NE shall clear all related alarms.
+- The NE detects that a previously reported threshold crossed alarm is no longer valid. It shall then clear the corresponding active alarm and the associated fault, without requiring any operator intervention. The details for the administration of thresholds and the exact condition for the NE to clear a threshold crossed alarm are implementation specific and depend on the definition of the threshold measurement, see also clause 4.1.1.
+- ADMC faults/alarms can, by definition, not be cleared by the NE autonomously. Therefore, in any case, system operator functions shall be available to request the clearing of ADAC alarms/faults in the NE. Once an ADMC alarm/fault has been cleared, the NE shall clear the associated ADAC fault/alarm.
+
+Details of these mechanisms are system/implementation specific.
+
+Each time an alarm is cleared the NE shall generate an appropriate clear alarm event. A clear alarm is defined as an alarm, as specified in clause 3.1, except that its severity is set to "cleared". The relationship between the clear alarm and the active alarm is established:
+
+- by re-using a set of parameters that uniquely identify the active alarm (see clause 4.1.1); or
+- by including a reference to the active alarm in the clear alarm.
+
+When a clear alarm is generated the corresponding active alarm is removed from the active alarm list.
+
+### 4.1.4 Alarm forwarding and filtering
+
+As soon as an alarm is entered into or removed from the active alarms list Alarm notifications shall be forwarded by the NE, in the form of unsolicited notifications;
+
+If forwarding is not possible at this time, e.g. due to communication breakdown, then the notifications shall be sent as soon as the communication capability has been restored. The storage space is limited. The storage capacity is Operator and implementation dependent. If the number of delayed notifications exceeds the storage space then an alarm synchronization procedure shall be run when the communication capability has been restored.
+
+The OS shall detect the communication failures that prevent the reception of alarms and raise an appropriate alarm to the operator.
+
+If the Itf-N is implemented in the NE, then the destination of the notifications is the NM, and the interface shall comply with the stipulations made in clause 5. If the Itf-N resides in the EM, proprietary means may be employed to forward the notifications to the EM. Note that, even if the Itf-N is implemented in the NE, the EM may still also receive the notifications by one of the above mechanisms. However, the present document does not explicitly require the NEs to support the EM as a second destination.
+
+The event report shall include all information defined for the respective event (see clauses 4.1.1, 4.1.2 and 4.1.3), plus an identification of the NE that generated the report.
+
+The system operator shall be able to allow or suppress alarm reporting for each NE. As a minimum, the following criteria shall be supported for alarm filtering:
+
+- the NE that generated the alarm, i.e. all alarm messages for that NE shall be suppressed;
+- the device/resource/function to which the alarm relates;
+- the severity of the alarm;
+
+- the time at which the alarm was detected, i.e. the alarm time; and,
+- any combination of the above criteria.
+
+The result of any command to modify the forwarding criteria shall be confirmed by the NE to the requesting operator.
+
+### 4.1.5 Storage and retrieval of alarms in/from the NE
+
+For Fault Management (FM) purposes, each NE shall have to store and retain the following information:
+
+- a list of all active alarms, i.e. all alarms that have not yet been cleared; and
+- alarm history information, i.e. all notifications related to the occurrence and clearing of alarms.
+
+It shall be possible to apply filters when active alarm information is retrieved by the Manager and when the history information is stored by the NE and retrieved by the Manager.
+
+The storage space for alarm history in the NE is limited. Therefore it shall be organized as a circular buffer, i.e. the oldest data item(s) shall be overwritten by new data if the buffer is full. Further "buffer full" behaviours, e.g. those defined in ITU-T Recommendation X.735 [11], may be implemented as an option. The storage capacity itself, and thus the duration, for which the data can be retained, shall be Operator and implementation dependent.
+
+### 4.1.6 Fault Recovery
+
+After a fault has been detected and the replaceable faulty units have been identified, some management functions are necessary in order to perform system recovery and/or restoration, either automatically by the NE and/or the EM, or manually by the operator.
+
+The fault recovery functions are used in various phases of the Fault Management (FM):
+
+- 1) Once a fault has been detected, the NE shall be able to evaluate the effect of the fault on the telecommunication services and autonomously take recovery actions in order to minimize service degradation or disruption.
+- 2) Once the faulty unit(s) has (have) been replaced or repaired, it shall be possible from the EM to put the previously faulty unit(s) back into service so that normal operation is restored. This transition should be done in such a way that the currently provided telecommunication services are not, or only minimally, disturbed.
+- 3) At any time the NE shall be able to perform recovery actions if requested by the operator. The operator may have several reasons to require such actions; e.g. he has deduced a faulty condition by analysing and correlating alarm reports, or he wants to verify that the NE is capable of performing the recovery actions (proactive maintenance).
+
+The recovery actions that the NE performs (autonomously or on demand) in case of faults depend on the nature and severity of the faults, on the hardware and software capabilities of the NE and on the current configuration of the NE.
+
+Faults are distinguished in two categories: software faults and hardware faults. In the case of software faults, depending on the severity of the fault, the recovery actions may be system initializations (at different levels), activation of a backup software load, activation of a fallback software load, download of a software unit etc. In the case of hardware faults, the recovery actions depend on the existence and type of redundant (i.e. back-up) resources. Redundancy of some resources may be provided in the NE in order to achieve fault tolerance and to improve system availability.
+
+If the faulty resource has no redundancy, the recovery actions shall be:
+
+- a) Isolate and remove from service the faulty resource so that it cannot disturb other working resources;
+- b) Remove from service the physical and functional resources (if any) which are dependent on the faulty one. This prevents the propagation of the fault effects to other fault-free resources;
+- c) State management related activities for the faulty resource and other affected/dependent resources cf. clause 4.2;
+- d) Generate and forward appropriate notifications to inform the OS about all the changes performed.
+
+If the faulty resource has redundancy, the NE shall perform action a), c) and d) above and, in addition, the recovery sequence that is specific to that type of redundancy. Several types of redundancy exist (e.g. hot standby, cold standby, duplex, symmetric/asymmetric, N plus one or N plus K redundancy, etc.), and for each one, there is a specific sequence
+
+of actions to be performed in case of failure. The present document specifies the Fault Management aspects of the redundancies, but it does not define the specific recovery sequences of the redundancy types.
+
+In the case of a failure of a resource providing service, the recovery sequence shall start immediately. Before or during the changeover, a temporary and limited loss of service shall be acceptable. In the case of a management command, the NE should perform the changeover without degradation of the telecommunication services.
+
+The detailed definition of the management of the redundancies is out of the scope of the present document. If a fault causes the interruption of ongoing calls, then the interrupted calls shall be cleared, i.e. all resources allocated to these calls shall immediately be released by the system.
+
+### 4.1.7 Configuration of Alarms
+
+It shall be possible to configure the alarm actions, thresholds and severities by means of commands, according to the following requirements:
+
+- the operator shall be able to configure any threshold that determines the declaration or clearing of a fault. If a series of thresholds are defined to generate alarms of various severities, then for each alarm severity the threshold values shall be configurable individually.
+- it shall be possible to modify the severity of alarms defined in the system, e.g. from major to critical. This capability should be implemented on the manager, however, in case it is implemented on the NE, the alarms forwarded by the NE to the OS and the alarms displayed on the local MMI shall have the same severity.
+
+The NE shall confirm such alarm configuration commands and shall notify the results to the requesting system operator.
+
+### 4.1.8 Correlation of Alarms and Events
+
+A single network fault may result in the generation of multiple alarms and events from affected entities over time and spread over a wide geographical area. If possible, the OS should indicate which alarms and events are correlated to each other.
+
+Alarms may be correlated in view of certain rules such as alarm propagation path, specific geographical area, specific equipment, or repeated alarms from the same source. The alarms are partitioned into sets where alarms within one correlated set have a high probability of being caused by the same network fault. A correlated set may also contain events. These events are considered having a high probability of being related to the same network fault.
+
+The correlation describes relations between network events (e.g. current alarms as those captured in AlarmList, historical alarms as those captured in NotificationLog, network configuration changes).
+
+### 4.1.9 Root Cause Analysis
+
+For a set of correlated alarms, one alarm may relate to the fault which is the root cause of all the correlated alarms and events. If possible, the OS should perform a Root Cause Analysis to identify and indicate the Root Cause Alarm.
+
+Root Cause Analysis is a process that can determine and identify the network condition (e.g. fault, mis-configuration) causing the alarms. The determination may be based on the following (for example):
+
+- Information carried in alarm(s);
+- Information carried in correlated alarm sets;
+- Information carried in network notifications;
+- Network configuration information;
+- Operators' network management experience.
+
+## 4.2 State Management
+
+### 4.2.0 Introduction
+
+The State Management is a common service defined within Configuration Management [1] and used by several management areas, including Fault Management. In this clause, some detailed requirements on State Management as they apply to the Fault Management are defined.
+
+From the point of view of Fault Management, only two of the three primary state attributes are really important: the Administrative state and the Operational state. In addition the resources may have some secondary "status" attributes which give further detailed information about the reason of the primary state.
+
+The Administrative state is used by the Operator to make a resource available for service, or to remove a resource from service. For example:
+
+- for fault correction the Administrative state can be used to isolate a faulty resource;
+- in case of redundancy the Administrative state can be used to lock the active resource and let the standby resource to become active (preventive maintenance);
+- for Test management the Administrative state can be used to put a resource out of service to run an intrusive test on it.
+
+The Operational state gives the information about the real capability of a resource to provide or not provide service.
+
+- The operational state is "enabled" when the resource is able to provide service, "disabled" when the resource cannot provide service.
+- A resource can lose the capability to provide service because of a fault or because another resource on which it depends is out of service (e.g. disabled or locked).
+- In case a resource does not lose completely its capability to provide service, the Operational state shall be "enabled" and the Availability status shall be "degraded".
+
+The changes of the state and status attributes of a resource shall be notified to the relative manager(s) as specified in [1].
+
+When a state change is originated by a failure, the alarm notification and the related state change notifications shall be correlated to each other by means of explicit relationship information.
+
+### 4.2.1 Propagation of state change
+
+Within a managed element, when for any reason a resource changes its state, the change shall be propagated, in a consistent way, to all the other resources that are functionally dependent on the first one. Therefore:
+
+- In case of a fault occurring on a resource makes that resource completely out of service, if the current operational state is "enabled", it shall be changed to "disabled" and a state change notification shall be generated. Then, all the dependent resources (following the fault dependency diagram specific to that managed element) shall be checked and, in case they are "enabled" they shall be changed to "disabled". In this process, also the secondary status shall be changed consistently, in a way that it shall be possible to distinguish whether an object is disabled because it is faulty or because of it is functionally dependent on another object which is disabled.
+- In case a faulty resource is repaired, the Operational state of that resource is changed from "disabled" to "enabled" and all the dependent resources are turned back to "enabled" (this is the simple case). In more complex cases, some of the objects may be disabled for different causes (different faults or faults plus locks on different superior resources), in this cases the repaired resource can be turned "enabled" only when all the causes are cleared (i.e. faults are repaired and superior resources are unlocked). Also in this process the secondary status shall be changed consistently.
+- In case the operator locks a resource, the process of the state change propagation is similar to the first case (resource failure) except for the locked resource which does not change its operational state but only the administrative state from "unlocked" to "locked". The dependent resources are processed as in the first case.
+
+- In case the operator unlocks a resource, the process of the state change propagation is similar to the second case (fault reparation) except for the first resource (the unlocked one) which does not change its operational state but only the administrative state from "locked" to "unlocked". The dependent resources are processed as in the first case.
+
+## 4.3 Test management
+
+This management function provides capabilities that can be used in different phases of the Fault Management (FM). For example:
+
+- when a fault has been detected and if the information provided through the alarm report is not sufficient to localize the faulty resource, tests can be executed to better localize the fault;
+- during normal operation of the NE, tests can be executed for the purpose of detecting faults;
+- once a faulty resource has been repaired or replaced, before it is restored to service, tests can be executed on that resource to be sure that it is fault free.
+
+However, regardless of the context where the testing is used, its target is always the same: verify if a system's physical or functional resource performs properly and, in case it happens to be faulty, provide all the information to help the operator to localize and correct the faults.
+
+Testing is an activity that involves the operator, the managing system (the OS) and the managed system (the NE). Generally the operator requests the execution of tests from the OS and the managed NE autonomously executes the tests without any further support from the operator.
+
+In some cases, the operator may request that only a test bed is set up (e.g. establish special internal connections, provide access test points, etc.). The operator can then perform the real tests, which may require some manual support to handle external test equipment. Since the "local maintenance" and the "inter NE testing" are out of the scope of the present document, this aspect of the testing is not treated any further.
+
+The requirements for the test management service are based on ITU-T Recommendation X.745 [12], where the testing description and definitions are specified.
+
+# --- 5 Fault Management over Itf-N
+
+## 5.1 Fault Management concept
+
+An operations system on the network management layer (i.e. the NM) provides fault management services and functions required by the 3G operator on top of the element management layer.
+
+The Itf-N may connect the Network Management (NM) system either to Element Managers (EMs) or directly to the Network Elements (NEs). This is done by means of Integration Reference Points (IRPs). In the following, the term "subordinate entities" defines either EMs or NEs, which are in charge of supporting the Itf-N.
+
+This clause describes the properties of an interface enabling a NM to supervise a 3G-telecommunication network including - if necessary - the managing EMs. To provide to the NM the Fault Management capability for the network implies that the subordinate entities have to provide information about:
+
+- events and failures occurring in the subordinate entities;
+- events and failures of the connections towards the subordinate entities and also of the connections within the 3G network;
+- the network configuration (due to the fact that alarms and related state change information are always originated by network resources, see [1]). This is, however, not part of the FM functionality.
+
+Therefore, for the purpose of FM the subordinate entities send notifications to a NM indicating:
+
+- alarm reports (indicating the occurrence or the clearing of failures within the subordinate entities), so that the related alarm information can be updated;
+
+- state change event reports, so that the related (operational) state information can be updated. This is, however, not part of the FM functionality.
+
+The forwarding of these notifications is controlled by the NM operator using adequate filtering mechanisms within the subordinate entities.
+
+The Itf-N provides also means to allow the NM operator the storage ("logging") and the later evaluation of desired information within the subordinate entities.
+
+The retrieval capability of alarm-related information concerns two aspects:
+
+- retrieval of "dynamic" information (e.g. alarms, states), which describes the momentary alarm condition in the subordinate entities and allows the NM operator a synchronization of its alarm overview data;
+- retrieval of "history" information from the logs (e.g. active/clear alarms and state changes occurred in the past), which allows the evaluation of events that may have been lost, e.g. after an Itf-N interface failure or a system recovery.
+
+As a consequence of the requirements described above, both the NM and the subordinate entity shall be able to initiate the communication.
+
+## 5.2 Management of alarm event reports
+
+### 5.2.1 Mapping of alarm and related state change event reports
+
+The alarm and state change reports received by the NM relate to functional objects in accordance with the information model of Itf-N. This information model tailored for a multi-vendor capability is different from the information model of the EM-NE interface (if an EM is available) or from the internal resource modelling within the NE (in case of direct NM-NE interface). Thus a mapping of alarm and related state change event reports is performed by a mediation function within the subordinate entity.
+
+The mediation function translates the original alarm/state change event reports (which may contain proprietary parameters or parameter values) taking into account the information model of the Itf-N.
+
+The following examples describe potential mediation function behaviour:
+
+- Alarm notifications generated by a functional object in a subordinate entity can be mapped to alarm reports of the corresponding ("equivalent") functional object at the Itf-N. If the functional object generating the original alarm notification has not a direct corresponding object at the Itf-N, the mediation functions maps the alarm to the next superior functional object in accordance with the containment tree of the Itf-N.
+- State change notifications generated by a functional object in a subordinate entity can be mapped to state change reports of the corresponding ("equivalent") functional object at the Itf-N. If the functional object generating the original state change notification has not a direct corresponding object at the Itf-N, the mediation functions maps the alarm to the next superior functional object in accordance with the containment tree of the Itf-N.
+
+Every alarm notification generated by a manufacturer-specific, equipment-related object in the subordinate entity is mapped to an alarm report of a generic logical object, which models the corresponding equipment-related resource.
+
+### 5.2.2 Real-time forwarding of event reports
+
+If the Itf-N is in normal operation (the NM connection to the subordinate entities is up), alarm reports are forwarded in real-time to the NM via appropriate filtering located in the subordinate entity. These filters may be controlled either locally or remotely by the managing NM (via Itf-N) and ensure that only the event reports which fulfil pre-defined criteria can reach the superior NM. In a multi-NM environment each NM shall have an own filter within every subordinate entity which may generate notifications.
+
+### 5.2.3 Alarm clearing
+
+On the Itf-N, alarm reports containing the value "cleared" of the parameter perceivedSeverity are used to clear the alarms. The correlation between the clear alarm and the related active alarms is performed by means of unambiguous identifiers.
+
+This clearing mechanism ensures the correct clearing of alarms, independently of the (manufacturer-specific) implementation of the mapping of alarms/state change events in accordance with the information model of the Itf-N.
+
+The IRP manager may also clear alarms manually.
+
+## 5.3 Retrieval of alarm information
+
+### 5.3.0 Introduction
+
+The retrieval of alarm information comprises two aspects:
+
+- Retrieval of current information:
+
+This mechanism shall ensure data consistency about the current alarm information between the NM and its subordinate entities and is achieved by means of a so-called synchronization ("alignment") procedure, triggered by the NM. The synchronization is required after every start-up of the Itf-N, nevertheless the NM may trigger it at any time.
+
+- Logging and retrieval of history information:
+
+This mechanism offers to the NM the capability to get the alarm information stored within the subordinate entities for later evaluation.
+
+### 5.3.1 Retrieval of current alarm information on NM request
+
+The present document defines a flexible, generic synchronization procedure, which fulfils the following requirements:
+
+- The alarm information provided by means of the synchronization procedure shall be the same (at least for the mandatory parameters) as the information already available in the alarm list. The procedure shall be able to assign the received synchronization-alarm information to the correspondent requests, if several synchronization procedures triggered by one NM run at the same time.
+- The procedure shall allow the NM to trigger the start at any time and to recognize unambiguously the end and the successful completion of the synchronization.
+- The procedure shall allow the NM to discern easily between an "on-line" (spontaneous) alarm report and an alarm report received as consequence of a previously triggered synchronization procedure.
+- The procedure shall allow the NM to specify filter criteria in the alignment request (e.g. for a full network or only a part of it).
+- The procedure shall support connections to several NM and route the alignment-related information only to the requesting NM.
+- During the synchronization procedure new ("real-time") alarms may be sent at any time to the managing NM.
+- If the EM loses confidence to its alarm list and rebuilds it, then the EM shall indicate to the NM that the alarm list have been rebuilt. If the rebuild of the alarm list only concerns alarms for e.g. one NE then the EM may indicate that it is only that part of the alarm list that has been rebuilt. In the latter case the NM may use the knowledge that only a specific subset of the alarm list have been rebuilt to perform a partial resynchronization using filters.
+
+If applicable, an alarm synchronization procedure may be aborted by the requesting NM.
+
+### 5.3.2 Logging and retrieval of alarm history information on NM request
+
+The alarm history information may be stored in the subordinate entities. The NM is able to create logs for alarm reports and to define the criteria for storage of alarm information according to ITU-T Recommendation X.735 [11].
+
+Nevertheless these particular requirements are not specific for alarm or state change information.
+
+The alarm history information should be returned by files when IRP agent finished collecting all the alarm history information that NM requested.
+
+## 5.4 Co-operative alarm acknowledgement on the Itf-N
+
+The acknowledgement of an alarm is a maintenance function that aids the operators in his day-to-day management activity of his network. An alarm is acknowledged by the operator to indicate he has started the activity to resolve this specific problem. In general a human operator performs the acknowledgement, however a management system (NM or EM) may automatically acknowledge an alarm as well.
+
+The alarm acknowledgement function requires that:
+
+- a) All involved OSs have the same information about the alarms to be managed (including the current responsibility for alarm handling).
+- b) All involved OSs have the capability to send and to receive acknowledgement messages associated to previous alarm reports.
+
+A co-operative alarm acknowledgement means that the acknowledgement performed at EM layer is notified at NM layer and vice versa, thus the acknowledgement-related status of this alarm is the same across the whole management hierarchy. The OSs often gives the operator(s) a possibility to add a comment to an alarm. An OS can have the capability to record more than one comment for each alarm. To make the same alarm look the same in all OSs subscribing to the alarm, it should be possible to distribute the recorded comments in the same way as for the acknowledgement information.
+
+The co-operative alarm acknowledgement on Itf-N shall fulfil the following requirements:
+
+- Acknowledgement messages may be sent in both directions between EMs and NM, containing the following information:
+  - Correlation information to the alarm just acknowledged.
+  - Acknowledgement history data, including the current alarm state (active | cleared), the time of alarm acknowledgement and, as configurable information, the management system (EM | NM) and the operator in charge of acknowledgement (the parameter operator name or, in case of auto-acknowledgement, a generic system name).
+  - Acknowledgement notifications sent to NM shall be filtered with the same criteria applied to the alarms.
+- Taking into account the acknowledgement functionality, the above described synchronization procedure for retrieval of current alarm information on NM request may be extended. Additionally to the requirements defined in clause 5.3.1, this extended synchronization procedure relates not only to the active, but also to the "cleared and not acknowledged" alarms, which have still to be managed by the EM.
+
+## 5.5 Overview of IRPs related to Fault Management (FM)
+
+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] and 3GPP TS 32.102 [3].
+
+For the purpose of FM, the following IRPs are needed:
+
+- Alarm IRP, see 3GPP TS 32.111-2 [13];
+- Notification IRP, see [1]; and
+- Log IRP.
+
+NOTE: The Log IRP is not part of Release 1999, therefore the requirements related to the log functionality are not valid for Release 1999).
+
+# Annex A (informative): Change history
+
+| Change history |       |           |     |     |                                                                                                                                           |        |        |
+|----------------|-------|-----------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                                                                                                           | Old    | New    |
+| Mar 2000       | SA 07 | SP-000013 | --  | --  | 32.111 Approved at TSG SA#7 and placed under Change Control                                                                               | 2.0.0  | 3.0.0  |
+| Mar 2000       | --    | --        | --  | --  | cosmetic                                                                                                                                  | 3.0.0  | 3.0.1  |
+| Jun 2000       | SA 08 | SP-000247 | 001 | --  | Split of TS 32.111 - Part 1: Main part of spec – Requirements                                                                             | 3.0.1  | 3.1.0  |
+| Jun 2000       | SA 08 | SP-000248 | 002 | --  | Split of TS 32.111- Part 1: Merged Clause X into Clause 4                                                                                 | 3.0.1  | 3.1.0  |
+| Jun 2000       | SA_08 | SP-000249 | 003 | --  | Split of TS 32.111 - Part 1: Alignment of FM requirements with IRP, etc                                                                   | 3.0.1  | 3.1.0  |
+| Sep 2000       | SA 09 | SP-000437 | 001 | --  | Clarification On Mediation Function Algorithms                                                                                            | 3.1.0  | 3.2.0  |
+| Sep 2000       | SA 09 | SP-000437 | 002 | --  | Clarification On Clear Alarm Suppression                                                                                                  | 3.1.0  | 3.2.0  |
+| Jun 2001       | SA_12 | SP-010282 | 003 | --  | Added two new features 'partial resynchronization' or 'ltf-N distribution of comments associated to faults'.                              | 3.2.0  | 4.0.0  |
+| Mar 2002       | SA 15 | --        | --  | --  | Automatic upgrade to Rel-5 (no Rel-5 CR)                                                                                                  | 4.0.0  | 5.0.0  |
+| Sep 2002       | SA 17 | SP-020477 | 004 | --  | Add requirements for new clearAlarms() operation in Alarm IRP                                                                             | 5.0.0  | 5.1.0  |
+| Dec 2002       | --    | --        | --  | --  | Updated references & cosmetics                                                                                                            | 5.1.0  | 5.1.1  |
+| Dec 2003       | SA 22 | SP-030631 | 005 | --  | Add retrieval of alarm history information requirement                                                                                    | 5.1.1  | 6.0.0  |
+| Jun 2005       | --    | --        | --  | --  | Foreword, Introduction update : added 32.111-5 new TS-family member                                                                       | 6.0.0  | 6.0.1  |
+| Jun 2007       | SA_36 | --        | --  | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. Cleaned-up references. | 6.0.1  | 7.0.0  |
+| Mar 2009       | SA 43 | SP-090207 | 006 | --  | Include reference to SOAP Solution Set specification                                                                                      | 7.0.0  | 8.0.0  |
+| Dec 2009       | SA 46 | --        | --  | --  | Upgrade to Rel-9                                                                                                                          | 8.0.0  | 9.0.0  |
+| Mar 2011       | -     | -         | -   | -   | Update to Rel-10 version (MCC)                                                                                                            | 9.0.0  | 10.0.0 |
+| Sep 2011       | SA 53 | SP-110534 | 007 | -   | Add concepts for Alarm Correlation and Root Cause Analysis                                                                                | 10.0.0 | 10.1.0 |
+| Mar 2015       | SA 67 | SP-150060 | 014 | 1   | Replacement of obsolete term "N interface"                                                                                                | 10.1.0 | 10.2.0 |

marked/Rel-10/32_series/32121/raw.md

@@ -0,0 +1,183 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 32.121 (V10.0.0 (2011-03)) ~~Telecommunication management; Advanced Alarm Management (AAM)~~ *Technical Specification* **Integration Reference Point (IRP): Requirements (Release 10)**** ---
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in bold lowercase letters with a red signal icon above the "l", and the word "ADVANCED" in smaller uppercase letters to the right. A trademark symbol (TM) is at the bottom right.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold font with a red signal icon below the "G", and a trademark symbol (TM) at the top right.
+
+3GPP logo
+
+Keywords  
+UMTS, GSM, management
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+- Foreword ..... 4
+- Introduction ..... 4
+- 1 Scope..... 5
+- 2 References..... 5
+- 3 Definitions and abbreviations ..... 5
+- 3.1 Definitions..... 5
+- 3.2 Abbreviations ..... 5
+- 4 Requirements for AAM on Itf-N ..... 6
+- 4.1 Concept..... 6
+- 4.2 General Requirements for AAM on Itf-N ..... 6
+- Annex A (informative): Change history..... 7
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.121: "Advanced Alarm Management Integration Reference Point (IRP): Requirements";**
+- 32.122: "Advanced Alarm Management Integration Reference Point (IRP): Information Service (IS)";
+- 32.126: "Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions".
+
+The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 [1].
+
+IRPManagers (typically Network Management Systems) and IRPAgents (typically EMs or NEs) synchronize their data concerning alarms or configuration data. In certain scenarios this synchronization is lost or not done.
+
+This IRP provides functionality to significantly reduce the amount of data which needs to be transferred in order to re-establish synchronization.
+
+# --- 1 Scope
+
+The purpose of this set of specifications is to provide a mechanism enabling the IRP Manager to improve the information content of alarms, thereby contributing to reduce the time-to-repair. For this configurable rules for advanced alarm filtering are defined to reduce the number of alarms by applying such advanced alarm filtering.
+
+The present document contains the Requirements of Advanced Alarm Management (AAM) on Itf-N IRP. It defines, for the purpose of AAM on Itf-N, the basic requirements to be fulfilled on Itf-N.
+
+# --- 2 References
+
+The following documents contain provisions that, 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.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**IRP:** See 3GPP TS 32.150 [1].
+
+**IRPAgent:** See 3GPP TS 32.150 [1].
+
+**IRPManager:** See 3GPP TS 32.150 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                             |
+|-------|-----------------------------|
+| IRP   | Integration Reference Point |
+| IS    | Information Service         |
+| Itf-N | Interface N                 |
+| NE    | Network Element             |
+
+# --- 4 Requirements for AAM on Itf-N
+
+## 4.1 Concept
+
+A single network fault may generate a large number of alarms over space and time. In a large and complex network, simultaneous network faults may occur, causing the network operator to be flooded with high volume of alarms. The high volume of alarms, typically the one received by an IRPManager via the getAlarmList or alarm notifications of Alarm IRP specification, greatly inhibits the operator ability to quickly identify and locate the responsible network faults.
+
+Therefore it is considered advantageous to have methods categorizing network alarms as insignificant or significant. The word 'insignificant' does not imply "low priority". In the context of this specification the words 'significant' and 'insignificant' have the following implications:
+
+- IRP Agent shall not report alarms categorized as insignificant.
+- IRP Agent shall report all significant alarms.
+
+Reporting only significant alarms and not reporting insignificant alarms would reduce network operator's time to locate network faults so that more time can be spent fixing them.
+
+When reading the alarmList it can be advantageous to partition alarms in the alarmList into sets of alarms which might be caused by the same network fault.
+
+By assigning network operators to locate network faults based on alarms in such alarm partitions, rather than based on alarm severity, alarm type or reporting location, duplication of network operator effort (e.g. two network operators work on two different alarms and their resolutions lead to the same network faults) can be reduced or avoided
+
+## 4.2 General Requirements for AAM on Itf-N
+
+4.2.1 The IRP Manager should be able to request the IRP Agent to
+
+- a) categorize alarms as insignificant or significant and
+  - b) to act based on these categories, e.g. to discard if insignificant.
+- The IRP Manager should be able to cancel such requests.
+
+4.2.2 The standard should define some alarm categorization rules. The standard should also allow vendor to define their own alarm categorization rules.
+
+4.2.3 Possible alarm categorization rule(s) may depend for example on the type of alarm, the environment, the time of day, the type of network element, the alarm severity, the location, position in the containment tree and many more. No restriction is imposed in this regard.
+
+4.2.4 The IRP Manager should be able to request the IRP Agent for the list of active categorization rules (i.e. standard defined and vendor defined).
+
+4.2.5 The IRP manager should be able to request the IRP Agent to apply the categorization rule(s) and to remove the insignificant alarms in the following situations:
+
+- + alarm notifications to be sent to any IRP Manager
+- + advanced alarm management requests by this IRP Manager to read the alarm list
+
+Certain types of categorization rules are only to be applied to read the alarm list. The term used for these rules is alarm partitioning rules.
+
+## --- Annex A (informative): Change history
+
+| Change history |       |           |    |    |                                    |     |       |        |
+|----------------|-------|-----------|----|----|------------------------------------|-----|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR | R  | Subject/Comment                    | Cat | Old   | New    |
+| May 2007       | SA 36 | SP-070294 | -- | -- | Submitted to SA#36 for Information | --  | --    | 1.0.0  |
+| Mar 2008       | SA 39 | SP-080071 | -- | -- | Submitted to SA#39 for Approval    | --  | 2.0.0 | 8.0.0  |
+| Dec 2009       | -     | -         | -  | -  | Update to Rel-9 version (MCC)      | --  | 8.0.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -  | -  | Update to Rel-10 version (MCC)     | --  | 9.0.0 | 10.0.0 |

marked/Rel-10/32_series/32122/raw.md

@@ -0,0 +1,983 @@
+
+
+# **3rd Generation Partnership Project;** Keywords **Technical Specification Group Services and System Aspects;** **3GPP TS 32.122 V10.0.0 (2011-03)** **Telecommunication management;** **Advanced Alarm Management (AAM)** Technical Specification **Integration Reference Point (IRP):** **Information Service (IS)** **(Release 10)** ---
+
+**3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+050 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+![LTE logo with '4ADVANCED' text above the 'e' and a red signal icon.](4f4b52340aaccb1bcf733468dca9ee03_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e' and a red signal icon.
+
+![3GPP logo with a red signal icon below the 'P'.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg)
+
+3GPP logo with a red signal icon below the 'P'.
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTETM is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                                                                      |    |
+|------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                       | 5  |
+| Introduction .....                                                                                   | 5  |
+| 1 Scope.....                                                                                         | 6  |
+| 2 References.....                                                                                    | 6  |
+| 3 Definitions and abbreviations .....                                                                | 7  |
+| 3.1 Definitions.....                                                                                 | 7  |
+| 3.2 Abbreviations .....                                                                              | 7  |
+| 4 System overview .....                                                                              | 8  |
+| 4.1 System context .....                                                                             | 8  |
+| 5 Information Object Classes.....                                                                    | 9  |
+| 5.1 Imported information entities and local labels.....                                              | 9  |
+| 5.2 Class diagram .....                                                                              | 9  |
+| 5.2.1 Attributes and relationships.....                                                              | 9  |
+| 5.2.2 Inheritance .....                                                                              | 10 |
+| 5.3 Information Object Class definitions .....                                                       | 11 |
+| 5.3.1 advancedAlarmManagementRule .....                                                              | 11 |
+| 5.3.1.1 Definition .....                                                                             | 11 |
+| 5.3.1.1.1 General Definition .....                                                                   | 11 |
+| 5.3.1.2 Attributes .....                                                                             | 11 |
+| 5.3.2 advancedAlarmManagementIRP.....                                                                | 11 |
+| 5.3.2.1 Definition .....                                                                             | 11 |
+| 5.4 Information relationships definition.....                                                        | 12 |
+| 5.4.1 relation- AdvancedAlarmManagementIRP-AdvancedAlarm ManagementRule (M) ..                       | 12 |
+| 5.4.1.1 Definition .....                                                                             | 12 |
+| 5.4.1.2 Roles .....                                                                                  | 12 |
+| 5.4.1.3 Constraints .....                                                                            | 12 |
+| 5.5 Information attributes definition .....                                                          | 12 |
+| 5.5.1 Definitions and legal values .....                                                             | 12 |
+| 6 Interface Definition .....                                                                         | 13 |
+| 6.1 Class diagram representing interfaces.....                                                       | 13 |
+| 6.2 AAMIRPOperation_1 Interface (M).....                                                             | 14 |
+| 6.2.1 Scope .....                                                                                    | 14 |
+| 6.2.2 Operation activateAAMRule (M).....                                                             | 14 |
+| 6.2.2.1 Definition .....                                                                             | 14 |
+| 6.2.2.2 Input parameters .....                                                                       | 14 |
+| 6.2.2.2.1 Generic Input parameters.....                                                              | 14 |
+| 6.2.2.2.2 Content of Input parameter aAMRuleParameterList depending on value of<br>aAMRuleType ..... | 14 |
+| 6.2.2.2.2.1 aAMRuleType = ThresholdRule.....                                                         | 14 |
+| 6.2.2.2.2.2 aAMRuleType = TransientRule.....                                                         | 15 |
+| 6.2.2.2.2.3 aAMRuleType = ToggleRule.....                                                            | 15 |
+| 6.2.2.2.2.4 aAMRuleType = vendorSpecificRule.....                                                    | 15 |
+| 6.2.2.3 Output parameters.....                                                                       | 15 |
+| 6.2.2.4 Pre-condition.....                                                                           | 15 |
+| 6.2.2.5 Post-condition .....                                                                         | 15 |
+| 6.2.2.6 Exceptions.....                                                                              | 15 |
+| 6.2.3 Operation getAAMRules (M).....                                                                 | 16 |
+| 6.2.3.1 Definition .....                                                                             | 16 |
+| 6.2.3.2 Input parameters .....                                                                       | 16 |
+| 6.2.3.3 Output parameters.....                                                                       | 16 |
+| 6.2.3.4 Pre-condition.....                                                                           | 16 |
+| 6.2.3.5 Post-condition .....                                                                         | 16 |
+
+|         |                                      |    |
+|---------|--------------------------------------|----|
+| 6.2.3.6 | Exceptions.....                      | 16 |
+| 6.2.4   | Operation deactivateAAMRule (M)..... | 17 |
+| 6.2.4.1 | Definition .....                     | 17 |
+| 6.2.4.2 | Input parameters .....               | 17 |
+| 6.2.4.3 | Output parameters.....               | 17 |
+| 6.2.4.4 | Pre-condition.....                   | 17 |
+| 6.2.4.5 | Post-condition .....                 | 17 |
+| 6.2.4.6 | Exceptions.....                      | 17 |
+
+# **Annex A (normative): Advanced Alarm Management Rules..... 18**
+
+|                        |                                                |    |
+|------------------------|------------------------------------------------|----|
+| A.1                    | General.....                                   | 18 |
+| A.2                    | AAM Rules .....                                | 20 |
+| A.2.1                  | Threshold Rule .....                           | 20 |
+| A.2.1.1                | Parameters .....                               | 20 |
+| A.2.1.2                | Criterion to determine alike alarm.....        | 20 |
+| A.2.1.3                | Treatment of alike alarm.....                  | 20 |
+| A.2.1.4                | Relation to Log and AlarmList.....             | 21 |
+| A.2.1.5                | Samples.....                                   | 21 |
+| A.2.1.6                | Example for Use cases.....                     | 21 |
+| A.2.2                  | Transient Rule .....                           | 22 |
+| A.2.2.1                | Parameters .....                               | 22 |
+| A.2.2.2                | Criterion to determine alike alarm.....        | 22 |
+| A.2.2.3                | Treatment of alike alarm.....                  | 22 |
+| A.2.2.4                | Relation to Log and AlarmList.....             | 22 |
+| A.2.2.5                | Samples.....                                   | 23 |
+| A.2.2.6                | Example for Use cases.....                     | 23 |
+| A.2.3                  | Toggle Rule .....                              | 24 |
+| A.2.3.1                | Parameters .....                               | 24 |
+| A.2.3.2                | Criterion to determine alike alarm.....        | 24 |
+| A.2.3.3                | Treatment of alike alarm.....                  | 24 |
+| A.2.3.4                | Relation to Log and AlarmList.....             | 25 |
+| A.2.3.5                | Samples.....                                   | 25 |
+| A.2.3.6                | Example for Use cases.....                     | 26 |
+| A.2.3.7                | Exception Handling .....                       | 27 |
+| A.2.4                  | Definition of vendor specific rule .....       | 27 |
+| A.3                    | Relation of Rule and Notification filter ..... | 28 |
+| Annex B (informative): | Change history.....                            | 29 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.121: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements;
+- 32.122: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS);**
+- 32.126: Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions.
+
+The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 [1].
+
+A single network fault may generate a large number of alarms over space and time. In a large and complex network, simultaneous network faults may occur, causing the network operator to be flooded with high volume of alarms. The high volume of alarms, typically the one received by an IRPManager via the getAlarmList or alarm notifications of Alarm IRP specification, greatly inhibits the operator ability to quickly identify and locate the responsible network faults. AAM IRP is intended to provide methods to improve this situation.
+
+# --- 1 Scope
+
+The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
+
+The present document is the Information Service of AAM. It defines, for the purpose of categorizing alarm notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+# --- 2 References
+
+The following documents contain provisions that, 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.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.121: "Telecommunication management; Advanced Alarm Management Reference Point (IRP): Requirements".
+- [5] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [6] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [7] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [8] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (SS)".
+- [9] 3GPP TS 32.662: "Telecommunication management; Configuration Management (CM); Kernel CM; Information service (IS)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**IRP:** See 3GPP TS 32.150 [1].
+
+**IRPAgent:** See 3GPP TS 32.150 [1].
+
+**IRPManager:** See 3GPP TS 32.150 [1].
+
+**Alike Alarm:** Two alarms are considered alike, if the corresponding alarm notifications are issued by the same object instance with the same `alarmType`, same `perceivedSeverity`, same `probableCause` and same `specificProblem` (if present).
+
+**Lower Edge of Time Window:** The point in time which determines the begin of a time span.
+
+**Upper Edge of Time Window:** The point in time which determines the end of a time span.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                |
+|---------|--------------------------------|
+| AAM     | Advanced Alarm Management      |
+| AAMRule | Advanced Alarm Management Rule |
+| CM      | Configuration Management       |
+| EM      | Element Manager                |
+| IOC     | Information Object Class       |
+| IRP     | Integration Reference Point    |
+| IS      | Information Service            |
+| Itf-N   | Interface N                    |
+| MIB     | Management Information Base    |
+| NE      | Network Element                |
+
+# 4 System overview
+
+## 4.1 System context
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [5], clause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in figures 4.1-1 and 4.1-2.
+
+![Figure 4.1-1: System Context A. A diagram showing an IRPManager (NM) connected to an IRPAgent (EM), which is connected to multiple NEs. A notification path is shown from the IRPAgent to the Advanced Alarm Management IRP via the Itf-N interface.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg)
+
+The diagram illustrates System Context A. On the left, a box labeled 'NM' contains 'IRPManager'. A solid line connects it to a box labeled 'EM' containing 'IRPAgent'. A dotted line connects the 'IRPAgent' to a box labeled 'NEs'. A vertical dashed line, labeled 'Itf-N' at its base, separates the 'IRPManager' from the 'IRPAgent'. A curved arrow points from the 'IRPAgent' to the 'Itf-N' interface. From the 'Itf-N' interface, a vertical line leads to a horizontal line labeled 'Notification'. To the right of this line is the text 'Advanced Alarm Management IRP'.
+
+Figure 4.1-1: System Context A. A diagram showing an IRPManager (NM) connected to an IRPAgent (EM), which is connected to multiple NEs. A notification path is shown from the IRPAgent to the Advanced Alarm Management IRP via the Itf-N interface.
+
+Figure 4.1-1: System Context A
+
+![Figure 4.1-2: System Context B. A diagram showing an IRPManager (NM) connected to an IRPAgent (NE), which is connected to the Advanced Alarm Management IRP via the Itf-N interface.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg)
+
+The diagram illustrates System Context B. On the left, a box labeled 'NM' contains 'IRPManager'. A solid line connects it to a box labeled 'NE' containing 'IRPAgent'. A vertical dashed line, labeled 'Itf-N' at its base, separates the 'IRPManager' from the 'IRPAgent'. A curved arrow points from the 'IRPAgent' to the 'Itf-N' interface. From the 'Itf-N' interface, a vertical line leads to a horizontal line labeled 'Notification IRP'. To the right of this line is the text 'Advanced Alarm Management IRP'.
+
+Figure 4.1-2: System Context B. A diagram showing an IRPManager (NM) connected to an IRPAgent (NE), which is connected to the Advanced Alarm Management IRP via the Itf-N interface.
+
+Figure 4.1-2: System Context B
+
+# 5 Information Object Classes
+
+## 5.1 Imported information entities and local labels
+
+| Label reference                                                 | Local label       |
+|-----------------------------------------------------------------|-------------------|
+| 3GPP TS 32.622 [6], information object class, Top               | Top               |
+| 3GPP TS 32.312 [7], information object class, managedGenericIRP | managedGenericIRP |
+| 3GPP TS 32.622 [6], information object class, IRPAgent          | IRPAgent          |
+
+## 5.2 Class diagram
+
+### 5.2.1 Attributes and relationships
+
+This clause depicts the set of IOC that encapsulate information within the AAM IRP. The intent is to identify the information required for the AAM IRP implementation of its operations and notification emission.
+
+This clause provides the overview of all Information Object Classes in UML.
+
+Subsequent clauses provide more detailed specification of various aspects of these Information Object Classes.
+
+![UML Class Diagram showing AdvancedAlarmManagementIRP and AdvancedAlarmManagementRule classes.](e1a0d046fbe7f28f5e93a47091851747_img.jpg)
+
+```
+classDiagram
+    class AdvancedAlarmManagementIRP {
+        <<InformationObjectClass>>
+    }
+    class AdvancedAlarmManagementRule {
+        <<InformationObjectClass>>
+        aAMRuleIdentifier
+        aAMRuleType
+        aAMRuleParameterList
+        filter
+    }
+    AdvancedAlarmManagementIRP "1" *-- "0..*" AdvancedAlarmManagementRule
+```
+
+The diagram shows two classes: **AdvancedAlarmManagementIRP** and **AdvancedAlarmManagementRule**. **AdvancedAlarmManagementIRP** is at the top and has a stereotype `<<InformationObjectClass>>`. **AdvancedAlarmManagementRule** is at the bottom and also has a stereotype `<<InformationObjectClass>>`. It lists four attributes: `aAMRuleIdentifier`, `aAMRuleType`, `aAMRuleParameterList`, and `filter`. A red line with a solid diamond at the top connects **AdvancedAlarmManagementIRP** to **AdvancedAlarmManagementRule**. The multiplicity `0..*` is shown near the bottom class.
+
+UML Class Diagram showing AdvancedAlarmManagementIRP and AdvancedAlarmManagementRule classes.
+
+Figure 5.2.1-1: Class Diagram
+
+### 5.2.2 Inheritance
+
+This clause depicts the inheritance relationships that exist between Information Object Classes.
+
+![UML inheritance diagram showing AdvancedAlarmManagementRP inheriting from ManagedGenericRP.](562f471e8153729557e6a4ee6343c32c_img.jpg)
+
+```
+classDiagram
+    class ManagedGenericRP {
+        <<InformationObjectClass>>
+        (from 32.622)
+    }
+    class AdvancedAlarmManagementRP {
+        <<InformationObjectClass>>
+    }
+    ManagedGenericRP <|-- AdvancedAlarmManagementRP
+```
+
+The diagram illustrates an inheritance relationship between two Information Object Classes. The base class, **ManagedGenericRP** (from 32.622), is shown in a yellow box at the top. The derived class, **AdvancedAlarmManagementRP**, is shown in a yellow box at the bottom. A vertical line with an open triangle arrowhead points from the derived class to the base class, indicating that **AdvancedAlarmManagementRP** inherits from **ManagedGenericRP**.
+
+UML inheritance diagram showing AdvancedAlarmManagementRP inheriting from ManagedGenericRP.
+
+**Figure 5.2.2-1: Inheritance Diagram**
+
+## 5.3 Information Object Class definitions
+
+### 5.3.1 advancedAlarmManagementRule
+
+#### 5.3.1.1 Definition
+
+##### 5.3.1.1.1 General Definition
+
+This information object represents an AAM Rule object instance.
+
+An AdvancedAlarmManagementRule is fully identified by its distinguished name.
+
+It inherits from IOC top.
+
+An AAM Rule is a way for the IRPManager to define which alarms / alarm clearings deliver significant or insignificant information (significant seen with the eyes of the IRPManager) and to tell the IRPAgent not to send the insignificant alarms / alarm clearings.
+
+AAMRules will not screen out all insignificant alarms/alarm clearings, but contribute to enable the network operator to reduce the number of reported alarms to a reasonable and manageable level.
+
+The choice of rule/s may depend on the type of alarm, the environment, the time of day and many more.
+
+To avoid screening of alarms which might be important for the network operator, the user of AAM rules should apply AAMrules with careful consideration and appropriate setting of parameters.
+
+An AAM Rule instance is fully identified by its DN distinguished name. A Rule instance carries, among other things, the identification of the Rule type called AdvancedAlarmManagementRuleType. Of these there exist the following:
+
+- ThresholdRule
+- TransientRule
+- ToggleRule
+- VendorSpecificRule
+
+See Annex A for the description of the above Rules.
+
+#### 5.3.1.2 Attributes
+
+| Attribute name                           | Support Qualifier | Read Qualifier | Write Qualifier |
+|------------------------------------------|-------------------|----------------|-----------------|
+| advancedAlarmManagementRuleIdentifier    | M                 | M              | -               |
+| advancedAlarmManagementRuleType          | M                 | M              | -               |
+| advancedAlarmManagementRuleParameterList | M                 | M              | -               |
+| filter                                   | M                 | M              | -               |
+
+### 5.3.2 advancedAlarmManagementIRP
+
+#### 5.3.2.1 Definition
+
+This information object represents an AAM IRP. It inherits from IOC managedGenericIRP.
+
+## 5.4 Information relationships definition
+
+### 5.4.1 relation- AdvancedAlarmManagementIRP-AdvancedAlarmManagementRule (M)
+
+#### 5.4.1.1 Definition
+
+This relationship defines the relationship between an AdvancedAlarmManagementIRP and an AdvancedAlarmManagementRule instance.
+
+#### 5.4.1.2 Roles
+
+| Name                           | Definition                                                                                                               |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| theAdvancedAlarmManagementRule | This role represents an AAM Rule. It can be played by instances of IOC advancedAlarmingRule                              |
+| theAdvancedAlarmManagementIRP  | This role represents the AAM IRP which an IRPManager uses. It is played by instances of IOC advancedAlarm Management IRP |
+
+#### 5.4.1.3 Constraints
+
+None
+
+## 5.5 Information attributes definition
+
+This clause defines the semantics of the Attributes used in Information Object Classes.
+
+### 5.5.1 Definitions and legal values
+
+| Attribute Name                           | Definition                                                              | Legal Values |
+|------------------------------------------|-------------------------------------------------------------------------|--------------|
+| advancedAlarmManagementRuleIdentifier    | This attribute identifies uniquely an AAM Rule base object instance     | String       |
+| advancedAlarmManagementRuleType          | This attribute indicates the type of AAM Rule this instance represents. | String       |
+| advancedAlarmManagementRuleParameterList | This attribute identifies parameters and values of this AAM Rule        | N/A          |
+
+# --- 6 Interface Definition
+
+## 6.1 Class diagram representing interfaces
+
+![UML Class Diagram showing AdvancedAlarmManagementRP as an InformationObjectClass and AdvancedAlarmManagementRPOperation_1 as an Interface with methods: activateAAMRule(), deactivateAAMRule(), and getAAMRules(). A dashed inheritance arrow points from the class to the interface.](042733dc5e8e7f5f30b60adba3266cde_img.jpg)
+
+```
+classDiagram
+    class AdvancedAlarmManagementRP {
+        <<InformationObjectClass>>
+    }
+    class AdvancedAlarmManagementRPOperation_1 {
+        <<Interface>>
+        activateAAMRule()
+        deactivateAAMRule()
+        getAAMRules()
+    }
+    AdvancedAlarmManagementRP ..|> AdvancedAlarmManagementRPOperation_1
+```
+
+UML Class Diagram showing AdvancedAlarmManagementRP as an InformationObjectClass and AdvancedAlarmManagementRPOperation\_1 as an Interface with methods: activateAAMRule(), deactivateAAMRule(), and getAAMRules(). A dashed inheritance arrow points from the class to the interface.
+
+Figure 6.1-1: Class Diagram for AdvancedAlarmManagementRPOperation\_1 Interface
+
+## 6.2 AAMIRPOperation\_1 Interface (M)
+
+### 6.2.1 Scope
+
+This interface defines methods for the IRPManager to request for alarm notifications of significant information (significant from the IRPManager's perspective).
+
+The definition of insignificance is determined by the IRPManager. The choice of AAM Rule/s may depend on the type of alarm, the environment, the time of day and many more.
+
+An implementation can claim compliance to this IRP if it supports at least one of the AAMRules, i.e. one of the operations defined in clause 6.2.2 up to and including clause 6.2.5, and the mandatory operations defined in this interface.
+
+### 6.2.2 Operation activateAAMRule (M)
+
+#### 6.2.2.1 Definition
+
+This operation allows an IRPManager to activate an AAM rule (see §A.3.1.1.2.1).
+
+#### 6.2.2.2 Input parameters
+
+##### 6.2.2.2.1 Generic Input parameters
+
+| Parameter Name       | Qualifier | Information type | Comment                                                                                                                                                                                                                           |
+|----------------------|-----------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| aAMRuleType          | M         | N/A              | This corresponds to attribute advancedAlarmManagementRuleType of advancedAlarmManagementRule (see 5.3.1.2)<br>Values: ThresholdRule, TransientRule, ToggleRule, VendorSpecificRule                                                |
+| aAMRuleParameterList | M         | N/A              | This corresponds to attribute advancedAlarmManagementRuleParameterList of advancedAlarmManagementRule (see 5.3.1.2)<br>Content depends on value of advancedAlarmManagementRuleType                                                |
+| filter               | M         | N/A              | This corresponds to attribute filter of advancedAlarmManagementRule (see 5.3.1.2)<br>Carries a filter constraint. It can e.g. comprise objectClass, objectInstance, alarmType, probableCause, perceivedSeverity, specificProblem. |
+
+##### 6.2.2.2.2 Content of Input parameter aAMRuleParameterList depending on value of aAMRuleType
+
+###### 6.2.2.2.2.1 aAMRuleType = ThresholdRule
+
+| Parameter Name          | Qualifier | Information type | Comment       |
+|-------------------------|-----------|------------------|---------------|
+| alarmOccurenceThreshold | M         | N/A              | value >0      |
+| slidingTimeWindow       | M         | N/A              | Unit: minutes |
+
+###### 6.2.2.2.1.2 aAMRuleType = TransientRule
+
+| Parameter Name | Qualifier | Information type | Comment       |
+|----------------|-----------|------------------|---------------|
+| timeSpan       | M         | N/A              | Unit: minutes |
+
+###### 6.2.2.2.2.3 aAMRuleType = ToggleRule
+
+| Parameter Name                   | Qualifier | Information type | Comment       |
+|----------------------------------|-----------|------------------|---------------|
+| alarmOccurenceThreshold          | M         | N/A              | value>0       |
+| slidingTimeWindowTogglingStarted | M         | N/A              | Unit: minutes |
+| slidingTimeWindowTogglingSettled | M         | N/A              | Unit: minutes |
+
+###### 6.2.2.2.2.4 aAMRuleType = vendorSpecificRule
+
+| Parameter Name             | Qualifier | Information type | Comment |
+|----------------------------|-----------|------------------|---------|
+| vendor specific parameters | N/A       | N/A              | N/A     |
+
+#### 6.2.2.3 Output parameters
+
+| Parameter Name    | Qualifier | Matching Information                          | Comment    |
+|-------------------|-----------|-----------------------------------------------|------------|
+| aAMRuleIdentifier | M         | N/A                                           | See §5.5.1 |
+| status            | M         | ENUM (Success, Failure, aAMRuleAlreadyActive) |            |
+
+#### 6.2.2.4 Pre-condition
+
+AAMIsSupported
+
+| Assertion Name | Definition                                           |
+|----------------|------------------------------------------------------|
+| aAMIsSupported | The AAM functionality is supported by the IRP Agent. |
+
+#### 6.2.2.5 Post-condition
+
+AAMRuleIsApplied
+
+| Assertion Name   | Definition                                                                    |
+|------------------|-------------------------------------------------------------------------------|
+| aAMRuleIsApplied | The AAM rule is applied. For the consequences see the definitions in Annex A. |
+
+#### 6.2.2.6 Exceptions
+
+| Name             | Properties                                                                                                                                                                   |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.2.3 Operation getAAMRules (M)
+
+#### 6.2.3.1 Definition
+
+This operation allows an IRPManager to request from the IRPAgent a list of activated AAMRules.
+
+#### 6.2.3.2 Input parameters
+
+None
+
+#### 6.2.3.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                                                                                                                                                                                                                                                                                                                                    | Comment                                                                                                   |
+|----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
+| aAMRuleList    | M         | LIST of aAMRuleInstance {<br><br>aAMRuleInstance<br>LIST OF {<br>aAMRuleIdentifier,<br>aAMRuleType,<br>aAMRuleParameterList,<br>filter<br>}<br><br>aAMRuleType<br>ENUM (<br>thresholdRule,<br>toggleRule,<br>transientRule,<br>vendorSpecificRule<br>)<br><br>aAMRuleParameterList:<br>Content type depends on the value of<br>aAMRuleType (see §6.2.2) |                                                                                                           |
+| Status         | M         | ENUM (Success, Failure)                                                                                                                                                                                                                                                                                                                                 | If no rule is defined, an empty advancedAlarmManagementRuleList a shall be delivered and status==Success. |
+
+#### 6.2.3.4 Pre-condition
+
+None
+
+#### 6.2.3.5 Post-condition
+
+allActiveAdvanceAlarmManagementRulesAreDelivered
+
+| Assertion Name                            | Definition                                     |
+|-------------------------------------------|------------------------------------------------|
+| allActiveAlarmManagementRulesAreDelivered | All active AAM rules are listed in the output. |
+
+#### 6.2.3.6 Exceptions
+
+| Name             | Properties                                                                                                                                                                   |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.2.4 Operation deactivateAAMRule (M)
+
+#### 6.2.4.1 Definition
+
+This operation allows an IRPManager to request from the IRPAgent to deactivate one or all activated AAMRules.
+
+Deactivated rules are not visible for the IRPManager.
+
+#### 6.2.4.2 Input parameters
+
+| Parameter Name                        | Qualifier | Information type | Comment                                                                                    |
+|---------------------------------------|-----------|------------------|--------------------------------------------------------------------------------------------|
+| advancedAlarmManagementRuleIdentifier | M         | See 32.302 [3]   | If this parameter contains no information, then all active AAM Rules shall be deactivated. |
+
+#### 6.2.4.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                              | Comment                                                                                                                                                                                                                                                      |
+|----------------|-----------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| status         | M         | ENUM (Success, SpecifiedRuleNotExisting, Failure) | If input parameter advancedAlarmManagementRuleIdentifier is present and no such rule exists, then status==SpecifiedRuleNotExisting.<br>If input parameter advancedAlarmManagementRuleIdentifier is not present and no rule is defined, then status==Success. |
+
+#### 6.2.4.4 Pre-condition
+
+None
+
+#### 6.2.4.5 Post-condition
+
+allOrSpecifiedActiveAdvanceAlarmManagementRulesAreDeactivated
+
+| Assertion Name                                                | Definition                                                                          |
+|---------------------------------------------------------------|-------------------------------------------------------------------------------------|
+| allOrSpecifiedActiveAdvanceAlarmManagementRulesAreDeactivated | Depending on the input all or only the specified active AAM Rule are/is deactivated |
+
+#### 6.2.4.6 Exceptions
+
+| Name             | Properties                                                                                                                                                                   |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+# --- Annex A (normative): Advanced Alarm Management Rules
+
+## A.1 General
+
+It is not recommended to have several AAMRules applicable at one time for one event. However, if YyyFunction supports and allows it, then it is vendor specific which AAMRule is applied or not.
+
+An AAMRule (called Rule hereafter) contains multiple elements.
+
+The first element (subSection titled: Criterion to determine alike alarm) is a criterion used to determine if an alarm is classified as ‘alike’ or “not alike”. If the alarm is not-alike, then the alarm is not subject to further scrutiny (processing) by the Rule, i.e. it would be processed as if there is no Rule in effect. The IRPManager specifies such criterion in an input parameter named filter in various relevant AAM operations.
+
+The second element (subSection titled: Treatment of alike alarm) is the algorithm to determine if
+
+- a) An alike alarm should be reported as one alarm (i.e. it is a significant alarm) or
+- b) The alike alarm should be suppressed (i.e. it is an insignificant alarm).
+
+When a significant alarm is identified, the algorithm also determines:
+
+- a) The time when the notifyNew/Changed/ClearedAlarm of this significant alarm should be sent to IRPManager and
+- b) The value of alarmRaisedTime, alarmChangedTime and alarmClearedTime parameters in the relevant notifyNew/Changed/ClearedAlarm of this significant alarm.
+
+The third element (subSection titled: Relation to Log and AlarmList) specifies which alarms shall enter into Log of LogIRP and AlarmList of AlarmIRP.
+
+Each of the following subsections defines a Rule using the three-element description outlined above.
+
+For each Rule, illustration samples, using symbols shown below, are given (titled: Samples). The thick horizontal line indicates a time-line. The dotted double-arrow line indicates a time parameter, if applicable. The “?” box indicates the alarm under investigation. The left-edge of a box corresponds to the alarmRaisedTime while the right-edge corresponds to the alarmClearedTime. So, the horizontal span of a box indicates the alarm active time span.
+
+![Figure A.1-1: Sample diagram notations. A horizontal timeline with an arrow pointing right, labeled 't' at the end. A shaded rectangular box with a question mark '?' inside is positioned above the timeline. The left edge of the box is aligned with a vertical dotted line, and the right edge is aligned with another vertical dotted line. These dotted lines extend downwards to the timeline.](aa9441a5971655a79987d70fc551b26a_img.jpg)
+
+Figure A.1-1: Sample diagram notations. A horizontal timeline with an arrow pointing right, labeled 't' at the end. A shaded rectangular box with a question mark '?' inside is positioned above the timeline. The left edge of the box is aligned with a vertical dotted line, and the right edge is aligned with another vertical dotted line. These dotted lines extend downwards to the timeline.
+
+**Figure A.1-1: Sample diagram notations**
+
+Sometimes, a shaded box is drawn below the time line as below. Such shaded box indicates the identification of a significant alarm (to be reported alarm).
+
+The left-edge of the box indicates the time when the corresponding alarm notification is sent out. This emission time is not necessarily identical to the alarmRaised/ChangedTime within the alarm notification.
+
+The right-edge of a box indicates the time when the corresponding alarm clearing notification is sent out. This emission time is not necessarily identical to the alarmClearedTime within the alarm notification.
+
+![A diagram showing a horizontal timeline labeled 't' at the right end. A rectangular box is centered on the timeline, with its top half being light gray and containing a question mark '?', and its bottom half being dark gray.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+A horizontal timeline with an arrow pointing to the right, labeled with the letter 't' at the far right. Centered on this timeline is a rectangular box. The box is divided into two horizontal sections: the top section is light gray and contains a black question mark '?', and the bottom section is dark gray.
+
+A diagram showing a horizontal timeline labeled 't' at the right end. A rectangular box is centered on the timeline, with its top half being light gray and containing a question mark '?', and its bottom half being dark gray.
+
+**Figure A.1-2: Sample diagram notations**
+
+For each Rule, use cases are given (subSection titled: Example for Use cases).
+
+For some Rules exception handling is defined (subSection titled: Exception Handling).
+
+## --- A.2 AAM Rules
+
+### A.2.1 Threshold Rule
+
+#### A.2.1.1 Parameters
+
+This Rule has three parameters, namely, the `alarmOccurenceThreshold` (called N here), the `slidingTimeWindow` (called T here) and `filter`.
+
+#### A.2.1.2 Criterion to determine alike alarm
+
+The `filter` parameter carries values for `objectInstance`, `alarmType`, `perceivedSeverity`, `probableCause` and `specificProblem`. If the alarm under investigation (e.g. the box with a “?” in the sample below) carries the same values, then it is considered ‘alike’ otherwise, “not-alike”.
+
+#### A.2.1.3 Treatment of alike alarm
+
+Starting value for Lower Edge of Time Window is the activation time of the threshold rule.
+
+Test an alike alarm.
+
+When a new alarm matches the filter, then Lower and Upper Edge of Time Window and count are newly determined: Upper Edge of Time Window becomes the time of the new alarm.
+
+Lower Edge of Time Window becomes either the time of the current Lower Edge of Time Window or the time of the new alarm minus the default size T of the time window, whichever of these two times is later.
+
+The count is the number of alarms between Lower and Upper Edge of Time Window (including the new alarm). If the count reaches the threshold N, then the alarm is considered as significant and the Lower Edge of Time Window becomes the time of the alarm.
+
+For a not reported alarm no `notifyClearedAlarm` shall be sent.
+
+`NotifyClearedAlarms` for alarms which were reported to the `IRPManager` before the activation of the threshold rule shall not be suppressed.
+
+Table A.2.1.3-1 shows the emission times of the various related to a significant alarm.
+
+**Table A.2.1.3-1: Significant alarm emission time for Threshold Rule**
+
+| Reported alarm types            | Emission (to IRPManager) times of a reported alarm    |
+|---------------------------------|-------------------------------------------------------|
+| <code>notifyNewAlarm</code>     | Immediately after the <code>alarmRaisedTime</code> .  |
+| <code>notifyChangedAlarm</code> | Immediately after the <code>alarmChangedTime</code> . |
+| <code>notifyClearedAlarm</code> | Immediately after the <code>alarmClearedTime</code>   |
+
+Table A.2.1.3-2 shows the time related parameters in significant alarm.
+
+**Table A.2.1.3-2: Significant alarm time parameters for Threshold Rule**
+
+| Parameters of the Reported alarm | Parameter values                               |
+|----------------------------------|------------------------------------------------|
+| <code>alarmRaisedTime</code>     | Same value as that carried in the alike alarm. |
+| <code>alarmChangedTime</code>    | Same value as that carried in the alike alarm. |
+| <code>notifyClearedTime</code>   | Same value as that carried in the alike alarm. |
+| <code>alarmId</code>             | Same value as that carried in the alike alarm. |
+
+#### A.2.1.4 Relation to Log and AlarmList
+
+The alike alarms enter the Log. The significant alarms enter the AlarmList.
+
+#### A.2.1.5 Samples
+
+![Timeline diagram showing two alarms within a threshold T. The first alarm is a small gray rectangle. The second alarm is a small gray rectangle with a question mark '?' inside. A dotted double-headed arrow labeled 'T' spans the time between the start of the first alarm and the start of the second alarm. The horizontal axis is labeled 't' at the right end.](ebce355620876e10f907f8b71926c112_img.jpg)
+
+N=3
+
+A horizontal timeline labeled 't' at the right end. Above the timeline, a dotted double-headed arrow labeled 'T' spans from the start of a small gray rectangle to the start of another small gray rectangle containing a question mark '?'. The label 'N=3' is positioned to the left of the timeline.
+
+Timeline diagram showing two alarms within a threshold T. The first alarm is a small gray rectangle. The second alarm is a small gray rectangle with a question mark '?' inside. A dotted double-headed arrow labeled 'T' spans the time between the start of the first alarm and the start of the second alarm. The horizontal axis is labeled 't' at the right end.
+
+FigureA.2.1.5-1: Threshold Rule illustrations – insignificant alarm
+
+![Timeline diagram showing three alarms within a threshold T. The first alarm is a wide gray rectangle. The second alarm is a small gray rectangle. The third alarm is a small gray rectangle with a question mark '?' inside. A dotted double-headed arrow labeled 'T' spans the time between the start of the first alarm and the start of the third alarm. The horizontal axis is labeled 't' at the right end.](723827e0738d2743c3b3423760a5c48e_img.jpg)
+
+N=3
+
+A horizontal timeline labeled 't' at the right end. Above the timeline, a dotted double-headed arrow labeled 'T' spans from the start of a wide gray rectangle to the start of a small gray rectangle containing a question mark '?'. A second small gray rectangle is positioned between them. The label 'N=3' is positioned to the left of the timeline.
+
+Timeline diagram showing three alarms within a threshold T. The first alarm is a wide gray rectangle. The second alarm is a small gray rectangle. The third alarm is a small gray rectangle with a question mark '?' inside. A dotted double-headed arrow labeled 'T' spans the time between the start of the first alarm and the start of the third alarm. The horizontal axis is labeled 't' at the right end.
+
+FigureA.2.1.5-2: Threshold Rule illustrations – insignificant alarm
+
+![Timeline diagram showing three alarms within a threshold T. The first two alarms are small gray rectangles. The third alarm is a large gray rectangle with a question mark '?' inside, which extends below the timeline. A dotted double-headed arrow labeled 'T' spans the time between the start of the first alarm and the start of the third alarm. The horizontal axis is labeled 't' at the right end.](812b773680b611c18d49243e102b895a_img.jpg)
+
+N=3
+
+A horizontal timeline labeled 't' at the right end. Above the timeline, a dotted double-headed arrow labeled 'T' spans from the start of a small gray rectangle to the start of a large gray rectangle containing a question mark '?'. A second small gray rectangle is positioned between them. The large gray rectangle extends both above and below the timeline. The label 'N=3' is positioned to the left of the timeline.
+
+Timeline diagram showing three alarms within a threshold T. The first two alarms are small gray rectangles. The third alarm is a large gray rectangle with a question mark '?' inside, which extends below the timeline. A dotted double-headed arrow labeled 'T' spans the time between the start of the first alarm and the start of the third alarm. The horizontal axis is labeled 't' at the right end.
+
+FigureA.2.1.5-3: Threshold Rule illustrations – significant alarm
+
+#### A.2.1.6 Example for Use cases
+
+The thresholdRule can be used to screen out alarms which are only important if they appear repeatedly, e.g. if an alarm which is self-healing comes back again and again,
+
+### A.2.2 Transient Rule
+
+#### A.2.2.1 Parameters
+
+This Rule has two parameters, namely, the minutesAtLeastActive (called T here) and filter.
+
+#### A.2.2.2 Criterion to determine alike alarm
+
+The filter parameter carries values for objectInstance, alarmType, perceivedSeverity, probableCause and specificProblem. If the alarm under investigation (e.g. the box with a ‘?’ in the sample below) carries the identified parameters and having the same values, then it is considered ‘alike’ otherwise, "not-alike".
+
+#### A.2.2.3 Treatment of alike alarm
+
+Take an alike alarm. If it's period is smaller than T, then it is an insignificant alarm; otherwise, it is a significant alarm. For a not reported alarm no notifyClearedAlarm shall be sent.
+
+NotifyClearedAlarms for alarms which were reported to the IRPManager before the activation of the transientRule shall not be suppressed.
+
+Table A.2.2.3-1 shows the emission times of the various related to significant alarm.
+
+**Table A.2.2.3-1: Significant alarm emission time re: Transient Rule**
+
+| Reported alarm type | Emission (to IRPManager) times of an Reported alarm |
+|---------------------|-----------------------------------------------------|
+| notifyNewAlarm      | Immediately after the alarmRaisedTime plus T.       |
+| notifyChangedAlarm  | Immediately after the alarmChangedTime plus T.      |
+| notifyClearedAlarm  | Immediately after the alarmClearedTime              |
+
+Table A.2.2.3-2 shows the time related parameters in significant alarm.
+
+**Table A.2.2.3-2: Significant alarm time parameters re: Transient Rule**
+
+| Parameters of the Reported alarm | Parameter values                               |
+|----------------------------------|------------------------------------------------|
+| alarmRaisedTime                  | Same value as that carried in the alike alarm. |
+| alarmChangedTime                 | Same value as that carried in the alike alarm. |
+| notifyClearedTime                | Same value as that carried in the alike alarm  |
+| alarmId                          | Same value as that carried in the alike alarm. |
+
+#### A.2.2.4 Relation to Log and AlarmList
+
+The alike alarms enter the Log. The significant alarms enter the AlarmList.
+
+#### A.2.2.5 Samples
+
+Here are two samples. One is a not-to-be reported alarm while the other is a significant alarm.
+
+![Diagram of an insignificant alarm](9b5411fa2d169b66f6185fbf67b49766_img.jpg)
+
+N=3
+
+A horizontal timeline labeled 't' at the right end. A light gray rectangular box with a question mark '?' is positioned on the timeline. Above the box, a horizontal dotted line with arrows at both ends spans its width and is labeled 'T' above its center.
+
+Diagram of an insignificant alarm
+
+Figure A.2.2.5-1: TransientRule Illustrations – insignificant alarm
+
+![Diagram of a significant alarm](50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg)
+
+N=3
+
+A horizontal timeline labeled 't' at the right end. A light gray rectangular box with a question mark '?' is positioned on the timeline. Above the box, a horizontal dotted line with arrows at both ends spans its width and is labeled 'T' above its center. A second, darker gray rectangular box is positioned below the timeline, partially overlapping the right side of the first box.
+
+Diagram of a significant alarm
+
+Figure A.2.2.5-2: TransientRule Illustrations – significant alarm
+
+#### A.2.2.6 Example for Use cases
+
+The transientRule can be used to screen out alarms which usually are of temporarily nature.
+
+### A.2.3 Toggle Rule
+
+#### A.2.3.1 Parameters
+
+This Rule has 4 parameters, namely, the filter, the alarmOccurenceThreshold (called N here), the slidingTimeWindowTogglingStarted (called T1 here) and slidingTimeWIndowTogglingSettled (called T2 here).
+
+#### A.2.3.2 Criterion to determine alike alarm
+
+The filter parameter carries values for objectInstance, alarmType, perceivedSeverity, probableCause and specificProblem. If the alarm under investigation (e.g. the box with a '?' in the sample below) carries the identified parameters and having the same values, then it is considered 'alike' otherwise, "not-alike".
+
+#### A.2.3.3 Treatment of alike alarm
+
+##### 1. Starting values:
+
+Starting value for Lower Edges of Time Windows for Toggling Started/Settled is the activation time of the toggle rule. Starting value for the count is zero.
+
+At the beginning all alarms are "non-toggling"
+
+##### 2. To do when alike alarm was identified
+
+When a notifyNew/Changed/ClearedAlarm event matches the filter, then Lower and Upper Edge of the Time Window TogglingStarted/Settled and count are newly determined:
+
+###### 2.1. Determine Time Window TogglingStarted
+
+Upper Edge of Time Window TogglingStarted becomes the time of the event.
+
+Lower Edge of Time Window TogglingStarted becomes the time of the event minus the size T1 of the time window.
+
+##### 2.2. Determination of "toggling" (via count)
+
+The count is the number of alike alarms between Lower and Upper Edge of Time Window TogglingStarted (including the new alarm).
+
+If the count is above or equal to the threshold N and the event was a notifyNewAlarm and the alarm was "non-toggling", then the notifyNewAlarm is sent and the alarm is considered as "toggling", with the consequence that further alike notifyNew/Changed/Alarm events are regarded as not significant, until the alarm is considered as "non-toggling" again.
+
+###### 2.3.Determine Time Window TogglingSettled
+
+If the alarm is "non-toggling", then there is no need to determine Upper and Lower Edge of Time Window TogglingSettled.
+
+If the alarm is "toggling", then:
+
+Upper Edge of Time Window TogglingSettled becomes the time of the new event plus the size T2 of the Time Window TogglingSettled .
+
+Lower Edge of Time Window TogglingSettled becomes the time of the new alarm .
+
+##### 3. Return to non-toggling
+
+If the time reaches the Upper Edge of Time Window TogglingSettled, then the alarm is considered as "non-toggling", i.e. alike alarms are regarded as significant.
+
+If the last event was a notifyChanged/ClearedAlarm, then the change to "non-toggling" triggers the emission of the related notification.
+
+Table A.2.3.3-1 shows the emission times of the various related to significant alarm.
+
+**Table A.2.3.3-1: Significant alarm emission time re: Toggle Rule**
+
+| Reported alarm types | Emission (to IRPManager) times of an Reported alarm                                                                                                                                                                                                           |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| notifyNewAlarm       | Immediately after the alarmRaisedTime                                                                                                                                                                                                                         |
+| notifyChangedAlarm   | Immediately after the alarmChangedTime [Remark: If the alarm is toggling state, then the notifyChangeAlarm is dropped (not significant).]                                                                                                                     |
+| notifyClearedAlarm   | Immediately after the alarmClearedTime+T2 of the last alike alarm , if alarmClearedTime is earlier than alarmRaisedTime+T2<br>or<br>immediately after the alarmClearedTime of the last alike alarm, if this time is later than or equal to alarmRaisedTime+T2 |
+
+Table A.2.3.3-2 shows the time related parameters in significant alarm.
+
+**Table A.2.3.3-2: Significant alarm time parameters re: Toggle Rule**
+
+| Parameters of the Reported alarm | Parameter values                                              |
+|----------------------------------|---------------------------------------------------------------|
+| alarmRaisedTime                  | Same value as that carried in the alike alarm.                |
+| alarmChangedTime                 | Same value as that carried in the alike alarm.                |
+| notifyClearedTime                | Same value as that carried in the last alike alarm.           |
+| alarmId                          | Same value as that carried by the first member of a sequence. |
+
+#### A.2.3.4 Relation to Log and AlarmList
+
+The alike alarms enter the Log. The significant alarms enter the AlarmList.
+
+#### A.2.3.5 Samples
+
+The samples below use N=3.
+
+![Figure A.2.3.5-1: Toggle Rule illustration 1. A timeline diagram showing three alarm events on a horizontal axis labeled 't'. The first event is a rectangle with a light gray top half and a dark gray bottom half. The second event is a similar rectangle. The third event is a rectangle with a question mark '?' in the light gray top half and a dark gray bottom half. Above the first two events, a double-headed arrow labeled 'T 1' spans the gap between them. Above the third event, a double-headed arrow labeled 'T 2' spans from the start of the event to a point further right. To the left of the first event, a double-headed arrow labeled 'N=3' spans the gap between the start of the timeline and the first event.](dd380ccd5aca1151074fede04826f1a4_img.jpg)
+
+Figure A.2.3.5-1: Toggle Rule illustration 1. A timeline diagram showing three alarm events on a horizontal axis labeled 't'. The first event is a rectangle with a light gray top half and a dark gray bottom half. The second event is a similar rectangle. The third event is a rectangle with a question mark '?' in the light gray top half and a dark gray bottom half. Above the first two events, a double-headed arrow labeled 'T 1' spans the gap between them. Above the third event, a double-headed arrow labeled 'T 2' spans from the start of the event to a point further right. To the left of the first event, a double-headed arrow labeled 'N=3' spans the gap between the start of the timeline and the first event.
+
+**Figure A.2.3.5-1: Toggle Rule illustration 1**
+
+![Figure A.2.3.5-2: Toggle Rule illustration 2. A timeline 't' shows five boxes. The first two are light gray above and dark gray below. The third and fourth are light gray above and part of a long dark gray block below. The fifth is light gray above with a '?' and part of the long dark gray block below. A dotted double-headed arrow labeled 'T 1' spans the first two boxes. A dotted double-headed arrow labeled 'T 2' spans the last three boxes. The label 'N=3' is to the left of the 'T 1' arrow.](97f61e67792478fb6ce089868e503063_img.jpg)
+
+Figure A.2.3.5-2: Toggle Rule illustration 2. A timeline 't' shows five boxes. The first two are light gray above and dark gray below. The third and fourth are light gray above and part of a long dark gray block below. The fifth is light gray above with a '?' and part of the long dark gray block below. A dotted double-headed arrow labeled 'T 1' spans the first two boxes. A dotted double-headed arrow labeled 'T 2' spans the last three boxes. The label 'N=3' is to the left of the 'T 1' arrow.
+
+Figure A.2.3.5-2: Toggle Rule illustration 2
+
+![Figure A.2.3.5-3: Toggle Rule illustration 3. A timeline 't' shows five boxes. The first two are light gray above and dark gray below. The third and fourth are light gray above and part of a long dark gray block below. The fifth is a long light gray box above with a '?' and part of the long dark gray block below. A dotted double-headed arrow labeled 'T 1' spans the first two boxes. A dotted double-headed arrow labeled 'T 2' spans the last three boxes. The label 'N=3' is to the left of the 'T 1' arrow.](2a25e8bc21554c0efceda1a8ccf57db3_img.jpg)
+
+Figure A.2.3.5-3: Toggle Rule illustration 3. A timeline 't' shows five boxes. The first two are light gray above and dark gray below. The third and fourth are light gray above and part of a long dark gray block below. The fifth is a long light gray box above with a '?' and part of the long dark gray block below. A dotted double-headed arrow labeled 'T 1' spans the first two boxes. A dotted double-headed arrow labeled 'T 2' spans the last three boxes. The label 'N=3' is to the left of the 'T 1' arrow.
+
+Figure A.2.3.5-3: Toggle Rule illustration 3
+
+![Figure A.2.3.5-4: Toggle Rule illustration 4. A timeline 't' shows a single long box. The top half is light gray with a '?' and the bottom half is dark gray. A dotted double-headed arrow labeled 'T 1' spans the top half. The label 'N=3' is to the left of the 'T 1' arrow.](004a497465710d16d63f436bb330fb42_img.jpg)
+
+Figure A.2.3.5-4: Toggle Rule illustration 4. A timeline 't' shows a single long box. The top half is light gray with a '?' and the bottom half is dark gray. A dotted double-headed arrow labeled 'T 1' spans the top half. The label 'N=3' is to the left of the 'T 1' arrow.
+
+Figure A.2.3.5-4: Toggle Rule illustration 4
+
+#### A.2.3.6 Example for Use cases
+
+The toggleRule can be used to take some burden from alarm management for cases where an alarm comes and goes back and forth, e.g. because of some entity is in a swinging state.
+
+#### A.2.3.7 Exception Handling
+
+The Toggle Rule can potentially group multiple alike alarms together to form one significant alarm. If the process executing the Rule misses the alarm clearing time of one member of a group, then this can have the following consequences:
+
+If a clearing of one of the alike alarms during the toggling state is missed (green box in Figure A.2.3.7-1), then the significant alarm would also not be cleared (pink box continuing the dark grey in the same figure). This can be avoided if the filter is set in a way that only alarms of one instance will pass it and if always the latest `notifyClearedAlarms` triggers the start of T2.
+
+![Figure A.2.3.7-1: Exception handling example. A timeline diagram showing alarm states over time. A horizontal axis represents time (t). Above the axis, a green bar labeled 'alarmList' contains several boxes. From left to right: three grey boxes (two above, one below the axis), a green box (above), a green box with a question mark (above), and a large green box (above). A red arrow labeled 'Missed notifyClearedAlarm' points to the second green box. To the left of the first grey box is a double-headed arrow labeled 'N=3'. To the right of the first grey box is a double-headed arrow labeled 'T1'. To the right of the green box with the question mark is a double-headed arrow labeled 'T2'. Below the axis, a dark grey bar extends from the start of the third grey box to the start of a pink box. The pink box continues to the right, ending at a vertical line labeled 't'.](043e64d41a3368d138ace3816fd26469_img.jpg)
+
+Figure A.2.3.7-1: Exception handling example. A timeline diagram showing alarm states over time. A horizontal axis represents time (t). Above the axis, a green bar labeled 'alarmList' contains several boxes. From left to right: three grey boxes (two above, one below the axis), a green box (above), a green box with a question mark (above), and a large green box (above). A red arrow labeled 'Missed notifyClearedAlarm' points to the second green box. To the left of the first grey box is a double-headed arrow labeled 'N=3'. To the right of the first grey box is a double-headed arrow labeled 'T1'. To the right of the green box with the question mark is a double-headed arrow labeled 'T2'. Below the axis, a dark grey bar extends from the start of the third grey box to the start of a pink box. The pink box continues to the right, ending at a vertical line labeled 't'.
+
+Figure A.2.3.7-1: Exception handling example
+
+### A.2.4 Definition of vendor specific rule
+
+It is possible to implement vendor specific `AAMRules`. No specific definitions are supplied here.
+
+## A.3 Relation of Rule and Notification filter
+
+This clause illustrates the relation between the AAM capabilities and the NotificationIRP and AlarmIRP.
+
+The following diagram illustrates the case when AAM capabilities are not deployed. The "1, 2.. 6" indicates 6 alarms. They will be logged and they would appear in the `AlarmList`. The NotificationIRP supported a filter F1. The `IRPManager`, in this case, receives "1, 3" where '2, 4, 5, 6' were discarded because of Notification filter F1 is in effect.
+
+![Diagram showing alarm flow without AAM capabilities. Alarms 1-6 enter AlarmIRP. AlarmIRP sends 1-6 to NotificationIRP, Log, and AlarmList. NotificationIRP uses filter F1 to output only 1 and 3.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+```
+
+    graph LR
+        Input(( )) -- "1,2,3,4,5,6" ---> AlarmIRP[AlarmIRP]
+        AlarmIRP -- "1,2,3,4,5,6" ---> NotificationIRP[NotificationIRP]
+        NotificationIRP -- "F1" ---> Output["1,3"]
+        AlarmIRP -- "1,2,3,4,5,6" ---> Log[[Log]]
+        AlarmIRP -- "1,2,3,4,5,6" ---> AlarmList[[AlarmList]]
+    
+```
+
+Diagram showing alarm flow without AAM capabilities. Alarms 1-6 enter AlarmIRP. AlarmIRP sends 1-6 to NotificationIRP, Log, and AlarmList. NotificationIRP uses filter F1 to output only 1 and 3.
+
+**Figure A.3-1: Deployment without AAM capabilities**
+
+The following diagram illustrates the case when AAM capabilities are deployed. The "1, 2.. 6" indicates 6 alarms. They will be logged. Because of AAMRule R1 is in effect, the ""1,2...6" result in two significant alarms, A and B. The A and B will appear in `AlarmList`. They will also be broadcasted to `IRPManagers` subject to NotificationIRP filter in effect. In the case below, the `IRPManager` would receive only A because Notification IRP filter F2 is in effect.
+
+![Diagram showing alarm flow with AAM capabilities. Alarms 1-6 enter AAMIRP. AAMRule R1 processes them into A and B. A and B are sent to NotificationIRP and AlarmList. NotificationIRP uses filter F2 to output only A. Original alarms 1-6 are sent to Log.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg)
+
+```
+
+    graph LR
+        Input(( )) -- "1,2,3,4,5,6" ---> AAMIRP[AAMIRP]
+        AAMIRP -- "R1" ---> AAMIRP
+        AAMIRP -- "A,B" ---> NotificationIRP[NotificationIRP]
+        NotificationIRP -- "F2" ---> Output["A"]
+        AAMIRP -- "A,B" ---> AlarmList[[AlarmList]]
+        Input -- "1,2,3,4,5,6" ---> Log[[Log]]
+    
+```
+
+Diagram showing alarm flow with AAM capabilities. Alarms 1-6 enter AAMIRP. AAMRule R1 processes them into A and B. A and B are sent to NotificationIRP and AlarmList. NotificationIRP uses filter F2 to output only A. Original alarms 1-6 are sent to Log.
+
+**Figure A.3-2: Deployment with AAM capabilities**
+
+# Annex B (informative): Change history
+
+| Change history |       |           |          |     |                                             |     |       |        |
+|----------------|-------|-----------|----------|-----|---------------------------------------------|-----|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR       | Rev | Subject/Comment                             | Cat | Old   | New    |
+| Sep 2007       | SA_37 | SP-070616 | --       | --  | Submitted to SA#37 for Information          | --  | 1.0.0 |        |
+| Mar 2008       | SA_39 | SP-080072 | --       | --  | Submitted to SA#39 for Approval             | --  | 2.0.0 | 8.0.0  |
+| Jun 2008       | SA_40 | SP-080329 | 000<br>1 | --  | Clarify the assumed scenarios for AAM rules | F   | 8.0.0 | 8.1.0  |
+| Dec 2009       | -     | -         | -        | -   | Update to Rel-9 version (MCC)               | -   | 8.1.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -        | -   | Update to Rel-10 version (MCC)              | -   | 9.0.0 | 10.0.0 |
+
+document.
+
+**30**Error! No text of  
+specified style in
+
+Error! No text of specified style in

marked/Rel-10/32_series/32126/raw.md

@@ -0,0 +1,1109 @@
+
+
+# Keywords Alarm management, CORBA, XML, SOAP 3GPP TS 32.126 V10.1.0 (2011-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **Telecommunication management;** **Advanced Alarm Management (AAM)** **Integration Reference Point (IRP):** **Solution Set**
+
+![LTE logo with '4ADVANCED' text above the 'e' and a red signal icon.](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e' and a red signal icon.
+
+Postal address  
+3GPP SA-NGSI WG1 Coord  
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a red signal icon below the 'P'.](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo with a red signal icon below the 'P'.
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP..
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                              |           |
+|--------------------------------------------------------------|-----------|
+| Foreword .....                                               | 4         |
+| Introduction .....                                           | 4         |
+| 1 Scope.....                                                 | 5         |
+| 2 References.....                                            | 5         |
+| 3 Definitions and abbreviations .....                        | 6         |
+| 3.1 Definitions.....                                         | 6         |
+| 3.2 Abbreviations .....                                      | 7         |
+| 4 Solution Set definitions.....                              | 7         |
+| <b>Annex A (normative): CORBA Solution Set.....</b>          | <b>8</b>  |
+| A.1 Architectural features.....                              | 8         |
+| A.1.1 Syntax for Distinguished Names.....                    | 8         |
+| A.1.2 Notifications.....                                     | 8         |
+| A.2 Mapping .....                                            | 8         |
+| A.2.1 General mappings.....                                  | 8         |
+| A.2.2 Operation and notification mapping.....                | 8         |
+| A.2.3 Operation parameter mapping.....                       | 9         |
+| A.2.4 Notification parameter mapping.....                    | 9         |
+| A.3 Solution Set definitions.....                            | 10        |
+| A.3.1 IDL definition structure.....                          | 10        |
+| A.3.2 IDL specification (file name "AAMConstDefs.idl") ..... | 11        |
+| A.3.3 IDL specification (file name "AAMSystem.idl") .....    | 13        |
+| <b>Annex B (normative): XML definitions.....</b>             | <b>15</b> |
+| B.1 Architectural Features .....                             | 15        |
+| B.1.1 Syntax for Distinguished Names.....                    | 15        |
+| B.1.2 Notification Services.....                             | 15        |
+| B.1.3 IOC definitions.....                                   | 15        |
+| B.2 Mapping .....                                            | 15        |
+| B.3 Solution Set definitions.....                            | 15        |
+| B.3.1 XML definition structure .....                         | 15        |
+| B.3.2 Graphical Representation.....                          | 16        |
+| B.3.3 XML Schema "aamIOCs.xsd".....                          | 17        |
+| <b>Annex C (normative): SOAP Solution Set.....</b>           | <b>19</b> |
+| C.1 Architectural features.....                              | 19        |
+| C.1.1 Syntax for Distinguished Names.....                    | 19        |
+| C.1.2 Notification Services.....                             | 19        |
+| C.1.3 Supported W3C specifications.....                      | 19        |
+| C.1.4 Prefixes and namespaces.....                           | 19        |
+| C.2 Mapping .....                                            | 20        |
+| C.2.1 Operation and notification mapping.....                | 20        |
+| C.2.2 Operation parameter mapping.....                       | 20        |
+| C.2.3 Notification parameter mapping.....                    | 20        |
+| C.3 Solution Set definitions.....                            | 21        |
+| C.3.1 WSDL definition structure .....                        | 21        |
+| C.3.2 Graphical Representation.....                          | 21        |
+| C.3.3 WSDL specification "AAMIRPSystem.wsdl".....            | 22        |
+| Annex D (informative): Change history.....                   | 26        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.121: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements.
+- 32.122: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS).
+- 32.126: Advanced Alarm Management (AAM) Integration Reference Point (IRP): Solution Set (SS) definitions.**
+
+The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 [4].
+
+A single network fault may generate a large number of alarms over space and time. In a large and complex network, simultaneous network faults may occur, causing the network operator to be flooded with high volume of alarms. The high volume of alarms, typically the one received by an IRPManager via the getAlarmList or alarm notifications of Alarm IRP specification, greatly inhibits the operator ability to quickly identify and locate the responsible network faults. Advanced Alarm Management IRP is intended to provide methods to improve this situation.
+
+# --- 1 Scope
+
+The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 [6]).
+
+This Solution Set specification is related to TS 32.122 v10.0.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.121: "Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements".
+- [6] 3GPP TS 32.122: "Telecommunication management; Advanced Alarm Management (AAM) Integrations Reference Point (IRP); Information Service (IS)".
+- [7] W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
+- [8] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
+- [9] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
+- [10] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
+- [11] W3C REC-xml-names-19990114: "Namespaces in XML".
+- [12] W3C SOAP 1.1 specification (<http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>)
+- [13] W3C XPath 1.0 specification (<http://www.w3.org/TR/1999/REC-xpath-19991116>)
+- [14] W3C WSDL 1.1 specification (<http://www.w3.org/TR/2001/NOTE-wsdl-20010315>)
+- [15] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>)
+- [16] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions".
+- [17] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)"
+- [18] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+
+# --- 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].
+
+**Alike Alarm:** Two alarms are considered alike, if the corresponding alarm notifications are issued by the same object instance with the same alarmType, same perceivedSeverity, same probableCause and same specificProblem (if present).
+
+**Lower Edge of Time Window:** The point in time which determines the begin of a time span.
+
+**Upper Edge of Time Window:** The point in time which determines the end of a time span
+
+**XML file:** file containing an XML document
+
+**XML document:** composed of the succession of an optional XML declaration followed by a root XML element
+
+NOTE: See [7]; in the scope of the present document.
+
+**XML declaration:** it specifies the version of XML being used
+
+NOTE: See [7].
+
+**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
+
+NOTE: See [7].
+
+**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
+
+NOTE: See [7].
+
+**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
+
+**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
+
+NOTE: See [7].
+
+**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
+
+NOTE: See [7].
+
+**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.
+
+NOTE: See [7].
+
+**XML attribute specification:** has a name and a value
+
+NOTE: See [7].
+
+**DTD:** defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD
+
+NOTE: See [7].
+
+**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
+
+NOTE: See [8], [9] and [10].
+
+**XML namespace:** enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas
+
+NOTE: See [11], in the scope of the present document.
+
+**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
+
+NOTE: See [8], [9] and [10].
+
+**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
+
+NOTE: See [8], [9] and [10].
+
+## 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].
+
+|         |                                |
+|---------|--------------------------------|
+| AAM     | Advanced Alarm Management      |
+| AAMRule | Advanced Alarm Management Rule |
+| CM      | Configuration Management       |
+| EM      | Element Manager                |
+| IOC     | Information Object Class       |
+| IRP     | Integration Reference Point    |
+| IS      | Information Service            |
+| Itf-N   | Interface N                    |
+| MIB     | Management Information Base    |
+| NE      | Network Element                |
+| XML     | eXtensible Markup Language     |
+
+# --- 4 Solution Set definitions
+
+This specification defines the following 3GPP Advance Alarm 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 AAM IRP: Information Service (3GPP TS 32.122 [6]).
+
+---
+
+## A.1 Architectural features
+
+The overall architectural feature of Advanced Alarm Management IRP is specified in 3GPP TS 32.122 [6]
+
+### A.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300[18]
+
+### A.1.2 Notifications
+
+Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.306 [16]).
+
+Currently there are no AAM IRP notifications defined in 3GPP TS 32.122 [6].
+
+---
+
+## A.2 Mapping
+
+### A.2.1 General mappings
+
+Not applicable.
+
+### A.2.2 Operation and notification mapping
+
+The AAM IS (3GPP TS 32.122 [6]) defines semantics of operations visible across the Itf-N.
+
+Table A.2.2-1 indicates mapping of these operations and notifications to their equivalents defined in this CORBA SS.
+
+**Table A.2.2-1: Mapping from IS Operation to SS equivalents**
+
+| IS Operation / Notification<br>(3GPP TS 32.122) | SS Method           | Qualifier |
+|-------------------------------------------------|---------------------|-----------|
+| activateAAMRule                                 | activate_aam_rule   | M         |
+| getAAMRules                                     | get_aam_rules       | M         |
+| deactivateAAMRule                               | deactivate_aam_rule | M         |
+
+### A.2.3 Operation parameter mapping
+
+The AAM IS (3GPP TS 32.122 [6]) defines semantics of parameters carried in operations across the Itf-N. The following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this CORBA SS.
+
+**Table A.2.3-1: Mapping from IS `activate_aam_rule` parameters to SS equivalents**
+
+| IS Operation parameter               | SS Method parameter                                                                                                                                                                                                                                                                                                                                                                   | Qualifier |
+|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>aam_rule_type</code>           | <code>AAMConstDefs::AAMRuleType</code>                                                                                                                                                                                                                                                                                                                                                | M         |
+| <code>aam_rule_parameter_list</code> | <code>AAMConstDefs::AAMRuleParameterList</code>                                                                                                                                                                                                                                                                                                                                       | M         |
+| <code>filter</code>                  | <code>AdvancedAlarmManagementConstDefs::FilterType</code>                                                                                                                                                                                                                                                                                                                             | M         |
+| <code>status</code>                  | Exceptions:<br><code>AAMConstDefs::ActivateAAMRule</code> ,<br><code>AAMConstDefs::AAMRuleAlreadyActive</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M         |
+| <code>aam_rule_identifier</code>     | <code>AAMConstDefs::AAMRuleIdentifier</code>                                                                                                                                                                                                                                                                                                                                          | M         |
+
+**Table A.2.3-2: Mapping from IS `get_advanced_alarm_management_rules` parameters to SS equivalents**
+
+| IS Operation parameter     | SS Method parameter                                                                                                                                                                                                                                                                                                          | Qualifier |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>aam_rule_list</code> | <code>AAMConstDefs::AAMRuleList</code>                                                                                                                                                                                                                                                                                       | M         |
+| <code>Status</code>        | Exceptions:<br><code>AAMConstDefs::GetAAMRules</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M         |
+
+**Table A.2.3-3: Mapping from IS `deactivate_aam_rule` parameters to SS equivalents**
+
+| IS Operation parameter           | SS Method parameter                                                                                                                                                                                                                                                                                                                                                                         | Qualifier |
+|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>aam_rule_identifier</code> | <code>AAMConstDefs::AAMRuleIdentifier</code>                                                                                                                                                                                                                                                                                                                                                | M         |
+| <code>Status</code>              | Exceptions:<br><code>AAMConstDefs::DeactivateAAMRule</code> ,<br><code>AAMConstDefs::SpecifiedRuleNotExisting</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M         |
+
+### A.2.4 Notification parameter mapping
+
+None.
+
+## --- A.3 Solution Set definitions
+
+### A.3.1 IDL definition structure
+
+Clause A.3.2 defines the constants and types used by the AAM IRP.
+
+Clause A.3.3 defines the operations which are performed by the AAM IRP agent.
+
+### A.3.2 IDL specification (file name "AAMConstDefs.idl")
+
+```
+// File: AAMConstDefs.idl
+#ifndef _AAM_CONST_DEFS_IDL_
+#define _AAM_CONST_DEFS_IDL_
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: AAMConstDefs */
+
+module AAMConstDefs
+{
+
+/*****
+ * definition of types used in several operations for Advanced Alarm Management */
+/*****
+
+enum AAMRuleType {
+    THRESHOLD_RULE,
+    TRANSIENT_RULE,
+    TOGGLE_RULE,
+    VENDOR_SPECIFIC_RULE
+};
+
+enum Status {SUCCESS, FAILURE, AAM_RULE_ALREADY_ACTIVE };
+
+typedef string AAMRuleIdentifier;
+
+/*****
+ * types used in operation activateAAMRule and */
+ * types used in operation getAAMRules */
+/*****
+
+typedef string FilterType;
+
+typedef string TimeSpan;
+typedef string AlarmOccurenceThreshold;
+typedef string SlidingTimeWindow;
+
+struct AAMRuleParameterListForTransientRule
+{
+    TimeSpan time_span;
+};
+
+struct AAMRuleParameterListForThresholdRule
+{
+    AlarmOccurenceThreshold alarm_occurence_threshold;
+    SlidingTimeWindow sliding_time_window;
+};
+
+struct AAMRuleParameterListForToggleRule
+{
+    AlarmOccurenceThreshold alarm_occurence_threshold;
+    SlidingTimeWindow sliding_time_window_toggling_started;
+    SlidingTimeWindow sliding_time_window_toggling_settled;
+};
+
+typedef string VendorSpecificParameterIdentifier;
+typedef string VendorSpecificParameterValue;
+
+struct VendorSpecificParameter
+{
+    VendorSpecificParameterIdentifier vendor_specific_parameter_identifier;
+    VendorSpecificParameterValue vendor_specific_parameter_value;
+};
+
+typedef sequence <VendorSpecificParameter> AAMRuleParameterListForVendorSpecificRule;
+
+/* The AAMRuleParameterList may contain a list of */
+```
+
+```
+
+/* AAMParameters with different content depending on the */
+/* AAMRuleType. */
+union AAMRuleParameterList switch (AAMRuleType)
+{
+    case THRESHOLD_RULE: AAMRuleParameterListForTransientRule
+                        aam_rule_parameter_list_for_transient_rule;
+    case TRANSIENT_RULE: AAMRuleParameterListForThresholdRule
+                        aam_rule_parameter_list_for_threshold_rule;
+    case TOGGLE_RULE: AAMRuleParameterListForToggleRule
+                        aam_rule_parameter_list_for_toggle_rule;
+    case VENDOR_SPECIFIC_RULE: AAMRuleParameterListForVendorSpecificRule
+                        aam_rule_parameter_list_for_vendor_specificRule;
+};
+
+struct AAMRule
+{
+    AAMRuleIdentifier aam_rule_identifier;
+    AAMRuleType aam_rule_type;
+    AAMRuleParameterList aam_rule_parameter_list;
+    FilterType filter;
+};
+
+typedef sequence <AAMRule> AAMRuleList;
+
+/*****
+ * types used in operation deactivateAAMRule only */
+/*****
+
+ * none */
+
+};
+
+#endif // _AAM_CONST_DEFS_IDL_
+
+```
+
+### A.3.3 IDL specification (file name "AAMSystem.idl")
+
+```
+//File: AAMSystem.idl
+#ifndef _AAM_SYSTEM_IDL_
+#define _AAM_SYSTEM_IDL_
+
+#include <AAMConstDefs.idl>
+#include <GenericIRPManagementSystem.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: AAMSystem */
+
+module AdvancedAlarmManagementIRPOperation_1
+{
+
+    /*
+    If the system fails to complete an operation, then it can provide a reason
+    to qualify the exception. The semantics carried in this reason are outside
+    the scope of the present document.
+    */
+
+    exception ActivateAAMRule { string reason; };
+    exception AAMRuleAlreadyActive { string reason; };
+    exception GetAAMRules { string reason; };
+    exception DeactivateAAMRule { string reason; };
+    exception SpecifiedRuleNotExisting { string reason; };
+
+    interface AdvancedAlarmManagement
+    {
+
+        AAMConstDefs::Status activate_aam_rule
+        /* for the purpose of this operation see 3GPP TS 32.322 */
+        (
+            in AAMConstDefs::AAMRuleType
+                aam_rule_type,
+            in AAMConstDefs::AAMRuleParameterList
+                aam_rule_parameter_list,
+            in AAMConstDefs::FilterType filter,
+            out AAMConstDefs::AAMRuleIdentifier
+                aam_rule_identifier
+        )
+        raises
+        (
+            ActivateAAMRule,
+            AAMRuleAlreadyActive,
+            GenericIRPManagementSystem::ParameterNotSupported,
+            GenericIRPManagementSystem::InvalidParameter,
+            GenericIRPManagementSystem::ValueNotSupported,
+            GenericIRPManagementSystem::OperationNotSupported
+        );
+
+        AAMConstDefs::Status get_aam_rules
+        /* for the purpose of this operation see 3GPP TS 32.322 */
+        (
+            out AAMConstDefs::AAMRuleList
+                aam_rule_list
+        )
+        raises
+        (
+            GetAAMRules,
+            GenericIRPManagementSystem::ParameterNotSupported,
+            GenericIRPManagementSystem::InvalidParameter,
+            GenericIRPManagementSystem::ValueNotSupported,
+            GenericIRPManagementSystem::OperationNotSupported
+        );
+
+        AAMConstDefs::Status deactivate_aam_rule
+        /* for the purpose of this operation see 3GPP TS 32.322 */
+        (
+            in AAMConstDefs::AAMRuleIdentifier
+                aam_rule_identifier
+        )
+        raises
+    }
+}
+```
+
+```
+(
+    DeactivateAAMRule,
+    SpecifiedRuleNotExisting,
+    GenericIRPManagementSystem::ParameterNotSupported,
+    GenericIRPManagementSystem::InvalidParameter,
+    GenericIRPManagementSystem::ValueNotSupported,
+    GenericIRPManagementSystem::OperationNotSupported
+);
+```
+
+```
+};
+```
+
+```
+);
+#endif // _AAM_SYSTEM_IDL_
+```
+
+# --- Annex B (normative): XML definitions
+
+This annex contains the XML Definitions for the Advance Alarm Management Integration Reference Point (AAM IRP) as it applies to Itf-N, in accordance with AAM IRP IS definitions [6]
+
+## --- B.1 Architectural Features
+
+The overall architectural feature of AAM IRP is specified in 3G TS 32.122 [6]. 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[18].
+
+### B.1.2 Notification Services
+
+Currently there are no AAM IRP notifications defined in 3GPP TS 32.122 [6].
+
+### B.1.3 IOC definitions
+
+This annex defines the XML syntax for the IOC definitions of the AAM IRP IS [6], which are used by the XML definitions for the AAM IRP notifications and the AAM 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 AAM IOC as defined in [6].
+
+### B.3.2 Graphical Representation
+
+![UML Class Diagram showing the structure of AdvancedAlarmManagementRule and its parameter lists.](5cab96b2d23174c25919840ecd50aa48_img.jpg)
+
+```
+classDiagram
+    class AdvancedAlarmManagementRule
+    class xaa:AAMRuleParameterListForTransientRule
+    class xaa:AAMRuleParameterListForThresholdRule
+    class xaa:AAMRuleParameterListForToggleRule
+    class xaa:AAMRuleParameterListForVendorSpecificRule
+    class xaa:TimeSpan
+    class xaa:AlarmOccurenceThreshold
+    class xaa:SlidingTimeWindow
+    class xaa:SlidingTimeWindowTogglin...
+    class xaa:VendorSpecificParameter
+    class xaa:VendorSpecificParameterId...
+    class xaa:VendorSpecificParameterVa...
+
+    AdvancedAlarmManagementRule --> xaa:AAMRuleParameterListForTransientRule
+    AdvancedAlarmManagementRule --> xaa:AAMRuleParameterListForThresholdRule
+    AdvancedAlarmManagementRule --> xaa:AAMRuleParameterListForToggleRule
+    AdvancedAlarmManagementRule --> xaa:AAMRuleParameterListForVendorSpecificRule
+
+    xaa:AAMRuleParameterListForTransientRule --> xaa:TimeSpan
+    xaa:AAMRuleParameterListForThresholdRule --> xaa:AlarmOccurenceThreshold
+    xaa:AAMRuleParameterListForThresholdRule --> xaa:SlidingTimeWindow
+    xaa:AAMRuleParameterListForToggleRule --> xaa:AlarmOccurenceThreshold
+    xaa:AAMRuleParameterListForToggleRule --> xaa:SlidingTimeWindowTogglin...
+    xaa:AAMRuleParameterListForToggleRule --> xaa:SlidingTimeWindowTogglin...
+    xaa:AAMRuleParameterListForVendorSpecificRule --> xaa:VendorSpecificParameter
+    xaa:VendorSpecificParameter --> xaa:VendorSpecificParameterId...
+    xaa:VendorSpecificParameter --> xaa:VendorSpecificParameterVa...
+```
+
+The diagram illustrates the structure of **AdvancedAlarmManagementRule** and its associated parameter lists. The main class, **AdvancedAlarmManagementRule**, is shown on the left. It has four associations leading to different parameter list classes, each represented by a yellow box:
+
+- xaa:AAMRuleParameterListForTransientRule**: Contains the attribute **xaa:TimeSpan**.
+- xaa:AAMRuleParameterListForThresholdRule**: Contains the attributes **xaa:AlarmOccurenceThreshold** and **xaa:SlidingTimeWindow**.
+- xaa:AAMRuleParameterListForToggleRule**: Contains the attributes **xaa:AlarmOccurenceThreshold**, **xaa:SlidingTimeWindowTogglin...**, and **xaa:SlidingTimeWindowTogglin...**.
+- xaa:AAMRuleParameterListForVendorSpecificRule**: Contains the attribute **xaa:VendorSpecificParameter**. This attribute is further associated with a class **xaa:VendorSpecificParameter** (also shown in a yellow box), which contains the attributes **xaa:VendorSpecificParameterId...** and **xaa:VendorSpecificParameterVa...**. The association between **xaa:VendorSpecificParameter** and **xaa:VendorSpecificParameter** has a multiplicity of **1..∞**.
+
+UML Class Diagram showing the structure of AdvancedAlarmManagementRule and its parameter lists.
+
+### B.3.3 XML Schema “aamIRPIOCs.xsd”
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  3GPP TS 32.126 AAMIRP IOC XML Schema
+  aamIRPIOCs.xsd
+-->
+<schema xmlns:xaa="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#aamIRPIOCs"
+  xmlns="http://www.w3.org/2001/XMLSchema"
+  targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#aamIRPIOCs"
+  elementFormDefault="qualified" attributeFormDefault="unqualified">
+  <simpleType name="AdvancedAlarmManagementRuleIdentifier">
+    <restriction base="string">
+      <length value="64"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="AdvancedAlarmManagementRuleType">
+    <restriction base="string">
+      <enumeration value="THRESHOLD_RULE"/>
+      <enumeration value="TRANSIENT_RULE"/>
+      <enumeration value="TOGGLE_RULE"/>
+      <enumeration value="VENDOR_SPECIFIC_RULE"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="TimeSpan">
+    <restriction base="string">
+      <length value="3"/>
+    </restriction>
+  </simpleType>
+  <complexType name="AAMRuleParameterListForTransientRule">
+    <sequence>
+      <element name="TimeSpan" type="xaa:TimeSpan"/>
+    </sequence>
+  </complexType>
+  <simpleType name="AlarmOccurenceThreshold">
+    <restriction base="string">
+      <length value="3"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="SlidingTimeWindow">
+    <restriction base="string">
+      <length value="3"/>
+    </restriction>
+  </simpleType>
+  <complexType name="AAMRuleParameterListForThresholdRule">
+    <sequence>
+      <element name="AlarmOccurenceThreshold" type="xaa:AlarmOccurenceThreshold"/>
+      <element name="SlidingTimeWindow" type="xaa:SlidingTimeWindow"/>
+    </sequence>
+  </complexType>
+  <complexType name="AAMRuleParameterListForToggleRule">
+    <sequence>
+      <element name="AlarmOccurenceThreshold" type="xaa:AlarmOccurenceThreshold"/>
+      <element name="SlidingTimeWindowTogglingStarted" type="xaa:SlidingTimeWindow"/>
+      <element name="SlidingTimeWindowTogglingSettled" type="xaa:SlidingTimeWindow"/>
+    </sequence>
+  </complexType>
+  <simpleType name="VendorSpecificParameterIdentifier">
+    <restriction base="string">
+      <length value="64"/>
+    </restriction>
+  </simpleType>
+  <simpleType name="VendorSpecificParameterValue">
+    <restriction base="string">
+      <length value="64"/>
+    </restriction>
+  </simpleType>
+  <complexType name="VendorSpecificParameter">
+    <sequence>
+      <element name="VendorSpecificParameterIdentifier"
+        type="xaa:VendorSpecificParameterIdentifier"/>
+      <element name="VendorSpecificParameterValue" type="xaa:VendorSpecificParameterValue"/>
+    </sequence>
+  </complexType>
+  <complexType name="AAMRuleParameterListForVendorSpecificRule">
+    <sequence>
+```
+
+```
+
+        <element name="VendorSpecificParameter" type="xaa:VendorSpecificParameter"
+maxOccurs="unbounded"/>
+      </sequence>
+    </complexType>
+    <complexType name="AdvancedAlarmManagementRuleParameterList">
+      <choice>
+        <element name="AAMRuleParameterListForTransientRule"
+type="xaa:AAMRuleParameterListForTransientRule"/>
+        <element name="AAMRuleParameterListForThresholdRule"
+type="xaa:AAMRuleParameterListForThresholdRule"/>
+        <element name="AAMRuleParameterListForToggleRule"
+type="xaa:AAMRuleParameterListForToggleRule"/>
+        <element name="AAMRuleParameterListForVendorSpecificRule"
+type="xaa:AAMRuleParameterListForVendorSpecificRule"/>
+      </choice>
+    </complexType>
+    <simpleType name="Filter">
+      <restriction base="string">
+        <length value="256"/>
+      </restriction>
+    </simpleType>
+    <!-- Attributes of the advancedAlarmManagementRule IOC -->
+    <element name="advancedAlarmManagementRuleIdentifier"
+type="xaa:AdvancedAlarmManagementRuleIdentifier"/>
+    <element name="advancedAlarmManagementRuleType" type="xaa:AdvancedAlarmManagementRuleType"/>
+    <element name="advancedAlarmManagementRuleParameterList"
+type="xaa:AdvancedAlarmManagementRuleParameterList"/>
+    <element name="filter" type="xaa:Filter"/>
+  </schema>
+
+```
+
+# --- Annex C (normative): SOAP Solution Set
+
+This annex specifies the SOAP Solution Set for the IRP whose semantics are specified in AAM IRP: Information Service (3GPP TS 32.122 [6]).
+
+---
+
+## C.1 Architectural features
+
+The overall architectural feature of the AAM IRP is specified in 3GPP TS 32.122 [6]. This clause specifies features that are specific to the SOAP Solution Set.
+
+### C.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300[18].
+
+### C.1.2 Notification Services
+
+Currently there are no AAM IRP notifications defined in 3GPP TS 32.122 [6].
+
+### C.1.3 Supported W3C specifications
+
+The overall architectural feature of the Advanced Alarm Management IRP is specified in 3GPP TS 32.122 [6]. This clause specifies features that are specific to the SOAP solution set.
+
+The SOAP 1.1 specification [12] and WSDL 1.1 specification [14] are supported.
+
+The SOAP 1.2 specification [15] is supported optionally.
+
+This specification uses "document" style in WSDL file.
+
+This specification uses "literal" encoding style in WSDL file.
+
+The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification [13]). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex.
+
+### C.1.4 Prefixes and namespaces
+
+This specification uses a number of namespace prefixes throughout that are listed in Table C.1.4.
+
+**Table C.1.4: Prefixes and Namespaces used in this specification**
+
+| PREFIX           | NAMESPACE                                                                                                                                                                     |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| (no prefix)      | <a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a>                                                                                               |
+| soap             | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a>                                                                                     |
+| aamIRPSystem     | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMRPSystem</a>                           |
+| aamIRPData       | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRPData">http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRPData</a>                             |
+| aam              | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#aamIRP">http://www.3gpp.org/ftp/specs/archive/32_series/32.126#aamIRP</a>                                     |
+| xn               | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm">http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm</a>                             |
+| genericIRPSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem</a>                 |
+| ntfIRPNtfSystem  | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem</a> |
+
+## C.2 Mapping
+
+### C.2.1 Operation and notification mapping
+
+The Advanced Alarm Management IRP IS (3GPP TS 32.122 [6]) defines semantics of operation and notification visible across the Itf-N. Table C.2.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
+
+**Table C.2.1: Mapping from IS Operation to SS Equivalents**
+
+| IS Operations in 3GPP TS 32.122 [6] | SS Operations          | Qualifier |
+|-------------------------------------|------------------------|-----------|
+| activateAAMRule                     | activateAAMRule        | M         |
+| getAAMRules                         | getAAMRules            | M         |
+| deactivateAAMRule                   | deactivateAAMRule      | M         |
+| getIRPVersion (note 1)              | getIRPVersion          | M         |
+| getOperationProfile (note 1)        | getOperationProfile    | O         |
+| getNotificationProfile (note 1)     | getNotificationProfile | O         |
+
+NOTE 1: These 3 operations are operations of ManagedGenericIRP IOC specified in 3GPP TS 32.312 [17]. The AdvancedAlarmManagementIRP IOC of 3GPP TS 32.122 [6] inherits from it.
+
+### C.2.2 Operation parameter mapping
+
+The Advanced Alarm Management IRP IS (3GPP TS 32.122 [6]) defines semantics of parameters carried in the operations. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table C.2.2.1: Mapping from IS activateAAMRule parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter  | Qualifier |
+|------------------------|----------------------|-----------|
+| aAMRuleType            | aAMRuleType          | M         |
+| aAMRuleParameterList   | aAMRuleParameterList | M         |
+| filter                 | filter               | M         |
+| aAMRuleIdentifier      | aAMRuleIdentifier    | M         |
+| status                 | status               | M         |
+
+**Table C.2.2.2: Mapping from IS getAAMRules parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|---------------------|-----------|
+| aAMRuleList            | aAMRuleList         | M         |
+| status                 | status              | M         |
+
+**Table C.2.2.3: Mapping from IS deactivateAAMRule parameters to SS equivalents**
+
+| IS Operation parameter                | SS Method parameter                   | Qualifier |
+|---------------------------------------|---------------------------------------|-----------|
+| advancedAlarmManagementRuleIdentifier | advancedAlarmManagementRuleIdentifier | M         |
+| status                                | status                                | M         |
+
+### C.2.3 Notification parameter mapping
+
+The Advance Alarm Management IRP IS (3GPP TS 32.122 [6]) does not currently define any notifications.
+
+## C.3 Solution Set definitions
+
+### C.3.1 WSDL definition structure
+
+Clause C.3.2 provides a graphical representation of the AAM IRP service.
+
+Clause C.3.3 defines the services which are supported the AAM IRP agent.
+
+### C.3.2 Graphical Representation
+
+The WSDL structure is depicted in Figure C.3.2 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service.
+
+![WSDL structure diagram showing AAMIRPPortType, AAMIRPBinding, and AAMIRPService components and their relationships.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+The diagram illustrates the WSDL structure for the Advance Alarm IRP SOAP Solution Set. It consists of three main components connected by lines: AAMIRPPortType, AAMIRPBinding, and AAMIRPService.
+
+- AAMIRPPortType**: Contains three operations: activateAAMRule, getAAMRules, and deactivateAAMRule.
+- AAMIRPBinding**: Contains three operations: activateAAMRule, getAAMRules, and deactivateAAMRule. It specifies the transport as http://schemas.xmlsoap.org/soap/http.
+- AAMIRPService**: Contains two ports: AAMIRPPort and GenericIRPPort. AAMIRPPort is associated with the AAMIRPBinding and has a location of http://www.3gpp.org/ftp/specs/archive/32\_series/32.126#AAMIRP. GenericIRPPort is associated with the GenericIRPSystem:GenericIRPBinding and has a location of http://www.3gpp.org/ftp/specs/archive/32\_series/32.316#GenericIRP.
+
+Relationships: AAMIRPPortType is connected to AAMIRPBinding. AAMIRPBinding is connected to AAMIRPService. Specifically, AAMIRPBinding is connected to the AAMIRPPort within AAMIRPService.
+
+WSDL structure diagram showing AAMIRPPortType, AAMIRPBinding, and AAMIRPService components and their relationships.
+
+**Figure C.3.2: Advance Alarm IRP SOAP Solution Set WSDL structure**
+
+### C.3.3 WSDL specification “AAMIRPSystem.wsdl”
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    3GPP TS 32.126 Advanced Alarm Management (AAM) IRP SOAP Solution Set
+-->
+<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
+    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
+    xmlns:aamIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRPSystem"
+    xmlns:aamIRPData="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRPData"
+    xmlns:xaa="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#aamIRPIOCs"
+    xmlns:genericIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem"
+    targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRPSystem"
+    <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem"/>
+    <types>
+        <schema targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRPData"
+            xmlns="http://www.w3.org/2001/XMLSchema">
+            <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#aamIRPIOCs"/>
+            <!-- The following types are defined for the AAM IRP operations -->
+            <complexType name="AdvancedAlarmRule">
+                <sequence>
+                    <element name="AdvancedAlarmRuleIdentifier"
+                        type="xaa:AdvancedAlarmManagementRuleIdentifier"/>
+                    <element name="AdvancedAlarmRuleType" type="xaa:AdvancedAlarmManagementRuleType"/>
+                    <element name="AdvancedAlarmManagementRuleParameterList"
+                        type="xaa:AdvancedAlarmManagementRuleParameterList"/>
+                    <element name="Filter" type="xaa:Filter"/>
+                </sequence>
+            </complexType>
+            <complexType name="AdvancedAlarmRuleList">
+                <sequence>
+                    <element name="AdvancedAlarmRule" type="aamIRPData:AdvancedAlarmRule"
+                        maxOccurs="unbounded"/>
+                </sequence>
+            </complexType>
+            <simpleType name="Status">
+                <restriction base="string">
+                    <enumeration value="Success"/>
+                    <enumeration value="AAMRuleAlreadyActive"/>
+                    <enumeration value="SpecifiedRuleNotExisting"/>
+                    <enumeration value="Failure"/>
+                </restriction>
+            </simpleType>
+            <!-- activateAAMRule Request-->
+            <element name="activateAAMRule">
+                <complexType>
+                    <sequence>
+                        <element name="advancedAlarmManagementRuleType"
+                            type="xaa:AdvancedAlarmManagementRuleType"/>
+                        <element name="advancedAlarmManagementRuleParameterList"
+                            type="xaa:AdvancedAlarmManagementRuleParameterList"/>
+                        <element name="filter" type="xaa:Filter"/>
+                    </sequence>
+                </complexType>
+            </element>
+            <!-- activateAAMRule Response -->
+            <element name="activateAAMRuleResponse">
+                <complexType>
+                    <sequence>
+                        <element name="advancedAlarmManagementRuleIdentifier"
+                            type="xaa:AdvancedAlarmManagementRuleIdentifier"/>
+                        <element name="status" type="aamIRPData:Status"/>
+                    </sequence>
+                </complexType>
+            </element>
+            <!-- activateAAMRule Fault -->
+            <element name="activateAAMRuleFault">
+                <simpleType>
+                    <restriction base="string">
+                        <enumeration value="OPERATION_FAILED"/>
+                    </restriction>
+                </simpleType>
+            </element>
+            <!-- getAAMRules Request-->
+            <element name="getAAMRules">
+                <!-- no input parameter -->
+                <complexType>
+```
+
+```
+
+        <sequence>
+          <element name="dummy" type="string" minOccurs="0"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- getAAMRules Response -->
+    <element name="getAAMRulesResponse">
+      <complexType>
+        <sequence>
+          <element name="advancedAlarmRuleList" type="aamIRPData:AdvancedAlarmRuleList"/>
+          <element name="status" type="aamIRPData:Status"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- getAAMRules Fault -->
+    <element name="getAAMRulesFault">
+      <simpleType>
+        <restriction base="string">
+          <enumeration value="OPERATION_FAILED"/>
+        </restriction>
+      </simpleType>
+    </element>
+    <!-- deactivateAAMRule Request-->
+    <element name="deactivateAAMRule">
+      <complexType>
+        <sequence>
+          <element name="advancedAlarmManagementRuleIdentifier"
+type="xaa:AdvancedAlarmManagementRuleIdentifier"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- deactivateAAMRule Response -->
+    <element name="deactivateAAMRuleResponse">
+      <complexType>
+        <sequence>
+          <element name="status" type="aamIRPData:Status"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- deactivateAAMRule Fault -->
+    <element name="deactivateAAMRuleFault">
+      <simpleType>
+        <restriction base="string">
+          <enumeration value="OPERATION_FAILED"/>
+        </restriction>
+      </simpleType>
+    </element>
+  </schema>
+</types>
+<message name="activateAAMRule">
+  <part name="parameter" element="aamIRPData:activateAAMRule"/>
+</message>
+<message name="activateAAMRuleResponse">
+  <part name="parameter" element="aamIRPData:activateAAMRuleResponse"/>
+</message>
+<message name="activateAAMRuleFault">
+  <part name="parameter" element="aamIRPData:activateAAMRuleFault"/>
+</message>
+<message name="getAAMRules">
+  <part name="parameter" element="aamIRPData:getAAMRules"/>
+</message>
+<message name="getAAMRulesResponse">
+  <part name="parameter" element="aamIRPData:getAAMRulesResponse"/>
+</message>
+<message name="getAAMRulesFault">
+  <part name="parameter" element="aamIRPData:getAAMRulesFault"/>
+</message>
+<message name="deactivateAAMRule">
+  <part name="parameter" element="aamIRPData:deactivateAAMRule"/>
+</message>
+<message name="deactivateAAMRuleResponse">
+  <part name="parameter" element="aamIRPData:deactivateAAMRuleResponse"/>
+</message>
+<message name="deactivateAAMRuleFault">
+  <part name="parameter" element="aamIRPData:deactivateAAMRule"/>
+</message>
+<portType name="AAMIRPPortType">
+  <operation name="activateAAMRule">
+
+```
+
+```
+
+    <input message="aamIRPSystem:activateAAMRule"/>
+    <output message="aamIRPSystem:activateAAMRuleResponse"/>
+    <fault name="activateAAMRuleFault" message="aamIRPSystem:activateAAMRuleFault"/>
+  </operation>
+  <operation name="getAAMRules">
+    <input message="aamIRPSystem:getAAMRules"/>
+    <output message="aamIRPSystem:getAAMRulesResponse"/>
+    <fault name="getAAMRulesFault" message="aamIRPSystem:getAAMRulesFault"/>
+  </operation>
+  <operation name="deactivateAAMRule">
+    <input message="aamIRPSystem:deactivateAAMRule"/>
+    <output message="aamIRPSystem:deactivateAAMRuleResponse"/>
+    <fault name="deactivateAAMRuleFault" message="aamIRPSystem:deactivateAAMRuleFault"/>
+  </operation>
+</portType>
+<binding name="AAMIRPBinding" type="aamIRPSystem:AAMIRPPortType">
+  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+  <operation name="activateAAMRule">
+    <soap:operation
+      soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#activateAAMRule"
+      style="document"/>
+    <input>
+      <soap:body use="literal"/>
+    </input>
+    <output>
+      <soap:body use="literal"/>
+    </output>
+    <fault name="activateAAMRuleFault">
+      <soap:fault name="activateAAMRuleFault" use="literal"/>
+    </fault>
+  </operation>
+  <operation name="getAAMRules">
+    <soap:operation
+      soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#getAAMRules" style="document"/>
+    <input>
+      <soap:body use="literal"/>
+    </input>
+    <output>
+      <soap:body use="literal"/>
+    </output>
+    <fault name="getAAMRulesFault">
+      <soap:fault name="getAAMRulesFault" use="literal"/>
+    </fault>
+  </operation>
+  <operation name="deactivateAAMRule">
+    <soap:operation
+      soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#deactivateAAMRule"
+      style="document"/>
+    <input>
+      <soap:body use="literal"/>
+    </input>
+    <output>
+      <soap:body use="literal"/>
+    </output>
+    <fault name="deactivateAAMRuleFault">
+      <soap:fault name="deactivateAAMRuleFault" use="literal"/>
+    </fault>
+  </operation>
+</binding>
+<service name="AAMIRPService">
+  <port name="AAMIRPPort" binding="aamIRPSystem:AAMIRPBinding">
+    <soap:address location="http://www.3gpp.org/ftp/specs/archive/32_series/32.126#AAMIRP"/>
+  </port>
+  <port name="GenericIRPPort" binding="genericIRPSystem:GenericIRPBinding">
+    <soap:address
+      location="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRP"/>
+  </port>
+</service>
+</definitions>
+
+```
+
+# --- Annex D (informative): Change history
+
+| Change history |       |           |     |     |                                                  |        |        |
+|----------------|-------|-----------|-----|-----|--------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                  | Old    | New    |
+| 2010-09        | SA#49 | SP-100505 | --  | --  | Presentation to SA for Information and Approval  | ---    | 1.0.0  |
+| 2010-10        | --    | --        | --  | --  | Publication                                      | 1.0.0  | 10.0.0 |
+| 2011-06        | SA#52 | SP-110291 | 001 | --  | Correct syntax errors in AAM IRP schema and wsdl | 10.0.0 | 10.1.0 |
+

marked/Rel-10/32_series/32141/raw.md

@@ -0,0 +1,356 @@
+
+
+# Keywords UMTS, management , architecture 3GPP TS 32.141 V10.0.0 (2011-03)
+
+*Technical Specification*
+
+**3GPP**
+
+## Postal address **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **Telecommunication management;** **Subscription Management (Su)** 3GPP support office address 650 Route des Lucioles - Sophia Antipolis 06410 VALBONNE - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 95 47 16
+
+![LTE logo with '4ADVANCED' text above the 'e'](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e'
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon below the 'P'](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo with a signal icon below the 'P'
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- 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 Subscription Management (SuM) architecture ..... | 6         |
+| 4.1 Functional entities .....                      | 7         |
+| 4.2 Interfaces .....                               | 8         |
+| 4.2.1 Application of Itf-N for SuM .....           | 8         |
+| 4.2.2 Void .....                                   | 8         |
+| 4.3 Overview of IRP.....                           | 8         |
+| 4.3.1 IRP security .....                           | 9         |
+| 4.4 Methodology .....                              | 9         |
+| 4.4.1 SuM Stage 1 .....                            | 9         |
+| 4.4.2 SuM Stage 2 .....                            | 9         |
+| 4.4.3 SuM Stage 3 .....                            | 10        |
+| <b>Annex A (informative): Void.....</b>            | <b>11</b> |
+| Annex B (informative): Change history.....         | 12        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
+
+- TS 32.140: "Subscription Management (SuM) requirements".
+- TS 32.141: "Subscription Management (SuM) architecture".**
+- TS 32.171: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements".
+- TS 32.172: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
+- TS 32.176: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions".
+
+The 3G environment requires more complex service delivery mechanisms and is no longer simply an internal matter for a single operator but a capability that is achieved by linking together features across multiple service providers and operators. Subscription Management (SuM) is a feature that permits Service Providers, Value Added Service Providers, and Mobile Operators to provision services for a specific subscriber. The feature is necessary to allow service providers and operators to provision, control, monitor and bill the configuration of services that they offer to their subscribers.
+
+For further details see 3GPP TS 32.140 [5] on SuM requirements that gives an overview of SuM.
+
+# --- 1 Scope
+
+The present document defines the architecture for Subscription Management (SuM).
+
+# --- 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 23.002: "Network Architecture".
+- [3] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [4] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [5] 3GPP TS 32.140: "Telecommunication management; Subscription Management (SuM) requirements".
+- [6] 3GPP TS 23.008: "Organization of subscriber data".
+- [7] 3GPP TS 32.150: "Integration Reference Point (IRP) Concept and definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**subscriber:** See 3GPP TR 21.905 [1].
+
+**service:** See 3GPP TR 21.905 [1].
+
+**Integration Reference Point (IRP):** See 3GPP TS 32.101 [3].
+
+**user:** See 3GPP TR 21.905 [1].
+
+**subscription:** See 3GPP TR 21.905 [1].
+
+**Subscription Management (SuM):** See 3GPP TR 32.140 [5].
+
+**Subscription Profile:** See 3GPP TR 32.140 [5].
+
+**Subscription Profile Component:** See 3GPP TR 32.140 [5].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                                   |
+|-----|-----------------------------------|
+| 2G  | Second Generation Mobile          |
+| 3G  | Third Generation Mobile           |
+| API | Application Programming Interface |
+
+|        |                                                  |
+|--------|--------------------------------------------------|
+| ASP    | Application Service Provider                     |
+| AuC    | Authentication Center                            |
+| B2B    | Business to Business                             |
+| CS     | Circuit Switch                                   |
+| EIR    | Equipment Identity Register                      |
+| GTT    | Global Text Telephony                            |
+| GUP    | Generic User Profile                             |
+| HE     | Home Environment                                 |
+| HLR    | Home Location Register                           |
+| HSS    | Home Subscriber Server                           |
+| IMS    | IP Multimedia Subsystem                          |
+| IRP    | Integration Reference Point (3GPP TS 32.102 [4]) |
+| ISP    | Internet Service Provider                        |
+| NPDB   | Number Portability Data Base                     |
+| NRM    | Network Resource Model                           |
+| OAM    | Operations, Administration and Maintenance       |
+| OSA    | Open Services Access                             |
+| OSF    | Operations System Functions                      |
+| OSS    | Operations Support System                        |
+| PS     | Packet Switch                                    |
+| SLA    | Service Level Agreement                          |
+| SM&O   | Service Management and Operations (TMF/ITU-T)    |
+| SP     | Service Provider                                 |
+| SuM    | Subscription Management                          |
+| TMN    | Telecommunication Management Network             |
+| TR-IRP | Trading Partner IRP                              |
+| UICC   | Universal Integrated Circuit Card                |
+| USIM   | Universal Subscriber Identity Module             |
+| VASP   | Value Added Service Provider                     |
+| VHE    | Virtual Home Environment                         |
+| VNO    | Virtual Network Operator                         |
+
+# --- 4 Subscription Management (SuM) architecture
+
+3G Telecommunication Management focuses on the most important and strategic contexts in the physical architecture for the management of UMTS. The framework to help define a telecom management physical architecture for a planned UMTS and to adopt standards and provide products that are easy to integrate is defined in 3GPP TS 32.102 [4].
+
+SuM manages Subscription Profile Components stored in network resources for the purpose of providing services to specific subscribers. This is done with an architecture that is consistent with the one specified in 3GPP TS 32.102 [4].
+
+Subscription Profiles represent services and are associated to subscribers that employ these services (3GPP TS 32.140 [5]). To the extent the HSS controls certain services, Subscription Profile Components can be associated with the HSS. Other services, and as a result Subscription Profiles Components, are outside the jurisdiction of the HSS.
+
+## 4.1 Functional entities
+
+Functional entities belonging to SuM are described in Figure 1. The figure also contains the actors related to Subscriptions.
+
+![Figure 1: Functional entities in SUM. A UML class diagram showing relationships between actors (PLMN operator/Service Provider, Subscriber, User) and entities (Service, Subscription Profile, Service Preferences, Subscription Profile Component, System).](a7d78d22e465dea388b31d0739f9d0cd_img.jpg)
+
+```
+
+classDiagram
+    actor PLMN_operator_Service_Provider as PLMN operator/Service Provider
+    actor Subscriber
+    actor User
+    class Service
+    class Subscription_Profile as Subscription Profile
+    class Service_Preferences as Service Preferences
+    class Subscription_Profile_Component as Subscription Profile Component
+    class System
+
+    PLMN_operator_Service_Provider "1" -- "0..n" Service : Has
+    Subscriber "1" -- "0..n" Subscription_Profile : Has
+    User "1" -- "0..n" Service_Preferences : Has
+    Service "1" -- "0..n" Subscription_Profile : Refers to
+    Subscription_Profile "1" -- "0..n" Service_Preferences : Defines
+    Subscription_Profile "1" -- "0..n" Subscription_Profile_Component : Consists of
+    Subscription_Profile_Component -- System : Resides in
+
+    subgraph SM_O_mapping [SM&O mapping of information entities]
+        Service
+        Subscription_Profile
+        Service_Preferences
+    end
+  
+```
+
+The diagram illustrates the functional entities and actors in the SuM (Service Management) domain. It shows the following relationships:
+
+- PLMN operator/Service Provider** (actor) has **Service** (entity) (1 to 0..n).
+- Subscriber** (actor) has **Subscription Profile** (entity) (1 to 0..n).
+- User** (actor) has **Service Preferences** (entity) (1 to 0..n).
+- Service** (entity) refers to **Subscription Profile** (entity) (1 to 0..n).
+- Subscription Profile** (entity) defines **Service Preferences** (entity) (1 to 0..n).
+- Subscription Profile** (entity) consists of **Subscription Profile Component** (entity) (1 to 0..n).
+- Subscription Profile Component** (entity) resides in **System** (entity).
+
+A dashed oval labeled "SM&O mapping of information entities" encloses the **Service**, **Subscription Profile**, and **Service Preferences** entities.
+
+Figure 1: Functional entities in SUM. A UML class diagram showing relationships between actors (PLMN operator/Service Provider, Subscriber, User) and entities (Service, Subscription Profile, Service Preferences, Subscription Profile Component, System).
+
+Figure 1: Functional entities in SUM
+
+Actors described in Figure 1 are:
+
+- **Subscriber** (definition See TS 21.905)
+- **User** (definition See TS 21.905)
+- **Service Provider** (definition See TS 21.905)
+- **PLMN Operator** (definition See TS 21.905)
+
+The entities described in Figure 1 are:
+
+- **Subscription Profile** (definition See TS 32.140)
+- **Subscription Profile Component** (definition See TS 32.140)
+- **Service** (definition See TS 21.905)
+- **System** (definition See TS 32.102)
+- **Service Preferences**: Contains the service preferences chosen for a user. Each user configures his preferences for a particular subscribed service, but only within the limits defined by the Subscription.
+
+### Clarifications to the figure:
+
+- A PLMN Operator/Service Provider has one or several Services to offer for Subscribers.
+- A Subscriber has one or several Subscription Profiles, where each describes an offered Service.
+- A User has one or several Service Preferences, where each describes the user's chosen preferences for the service.
+
+- A Subscription Profile may consist of one or several Subscription Profile Components.
+- A Subscription Profile may define one or several Service Preferences.
+- A Subscription Profile Component resides in one or several systems
+- Subscriptions are managed in the form of Subscription profile components, which may be distributed across Service Management & Operations (SM&O), Network Resource Management & Operations (RM&O) and Network Domains. There may also be mappings among the SM&O, RM&O and Network Domains.
+
+## 4.2 Interfaces
+
+### 4.2.1 Application of Itf-N for SuM
+
+![Diagram showing the OSF for Network Management and Service Management connected via Itf-N to various OSF domains: User Equipment Domain, Access Network Domain, Core Network Basic Entities Domain (Common CN, CS, PS), and Core network Service Specific entities. The NE Management is also shown.](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+The diagram illustrates the architecture of PLMN Telecom Management Domains. At the top, a large box labeled "OSF for Network Management and Service Management" is connected via a vertical line labeled "Itf-N" to a lower section. This lower section contains four boxes: "OSF User Equipment Domain", "OSF Access Network Domain", "OSF Core Network Basic Entities Domain" (which is further divided into "Common CN Domain", "CS Domain", and "PS (GPRS) Domain"), and "OSF Core network Service Specific entities". To the right of these boxes is a label "NE Management".
+
+Diagram showing the OSF for Network Management and Service Management connected via Itf-N to various OSF domains: User Equipment Domain, Access Network Domain, Core Network Basic Entities Domain (Common CN, CS, PS), and Core network Service Specific entities. The NE Management is also shown.
+
+**Figure 2: Overview of PLMN Telecom Management Domains and Itf-N (3GPP TS 32.102 [4])**
+
+The Itf-N for SuM is realized by means of an Integration Reference Point (IRP) as defined in 3GPP TS 32.102 [4].
+
+Operations System Functions (OSF) functionality can be realized in NEs or in the NE Management systems. SuM, for this release, is concerned with the OSF functionality contained in the Core Network Basic Entities Domain and specifically that of the Common CN Domain. Subscription Profile Components are located in the NEs OSF's within the Common CN Domain or their NEs OSF's in the NE management systems, and are in either case accessed consistent with the IRP concept. SuM OSF's for Network Management and Service Management are located in network- and service management systems.
+
+### 4.2.2 Void
+
+## 4.3 Overview of IRP
+
+Figures 3 and 4 identify system contexts of the IRP in terms of its implementation, called IRP Agent (3GPP TS 32.150 [7]), and the user of the IRP Agent, called IRP Manager (3GPP TS 32.150 [7]).
+
+The IRP Agent implements and supports the Interface IRPs for SuM NRM IRP. The IRP Agent can reside in an Element Manager (EM) or a Network Element (NE) (3GPP TS 32.102 [4]). In the former case, the interface (represented by a thick dotted line) between the EM and the NEs is not the subject of the Interface IRPs for SuM NRM IRP.
+
+An IRP Manager using the Interface IRPs for SuM NRM IRP shall choose one of the two System Contexts defined here, for each NE. For instance, if an EM is responsible for managing a number of NEs, the NM shall access the Interface IRPs for SuM NRM IRP through the EM and not directly to those NEs.
+
+The interface IRPs for SuM NRM IRP can be the followings:
+
+- Basic CM IRP
+
+![Figure 3: System Context A. A diagram showing the interaction between an IRPManager (NM) and an IRPAgent (EM). The IRPManager is connected to the IRPAgent via a solid line. The IRPAgent is connected to NEs via a dotted line. A dashed vertical line separates the NM and EM domains. An arrow labeled 'Itf-N' points to the interface between the NM and EM. A bracket on the right side of the interface is labeled 'Interface IRPs for SuM NRM IRP'.](3121ebddccf183ca63bb9781be440a7e_img.jpg)
+
+Figure 3: System Context A. A diagram showing the interaction between an IRPManager (NM) and an IRPAgent (EM). The IRPManager is connected to the IRPAgent via a solid line. The IRPAgent is connected to NEs via a dotted line. A dashed vertical line separates the NM and EM domains. An arrow labeled 'Itf-N' points to the interface between the NM and EM. A bracket on the right side of the interface is labeled 'Interface IRPs for SuM NRM IRP'.
+
+**Figure 3: System Context A**
+
+![Figure 4: System Context B. A diagram showing the interaction between an IRPManager (NM) and an IRPAgent (NE). The IRPManager is connected to the IRPAgent via a solid line. A dashed vertical line separates the NM and NE domains. An arrow labeled 'Itf-N' points to the interface between the NM and NE. A bracket on the right side of the interface is labeled 'Interface IRPs for SuM NRM IRP'.](990567efebf979be51f56d1150012c9d_img.jpg)
+
+Figure 4: System Context B. A diagram showing the interaction between an IRPManager (NM) and an IRPAgent (NE). The IRPManager is connected to the IRPAgent via a solid line. A dashed vertical line separates the NM and NE domains. An arrow labeled 'Itf-N' points to the interface between the NM and NE. A bracket on the right side of the interface is labeled 'Interface IRPs for SuM NRM IRP'.
+
+**Figure 4: System Context B**
+
+### 4.3.1 IRP security
+
+The IRP interface is made secure by controlling access to the network and management systems. Operations processes must insure that only authorized personnel have the access authority to retrieve and alter SuM data. Standard protocols used over the interface between the IRPManager and the IRPAgent provide some degree of security. The exact nature of the security is described in the Solution Set for that protocol. In addition to the requirement that the IRPManager and the IRPAgent be secure, most physical links between them are secured as well.
+
+## 4.4 Methodology
+
+The methodology used to conclude the standard work for SuM shall follow the IRP methodology described in 3GPP TS 32.150 [4]. This subclause describes how to apply that methodology.
+
+### 4.4.1 SuM Stage 1
+
+SuM Stage 1 is documented in 3GPP TS 32.140 [5].
+
+### 4.4.2 SuM Stage 2
+
+SuM Stage 2 is documented as follows:
+
+- a) The present document (3GPP TS 32.141) is finalized by identifying the relevant IRPs.
+- b) 3GPP TS 32.171 describes the Requirements for the NRM IRP – containing the Information Object Classes (IOCs), attributes, relations etc. for SuM.  
+3GPP TS 32.171 shall, where applicable, follow the structure from 3GPP TS 32.621 (Configuration Management (CM); Generic network resources Integration Reference Point (IRP): requirements).
+- c) 3GPP TS 32.172 describes the Information Service for the Network Resource Model (NRM) IRP – containing the Information Object Classes (IOCs), attributes, relations etc. for SuM.  
+3GPP TS 32.172 shall, where applicable, follow the structure from 3GPP TS 32.622 (Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)).
+
+### 4.4.3 SuM Stage 3
+
+SuM Stage 3 is documented in the following documents:
+
+- TS 32.176 SuM NRM IRP: Solution set definition
+
+---
+
+Annex A (informative): Void
+
+# --- Annex B (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                                                        |       |        |
+|----------------|-------|-----------|------|-----|----------------------------------------------------------------------------------------------------------------------------------------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                                        | Old   | New    |
+| Mar 2003       | SA 19 | SP-030042 | --   | --  | Submitted to SA#19 as v1.0.0 for Information                                                                                           | 1.0.0 | --     |
+| Sep 2003       | SA 21 | SP-030405 | --   | --  | Submitted to SA#21 as v2.0.0 for Approval                                                                                              | 2.0.0 | 6.0.0  |
+| Mar 2004       | SA_23 | SP-040108 | 0001 | --  | Subscription Management TS-family (32.14x and 32.17x) title alignment ("SM" becomes "SuM" and delete "Services operations management") | 6.0.0 | 6.1.0  |
+| Jun 2007       | SA 36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7.                                                                                 | 6.1.0 | 7.0.0  |
+| Dec 2008       | SA 42 | --        | --   | --  | Upgrade to Release 8                                                                                                                   | 7.0.0 | 8.0.0  |
+| Sep 2009       | SA 45 | SP-090627 | 0002 | --  | Align with TS 32.140 SuM requirements                                                                                                  | 8.0.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -    | -   | Update to Rel-10 version (MCC)                                                                                                         | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32150/raw.md

@@ -0,0 +1,487 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                               |           |
+|-------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                | 4         |
+| Introduction .....                                                            | 4         |
+| 1 Scope.....                                                                  | 5         |
+| 2 References.....                                                             | 5         |
+| 3 Definitions and abbreviations .....                                         | 6         |
+| 3.1 Definitions.....                                                          | 6         |
+| 3.2 Abbreviations .....                                                       | 7         |
+| 4 Integration Reference Points (IRPs) .....                                   | 8         |
+| 4.1 Introduction .....                                                        | 8         |
+| 4.1.1 General .....                                                           | 8         |
+| 4.1.2 IRP Specifications Approach .....                                       | 9         |
+| 4.2 Integration levels.....                                                   | 10        |
+| 4.2.1 Application integration.....                                            | 10        |
+| 4.3 Application of IRPs.....                                                  | 11        |
+| 4.4 Defining the IRPs.....                                                    | 12        |
+| 4.5 Void.....                                                                 | 12        |
+| 4.6 Mandatory, Optional and Conditional qualifiers.....                       | 13        |
+| 4.7 System context for Interface IRPs.....                                    | 15        |
+| <b>Annex A (informative): Void.....</b>                                       | <b>16</b> |
+| <b>Annex B (normative): Void.....</b>                                         | <b>17</b> |
+| <b>Annex C (informative): Void.....</b>                                       | <b>18</b> |
+| <b>Annex D (informative): Void.....</b>                                       | <b>19</b> |
+| <b>Annex E (normative): Void.....</b>                                         | <b>20</b> |
+| <b>Annex F (informative): Void.....</b>                                       | <b>21</b> |
+| <b>Annex G (normative): IOC Properties and Inheritance .....</b>              | <b>22</b> |
+| G.1 Property.....                                                             | 22        |
+| G.2 Inheritance.....                                                          | 23        |
+| <b>Annex H (normative): Interface Properties and Inheritance .....</b>        | <b>24</b> |
+| H.1 Property.....                                                             | 24        |
+| H.2 Inheritance.....                                                          | 24        |
+| <b>Annex I (normative): Entity (Interface, IOC and Attribute) Import.....</b> | <b>25</b> |
+| Annex H (informative): Change history.....                                    | 26        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.150: Integration Reference Point (IRP) Concept and definitions**
+- TS 32.151: Integration Reference Point (IRP) Information Service (IS) template
+- TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
+- TS 32.153: Integration Reference Point (IRP) technology specific templates
+- TS 32.154: Backward and Forward Compatibility (BFC); Concept and definitions
+- TS 32.155: Telecommunication management; Requirements template
+
+# --- 1 Scope
+
+The present document provides the overall concept for all Integration Reference Point (IRP) specifications. Relevant IRP overview and high-level definitions are already provided in 3GPP TS 32.101 [1] and TS 32.102 [2].
+
+IRP specifications are intended to be applicable to any management interface (see definition of Integration Reference Point in subclause 3.1).
+
+# --- 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.151: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template".
+- [4] 3GPP TS 32.152: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire".
+- [5] ITU-T Recommendation M.3020: "TMN Interface Specification Methodology".
+- [6] OMG IDL Style Guide, ab/98-06-03, June 17, 1998.
+- [7] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service (IS)".
+- [8] 3GPP TS 32.601: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements".
+- [9] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
+- [10] 3GPP TS 32.606: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions".
+- [11] 3GPP TS 32.621: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements".
+- [12] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [13] 3GPP TS 32.626: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [14] 3GPP TS 32.671: "Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Requirements".
+- [15] 3GPP TS 32.672: "Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Information Service (IS)".
+
+[16] 3GPP TS 32.676: "Telecommunication management; Configuration Management (CM); State Management 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 TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.151 [3] and the following apply:
+
+**Data Definition IRP:** 3GPP publishes IRP specifications relating to commonly used data definitions that can be imported for use by Interface IRP and/or NRM IRP. This term represents all such specifications. An example of a Data Definition IRP is the State Management IRP (32.671 [14], 32.672 [15], 32.676 [16], etc.).
+
+**Information Object Class (IOC):** Describes the information that can be passed/used in management interfaces and is modelled using the stereotype "Class" in the UML meta-model. For a formal definition of Information Object Class and its structure of specification, see 3GPP TS 32.151[3].
+
+**Integration Reference Point (IRP):** An architectural concept that is described by a set of specifications for definition of a certain aspect of a management interface, comprising a **Requirements** specification, an **Information Service** specification, and one or more **Solution Set** specifications.
+
+**Interface IRP:** 3GPP publishes a number of IRP specifications each of which is related to a set of operations and notifications for a specific telecom management domain such as alarm management, configuration management, etc. Interface IRPs also contain definitions of Support IOCs. This term represents all such specifications. An example of an Interface IRP is the Basic CM IRP (the set of TSs 32.601 [8], 32.602 [9], 32.606 [10], etc.).
+
+**IRP Agent:** Encapsulates a well-defined subset of network (element) functions. It interacts with IRPManagers using one or more IRPs. From the IRPManager's perspective, the IRP Agent behaviour is only visible via the IRP(s).
+
+**Information Service (IS):** an IRP Information Service describes the information related to the entities (either network resources or support objects) to be managed and the way that the information may be managed for a certain functional area (e.g. the Alarm IRP Information Service in the fault management area). Information Services are defined for all IRPs.
+
+**IRP Manager:** Models a user of IRP Agent(s) and it interacts directly with the IRP Agent(s) using IRP(s). Since the IRP Manager represents an IRP Agent user, it gives a clear picture of what the IRP Agent is supposed to do. From the IRP Agent perspective, the IRP Manager behaviour is only visible via the IRP.
+
+**Managed Object (MO):** An instance of a Managed Object Class (MOC).
+
+**Managed Object Class (MOC):** The mapping of an Information Object Class (IOC) to a Solution Set.
+
+**Managed Object Instance (MOI):** An instance of a MOC, i.e. the same as a MO as described above.
+
+**Network Resource Model (NRM):** An Information Service describing Information Object Classes representing the manageable aspects of network resources, e.g. an RNC or NodeB.
+
+**NRM IRP:** 3GPP publishes a number of IRP specifications each of which is related to a particular NRM (Network Resource Model) as defined in 3GPP TS 32.101 [1]. NRM IRPs do not define any operations or notifications. This term represents all such specifications. Note: In some NRM IRP titles, for historic reasons, they are named "...network resources IRP"). An example of an NRM IRP is the Generic NRM IRP (32.621 [11], 32.622 [12], 32.626 [13], etc.).
+
+**Solution Set (SS):** contains a mapping of the IRP Information Service (IS) defined entities (that are technology-agnostic) to technology specific termed entities. It does not contain specification of the entities' semantics. The semantics can be found in the corresponding IS. It is noted that one IS can be mapped to one or several SSs.
+
+**Support IOC:** IOC that represents a particular capability, introduced to model a management service. As an example of Support IOC, in the Alarm IRP Information Service [59] there are the AlarmInformation and AlarmList IOCs.
+
+**YyyIRP:** 3GPP defines a number of support-IOCs (defined in Interface IRPs) such as AlarmIRP, BasicCMIRP and EPIRP. This term represents all such support-IOCs.
+
+**Yyy IRP:** For a specific Interface IRP such as the Basic CM IRP, when the letters Yyy are replaced by the specific key words naming that IRP (in the given example the Yyy is replaced by “Basic CM”), this term represents all specifications that are part of that Interface IRP.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.151 [3] and the following apply:
+
+|       |                                                  |
+|-------|--------------------------------------------------|
+| CORBA | Common Object Request Broker Architecture        |
+| EM    | Element Manager                                  |
+| GDMO  | Guidelines for the Definition of Managed Objects |
+| GUI   | Graphical User Interface                         |
+| IDL   | Interface Definition Language                    |
+| IOC   | Information Object Class                         |
+| IRP   | Integration Reference Point                      |
+| IS    | Information Service                              |
+| NE    | Network Element                                  |
+| NM    | Network Manager                                  |
+| NRM   | Network Resource Model                           |
+| OMG   | Object Management Group                          |
+| ORB   | Object Request Broker                            |
+| PSA   | Product Specific Application                     |
+| SMP   | System Management Processes                      |
+| SNM   | Sub-Network Manager                              |
+| SS    | Solution Set                                     |
+| TMF   | TeleManagement Forum                             |
+| TOM   | Telecom Operations Map                           |
+| UML   | Unified Modelling Language                       |
+
+# 4 Integration Reference Points (IRPs)
+
+## 4.1 Introduction
+
+For the purpose of management interface development 3GPP has developed an interface concept known as Integration Reference Point (IRP) to promote the wider adoption of standardized management interfaces in telecommunication networks. The IRP concept and associated methodology employs protocol and technology neutral modelling methods as well as protocol specific solution sets to achieve its goals.
+
+### 4.1.1 General
+
+The three cornerstones of the IRP concept are:
+
+- **Top-down, process-driven modelling approach:** The purpose of each IRP is automation of one specific task, related to TMF TOM. This allows taking a "one step at a time" approach with a focus on the most important tasks.
+- **Technology-independent modelling:** To create from the requirements an interface technology independent model. This is specified in the IRP Information Service.
+- **Standards-based technology-dependent modelling:** To create one or more interface technology dependent models from the technology independent model. This is specified in the IRP Solution Set(s).
+
+![Diagram of IRP components showing the hierarchy from Requirements to Information Service to Solution Sets.](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+The diagram illustrates the components of an Integration Reference Point (IRP). It is structured into three main levels:
+
+- IRP REQUIREMENTS:** The top level, represented by a yellow box containing a white box labeled "IRP REQUIREMENTS".
+- IRP INFORMATION SERVICE:** The middle level, represented by a white box containing two icons: a document with a person and a tree diagram, separated by a plus sign (+). This box is situated within a larger yellow box.
+- IRP SOLUTION SETS:** The bottom level, represented by a pink box containing four stacked colored bars labeled "SNMP" (blue), "XML" (green), "SOAP" (magenta), and "CORBA" (orange). Two large green arrows point from the "IRP INFORMATION SERVICE" box down to the "IRP SOLUTION SETS" box.
+
+Diagram of IRP components showing the hierarchy from Requirements to Information Service to Solution Sets.
+
+Figure 4.1: IRP components (with example Solution Sets; for definition of valid 3GPP Solution Sets, see Annex C in TS 32.101 [1])
+
+### 4.1.2 IRP Specifications Approach
+
+As highlighted in the previous subclause, IRP specifications are specified using a 3-level approach: Requirements, IS-level and SS-level.
+
+Furthermore, there are three categories of IRP specifications (see formal and more detailed definitions in subclause 3.1):
+
+- Interface IRPs
+- NRM IRPs
+- Data Definition IRPs.
+
+Each category is partitioned into Requirements, IS-level and SS-level specifications.
+
+![Diagram illustrating the IRP 3-Level Specifications Approach combined with the three IRP categories. The diagram shows three horizontal levels: Requirements / Use Cases, Information Service Definitions (UML), and Solution Set Definitions (CORBA, SOAP, XML, CMIP) and Solution Set Definitions (other/future e.g. JAVA, SNMP). The first two levels are further divided into three vertical categories: Interface IRP's, NRM IRP's, and Data Definition IRP's. Annotations on the right indicate stability or change over time for each level.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+The diagram illustrates the IRP 3-Level Specifications Approach combined with the three IRP categories. It is structured as follows:
+
+- Requirements / Use Cases** (Top Level): This level is divided into three categories:
+  - Interface IRP's**
+  - NRM IRP's**
+  - Data Definition IRP's**
+ An annotation on the right indicates this level is "Relative stable over long period of time".
+- Information Service Definitions (UML)** (Middle Level): This level is also divided into three categories:
+  - Interface IRP's**: Notification IRP, Alarm IRP, BulkCM IRP, KernelCM IRP, BasicCM IRP, etc.
+  - NRM IRP's**: Generic NRM, CoreNW NRM, UMTS NRM's, CDMA NRM's, Inventory NRM, etc.
+  - Data Definition IRP's**: State Mgmt IRP, etc.
+ An annotation on the right indicates this level "Changes only with respect to addition and extensions".
+- Solution Set Definitions (CORBA, SOAP, XML, CMIP)** and **Solution Set Definitions (other/future e.g. JAVA, SNMP)** (Bottom Level): This level represents technology-specific definitions. An annotation on the right indicates this level "Changes with new/better Technologies".
+
+Diagram illustrating the IRP 3-Level Specifications Approach combined with the three IRP categories. The diagram shows three horizontal levels: Requirements / Use Cases, Information Service Definitions (UML), and Solution Set Definitions (CORBA, SOAP, XML, CMIP) and Solution Set Definitions (other/future e.g. JAVA, SNMP). The first two levels are further divided into three vertical categories: Interface IRP's, NRM IRP's, and Data Definition IRP's. Annotations on the right indicate stability or change over time for each level.
+
+Figure 4.2: The IRP 3-Level Specifications Approach combined with the three IRP categories.
+
+#### Level 1:
+
+The "Requirements-level" intends to provide conceptual and use cases definitions for a specific management interface aspect as well as defining subsequent requirements for this IRP.
+
+#### Level 2:
+
+- The "IS-level" provides the technology independent specification of an IRP.
+
+#### Level 3:
+
+The "SS-level" finally provides the mapping of IS definitions into one or more technology-specific Solution Sets. This concept provides support for multiple interface technologies as applicable on a vendor and/or network type basis and also enables accommodation of future interface technologies - without the need to redefine requirements and IS-level definitions.
+
+## 4.2 Integration levels
+
+Virtually all types of telecom/datacom networks comprise many different technologies purchased from several different vendors. This implies that the corresponding management solution need to be built by integrating product-specific applications from different vendors with a number of generic applications that each provide some aspect of multi-vendor and/or multi-technology support. A complete management solution is thus composed of several independent applications.
+
+The following levels of integration are defined:
+
+- **Screen Integration:** Each application provides its own specific Graphical User Interface (GUI) that need to be accessible from a single, unified screen (a common desktop). A seamless integration between the various GUIs is then required. Screen Integration is not specified in the present document.
+- **Application Integration:** Applications need to interwork, on a machine-machine basis, in order to automate various end-to-end processes of a communication provider.
+
+### 4.2.1 Application integration
+
+Interfaces related to application integration can be divided in the following three categories:
+
+- 1) **High-level generic interfaces:** between generic applications on the network and service management layers. The same approach and concepts apply for these as the next category.
+- 2) **High-level (technology-independent to the extent possible) interfaces:** between product-specific and generic applications are needed in order to automate and streamline frequently occurring tasks applicable to several types of network elements. A top-down approach shall be taken when defining these interfaces, where the main input is:
+  - a) business processes of a communication provider; and
+  - b) the types of generic applications that are used to implement the process support.
+
+- 3) **Detailed (product-specific) interfaces:** between product-specific applications and the corresponding network elements are of course also needed. These interfaces are defined using the traditional bottom-up approach, where the actual network infrastructure is modelled. This is the traditional TMN approach to element management. The management information in these interfaces is not further discussed in the present document, as it is internal to a specific development organization and does not need to be open. In fact, by publishing the management information in these interfaces, too much of the internal design may be revealed and it may become impossible to later enhance the systems that are using the interfaces. The management services (operations and notifications) and protocol shall however be open and standardized as long as they are independent of the NRM describing the managed NEs/NRs.
+
+## 4.3 Application of IRPs
+
+When providing integrated management solutions for multi-vendor networks, there is a strong requirement that the NEs and the management solutions that go together with them are systems integratable.
+
+It should be noted that these IRPs could be provided by an IRP Agent on any management interface.
+
+These IRPs are introduced to ensure interoperability, for example between Product-Specific Applications (PSA) and the Network and System Management Processes (SMP) of the Network Manager (NM) - see figure 4.3 from TS 32.101 [1]. These IRPs are considered to cover the most basic needs of task automation.
+
+![Figure 4.3: Examples of IRPs for application integration. The diagram shows a Network Manager at the top containing five Network & System Management Processes: Network Planning & Development, Network Inventory Management, Network Provisioning, Network Maintenance & Restoration, and Network Data Management. Below the Network Manager is a cloud representing a network element (NE) containing an Element Manager and a Product Specific Application (PSA). Arrows indicate the flow of Information Resource Protocols (IRPs) between the PSA and the Network Manager processes. The IRPs are categorized as Service IRPs, CM IRPs (Bulk, Inventory, State...), Common IRPs (Notification, File Xfer, Log...), FM IRPs (Alarm, Test...), and PM IRPs. On the left, two alternative IRPs are shown between the PSA and the NE. A legend at the bottom right defines PSA as Product Specific Application and NE as Network Element.](853f59c89931a666c07903b31d098277_img.jpg)
+
+Figure 4.3: Examples of IRPs for application integration. The diagram shows a Network Manager at the top containing five Network & System Management Processes: Network Planning & Development, Network Inventory Management, Network Provisioning, Network Maintenance & Restoration, and Network Data Management. Below the Network Manager is a cloud representing a network element (NE) containing an Element Manager and a Product Specific Application (PSA). Arrows indicate the flow of Information Resource Protocols (IRPs) between the PSA and the Network Manager processes. The IRPs are categorized as Service IRPs, CM IRPs (Bulk, Inventory, State...), Common IRPs (Notification, File Xfer, Log...), FM IRPs (Alarm, Test...), and PM IRPs. On the left, two alternative IRPs are shown between the PSA and the NE. A legend at the bottom right defines PSA as Product Specific Application and NE as Network Element.
+
+**Figure 4.3: Examples of IRPs for application integration**
+
+Taking one of the above mentioned IRPs as an example, the Network and System Management Processes have similar need to receive notifications from various PSAs. The corresponding service is formalized as a *Notification IRP*. It specifies: firstly, an interface through which subscriptions to different types of notifications can be set-up (or cancelled), and secondly, common attributes for all notifications.
+
+Further, applying a common *Name Convention for Managed Objects* is useful for co-operating applications that require identical interpretation of names assigned to network resources under management.
+
+## 4.4 Defining the IRPs
+
+It is important to accommodate more than one specific technology, as the technologies will change over time. Applications need to be future-proof. One fundamental principle for achieving this is to clearly separate the semantics of information definition from the protocols definitions (accessing the information) for the external interfaces.
+
+The framework being used to define IRPs allows the implementation of user requirements for each management capability (e.g. configuration management), by modelling the information related to the resources to be managed and the way that the information may be accessed and manipulated. Such modelling is done in a way that is independent of the technology and distribution used in the implementation of a management system.
+
+The IRP methodology uses the following steps:
+
+- Capture the management requirements.
+- Specify the semantics of the information to describe the system. Trace back to item (a).
+- Specify the semantics of the interactions between the management system and its clients. Trace back to item (a).
+- Specify the syntaxes of the information and interactions identified in (b) and (c). The specification is technology dependent. Trace back to items (b) and (c).
+
+Figure 4.4 shows an example of how an IRP can be structured (the Alarm IRP).
+
+![Figure 4.4: Example of an IRP (Alarm IRP). The diagram shows a layered structure for the Alarm IRP. The top layer is 'Alarm IRP: Requirements' (Requirements). The second layer is 'Alarm IRP: Information Service' (Information Service), which includes 'Notifications for Alarm reporting and operations possible over the Alarm IRP (Specified in UML and natural language)'. A dashed line separates the top two layers from the bottom layers, labeled 'Protocol independent' above and 'Protocol specific' below. The third layer is 'Solution Set Layer', which branches into three boxes: 'SNMP Solution Set' (Alarm IRP mapped to SNMP including standard SNMP MIB:s), 'CORBA Solution Set' (Alarm IRP mapped to CORBA IDL files. Alarm reporting mapped to OMG Structured events.), and 'CMIP Solution Set' (Alarm IRP mapped to GDMO including relevant ITU-T standards.). Below this are three rows of protocol boxes: 'Application Layer' (SNMP, CORBA/IIOP, CMIS/CMIP), 'Transport Layer' (UDP, TCP, OSI transport protocol), and 'Network Layer' (IP, OSI network protocol).](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+|                                                                                                                       |                                                                                       |                                                              |                      |
+|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|----------------------|
+| <b>Alarm IRP: Requirements</b>                                                                                        |                                                                                       |                                                              | Requirements         |
+| <b>Alarm IRP: Information Service</b>                                                                                 |                                                                                       |                                                              | Information Service  |
+| Notifications for Alarm reporting and operations possible over the Alarm IRP (Specified in UML and natural language). |                                                                                       |                                                              |                      |
+| <hr style="border-top: 1px dashed blue;"/>                                                                            |                                                                                       |                                                              | Protocol independent |
+| <b>Solution Set Layer</b>                                                                                             |                                                                                       |                                                              |                      |
+| <b>SNMP Solution Set</b>                                                                                              | <b>CORBA Solution Set</b>                                                             | <b>CMIP Solution Set</b>                                     |                      |
+| Alarm IRP mapped to SNMP including standard SNMP MIB:s                                                                | Alarm IRP mapped to CORBA IDL files. Alarm reporting mapped to OMG Structured events. | Alarm IRP mapped to GDMO including relevant ITU-T standards. |                      |
+| <hr style="border-top: 1px dotted black;"/>                                                                           |                                                                                       |                                                              |                      |
+| SNMP                                                                                                                  | CORBA/IIOP                                                                            | CMIS                                                         | Application Layer    |
+|                                                                                                                       |                                                                                       | CMIP                                                         |                      |
+| <hr style="border-top: 1px dotted black;"/>                                                                           |                                                                                       |                                                              |                      |
+| UDP                                                                                                                   | TCP                                                                                   | OSI transport protocol                                       | Transport Layer      |
+| <hr style="border-top: 1px dotted black;"/>                                                                           |                                                                                       |                                                              |                      |
+| IP                                                                                                                    |                                                                                       | OSI network protocol                                         | Network Layer        |
+
+Figure 4.4: Example of an IRP (Alarm IRP). The diagram shows a layered structure for the Alarm IRP. The top layer is 'Alarm IRP: Requirements' (Requirements). The second layer is 'Alarm IRP: Information Service' (Information Service), which includes 'Notifications for Alarm reporting and operations possible over the Alarm IRP (Specified in UML and natural language)'. A dashed line separates the top two layers from the bottom layers, labeled 'Protocol independent' above and 'Protocol specific' below. The third layer is 'Solution Set Layer', which branches into three boxes: 'SNMP Solution Set' (Alarm IRP mapped to SNMP including standard SNMP MIB:s), 'CORBA Solution Set' (Alarm IRP mapped to CORBA IDL files. Alarm reporting mapped to OMG Structured events.), and 'CMIP Solution Set' (Alarm IRP mapped to GDMO including relevant ITU-T standards.). Below this are three rows of protocol boxes: 'Application Layer' (SNMP, CORBA/IIOP, CMIS/CMIP), 'Transport Layer' (UDP, TCP, OSI transport protocol), and 'Network Layer' (IP, OSI network protocol).
+
+Figure 4.4: Example of an IRP (Alarm IRP)
+
+## 4.5 Void
+
+## 4.6 Mandatory, Optional and Conditional qualifiers
+
+This subclause defines a number of terms used to qualify the relationship between the Information Service, the Solution Sets and their impact on the IRP implementations. The qualifiers defined in this clause are used to qualify IRP Agent behaviour only. This is considered sufficient for the specification of the IRPs.
+
+IS specifications define IOC attributes, interfaces, operations, notifications, operation parameters and notification parameters. They can have the following support/read/write qualifiers: M, O, CM, CO, C.
+
+Definition of qualifier M (Mandatory):
+
+- Used for items that shall be supported.
+
+Definition of qualifier O (Optional):
+
+- Used for items which may or may not be supported.
+
+Definition of qualifier CM (Conditional-Mandatory):
+
+- Used for items that are mandatory under certain conditions, specifically:
+  - All items having the support qualifier CM shall have a corresponding constraint defined in the IS specification. If the specified constraint is met then the items shall be supported.
+
+Definition of qualifier CO (Conditional-Optional):
+
+- Used for items that are optional under certain conditions, specifically:
+  - All items having the support qualifier CO shall have a corresponding constraint defined in the IS specification. If the specified constraint is met then the items may be supported.
+
+Definition of qualifier C (SS-Conditional):
+
+- Used for items that are only applicable for certain but not all Solutions Sets (SSs).
+
+SS specifications define the SS-equivalents of the IS-defined IOC attributes, operations, notifications, operation parameters and notification parameters. These SS-equivalents can have the following support/read/write qualifiers: M, O, CM and CO.
+
+The mapping of the qualifiers of IS-defined constructs to the qualifiers of the corresponding SS-constructs is defined as follows:
+
+- For qualifier M, O, CM and CO, each IS-defined item (operation and notification, input and output parameter of operations, input parameter of notifications, information relationship and information attribute) shall be mapped to its equivalent(s) in all SSs. Mapped equivalent(s) shall have the same qualifier as the IS-defined qualifier.
+- For qualifier C, each IS-defined item shall be mapped to its equivalent(s) in at least one SS. Mapped equivalent(s) can have support qualifier M or O.
+
+Table 4.6 defines the semantics of qualifiers of the Interface IRP SS equivalents, in terms of support from the IRP Agent perspective.
+
+**Table 4.6: Semantics for Mandatory, Optional and Conditional qualifiers used in Solution Sets**
+
+| <b>Mapped SS Equivalent</b>                                                                           | <b>Mandatory</b>                                              | <b>Optional</b>                                                                                                                                                                                                                                                                                                                                                                 | <b>Conditional-Mandatory (CM)</b>                                                                                              | <b>Conditional-Optional (CO)</b>                                                                                                                                             |
+|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Mapped notification equivalent                                                                        | The IRP Agent shall generate the notification.                | The IRP Agent may or may not generate it.                                                                                                                                                                                                                                                                                                                                       | The IRP Agent shall generate this notification if the constraint described in the IS for this item is satisfied.               | The IRP Agent may choose whether or not to generate it. If the IRP Agent chooses to generate it, the constraint described in the IS for this notification must be satisfied. |
+| Mapped operation equivalent                                                                           | The IRP Agent shall support it.                               | The IRP Agent may or may not support this operation. If the IRP Agent does not support this operation, the IRP Agent shall reject the operation invocation with a reason indicating that the IRP Agent does not support this operation. The rejection, together with a reason, shall be returned to the IRP Manager.                                                            | The IRP Agent shall support this operation if the constraint described in the IS for this item is satisfied.                   | The IRP Agent may support this operation if the constraint described in the IS for this item is satisfied.                                                                   |
+| Input parameter of the mapped operation equivalent                                                    | The IRP Agent shall accept and behave according to its value. | The IRP Agent may or may not support this input parameter. If the IRP Agent does not support this input parameter and if it carries meaning (i.e. it does not carry no-information semantics), the IRP Agent shall reject the invocation with a reason (that it does not support the parameter). The rejection, together with the reason, shall be returned to the IRP Manager. | The IRP Agent shall accept and behave according to its value if the constraint described in the IS for this item is satisfied. | The IRP Agent may accept and behave according to its value if the constraint described in the IS for this item is satisfied.                                                 |
+| Input parameter of mapped notification equivalent AND output parameter of mapped operation equivalent | The IRP Agent shall supply this parameter.                    | The IRP Agent may supply this parameter.                                                                                                                                                                                                                                                                                                                                        | The IRP Agent shall supply this parameter if the constraint described in the IS for this item is satisfied.                    | The IRP Agent may supply this parameter if the constraint described in the IS for this item is satisfied.                                                                    |
+| Mapped IOC attribute equivalent                                                                       | The IRP Agent shall support it.                               | The IRP Agent may support it.                                                                                                                                                                                                                                                                                                                                                   | The IRP Agent shall support this attribute if the constraint described in the IS for this item is satisfied.                   | The IRP Agent may support this attribute if the constraint described in the IS for this item is satisfied.                                                                   |
+
+## 4.7 System context for Interface IRPs
+
+Every Interface IRP on a management interface (e.g. Alarm IRP, Notification IRP, Basic CM IRP, Bulk CM IRP) is subject to a System Context as described in this subclause (also consistent with 3GPP TS 32.102 [2] clause 8).
+
+Figure 4.7.1 and 4.7.2 identify system contexts of the Interface IRP in terms of its implementation, called IRP<sub>Agent</sub>, and the user of the IRP<sub>Agent</sub>, called IRP<sub>Manager</sub>.
+
+Each IRP<sub>Agent</sub> implements and supports one or more IRPs. The set of IRPs that is related to each Interface IRP is defined by the System Context subclause in each individual Interface IRP IS specification, e.g. subclause 4.2 in the Alarm IRP IS [7].
+
+An NE can be managed via System Context A or B. The criterion for choosing System Context A or B to manage a particular NE is implementation dependent. An IRP<sub>Agent</sub> shall support one of the two System Contexts. By observing the interaction across the management interface, an IRP<sub>Manager</sub> cannot deduce if the EM and NE are integrated in a single system or if they run in separate systems.
+
+![Diagram of System Context A showing an IRPManager in an NM connected to an IRPAgent in an EM, which is connected to NEs via a management interface (e.g. Itf-N). The IRPAgent supports IRP(s).](b90144cfbb81a2d610d920240fda689d_img.jpg)
+
+The diagram illustrates System Context A. On the left, a box labeled 'NM' contains a sub-box labeled 'IRPManager'. A solid line connects 'IRPManager' to a vertical dashed line representing the 'management interface (e.g. Itf-N)'. On the right of the interface, a box labeled 'EM' contains a sub-box labeled 'IRPAgent'. A solid line connects the 'IRPAgent' to the interface. A curved arrow points from the interface to the 'IRPAgent', labeled 'Supported IRP(s)'. A dotted line extends from the 'IRPAgent' to a box labeled 'NEs'.
+
+Diagram of System Context A showing an IRPManager in an NM connected to an IRPAgent in an EM, which is connected to NEs via a management interface (e.g. Itf-N). The IRPAgent supports IRP(s).
+
+Figure 4.7.1: System Context A
+
+![Diagram of System Context B showing an IRPManager in an NM connected to an IRPAgent in an NE, which is connected via a management interface (e.g. Itf-N). The IRPAgent supports IRP(s).](f57a881fcbcaf494a7dedc4f61224991_img.jpg)
+
+The diagram illustrates System Context B. On the left, a box labeled 'NM' contains a sub-box labeled 'IRPManager'. A solid line connects 'IRPManager' to a vertical dashed line representing the 'management interface (e.g. Itf-N)'. On the right of the interface, a box labeled 'NE' contains a sub-box labeled 'IRPAgent'. A solid line connects the 'IRPAgent' to the interface. A curved arrow points from the interface to the 'IRPAgent', labeled 'Supported IRP(s)'.
+
+Diagram of System Context B showing an IRPManager in an NM connected to an IRPAgent in an NE, which is connected via a management interface (e.g. Itf-N). The IRPAgent supports IRP(s).
+
+Figure 4.7.2: System Context B
+
+# --- Annex A (informative): Void
+
+# Annex B (normative): Void
+
+# Annex C (informative): Void
+
+# Annex D (informative): Void
+
+# Annex E (normative): Void
+
+# Annex F (informative): Void
+
+# Annex G (normative): IOC Properties and Inheritance
+
+## G.1 Property
+
+The properties of an IOC (including Support IOC) are specified in terms of the following:
+
+- a) An IOC attribute(s) including its semantics and syntax, its legal value ranges and support qualifications. The IOC attributes are not restricted to Configuration Management but also include those related to, for example, 1) Performance Management (i.e., measurement types), 2) Trace Management and 3) Accounting Management.
+- b) The non-attribute-specific behaviour associated with an IOC (see Note 1).
+
+NOTE 1: As an example, the Link between MscServerFunction and CsMgwFunction is optional. It is mandatory if the MscServerFunction instance belongs to one ManagedElement instance while the CsMgwFunction instance belongs to another ManagedElement instance. This Link behaviour is a non-attribute-specific behaviour. It is expected that this behaviour, like others, will be inherited.
+
+- c) An IOC relationship(s) with another IOC(s).
+- d) An IOC notification type(s) and their qualifications.
+- e) An IOC's relation with its parents (see Note 2). There are three mutually exclusive cases:
+  - 1) The IOC can have any parent. In UML diagram, the class has a parent *Any*.
+  - 2) The IOC is abstract and all of the possible parent(s) have been designated and whether subclass IOCs can be designated as a root IOC. In UML diagram, the class has zero or more possible parents of specific classes (except *Any*).
+  - 3) The IOC is concrete and all of the possible parent(s) have been designated and whether the IOC can be designated as a root IOC. In UML diagram, the class has one or more possible parents of specific classes (except *Any*).
+
+An IOC instance is either a root IOC or it has one and only one parent. Only 3GPP SA5 may designate an IOC class as a potential root IOC. Currently, only SubNetwork, ManagedElement or MeContext IOCs can be root IOCs.
+
+NOTE 2: The parent and child relation in this clause is the parent name-containing the child relation.
+
+- f) An IOC's relation with its children. There are three mutually exclusive cases:
+  - 1) An IOC shall not have any children (name-containment relation) IOCs. In UML diagram, the class has no child.
+  - 2) An IOC can have children IOC(s). The maximum number of instances per children IOC can be specified. An IOC may designate that vendor specific objects are not allowed as children IOCs. In UML diagram, the class has a child *Any*.
+  - 3) An IOC can only have the specific children IOC(s) (or their subclasses). The maximum number of instances per children IOC can be specified. An IOC may designate that vendor specific objects are not allowed as children IOCs. In UML diagram, the class has one or more children of specific classes (except *Any*).
+- g) Whether An IOC can be instantiated or not (i.e., whether An IOC is an abstract IOC).
+- h) An attribute for naming purpose.
+- i) An optional attribute for holding IOC name. An IOC name is unique among all 3GPP-defined IOCs and vendor-defined IOCs. An IOC name must be unambiguous.
+
+Editor's Note: No agreement on above point i) achieved yet. This is FFS.]
+
+---
+
+## G.2 Inheritance
+
+An IOC (the subclass) inherits from another IOC (the superclass) in that the subclass shall have all the properties of the superclass.
+
+The subclass can change the inherited support-qualification(s) from optional to mandatory but not vice versa. The subclass can change the inherited support-qualification from conditional-optional to conditional-mandatory but not vice versa.
+
+An IOC can be a superclass of many IOC(s). A subclass cannot have more than one superclass.
+
+The subclass can:
+
+- a) Add (compared to those of its superclass) unique attributes including their behaviour, legal value ranges and support-qualifications. Each additional attribute shall have its own unique attribute name (among all added and inherited attributes).
+- b) Add non-attribute behaviour on an IOC basis. This behaviour may not contradict inherited superclass behaviour.
+- c) Add relationship(s) with IOC(s). Each additional relationship shall have its own unique name (among all added and inherited relations).
+- d) Add additional notification types and their qualifications.
+- e) Designate all of the possible parent(s) (and their subclasses) if the superclass has Property-e-1 such that an IOC will have Property-e-2 or Property-e-3. Restrict possible parent(s) (and their subclasses) and/or remove the capability of the subclass from being a root IOC, if the superclass has Property-e-2 or Property-e-3.
+- f) Add children IOC(s) if the superclass has Property-f-2 such that an IOC will have Property-f-3. Restrict the allowed children IOC(s) (or their subclasses) if the superclass has Property-f-3.
+- g) Specify whether an IOC can be instantiated or not (i.e. the IOC is an abstract IOC).
+- h) Restrict the legal value range of a superclass attribute that has a legal value range.
+
+# --- Annex H (normative): Interface Properties and Inheritance
+
+## H.1 Property
+
+To be defined.
+
+## --- H.2 Inheritance
+
+To be defined.
+
+# --- Annex I (normative): Entity (Interface, IOC and Attribute) Import
+
+IRP specifications define entities(e.g., IOCs, interfaces and attribute). To facilitate re-use of entity definitions among IRP specifications, an import mechanism is used. When an IRP specification (the subject IRP specification) imports an entity defined in another IRP specification, the subject IRP specification is considered to have defined the imported entity in its specification. Furthermore, the subject IRP specification cannot change the properties of this imported entity. If it requires an entity that is not identical but similar to the imported entity, it should define a new entity that inherits the imported entity and introduce changes in the new entity definition.
+
+# Annex H (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                      |     |        |        |  |
+|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------------|-----|--------|--------|--|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                      | Cat | Old    | New    |  |
+| Mar 2006       | SP-31 | SP-060099 | 0006 | --  | Extension/Generalization of the IRP definition and concept (OAM7-NIM-NGN)                            | C   | 6.5.0  | 7.0.0  |  |
+| Dec 2006       | SP-34 | SP-060723 | 0007 | --  | Correct existing definitions of the IRPs and gather all IRP-related definitions                      | F   | 7.0.0  | 7.1.0  |  |
+| Jan 2007       | --    | --        | --   | --  | Editorial: added two returns in 3.1 Definitions                                                      | --  | 7.1.0  | 7.1.1  |  |
+| Mar 2007       | SP-35 | SP-070045 | 0008 | --  | Delete the incorrect reference                                                                       | F   | 7.1.1  | 7.2.0  |  |
+| Jun 2007       | SP-36 | SP-070309 | 0009 | --  | Identify the use case of XSD schema                                                                  | B   | 7.2.0  | 8.0.0  |  |
+| Jun 2007       | SP-36 | SP-070309 | 0010 | --  | Add IOC Property Inheritance and Import definitions                                                  | B   | 7.2.0  | 8.0.0  |  |
+| Mar 2008       | SP-39 | SP-080058 | 0012 | --  | Generalization of the IRP definition for NGN management - Align with 32.101 and TISPAN               | A   | 8.0.0  | 8.1.0  |  |
+| Jun 2008       | SP-40 | SP-080329 | 0013 | --  | Remove CMIP and add SOAP reference as supported technology for IRP Solution Sets - Align with 32.101 | F   | 8.1.0  | 8.2.0  |  |
+| Mar 2009       | SP-43 | SP-090207 | 0014 | --  | Remove parts moved to 32.153                                                                         | F   | 8.2.0  | 8.3.0  |  |
+| Dec 2009       | --    | --        | --   | --  | Update to Rel-9 version (MCC)                                                                        | -   | 8.3.0  | 9.0.0  |  |
+| Mar 2010       | SP-47 | SP-100035 | 0015 | --  | Introduce the use of ProxyClass Any to represent parent and child relation property of IOC           | F   | 9.0.0  | 9.1.0  |  |
+| Jun 2010       | SP-48 | SP-100264 | 0016 | --  | Move common definitions from TS 32.600 and clarify SS definition                                     | F   | 9.1.0  | 10.0.0 |  |
+| Sep 2010       | SP-49 | SP-100488 | 0017 | --  | Clarification on the meaning of the imported entities                                                | A   | 10.0.0 | 10.1.0 |  |
+| Mar 2011       | SP-51 | SP-110103 | 0019 | 1   | Reference updates related to IRP SS Improvements WID                                                 | D   | 10.1.0 | 10.2.0 |  |

marked/Rel-10/32_series/32151/raw.md

@@ -0,0 +1,705 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management;** 3GPP TS 32.151 V10.1.0 (2010-09) --- **Integration Reference Point (IRP) Information Service (IS) template (Release 10)**
+
+---
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'G'.
+
+3GPP logo
+
+Keywords  
+UMTS, management
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                           |    |
+|---------------------------------------------------------------------------|----|
+| Foreword .....                                                            | 5  |
+| Introduction .....                                                        | 5  |
+| 1 Scope.....                                                              | 6  |
+| 2 References.....                                                         | 6  |
+| 3 Definitions and abbreviations .....                                     | 7  |
+| 3.1 Definitions.....                                                      | 7  |
+| 3.2 Abbreviations .....                                                   | 7  |
+| 4 Information Service (IS) template.....                                  | 7  |
+| W1 Scope.....                                                             | 9  |
+| W2 Scope.....                                                             | 9  |
+| X Information Object Classes.....                                         | 9  |
+| X.1 Imported information entities and local labels.....                   | 9  |
+| X.2 Class diagram.....                                                    | 10 |
+| X.2.1 Attributes and relationships .....                                  | 10 |
+| X.2.2 Inheritance .....                                                   | 10 |
+| X.3 Information object class definitions.....                             | 11 |
+| X.3.a <code>InformationObjectClassName</code> .....                       | 11 |
+| X.3.a.1 Definition .....                                                  | 11 |
+| X.3.a.2 Attributes .....                                                  | 11 |
+| X.3.a.3 Attribute constraints.....                                        | 12 |
+| X.3.a.4 Relationships.....                                                | 12 |
+| X.3.a.5 State diagram .....                                               | 12 |
+| X.3.a.6 Notifications.....                                                | 13 |
+| X.4 Information relationship definitions.....                             | 14 |
+| X.4.a <code>InformationRelationshipName (supportQualifier)</code> .....   | 14 |
+| X.4.a.1 Definition .....                                                  | 14 |
+| X.4.a.2 Roles .....                                                       | 14 |
+| X.4.a.3 Constraints .....                                                 | 14 |
+| X.5 Information attribute definitions .....                               | 15 |
+| X.5.1 Definition and Legal Values.....                                    | 15 |
+| X.5.2 Constraints .....                                                   | 15 |
+| X.6 Common Notifications .....                                            | 15 |
+| X.7 System State Model.....                                               | 15 |
+| Y Interface Definition .....                                              | 16 |
+| Y.1 Class diagram representing interfaces.....                            | 16 |
+| Y.2 Generic rules .....                                                   | 16 |
+| Y.b <code>InterfaceName Interface (supportQualifier)</code> .....         | 16 |
+| Y.b.a Operation <code>OperationName (supportQualifier)</code> .....       | 17 |
+| Y.b.a.1 Definition .....                                                  | 17 |
+| Y.b.a.2 Input parameters .....                                            | 17 |
+| Y.b.a.3 Output parameters.....                                            | 17 |
+| Y.b.a.4 Pre-condition.....                                                | 19 |
+| Y.b.a.5 Post-condition .....                                              | 19 |
+| Y.b.a.6 Exceptions.....                                                   | 19 |
+| Y.b.a.6.c <code>exceptionName</code> .....                                | 20 |
+| Y.b.a.7 Constraints .....                                                 | 20 |
+| Y.b.a Notification <code>NotificationName (supportQualifier)</code> ..... | 21 |
+| Y.b.a.1 Definition .....                                                  | 21 |
+| Y.b.a.2 Input parameters .....                                            | 21 |
+| Y.b.a.3 Triggering event.....                                             | 21 |
+| Y.b.a.3.1 From state.....                                                 | 22 |
+| Y.b.a.3.2 To state .....                                                  | 22 |
+| Y.b.a.4 Constraints .....                                                 | 22 |
+
+Y.c Scenario................................................................................................................................................................ 22
+
+Annex A (informative): Change history................................................................................................................ 23
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.150: Integration Reference Point (IRP) Concept and definitions
+- TS 32.151: Integration Reference Point (IRP) Information Service (IS) template**
+- TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
+- TS 32.153: Integration Reference Point (IRP) technology specific templates
+- TS 32.154: Backward and Forward Compatibility (BFC); Concept and definitions
+- TS 32.155: Requirements template
+
+# --- 1 Scope
+
+The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series.
+
+# --- 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.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [4] 3GPP TS 32.152: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire".
+- [5] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service".
+- [7] 3GPP TS 32.302: "Telecommunication Management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [8] ITU-T Recommendation M.3020 (2009): Management interface specification methodology – Annex E Information type definitions – type repertoire.
+- [9] 3GPP TS 32.602: "Telecommunication Management; Configuration Management (CM): Basic CM IRP: Information Service (IS)".
+- [10] 3GPP TS 32.612: "Telecommunication Management; Configuration Management (CM): Bulk CM IRP: Information Service (IS)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+**IRP Agent:** See 3GPP TS 32.150 [3].
+
+**IRP Manager:** See 3GPP TS 32.150 [3].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+|     |                                  |
+|-----|----------------------------------|
+| IOC | Information Object Class         |
+| IRP | Integration Reference Point      |
+| IS  | Information Service              |
+| OMG | Object Management Group          |
+| UML | Unified Modelling Language (OMG) |
+
+# --- 4 Information Service (IS) template
+
+The present document contains the templates to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series.
+
+For the introductory clause 1 (Scope) of all NRM IRP ISs, clause W1 shall be used.
+
+For the introductory clause 1 (Scope) of all Interface IRP ISs, clause W2 shall be used.
+
+For the introductory clauses 2 and 3 of all IRP ISs, the text shall be written conforming to the standard 3GPP TS template (i.e. not this IRP IS template).
+
+The other clauses in this template that shall be used in the IS specifications following their introductory clauses are numbered starting with "X", which in general should correspond to clause 4 that is the beginning of the main part of the TS. However, if there is a need in a specific IS to introduce additional clauses in the body, X may correspond to a number higher than 4.
+
+For a NRM IRP IS, only clause X shall be used.
+
+For an Interface IRP IS, both clauses X and Y shall be used.
+
+The IS template uses qualifiers M, O, CM, CO and C. The semantics of these qualifiers are defined in TS 32.150 [3].
+
+The IS template uses Information Type as one characteristic to describe IOC attributes and operation/notification parameters. The valid Information Type(s) that can be used and their semantics are defined in ITU-T M.3020 Annex E [8].
+
+Usage of fonts shall be according to the following table.
+
+| Item                                                        | Font        |
+|-------------------------------------------------------------|-------------|
+| Class names                                                 | Courier New |
+| Attribute names                                             | Courier New |
+| Operation names                                             | Courier New |
+| Parameter names                                             | Courier New |
+| Assertion names                                             | Courier New |
+| Notification names                                          | Courier New |
+| Exception names                                             | Courier New |
+| State names                                                 | Arial       |
+| Matching Information                                        | Courier New |
+| Information Type                                            | Courier New |
+| Legal Values                                                | Courier New |
+| NOTE: These font requirements do not apply to UML diagrams. |             |
+
+## --- W1 Scope
+
+*The following quoted text is relevant for all NRM IRP ISs. It shall be copied as the first two paragraphs of the NRM IRP IS specification. IRP IS author may add additional paragraph(s) if necessary.*
+
+“
+
+The present document specifies the <<n>> (where <<n>> shall be substituted by the name of the NRM IRP IS concerned such as ‘HNS’, ‘E\_UTRAN’, ‘GERAN’) network resource information that can be communicated between an IRP Agent and one or several IRP Managers for network management purposes.
+
+This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
+
+“
+
+## --- W2 Scope
+
+*The following quoted text is relevant for all Interface IRP ISs. It shall be copied as the first two paragraphs of the Interface IRP IS specification. IRP IS author may add additional paragraph(s) if necessary.*
+
+“
+
+The present document specifies the <<n>> (where <<n>> shall be substituted by the name of the Interface IRP IS concerned such as “Alarm”, “Test”, “Entry Point”) management operations and notifications that can be communicated between an IRP Agent and one or several IRP Managers.
+
+This document specifies the semantics and behaviour of operations, notifications and their parameters visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
+
+“
+
+# --- X Information Object Classes
+
+*This “X” clause shall be used for NRM IRP ISs. This “X” clause shall also be used for Interface IRP ISs.*
+
+*“X” represents a clause number in the actual Information Service TS.*
+
+## X.1 Imported information entities and local labels
+
+*This clause identifies a list of information entities (e.g. information object class, interface, information relationship, information attribute) that have been defined in other specifications and that are imported in the present specification. All imported entities shall be treated as if it is defined locally in present specification. One usage of import is for inheritance purpose. Each element of this list is a pair (label reference, local label). The label reference contains the name of the specification where it is defined, the type of the information entity and its name. The local label of imported information entities can then be used throughout the specification instead of the label reference.*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Label reference                                   | Local label |
+|---------------------------------------------------|-------------|
+| 3GPP TS 32.622 [5], information object class, Top | Top         |
+
+## X.2 Class diagram
+
+### X.2.1 Attributes and relationships
+
+*This first set of diagrams represents all information object classes defined in this IS with all their relationships and all their attributes, including relationships with imported IOCs (if any). These diagrams shall contain information object class cardinalities (for associations as well as containment relationships) and may also contain association names and role names. These shall be UML compliant class diagrams (see also 3GPP TS 32.152 [4]).*
+
+*Characteristics (attributes, relationships) of imported information object classes need not to be repeated in the diagrams. Information object classes should be defined using the stereotype <<InformationObjectClass>>.*
+
+### X.2.2 Inheritance
+
+*This second set of diagrams represents the inheritance hierarchy of all information object classes defined in this IS. These diagrams do not need to contain the complete inheritance hierarchy but shall at least contain the parent information object classes of all information object classes defined in the present document. By default, an information object class inherits from the information object class "top". These shall be UML compliant class diagrams.*
+
+*Characteristics (attributes, relationships) of imported information object classes need not to be repeated in the diagrams. Information object classes should be defined using the stereotype <<InformationObjectClass>>.*
+
+*NOTE: some inheritance relationships presented in clause X.2.2 can be repeated in clause X.2.1 to enhance readability.*
+
+## X.3 Information object class definitions
+
+Each information object class is defined using the following structure.
+
+*Inherited items (attributes etc.) shall not be shown, as they are defined in the parent IOC(s) and thus valid for all subclasses.*
+
+### X.3.a InformationObjectClassName
+
+*InformationObjectClassName is the name of the information object class.*
+
+*"a" represents a number, starting at 1 and increasing by 1 with each new definition of an IOC.*
+
+#### X.3.a.1 Definition
+
+*The <definition> subclause is written in natural language. The <definition> subclause refers to the information object class itself. The characteristics related to the relationships that the object class can have with other object classes can't be found in the definition. The reader has to refer to relationships definition to find such kind of information. Information related to inheritance shall be precised here.*
+
+*For NRM IRP ISs, information on traceability back to one or more requirements supported by this IOC should also be defined here, in the following form:*
+
+| Referenced TS       | Requirement label | Comment                |
+|---------------------|-------------------|------------------------|
+| 3GPP TS 32.xyz [xy] | REQ-SM-CON-23     | Optional clarification |
+| 3GPP TS 32.xyz [xy] | REQ-SM-FUN-11     | Optional clarification |
+
+#### X.3.a.2 Attributes
+
+*The <attributes> subclause presents the list of attributes, which are the manageable properties of the object class. Each element is a tuple (attributeName, supportQualifier, readQualifier, writeQualifier):*
+
+- The supportQualifier indicates whether the attribute is Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), SS-Conditional (C) or Not supported (—).*
+- The readQualifier indicates whether the attribute shall be readable by the IRPManager. Allowed values are: Mandatory (M), Optional (O) and Not supported (—).*
+- The writeQualifier indicates whether the attribute shall be writeable by the IRPManager. Allowed values are: Mandatory (M), Optional (O) and Not supported (—).*
+
+*The semantics of the above used qualifiers are defined in TS 32.150 [3].*
+
+*There is a dependency relationship between the supportQualifier, readQualifier, and writeQualifier. The supportQualifier indicates the requirements for the support of the attribute. For any given attribute, regardless of the value of the supportQualifier, at least one of the readQualifier or writeQualifier must be "M". The implication of the "O" supportQualifier is that the attribute is optional, however the read and write qualifiers indicate how the optional attribute shall be supported, should the optional attribute be supported.*
+
+*Private or IRPAgent Internal attributes are per definition not readable by the IRPManager. Their readQualifier is hence always "—".*
+
+*Private or IRPAgent Internal attributes are per definition not writable by the IRPManager. Their writeQualifier is hence always "—".*
+
+*The readQualifier and writeQualifier of a supported attribute, that is public, may not be both "—".*
+
+*The use of "—" in supportQualifier is reserved for documenting support of attributes defined by an «Archetype» IOC. Attributes with a supportQualifier of "—" are not implemented by the IOC that is realizing a subset of the attributes defined by the «Archetype». The readQualifier and writeQualifier are of no relevance in this case. However, a not supported attribute is neither readable nor writable. For this reason the readQualifier and writeQualifier shall be "—" for unsupported attributes.*
+
+For any IOC that uses one or more attributes from an «Archetype», a separate table shall be used to indicate the supported attributes. This table is absent if no «Archetype» attributes are supported. For example, if a particular IOC has defined attributes (i.e. attributes not defined by an «Archetype») and encapsulates attributes from two «Archetype»s, then the totality of the attributes of said IOC will be contained in three separate tables.
+
+This information is provided in a table. An example of such a table is given below:
+
+| Attribute name    | Support Qualifier | Read Qualifier | Write Qualifier |
+|-------------------|-------------------|----------------|-----------------|
+| ntfSubscriptionId | M                 | M              | O               |
+
+Another example, where the support qualifier is "O" is given here below:
+
+| Attribute name    | Support Qualifier | Read Qualifier | Write Qualifier |
+|-------------------|-------------------|----------------|-----------------|
+| ntfSubscriptionId | O                 | M              | O               |
+
+In this example, the ntfSubscriptionId is an optional attribute. If the implementation chose to support ntfSubscriptionId, then the said implementation is required to support read and may support write.
+
+NOTE: This subclause shall state “There is no attribute defined.” when there is no attribute to define.
+
+#### X.3.a.3 Attribute constraints
+
+The <attribute constraints> subclause presents constraints for the attributes, and one use is to present the predicates for conditional qualifiers (CM/CO).
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Name                                   | Definition                                                                                                              |
+|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
+| pci CM write qualifier                 | Centralized PCI assignment (see TS 32.500, ref [15] subclause 6.1.6) is supported.                                      |
+| pciList CM support qualifier           | Distributed PCI assignment (see TS 32.500, ref [15] subclause 6.1.6) is supported.                                      |
+| partOfSectorPower CM support qualifier | The IOC SectorEquipmentFunction is used.                                                                                |
+| attributeX max value                   | The value of attributeX shall be within the specified value range but may never be higher than the value of attributeY. |
+
+NOTE: This subclause shall state “There is no attribute constraint defined.” when there is no attribute constraints to define.
+
+#### X.3.a.4 Relationships
+
+The <relationship> subclause presents the list of relationships in which this class is involved. Each element is a relationshipName.
+
+NOTE: This subclause shall state “There is no attribute constraint defined.” when there is no relationship represented in the class diagram in clause X.2.1.
+
+#### X.3.a.5 State diagram
+
+The <state diagram> subclause contains state diagrams. A state diagram of an information object class defines permitted states of this information object class and the transitions between those states. A state is expressed in terms of individual attribute values or a combination of attribute values or involvement in relationships of the information object class being defined. This shall be a UML compliant state diagram.
+
+NOTE: This subclause shall state “There is no State diagram defined.” when there is no State diagram defined.
+
+#### X.3.a.6 Notifications
+
+The <Notifications> subclause, for this IOC, presents:
+
+- a) *optionally, a reference to the common notifications defined in subclause X.6 as valid for this IOC, and*
+- b) *optionally, a list of notifications that shall be excluded from the list of common notifications (defined in subclause X.6) for this IOC (note: inherited notifications from the parent IOC(s) can not be excluded), and*
+- c) *optionally, a list of notifications applicable to this IOC, and which may or may not be defined in the common notifications in subclause X.6.*
+
+*The notifications identified in this subclause are notifications that can be emitted across the Itf-N, where the "object class" and "object instance" parameters of the notification header (see note 2) of these notifications identifies an instance of the IOC defined by the encapsulating subclause (i.e. clause X.3.a).*
+
+*The notifications identified in this subclause, may originate from implementation object(s) whose identifier is mapped in the implementation, to the object instance identifier used over the Itf-N. Hence the presence of notifications in this clause (i.e. clause X.3.a.6) does not imply nor identify those notifications as being originated from an instance of the IOC defined by the encapsulating subclause (i.e. clause X.3.a).*
+
+*The information related to option c) above is provided in a table. An example of such a table is given below:*
+
+| Name                               | Qualifier | Notes                 |
+|------------------------------------|-----------|-----------------------|
+| notifyCMSynchronizationRecommended | O         | Example notification. |
+
+*NOTE 1: This subclause shall state "There is no notification defined for this IOC" when there is no notification defined for the IOC.*
+
+*NOTE 2: The notification header is defined in the notification IRP Information service TS 32.302 [7].*
+
+*NOTE 3: The qualifier of a notification, specified in Notification Table, indicates if such notification can carry the instance DN in the notification. The qualifier of a notification, specified in an Interface IRP, indicates the Interface IRP support level regarding the emission of the subject notification.*
+
+*An IRPManager can receive notification-XYZ that carries DN of class-ABC instance if and only if:*
+
+- a) *The class-ABC Notification Table defines the notification-XYZ and*
+- b) *The class-ABC instance implementation supports this notification-XYZ and*
+- c) *An Interface IRP defines the notification-XYZ and*
+- d) *The Interface IRP implementation supports this notification-XYZ.*
+
+## X.4 Information relationship definitions
+
+*Each information relationship is defined using the following structure.*
+
+*Inherited relationships shall not be shown, as they are defined by the parent IOC(s) and thus valid for all subclasses.*
+
+### X.4.a InformationRelationshipName (supportQualifier)
+
+*InformationRelationshipName is the name of the information relationship followed by a qualifier indicating whether the relationship is Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C).*
+
+*"a" represents a number, starting at 1 and increasing by 1 with each new definition of an information relationship.*
+
+#### X.4.a.1 Definition
+
+*The <definition> subclause is written in natural language.*
+
+#### X.4.a.2 Roles
+
+*The <roles> subclause identifies the roles played in the relationship by object classes. Each element is a pair (roleName, roleDefinition).*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Name           | Definition                                       |
+|----------------|--------------------------------------------------|
+| isSubscribedBy | This role represents the one who has subscribed. |
+
+#### X.4.a.3 Constraints
+
+*The <constraints> subclause contains the list of properties specifying the semantic invariants that must be preserved on the relationship. Each element is a pair (propertyName, propertyDefinition). Those properties are always held to be true during the lifetime of the relationship and don't need to be repeated in pre or post conditions of operations or notifications.*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Name                                  | Definition                                                                                                                                                                 |
+|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| inv_notificationCategoriesAllDistinct | The notification categories contained in the ntfNotificationCategorySet attribute of NtfSubscription playing the role theNtfSubscription are all distinct from each other. |
+
+## X.5 Information attribute definitions
+
+*Each information attribute is defined using the following structure.*
+
+*Inherited attributes shall not be shown, as they are defined in the parent IOC(s) and thus valid for all subclasses.*
+
+### X.5.1 Definition and Legal Values
+
+*This subclause contains for each attribute being defined its Attribute Name, its Definition written in natural language, its Information Type (see [8]) and an optional list of Legal Values supported by the attribute.*
+
+*In the case where the Legal Values can be enumerated, each element is a pair (Legal Value Name, Legal Value Semantics), unless a Legal Value Semantics applies to several values in which case the Semantics is provided only once. When the Legal Values cannot be enumerated, the list of Legal Values is defined by a single definition.*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Attribute Name       | Definition                                          | Information Type / Legal Values                                                                            |
+|----------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+| ntfSubscriptionId    | It identifies uniquely a subscription               | INTEGER / --                                                                                               |
+| ntfSubscriptionState | It indicates the activation state of a subscription | ENUMERATED /<br>"suspended": the subscription is suspended.<br>"notSuspended": the subscription is active. |
+
+### X.5.2 Constraints
+
+*The <constraints> subclause indicates whether there are any constraints affecting attributes. Each constraint is defined by a pair (propertyName, propertyDefinition). PropertyDefinitions are expressed in natural language.*
+
+An example is given here below:
+
+| Name                 | Definition                                                  |
+|----------------------|-------------------------------------------------------------|
+| inv_TimerConstraints | The ntfTimeTickTimer is lower than or equal to ntfTimeTick. |
+
+## X.6 Common Notifications
+
+*This <Common Notifications> subclause presents a list of notifications that can be referred to by any IOC defined by this IRP specification. These notifications are only applicable to IOCs referring to this subclause in subclause “X.3.a.6”. This information is provided in a table. An example of such a table is given below:*
+
+| Name                       | Qualifier | Notes                       |
+|----------------------------|-----------|-----------------------------|
+| notifyAttributeValueChange | O         | Example common notification |
+| notifyObjectCreation       | O         | Example                     |
+| notifyObjectDeletion       | O         | Example                     |
+
+*NOTE: This clause does not need to be present when there are no common notifications.*
+
+## X.7 System State Model
+
+*Some configurations of information are special or complex enough to justify the usage of a state diagram to clarify them. A state diagram in this clause defines permitted states of the system and the transitions between those states. A state is expressed in terms of a combination of attribute values constraints or involvement in relationships of one or more information object classes.*
+
+# --- Y Interface Definition
+
+*This "Y" clause shall be used for Interface IRP ISs.*
+
+*"Y" represents a number, immediately following "X".*
+
+## Y.1 Class diagram representing interfaces
+
+*Each interface is defined in the diagram. This shall be a UML compliant class diagram (see also 3GPP TS 32.152 [4]).*
+
+*Interfaces are defined using a stereotype <<Interface>>. Each interface contains a set of either operations or notifications which are mandatory or either a single operation or a single notification which is optional. The support of an interface by an information object class is represented by a relationship between the 2 entities with a cardinality (1..1) if all the operations or notifications contained in the interface are mandatory, and (0..1) if the operation or notification contained in the interface is optional. On the class diagram, each operation and notification in an interface shall be qualified as "public" by the addition of a symbol "+" before each operation and notification.*
+
+## Y.2 Generic rules
+
+*The following rules are relevant for all ISs. They shall simply be copied as part of the specification.*
+
+*Rule 1: each operation with at least one input parameter supports a pre-condition valid\_input\_parameter which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception operation\_failed\_invalid\_input\_parameter which is raised when pre-condition valid\_input\_parameter is false. The exception has the same entry and exit state.*
+
+*Rule 2: Each operation with at least one optional input parameter supports a set of pre-conditions supported\_optional\_input\_parameter\_yyy where "yyy" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception operation\_failed\_unsupported\_optional\_input\_parameter\_yyy which is raised when (a) the pre-condition supported\_optional\_input\_parameter\_yyy is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.*
+
+*Rule 3: each operation shall support a generic exception operation\_failed\_internal\_problem which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.*
+
+## Y.b InterfaceName Interface (supportQualifier)
+
+*InterfaceName is the name of the interface followed by a qualifier indicating whether the interface is Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C).*
+
+*"b" represents a number, starting at 3 and increasing by 1 with each new definition of an interface.*
+
+*Each interface is defined by its name and by a sequence of operations or notifications.*
+
+*Interfaces related to operations shall be listed before the interfaces related to notifications.*
+
+*If the interface is related to operation(s), the following Y.b.a "Operation OperationName (supportQualifier)" shall be applied.*
+
+*If the interface is related to notification(s), the next Y.b.a "Notification NotificationName (supportQualifier)" below shall be applied.*
+
+### Y.b.a Operation OperationName (supportQualifier)
+
+*OperationName is the name of the operation followed by a qualifier indicating whether the operation is Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C).*
+
+*"a" represents a number, starting at 1 and increasing by 1 with each new definition of an operation.*
+
+#### Y.b.a.1 Definition
+
+*The <definition> subclause is written in natural language.*
+
+*Information on traceability back to one or more requirements supported by this operation should also be defined here, in the following form:*
+
+| Referenced TS       | Requirement label | Comment                       |
+|---------------------|-------------------|-------------------------------|
+| 3GPP TS 32.xyz [xy] | REQ-SM-CON-23     | <i>Optional clarification</i> |
+| 3GPP TS 32.xyz [xy] | REQ-SM-FUN-11     | <i>Optional clarification</i> |
+
+#### Y.b.a.2 Input parameters
+
+*List of input parameters of the operation. Each element is a tuple (Parameter Name, Support Qualifier, Information Type (see [8] and Note 1) and an optional list of Legal Values supported by the parameter, Comment). Legal Values for the Support Qualifier are: Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C).*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Parameter Name | Support Qualifier | Information Type / Legal Values | Comment                       |
+|----------------|-------------------|---------------------------------|-------------------------------|
+| eventIdList    | M                 | SET OF INTEGER / --             | One or more event identifiers |
+
+Note 1: Information Type qualifies the parameter of Parameter Name. In the case where the Legal Values can be enumerated, each element is a pair (Legal Value Name, Legal Value Semantics), unless a Legal Value Semantics applies to several values in which case the definition is provided only once. When the Legal Values cannot be enumerated, the list of Legal Values is defined by a single definition.
+
+#### Y.b.a.3 Output parameters
+
+*List of output parameters of the operation. Each element is a tuple (Parameter Name, Support Qualifier, Matching Information / Information Type (see [8]) (Note 1) and an optional list of Legal Values supported by the parameter, Comment). Legal Values for the Support Qualifier are: Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C).*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Parameter Name | Support Qualifier | Matching Information / Information Type / Legal Values  | Comment                                                                                                                                                                                                                                                                                                    |
+|----------------|-------------------|---------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| eventTime      | M                 | AlarmInformation.alarmRaisedTime / GeneralizedTime / -- | The parameter carries the <ul style="list-style-type: none"> <li>alarmRaisedTime in case notificationType carries notifyNewAlarm,</li> <li>alarmChangedTime in case notificationType carries notifyChangedAlarm,</li> <li>alarmClearedTime in case notificationType carries notifyClearedAlarm.</li> </ul> |
+
+Note 1: Information Type qualifies the parameter of Parameter Name. In the case where the Legal Values can be enumerated, each element is a pair (Legal Value Name, Legal Value Semantics), unless a Legal Value Semantics applies to several values in which case the definition is provided only once. When the Legal Values cannot be enumerated, the list of Legal Values is defined by a single definition.
+
+*This table shall also include a special parameter 'status' to indicate the completion status of the operation (success, partial success, failure reason etc.).*
+
+#### Y.b.a.4 Pre-condition
+
+*A pre-condition is a collection of assertions joined by AND, OR, and NOT logical operators. The pre-condition must be held to be true before the operation is invoked. An example is given here below:*
+
+```
+notificationCategoriesNotAllSubscribed OR
+  notificationCategoriesParameterAbsentAndNotAllSubscribed
+```
+
+Each assertion is defined by a pair (propertyName, propertyDefinition). All assertions constituting the pre-condition are provided in a table. An example of such a table is given here below:
+
+| Assertion Name                                           | Definition                                                                                                                                                                                                                                                                                                                            |
+|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| notificationCategoriesNotAllSubscribed                   | At least one notificationCategory identified in the notificationCategories input parameter is supported by IRPAGENT and is not a member of the ntfNotificationCategorySet attribute of an NtfSubscription which is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter. |
+| notificationCategoriesParameterAbsentAndNotAllSubscribed | The notificationCategories input parameter is absent and at least one notificationCategory supported by IRPAGENT is not a member of the ntfNotificationCategorySet attribute of an ntfSubscription which is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter.        |
+
+#### Y.b.a.5 Post-condition
+
+*A post-condition is a collection of assertions joined by AND, OR, and NOT logical operators. The post-condition must be held to be true after the completion of the operation. When nothing is said in a post-condition regarding an information entity, the assumption is that this information entity has not changed compared to what is stated in the pre-condition. An example is given here below:*
+
+```
+subscriptionDeleted OR allSubscriptionDeleted
+```
+
+Each assertion is defined by a pair (propertyName, propertyDefinition). All assertions constituting the post-condition are provided in a table. An example of such a table is given here below:
+
+| Assertion Name         | Definition                                                                                                                                                                                                                                                                                    |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionDeleted    | The ntfSubscription identified by subscriptionId input parameter is no more involved in a subscription relationship with the ntfSubscriber identified by the managerReference input parameter and has been deleted. If this ntfSubscriber has no more ntfSubscription, it is deleted as well. |
+| allSubscriptionDeleted | In the case subscriptionId input parameter was absent, the ntfSubscriber identified by the managerReference input parameter is no more involved in any subscription relationship and is deleted, the corresponding ntfSubscription have been deleted as well.                                 |
+
+#### Y.b.a.6 Exceptions
+
+*List of exceptions that can be raised by the operation. Each element is a tuple (exceptionName, condition, ReturnedInformation, exitState).*
+
+##### Y.b.a.6.c exceptionName
+
+*ExceptionName is the name of an exception.*
+
+*"c" represents a number, starting at 1 and increasing by 1 with each new definition of an exception.*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Exception Name                   | Definition                                                                                                                                                                                                                                                                     |
+|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ope_failed_existing_subscription | <b>Condition:</b> (notificationCategoriesNotAllSubscribed OR notificationCategoriesParameterAbsentAndNotAllSubscribed) not verified.<br><b>Returned information:</b> output parameter status is set to OperationFailedExistingSubscription.<br><b>Exit state:</b> Entry State. |
+
+*Each notification is defined using the following structure.*
+
+#### Y.b.a.7 Constraints
+
+*The < constraints> subclause presents constraints for the operation or its parameters.*
+
+NOTE: This subclause does not need to be present when there are no constraints to define.
+
+### Y.b.a Notification NotificationName (supportQualifier)
+
+*NotificationName is the name of the notification followed by a qualifier indicating whether the notification is Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO) or SS-Conditional (C).*
+
+*"a" represents a number, starting at 1 and increasing by 1 with each new definition of a notification.*
+
+#### Y.b.a.1 Definition
+
+*The <definition> subclause is written in natural language.*
+
+*Information on traceability back to one or more requirements supported by this notification should also be defined here, in the following form:*
+
+| Referenced TS       | Requirement label | Comment                       |
+|---------------------|-------------------|-------------------------------|
+| 3GPP TS 32.xyz [xy] | REQ-SM-CON-23     | <i>Optional clarification</i> |
+| 3GPP TS 32.xyz [xy] | REQ-SM-FUN-11     | <i>Optional clarification</i> |
+
+#### Y.b.a.2 Input parameters
+
+*List of input parameters of the notification. Each element is a tuple (Parameter Name, Qualifiers, Matching Information / Information Type (see [8]) (Note 1) and an optional list of Legal Values supported by the parameter, Comment).*
+
+*The column "Qualifiers" contains the two qualifiers, Support Qualifier and Filtering Qualifier, separated by a comma. The Support Qualifier indicates whether the attribute is Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C). The Filtering Qualifier indicates whether the parameter of the notification can be filtered or not. Values are Yes (Y) or No (N).*
+
+This information is provided in a table. An example of such a table is given here below:
+
+| Parameter Name   | Qualifiers | Matching Information / Information Type / Legal Values                                                                                                                                                                                                                                                                                                     | Comment                                                                        |
+|------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| managerReference | M,Y        | ntfSubscriber.ntfManagerReference / STRING / --                                                                                                                                                                                                                                                                                                            | It specifies the reference of IRPManager to which notifications shall be sent. |
+| alarmType        | M,Y        | AlarmInformation.eventType / ENUMERATED /<br>"Communications Alarm": a communication error alarm.<br>"Processing Error Alarm": a processing error alarm.<br>"Environmental Alarm": an environmental violation alarm.<br>"Quality Of Service Alarm": a quality of service violation alarm.<br>"Equipment Alarm": an alarm related to equipment malfunction. |                                                                                |
+
+Note 1: Information Type qualifies the parameter of Parameter Name. In the case where the Legal Values can be enumerated, each element is a pair (Legal Value Name, Legal Value Semantics), unless a Legal Value Semantics applies to several values in which case the definition is provided only once. When the Legal Values cannot be enumerated, the list of Legal Values is defined by a single definition.
+
+#### Y.b.a.3 Triggering event
+
+*The triggering event for the notification to be sent is the transition from the information state defined by the "from state" subclause to the information state defined by the "to state" subclause.*
+
+##### Y.b.a.3.1 From state
+
+*This subclause is a collection of assertions joined by AND, OR, and NOT logical operators. An example is given here below:*
+
+*alarmMatched AND alarmInformationNotCleared*
+
+*Each assertion is defined by a pair (propertyName, propertyDefinition). All assertions constituting the state "from state" are provided in a table. An example of such a table is given here below:*
+
+| Assertion Name             | Definition                                                                                                                                                     |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| alarmMatched               | The matching-criteria-attributes of the newly generated network alarm has values that are identical (matches) with ones in one AlarmInformation in AlarmList.. |
+| alarmInformationNotCleared | The perceivedSeverity of the newly generated network alarm is not Cleared.                                                                                     |
+
+##### Y.b.a.3.2 To state
+
+*This subclause is a collection of assertions joined by AND, OR and NOT logical operators. When nothing is said in a to-state regarding an information entity, the assumption is that this information entity has not changed compared to what is stated in the from state. An example is given here below:*
+
+*resetAcknowledgementInformation AND perceivedSeverityUpdated*
+
+*Each assertion is defined by a pair (propertyName, propertyDefinition). All assertions constituting the state "to state" are provided in a table. An example of such a table is given here below:*
+
+| Assertion Name                  | Definition                                                                                                                                                                                                                                              |
+|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| resetAcknowledgementInformation | The matched AlarmInformation identified in inv_alarmMatched in pre-condition has been updated according to the following rule:<br>ackTime, ackUserId and ackSystemId are updated to contain no information;<br>ackState is updated to "unacknowledged". |
+| perceivedSeverityUpdated        | The perceivedSeverity attribute of matched AlarmInformation identified in inv_alarmMatched in pre-condition has been updated.                                                                                                                           |
+
+#### Y.b.a.4 Constraints
+
+*The < constraints> subclause presents constraints for the notification or its parameters.*
+
+NOTE: This subclause does not need to be present when there are no constraints to define.
+
+## Y.c Scenario
+
+*This subclause contains one or more sequence diagrams, each describing a possible scenario. These shall be UML compliant sequence diagrams. This is an optional subclause.*
+
+# Annex A (informative): Change history
+
+| Change history |           |               |          |     |                                                                            |         |        |        |
+|----------------|-----------|---------------|----------|-----|----------------------------------------------------------------------------|---------|--------|--------|
+| Date           | TSG #     | TSG Doc.      | CR       | Rev | Subject/Comment                                                            | Ca<br>t | Old    | New    |
+| Sep 2006       | SA_3<br>3 | SP-<br>060548 | 000<br>4 | --  | Update of 32.151 to use a MCC supported font                               | F       | 6.3.0  | 7.0.0  |
+| Dec 2006       | SA_3<br>4 | SP-<br>060724 | 000<br>5 | --  | Correct the clause numbering instructions for Operations and Notifications | F       | 7.0.0  | 7.1.0  |
+| Mar 2007       | SA_3<br>5 | SP-<br>070045 | 000<br>6 | --  | Suppress inherited items                                                   | F       | 7.1.0  | 7.2.0  |
+| Mar 2007       | SA_3<br>5 | SP-<br>070045 | 000<br>7 | --  | Improve specification of Common notifications                              | F       | 7.1.0  | 7.2.0  |
+| Mar 2007       | SA_3<br>5 | SP-<br>070045 | 000<br>8 | --  | Correct the references of IRP Agent and IRP Manager                        | F       | 7.1.0  | 7.2.0  |
+| Sep 2007       | SA_3<br>7 | SP-<br>070610 | 000<br>9 | --  | Correct open issues in the IS template                                     | F       | 7.2.0  | 8.0.0  |
+| Sep 2007       | SA_3<br>7 | SP-<br>070610 | 001<br>0 | --  | Add missing instructions for Interface IRP ISs                             | F       | 7.2.0  | 8.0.0  |
+| Sep 2007       | SA_3<br>7 | SP-<br>070614 | 001<br>1 | --  | Remove visibility qualifier usage                                          | C       | 7.2.0  | 8.0.0  |
+| Jun 2008       | SA_4<br>0 | SP-<br>080329 | 001<br>2 | --  | Introduction of traceability in the IS template                            | C       | 8.0.0  | 8.1.0  |
+| Mar 2009       | SA_4<br>3 | SP-<br>090207 | 001<br>3 | --  | Correct subclause numbering                                                | F       | 8.1.0  | 8.2.0  |
+| Mar 2009       | --        | --            | --       | --  | Editorial modifications                                                    | --      | 8.2.0  | 8.2.1  |
+| Jun 2009       | SA_4<br>4 | SP-<br>090290 | 001<br>4 | --  | Introduce Information Type in IS template                                  | C       | 8.2.1  | 9.0.0  |
+| Sep 2009       | SA_4<br>5 | SP-<br>090627 | 001<br>5 | --  | Introduce Information Type in IS template                                  | D       | 9.0.0  | 9.1.0  |
+| Dec 2009       | SA-46     | SP-<br>090719 | 001<br>6 | --  | Add template text for Scope section for all IRP IS                         | F       | 9.1.0  | 9.2.0  |
+| Mar 2010       | SA-47     | SP-<br>100035 | 001<br>7 | --  | Clarify support qualifier usage in Notification Table in 32.151            | F       | 9.2.0  | 9.3.0  |
+| Mar 2010       | SA-47     | SP-<br>100036 | 001<br>8 | --  | Clarify Attribute constraints                                              | C       | 9.3.0  | 10.0.0 |
+| Mar 2010       | SA-47     | SP-<br>100036 | 001<br>9 | --  | Correct the pseudo subclause numbering                                     | F       | 9.3.0  | 10.0.0 |
+| Sep 2010       | SA-49     | SP-<br>100488 | 008<br>2 | --  | Clarification on the meaning of the imported entities                      | A       | 10.0.0 | 10.1.0 |

marked/Rel-10/32_series/32152/raw.md

@@ -0,0 +1,1024 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire (Release 10)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in bold lowercase letters with a red signal icon above the "e", and the word "ADVANCED" in smaller uppercase letters to the right. A trademark symbol (TM) is at the bottom right.
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The 3GPP logo, consisting of the letters "3GPP" in a stylized font with a red signal icon below the "P", and the text "A GLOBAL INITIATIVE" in smaller uppercase letters below the logo. A trademark symbol (TM) is at the bottom right of the logo.
+
+3GPP logo
+
+Keywords  
+UMTS, management
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                           |           |
+|-----------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                            | 5         |
+| Introduction .....                                                                                        | 5         |
+| 1 Scope.....                                                                                              | 6         |
+| 2 References.....                                                                                         | 6         |
+| 3 Definitions and abbreviations .....                                                                     | 7         |
+| 3.1 Definitions.....                                                                                      | 7         |
+| 3.2 Abbreviations .....                                                                                   | 7         |
+| 4 Requirements .....                                                                                      | 7         |
+| 5 Model Elements and Notations.....                                                                       | 8         |
+| 5.1 Basic model elements.....                                                                             | 8         |
+| 5.1.1 attribute.....                                                                                      | 8         |
+| 5.1.2 aggregation .....                                                                                   | 8         |
+| 5.1.3 operation.....                                                                                      | 8         |
+| 5.1.4 association and association name .....                                                              | 8         |
+| 5.1.5 realization relationship .....                                                                      | 9         |
+| 5.1.6 generalization relationship.....                                                                    | 9         |
+| 5.1.7 dependency relationship .....                                                                       | 9         |
+| 5.1.8 note .....                                                                                          | 10        |
+| 5.1.9 multiplicity, a.k.a. cardinality.....                                                               | 10        |
+| 5.1.10 rolename .....                                                                                     | 10        |
+| 5.1.11 Xor constraint.....                                                                                | 10        |
+| 5.2 Stereotype.....                                                                                       | 11        |
+| 5.2.1 <<Interface>> .....                                                                                 | 11        |
+| 5.2.1.1 Sample .....                                                                                      | 12        |
+| 5.2.2 Void .....                                                                                          | 12        |
+| 5.2.3 <<ProxyClass>>.....                                                                                 | 12        |
+| 5.2.3.1 Sample .....                                                                                      | 12        |
+| 5.2.4 <<Archetype>> .....                                                                                 | 12        |
+| 5.2.4.1 Sample .....                                                                                      | 13        |
+| 5.2.5 <<InformationObjectClass>>.....                                                                     | 13        |
+| 5.2.5.1 Sample .....                                                                                      | 13        |
+| 5.2.6 <<use>> and <<may use>>.....                                                                        | 13        |
+| 5.2.6.1 Sample for target <<Interface>> .....                                                             | 14        |
+| 5.2.6.2 Sample for target <<Notification>> .....                                                          | 14        |
+| 5.2.7 <<may realize>>.....                                                                                | 15        |
+| 5.2.7.1 Sample .....                                                                                      | 15        |
+| 5.2.8 Void .....                                                                                          | 15        |
+| 5.2.9 <<names>> .....                                                                                     | 15        |
+| 5.2.9.1 Sample .....                                                                                      | 16        |
+| 5.2.10 <<opt>> .....                                                                                      | 16        |
+| 5.2.10.1 Sample .....                                                                                     | 16        |
+| 5.2.11 <<Notification>>.....                                                                              | 16        |
+| 5.2.11.1 Sample .....                                                                                     | 16        |
+| 5.2.12 <<agent-internal-usage>> .....                                                                     | 17        |
+| 5.2.12.1 Sample .....                                                                                     | 17        |
+| 5.2.13 <<SupportIOC>>.....                                                                                | 17        |
+| 5.2.13.1 Sample .....                                                                                     | 17        |
+| 5.3 Void.....                                                                                             | 18        |
+| 5.4 Association classes.....                                                                              | 18        |
+| 5.4 Association classes.....                                                                              | 19        |
+| 5.5 Abstract Class.....                                                                                   | 20        |
+| 5.5.1 Sample .....                                                                                        | 20        |
+| <b>Annex A (informative): Samples of using &lt;&lt;ProxyClass&gt;&gt; to model Link related IOCs.....</b> | <b>21</b> |
+
+A.1 First Sample ..... 21
+
+A.2 Second Sample..... 22
+
+X.Y.1 AsFunction ..... 22
+
+X.Y.1.1 Definition ..... 22
+
+**Annex B (normative): Application of <<InformationObjectClass>> and <SupportIOC>> ..... 23**
+
+Annex C (informative): Change history..... 24
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+TS 32.150: Integration Reference Point (IRP) Concept and definitions
+
+TS 32.151: Integration Reference Point (IRP) Information Service (IS) template
+
+**TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire**
+
+TS 32.153 Integration Reference Point (IRP) technology specific templates
+
+TS 32.154 Backward and Forward Compatibility (BFC); Concept and definitions
+
+TS 32.155 Requirements template
+
+# --- 1 Scope
+
+3GPP has chosen UML to capture systems behaviour in the IRP IS context.
+
+UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
+
+The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
+
+IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.
+
+# --- 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.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [4] 3GPP TS 32.151: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template".
+- [5] OMG: "Unified Modelling Language Specification, Version 1.5".  
+<http://www.omg.org/spec/UML/1.5/>
+- [6] 3GPP TS 32.602 "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
+- [7] 3GPP TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)".
+- [8] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [9] 3GPP TS 32.404: "Telecommunication management; Performance Management (PM); Performance measurements - Definitions and template".
+- [10] 3GPP TS 32.300: "Name convention for Managed Objects".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+**Distinguished Name:** See 3GPP TS 32.300 [10].
+
+**IRP Agent:** See 3GPP TS 32.150 [3].
+
+**IRP Manager:** See 3GPP TS 32.150 [3].
+
+**Naming attribute:** See 3GPP TS 32.300 [10].
+
+**Notification:** See 3GPP TS 32.302 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+|       |                                  |
+|-------|----------------------------------|
+| CM    | Configuration Management         |
+| DN    | Distinguished Name               |
+| GERAN | GSM/EDGE Radio Access Network    |
+| IRP   | Integration Reference Point      |
+| IS    | Information Service              |
+| NRM   | Network Resource Model           |
+| OMG   | Object Management Group          |
+| UML   | Unified Modelling Language (OMG) |
+
+# --- 4 Requirements
+
+IRP Agent can be characterized by several different but related models. The models can be exterior or interior to the IRP Agent. Exterior models are use case models and interior models are object models.
+
+Current version of this TS focuses on the interior model aspects of IRP Agents.
+
+The notation elements captured in this repertoire shall be used to model all aspects of NRM IRP IS (such as GERAN NRM IRP: IS) and (interface) IRP (such as Alarm IRP: IS).
+
+All quotes are from [5].
+
+Capitalized words are defined by various 3GPP IRP IS specifications or the reference [5].
+
+# 5 Model Elements and Notations
+
+## 5.1 Basic model elements
+
+UML defined a number of basic model elements. This subclause lists the selected subset for use in the repertoire. The semantics of the selected ones are defined in [5].
+
+### 5.1.1 attribute
+
+See subclause 3.25 of [5].
+
+This sample shows some attributes, listed as strings in the attribute compartment of the class `AlarmInformation`.
+
+![UML class diagram for AlarmInformation](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+A UML class diagram for `AlarmInformation`. The class is shown as a yellow rectangle with a red border. The top compartment contains the stereotype `<<SupportIOC>>` and the class name `AlarmInformation`. The second compartment lists the attributes: `alarmId`, `notificationId`, `clearUserId`, and `other attributes ...`. The third compartment is empty.
+
+UML class diagram for AlarmInformation
+
+### 5.1.2 aggregation
+
+See subclause 3.43.2.5 of [5].
+
+This sample shows a hollow diamond attached to the end of a path to indicate aggregation. The diamond is attached to the class that is the aggregate.
+
+![UML diagram showing aggregation between ManagedElement and MscFunction](740442c999390734911677f01af0316d_img.jpg)
+
+A UML diagram showing an aggregation relationship between two classes. On the left is a class box for `ManagedElement` (stereotype `<<InformationObjectClass>>`). On the right is a class box for `MscFunction` (stereotype `<<InformationObjectClass>>`). A horizontal line connects the two boxes. At the `ManagedElement` end of the line is a hollow diamond, indicating that `ManagedElement` is the aggregate.
+
+UML diagram showing aggregation between ManagedElement and MscFunction
+
+### 5.1.3 operation
+
+See subclause 3.26 of [5].
+
+This sample shows two operations, shown as strings in the operation compartment of class `NotificationIRPManagement`, that the instance of `NotificationIRPManagement` may be requested to perform. The operation has a name, e.g. `subscribe` and a list of arguments (not shown).
+
+![UML class diagram for NotificationIRPManagement interface](6f119d066b5e51370df585ce69c94fb4_img.jpg)
+
+A UML class diagram for the `NotificationIRPManagement` interface. The class is shown as a yellow rectangle with a red border. The top compartment contains the stereotype `<< Interface>>` and the class name `NotificationIRPManagement`. The second compartment lists the operations: `subscribe()` and `unsubscribe()`.
+
+UML class diagram for NotificationIRPManagement interface
+
+### 5.1.4 association and association name
+
+See subclause 3.41 of [5].
+
+These two samples show a binary association between exactly two model elements. The association can include the possibility of relating a model element to itself. The first sample shows a bi-directional association in that each model element is aware of the other. The second sample shows a unidirectional association (shown with an open arrow at the target model element end) in that only the source model element is aware of the target model element and not vice-versa.
+
+Association can be named, such as *abcd* and *label6* in the following samples.
+
+![UML diagrams showing associations between InformationObjectClass elements.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+```
+
+    classDiagram
+        class YClass["<<InformationObjectClass>>\nYClass"]
+        class XClass["<<InformationObjectClass>>\nXClass"]
+        YClass -- XClass : abcd
+
+        class AClass["<<InformationObjectClass>>\nAClass"]
+        class BClass["<<InformationObjectClass>>\nBClass"]
+        AClass --> BClass : label6
+    
+```
+
+Two UML diagrams illustrating associations. The first shows a non-directional association between `<<InformationObjectClass>> YClass` and `<<InformationObjectClass>> XClass` labeled "abcd". The second shows a directed association from `<<InformationObjectClass>> AClass` to `<<InformationObjectClass>> BClass` labeled "label6".
+
+UML diagrams showing associations between InformationObjectClass elements.
+
+### 5.1.5 realization relationship
+
+See subclause 2.5.2.1 of [5].
+
+This sample shows the realization relationship between a source model element, `AlarmIRP`, and a target model element, `AlarmIRPOperations_1`. The source model element implements the target model element. The target model element needs to be an `<<Interface>>`.
+
+![UML diagram showing a realization relationship between AlarmIRP and AlarmIRPOperations_1.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+```
+
+    classDiagram
+        class AlarmIRP["<<SupportIOC>>\nAlarmIRP"]
+        class AlarmIRPOperations_1["<<Interface>>\nAlarmIRPOperations_1"]
+        AlarmIRPOperations_1 : +getAlarmList()
+        AlarmIRPOperations_1 : +acknowledgeAlarms()
+        AlarmIRP ..|> AlarmIRPOperations_1
+    
+```
+
+A UML diagram illustrating a realization relationship. The source element `<<SupportIOC>> AlarmIRP` realizes the target interface `<<Interface>> AlarmIRPOperations_1`, which contains methods `getAlarmList()` and `acknowledgeAlarms()`. The relationship is shown with a solid line and a large open triangular arrowhead pointing to the interface.
+
+UML diagram showing a realization relationship between AlarmIRP and AlarmIRPOperations\_1.
+
+### 5.1.6 generalization relationship
+
+See subclause 3.50 of [5].
+
+This sample shows a generalization relationship between a more general element (the `IRPAgent`) and a more specific element (the `IRPAgent_vendor_A`) that is fully consistent with the first element and that adds additional information.
+
+![UML diagram showing a generalization relationship between IRPAgent and IRPAgent_vendor_A.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg)
+
+```
+
+    classDiagram
+        class IRPAgent["<<InformationObjectClass>>\nIRPAgent"]
+        class IRPAgent_vendor_A["<<InformationObjectClass>>\nIRPAgent_vendor_A"]
+        IRPAgent_vendor_A --|> IRPAgent
+    
+```
+
+A UML diagram illustrating a generalization relationship. The specific element `<<InformationObjectClass>> IRPAgent_vendor_A` inherits from the general element `<<InformationObjectClass>> IRPAgent`. The relationship is shown with a solid line and a large open triangular arrowhead pointing to the general class.
+
+UML diagram showing a generalization relationship between IRPAgent and IRPAgent\_vendor\_A.
+
+### 5.1.7 dependency relationship
+
+See subclause 3.51 of [5].
+
+This sample shows that `BClass` instances have a semantic relationship with `AClass` instances. It indicates a situation in which a change to the target element will require a change to the source element in the dependency.
+
+![UML diagram showing a dependency relationship between AClass and BClass.](9283a3f6b39120df9dc9aee4712b3a0a_img.jpg)
+
+```
+
+    classDiagram
+        class AClass["<<InformationObjectClass>>\nAClass"]
+        class BClass["<<InformationObjectClass>>\nBClass"]
+        BClass ..> AClass
+    
+```
+
+A UML diagram illustrating a dependency relationship. The source element `<<InformationObjectClass>> BClass` depends on the target element `<<InformationObjectClass>> AClass`. The relationship is shown with a dashed line and an open arrowhead pointing to the target class.
+
+UML diagram showing a dependency relationship between AClass and BClass.
+
+### 5.1.8 note
+
+See subclause 3.11 of [5].
+
+This sample shows a note, as a rectangle with a "bent corner" in the upper right corner. The note contains arbitrary text. It appears on a particular diagram and may be attached to zero or more modelling elements by dashed lines.
+
+![Diagram showing a note attached to an Information Object Class box.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+A diagram showing a yellow box labeled "<<InformationObjectClass>> SubNetwork". To its right, a note box with a folded top-right corner contains the text "This is a sample of a note." A line connects the right side of the class box to the note box.
+
+Diagram showing a note attached to an Information Object Class box.
+
+### 5.1.9 multiplicity, a.k.a. cardinality
+
+See subclause 3.44 of [5].
+
+This sample shows a multiplicity attached to the end of an association path. The meaning of this multiplicity is that one to many. Network instance(s) is associated with zero, one or more SubNetwork instances.
+
+In Release 7 and earlier versions, the cardinality zero can indicate that the IOC has the so-called “transient state” characteristic. For example, it indicates that the instance is not yet created but it is in the process of being created. In Release 8 and onwards, the cardinality zero will not be used to indicate this characteristic since such characteristic is considered inherent in all IOCs. In Release 8 and onwards, all IOCs defined are considered to have such inherent “transient state” characteristics.
+
+![Diagram showing a Network class associated with a SubNetwork class with a 0..* multiplicity.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+A diagram showing two yellow boxes. The left box is labeled "<<InformationObjectClass>> Network" and the right box is labeled "<<InformationObjectClass>> SubNetwork". A horizontal line with an arrow points from the Network box to the SubNetwork box. Near the arrowhead, the multiplicity "0..\*" is displayed.
+
+Diagram showing a Network class associated with a SubNetwork class with a 0..\* multiplicity.
+
+### 5.1.10 rolename
+
+See subclause 3.43.2.6 of [5].
+
+This sample shows a Person (say instance John) is associated with a Company (say whose DN is “Company=XYZ”). We navigate the association by using the opposite association-end such that John’s Person.theCompany would hold the DN, i.e."Company=XYZ". Use noun for the rolename.
+
+![Diagram showing a Person class associated with a Company class with the rolename +theCompany.](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg)
+
+A diagram showing two yellow boxes. The left box is labeled "<<InformationObjectClass>> Company" and the right box is labeled "<<InformationObjectClass>> Person". A horizontal line with an arrow points from the Person box to the Company box. Near the arrowhead, the rolename "+theCompany" is displayed.
+
+Diagram showing a Person class associated with a Company class with the rolename +theCompany.
+
+### 5.1.11 Xor constraint
+
+See subclause 2.5.2.3 and 3.42.5.1 of [5].
+
+This sample shows an Account (e.g. account 0960) that is associated with a Person (e.g. John Smith) or a Corporation (e.g. ABC Inc).
+
+![UML Class Diagram showing Account as a base class for Person and Corporation with an {xor} constraint.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+classDiagram
+    class Account {
+        <<InformationObjectClass>>
+    }
+    class Person {
+        <<InformationObjectClass>>
+    }
+    class Corporation {
+        <<InformationObjectClass>>
+    }
+    Account <|-- Person : {xor}
+    Account <|-- Corporation : {xor}
+  
+```
+
+UML Class Diagram showing Account as a base class for Person and Corporation with an {xor} constraint.
+
+## 5.2 Stereotype
+
+This subclause lists all allowable stereotypes to be used in IRP IS specifications. One stereotype <<Interface>> is defined in [5]. This document lists it out for ease of reference and completeness. Other stereotypes are defined in this document.
+
+**Table: Stereotypes**
+
+| Stereotype             | Base Class                             | Affected Metamodel Elements |
+|------------------------|----------------------------------------|-----------------------------|
+| Interface              | Class                                  |                             |
+| ProxyClass             | Class                                  |                             |
+| Notification           | Class                                  |                             |
+| Archetype              | Classifier (subclause 2.5.2.10 of [5]) |                             |
+| InformationObjectClass | Classifier                             |                             |
+| SupportIOC             | Classifier                             |                             |
+| agent-internal-usage   | Association                            |                             |
+| use                    | Association                            |                             |
+| may use                | Association                            |                             |
+| may realize            | Association                            |                             |
+| names                  | Composition                            | --                          |
+
+### 5.2.1 <<Interface>>
+
+Subclause 2.5.2.25 of [5]:
+
+"An interface is a named set of operations that characterize the behaviour of an element. In the metamodel, an Interface contains a set of Operations that together define a service offered by a Classifier realizing the Interface. A Classifier may offer several services, which means that it may realize several Interfaces, and several Classifiers may realize the same Interface.
+
+Interfaces may not have Attributes, Associations, or Methods. An Interface may participate in an Association provided the Interface cannot see the Association; that is, a Classifier (other than an Interface) may have an Association to an Interface that is navigable from the Classifier but not from the Interface."
+
+Subclause 2.5.4.6 of [5]: "The purpose of an interface is to collect a set of operations that constitute a coherent service offered by classifiers. Interfaces provided a way to partition and characterize groups of operations. An interface is only a collection of operations with a name. It cannot be directly instantiated. Instantiable classifiers, such as class or use case, may use interfaces for specifying different services offered by their instances. Several classifiers may realize the same interface. All of them must contain at least the operations matching those contained in the interface. The specification of an operation contains the signature of the operation (i.e. its name, the types of the parameters and the return type). An interface does not imply any internal structure of the realizing classifier. For example, it does not include which algorithm to use for realizing an operation."
+
+An operation may, however, include a specification of the effects [e.g. with pre and post-conditions] of its invocation.
+
+#### 5.2.1.1 Sample
+
+This sample shows an AlarmIRPOperations\_1 <<Interface>> that has two operations. The input and output parameters of the operations are hidden (i.e. not shown). The AlarmIRP has a unidirectional mandatory realization relationship with the <<Interface>>.
+
+![UML diagram showing the <<Interface>> Notation. A class box labeled <<SupportIOC>> AlarmIRP is connected by a solid line with an open triangle arrowhead to an interface box labeled <<Interface>> AlarmIRPOperations_1. The interface box contains two methods: getAlarmList() and acknowledgeAlarms().](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+
+classDiagram
+    class AlarmIRP {
+        <<SupportIOC>>
+    }
+    class AlarmIRPOperations_1 {
+        <<Interface>>
+        getAlarmList()
+        acknowledgeAlarms()
+    }
+    AlarmIRP --|> AlarmIRPOperations_1
+  
+```
+
+UML diagram showing the <> Notation. A class box labeled <> AlarmIRP is connected by a solid line with an open triangle arrowhead to an interface box labeled <> AlarmIRPOperations\_1. The interface box contains two methods: getAlarmList() and acknowledgeAlarms().
+
+**<<Interface>> Notation**
+
+### 5.2.2 Void
+
+### 5.2.3 <<ProxyClass>>
+
+It is a form or template representing a number of <<InformationObjectClass>>. It encapsulates attributes, links, methods (or operations), and interactions that are present in the represented <<InformationObjectClass>>.
+
+The semantics of a <<ProxyClass>> is that all behaviour of the <<ProxyClass>> is present in the represented <<InformationObjectClass>>. Since this class is simply a representation of other classes, this class cannot define its own behaviour other than those already defined by the represented <<InformationObjectClass>>.
+
+A particular <<InformationObjectClass>> can be represented by zero, one or more <<ProxyClass>> or <<Archetype>>. For example, the ManagedElement <<InformationObjectClass>> can have MonitoredEntity <<ProxyClass>> and ManagedEntity <<ProxyClass>>.
+
+The attributes of the <<ProxyClass>> are accessible by the source entity that has an association with the <<ProxyClass>>.
+
+#### 5.2.3.1 Sample
+
+This shows a <<ProxyClass>> named MonitoredEntity. It represents all NRM <<InformationObjectClass>> (e.g. GgsnFunction <<InformationObjectClass>>) whose instances are being monitored for alarm conditions.
+
+Note that <<MonitoredEntity>> does not define any attribute. The attributes are already defined by all NRM <<InformationObjectClass>>.
+
+![UML diagram showing the <<ProxyClass>> Notation. A class box labeled <<ProxyClass>> MonitoredEntity is connected by a solid line to a callout box containing the text: 'It represents all NRM IOCs that can have alarms.'](426efb7efdc753a13f2fa16f7bff9429_img.jpg)
+
+```
+
+classDiagram
+    class MonitoredEntity {
+        <<ProxyClass>>
+    }
+    MonitoredEntity --> Callout : It represents all NRM IOCs that can have alarms.
+  
+```
+
+UML diagram showing the <> Notation. A class box labeled <> MonitoredEntity is connected by a solid line to a callout box containing the text: 'It represents all NRM IOCs that can have alarms.'
+
+**<<ProxyClass>> Notation**
+
+See Annex A for more samples that use <<ProxyClass>>.
+
+### 5.2.4 <<Archetype>>
+
+It is a form or template representing common class properties (e.g. attributes, links, operations and interactions) of a number of represented <<InformationObjectClass>>.
+
+The semantics of an <<Archetype>> is that all attributes, links operations and interactions encapsulated by the <<Archetype>> may or may not be present in the represented <<InformationObjectClass>>. The <<Archetype>> represents a placeholder class that is most useful in technology neutral analysis models that will require further specification and/or mapping within a more complete construction model.
+
+#### 5.2.4.1 Sample
+
+This shows an <<Archetype>> StateManagement. It also shows an <<InformationObjectClass>> IRPAgent that depends on this StateManagement. Note that the StateManagement has defined a number of attributes (not shown in the UML diagram).
+
+The classes that depend on this `StateManagement` may or may not use all of the `StateManagement` attributes. In other words, at least one of the attributes of `StateManagement` is present in the `IRPAgent`. The precise set of `StateManagement` attributes used by the `IRPAgent` is specified in specification that defines the `IRPAgent`.
+
+![UML diagram showing a dependency from IRPAgent to StateManagement. The StateManagement class is labeled with <<Archetype>> and the IRPAgent class is labeled with <<InformationObjectClass>>. A dashed arrow points from IRPAgent to StateManagement.](cab0834804fb031b43865554cc8d06ab_img.jpg)
+
+```
+
+classDiagram
+    class StateManagement {
+        <<Archetype>>
+    }
+    class IRPAgent {
+        <<InformationObjectClass>>
+    }
+    IRPAgent --|> StateManagement
+  
+```
+
+UML diagram showing a dependency from IRPAgent to StateManagement. The StateManagement class is labeled with <> and the IRPAgent class is labeled with <>. A dashed arrow points from IRPAgent to StateManagement.
+
+**<<Archetype>> Notation**
+
+### 5.2.5 <<InformationObjectClass>>
+
+It is the descriptor for a set of network resources and network management capabilities. Each `<<InformationObjectClass>>` represents a set of instances with similar structure, behaviour and relationships.
+
+This `<<InformationObjectClass>>` and other information classes such as `<<Interface>>` are mapped into technology specific model elements. The mapping of IS modelling constructs to technology specific modelling constructs are captured in the corresponding IRP Solution Set specifications.
+
+The name of an `<<InformationObjectClass>>` has scope within the 3GPP IRP IS document in which it is specified and the name must be unique among all `<<InformationObjectClass>>` names within that 3GPP IRP IS document. The IRP IS document name is considered in the similar way as the UML Package-name.
+
+The `<<InformationObjectClass>>` is identical to UML *class* except that it does not include/define methods or operations.
+
+Subclause 3.22.1 of [5]: "A *class* represents a concept within the system being modelled. Classes have data structure and behaviour and relationships to other elements."
+
+See Annex B for information on various application of this Stereotype when compared to that of `<<SupportIOC>>`.
+
+#### 5.2.5.1 Sample
+
+This sample shows an `RncFunction` `<<InformationObjectClass>>`.
+
+![UML diagram showing an InformationObjectClass named RncFunction. The class is represented by a yellow box with the stereotype <<InformationObjectClass>> and the name RncFunction.](cce70c739081f63a6af83dc9483f98ce_img.jpg)
+
+```
+
+classDiagram
+    class RncFunction {
+        <<InformationObjectClass>>
+    }
+  
+```
+
+UML diagram showing an InformationObjectClass named RncFunction. The class is represented by a yellow box with the stereotype <> and the name RncFunction.
+
+**<<InformationObjectClass>> Notation**
+
+### 5.2.6 <<use>> and <<may use>>
+
+The `<<use>>` and `<<may use>>` are unidirectional associations. The target must be an `<<Interface>>` or `<<Notification>>`.
+
+In the case where the target is `<<Interface>>`, the `<<use>>` states that the source class must have the capability to use the target `<<Interface>>` in that it can invoke the operations defined by the `<<Interface>>`. Support of the capability by the source entity is mandatory. The `<<may use>>` states that the source class may have the capability to use the target `<<Interface>>` in that it may invoke the operations defined by the `<<Interface>>`. Support of the capability by the source entity is optional.
+
+In the case the target is `<<Notification>>`, the `<<use>>` states that the source class must be the originator of the notifications defined by the target `<<Notification>>`. Support of the capability by the source entity is mandatory. The `<<may use>>` states that the source class may be the originator of the notifications defined by the target `<<Notification>>`. Support of the capability by the source entity is optional.
+
+#### 5.2.6.1 Sample for target <<Interface>>
+
+This shows that the IRPManager shall use the operations defined by AlarmIRPOperations\_1 and may use the operations defined by AlarmIRPOperations\_2.
+
+![UML diagram showing IRPManager using AlarmIRPOperations_1 and AlarmIRPOperations_2.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+classDiagram
+    class IRPManager {
+        <<SupportIOC>>
+    }
+    class AlarmIRPOperations_1 {
+        <<Interface>>
+        getAlarmList()
+        acknowledgeAlarms()
+    }
+    class AlarmIRPOperations_2 {
+        <<Interface>>
+        getAlarmCount()
+    }
+    IRPManager --> AlarmIRPOperations_1 : <<use>>
+    IRPManager --> AlarmIRPOperations_2 : <<may use>>
+```
+
+The diagram illustrates the relationship between a SupportIOC and two Interfaces. On the left is a box labeled <<SupportIOC>> IRPManager. Two arrows originate from this box. The first arrow points to a box labeled <<Interface>> AlarmIRPOperations\_1, which contains the operations getAlarmList() and acknowledgeAlarms(). This arrow is labeled <<use>>. The second arrow points to a box labeled <<Interface>> AlarmIRPOperations\_2, which contains the operation getAlarmCount(). This arrow is labeled <<may use>>.
+
+UML diagram showing IRPManager using AlarmIRPOperations\_1 and AlarmIRPOperations\_2.
+
+**<<use>> and <<may use>> Notation for target <<Interface>>**
+
+#### 5.2.6.2 Sample for target <<Notification>>
+
+This shows that the PMIRP shall have the capability to emit or originate notifications defined by PMIRPNotifications\_1 and may have the capability to emit or originate notifications defined by PMIRPNotifications\_2.
+
+![UML diagram showing PMIRP using PMIRPNotifications_1 and PMIRPNotifications_2.](c036e2540a94b31357ceb0002f0cacab_img.jpg)
+
+```
+classDiagram
+    class PMIRP {
+        <<SupportIOC>>
+    }
+    class PMIRPNotifications_1 {
+        <<Notification>>
+        notifyMeasurementJobStatusChanger...
+    }
+    class PMIRPNotifications_2 {
+        <<Notification>>
+        notifyThresholdMonitorStatusChanger...
+        notifyThresholdMonitorObjectCreation()
+        notifyThresholdMonitorObjectDeletion()
+    }
+    PMIRP --> PMIRPNotifications_1 : <<use>>
+    PMIRP --> PMIRPNotifications_2 : <<may use>>
+```
+
+The diagram illustrates the relationship between a SupportIOC and two Notifications. On the left is a box labeled <<SupportIOC>> PMIRP. Two arrows originate from this box. The first arrow points to a box labeled <<Notification>> PMIRPNotifications\_1, which contains the operation notifyMeasurementJobStatusChanger... This arrow is labeled <<use>>. The second arrow points to a box labeled <<Notification>> PMIRPNotifications\_2, which contains the operations notifyThresholdMonitorStatusChanger..., notifyThresholdMonitorObjectCreation(), and notifyThresholdMonitorObjectDeletion(). This arrow is labeled <<may use>>.
+
+UML diagram showing PMIRP using PMIRPNotifications\_1 and PMIRPNotifications\_2.
+
+**<<use>> and <<may use>> Notation for target <<Notification>>**
+
+### 5.2.7 <<may realize>>
+
+The <<may realize>> is an unidirectional association. The target must be an <<Interface>>. The <<may realize>> shows that the source entity may realize the operations defined by the target <<Interface>>.
+
+Note that the UML basic element has defined the realize association (and therefore, there is no need to define a stereotype of such association). The realize association shows that the source entity must realize (or implement) the operations defined by the target <<Interface>>.
+
+#### 5.2.7.1 Sample
+
+This shows that the AlarmIRP may realize the operation of AlarmIRPOperations\_2.
+
+![UML diagram showing a <<may realize>> association between AlarmIRP and AlarmIRPOperations_2.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg)
+
+```
+
+classDiagram
+    class AlarmIRP {
+        <<SupportIOC>>
+    }
+    class AlarmIRPOperations_2 {
+        <<Interface>>
+        getAlarmCount()
+    }
+    AlarmIRP --> AlarmIRPOperations_2 : <<may realize>>
+  
+```
+
+UML diagram showing a <> association between AlarmIRP and AlarmIRPOperations\_2.
+
+<<may realize>> Notations
+
+### 5.2.8 Void
+
+### 5.2.9 <<names>>
+
+It specifies a unidirectional composition. The target instance is uniquely identifiable, within the namespace of the source entity, among all other targeted instances of the same target classifier and among other targeted instances of other classifiers that have the same <<names>> composition with the source.
+
+The source classifier and target classifier shall both have a naming attribute.
+
+Composition used as the act of name containment provides a semantic of a whole-part relationship between the domain and the named elements that are contained, even if only by name. From the management perspective access to the part is through the whole. Multiplicity shall be indicated at both ends of the relationship.
+
+A target instance can not have multiple <<names>> with multiple sources, i.e. a target instance can not participate in or belong to multiple namespaces.
+
+#### 5.2.9.1 Sample
+
+This shows that all instances of MscFunction are uniquely identifiable within a ManagedElement instance's namespace.
+
+![UML diagram showing a <<names>> composition between ManagedElement and MscFunction.](95cd9f56a54683029052b8c644228506_img.jpg)
+
+```
+
+classDiagram
+    class ManagedElement {
+        <<InformationObjectClass>>
+    }
+    class MscFunction {
+        <<InformationObjectClass>>
+    }
+    ManagedElement "1" *--> "0..*" MscFunction : <<names>>
+  
+```
+
+UML diagram showing a <> composition between ManagedElement and MscFunction.
+
+<<names>> Notation
+
+### 5.2.10 <<opt>>
+
+The <<opt>> (alternatively <<optional>>) enables the indication of optionality of attributes, parameters and operations (respectively) within the UML diagrams. The semantics of optionality are defined in TS 32.150 [3].
+
+In the absence of the stereotype, the attribute, parameter, or operation in question is mandatory.
+
+#### 5.2.10.1 Sample
+
+![UML class diagram for BulkCMActive interface](16152cf1d84aea10848758f51a91ff6a_img.jpg)
+
+```
+
+classDiagram
+    class BulkCMActive {
+        << Interface >>
+        download()
+        <<opt>> validate()
+        <<opt>> preactivate()
+        activate()
+        fallback()
+    }
+  
+```
+
+UML class diagram for BulkCMActive interface
+
+<<opt>> Notation for operations
+
+### 5.2.11 <<Notification>>
+
+<<Notification>> is a named set of notifications.
+
+#### 5.2.11.1 Sample
+
+This sample shows a <<Notification>> named “PMIRPNotifications\_1” and another <<Notification>> named “PMIRPNotifications\_2”. Both of them have notification(s). An example of a notification can be notifyMeasurementJobStatusChanged().
+
+![UML class diagram showing PMIRP associated with two Notification classes](f57a881fcbcaf494a7dedc4f61224991_img.jpg)
+
+```
+
+classDiagram
+    class PMIRP {
+        <<SupportIOC>>
+    }
+    class PMIRPNotifications_1 {
+        <<Notification>>
+        notifyMeasurementJobStatusChanged()
+    }
+    class PMIRPNotifications_2 {
+        <<Notification>>
+        notifyThresholdMonitorStatusChanged()
+        notifyThresholdMonitorObjectCreated()
+        notifyThresholdMonitorObjectDeleted()
+    }
+    PMIRP --> PMIRPNotifications_1
+    PMIRP --> PMIRPNotifications_2
+  
+```
+
+UML class diagram showing PMIRP associated with two Notification classes
+
+<<Notification>> Notation
+
+### 5.2.12 <<agent-internal-usage>>
+
+This is a unidirectional association. The source passes network management information to target. The source and target are entities or processes running in different IRP instances such as AlarmIRP, PMIRP. The instances may be name-contained by the same IRP Agent or different IRP Agent instances. The precise network management information passed and the information transfer mechanism are not standardized and are vendor-specific.
+
+#### 5.2.12.1 Sample
+
+This shows that NLIRP (NotificationLog IRP) can pass some network management information to FTIRP.
+
+![UML diagram showing a directed association between two SupportIOC elements. The source element is labeled NLIRP and the target element is labeled FileTransferRP. The association is labeled with the stereotype <<agent-internal-usage>>. Below the diagram is the caption '<<agent-internal-usage>> Notation'.](8307f6b04df072c9332f9987e034272c_img.jpg)
+
+**<<agent-internal-usage>> Notation**
+
+UML diagram showing a directed association between two SupportIOC elements. The source element is labeled NLIRP and the target element is labeled FileTransferRP. The association is labeled with the stereotype <>. Below the diagram is the caption '<> Notation'.
+
+### 5.2.13 <<SupportIOC>>
+
+It is the descriptor for a set of management capabilities.
+
+The <<SupportIOC>> is identical to UML *class* except that it does not include/define methods or operations.
+
+Subclause 3.22.1 of [5]: "A *class* represents a concept within the system being modelled. Classes have data structure and behaviour and relationships to other elements."
+
+#### 5.2.13.1 Sample
+
+This sample shows an AlarmList <<SupportIOC>>.
+
+![UML diagram showing a single SupportIOC element labeled AlarmList. Below the diagram is the caption '<<SupportIOC>> Notation'.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg)
+
+**<<SupportIOC>> Notation**
+
+UML diagram showing a single SupportIOC element labeled AlarmList. Below the diagram is the caption '<> Notation'.
+
+## 5.3 Void
+
+## 5.4 Association classes
+
+Subclause 3.46 of OMG: "Unified Modelling Language Specification defines an association class as
+
+"An association class is an association that also has class properties (or a class that has association properties). Even though it is drawn as an association and a class, it is really just a single model element."
+
+## 5.4 Association classes
+
+Subclause 3.46 of OMG: "Unified Modelling Language Specification, Version 1.51" [5]
+
+<http://www.omg.org/technology/documents/formal/uml.html> defines an association class as
+
+"An association class is an association that also has class properties (or a class that has association properties). Even though it is drawn as an association and a class, it is really just a single model element."
+
+Association classes are appropriate for use when an «InformationObjectClass» needs to maintain associations to several other «InformationObjectClass»'s and there are relationships between the members of the associations within the scope of the "containing" «InformationObjectClass». For example, a namespace maintains a set of bindings, a binding ties a name to an object. A Binding «IOC» can be modelled as an Association Class that provides the binding semantics to the relationship between a name and some other «InformationObjectClass». This is depicted in the following figure (exemplary only, not taken from another 3GPP specification).
+
+![UML Class Diagram illustrating an Association Class. A Namespace (InformationObjectClass) has a composition relationship with a Binding (InformationObjectClass) class, indicated by a solid diamond and a multiplicity of 0..* at the Binding end. The Binding class is connected to a Name class (multiplicity 1) and an Object (InformationObjectClass) class (multiplicity 1) via a dashed association line, making it an association class for the Name-Object relationship.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg)
+
+```
+classDiagram
+    class Namespace {
+        <<InformationObjectClass>>
+    }
+    class Binding {
+        <<InformationObjectClass>>
+    }
+    class Name
+    class Object {
+        <<InformationObjectClass>>
+    }
+    Namespace "1" *-- "0..*" Binding
+    Name "1" -- "1" Object
+    Binding -.-> Name
+    Binding -.-> Object
+```
+
+UML Class Diagram illustrating an Association Class. A Namespace (InformationObjectClass) has a composition relationship with a Binding (InformationObjectClass) class, indicated by a solid diamond and a multiplicity of 0..\* at the Binding end. The Binding class is connected to a Name class (multiplicity 1) and an Object (InformationObjectClass) class (multiplicity 1) via a dashed association line, making it an association class for the Name-Object relationship.
+
+**Example of an Association Class**
+
+## 5.5 Abstract Class
+
+It specifies a <<InformationObjectClass>> as a base class to be inherited by subclasses. An abstract class can not be.
+
+Abstract class notation is the use of italics in the class name of the corresponding <<InformationObjectClass>> in the diagram.
+
+### 5.5.1 Sample
+
+This shows that ManagedGenericIRP is an abstract <<InformationObjectClass>>.
+
+![UML Class Diagram showing ManagedGenericIRP as an abstract class inherited by NotificationIRP.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg)
+
+```
+classDiagram
+    class ManagedGenericIRP {
+        <<InformationObjectClass>>
+        ManagedGenericIRP
+        (from 32.312)
+    }
+    class NotificationIRP {
+        <<InformationObjectClass>>
+        NotificationIRP
+        (from 32.302)
+    }
+    ManagedGenericIRP <|-- NotificationIRP
+```
+
+The diagram illustrates the inheritance relationship between two classes. At the top is the base class, **<<InformationObjectClass>> ManagedGenericIRP (from 32.312)**, which is an abstract class. At the bottom is the subclass, **<<InformationObjectClass>> NotificationIRP (from 32.302)**. A vertical inheritance arrow points from the subclass to the base class, indicating that NotificationIRP inherits from ManagedGenericIRP.
+
+UML Class Diagram showing ManagedGenericIRP as an abstract class inherited by NotificationIRP.
+
+**Abstract Class Notation**
+
+# Annex A (informative): Samples of using <<ProxyClass>> to model Link related IOCs
+
+## A.1 First Sample
+
+This shows a <<ProxyClass>> named YyyFunction. It represents all IOCs listed in the Note under the UML diagram. All the listed IOCs, in the context of this sample, inherit from ManagedFunction IOC.
+
+The use of <<ProxyClass>> eliminates the need to draw multiple UML <<InformationObjectClass>> boxes, i.e. those whose names are listed in the Note, in the UML diagram.
+
+![UML Class Diagram showing ManagedFunction as an InformationObjectClass and YyyFunction as a ProxyClass inheriting from it.](73dff6b45b2b9ffd384bab3235f869af_img.jpg)
+
+```
+classDiagram
+    class ManagedFunction {
+        <<InformationObjectClass>>
+        (from TS 32.622)
+    }
+    class YyyFunction {
+        <<ProxyClass>>
+    }
+    YyyFunction --|> ManagedFunction
+```
+
+The diagram shows two classes. The top class is labeled <<InformationObjectClass>> ManagedFunction (from TS 32.622). The bottom class is labeled <<ProxyClass>> YyyFunction. A generalization arrow points from YyyFunction to ManagedFunction.
+
+UML Class Diagram showing ManagedFunction as an InformationObjectClass and YyyFunction as a ProxyClass inheriting from it.
+
+Note: The YyyFunction <<ProxyClass>> represents AsFunction, AucFunction, BgFunction, ...
+
+**<<ProxyClass>> Notation Sample A.1**
+
+## A.2 Second Sample
+
+This shows a <<ProxyClass>> named YyyFunction. It represents all IOCs listed in the Note right under the UML diagram. All the listed IOCs, in the context of this sample, have link (internal and external) relations.
+
+The actual names of the IOC represented by InternalYyyFunction <<ProxyClass>> and by the ExternalYyyFunction <<ProxyClass>> are listed under the subsection of X.Y of the associated YyyFunction. For example, under X.Y.1 for AsFunction, two paragraphs are added to list all peer internal entities and external entities that are linked with AsFunction. See sample in quotation below that is using AsFunction as a sample for YyyFunction.
+
+The actual names of the IOC represented by Link\_a\_z <<ProxyClass>> and by ExternalLink\_a\_z <<ProxyClass>> are listed under the subsection of X.Y of the associated YyyFunction. For example, under X.Y.1 for AsFunction, two paragraphs are added to list the names of the IOCs represented by Link\_a\_z and by ExternalLink\_a\_z. See the quoted text below that is using AsFunction as a sample for YyyFunction.
+
+“
+
+### X.Y.1 AsFunction
+
+#### X.Y.1.1 Definition
+
+This IOC represents As functionality. For more information about the As, see 3GPP TS 23.002 [15].
+
+The linked InternalYyyFunction <<ProxyClass>> represents SlsFunction, CsefFunction, HlrFunction ...
+
+The linked ExternalYyyFunction <<ProxyClass>> represents ...
+
+The Link\_a\_z <<ProxyClass>> represents Link\_As\_Scesf, Link\_Bgcf\_Scesf ...
+
+The ExternalLink\_a\_z <<ProxyClass>> represents ...
+
+“
+
+![UML Class Diagram showing relationships between proxy classes. A central class 'YyyFunction' is connected to 'InternalYyyFunction' on its left and 'ExternalYyyFunction' on its right. Above 'YyyFunction', two classes 'Link_a_z' and 'ExternalLink_a_z' are shown, each connected to 'YyyFunction' by a vertical line. All classes are represented by yellow boxes with three compartments, with the first compartment containing the <<ProxyClass>> stereotype and the class name.](f68a5f1f8845159744eff3e0e786731e_img.jpg)
+
+```
+
+classDiagram
+    class Link_a_z {
+        <<ProxyClass>>
+    }
+    class ExternalLink_a_z {
+        <<ProxyClass>>
+    }
+    class InternalYyyFunction {
+        <<ProxyClass>>
+    }
+    class YyyFunction {
+        <<ProxyClass>>
+    }
+    class ExternalYyyFunction {
+        <<ProxyClass>>
+    }
+    Link_a_z -- YyyFunction
+    ExternalLink_a_z -- YyyFunction
+    InternalYyyFunction -- YyyFunction
+    ExternalYyyFunction -- YyyFunction
+  
+```
+
+UML Class Diagram showing relationships between proxy classes. A central class 'YyyFunction' is connected to 'InternalYyyFunction' on its left and 'ExternalYyyFunction' on its right. Above 'YyyFunction', two classes 'Link\_a\_z' and 'ExternalLink\_a\_z' are shown, each connected to 'YyyFunction' by a vertical line. All classes are represented by yellow boxes with three compartments, with the first compartment containing the <> stereotype and the class name.
+
+NOTE: The 'Yyy' of YyyFunction <<ProxyClass>> represents AsFunction, AucFunction, ...
+
+#### <<ProxyClass>> Notation Sample A.2
+
+# Annex B (normative): Application of <<InformationObjectClass>> and <<SupportIOC>>
+
+The <<InformationObjectClass>> and <<SupportIOC>> are stereotypes. These two stereotypes serve similar purpose in that each is a named set of network resource properties. However, their applications, in the context of supporting network management over Itf-N, can be different. This Annex highlights their similarities and differences of such application.
+
+|                                                                                                                                          | <<InformationObjectClass>>                                                                                                                                                                                               | <<SupportIOC>>                                                                                                                                                                                                                 |
+|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Can it be an abstract class?                                                                                                             | Yes                                                                                                                                                                                                                      | Yes                                                                                                                                                                                                                            |
+| Can it be a concrete class?                                                                                                              | Yes                                                                                                                                                                                                                      | Yes                                                                                                                                                                                                                            |
+| Can it inherit from <<InformationObjectClass>>?                                                                                          | Yes                                                                                                                                                                                                                      | No                                                                                                                                                                                                                             |
+| Can it inherit from <<SupportIOC>>?                                                                                                      | No                                                                                                                                                                                                                       | Yes                                                                                                                                                                                                                            |
+| Can it be name-contained by <<InformationObjectClass>>?                                                                                  | Yes                                                                                                                                                                                                                      | Yes                                                                                                                                                                                                                            |
+| Can it be name-contained by <<SupportIOC>>?                                                                                              | No                                                                                                                                                                                                                       | Yes                                                                                                                                                                                                                            |
+| Can an instance have a DN?                                                                                                               | <<InformationObjectClass>> must be a class of a naming-tree meaning all its instances must have a DN.                                                                                                                    | <<SupportIOC>> may be used by specification author for a class within a naming-tree. If so, it means that all its instances will have a DN.                                                                                    |
+| Can IRPManager use operations of Basic CM IRP [6] and Bulk CM IRP [7] to access the information in an instance?                          | IRPManager can use the Basic CM IRP and Bulk CM IRP operations to access information of all <<InformationObjectClass>> defined in all NRM IRPs, in accordance to the qualifier values of the <<InformationObjectClass>>. | IRPManager can use the Basic CM IRP and Bulk CM IRP operations to access information of instances of <<SupportIOC>> defined in their respective Interface IRP, in accordance to the qualifier values of the <<SupportIOC>>.    |
+| Can IRPManager use operations of Interface IRP, except Basic CM IRP [6] and Bulk CM IRP [7] (e.g. Alarm IRP), to access the information? | No                                                                                                                                                                                                                       | IRPManager can use the Interface IRP operations to access information of <<SupportIOC>> defined in their respective Interface IRP, in accordance to qualifier values of the <<SupportIOC>>.                                    |
+| Can IRPManager receive information via Notification [8] whose objectClass and objectInstance parameters carry the instance DN?           | Yes.<br>The types of notification emitted are shown by the Notification Table associated with the class definition.                                                                                                      | Yes if <<SupportIOC>> is a class of a naming-tree.<br>The types of notification emitted are shown by the Notification Table associated with the class definition.<br><br>No if <<SupportIOC>> is not a class of a naming-tree. |
+| Measurement [9]                                                                                                                          | Measurements can be associated with <<InformationObjectClass>> instances.                                                                                                                                                | Measurements can be associated with <<SupportIOC>> instances if <<SupportIOC>> class is used in a naming-tree.                                                                                                                 |
+
+# Annex C (informative): Change history
+
+| Change history |           |               |          |      |                                                                               |     |           |            |
+|----------------|-----------|---------------|----------|------|-------------------------------------------------------------------------------|-----|-----------|------------|
+| Date           | TSG #     | TSG Doc.      | CR       | Re v | Subject/Comment                                                               | Cat | Old       | New        |
+| Dec 2003       | SA_2<br>2 | SP-<br>030615 | --       | --   | Submitted to TSG SA#22 for Information                                        | --  | 1.0.<br>0 |            |
+| Mar 2004       | SA_2<br>3 | SP-<br>040115 | --       | --   | Submitted to TSG SA#23 for Approval                                           | --  | 2.0.<br>0 | 6.0.0      |
+| Oct 2006       | --        | --            | --       | --   | Corrected TS ver. and Rel #; added GSM logo in line with 41.101               | --  | 6.0.<br>0 | 6.0.1      |
+| Jun 2004       | SA_2<br>4 | SP-<br>040242 | 000<br>1 | --   | UML Repertoire Updates (Associations)                                         | C   | 6.0.<br>1 | 6.1.0      |
+| Mar 2005       | SA_2<br>7 | SP-<br>050023 | 000<br>2 | --   | Add "abstract" adornment                                                      | F   | 6.1.<br>0 | 6.2.0      |
+| Jun 2005       | SA_2<br>8 | SP-<br>050284 | 000<br>3 | --   | Add the stereotype "Notification" to UML repertoire. Align with TS 32.412     | F   | 6.2.<br>0 | 6.3.0      |
+| Jun 2005       | SA_2<br>8 | SP-<br>050284 | 000<br>4 | --   | Correction of stereotype name capitalization and visibility qualifiers        | F   | 6.2.<br>0 | 6.3.0      |
+| Dec 2005       | SA_3<br>0 | SP-<br>050729 | 000<br>5 | --   | Apply IS template - Align with 32.151                                         | F   | 6.3.<br>0 | 7.0.0      |
+| Mar 2007       | SA_3<br>5 | SP-<br>070045 | 000<br>6 | --   | Add samples to illustrate the use of ProxyClass to model Link related objects | F   | 7.0.<br>1 | 7.1.0      |
+| Mar 2007       | SA_3<br>5 | SP-<br>070045 | 000<br>7 | --   | Correct the references of IRPAgent and IRPManager                             | F   | 7.0.<br>1 | 7.1.0      |
+| Mar 2007       | --        | --            | --       | --   | Deleted reference to CMIP SS, discontinued from R7 onwards                    | --  | 7.0.<br>1 | 7.1.0      |
+| Sep 2007       | SA_3<br>7 | SP-<br>070614 | 000<br>8 | --   | Modify usage of cardinality zero for IOC                                      | C   | 7.1.<br>0 | 8.0.0      |
+| Sep 2007       | SA_3<br>7 | SP-<br>070614 | 000<br>9 | --   | Remove visibility qualifier stereotype                                        | C   | 7.1.<br>0 | 8.0.0      |
+| Sep 2007       | SA_3<br>7 | SP-<br>070614 | 001<br>0 | --   | Add "agent internal usage" stereotype description                             | C   | 7.1.<br>0 | 8.0.0      |
+| Sep 2009       | SA_4<br>5 | SP-<br>090627 | 001<br>1 | --   | Introduce SupportIOC Stereotype                                               | F   | 8.0.<br>0 | 9.0.0      |
+| Sep 2009       | SA_4<br>5 | SP-<br>090534 | 001<br>2 | --   | Align Repertoire with practice                                                | F   | 8.0.<br>0 | 9.0.0      |
+| Dec 2009       | SA_4<br>6 | SP-<br>090719 | 001<br>3 | --   | Add a new Annex B on Application of Stereotypes SupportIOC and IOC            | F   | 9.0.<br>0 | 9.1.0      |
+| Dec 2009       | SA_4<br>6 | SP-<br>090719 | 001<br>4 | --   | Clarify rules for <<names>> stereotype                                        | F   | 9.0.<br>0 | 9.1.0      |
+| Mar 2010       | SA_4<br>7 | SP-<br>100035 | 001<br>5 | --   | Clarify class support of notification re 32.152                               | F   | 9.1.<br>0 | 9.2.0      |
+| Sep 2010       | SA_4<br>9 | SP-<br>100489 | 001<br>6 | --   | Introduction of additional basic model element {xor}                          | F   | 9.1.<br>0 | 10.0.<br>0 |
+
+| Change history |         |           |      |     |     |                                                           |             |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                           | New version |
+| 2017-06        | SA#75   | SP-170509 | 0021 | 2   | F   | Correcting the definition of the realization relationship | 10.1.0      |

marked/Rel-10/32_series/32153/raw.md

@@ -0,0 +1,1259 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Integration Reference Point (IRP) technology-specific templates, rules and guidelines (Release 10)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in a bold, lowercase font with a red signal icon above the "l". The word "ADVANCED" is written in a smaller, uppercase font above the "e". A trademark symbol (TM) is located to the right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top, and the "P" and "P" are connected at the top. A red signal icon is located below the "G". A trademark symbol (TM) is located to the right of the "P". Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, uppercase font.
+
+3GPP logo
+
+Keywords  
+UMTS, management
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                     |           |
+|-----------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                      | 5         |
+| Introduction .....                                                                                  | 5         |
+| 1 Scope.....                                                                                        | 6         |
+| 2 References.....                                                                                   | 6         |
+| 3 Definitions and abbreviations .....                                                               | 7         |
+| 3.1 Definitions.....                                                                                | 7         |
+| 3.2 Abbreviations .....                                                                             | 7         |
+| 4 Interface IRP SS template.....                                                                    | 8         |
+| 5 NRM IRP SS template .....                                                                         | 14        |
+| <b>Annex A (normative): General rules for Solution Sets (SS) .....</b>                              | <b>16</b> |
+| A.1 Introduction.....                                                                               | 16        |
+| A.2 Solution Set (SS) versioning.....                                                               | 16        |
+| A.3 Referenced Information Service (IS) specification.....                                          | 16        |
+| <b>Annex B (normative): Technology specific rules &amp; guidelines for CORBA Solution Sets.....</b> | <b>17</b> |
+| B.1 Rules.....                                                                                      | 17        |
+| B.1.1 Introduction .....                                                                            | 17        |
+| B.1.2 Rules for specification of CORBA Solution Sets .....                                          | 17        |
+| B.1.2.1 Introduction .....                                                                          | 17        |
+| B.1.2.2 Pragma prefix .....                                                                         | 17        |
+| B.1.3 Implementation aspects of Interface IRP CORBA Solution Sets .....                             | 17        |
+| B.1.3.1 Introduction .....                                                                          | 17        |
+| B.1.3.2 IRP Agent behaviour on incoming optional method.....                                        | 18        |
+| B.1.3.3 IRP Agent behaviour on incoming optional parameter of operation.....                        | 18        |
+| B.1.3.4 IRP Agent behaviour on outgoing attributes of notification .....                            | 18        |
+| B.1.3.5 Encoding rule of absence semantics.....                                                     | 18        |
+| B.1.4 Rules for NRM IRP CORBA SS extensions.....                                                    | 19        |
+| B.1.4.1 Allowed extensions.....                                                                     | 19        |
+| B.1.4.2 Extensions not allowed .....                                                                | 19        |
+| B.2 Guidelines (Style Guide for CORBA SS IDL) .....                                                 | 20        |
+| B.2.1 Modules and File.....                                                                         | 20        |
+| B.2.1.1 Use of Modules.....                                                                         | 20        |
+| B.2.1.2 File Names.....                                                                             | 20        |
+| B.2.1.3 Include Conventions.....                                                                    | 20        |
+| B.2.1.4 File Structure .....                                                                        | 21        |
+| B.2.1.4.1 File Internal Identification .....                                                        | 21        |
+| B.2.1.4.2 File Guard .....                                                                          | 21        |
+| B.2.1.4.3 Required Contents.....                                                                    | 21        |
+| B.2.1.4.4 Example illustrating a File Structure .....                                               | 21        |
+| B.2.2 Identifiers .....                                                                             | 22        |
+| B.2.2.1 Mixed Case, Beginning Upper, No Underscores .....                                           | 22        |
+| B.2.2.2 Lower Case with Underscores.....                                                            | 22        |
+| B.2.2.3 Upper Case with Underscores .....                                                           | 23        |
+| B.2.2.4 Naming IDL Sequence Types .....                                                             | 23        |
+| B.2.3 Interface IRP .....                                                                           | 24        |
+| B.2.3.1 Constant String and Type Definitions .....                                                  | 24        |
+| B.2.3.2 Operations.....                                                                             | 25        |
+| B.2.3.3 Notifications .....                                                                         | 25        |
+| B.2.4 NRM IRP.....                                                                                  | 27        |
+| <b>Annex C (normative): Technology specific rules &amp; guidelines for SOAP SSs.....</b>            | <b>28</b> |
+
+|                               |                                                                                |           |
+|-------------------------------|--------------------------------------------------------------------------------|-----------|
+| C.1                           | Rules.....                                                                     | 28        |
+| C.1.1                         | Introduction .....                                                             | 28        |
+| C.1.2                         | Rules for specification of SOAP Solution Sets .....                            | 28        |
+| C.1.2.1                       | Introduction.....                                                              | 28        |
+| C.1.2.2                       | File names .....                                                               | 28        |
+| C.1.2.3                       | Void .....                                                                     | 28        |
+| C.1.2.4                       | XML version encoding .....                                                     | 28        |
+| C.1.2.5                       | Namespaces .....                                                               | 29        |
+| C.1.3                         | Implementation aspects of Interface IRP SOAP Solution Sets .....               | 29        |
+| C.1.3.1                       | Introduction.....                                                              | 29        |
+| C.1.3.n                       | XXXX rule.....                                                                 | 29        |
+| C.2                           | Guidelines (Style Guide for SOAP SS WSDL) .....                                | 29        |
+| C.2.1                         | File structure .....                                                           | 29        |
+| C.2.1.1                       | Definitions .....                                                              | 29        |
+| C.2.1.2                       | Namespaces .....                                                               | 29        |
+| C.2.1.3                       | Documentation.....                                                             | 29        |
+| C.2.1.4                       | Types.....                                                                     | 29        |
+| C.2.1.5                       | Message .....                                                                  | 30        |
+| C.2.1.6                       | Port type.....                                                                 | 30        |
+| C.2.1.7                       | Binding.....                                                                   | 30        |
+| C.2.1.8                       | Port.....                                                                      | 30        |
+| C.2.1.9                       | Service .....                                                                  | 30        |
+| C.2.2                         | Identifiers.....                                                               | 30        |
+| C.2.2.n                       | Rule n .....                                                                   | 30        |
+| C.3                           | XML Schema Guidelines .....                                                    | 30        |
+| C.3.1                         | XSD guidelines for messages definition .....                                   | 30        |
+| C.3.1.1                       | Request message .....                                                          | 30        |
+| C.3.1.2                       | Response messages .....                                                        | 30        |
+| C.3.1.3                       | Fault messages .....                                                           | 30        |
+| C.3.2                         | XSD guidelines for parameters definition.....                                  | 30        |
+| C.3.1.1                       | General guidelines .....                                                       | 30        |
+| C.3.1.1                       | Simple type definitions .....                                                  | 30        |
+| C.3.1.2                       | Complex type definition .....                                                  | 31        |
+| C.3.3                         | Identifiers.....                                                               | 31        |
+| <b>Annex D (normative):</b>   | <b>Technology specific rules &amp; guidelines for XML specifications .....</b> | <b>32</b> |
+| D.1                           | Rules.....                                                                     | 32        |
+| D.1.1                         | XSD Use Cases .....                                                            | 32        |
+| D.1.1.1                       | Background.....                                                                | 32        |
+| D.1.1.2                       | Use Cases Set 1 .....                                                          | 32        |
+| D.1.1.3                       | Use Cases Set 2.....                                                           | 33        |
+| D.1.2                         | Rules for NRM IRP XML specification extensions.....                            | 33        |
+| D.1.3                         | XML version encoding.....                                                      | 33        |
+| D.2                           | Guidelines .....                                                               | 34        |
+| <b>Annex E (informative):</b> | <b>Change history.....</b>                                                     | <b>35</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.150 "Integration Reference Point (IRP) Concept and definitions"
+- TS 32.151 "Integration Reference Point (IRP) Information Service (IS) template"
+- TS 32.152 "Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire"
+- TS 32.153 "Integration Reference Point (IRP) technology specific templates, rules and guidelines"**
+- TS 32.154 "Backward and Forward Compatibility (BFC); Concept and definitions"
+- TS 32.155 "Requirements template".
+
+## --- 1 Scope
+
+The present document contains the templates to be used for the production of Integration Reference Point (IRP) technology-specific specifications.
+
+# --- 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.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [4] Void.
+- [5] Void.
+- [6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [7] Void.
+- [8] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>).
+- [9] OMG IDL Style Guide, ab/98-06-03, June 17, 1998.
+- [10] W3C WSDL 1.1 specification (<http://www.w3.org/TR/wsdl>) .
+- [11] Void.
+- [12] Void.
+- [13] Void.
+- [14] Void.
+- [15] W3C XML Specifications (<http://www.w3.org/XML/Core/>).
+- [16] IETF RFC 3629 (<http://tools.ietf.org/html/rfc3629#ref-UNICODE>).
+- [17] 3GPP TS 32.642: "Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+
+## --- 3 Definitions and abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+**IRP Agent:** See 3GPP TS 32.150 [3].
+
+**IRP Manager:** See 3GPP TS 32.150 [3].
+
+**SOAP:** See [8].
+
+### 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| CM    | Conditional Mandatory                           |
+| CM    | Configuration Management                        |
+| CO    | Conditional Optional                            |
+| CORBA | Common Object Request Broker Architecture (OMG) |
+| FF    | File Format                                     |
+| IDL   | Interface Definition Language                   |
+| IOC   | Information Object Class                        |
+| IOC   | Information Object Class                        |
+| IRP   | Integration Reference Point                     |
+| IS    | Information Service                             |
+| M     | Mandatory                                       |
+| MO    | Managed Object                                  |
+| MOC   | Managed Object Class                            |
+| NRM   | Network Resource Model                          |
+| O     | Optional                                        |
+| OMG   | Object Management Group                         |
+| TS    | Technical Specification                         |
+| SOAP  | W3C acronym                                     |
+| SS    | Solution Set                                    |
+| SuM   | Subscription Management                         |
+| UML   | Unified Modelling Language (OMG)                |
+| URI   | Uniform Resource Identifier                     |
+| WSDL  | Web Service Description Language                |
+| XML   | eXtensible Markup Language                      |
+| XSD   | XML Schema Definition                           |
+
+# --- 4 Interface IRP SS template
+
+This clause contains the Interface IRP SS template.
+
+The clauses in this template (that shall be used in the SS specifications) are numbered starting with "X", which in general should correspond to clause 4 that is the beginning of the normative part of a TS. However, if there is a need in a specific SS to introduce additional clauses in the TS body, X may correspond to a number higher than 4.
+
+The SS templates use qualifiers M, O, CM and CO. The semantics of these qualifiers are defined in TS 32.150 [3].
+
+The introductory clauses (from clause 1 to clause 3) for the SS should be modelled similarly to that of clause 1 to 3 of this specification.
+
+Instructions are written in *italics*.
+
+Usage of fonts shall be according to the following table.
+
+**Table: Usage of fonts**
+
+| Item               | Font        |
+|--------------------|-------------|
+| Class names        | Courier New |
+| Attribute names    | Courier New |
+| Operation names    | Courier New |
+| Parameter names    | Courier New |
+| Assertion names    | Courier New |
+| Notification names | Courier New |
+| Exception names    | Courier New |
+| State names        | Arial       |
+| Enumerated values  | Arial       |
+
+## X Architectural Features
+
+*"X" represents a clause number in the actual SS. It contains at least the following this subclause:*
+
+### X.1 General
+
+*This subclause contains the following paragraph:*
+
+"The overall architectural feature of <subject IRP> is specified in 3GPP TS <relevant specification number> [<relevant reference>]. This clause specifies features that are specific to the <specific technology> SS."
+
+*Example:*
+
+"The overall architectural feature of Alarm IRP is specified in 3GPP TS 32.111-2 [6]. This clause specifies features that are specific to the CORBA SS."
+
+*Specific for SOAP SS: the supported XSD, WSDL and SOAP versions shall be indicated together with the style and encoding style, and the namespaces with corresponding prefixes used in the WSDL specifications. Therefore the SOAP SS also contains the information quoted below:*
+
+"The SOAP <supported version> specification [relevant reference], XSD <supported version> specification [relevant reference] and WSDL <supported version> specification [relevant reference] are supported.
+
+This specification uses "<RPC/Document>" style in WSDL file.
+
+This specification uses "<Literal/Encoded>" encoding style in WSDL file.
+
+This specification uses a number of namespace prefixes which are listed in Table X.1.
+
+| Prefix                | Namespace                                                                                         |
+|-----------------------|---------------------------------------------------------------------------------------------------|
+| http                  | <a href="http://schemas.xmlsoap.org/wsdl/http/">http://schemas.xmlsoap.org/wsdl/http/</a>         |
+| soap                  | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a>         |
+| xs or xsd             | <a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>                   |
+| xsi                   | <a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a> |
+| <IRP specific prefix> | <Namespace's URI>                                                                                 |
+
+**Table X.1: Prefixes and Namespaces used in this specification**
+
+”
+
+### X.a <Feature [a-1]>
+
+*<Description of architectural feature "a">*
+
+*"a" represents a number, starting at 2 and increasing by 1 with each new feature.*
+
+*NOTE: This subclause is optional.*
+
+## Y Mapping
+
+*"Y" represents a clause number, immediately following "X".*
+
+### Y.1 Operation and Notification mapping
+
+*It contains this leading paragraph:*
+
+"The <subject IRP>: IS (see 3GPP TS <relevant specification number> [<relevant reference number>]) defines semantics of operation and notification visible across the Itf-N. Table Y.1.1 indicates mapping of these operations and notifications to their equivalents defined in this SS."
+
+*Example:*
+
+"Alarm IRP: IS 3GPP TS 32.111-2 [6] defines semantics of operation and notification visible across the Itf-N. Table Y.1.1 indicates mapping of these operations and notifications to their equivalents defined in this SS."
+
+*The table includes all operations and notifications, including those inherited. The table lists the operations first and then the notifications. The list order is the same as the one used in the IS. Semantics for the Qualifier is defined in Ref [x].*
+
+**Table Y.1.1: Mapping from IS Operation/Notification to SS equivalents**
+
+| IS Operation/Notification<br>in 3GPP TS <relevant TS number > [<relevant reference number>] | SS Method | Qualifier      |
+|---------------------------------------------------------------------------------------------|-----------|----------------|
+| <operation1>                                                                                | <method1> | M, O, CM or CO |
+| <operation2>                                                                                | <method2> | M, O, CM or CO |
+| ...                                                                                         |           |                |
+| ..                                                                                          |           |                |
+| notify<notification1>                                                                       | <notify1> | M, O, CM or CO |
+| ...                                                                                         | ...       |                |
+
+### Y.2 Operation parameter mapping
+
+*It contains this leading paragraph:*
+
+"Reference 3GPP TS <relevant version> [<relevant reference number>] defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS."
+
+*Example:*
+
+"Reference 3GPP TS 32.111-2 [6] defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS."
+
+**Table Y.2.1: Mapping from IS <operation1> parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter            | Qualifier      |
+|------------------------|--------------------------------|----------------|
+| <parameter-1>          | <type definition> <parameter1> | M, O, CM or CO |
+| <parameter-2>          | <type definition> <parameter2> | M, O, CM or CO |
+| ...                    | ...                            | ...            |
+| ...                    | ...                            | ...            |
+| status                 | ...                            | M              |
+
+**Table Y.2.2: Mapping from IS <operation2> parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter            | Qualifier      |
+|------------------------|--------------------------------|----------------|
+| <parameter-1>          | <type definition> <parameter1> | M, O, CM or CO |
+| ...                    | ...                            | ...            |
+| status                 | ...                            | M              |
+
+**Table Y.2.x:**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|---------------------|-----------|
+| ...                    | ...                 | ...       |
+| ...                    | ...                 | ...       |
+| status                 | ...                 | M         |
+
+### Y.3 Notification parameter mapping
+
+*It contains this leading paragraph:*
+
+"Reference 3GPP TS <relevant version number> [<relevant referenced number>] defines semantics of parameters carried in notifications. The following tables indicate the mapping of these parameters to their SS equivalents."
+
+*Specific for CORBA SS: CORBA SS uses OMG CORBA Structured Event to carry IS-defined notification parameters. The Structured Event has the OMG defined parameters. These parameters will be related to the SS equivalents. So, the SS contains this paragraph.*
+
+"
+
+The following tables indicate the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification Service [<relevant reference number>]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [<relevant reference number>], 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 <subject> IRP: IS [<relevant reference number>] defined notification parameters.
+
+"
+
+Table Y.3.1: Mapping for **notifyKkk**
+
+| IS Parameters | <SS> Parameters | Qualifier | Comment |
+|---------------|-----------------|-----------|---------|
+| <parameter-1> | <parameter-A>   | M or O    | ...     |
+| <parameter-2> | <parameter-B>   | M or O    | ...     |
+| ...           | ...             | M or O    | ...     |
+
+## Z Notification Interface
+
+"Z" represents a number, immediately following "Y".
+
+This sub-clause captures SS technology specific details required to realize the IS-defined <interface> for notifications.
+
+Specific for CORBA SS:
+
+The SS contains this:
+
+"
+
+OMG CORBA Notification push operation is used to realise the notification of AlarmIRPNotifications. All the notifications in this interface are implemented using this `push_structured_event` method.
+
+### <Z>.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 [1]). 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.
+
+"
+
+# 5 NRM IRP SS template
+
+This clause contains the NRM IRP SS template.
+
+The clauses in this template (that shall be used in the SS specifications) are numbered starting with "X", which in general should correspond to clause 4 that is the beginning of the normative part of a TS. However, if there is a need in a specific SS to introduce additional clauses in the TS body, X may correspond to a number higher than 4.
+
+The introductory clauses (from clause 1 to clause 3) for the SS should be modelled similarly to that of this specification.
+
+Usage of fonts shall be according to the following table.
+
+**Table: Usage of fonts**
+
+| Item               | Font        |
+|--------------------|-------------|
+| Class names        | Courier New |
+| Attribute names    | Courier New |
+| Assertion names    | Courier New |
+| Notification names | Courier New |
+| State names        | Arial       |
+| Enumerated values  | Arial       |
+
+## X Architectural Features
+
+*"X" represents a clause number in the actual SS. It contains at least the following subclause:*
+
+### X.1 General
+
+*This subclause contains the following paragraph:*
+
+"The overall architectural feature of <subject IRP> is specified in 3GPP TS <relevant specification number> [<relevant reference>]. This clause specifies features that are specific to the <specific technology> SS."
+
+*Example:*
+
+"The overall architectural feature of UTRAN Network Resources IRP is specified in 3GPP TS 32.642 [17]. This clause specifies features that are specific to the CORBA SS."
+
+### X.a <Feature [a-1]>
+
+*<Description of architectural feature "a">*
+
+*"a" represents a number, starting at 2 and increasing by 1 with each new feature.*
+
+*NOTE: This subclause is optional.*
+
+## Y Mapping
+
+*"Y" represents a number, immediately following "X".*
+
+### Y.1 General
+
+*This subclause contains a general introduction to the mapping.*
+
+*For CORBA SSs, it contains the following paragraph:*
+
+"Attributes modelling associations as defined in the NRM (here also called "reference attributes") are in this SS mapped to attributes. The names of the reference attributes in the NRM are mapped to the corresponding attribute names in the MOC. When the cardinality for an association is 0..1 or 1..1 the datatype for the reference attribute is defined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the cardinality for an association allows more than one referred MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references."
+
+*For XML FF specifications, it contains the following paragraph:*
+
+"An IOC maps to an XML element of the same name as the IOC's name in the IS. An IOC attribute maps to a sub-element of the corresponding IOC's XML element, and the name of this sub-element is the same as the attribute's name in the IS."
+
+### Y.2 Information Object Class (IOC) mapping
+
+*This subclause is only applicable to NRM IRP CORBA Solution Sets. This clause contains the mapping tables of all iS-defined IOCs to corresponding SS-level MOCs, excluding those inherited.*
+
+#### Y.2.a IOC <IOC name >
+
+*It contains one table with Mapping from NRM IS IOC attribute name to the SS equivalent MOC attribute name and attribute types.*
+
+*"a" in the subclause heading represents a number, starting at 1 and increasing by 1 for each IOC.*
+
+| Attribute of IOC <IOC name > in<br>3GPP TS <relevant TS number> [<relevant<br>reference number>] | SS<br>Attribute | SS<br>Type | Support<br>Qualifier | Read<br>Qualifier | Write<br>Qualifier |
+|--------------------------------------------------------------------------------------------------|-----------------|------------|----------------------|-------------------|--------------------|
+| attribute-a                                                                                      | attribute-1     | <type>     | ...                  | ...               | ...                |
+| attribute-b                                                                                      | attribute-2     | <type>     | ...                  | ...               | ...                |
+| ...                                                                                              | ...             | ...        | ...                  | ...               | ...                |
+
+### Y.2 Information Object Class (IOC) mapping
+
+*This subclause is only applicable to NRM IRP XML FF specifications. This subclause describes the mapping of all IS-defined IOCs to corresponding XML definitions, excluding the inherited IOCs.*
+
+*Note: This subclause is also numbered Y.2, directly following Y.1, since every NRM SS-level TS is made for only one SS technology.*
+
+# --- Annex A (normative): General rules for Solution Sets (SS)
+
+## A.1 Introduction
+
+The intent of this annex is twofold.
+
+The first intent is for 3GPP-internal use to document how a 3GPP Solution Set is (SS) produced and what it shall contain.
+
+The second intent is to give the reader of an Information Service (IS) or a Solution Set (SS) a better understanding on how to interpret the IS or SS specifications.
+
+## --- A.2 Solution Set (SS) versioning
+
+*Editor's note: For Further Study.*
+
+## --- A.3 Referenced Information Service (IS) specification
+
+A sentence shall be included in the clause "Scope" of all SS specifications. The sentence shall read as follows:
+
+"This Solution Set specification is related to Z".
+
+where Z is the 3GPP Information Service (IS) specification number including the version, such as "TS 32.111-2 V4.1.X" for the case of Alarm Integration Reference Point (IRP): Information Service (IS).
+
+NOTE: that "X", rather than the actual digit, is actually used in the sentence. This is because the value of X is not relevant for the reference purpose since different values of X identify different 3GPP published specifications that reflect only editorial changes.
+
+# --- Annex B (normative): Technology specific rules & guidelines for CORBA Solution Sets
+
+## B.1 Rules
+
+### B.1.1 Introduction
+
+The intent of this annex is threefold.
+
+- 1) The first intent is for 3GPP internal use to document how a 3GPP CORBA SS is produced and how it is structured.
+- 2) The second intent with the annex is to give the reader or implementer of a CORBA SS a better understanding on how to interpret the CORBA SS specification.
+- 3) The third and maybe most important intent is to put requirement on an implementer of a CORBA SS.
+
+It is expected that this annex is to be extended in later versions of the present document.
+
+### B.1.2 Rules for specification of CORBA Solution Sets
+
+#### B.1.2.1 Introduction
+
+This subclause identifies rules for specification of CORBA SSs. This subclause is mainly for 3GPP-internal use. It is only for information for the implementer of a CORBA SS.
+
+#### B.1.2.2 Pragma prefix
+
+All IDL-code shall define the pragma prefix using the following statement:
+
+```
+#pragma prefix "3gppsa5.org"
+```
+
+See clause B.2.1.4.3 for information of this `#pragma` statement in relation to other IDL statements.
+
+### B.1.3 Implementation aspects of Interface IRP CORBA Solution Sets
+
+#### B.1.3.1 Introduction
+
+This subclause identifies rules for the implementation of CORBA SSs. This subclause is normative for the implementer of a CORBA SS.
+
+#### B.1.3.2 IRP Agent behaviour on incoming optional method
+
+The IRP Agent, claiming compliance to a particular SS version of a particular IRP such as the Alarm IRP, shall implement all Mandatory and all Optional methods. Each method implementation shall have a signature specifying all Mandatory and all Optional parameters.
+
+- If the IRP Agent does not support a particular optional method, it shall throw the `OperationNotSupportedException` when the IRP Manager invokes that method.
+- If the IRP Agent have not implemented a particular method (because it is compiled with an IDL version that does not define the method), the CORBA ORB of the IRP Agent shall throw a system exception if the IRP Manager invokes that method.
+
+In all the above cases when an exception is thrown, the IRP Agent shall restore its state before the method invocation.
+
+#### B.1.3.3 IRP Agent behaviour on incoming optional parameter of operation
+
+An IRP Agent must implement all optional parameters, as well as mandatory parameters, in all methods.
+
+If the IRP Agent supports the implemented method but does not support its (one or more) optional input parameters, upon method invocation, the IRP Agent shall check if those parameters carry "no information" or absence semantics (defined later in subclause B.1.3.5). If the check is negative, the IRP Agent shall throw the `ParameterNotSupportedException` exception with a string carrying the name of the unsupported optional parameter.
+
+#### B.1.3.4 IRP Agent behaviour on outgoing attributes of notification
+
+CORBA SS uses OMG defined structured event to carry notification. The structured event is partitioned into header and body.
+
+The absence semantics of attribute in the header is realized by a string of zero length.
+
+The body consists of one or more name-value pair attributes. The absence semantics of these attributes is realized by their absence.
+
+For optional sub-attributes of an attribute carried by the name-value pair, their absence semantics is realized by the encoding rule of "absence semantics". See subclause B.1.3.5.
+
+#### B.1.3.5 Encoding rule of absence semantics
+
+The operation parameters are mapped to method parameters of CORBA SS. The absence semantics for an operation (input and output) parameter is method parameter type dependent.
+
+- For a string type, if the parameter is specified as a string type, the absence semantics is a string of zero length. If the parameter is specified as a union structure (preferred), the absence semantics is conveyed via a `FALSE` Boolean value switch.
+- For an integer type, if the parameter is specified as a signed, unsigned, long, etc type, the absence semantics is the highest possible positive number. If the parameter is specified as a union structure (preferred), the absence semantics is conveyed via a `FALSE` Boolean value switch.
+- For a boxed `valueType` (supported by CORBA 2.3), it is the null value.
+
+The notification parameters are mapped to attributes of the CORBA Structured Events. The absence semantics for a notification parameter is attribute position (within the Structured Event) dependent.
+
+- For the fixed header of the Structured Event header, the absence semantics is realized by a string of zero length.
+- For the filterable body fields of the Structured Event body, the absence semantics is realized by the absence of the corresponding attribute.
+
+### B.1.4 Rules for NRM IRP CORBA SS extensions
+
+This clause discusses how the models and IDL definitions provided in a particular NRM IRP CORBA SS can be extended for a particular implementation and still remain compliant with IRP specifications.
+
+Note: Protocol-neutral rules for NRM IRP IS-level extensions are defined in TS 32.150 [3] Annex G.
+
+#### B.1.4.1 Allowed extensions
+
+Vendor-specific MOCs may be supported. The vendor-specific MOCs may support new types of attributes. The standardised notifications may be issued referring to the vendor-specific MOCs and vendor-specific attributes. New MOCs shall be distinguishable from standardised MOCs by name. Standardised and vendor-specific attributes may be used in vendor-specific MOCs. Vendor-specific attribute names shall be distinguishable from existing attribute names.
+
+MOCs may be subclassed. Subclassed MOCs shall maintain the specified behaviour of the superior classes. They may add vendor-specific behaviour with vendor-specific attributes. When subclassing, naming attributes cannot be changed. The subclassed MOC shall support all attributes of its superior class. Vendor-specific attributes cannot be added to MOCs without subclassing.
+
+When subclassing, the standardised containment rules and their specified cardinality shall still be followed. As an example, ManagementNode (or its subclasses) shall be contained under SubNetwork (or its subclasses).
+
+Managed Object Instances may be instantiated as CORBA objects. This requires that the MOCs be represented in IDL. MOCs are not currently specified in IDL, but may be specified in IDL for instantiation or subclassing purposes. However, management information models should not require that IRPManagers access the instantiated managed objects other than through supported methods in the present document.
+
+Extension rules related to notifications (Notification categories, Event Types, Extended Event Types etc.) are for further study.
+
+#### B.1.4.2 Extensions not allowed
+
+The IDL specifications in the present document cannot be edited or altered. Any additional IDL specifications shall be specified in separate IDL files.
+
+IDL interfaces (note: not MOCs) specified in the present document may not be subclassed or extended. New interfaces may be defined with vendor-specific methods.
+
+## --- B.2 Guidelines (Style Guide for CORBA SS IDL)
+
+This subclause describes the style guide for writing IDL statements for Interface IRP and NRM IRP. The guidelines are largely based on the OMG IDL Style Guide (OMG document: ab/98-06-03) [9] with extensions for IRP use.
+
+The guide sets out consistent naming, structural conventions and usage of SS interface for the IDL in IRP CORBA SS specifications.
+
+### B.2.1 Modules and File
+
+#### B.2.1.1 Use of Modules
+
+All declarations of IDL shall be contained in modules. No declarations of interfaces and definitions shall appear in the global scope.
+
+Nesting modules is a useful technique when dealing with large namespaces to avoid name clashes and clarify relationships. A module nested within another module shall not have the same name as a top-level module in any other IRP CORBA SS specification.
+
+#### B.2.1.2 File Names
+
+CORBA SS specifications contain IDL statements.
+
+The rule defined below specifies:
+
+- a) How to partition/extract these IDL statements to be placed in a file; and
+- b) How to name the file.
+
+Note that IDL uses "#include "X"" statement where X is a name of a file containing IDL statements.
+
+##### Rule:
+
+In the annex where IDL statements are defined, use a special marker to indicate that a set of IDL statements shall be contained in one file. The name of the file shall be the name of the first IDL module, concatenated with four characters ".idl". Within a CORBA SS, multiple markers (implying multiple files), can be used.
+
+It is not allowed to have an IDL module split into multiple files.
+
+#### B.2.1.3 Include Conventions
+
+All included IDL files shall be specified using the <...> form of #include. For example:
+
+```
+#include <ManagedGenericIRPConstDefs.idl>
+```
+
+#### B.2.1.4 File Structure
+
+##### B.2.1.4.1 File Internal Identification
+
+The first line of the IDL file shall contain ">//File:" followed by a single space followed by the name of the file. For example,
+
+```
+//File: ExampleIRPConstDefs.idl
+```
+
+##### B.2.1.4.2 File Guard
+
+An IDL file shall use a *guard* (consisting of three pre-processor lines) to avoid multiple definition errors. An example of a guard for the file called TestManagementIRPConstDefs.idl is:
+
+```
+#ifndef _TestManagementIRPConstDefs_idl_
+#define _TestManagementIRPConstDefs_idl_
+
+...remainder of the IDL
+
+#endif // _TestManagementIRPConstDefs_idl_
+```
+
+##### B.2.1.4.3 Required Contents
+
+If any other files are to be included, the #include statements come after the guard.
+
+After #include lines, if any, and immediately before the module statement, the following line shall appear:
+
+```
+#pragma prefix "3gppsa5.org"
+```
+
+##### B.2.1.4.4 Example illustrating a File Structure
+
+```
+//File: ExampleIRPConstDefs.idl
+#ifndef _EXAMPLE_IRP_CONST_DEFS_IDL_
+#define _EXAMPLE_IRP_CONST_DEFS_IDL_
+
+// This module describes/is part of...
+#include "ExampleIncludeOne.idl"
+#include "ExampleIncludeTwo.idl"
+
+#pragma prefix "3gppsa5.org"
+module ExampleIRPConstDefs {
+
+    // IDL Definitions here
+
+};
+
+#endif // _EXAMPLE_IRP_CONST_DEFS_IDL_
+```
+
+### B.2.2 Identifiers
+
+#### B.2.2.1 Mixed Case, Beginning Upper, No Underscores
+
+The following categories of identifiers follow the *Mixed Case, Beginning Upper, No Underscores* rules:
+
+- module
+- interface
+- typedef
+- Constructed types (struct, union, enum)
+- exception
+
+The "No underscores" rule is also applicable to all words that begin with an upper case letter with the remaining letters being lower case.
+
+As a further note on naming, it is not necessary to append the value "Type" to an identifier. The fact that it is a type is obvious from the consistent application of this naming convention.
+
+Examples:
+
+```
+module PMIRPConstDefs(...);  
+interface AttributeNameValue(...);
+```
+
+#### B.2.2.2 Lower Case with Underscores
+
+The following categories of identifiers follow the *Lower Case with Underscores* rules. All letters are lower case and words (if more than one) are separated with underscores.
+
+- Operation name and notification name
+- Attribute name
+- Parameter name
+- Structure member name
+
+Examples:
+
+```
+get_notification_categories(...);  
+string comment_text;  
+void get_alarm_count (... , out unsigned long critical_count, ..);  
+struct Comment { ...; string user_id; string system_id; ..};
+```
+
+#### B.2.2.3 Upper Case with Underscores
+
+The following categories of identifiers follow *Upper Case with Underscores* rules. All letters are in upper case and words have an underscore separating them.
+
+- Enum value
+- Constant
+
+Examples:
+
+```
+enum SubscriptionState {ACTIVE, SUSPENDED, INVALID};  
+const string JOB_ID = "JOB_ID";
+```
+
+#### B.2.2.4 Naming IDL Sequence Types
+
+Typically a new type declared as an IDL sequence of another type will have the text "List" appended to the name of the base type. Another convention is to declare such types as unordered sequences or ordered sets for consistency with ASN.1 notation. In this case they should have the "Seq" or "Set" (instead of "List") appended respectively.
+
+Example of an "ordered set":
+
+```
+typedef sequence <SubscriptionId> SubscriptionIdSet;
+```
+
+### B.2.3 Interface IRP
+
+Every Interface IRP should have 3 IDL modules (each specified in a separate IDL file):
+
+```
+module YyyIRPConstDefs {...}; // no change from Rel-5 practice.  
+  
+module YyyIRPSystem {...}; // no change from Rel-5 practice.  
+  
+module YyyIRPNotifications {...}; // new compared to Rel-5 practice
+```
+
+The first module defines all necessary IDL constructs, such as constant strings and type definitions, for the methods and notifications. The second module defines the methods. The third module defines the notifications.
+
+#### B.2.3.1 Constant String and Type Definitions
+
+This first module defines all necessary IDL constructs used by the methods (defined in the second module) and notifications (defined in the third module). The name of this module is YyyIRPConstDefs where Xxx is the name of the subject Interface IRP. An example is "PMIRPConstDefs".
+
+Within this module, define data types used in the methods.
+
+Also, define the data types of the attribute values used in the notifications.
+
+CORBA SS authors should always check the generic types defined in "ManagedGenericIRPConstDefs" before creating a new type.
+
+For the attribute names of the structured notifications, define an interface `AttributeNameValue` that captures the string definitions. Make sure these definitions do not clash with those defined for the notification header, i.e. notification id, event time, system DN, managed object class and managed object instance (see `NotificationIRPNotification::Notify`).
+
+An example from `PMIRPConstDefs`:
+
+```
+/**  
+ * This block identifies attributes which are included as part of the  
+ * PMIRP. These attribute values should not  
+ * clash with those defined for the attributes of notification  
+ * header (see IDL of Notification IRP).  
+ */  
+  
+interface AttributeNameValue  
+{  
+    const string JOB_ID = "JOB_ID";  
+    const string JOB_STATUS = "JOB_STATUS";  
+    const string REASON = "REASON";  
+    const string MONITOR_ID = "MONITOR_ID";  
+    const string MONITOR_STATUS = "MONITOR_STATUS";  
+};
+```
+
+#### B.2.3.2 Operations
+
+The second module defines the methods. The name of the module is `YyyIRPSystem` where `Yyy` is the name of the subject Interface IRP. An example is `AlarmIRPSystem`.
+
+At the beginning of this module, define all required exceptions. Naming conventions for exception are covered in B.2.2.1 above. CORBA SS authors should always check if the generic exceptions defined in the `ManagedGenericIRPSystem` can be reused before declaring new exception types.
+
+Then define one interface called `YyyIRP` encapsulating all methods of the subject `Yyy` Interface IRP. If the subject Interface IRP IS specifies that its `YyyIRP` inherits from `XxxIRP`, then reflect the inheritance relation in the interface definition. The following is an example of `AlarmIRP` that inherits from `ManagedGenericIRP`.
+
+```
+module AlarmIRPSystem
+{
+...
+...
+interface AlarmIRP : ManagedGenericIRPSystem:: ManagedGenericIRP {...};
+...
+};
+```
+
+Naming conventions for operations are covered in B.2.2.2 above.
+
+#### B.2.3.3 Notifications
+
+Use a separate module to define the notifications. The name the module is `YyyIRPNotifications` where `Yyy` is the name of the subject Interface IRP. Examples are `KernelCMIRPNotifications` and `PMIRPNotifications`.
+
+For `NotificationIRPNotifications`, do:
+
+- Define one IDL interface `Notify`. Capture the four constant strings that are the names of the four NV (name value) pairs of `filterable_body_field` of the CORBA structured event. These four CORBA NV pairs are mapped from the five notification header attributes (defined by the Notification IRP IS), i.e. the `objectClass`, `objectInstance`, `notificationId`, `eventTime` and `systemDN`.
+
+For `YyyIRPNotifications` where `Yyy` is not `Notification`, do:
+
+- At the beginning of this module, define the const strings for the notification types that correspond to the set of notifications specified by (and not inherited by and not imported by) the subject Interface IRP.
+- Then define a number of IDL interfaces corresponding to notifications specified in the subject Interface IRP. These interfaces should inherit from `NotificationIRPNotifications::Notify`. Within each interface, the first IDL statement defines the notification type (that is used as the second field of the fixed header of the structured notification). The second and subsequent IDL statements define the attribute names of this notification type, excepting those already defined by `NotificationIRPNotifications::Notify`. The data type of the attribute value, which is defined in `YyyIRPConstDefs`, should be mentioned in the comment block of this IDL statement.
+- Then define a number of IDL interfaces corresponding to notifications imported, if any. These interfaces should inherit from the imported interface. An example is `interface NotifyObjectCreation : KernelCMIRPNotifications:: NotifyObjectCreation`. Within this interface, define all necessary IDL constructs, if any, which are not defined in the imported interface. This interface may contain no IDL statement if the IDL constructs defined in the imported interface are sufficient. For each interface imported, insert a comment "The first field of this notification carries the IRPVersion of this CORBA SS."
+- There is no need to re-define interfaces for notifications that are already specified in other Interface IRP, and from which the subject IRP inherits.
+
+The following is an extract from `PMIRPNotifications`.
+
+```
+module PMIRPNotifications
+```
+
+```
+{  
+  
+    const string ET_MEASUREMENT_JOB_STATUS_CHANGED = "notifyMeasurementJobStatusChanged";  
+    const string ET_THRESHOLD_MONITOR_STATUS_CHANGED = "notifyThresholdMonitorStatusChanged";  
+  
+    interface NotifyMeasurementJobStatusChanged: NotificationIRPNotifications::Notify  
+    {  
+        const string EVENT_TYPE = ET_MEASUREMENT_JOB_STATUS_CHANGED;  
+  
+        /**  
+         * This constant defines the name of the jobId property,  
+         * which is transported in the filterable body fields.  
+         * The data type for the value of this property  
+         * is PMIRPConstDefs::JobIdType.  
+         */  
+        const string JOB_ID = PMIRPConstDefs::AttributeNameValue::JOB_ID;  
+  
+        ...  
+        ...  
+    };  
+  
+    interface NotifyXXX : NotificationIRPNotifications::Notify  
+    {  
+        ...  
+    };  
+  
+    ...  
+};
+```
+
+### B.2.4 NRM IRP
+
+Use one module to define the IDL constructs for the managed object classes. The name of this module is XxxNRIRPConstDefs where Xxx is the name of the subject NRM IRP.
+
+An example is UtranNRIRPConstDefs.
+
+Within the module, define a set of IDL interfaces each of which corresponds to a managed object class specified. The interface definition respects the inheritance relation specified.
+
+After the interface definition, the type definition for each attribute defined for the managed object class is defined (including inherited attributes). The type is defined in one of two ways:
+
+1. With a typedef of the type that matches the attribute definition in the NRM Information Object Class (IOC) mapping table, or
+2. With a CORBA IDL comment if the same attribute name is already defined in managed object classes already defined in this NRM.
+
+An example of managed object class RncFunction, which inherits from GenericNRIRPConstDefs::ManagedFunction, is shown below.
+
+```
+module UtranNRIRPConstDefs
+{
+  ...
+
+  /**
+   * Definitions for MO class RncFunction
+   */
+  interface RncFunction : GenericNRIRPConstDefs::ManagedFunction
+  {
+    const string CLASS = "RncFunction";
+
+    // Attribute Names
+    //
+    const string rncFunctionId = "rncFunctionId";
+
+    const string mcc= "mcc";
+    const string mnc= "mnc";
+    const string rncId= "rncId";
+  };
+
+  typedef string rncFunctionId;
+  typedef long mcc;
+  typedef long mnc;
+  typedef long rncId;
+  // userLabel
+
+  ...
+};
+```
+
+# --- Annex C (normative): Technology specific rules & guidelines for SOAP SSs
+
+## C.1 Rules
+
+### C.1.1 Introduction
+
+The intent of this annex is threefold.
+
+- 4) The first intent is for 3GPP internal use to document how a 3GPP SOAP SS is produced and how it is structured.
+- 5) The second intent with the annex is to give the reader or implementer of a SOAP SS a better understanding on how to interpret the SOAP SS specification.
+- 6) The third and maybe most important intent is to put requirement on an implementer of a SOAP SS.
+
+It is expected that this annex is to be extended in later versions of the present document.
+
+### C.1.2 Rules for specification of SOAP Solution Sets
+
+#### C.1.2.1 Introduction
+
+This subclause identifies rules for specification of SOAP SSs. This subclause is mainly for 3GPP-internal use. It is only for information for the implementer of a SOAP SS.
+
+#### C.1.2.2 File names
+
+The WSDL files should follow the naming convention:
+
+WSDLTarget.wsdl
+
+with:
+
+WSDLTarget being the text after the character '#' in the target namespace of the definitions
+
+Examples:
+
+If the 3GPP WSDL document contains
+
+<definitions ...
+
+targetNamespace="http://www.3gpp.org/ftp/specs/archive/32\_series/32.666#KernelCMIRPSystem">, then the WSDL filename shall be `KernelCMIRPSystem.wsdl`.
+
+If the WSDL document contains
+
+<definitions ... targetNamespace="http://www.3gpp.org/ftp/specs/archive/32\_series/32.111-6#AlarmIRPSystem">, then the WSDL filename shall be `AlarmIRPSystem.wsdl`.
+
+#### C.1.2.3 Void
+
+#### C.1.2.4 XML version encoding
+
+The first line of each wsdl and xsd file shall indicate the XML version and encoding. The supported XML version is 1.0 (refer to [15]) and encoding is UTF-8 (refer to [16]).
+
+Therefore, the wsdl and xsd files should begin with:
+
+<?xml version="1.0" encoding="UTF-8"?>
+
+#### C.1.2.5 Namespaces
+
+The WSDL namespace URI shall follow the naming convention:
+
+`http://www.3gpp.org/ftp/specs/archive/32_series/IRPNumber#ResourceName`
+
+with:
+
+- IRPNumber being the number before the 3GPP document version number, corresponding to the 3GPP document which describes the resource,
+- ResourceName being a mnemonic for the resource.
+
+Examples:
+
+If the 3GPP document "3GPP TS 32.111-7 V9.0.0 (2009-12)" describes the resource "AlarmIRPSystem", then the WSDL namespace URI shall be  
+[http://www.3gpp.org/ftp/specs/archive/32\\_series/32.111-7#AlarmIRPSystem](http://www.3gpp.org/ftp/specs/archive/32_series/32.111-7#AlarmIRPSystem)
+
+If the 3GPP document "3GPP TS 32.127 V9.0.0 (2009-12)" describes the resource "AAMIRPData", then the WSDL namespace URI shall be  
+[http://www.3gpp.org/ftp/specs/archive/32\\_series/32.127#AAMIRPData](http://www.3gpp.org/ftp/specs/archive/32_series/32.127#AAMIRPData)
+
+### C.1.3 Implementation aspects of Interface IRP SOAP Solution Sets
+
+#### C.1.3.1 Introduction
+
+This subclause identifies rules for the implementation of SOAP SSs. This subclause is normative for the implementer of a SOAP SS.
+
+#### C.1.3.n XXXX rule
+
+## C.2 Guidelines (Style Guide for SOAP SS WSDL)
+
+This subclause describes the style guide for writing WSDL documents for Interface IRP.
+
+The guide sets out consistent naming, structural conventions and usage of SS interface for the WSDL in IRP SOAP SS specifications.
+
+### C.2.1 File structure
+
+The structure of the wsdl file shall follow the W3C WSDL Document Structure defined in [10] specifications.
+
+#### C.2.1.1 Definitions
+
+*Guidelines for the Definitions section.*
+
+#### C.2.1.2 Namespaces
+
+*Guidelines for the Namespaces section.*
+
+#### C.2.1.3 Documentation
+
+*Guidelines for the optional Documentation section.*
+
+#### C.2.1.4 Types
+
+*Guidelines for Types*
+
+#### C.2.1.5 Message
+
+*Guidelines for Messages*
+
+#### C.2.1.6 Port type
+
+*Guidelines for Port types*
+
+#### C.2.1.7 Binding
+
+*Guidelines for Bindings*
+
+#### C.2.1.8 Port
+
+*Guidelines for Ports*
+
+#### C.2.1.9 Service
+
+*Guidelines for Services*
+
+### C.2.2 Identifiers
+
+#### C.2.2.n Rule n
+
+*Identify the categories of identifiers which follow the Rule n rules.*
+
+## C.3 XML Schema Guidelines
+
+This subclause describes the style guide for writing XML Schema for Operation/Notification messages and parameters to be imported into the WSDL file for the IRP SOAP SS specifications.
+
+### C.3.1 XSD guidelines for messages definition
+
+#### C.3.1.1 Request message
+
+*Guidelines for the Request message.*
+
+#### C.3.1.2 Response messages
+
+*Guidelines for the Response messages.*
+
+#### C.3.1.3 Fault messages
+
+*Guidelines for the Fault messages.*
+
+### C.3.2 XSD guidelines for parameters definition
+
+#### C.3.1.1 General guidelines
+
+*General guidelines for the parameters definitions.*
+
+#### C.3.1.1 Simple type definitions
+
+*Guidelines for the simple type definitions.*
+
+#### C.3.1.2 Complex type definition
+
+*Guidelines for the complex type.*
+
+### C.3.3 Identifiers
+
+The identifiers should follow the rules defined in paragraph C.2.2.
+
+# Annex D (normative): Technology specific rules & guidelines for XML specifications
+
+## D.1 Rules
+
+### D.1.1 XSD Use Cases
+
+#### D.1.1.1 Background
+
+3GPP defines a number of IOCs, say in Release-N. 3GPP also defines an XSD schema that can capture these IOCs, in Release-N.
+
+Release-N+1 authors can/may also extend these Release-N IOCs to capture the newly agreed capabilities and publish them as Release-N+1 IOCs. Authors also define a Release-N+1 XSD schema.
+
+The Use Cases here illustrate the capabilities of the Release-N+1 XSD schema.
+
+The "?" in the Use Case tables are for further study.
+
+#### D.1.1.2 Use Cases Set 1
+
+Suppose the old-XSD has SubNetwork (SN) containing ManagedElement (ME).
+
+Suppose the new-XSD has enhanced-SN containing enhanced-ME.
+
+Suppose we want the XML-instance-documents (doc-1, doc-2, etc) to contain instances as identified below:
+
+- Doc-1 has SN instance containing ME instances
+- Doc-2 has SN instance containing enhanced-ME instances
+- Doc-3 has SN instance containing ME instances and enhanced-ME instances
+- Doc-4 has enhanced-SN containing enhanced-ME instances
+- Doc-5 has enhanced-SN containing ME instances
+- Doc-6 has enhanced-SN containing enhanced-ME instances and ME instances
+
+Can a XML-instance-doc-creator (IRPAgent or IRPManager) produce the doc (column) using the XSD (row) identified?
+
+|         | Doc-1 | Doc-2 | Doc-3 | Doc-4 | Doc-5 | Doc-6 |
+|---------|-------|-------|-------|-------|-------|-------|
+| Old-XSD | ?     | ?     | ?     | ?     | ?     | ?     |
+| New-XSD | ?     | ?     | ?     | ?     | ?     | ?     |
+
+Can a XML-instance-doc-reader (IRPAgent or IRPManager) validate the doc (i.e. confirm that the document is well-formed) (column) using the XSD (row) identified?
+
+|         | Doc-1 | Doc-2 | Doc-3 | Doc-4 | Doc-5 | Doc-6 |
+|---------|-------|-------|-------|-------|-------|-------|
+| Old-XSD | ?     | ?     | ?     | ?     | ?     | ?     |
+| New-XSD | ?     | ?     | ?     | ?     | ?     | ?     |
+
+#### D.1.1.3 Use Cases Set 2
+
+Suppose one old-XSD has SubNetwork (SN) containing ManagedElement (ME) that in turn, contained an RNCFunction (RNC) defined by the other Old-XSD.
+
+Suppose the new-XSD has enhanced-SN containing enhanced-ME. Suppose also another new-XSD has enhanced-RNC.
+
+- Doc-7 has ME instance containing RNC instances
+- Doc-8 has ME instances containing enhanced-RNC instances
+- Doc-9 has ME instances containing RNC instances and enhanced-RNC instances
+- Doc-10 has enhanced-ME instances containing enhanced-RNC instances
+- Doc-11 has enhanced-ME instances containing RNC instances
+- Doc-12 has enhanced-ME instances containing RNC instances and enhanced-RNC instances
+
+Can a XML-instance-doc creator (IRP Agent or IRP Manager) produce the doc (column) using the XSD (row) identified?
+
+|         | Doc-7 | Doc-8 | Doc-9 | Doc-10 | Doc-11 | Doc-12 |
+|---------|-------|-------|-------|--------|--------|--------|
+| Old-XSD | ?     | ?     | ?     | ?      | ?      | ?      |
+| New-XSD | ?     | ?     | ?     | ?      | ?      | ?      |
+
+Can a reader (IRP Agent or IRP Manager) validate the doc (i.e. confirm that the document is well-formed) (column) using the XSD (row) identified?
+
+|         | Doc-1 | Doc-2 | Doc-3 | Doc-4 | Doc-5 | Doc-6 |
+|---------|-------|-------|-------|-------|-------|-------|
+| Old-XSD | ?     | ?     | ?     | ?     | ?     | ?     |
+| New-XSD | ?     | ?     | ?     | ?     | ?     | ?     |
+
+### D.1.2 Rules for NRM IRP XML specification extensions
+
+TBD
+
+### D.1.3 XML version encoding
+
+The first line of each XML schema description file shall indicate the XML version and encoding. The supported XML version is 1.0 (refer to [15]) and encoding is UTF-8 (refer to [16]).
+
+Therefore, the xsd files should begin with:
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+```
+
+## --- D.2 Guidelines
+
+TBD
+
+# Annex E (informative): Change history
+
+| Change history |       |           |     |     |                                                               |     |        |        |
+|----------------|-------|-----------|-----|-----|---------------------------------------------------------------|-----|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                               | Cat | Old    | New    |
+| Mar 2008       | SA_39 | SP-080070 | --  | --  | Submitted to SA#39 for Information                            | --  | --     | 1.0.0  |
+| Mar 2009       | SA-43 | SP-090057 | --  | --  | Submitted to SA for approval                                  | --  | 2.0.0  | 8.0.0  |
+| Dec 2009       | SA_46 | SP-090719 | 001 | --  | Discontinuation of the maintenance of WSDL/XML schema folders | F   | 8.0.0  | 9.0.0  |
+| Jun 2010       | SA_48 | SP-100264 | 002 | --  | New rule for WSDL namespace URIs                              | F   | 9.0.0  | 10.0.0 |
+| Sep 2010       | SA_49 | SP-100489 | 003 | --  | Change rule for WSDL filenames                                | F   | 10.0.0 | 10.1.0 |
+| Mar 2016       | SA_71 | SP-160032 | 007 | -   | Correctinjg references                                        | A   | 10.1.0 | 10.2.0 |

marked/Rel-10/32_series/32154/raw.md

@@ -0,0 +1,379 @@
+
+
+# Keywords GSM, UMTS, management **3GPP TS 32.154 V10.0.0 (2010-03)**
+
+*Technical Specification*
+
+## **3GPP** **3rd Generation Partnership Project;** Postal address **Technical Specification Group Services and System Aspects;** **Telecommunication management;** 3GPP support office address **Backward and Forward Compatibility (BFC);** 150 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 40 00 **Concept1**
+
+![LTE logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo](390120de4fe440c42fea8154fcaad334_img.jpg)
+
+3GPP logo
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+©2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- 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 BC between 3GPP TS 32-series specifications.....          | 6         |
+| 4.1 Prerequisite.....                                       | 6         |
+| 4.2 Rules.....                                              | 7         |
+| 5 BC context.....                                           | 8         |
+| 5.1 General .....                                           | 8         |
+| 5.2 IRP level.....                                          | 9         |
+| 5.3 IRP Agent level .....                                   | 10        |
+| 6 BC Recommendations.....                                   | 12        |
+| 6.1 Requirement .....                                       | 12        |
+| 6.2 IS-level .....                                          | 12        |
+| 6.3 SS-level .....                                          | 12        |
+| 6.3.1 CORBA .....                                           | 12        |
+| 6.3.2 Void .....                                            | 12        |
+| 6.3.3 File format description XML.....                      | 12        |
+| 6.3.4 File format description ASN.1 .....                   | 12        |
+| 6.3.5 SOAP .....                                            | 12        |
+| <b>Annex A (informative): BC and Conformance Tests.....</b> | <b>13</b> |
+| Annex B (informative): Change history.....                  | 14        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 Itf-N partitions two groups of interacting entities called IRPManager(s) and IRPAgent(s).
+
+The interactions between an IRPManager and IRPAgent are specified by the set of IRP specifications the IRPAgent supports, and which the IRPManager uses.
+
+Each YyyIRP (where "Yyy" stands for Alarm, BasicCM, etc.) permits a manager to, via `getIRPVersion`, inspect it's supported IRPVersion(s). Each such IRPVersion uniquely identifies one supported Interface IRP SS.
+
+Each YyyIRP may also permit an IRPManager to, via `getNRMIRPVersions`, inspect it's supported NRM IRPVersion(s). Each such IRPVersion uniquely identifies one supported NRM IRP SS.
+
+The 3GPP IRP specifications are expected to evolve. For example, 3GPP Release 6 specifications include more or modified features compared to the corresponding set in Release 5.
+
+An IRPManager and IRPAgent, with implementations conformant to the same IRP specification (at the same IRPVersion(s)) will be able to communicate.
+
+However, an upgrade of the IRPVersion, if not performed by both IRPAgent and IRPManager, can result in inter-working failure if Backward Compatibility (BC) issues are not addressed.
+
+The present document is applicable/relevant to a system context of a group of interacting IRPManagers and IRPAgents where some members are using one IRPVersion while others are using an upgraded IRPVersion.
+
+# --- 1 Scope
+
+The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
+
+The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
+
+Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.
+
+**Editor's Note:** The “forward compatibility” part is FFS.
+
+# --- 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 and/or edition number or version number) 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.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Element Manager (EM):** See 3GPP TS 32.101 [1].
+
+**IRPAgent:** See 3GPP TS 32.102 [2].
+
+**IRPManager:** See 3GPP TS 32.102 [2].
+
+**IRPVersion:** See "IRP document version number string" or "IRPVersion" in 3GPP TS 32.311 [4] clause 3.1.
+
+**Network Manager (NM):** See 3GPP TS 32.101 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                               |
+|-------|-----------------------------------------------|
+| ASN.1 | Abstract Syntax Notation One                  |
+| BC    | Backward Compatible or Backward Compatibility |
+
+|       |                                                       |
+|-------|-------------------------------------------------------|
+| CMIP  | Common Management Information Protocol                |
+| CORBA | Common Object Request Broker Architecture             |
+| EM    | Element Manager                                       |
+| IS    | Information Service                                   |
+| IRP   | Integration Reference Point                           |
+| NE    | Network Element                                       |
+| NM    | Network Manager                                       |
+| NRM   | Network Resource Model                                |
+| VSE   | Vendor Specific Extension (to 3GPP IRP specification) |
+| SS    | Solution Set                                          |
+| XML   | eXtensible Markup Language                            |
+
+# --- 4 BC between 3GPP TS 32-series specifications
+
+## 4.1 Prerequisite
+
+The words old and new, when qualifying an IRPVersion, refer to a single Interface IRPVersion of the same kind, e.g. Alarm IRP. They also refer to NRM IRPVersion of the same kind, e.g. Core NRM. The 'new' refers to a later release compared to the 'old'.
+
+The words old and new, when qualifying an IRPManager, refer to an entity that is using the old or the new (Interface or NRM) IRPVersion.
+
+The words old and new, when qualifying an IRPAgent, refer to an entity that contains an IRP that is supporting the old or the new (Interface or NRM) IRPVersion.
+
+In majority cases, an IRPAgent instance contains multiple IRPs, each of which is using a particular Interface IRPVersion. In these cases, each Recommendation statement should be repeated to cover all IRPs involved.
+
+The Recommendations do not imply that equipment vendors shall always supply their new IRPAgents in compliance to the solutions satisfying the Recommendations. The Recommendations simply identify the expected behaviours of a new system when it, claiming BC, interacts with an old system. Whether or not an IRPAgent should satisfy the Recommendations is a decision of the equipment vendor/supplier.
+
+The Recommendations do not imply that the next release of 3GPP Interface IRP or NRM IRP specification must be BC (to the older one). Whether or not a new release of an Interface IRP or NRM IRP should be BC to its older version is a decision of the 3GPP specification author, on a case-by-case basis.
+
+## 4.2 Rules
+
+[REC-1] An old IRPManager inter-operates with an old IRPAgent-A and a new IRPAgent-B.  
+The interaction shall be successful in that the IRPManager can obtain the network management services (capabilities and features) defined by the old IRPVersion from both IRPAgents.  
+The IRPManager needs not have knowledge of new network management services defined by the new IRPVersion.
+
+[REC-2] A new IRPManager inter-operates with a new IRPAgent-A and an old IRPAgent-B.  
+The interaction shall be successful in that the IRPManager can obtain the network management services defined by (a) the new IRPVersion from IRPAgent-A and (b) the old IRPVersion from IRPAgent-B.
+
+NOTE: If the next minor and/or major release of 3GPP Interface IRP or NRM IRP specification is BC (to the older one), one could reduce or eliminate the difficult coordination task to introduce IRPVersion upgrades in a large management domain containing multiple IRPManagers and IRPAgents.  
+It can be more cost-effective if IRPVersion upgrades to individual entity (i.e. IRPManager and IRPAgent) are done at different times.
+
+# 5 BC context
+
+## 5.1 General
+
+This clause defines the context under which the requirements specified in the present document are applicable.
+
+The word 'old' qualifies the related entity (i.e. the AlarmIRP of an IRPAgent instance or Alarm IRPManager) that is using an older 3GPP IRPVersion (called old version). The word 'new' qualifies the related entity that is using a newer (upgraded) 3GPP IRPVersion.
+
+EXAMPLE: A hypothetical 3GPP TS 32.123 V6.0.0 is considered the old version with reference to 3GPP TS 32.123 V6.1.0. The two versions in question can belong to the same or different major releases (e.g. Rel-5 or Rel-6).
+
+The box labelled EM in figure 5.1 conveys the same idea as the box of the same label in the System Context-A of other IRP specifications such as Alarm IRP IS 3GPP TS 32.111-2 [3].
+
+One or all EM-labelled boxes of figure 5.1 can be interchanged with the NE-labelled box (see System Context-B of other IRP specifications such as Alarm IRP IS 3GPP TS 32.111-2 [3]). The NE entities are not shown in order to make the figure easier to read.
+
+![Diagram of Overall BC System Context showing Old IRPManager (NM), New IRPManager (NM), Old IRPAgent (EM), and New IRPAgent (EM) connected by lines to a central vertical dashed line labeled Itf-N.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg)
+
+The diagram illustrates the 'Overall BC System Context'. It features four rectangular boxes arranged in a 2x2 grid, separated by a central vertical dashed line labeled 'Itf-N' at the top. The boxes are: 'Old IRPManager' (top-left), 'New IRPManager' (bottom-left), 'Old IRPAgent' (bottom-right), and 'New IRPAgent' (top-right). Below each box is a label: 'NM' for the IRPManagers and 'EM' for the IRPAgents. Lines connect each box to the central dashed line, crossing each other in the middle. Specifically, the top-left box connects to the bottom-right, and the bottom-left box connects to the top-right, both passing through the center of the dashed line.
+
+Diagram of Overall BC System Context showing Old IRPManager (NM), New IRPManager (NM), Old IRPAgent (EM), and New IRPAgent (EM) connected by lines to a central vertical dashed line labeled Itf-N.
+
+**Figure 5.1: Overall BC System Context**
+
+In general, an IRPAgent instance may contain several Interface YyyIRP instances and associated supporting Yyy NRM IRPs (where one IRP can be for example Alarm IRP, Test Management IRP, or "Notification IRP", etc and where the other IRP can be for example Generic IRP). The Interface and NRM YyyIRP specifications of particular IRPVersion(s) together specify the behaviour of an Interface IRP and the supporting NRM IRP (s).
+
+NOTE: The IRPVersion concept is related to the IRP.  
+The IRPVersion concept is not related to the IRPAgent as this may contain multiple IRPs.
+
+Given this background, the BC issues are addressed at two separate but related levels as described in clauses 5.2 and 5.3.
+
+## 5.2 IRP level
+
+The two diagrams here illustrate conceptually the two possible contexts when we address BC at this IRP level.
+
+![Figure 5.2: Specification BC System Context. Two diagrams showing interactions between IRPManagers and YyyIRP instances via an interface labeled Itf-N. The top diagram shows an 'Old IRPManager' (NM) and a 'New IRPManager' (NM) both connected to a 'YyyIRP IRPVersion-new' (EM) which is also connected to an 'IRP Agent'. The bottom diagram shows an 'Old IRPManager' (NM) connected to a 'YyyIRP IRPVersion-old' (EM) which is also connected to an 'IRP Agent'.](990567efebf979be51f56d1150012c9d_img.jpg)
+
+The diagram consists of two parts, top and bottom, separated by a horizontal dashed line labeled 'Itf-N'.
+
+**Top Diagram:** On the left, there are two boxes labeled 'Old IRPManager' and 'New IRPManager', both with a label 'NM' below them. Both boxes have lines connecting them to the 'Itf-N' interface. On the right, there is a large box labeled 'EM' containing two smaller boxes: 'YyyIRP IRPVersion-new' and 'IRP Agent'. The 'YyyIRP IRPVersion-new' box is connected to the 'Itf-N' interface and also connected to the 'IRP Agent' box.
+
+**Bottom Diagram:** On the left, there is a box labeled 'Old IRPManager' with a label 'NM' below it, connected to the 'Itf-N' interface. On the right, there is a large box labeled 'EM' containing two smaller boxes: 'YyyIRP IRPVersion-old' and 'IRP Agent'. The 'YyyIRP IRPVersion-old' box is connected to the 'Itf-N' interface and also connected to the 'IRP Agent' box.
+
+Figure 5.2: Specification BC System Context. Two diagrams showing interactions between IRPManagers and YyyIRP instances via an interface labeled Itf-N. The top diagram shows an 'Old IRPManager' (NM) and a 'New IRPManager' (NM) both connected to a 'YyyIRP IRPVersion-new' (EM) which is also connected to an 'IRP Agent'. The bottom diagram shows an 'Old IRPManager' (NM) connected to a 'YyyIRP IRPVersion-old' (EM) which is also connected to an 'IRP Agent'.
+
+**Figure 5.2: Specification BC System Context**
+
+An YyyIRP instance supports a particular Interface IRPVersion and a particular set of NRM IRPVersions.
+
+An IRPManager uses a particular Interface IRPVersion and a particular set of NRM IRPVersions.
+
+If an YyyIRP instance supports Interface IRPVersion-X and NRM IRPVersions-Y, then it can interact successfully with an IRPManager that uses the same IRPVersions. This is illustrated by the case of the "Old IRPManager" and the "Old IRP Agent" of the bottom diagram (and note that the diagram does not show the NRM IRP version support).
+
+If this same YyyIRP instance upgrades its Interface IRPVersion-X to X2 that is BC to X, then it can interact successfully with an IRPManager that uses the Interface IRPVersion-X or IRPVersion-X2. The top diagram of figure 5.2 illustrates this case (and note that the diagram does not show the NRM IRP version support).
+
+If this same YyyIRP instance upgrades its NRM IRPVersion-Y to Y2 that is BC to Y, then it can interact successfully with an IRPManager that uses the NRM IRPVersion-Y or NRM IRPVersion-Y2. The top diagram of figure 5.2 illustrated this case (and note that the diagram does not show the NRM IRP version support).
+
+Given the above, the BC issues addressed at the present document level are:
+
+- How to determine if an IRP IS or SS specification (Interface IRP or NRM IRP) is BC to an earlier version ? This can be addressed in another way. What are the BC-rules that the author of a 3GPP IRP specification should use to extend an old-version to produce a new version that can claim BC (to that old-version) ?
+
+At this level, the specification author shall define BC-rules for each of the following:
+
+- Interface IRP- Requirements.
+- Interface IRP IS.
+- Interface IRP SS(s).
+- NRM IRP requirements.
+- NRM IRP IS.
+- NRM IRP SS(s).
+- Data Definition IRP IS.
+- Data Definition IRP SS(s).
+
+One reason why the specification author addresses BC at this IRP level is that, for certain technologies, such as CORBA, it is possible that one entity using (compiles with) one IRP SS specification (i.e. the CORBA SS) while the other communicating entity using a new but BC version can interact successfully (such as the case of the IRPManager and IRPAgent-A of [REC-1]).
+
+## 5.3 IRPAgent level
+
+Figure 5.3 illustrates the two possible contexts when addressing BC at this IRPAgent level.
+
+![Figure 5.3: System/Implementation BC System Context. The diagram shows two contexts for BC at the IRPAgent level. The top context shows 'Old IRPManager' and 'New IRPManager' (both NM) connected via 'Itf-N' to a system containing 'YyyIRP IRPVersion-old' and 'YyyIRP IRPVersion-new' (both EM), each connected to an 'IRPAgent'. The bottom context shows 'Old IRPManager' (NM) connected via 'Itf-N' to a system containing 'YyyIRP IRPVersion-old' (EM) connected to an 'IRPAgent'.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+The diagram illustrates two system contexts for BC at the IRPAgent level, separated by a vertical dashed line labeled 'Itf-N'.
+
+**Top Context:** On the left, two boxes labeled 'Old IRPManager' and 'New IRPManager' are shown, each with a label 'NM' below it. Both are connected to the 'Itf-N' interface. On the right, a large box labeled 'EM' contains two boxes: 'YyyIRP IRPVersion-old' and 'YyyIRP IRPVersion-new'. Each of these boxes is connected to an 'IRPAgent' box. The 'Old IRPManager' is connected to the 'YyyIRP IRPVersion-old' box, and the 'New IRPManager' is connected to the 'YyyIRP IRPVersion-new' box.
+
+**Bottom Context:** On the left, a box labeled 'Old IRPManager' is shown with a label 'NM' below it, connected to the 'Itf-N' interface. On the right, a large box labeled 'EM' contains a box labeled 'YyyIRP IRPVersion-old', which is connected to an 'IRPAgent' box. The 'Old IRPManager' is connected to the 'YyyIRP IRPVersion-old' box.
+
+Figure 5.3: System/Implementation BC System Context. The diagram shows two contexts for BC at the IRPAgent level. The top context shows 'Old IRPManager' and 'New IRPManager' (both NM) connected via 'Itf-N' to a system containing 'YyyIRP IRPVersion-old' and 'YyyIRP IRPVersion-new' (both EM), each connected to an 'IRPAgent'. The bottom context shows 'Old IRPManager' (NM) connected via 'Itf-N' to a system containing 'YyyIRP IRPVersion-old' (EM) connected to an 'IRPAgent'.
+
+**Figure 5.3: System/Implementation BC System Context**
+
+NOTE 1: An IRPAgent instance contains multiple YyyIRP instances such as AlarmIRP, NotificationIRP, TestManagementIRP, etc. Each YyyIRP instance implements/supports the corresponding YyyIRP specification of a particular IRPVersion.
+
+Suppose IRPAgent-A contains YyyIRP of Interface IRPVersion-4, YyyIRP of Interface IRPVersion-5 and YyyIRP of Interface IRPVersion-6 and all IRPs support NRM IRPVersion-7 (see Note 2), this IRPAgent-A is BC if it can inter-operate successfully with the following:
+
+- IRPManager 1 using Interface IRPVersion-4 or 3 using NRM IRPVersion-7 or 6.
+- IRPManager 2 using Interface IRPVersion-5 or 4 using NRM IRPVersion-7 or 6.
+- IRPManager 3 using Interface IRPVersion-6 or 5 using NRM IRPVersion-7 or 6.
+
+NOTE 2: All IRPs contained by the same IRPAgent instance should support the same set of NRM IRPVersions.
+
+It is anticipated that the IRPAgent level BC solution includes:
+
+- An IRPAgent service allowing IRPManager to discover all the IRPAgent supported Interface IRPVersion(s).
+- An IRPAgent service allowing IRPManager to discover the IRPAgent supported NRM IRPVersion(s).
+- An IRPAgent service allowing IRPManager to discover the reference/address of the IRP instance (of the IRPAgent) supporting a particular Interface IRPVersion.
+
+The two diagrams in figure 5.3 illustrate the two possible ways to support BC at this so-called IRPAgent level.
+
+The IRPVersion-new needs not to be BC to IRPVersion-old. In the case that IRPVersion-new is BC to IRPVersion-old, it is EM supplier's choice if "IRP level" or "IRPAgent level" solution will be used to support BC. In the case that the IRPVersion-new is not BC to IRPVersion-old, then the EM supplier will have no choice but to use "IRPAgent level" solution if it wants its EM to support BC.
+
+NOTE 3: IRPAgent service supporting "discovery" (as stated by the above three bullets) is not illustrated in the two diagrams
+
+# --- 6 BC Recommendations
+
+## 6.1 Requirement
+
+The Requirement specification is in subclause 4.2 Rules.
+
+## 6.2 IS-level
+
+There is no text specifically written related to IS-level specification for BC systems. The two system context diagrams of subclauses 5.2 and 5.3 would be necessary and sufficient to describe the management services provided by EM to support the so-called Old IRPManager and New IRPManager.
+
+## 6.3 SS-level
+
+### 6.3.1 CORBA
+
+For CORBA Solution Set, the IRPAgent level (see subclause 5.3) context would be used.
+
+### 6.3.2 Void
+
+### 6.3.3 File format description XML
+
+*Editor's Note: This part is FFS.*
+
+### 6.3.4 File format description ASN.1
+
+*Editor's Note: This part is FFS.*
+
+### 6.3.5 SOAP
+
+*Editor's Note: This part is FFS.*
+
+# Annex A (informative): BC and Conformance Tests
+
+This annex illustrates that:
+
+- an IRP, implementing a new-version IRP specification that is BC to an old-version IRP specification, may or may not be compliant to the old-version IRP specification.
+
+![Diagram illustrating the BC and Conformance Tests Scenario. It shows two vertical paths. The left path starts with 'Old-version IRP specification' at the top, which 'extends, based on BC-Rules' to the 'New-version IRP specification' at the top right. Below the old specification is 'Old-IRP', connected by a downward 'implement' arrow. Below 'Old-IRP' is 'Conformance tests', connected by a downward 'test (should be OK)' arrow. A 'depend' arrow points from 'Conformance tests' up to 'Old-version IRP specification'. The right path starts with 'New-version IRP specification' at the top, with 'New-IRP' below it (connected by a downward 'implement' arrow), and 'Conformance tests' below that (connected by a downward 'test (should be OK)' arrow). A 'depend' arrow points from 'Conformance tests' up to 'New-version IRP specification'. A diagonal arrow labeled 'test (should fail)' points from the 'Old-IRP' box to the 'New-IRP' box.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+graph TD; OVI[Old-version IRP specification] -- "extend, based on BC-Rules" --> NVI[New-version IRP specification]; OVI -- "implement" --> OIRP[Old-IRP]; OIRP -- "test (should be OK)" --> CT1[Conformance tests]; CT1 -- "depend" --> OVI; NVI -- "implement" --> NIRP[New-IRP]; NIRP -- "test (should be OK)" --> CT2[Conformance tests]; CT2 -- "depend" --> NVI; OIRP -- "test (should fail)" --> NIRP;
+```
+
+Diagram illustrating the BC and Conformance Tests Scenario. It shows two vertical paths. The left path starts with 'Old-version IRP specification' at the top, which 'extends, based on BC-Rules' to the 'New-version IRP specification' at the top right. Below the old specification is 'Old-IRP', connected by a downward 'implement' arrow. Below 'Old-IRP' is 'Conformance tests', connected by a downward 'test (should be OK)' arrow. A 'depend' arrow points from 'Conformance tests' up to 'Old-version IRP specification'. The right path starts with 'New-version IRP specification' at the top, with 'New-IRP' below it (connected by a downward 'implement' arrow), and 'Conformance tests' below that (connected by a downward 'test (should be OK)' arrow). A 'depend' arrow points from 'Conformance tests' up to 'New-version IRP specification'. A diagonal arrow labeled 'test (should fail)' points from the 'Old-IRP' box to the 'New-IRP' box.
+
+**Figure A.1: BC and Conformance Tests Scenario**
+
+Suppose 3GPP has an older-version IRP specification (the "Old-version IRP specification" box) and there is a valid/correct implementation (the "Old-IRP" box).
+
+Suppose also that 3GPP produce a "New-version IRP specification" by extending the "Old-version IRP specification" using the BC-rules.
+
+The "New-IRP" should interwork with IRPManager that uses the "New-version IRP specification".
+
+This "New-IRP" should also interwork with IRPManager that uses the "Old-version IRP specification".
+
+The "Old-IRP" should pass the conformance test that is based on (see "depend" relation) the "Old-version IRP specification".
+
+Likewise, the "New-IRP" should pass the conformance test that is based on the "New-version IRP specification".
+
+However, this "New-IRP" may not be able to pass the conformance test that is based on "Old-version IRP specification" (see "test (should fail)" relation).
+
+Likewise, the "Old-IRP" should not be able to pass the conformance test that is based on "New-Version IRP specification".
+
+# --- Annex B (informative): Change history
+
+| Change history |       |           |     |     |                                        |         |       |        |
+|----------------|-------|-----------|-----|-----|----------------------------------------|---------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                        | Ca<br>t | Old   | New    |
+| Mar 2007       | SA_35 | SP-070065 | --  | --  | Submitted to TSG SA#35 for Information | --      | 1.0.0 |        |
+| Jun 2007       | SA_36 | SP-070283 | --  | --  | Submitted to TSG SA#36 for Approval    | --      | 2.0.0 | 7.0.0  |
+| Dec 2008       | SA_42 | --        | --  | --  | Upgrade to Release 8                   | -       | 7.0.0 | 8.0.0  |
+| Dec 2009       | -     | -         | -   | -   | Update to Rel-9 version (MCC)          | -       | 8.0.0 | 9.0.0  |
+| Mar 2010       | SA_47 | SP-100036 | 001 | --  | Introduction of SOAP SS                | C       | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32155/raw.md

@@ -0,0 +1,187 @@
+
+
+# Keywords GSM, UMTS, management 3GPP TS 32.155 V10.0.0 (2011-03)
+
+*Technical Specification*
+
+**3GPP**
+
+## Postal address: **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **Telecommunication management;** **Requirements**
+
+3GPP support office address  
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet  
+<http://www.3gpp.org>
+
+![LTE logo with '4ADVANCED' text above the 'e'](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e'
+
+![3GPP logo with a signal icon below the 'P'](4f4b52340aaccb1bcf733468dca9ee03_img.jpg)
+
+3GPP logo with a signal icon below the 'P'
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                                                    |   |
+|------------------------------------------------------------------------------------|---|
+| Foreword .....                                                                     | 4 |
+| Introduction .....                                                                 | 4 |
+| 1 Scope.....                                                                       | 5 |
+| 2 References.....                                                                  | 5 |
+| 3 Definitions, abbreviations .....                                                 | 5 |
+| 3.1 Definitions.....                                                               | 5 |
+| 3.2 Abbreviations .....                                                            | 5 |
+| 4 Requirements template.....                                                       | 6 |
+| 4.1 Template for high-level Requirements TSs .....                                 | 6 |
+| 4.2 Template for Integration Reference Point (IRP) specific Requirements TSs ..... | 6 |
+| Annex A (informative): Change history.....                                         | 8 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.150: Integration Reference Point (IRP) Concept and definitions
+- TS 32.151: Integration Reference Point (IRP) Information Service (IS) template
+- TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
+- TS 32.153: Integration Reference Point (IRP) technology specific templates
+- TS 32.154: Backward and Forward Compatibility (BFC); Concept and definitions
+- TS 32.155: Requirements template**
+
+# --- 1 Scope
+
+The present document contains the template to be used for the production of all Requirements TSs for the 3GPP Telecommunication management.
+
+This template is mainly based on the requirements template (mainly Annex A) in the ITU-T M.3020 recommendation [6].
+
+# --- 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.151: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template".
+- [6] ITU-T Recommendation M.3020 (07/2007): Management interface specification methodology.
+- [7] 3GPP TS 32.761: "E-UTRAN Network Resource Model (NRM) IRP; Requirements".
+- [8] ITU-T Recommendation [M.3020 \(2009\) Amendment 1](#): Management interface specification methodology - Simplified requirements template.
+
+# --- 3 Definitions, abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 32.101 [2], TS 32.102 [3], TS 32.150 [4], TS 32.151[5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 32.101 [2], TS 32.102 [3], 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].
+
+|     |                             |
+|-----|-----------------------------|
+| IRP | Integration Reference Point |
+| IS  | Information Service         |
+
+# --- 4 Requirements template
+
+This template is mainly based on the requirements template (mainly Annex A) in the ITU-T M.3020 recommendation [6], and shall be used for the production of all Requirements TSs for the 3GPP Telecommunication management. The template contains two options: Option 1 specified in subclause 4.1, which shall be used for all high-level Requirements TSs for the 3GPP Telecommunication management, and option 2 specified in subclause 4.2, which shall be used for all Integration Reference Point (IRP) specific Requirements TSs such as 3GPP TS 32.761 [7].
+
+The clauses in this template that shall be used in the Requirements TS are numbered starting with "X", which shall correspond to clause 4 that is the beginning of the main part of the TS, followed by "Y" which shall correspond to clause 5 in the TS, and "Z" (for the full template) which shall correspond to clause 6 in the TS.
+
+Instructions in *italics* below shall not be included in the Requirements TS.
+
+The introductory clauses (from clause 1 to clause 3) for the Requirements TS should be taken from the 3GPP TS template (i.e. not this requirements template) – see [http://www.3gpp.org/ftp/Information/TS\\_TR\\_Templates/](http://www.3gpp.org/ftp/Information/TS_TR_Templates/).
+
+Usage of fonts shall be according to the 3GPP TS template.
+
+## 4.1 Template for high-level Requirements TSs
+
+### --- X Concepts and background
+
+*"X" represents clause number 4 in the actual Requirements TS.*
+
+*For production of the contents of this clause, follow the instructions in M.3020 [6] subclause "A.2.1".*
+
+### --- Y Business level requirements
+
+*"Y" represents clause number 5 in the actual Requirements TS. For production of the contents of this subclause, follow the instructions in M.3020 [6] subclause "A.2.2".*
+
+### --- Z Specification level requirements
+
+*"Z" represents clause number 6 in the actual Requirements TS.*
+
+*For production of the contents of this subclause, follow the instructions in M.3020 [6] subclause "A.2.3".*
+
+## 4.2 Template for Integration Reference Point (IRP) specific Requirements TSs
+
+### --- X Concepts and background
+
+*"X" represents clause number 4 in the actual Requirements TS.*
+
+*For production of the contents of this clause, follow the instructions in M.3020 Amendment 1 [8] subclause "A.3.1".*
+
+### --- Y Requirements
+
+*"Y" represents clause number 5 in the actual Requirements TS. For production of the contents of this subclause, follow the instructions in M.3020 Amendment 1 [8] subclause "A.3.2".*
+
+# --- Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                              |         |       |        |
+|----------------|-------|-----------|------|-----|--------------------------------------------------------------|---------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                              | Ca<br>t | Old   | New    |
+| May 2007       | SA_36 | SP-070295 | --   | --  | Submitted to TSG SA#36 for Information                       | --      | 1.0.0 |        |
+| Sep 2007       | SA_37 | SP-070615 | --   | --  | Submitted to TSG SA#37 for Approval                          | --      | 2.0.0 | 8.0.0  |
+| Jun 2008       | SA_40 | SP-080329 | 0001 | -   | Correct the clause references to ITU-T Recommendation M.3020 | F       | 8.0.0 | 8.1.0  |
+| Dec 2008       | SA_42 | SP-080846 | 0002 | -   | Simplified requirements template for IRPs                    | F       | 8.1.0 | 8.2.0  |
+| Mar 2009       | SA-43 | SP-090207 | 0003 | --  | Simplified requirements template for IRPs                    | F       | 8.2.0 | 8.3.0  |
+| Dec 2009       | -     | -         | -    | -   | Update to Rel-9 version (MCC)                                | -       | 8.3.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -    | -   | Update to Rel-10 version (MCC)                               | -       | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32171/raw.md

@@ -0,0 +1,135 @@
+
+
+# Keywords subscription management **3GPP TS 32.171 V10.0.0 (2011-03)**
+
+*Technical Specification*
+
+## **3GPP** **3rd Generation Partnership Project;** Postal address **Technical Specification Group Services and System Aspects;** **Telecommunication management;** 3GPP support office address **Subscription Management (SuM) Network Resource Model** **(RM) Integration Reference Point (IRP)**
+
+![LTE logo with '4 ADVANCED' text above it.](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo with '4 ADVANCED' text above it.
+
+650 Route des Lucioles (Sophia Antipolis)  
+Valbonne - FRANCE  
+Tel.: +33 (0) 93 654 20 45 Fax: +33 (0) 93 654 20 33 E-mail: info@3gpp.org
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon.](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo with a signal icon.
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                            |   |
+|--------------------------------------------|---|
+| Foreword .....                             | 4 |
+| Introduction .....                         | 4 |
+| 1 Scope.....                               | 5 |
+| 2 References.....                          | 5 |
+| 3 Abbreviations .....                      | 5 |
+| 4 Requirements .....                       | 5 |
+| Annex A (informative): Change history..... | 6 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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
+
+Subscription Management is a feature that permits Service Providers, Value Added Service Providers and Mobile Operators to provision services for a specific subscriber. Subscription Management is an area of Service Operation Management that sets a complex challenge for Service Providers and Operators in their support of new or existing subscribers during their every day network operation.
+
+The present document is part a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
+
+- TS 32.140: "Subscription Management (SuM) requirements".
+- TS 32.141: "Subscription Management (SuM) architecture".
+- TS 32.171: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements".**
+- TS 32.172: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
+- TS 32.176: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions".
+
+# --- 1 Scope
+
+The present document defines, in addition to the requirements defined in [1], [2], [3] and [4], requirements for the present SuM NRM IRP.
+
+# --- 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.140: "Telecommunication management; Subscription Management (SuM) requirements".
+- [5] 3GPP TS 32.141: "Telecommunication management; Subscription Management (SuM) architecture".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                             |
+|-----|-----------------------------|
+| IRP | Integration Reference Point |
+| NRM | Network Resources Model     |
+| SuM | Subscription Management     |
+
+# --- 4 Requirements
+
+The following general and high-level requirements apply for the present IRP:
+
+- a) IRP-related requirements in 3GPP TS 32.101 [1].
+- b) IRP-related requirements in 3GPP TS 32.102 [2].
+- c) IRP-related requirements in 3GPP TS 32.140 [3].
+- d) IRP-related requirements in 3GPP TS 32.141 [4].
+
+# --- Annex A (informative): Change history
+
+| Change history |       |           |     |     |                                                                                                                                               |       |        |
+|----------------|-------|-----------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                                                                                                               | Old   | New    |
+| Dec 2003       | SA 22 | SP-030616 | --  | --  | Submitted to TSG SA#22 for Information                                                                                                        | 1.0.0 |        |
+| Jun 2004       | SA 24 | SP-040238 | --  | --  | Submitted to TSG SA#24 for Approval                                                                                                           | 2.0.0 | 6.0.0  |
+| Dec 2004       | SA_26 | SP-040764 | 001 | --  | Editorial modifications to "Subscription Management (SuM)<br>Network Resource Model (NRM) Integration Reference Point (IRP):<br>Requirements" | 6.0.0 | 6.1.0  |
+| Jun 2007       | SA 36 | --        | --  | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7.                                                                                        | 6.1.0 | 7.0.0  |
+| Dec 2008       | SA 42 | --        | --  | --  | Upgrade to Release 8                                                                                                                          | 7.0.0 | 8.0.0  |
+| Dec 2009       | -     | -         | -   | -   | Update to Rel-9 version (MCC)                                                                                                                 | 8.0.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -   | -   | Update to Rel-10 version (MCC)                                                                                                                | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32176/raw.md

@@ -0,0 +1,1856 @@
+
+
+Keywords  
+UMTS, Management
+
+# 3GPP TS 32.176 V10.3.0 (2011-03)
+
+*Technical Specification*
+
+**3rd Generation Partnership Project;**  
+**Technical Specification Group Services and System Aspects;**  
+**Telecommunication management;**  
+**Subscription Management (SuM)**  
+**Network Resource Model (NRM)**  
+**Integration Refere**  
+**Solution Set**
+
+![LTE logo with '4ADVANCED' text above the 'e' and a signal icon.](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e' and a signal icon.
+
+Postal address  
+3GPP support office address  
+630 Route des Lucioles - Les Algorithmes  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 92 94 47 10  
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon below the 'P'.](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo with a signal icon below the 'P'.
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- 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 Solution Set Definitions .....                   | 6        |
+| <b>Annex A (normative): XML Definitions.....</b>   | <b>7</b> |
+| A.1 Architectural features.....                    | 7        |
+| A.1.1 Syntax for Distinguished Names.....          | 7        |
+| A.2 Mapping .....                                  | 7        |
+| A.2.1 General mapping .....                        | 7        |
+| A.2.2 Information Object Class (IOC) mapping ..... | 7        |
+| A.3 Solution Set definitions .....                 | 8        |
+| A.3.1 XML definition structure .....               | 8        |
+| A.3.2 Graphical Representation.....                | 8        |
+| A.3.3 XML schema "sumNrm.xsd" .....                | 9        |
+| Annex B (informative): Change history.....         | 28       |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.140: "Subscription Management (SuM) requirements".
+- TS 32.141: "Subscription Management (SuM) architecture".
+- TS 32.171: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements ".
+- TS 32.172: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
+- TS 32.176: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions".**
+
+Subscription Management (SuM) is a feature that permits Service Providers, Value Added Service Providers and Mobile Operators to provision services for a specific subscriber. The feature is necessary to allow Service Providers and Operators to provision, control, monitor, and bill the configuration of services that they offer to their subscribers. SuM focuses on the OAM processes to manage subscription information. The overall SuM requirements and architecture are detailed in 3GPP TS 32.140 [2] and 3GPP TS 32.141 [3].
+
+The Itf-N interface for Subscription Management is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 [1]. For SuM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as other technical specifications for telecom management produced by 3GPP.
+
+# --- 1 Scope
+
+The present document is part of an Integration Reference Point (IRP) named Subscription Management (SuM) Network Resource Model (NRM) IRP, through which an `IRPAgent` can communicate configuration management information to one or several `IRPManagers` concerning SuM resources. The SuM NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
+
+The present document specifies the Solution Sets for the SuM NRM IRP.
+
+This specification is related to 3GPP TS 32.172 [5] V10.2.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 TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [2] 3GPP TS 32.140: "Telecommunication management; Subscription Management (SuM) requirements".
+- [3] 3GPP TS 32.141: "Telecommunication management; Subscription Management (SuM) architecture".
+- [4] 3GPP TS 32.171: "Telecommunication management; Subscription Management (SuM) resources Integration Reference Point (IRP); Requirements".
+- [5] 3GPP TS 32.172: "Telecommunication management; Subscription Management Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
+- [6] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [7] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [8] 3GPP TS 32.616: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [9] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions in 3GPP TS 32.101 [6], TS 32.102 [7], TS 32.140 [2], TS 32.141 [3], TS 32.171 [4] and TS 32.172 [5] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations in 3GPP TS 32.101 [6], TS 32.102 [7], TS 32.140 [2], TS 32.141 [3], TS 32.171 [4] and TS 32.172 [5] apply.
+
+# --- 4 Solution Set Definitions
+
+This specification defines the following 3GPP SuM NRM IRP Solution Set Definitions:
+
+- 3GPP SuM NRM IRP XML Definitions (Annex A)
+
+CORBA Solution Set is not supported.
+
+# --- Annex A (normative): XML Definitions
+
+This annex contains the XML Definitions for the SuM NRM IRP as it applies to Itf-N, in accordance with SuM NRM IRP Information Service (TS 32.172 [5])
+
+---
+
+## A.1 Architectural features
+
+The overall architectural feature of Subscription Management (SuM) resources is specified in 3GPP TS 32.172 [5]. This clause specifies features that are specific to the Schema definitions.
+
+### A.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [9].
+
+---
+
+## A.2 Mapping
+
+### A.2.1 General mapping
+
+An IOC maps to an XML element of the same name as the IOC's name in the IS. An IOC attribute maps to a sub-element of the corresponding IOC's XML element, and the name of this sub-element is the same as the attribute's name in the IS.
+
+### A.2.2 Information Object Class (IOC) mapping
+
+Not present in the current version of this specification.
+
+## --- A.3 Solution Set definitions
+
+### A.3.1 XML definition structure
+
+The overall description of the file format of configuration data XML files is provided by 3GPP TS 32.616 [8].
+
+Annex A.3.3 of the present document defines the NRM-specific XML schema `sumNrm.xsd` for the Subscription Management IRP NRM defined in 3GPP TS 32.172 [5].
+
+XML schema `sumNrm.xsd` explicitly declares NRM-specific XML element types for the related NRM.
+
+The definition of those NRM-specific XML element types complies with the generic mapping rules defined in 3GPP TS 32.616 [8].
+
+### A.3.2 Graphical Representation
+
+Not present in the current version of this specification.
+
+### A.3.3 XML schema "sumNrm.xsd"
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+  3GPP TS 32.176 SuM Network Resources IRP
+  SuM NRM-specific XML schema
+  sumNrm.xsd
+-->
+
+<schema
+  targetNamespace=
+  "http://www.3gpp.org/ftp/specs/archive/32_series/32.176#sumNrm"
+  elementFormDefault="qualified"
+  xmlns="http://www.w3.org/2001/XMLSchema"
+  xmlns:sn=
+  "http://www.3gpp.org/ftp/specs/archive/32_series/32.176#sumNrm"
+  xmlns:xn=
+  "http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"
+>
+
+  <import
+    namespace=
+    "http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"
+  />
+
+  <!-- SuM Network Resources IRP NRM class associated XML elements -->
+
+  <element
+    name="SubscriptionFunction"
+    substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass"
+  >
+    <complexType>
+      <complexContent>
+        <extension base="xn:NrmClass">
+          <sequence>
+            <element name="attributes" minOccurs="0">
+              <complexType>
+                <all>
+                  <element name="userLabel"/>
+                  <element name="theUser" type="xn:dnList"/>
+                  <element name="theSubscriberProfile" type="xn:dnList"/>
+                </all>
+              </complexType>
+            </element>
+          </sequence>
+        </extension>
+      </complexContent>
+    </complexType>
+  </element>
+  <element name="SuMSubscriberProfile" substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+    <complexType>
+      <complexContent>
+        <extension base="xn:NrmClass">
+          <sequence>
+            <element name="attributes" minOccurs="0">
+              <complexType>
+                <all>
+                  <element name="suMSubscriberProfileInfo"/>
+                  <element name="theUser" type="xn:dnList"/>
+                  <element name="theSubscribedService" type="xn:dnList"/>
+                  <element name="theMobileUserData" type="xn:dnList"/>
+                </all>
+              </complexType>
+            </element>
+          </sequence>
+        </extension>
+      </complexContent>
+    </complexType>
+  </element>
+  <element name="MobileUserData" substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+    <complexType>
+      <complexContent>
+        <extension base="xn:NrmClass">
+          <sequence>
+            <element name="attributes" minOccurs="0">
+              <complexType>
+                <all>
+                  <element name="theServiceProfile" type="xn:dnList"/>
+                </all>
+              </complexType>
+            </element>
+          </sequence>
+        </extension>
+      </complexContent>
+    </complexType>
+  </element>
+</schema>
+```
+
+```
+
+        <element name="iMSI" type="string"/>
+        <element name="mSISDN" type="string"/>
+        <element name="multinumberingMSISDNs" type="sn:multinumberingMSISDNList"/>
+        <element name="IMEISV" type="string" minOccurs="0"/>
+      </all>
+    </complexType>
+  </element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element name="SuMUser" substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theMobileUserData" type="xn:dnList"/>
+                <element name="theSubscriber" type="xn:dnList" minOccurs="0"/>
+                <element name="theCredentials" type="xn:dnList"/>
+                <element name="theServiceProfile" type="xn:dnList"/>
+                <element name="theIdentity" type="xn:dnList" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="SuMCredentials" substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="thePublicId" type="xn:dnList"/>
+                <element name="theServiceProfile" type="xn:dnList"/>
+                <element name="iMSPrivateUserIdentity" type="string"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="SuMService" type="xn:NrmClass" abstract="true"
+substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass"/>
+
+<element
+  name="CSService"
+  substitutionGroup="sn:SuMService"
+>
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theContract" minOccurs="0"/>
+                <element name="networkAccessMode"/>
+                <element name="basicMSISDNIndicator" minOccurs="0"/>
+                <element name="mSISDNAlertIndicator" minOccurs="0"/>
+                <element name="subscriptionRestriction" minOccurs="0"/>
+                <element name="rSZIlists" minOccurs="0"/>
+                <element name="LSAIdentity" minOccurs="0"/>
+                <element name="LSAPriority" minOccurs="0"/>
+                <element name="LSAPreferentialAccessIndicator" minOccurs="0"/>
+                <element name="LSAActiveModeSupportIndicator" minOccurs="0"/>
+
+```
+
+```
+
+<element name="lSAOnlyAccessIndicator" minOccurs="0"/>
+<element name="lSAActiveModeIndicator" minOccurs="0"/>
+<element name="vPLMNIdentifier" minOccurs="0"/>
+<element name="accessRestrictionData" minOccurs="0"/>
+<element name="privacyExceptionList" minOccurs="0"/>
+<element name="gMLCNumbers" minOccurs="0"/>
+<element name="mOLRList" minOccurs="0"/>
+<element name="serviceTypes" minOccurs="0"/>
+<element name="mobileStationCategory" minOccurs="0"/>
+<element name="lMUIdentifier" minOccurs="0"/>
+<element name="subscriberStatus" minOccurs="0"/>
+<element name="gsmSCFaddresslistForODB"/>
+<element name="provisionOfBearerService"/>
+<element name="provisionOfTeleservice"/>
+<element name="bCAllocation" minOccurs="0"/>
+<element name="barringOfOutgoingCalls" minOccurs="0"/>
+<element name="barringOfIncomingCalls" minOccurs="0"/>
+<element name="barringOfRoaming" minOccurs="0"/>
+<element name="barringOfPremiumRateCalls" minOccurs="0"/>
+<element
+  name="barringOfSupplementaryServiceManagement"
+  minOccurs="0"
+/>
+<element
+  name="barringOfRegistrationOfCallForwarding"
+  minOccurs="0"
+/>
+<element
+  name="barringOfInvocationOfCallTransfer"
+  minOccurs="0"
+/>
+<element
+  name="operatorDeterminedBarringPLMNSpecificData"
+  minOccurs="0"
+/>
+<element name="vGCSGroupMembershipList" minOccurs="0"/>
+<element name="vBSGroupMembershipList" minOccurs="0"/>
+<element
+  name="broadcastCallInitiationAllowedList"
+  minOccurs="0"
+/>
+<element
+  name="originatingCAMELSubscriptionInformationOCSI"
+  minOccurs="0"
+/>
+<element
+  name="terminatingCAMELSubscriptionInformationTCSI"
+  minOccurs="0"
+/>
+<element
+  name="vMSCTerminatingCAMELSubscriptionInformationVTCSCI"
+  minOccurs="0"
+/>
+<element
+  name="locationInformationSubscriberStateInformation"
+  minOccurs="0"
+/>
+<element
+  name="uSSDCAMELSubscriptionInformationUCSCI"
+  minOccurs="0"
+/>
+<element name="sSInvocationNotificationSSCSI" minOccurs="0"/>
+<element
+  name="translationInformationFlagTIFCSI"
+  minOccurs="0"
+/>
+<element
+  name="dialledServiceCAMELSubscriptionInformationDCSCI"
+  minOccurs="0"
+/>
+<element
+  name="uSSDGeneralCAMELServiceInformationUGCSI"
+  minOccurs="0"
+/>
+<element
+  name="shortMessageServiceCAMELSubscriptionInformationMOSMSCSCI"
+  minOccurs="0"
+/>
+<element
+  name="shortMessageServiceCAMELSubscriptionInformationMTSMSCSCI"
+
+```
+
+```
+
+        minOccurs="0"
+    />
+    <element
+        name="mTSMSCSIVLRNegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+    />
+    <element name="gsmSCFaddressforCSI" minOccurs="0"/>
+    <element name="iSTAlertTimer" minOccurs="0"/>
+    <element name="cSAllocationRetentionpriority" minOccurs="0"/>
+    <element name="iCSIndicator" minOccurs="0"/>
+    <element name="theCSSupplServiceForCS" type="xn:dnList"/>
+    </all>
+</complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+<element name="SuMCSupplService"
+    substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+    <complexType>
+        <complexContent>
+            <extension base="xn:NrmClass">
+                <sequence>
+                    <element name="attributes" minOccurs="0">
+                        <complexType>
+                            <all>
+                                <element name="sS-Code"/>
+                                <element name="provisioningState"/>
+                                <element name="activationState"/>
+                                <element name="registrationState" minOccurs="0"/>
+                                <element name="overrideCategory" minOccurs="0"/>
+                                <element name="cLIRestrictionOption" minOccurs="0"/>
+                                <element name="forwarded-toNumber" minOccurs="0"/>
+                                <element name="forwarded-toSubaddress" minOccurs="0"/>
+                                <element name="noReplyConditionTimer" minOccurs="0"/>
+                                <element name="maximumEntitledPriority" minOccurs="0"/>
+                                <element name="defaultPriority" minOccurs="0"/>
+                                <element name="nbrUser" minOccurs="0"/>
+                                <element name="nbrSB" minOccurs="0"/>
+                            </all>
+                        </complexType>
+                    </element>
+                </sequence>
+            </extension>
+        </complexContent>
+    </complexType>
+</element>
+
+<element
+    name="GPRSService"
+    substitutionGroup="sn:SuMService"
+>
+    <complexType>
+        <complexContent>
+            <extension base="xn:NrmClass">
+                <sequence>
+                    <element name="attributes" minOccurs="0">
+                        <complexType>
+                            <all>
+                                <element name="theContract" minOccurs="0"/>
+                                <element name="networkAccessMode" minOccurs="0"/>
+                                <element name="basicMSISDNIndicator" minOccurs="0"/>
+                                <element name="mSISDNAlertIndicator" minOccurs="0"/>
+                                <element name="rSZIlists" minOccurs="0"/>
+                                <element name="lSAIdentity" minOccurs="0"/>
+                                <element name="lSAPriority" minOccurs="0"/>
+                                <element name="lSAPreferentialAccessIndicator" minOccurs="0"/>
+                                <element name="lSAActiveModeSupportIndicator" minOccurs="0"/>
+                                <element name="lSAOnlyAccessIndicator" minOccurs="0"/>
+                                <element name="lSAActiveModeIndicator" minOccurs="0"/>
+                                <element name="vPLMNIdentifier" minOccurs="0"/>
+                                <element name="accessRestrictionData" minOccurs="0"/>
+                                <element name="privacyExceptionList" minOccurs="0"/>
+                                <element name="gMLCNumbers" minOccurs="0"/>
+                                <element name="mOLRList" minOccurs="0"/>
+                                <element name="serviceTypes" minOccurs="0"/>
+                                <element name="gGSNNumber" minOccurs="0"/>
+                            </all>
+                        </complexType>
+                    </element>
+                </sequence>
+            </extension>
+        </complexContent>
+    </complexType>
+</element>
+
+```
+
+```
+
+<element name="provisionOfTeleservice" minOccurs="0"/>
+<element name="subscriberStatus" minOccurs="0"/>
+<element name="transferOfSMoption" minOccurs="0"/>
+<element
+  name="barringOfPacketOrientedServices"
+  minOccurs="0"
+/>
+<element name="pDPType" minOccurs="0"/>
+<element name="pDPAddress" minOccurs="0"/>
+<element name="accessPointName" minOccurs="0"/>
+<element name="vPLMNAddressAllowed" minOccurs="0"/>
+<element name="qualityOfServiceSubscribed" minOccurs="0"/>
+<element
+  name="pDPContextChargingCharacteristics"
+  minOccurs="0"
+/>
+<element
+  name="gPRSCAMELSubscriptionInformationGPRSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mOShortMessageServiceCAMELSubscriptionInformationMOSMSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mTShortMessageServiceCAMELSubscriptionInformationMTMSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mOSMSCSISGSNNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="mTSMSCSISGSNNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="mobilityManagementforGPRSeventnotificationMGCSI"
+  minOccurs="0"
+/>
+<element
+  name="mGCSINegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element name="gsmSCFaddressforCSI" minOccurs="0"/>
+<element
+  name="subscribedChargingCharacteristics"
+  minOccurs="0"
+/>
+<element name="closedSubscriberGroupInformation" minOccurs="0"/>
+<element name="gSMSCFaddresslistForODB" minOccurs="0"/>
+<element name="barringOfOutgoingCalls" minOccurs="0"/>
+<element name="barringOfRoaming" minOccurs="0"/>
+<element name="operatorDeterminedBarringPLMNSpecificData" minOccurs="0"/>
+<element name="sTNSR" minOccurs="0"/>
+<element name="iCSIndicator" minOccurs="0"/>
+<element
+  name="listOfauthorizedvisitednetworkidentifiers"
+  minOccurs="0"
+/>
+<element name="wLANUERemoteIPaddress" minOccurs="0"/>
+<element name="staticWLANUERemoteIPaddressList" minOccurs="0"/>
+<element name="w-APNBarringTypeList" minOccurs="0"/>
+<element name="w-APNChargingDataList" minOccurs="0"/>
+<element name="accessDependenceFlag" minOccurs="0"/>
+<element name="chargingCharacteristics" minOccurs="0"/>
+<element name="primaryOCSChargingFunctionName" minOccurs="0"/>
+<element
+  name="secondaryOCSChargingFunctionName"
+  minOccurs="0"
+/>
+<element
+  name="primaryChargingCollectionFunctionName"
+  minOccurs="0"
+/>
+<element
+  name="secondaryChargingCollectionFunctionName"
+  minOccurs="0"
+/>
+<element name="w-APNIdentifierList" minOccurs="0"/>
+
+```
+
+```
+
+        <element name="maxNumberAccessesList" minOccurs="0"/>
+        <element name="subscribed3GPPWLANQoSProfile" minOccurs="0"/>
+        <element name="maxSubscribedBandwidth" minOccurs="0"/>
+        <element name="theGPRSSupplServiceForGPRS" type="xn:dnList"/>
+      </all>
+    </complexType>
+  </element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element name="SuMGPRSSupplService"
+  substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="sS-Code" minOccurs="0"/>
+                <element name="provisioningState" minOccurs="0"/>
+                <element name="activationState" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="EPSService" substitutionGroup="sn:SuMService">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theContract" minOccurs="0"/>
+                <element name="accessPointName" minOccurs="0"/>
+                <element name="accessRestrictionData" minOccurs="0"/>
+                <element name="aPNAMBR" minOccurs="0"/>
+                <element name="barringOfPacketOrientedServices" minOccurs="0"/>
+                <element name="contextIdentifier" minOccurs="0"/>
+                <element name="operatorDeterminedBarringPLMNSpecificData" minOccurs="0"/>
+                <element name="pDNAddress" minOccurs="0"/>
+                <element name="rSZILists" minOccurs="0"/>
+                <element name="sTNSR" minOccurs="0"/>
+                <element name="subscribedChargingCharacteristics" minOccurs="0"/>
+                <element name="subscriberStatus" minOccurs="0"/>
+                <element name="networkAccessMode" minOccurs="0"/>
+                <element name="barringOfOutgoingCalls" minOccurs="0"/>
+                <element name="barringOfRoaming" minOccurs="0"/>
+                <element name="privacyExceptionList" minOccurs="0"/>
+                <element name="gMLCNumbers" minOccurs="0"/>
+                <element name="mOLRList" minOccurs="0"/>
+                <element name="serviceTypes" minOccurs="0"/>
+                <element name="iCSIndicator" minOccurs="0"/>
+                <element name="aPNOIReplacement" minOccurs="0"/>
+                <element name="subscribedUEAMBR" minOccurs="0"/>
+                <element name="aPNConfigurationProfile" minOccurs="0"/>
+                <element name="rFSP" minOccurs="0"/>
+                <element name="vPLMNAddressAllowed-EPS" minOccurs="0"/>
+                <element name="pDNGWIdentity" minOccurs="0"/>
+                <element name="ePSPDNConnectedChargingCharacteristics" minOccurs="0"/>
+                <element name="pDNGWAllocationType" minOccurs="0"/>
+                <element name="aPNLevelAPNOIReplacement" minOccurs="0"/>
+                <element name="closedSubscriberUserGroupInformation" minOccurs="0"/>
+                <element name="listOfAuthorizedvisitednetowrkidentifiers" minOccurs="0"/>
+                <element name="staticWLANUERemoteIPAddressList" minOccurs="0"/>
+                <element name="w-APONBarringTypeList" minOccurs="0"/>
+                <element name="w-APNChargingDataList" minOccurs="0"/>
+                <element name="wLANUERemoteIPAddress" minOccurs="0"/>
+                <element name="accessDependenceFlag" minOccurs="0"/>
+                <element name="chargingCharacteristics" minOccurs="0"/>
+                <element name="primaryOCSChargingFunctionName" minOccurs="0"/>
+                <element name="secondaryOCSChargingFunctionName" minOccurs="0"/>
+
+```
+
+```
+
+      <element name="primaryChargingCollectionFunctionName" minOccurs="0"/>
+      <element name="secondaryChargingCollectionFunctionName" minOccurs="0"/>
+      <element name="w-APNIdentifierList" minOccurs="0"/>
+      <element name="maxNumberAccessesList" minOccurs="0"/>
+      <element name="maxSubscribedBandwidth" minOccurs="0"/>
+      <element name="subscribed3GPPWLANQoSProfile" minOccurs="0"/>
+      <element name="permanentUserIdentity" minOccurs="0"/>
+      <element name="mIPSubscriberProfile" minOccurs="0"/>
+    </all>
+  </complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element
+  name="IMSService"
+  substitutionGroup="sn:SuMService"
+>
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theContract" minOccurs="0"/>
+                <element
+                  name="listofauthorizedvisitednetworkidentifiers"/>
+                <element name="registrationStatus"/>
+                <element name="sCSCFName" minOccurs="0"/>
+                <element name="diameterClientAddressofSCSCF" minOccurs="0"/>
+                <element name="theServerCapabilities" type="xn:dn" minOccurs="0"/>
+                <element
+                  name="subscribedMediaProfileIdentifier"
+                  minOccurs="0"
+                />
+                <element name="initialFilterCriteriaList" minOccurs="0">
+                  <complexType>
+                    <sequence>
+                      <element name="initialFilterCriteria" minOccurs="1" maxOccurs="unbounded"/>
+                    </sequence>
+                  </complexType>
+                </element>
+                <element name="applicationServerInformation" minOccurs="0"/>
+                <element name="serviceIndicationList" minOccurs="0">
+                  <complexType>
+                    <sequence>
+                      <element name="serviceIndication" minOccurs="1" maxOccurs="unbounded"/>
+                    </sequence>
+                  </complexType>
+                </element>
+
+                <element
+                  name="primaryEventChargingFunctionName"
+                  minOccurs="0"
+                />
+                <element
+                  name="secondaryEventChargingFunctionName"
+                  minOccurs="0"
+                />
+                <element name="primaryChargingCollectionFunctionName"/>
+                <element
+                  name="secondaryChargingCollectionFunctionName"
+                  minOccurs="0"
+                />
+                <element name="gsmSCFaddressforIMCSI" minOccurs="0"/>
+                <element name="oIMCSI" minOccurs="0"/>
+                <element name="vTIMCSI" minOccurs="0"/>
+                <element name="dIMCS" minOccurs="0"/>
+                <element name="gAAServiceType" minOccurs="0"/>
+                <element name="gAAServiceIdentifier" minOccurs="0"/>
+                <element name="gBAUserSecuritySettings" minOccurs="0"/>
+                <element name="userSecuritySetting" minOccurs="0"/>
+                <element name="userPublicIdentity" minOccurs="0"/>
+                <element name="gAAAuthorizationflag" minOccurs="0"/>
+                <element name="keyLifetime" minOccurs="0"/>
+                <element name="uICCSecurityType" minOccurs="0"/>
+                <element name="nAFGroupIdentity" minOccurs="0"/>
+
+```
+
+```
+
+    </all>
+  </complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element name="SuMSubscribedService"
+substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass" type="xn:NrmClass"
+abstract="true"/>
+
+<element
+name="CSSubscribedService"
+substitutionGroup="sn:SuMSubscribedService"
+>
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theService" minOccurs="0"/>
+                <element name="theOffer" minOccurs="0"/>
+                <element name="networkAccessMode"/>
+                <element name="basicMSISDNIndicator" minOccurs="0"/>
+                <element name="mSISDNAlertIndicator" minOccurs="0"/>
+                <element name="subscriptionRestriction" minOccurs="0"/>
+                <element name="rSZIlists" minOccurs="0"/>
+                <element name="LSAIdentity" minOccurs="0"/>
+                <element name="LSAPriority" minOccurs="0"/>
+                <element name="LSAPreferentialAccessIndicator" minOccurs="0"/>
+                <element name="LSAActiveModeSupportIndicator" minOccurs="0"/>
+                <element name="LSAOnlyAccessIndicator" minOccurs="0"/>
+                <element name="LSAActiveModeIndicator" minOccurs="0"/>
+                <element name="vPLMNIdentifier" minOccurs="0"/>
+                <element name="accessRestrictionData" minOccurs="0"/>
+                <element name="privacyExceptionList" minOccurs="0"/>
+                <element name="gMLCNumbers" minOccurs="0"/>
+                <element name="mOLRList" minOccurs="0"/>
+                <element name="serviceTypes" minOccurs="0"/>
+                <element name="mobileStationCategory" minOccurs="0"/>
+                <element name="lMUIdentifier" minOccurs="0"/>
+                <element name="subscriberStatus" minOccurs="0"/>
+                <element name="gsmSCFaddresslistForODB"/>
+                <element name="provisionOfBearerService"/>
+                <element name="provisionOfTeleservice"/>
+                <element name="bCAllocation" minOccurs="0"/>
+                <element name="barringOfOutgoingCalls" minOccurs="0"/>
+                <element name="barringOfIncomingCalls" minOccurs="0"/>
+                <element name="barringOfRoaming" minOccurs="0"/>
+                <element name="barringOfPremiumRateCalls" minOccurs="0"/>
+                <element
+name="barringOfSupplementaryServiceManagement"
+minOccurs="0"
+/>
+                <element
+name="barringOfRegistrationOfCallForwarding"
+minOccurs="0"
+/>
+                <element
+name="barringOfInvocationOfCallTransfer"
+minOccurs="0"
+/>
+                <element
+name="operatorDeterminedBarringPLMNsensitiveData"
+minOccurs="0"
+/>
+                <element name="vGCSGroupMembershipList" minOccurs="0"/>
+                <element name="vBSGroupMembershipList" minOccurs="0"/>
+                <element
+name="broadcastCallInitiationAllowedList"
+minOccurs="0"
+/>
+                <element
+name="originatingCAMELSubscriptionInformationOCSI"
+minOccurs="0"
+/>
+
+```
+
+```
+
+<element
+  name="terminatingCAMELSubscriptionInformationTCSI"
+  minOccurs="0"
+/>
+<element
+  name="vMSCTerminatingCAMELSubscriptionInformationVTCSCI"
+  minOccurs="0"
+/>
+<element
+  name="locationInformationSubscriberStateInformation"
+  minOccurs="0"
+/>
+<element
+  name="uSSDCAMELSubscriptionInformationUCSCI"
+  minOccurs="0"
+/>
+<element name="sSInvocationNotificationSSCSI" minOccurs="0"/>
+<element
+  name="translationInformationFlagTIFCSI"
+  minOccurs="0"
+/>
+<element
+  name="dialledServiceCAMELSubscriptionInformationDCSCI"
+  minOccurs="0"
+/>
+<element
+  name="uSSDGeneralCAMELServiceInformationUGCSI"
+  minOccurs="0"
+/>
+<element
+  name="shortMessageServiceCAMELSubscriptionInformationMOSMSCSCI"
+  minOccurs="0"
+/>
+<element
+  name="shortMessageServiceCAMELSubscriptionInformationMTSMSCSCI"
+  minOccurs="0"
+/>
+<element
+  name="mTSMSCSCIvLRNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element name="gsmSCFaddressforCSI" minOccurs="0"/>
+<element name="iSTAlertTimer" minOccurs="0"/>
+<element name="cSAllocationRetentionpriority" minOccurs="0"/>
+<element name="iCSIIndicator" minOccurs="0"/>
+<element name="theCSSupplServiceForCSSS" type="xn:dnList"/>
+</all>
+</complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element
+  name="GPRSSSubscribedService"
+  substitutionGroup="sn:SuMSUBscribedService"
+>
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theService" minOccurs="0"/>
+                <element name="theOffer" minOccurs="0"/>
+                <element name="networkAccessMode" minOccurs="0"/>
+                <element name="basicMSISDNIndicator" minOccurs="0"/>
+                <element name="mSISDNAlertIndicator" minOccurs="0"/>
+                <element name="rSZIlists" minOccurs="0"/>
+                <element name="LSAIdentity" minOccurs="0"/>
+                <element name="LSAPriority" minOccurs="0"/>
+                <element name="LSAPreferentialAccessIndicator" minOccurs="0"/>
+                <element name="LSAActiveModeSupportIndicator" minOccurs="0"/>
+                <element name="LSAOnlyAccessIndicator" minOccurs="0"/>
+                <element name="LSAActiveModeIndicator" minOccurs="0"/>
+                <element name="vPLMNIdentifier" minOccurs="0"/>
+                <element name="accessRestrictionData" minOccurs="0"/>
+
+```
+
+```
+
+<element name="privacyExceptionList" minOccurs="0"/>
+<element name="gMLCNumbers" minOccurs="0"/>
+<element name="mOLRList" minOccurs="0"/>
+<element name="serviceTypes" minOccurs="0"/>
+<element name="gGSNNumber" minOccurs="0"/>
+<element name="provisionofTeleservice" minOccurs="0"/>
+<element name="subscriberStatus" minOccurs="0"/>
+<element name="transferofSOption" minOccurs="0"/>
+<element
+  name="barringofPacketOrientedServices"
+  minOccurs="0"
+/>
+<element name="pDPType" minOccurs="0"/>
+<element name="pDPAddress" minOccurs="0"/>
+<element name="accessPointName" minOccurs="0"/>
+<element name="vPLMNAddressAllowed" minOccurs="0"/>
+<element name="qualityofServiceSubscribed" minOccurs="0"/>
+<element
+  name="pDPContextChargingCharacteristics"
+  minOccurs="0"
+/>
+<element
+  name="gPRSCAMELSubscriptionInformationGPRSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mOShortMessageServiceCAMELSubscriptionInformationMOSMSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mTShortMessageServiceCAMELSubscriptionInformationMTSMSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mOSMSCSISGSNNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="mTSMSCSISGSNNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="mobilityManagementforGPRSeventnotificationMGCSI"
+  minOccurs="0"
+/>
+<element
+  name="mGCSINegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element name="gsmSCFaddressforCSI" minOccurs="0"/>
+<element name="closedSubscriberGroupInformation" minOccurs="0"/>
+<element name="gSMSCFaddresslistForODB" minOccurs="0"/>
+<element name="barringOfOutgoingCalls" minOccurs="0"/>
+<element name="barringOfRoaming" minOccurs="0"/>
+<element name="operatorDeterminedBarringPLMNspectificData" minOccurs="0"/>
+<element name="sTNSR" minOccurs="0"/>
+<element name="iCSIIndicator" minOccurs="0"/>
+<element
+  name="subscribedChargingCharacteristics"
+  minOccurs="0"
+/>
+<element
+  name="listofauthorizedvisitednetworkidentifiers"
+  minOccurs="0"
+/>
+<element name="wLANUERemoteIPaddress" minOccurs="0"/>
+<element name="staticWLANUERemoteIPaddressList" minOccurs="0"/>
+<element name="w-APNBarringTypeList" minOccurs="0"/>
+<element name="w-APNChargingDataList" minOccurs="0"/>
+<element name="accessDependenceFlag" minOccurs="0"/>
+<element name="chargingData" minOccurs="0"/>
+<element name="chargingCharacteristics" minOccurs="0"/>
+<element name="primaryOCSChargingFunctionName" minOccurs="0"/>
+<element name="secondaryOCSChargingFunctionName" minOccurs="0"/>
+<element name="w-APNIdentifierList" minOccurs="0"/>
+<element name="maxNumberAccessesList" minOccurs="0"/>
+<element name="maxSubscribedBandwidth" minOccurs="0"/>
+<element name="subscribed3GPPWLANQoSProfile" minOccurs="0"/>
+<element
+  name="primaryChargingCollectionFunctionName"
+
+```
+
+```
+
+        minOccurs="0"
+    />
+    <element
+        name="secondaryChargingCollectionFunctionName"
+        minOccurs="0"
+    />
+    <element name="theGPRSSuppServiceForGPRSSS" type="xn:dnList"/>
+</all>
+</complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element name="EPSSubscribedService" substitutionGroup="sn:SuMSubscribedService">
+    <complexType>
+        <complexContent>
+            <extension base="xn:NrmClass">
+                <sequence>
+                    <element name="attributes" minOccurs="0">
+                        <complexType>
+                            <all>
+                                <element name="theService" minOccurs="0"/>
+                                <element name="theOffer" minOccurs="0"/>
+                                <element name="accessPointName" minOccurs="0"/>
+                                <element name="accessRestrictionData" minOccurs="0"/>
+                                <element name="aPNAMBR" minOccurs="0"/>
+                                <element name="barringOfPacketOrientedServices" minOccurs="0"/>
+                                <element name="contextIdentifier" minOccurs="0"/>
+                                <element name="operatorDeterminedBarringPLMNSpecificData" minOccurs="0"/>
+                                <element name="pDNAddress" minOccurs="0"/>
+                                <element name="rSZILists" minOccurs="0"/>
+                                <element name="sTNSR" minOccurs="0"/>
+                                <element name="subscribedChargingCharacteristics" minOccurs="0"/>
+                                <element name="subscriberStatus" minOccurs="0"/>
+                                <element name="networkAccessMode" minOccurs="0"/>
+                                <element name="barringOfOutgoingCalls" minOccurs="0"/>
+                                <element name="barringOfRoaming" minOccurs="0"/>
+                                <element name="privacyExceptionList" minOccurs="0"/>
+                                <element name="gMLCNumbers" minOccurs="0"/>
+                                <element name="mOLRList" minOccurs="0"/>
+                                <element name="serviceTypes" minOccurs="0"/>
+                                <element name="iCSIndicator" minOccurs="0"/>
+                                <element name="aPNOIReplacement" minOccurs="0"/>
+                                <element name="subscribedUEAMBR" minOccurs="0"/>
+                                <element name="aPNConfigurationProfile" minOccurs="0"/>
+                                <element name="rFSP" minOccurs="0"/>
+                                <element name="vPLMNAddressAllowed-EPS" minOccurs="0"/>
+                                <element name="pDNGWIdentity" minOccurs="0"/>
+                                <element name="ePSPDNConnectedChargingCharacteristics" minOccurs="0"/>
+                                <element name="pDNGWAllocationType" minOccurs="0"/>
+                                <element name="aPNLevelAPNOIReplacement" minOccurs="0"/>
+                                <element name="closedSubscriberUserGroupInformation" minOccurs="0"/>
+                                <element name="listOfAuthorizedvisitednetowrkidentifiers" minOccurs="0"/>
+                                <element name="staticWLANUERemoteIPAddressList" minOccurs="0"/>
+                                <element name="w-APONBarringTypeList" minOccurs="0"/>
+                                <element name="w-APNChargingDataList" minOccurs="0"/>
+                                <element name="wLANUERemoteIPAddress" minOccurs="0"/>
+                                <element name="accessDependenceFlag" minOccurs="0"/>
+                                <element name="chargingCharacteristics" minOccurs="0"/>
+                                <element name="primaryOCSChargingFunctionName" minOccurs="0"/>
+                                <element name="secondaryOCSChargingFunctionName" minOccurs="0"/>
+                                <element name="primaryChargingCollectionFunctionName" minOccurs="0"/>
+                                <element name="secondaryChargingCollectionFunctionName" minOccurs="0"/>
+                                <element name="w-APNIdentifierList" minOccurs="0"/>
+                                <element name="maxNumberAccessesList" minOccurs="0"/>
+                                <element name="maxSubscribedBandwidth" minOccurs="0"/>
+                                <element name="subscribed3GPPWLANQoSProfile" minOccurs="0"/>
+                                <element name="permanentUserIdentity" minOccurs="0"/>
+                                <element name="mIPSubscriberProfile" minOccurs="0"/>
+                            </all>
+                        </complexType>
+                    </element>
+                </sequence>
+            </extension>
+        </complexContent>
+    </complexType>
+
+```
+
+```
+
+</element>
+
+<element
+  name="IMSSubscribedService"
+  substitutionGroup="sn:SuMSubscribedService"
+>
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theService" minOccurs="0"/>
+                <element name="theOffer" minOccurs="0"/>
+                <element name="listofauthorizedvisitednetworkidentifiers"/>
+                <element name="registrationStatus"/>
+                <element name="sCSCFName" minOccurs="0"/>
+                <element name="diameterClientAddressofSCSCF" minOccurs="0"/>
+                <element name="theServerCapabilities" type="xn:dn" minOccurs="0"/>
+                <element
+                  name="subscribedMediaProfileIdentifier"
+                  minOccurs="0"
+                />
+                <element name="initialFilterCriteriaList" minOccurs="0">
+                  <complexType>
+                    <sequence>
+                      <element name="initialFilterCriteria" minOccurs="1" maxOccurs="unbounded"/>
+                    </sequence>
+                  </complexType>
+                </element>
+                <element name="applicationServerInformation" minOccurs="0"/>
+                <element name="serviceIndication" minOccurs="0">
+                  <complexType>
+                    <sequence>
+                      <element name="serviceIndication" minOccurs="1" maxOccurs="unbounded"/>
+                    </sequence>
+                  </complexType>
+                </element>
+                <element
+                  name="primaryEventChargingFunctionName"
+                  minOccurs="0"
+                />
+                <element
+                  name="secondaryEventChargingFunctionName"
+                  minOccurs="0"
+                />
+                <element name="primaryChargingCollectionFunctionName"/>
+                <element
+                  name="secondaryChargingCollectionFunctionName"
+                  minOccurs="0"
+                />
+                <element name="gsmSCFaddressforIMCSI" minOccurs="0"/>
+                <element name="oIMCSI" minOccurs="0"/>
+                <element name="vTIMCSI" minOccurs="0"/>
+                <element name="dIMCS" minOccurs="0"/>
+                <element name="gAAServiceType" minOccurs="0"/>
+                <element name="gAAServiceIdentifier" minOccurs="0"/>
+                <element name="gBAUserSecuritySettings" minOccurs="0"/>
+                <element name="userSecuritySetting" minOccurs="0"/>
+                <element name="userPublicIdentity" minOccurs="0"/>
+                <element name="gAAAuthorizationflag" minOccurs="0"/>
+                <element name="keyLifetime" minOccurs="0"/>
+                <element name="uICCSecurityType" minOccurs="0"/>
+                <element name="nAFGroupIdentity" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="SuMServiceProfile" substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass"
+type="xn:NrmClass" abstract="true"/>
+
+<element
+  name="CSServiceProfile"
+
+```
+
+```
+
+substitutionGroup="sn:SuMServiceProfile"
+>
+  <complexType>
+    <complexContent>
+      <extension base="sn:Common3GPPAccessServiceProfile">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theSpecification" minOccurs="0"/>
+                <element name="basicMSISDNIndicator" minOccurs="0"/>
+                <element name="mSISDNAlertIndicator" minOccurs="0"/>
+                <element name="vLRNumber"/>
+                <element name="mSCNumber"/>
+                <element name="subscriptionRestriction" minOccurs="0"/>
+                <element name="mSCAreaRestrictedFlag"/>
+                <element name="oDBinducedBarringData" minOccurs="0"/>
+                <element name="roamingRestrictionDueToUnsupportedFeature"/>
+                <element name="lSAIdentity" minOccurs="0"/>
+                <element name="lSAPriority" minOccurs="0"/>
+                <element name="lSAPreferentialAccessIndicator" minOccurs="0"/>
+                <element name="lSAActiveModeSupportIndicator" minOccurs="0"/>
+                <element name="lSAOnlyAccessIndicator" minOccurs="0"/>
+                <element name="lSAActiveModeIndicator" minOccurs="0"/>
+                <element name="vPLMNIdentifier" minOccurs="0"/>
+                <element name="ageIndicator" minOccurs="0"/>
+                <element name="lMSI"/>
+                <element name="mobileStationCategory"/>
+                <element name="lMUIdentifier" minOccurs="0"/>
+                <element name="mNRMSC"/>
+                <element name="notificationToCSEFlagForODB" minOccurs="0"/>
+                <element name="gsmSCFaddresslistForODB" minOccurs="0"/>
+                <element name="messagesWaitingData" minOccurs="0"/>
+                <element name="mobileStationNotReachableFlag" minOccurs="0"/>
+                <element name="memoryCapacityExceededFlag"/>
+                <element name="traceReference" minOccurs="0"/>
+                <element name="traceType" minOccurs="0"/>
+                <element name="operationsSystemsIdentity" minOccurs="0"/>
+                <element name="hLRTraceType" minOccurs="0"/>
+                <element name="mAPErrorOnTrace" minOccurs="0"/>
+                <element name="traceActivatedInVLR" minOccurs="0"/>
+                <element name="provisionOfBearerService"/>
+                <element name="provisionOfTeleservice"/>
+                <element name="bCAllocation" minOccurs="0"/>
+                <element name="checkSSIndicator"/>
+                <element name="mSPurgedForNonGPRSFlag"/>
+                <element name="barringOfIncomingCalls" minOccurs="0"/>
+                <element name="barringOfPremiumRateCalls" minOccurs="0"/>
+                <element
+                  name="barringOfSupplementaryServiceManagement"
+                  minOccurs="0"
+                />
+                <element
+                  name="barringOfRegistrationOfCallForwarding"
+                  minOccurs="0"
+                />
+                <element
+                  name="barringOfInvocationOfCallTransfer"
+                  minOccurs="0"
+                />
+                <element name="vGCSGroupMembershipList" minOccurs="0"/>
+                <element name="vBSGroupMembershipList" minOccurs="0"/>
+                <element
+                  name="broadcastCallInitiationAllowedList"
+                  minOccurs="0"
+                />
+                <element
+                  name="originatingCAMELSubscriptionInformationOCSI"
+                  minOccurs="0"
+                />
+                <element
+                  name="terminatingCAMELSubscriptionInformationTCSI"
+                  minOccurs="0"
+                />
+                <element
+                  name="vMSCTerminatingCAMELSubscriptionInformationVTCI"
+                  minOccurs="0"
+                />
+                <element
+                  name="locationInformationSubscriberStateInformation"
+                />
+
+```
+
+```
+
+        minOccurs="0"
+      />
+      <element
+        name="uSSDCAMELSubscriptionInformationUCSI"
+        minOccurs="0"
+      />
+      <element name="sSInvocationNotificationSSCSI" minOccurs="0"/>
+      <element
+        name="translationInformationFlagTIFCSI"
+        minOccurs="0"
+      />
+      <element
+        name="dialledServiceCAMELSubscriptionInformationDCSI"
+        minOccurs="0"
+      />
+      <element
+        name="uSSDGeneralCAMELServiceInformationUGCSI"
+        minOccurs="0"
+      />
+      <element
+        name="oCSINegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+      />
+      <element
+        name="sSCSINegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+      />
+      <element
+        name="vTCSINegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+      />
+      <element
+        name="shortMessageServiceCAMELSubscriptionInformationMOSMSCSI"
+        minOccurs="0"
+      />
+      <element
+        name="shortMessageServiceCAMELSubscriptionInformationMTSMSCSI"
+        minOccurs="0"
+      />
+      <element
+        name="mOSMSCSIVLRNegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+      />
+      <element
+        name="mTSMSCSIVLRNegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+      />
+      <element
+        name="mCSINegotiatedCAMELCapabilityHandling"
+        minOccurs="0"
+      />
+      <element name="vLRSupportedCAMELPhases" minOccurs="0"/>
+      <element name="gsmSCFaddressforCSI" minOccurs="0"/>
+      <element name="vLROfferedCAMEL4CSIs" minOccurs="0"/>
+      <element name="iSTAlertTimer" minOccurs="0"/>
+      <element name="cSAllocationRetentionpriority" minOccurs="0"/>
+      <element name="theCSSupplServiceForCSSP" type="xn:dnList"/>
+    </all>
+  </complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element
+  name="GPRSServiceProfile"
+  substitutionGroup="sn:SuMServiceProfile"
+>
+  <complexType>
+    <complexContent>
+      <extension base="sn:PSCommonServiceProfile">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theSpecification" minOccurs="0"/>
+                <element name="basicMSISDNIndicator" minOccurs="0"/>
+                <element name="mSISDNAlertIndicator" minOccurs="0"/>
+
+```
+
+```
+
+<element name="vLRNumber" minOccurs="0"/>
+<element name="LSAIdentity" minOccurs="0"/>
+<element name="LSAPriority" minOccurs="0"/>
+<element name="LSAPreferentialAccessIndicator" minOccurs="0"/>
+<element name="LSAActiveModeSupportIndicator" minOccurs="0"/>
+<element name="LSAOnlyAccessIndicator" minOccurs="0"/>
+<element name="LSAActiveModeIndicator" minOccurs="0"/>
+<element name="vPLMNIdentifier" minOccurs="0"/>
+<element name="ageIndicator" minOccurs="0"/>
+<element name="sGSNNumber" minOccurs="0"/>
+<element name="gGSNNumber" minOccurs="0"/>
+<element name="mNRC" minOccurs="0"/>
+<element name="provisionofTeleservice" minOccurs="0"/>
+<element name="transferofSMoption" minOccurs="0"/>
+<element name="mSpurgedforGPRSflag" minOccurs="0"/>
+<element name="pDPType" minOccurs="0"/>
+<element name="pDPAddress" minOccurs="0"/>
+<element name="vPLMNAddressAllowed" minOccurs="0"/>
+<element name="gGSNlist" minOccurs="0"/>
+<element name="qualityofServiceSubscribed" minOccurs="0"/>
+<element name="pDPContextIdentifier" minOccurs="0"/>
+<element
+  name="pDPContextChargingCharacteristics"
+  minOccurs="0"
+/>
+<element
+  name="gPRSCAMELSubscriptionInformationGPRSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mOShortMessageServiceCAMELSubscriptionInformationMOSMSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mTShortMessageServiceCAMELSubscriptionInformationMTSMSCSI"
+  minOccurs="0"
+/>
+<element
+  name="mOSMSCSISGSNNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="mTSMSCSISGSNNegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="mobilityManagementforGPRSeventnotificationMGCSI"
+  minOccurs="0"
+/>
+<element
+  name="mGCSINegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element
+  name="gPRSCSINegotiatedCAMELCapabilityHandling"
+  minOccurs="0"
+/>
+<element name="sGSNSupportedCAMELPhases" minOccurs="0"/>
+<element name="sGSNOfferedCAMEL4CSIs" minOccurs="0"/>
+<element name="gsmSCFaddressforCSI" minOccurs="0"/>
+<element name="gSMSCFaddresslistForODB" minOccurs="0"/>
+<element name="iPSMGWNumber" minOccurs="0"/>
+<element name="mNRR-SGSN" minOccurs="0"/>
+<element name="notificationToCSEFlagForODB" minOccurs="0"/>
+<element name="theGPRSSupplServiceForGPRSSP" type="xn:dnList"/>
+</all>
+</complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+<element name="EPSServiceProfile" substitutionGroup="sn:SuMServiceProfile">
+  <complexType>
+    <complexContent>
+      <extension base="sn:PSCommonServiceProfile">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+
+```
+
+```
+
+    <all>
+      <element name="theSpecification" minOccurs="0"/>
+      <element name="aPNAMBR" minOccurs="0"/>
+      <element name="contextIdentifier" minOccurs="0"/>
+      <element name="pDNAddress" minOccurs="0"/>
+      <element name="aPNOIReplacement" minOccurs="0"/>
+      <element name="subscribedUEAMBR" minOccurs="0"/>
+      <element name="aPNConfigurationProfile" minOccurs="0"/>
+      <element name="rFSP" minOccurs="0"/>
+      <element name="pDNGWIdentity" minOccurs="0"/>
+      <element name="ePSPDNConnectionChargingCharacteristics" minOccurs="0"/>
+      <element name="pDNGWAllocationType" minOccurs="0"/>
+      <element name="aPNLevelAPNOIReplacement" minOccurs="0"/>
+      <element name="roamingRestrictionsDueToUnsupportedFeatureMME" minOccurs="0"/>
+      <element name="roamingRestrictionsDueToUnsupportedFeatureSGSN" minOccurs="0"/>
+      <element name="mSPurgedForEPSFlag" minOccurs="0"/>
+      <element name="uRRPMME" minOccurs="0"/>
+      <element name="mMEName" minOccurs="0"/>
+      <element name="sGSNName" minOccurs="0"/>
+      <element name="iWFNumber" minOccurs="0"/>
+      <element name="sGSNAreaRestrictedFlag" minOccurs="0"/>
+      <element name="permanentUserIdentity" minOccurs="0"/>
+      <element name="vPLMNAddressAllowed-EPS" minOccurs="0"/>
+      <element name="theOptHandover3GPP2Par" type="xn:dn"/>
+      <element name="theNon3GPPAccessPar" type="xn:dn"/>
+    </all>
+  </complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element name="PSCommonServiceProfile" abstract="true" substitutionGroup="sn:SuMServiceProfile">
+  <complexType>
+    <complexContent>
+      <extension base="sn:Common3GPPAccessServiceProfile">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="roamingRestrictedintheSGSNduetounsupportedfeature" minOccurs="0"/>
+                <element name="barringofPacketOrientedServices" minOccurs="0"/>
+                <element name="traceActivatedinSGSN" minOccurs="0"/>
+                <element name="iPAddressOfTraceCollectionEntity" minOccurs="0"/>
+                <element name="accessPointName" minOccurs="0"/>
+                <element name="subscribedChargingCharacteristics" minOccurs="0"/>
+                <element name="sTNSR" minOccurs="0"/>
+                <element name="closedSubscriberGroupInformation" minOccurs="0"/>
+                <element name="theIWANPar" type="xn:dn" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="Common3GPPAccessServiceProfile" abstract="true"
+substitutionGroup="sn:SuMServiceProfile">
+  <complexType>
+    <complexContent>
+      <extension base="sn:SuMServiceProfile">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="rSZILists" minOccurs="0"/>
+                <element name="accessRestrictionData" minOccurs="0" />
+                <element name="subscriberStatus" minOccurs="0"/>
+                <element name="barringOfOutgoingCalls" minOccurs="0"/>
+                <element name="barringOfRoaming" minOccurs="0"/>
+                <element name="operatorDeterminedBarringPLMNSpecificData" minOccurs="0"/>
+                <element name="traceReference2" minOccurs="0"/>
+                <element name="traceDepth" minOccurs="0"/>
+                <element name="listOfNETypesToTrace" minOccurs="0"/>
+                <element name="triggeringEvents" minOccurs="0"/>
+                <element name="listOfInterfacesToTrace" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+```
+
+```
+
+        <element name="privacyExceptionList" minOccurs="0"/>
+        <element name="gMLCNumbers" minOccurs="0"/>
+        <element name="iCSIndicator" minOccurs="0"/>
+        <element name="mOLRList" minOccurs="0"/>
+        <element name="serviceTypes" minOccurs="0"/>
+        <element name="networkAccessMode" minOccurs="0"/>
+      </all>
+    </complexType>
+  </element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element name="IWANParameters" substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="w-APN" minOccurs="0"/>
+                <element name="listofauthorizedvisitednetworkidentifiers" minOccurs="0"/>
+                <element name="threeGPPAAAServerName" minOccurs="0" />
+                <element name="threeGPPAAProxyName" minOccurs="0"/>
+                <element name="wLANUERemoteIPAddress" minOccurs="0"/>
+                <element name="statisWLANUERemoteIPAddressList" minOccurs="0"/>
+                <element name="w-APNBarringTypeList" minOccurs="0"/>
+                <element name="w-APNChargingDataList" minOccurs="0"/>
+                <element name="accessDependenceFlag" minOccurs="0"/>
+                <element name="i-WLANAccessType" minOccurs="0"/>
+                <element name="wLANIdentifierList" minOccurs="0"/>
+                <element name="maxNumberAccessesList" minOccurs="0"/>
+                <element name="maxSubscribedBandwidth" minOccurs="0"/>
+                <element name="subscribed3GPPWLANQoSProfile" minOccurs="0"/>
+                <element name="chargingCharacteristics" minOccurs="0"/>
+                <element name="primaryOCSChargingFunctionName" minOccurs="0"/>
+                <element name="secondaryOCSChargingFunctionName" minOccurs="0"/>
+                <element name="primaryChargingCollectionFunctionName" minOccurs="0"/>
+                <element name="secondaryChargingCollectionFunctionName" minOccurs="0"/>
+                <element name="userStatus" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="OptHandover3GPP2Parameters"
+substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="rATType" minOccurs="0"/>
+              </all>
+            </complexType>
+          </element>
+        </sequence>
+      </extension>
+    </complexContent>
+  </complexType>
+</element>
+
+<element name="Non3GPPAccessParameters"
+substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass">
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+
+```
+
+```
+
+    <all>
+      <element name="rATType" minOccurs="0"/>
+      <element name="visitedNetworkIdentifier" minOccurs="0"/>
+      <element name="mIPSSubscriberProfile" minOccurs="0"/>
+      <element name="permanentUserIdentity" minOccurs="0"/>
+    </all>
+  </complexType>
+</element>
+</sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<element
+  name="IMSServiceProfile"
+  substitutionGroup="sn:SuMServiceProfile"
+>
+  <complexType>
+    <complexContent>
+      <extension base="xn:NrmClass">
+        <sequence>
+          <element name="attributes" minOccurs="0">
+            <complexType>
+              <all>
+                <element name="theSpecification" minOccurs="0"/>
+                <element name="listofauthorizedvisitednetworkidentifiers"/>
+                <element name="registrationStatus"/>
+                <element name="sCSCFName" minOccurs="0"/>
+                <element name="diameterClientAddressofSCSCF" minOccurs="0"/>
+                <element name="theServerCapabilities" type="xn:dn" minOccurs="0"/>
+                <element
+                  name="subscribedMediaProfileIdentifier"
+                  minOccurs="0"
+                />
+                <element name="initialFilterCriteriaList" minOccurs="0">
+                  <complexType>
+                    <sequence>
+                      <element name="initialFilterCriteria" minOccurs="1" maxOccurs="unbounded"/>
+                    </sequence>
+                  </complexType>
+                </element>
+                <element name="applicationServerInformation" minOccurs="0"/>
+                <element name="serviceIndicationList" minOccurs="0">
+                  <complexType>
+                    <sequence>
+                      <element name="serviceIndication" minOccurs="1" maxOccurs="unbounded"/>
+                    </sequence>
+                  </complexType>
+                </element>
+                <element
+                  name="primaryEventChargingFunctionName"
+                  minOccurs="0"
+                />
+                <element
+                  name="secondaryEventChargingFunctionName"
+                  minOccurs="0"
+                />
+                <element name="primaryChargingCollectionFunctionName"/>
+                <element
+                  name="secondaryChargingCollectionFunctionName"
+                  minOccurs="0"
+                />
+                <element name="gsmSCFaddressforIMCSI" minOccurs="0"/>
+                <element name="iMSSFaddressforIMCSI" minOccurs="0"/>
+                <element name="oIMCSI" minOccurs="0"/>
+                <element name="vTIMCSI" minOccurs="0"/>
+                <element name="dIMCS" minOccurs="0"/>
+                <element name="gAAServiceType" minOccurs="0"/>
+                <element name="gAAServiceIdentifier" minOccurs="0"/>
+                <element name="gBAUserSecuritySettings" minOccurs="0"/>
+                <element name="userSecuritySetting" minOccurs="0"/>
+                <element name="userPublicIdentity" minOccurs="0"/>
+                <element name="gAAAuthorizationflag" minOccurs="0"/>
+                <element name="keyLifetime" minOccurs="0"/>
+                <element name="uICCSecurityType" minOccurs="0"/>
+                <element name="nAFGroupIdentity" minOccurs="0"/>
+                <element name="thePublicId" type="xn:dnList"/>
+              </all>
+            </complexType>
+          </element>
+
+```
+
+```
+
+    </element>
+  </sequence>
+</extension>
+</complexContent>
+</complexType>
+</element>
+
+<complexType name="IMSPublicIdentificationType">
+  <complexContent>
+    <extension base="sn:SuMIdentityType">
+      <all>
+        <element name="publicUserIdentity" type="string" minOccurs="0"/>
+        <element name="barringIndication" type="sn:binEnum" minOccurs="0"/>
+      </all>
+    </extension>
+  </complexContent>
+</complexType>
+
+<element name="IMSPublicIdentification" type="sn:IMSPublicIdentificationType"
+substitutionGroup="sn:SuMIdentity"/>
+
+<simpleType name="binEnum">
+  <restriction base="string">
+    <enumeration value="FALSE"/>
+    <enumeration value="TRUE"/>
+  </restriction>
+</simpleType>
+
+<simpleType name="multinumberingMSISDNIndicator">
+  <restriction base="string">
+    <enumeration value="BASIC"/>
+    <enumeration value="ALERT"/>
+  </restriction>
+</simpleType>
+
+<complexType name="multinumberingMSISDNList">
+  <sequence minOccurs="0" maxOccurs="unbounded">
+    <element name="mSISDN" type="string"/>
+    <element name="indicator" type="sn:multinumberingMSISDNIndicator"/>
+  </sequence>
+</complexType>
+
+<complexType name="ServerCapabilitiesType">
+  <complexContent>
+    <extension base="sn:SuMServiceParameterType">
+      <all>
+        <element name="serverCapabilities"/>
+      </all>
+    </extension>
+  </complexContent>
+</complexType>
+
+<element name="ServerCapabilities" type="sn:ServerCapabilitiesType"
+substitutionGroup="sn:SuMServiceParameter"/>
+
+<complexType name="SuMIdentityType">
+  <complexContent>
+    <restriction base="xn:NrmClass"/>
+  </complexContent>
+</complexType>
+
+<complexType name="SuMServiceParameterType">
+  <complexContent>
+    <restriction base="xn:NrmClass"/>
+  </complexContent>
+</complexType>
+
+<element name="SuMIdentity" type="sn:SuMIdentityType"
+substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass" abstract="true"/>
+
+<element name="SuMServiceParameter" type="sn:SuMServiceParameterType"
+substitutionGroup="xn:SubNetworkOptionallyContainedNrmClass" abstract="true"/>
+
+</schema>
+
+```
+
+# Annex B (informative): Change history
+
+| Change history |       |           |     |     |                                                                                                                                                      |     |        |        |
+|----------------|-------|-----------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                                                                                                                      | Cat | Old    | New    |
+| 05-2010        | SA-48 | SP-100270 | --  | --  | Presentation to SA for information and approval                                                                                                      | --  | --     | 1.0.0  |
+| 06-2010        | SA-48 | --        | --  | --  | Publication                                                                                                                                          | --  | 1.0.0  | 10.0.0 |
+| 09-2010        | SA-49 | SP-100489 | 001 | --  | Correct the support qualifier in XML definition to be aligned with IS                                                                                | F   | 10.0.0 | 10.1.0 |
+| 09-2010        | SA-49 | SP-100494 | 002 | --  | Modifications to Packet Access Service Parameters and Modeling                                                                                       | C   | 10.0.0 | 10.1.0 |
+| 09-2010        | SA-49 | SP-100494 | 003 | --  | Aligning with the SuM NRM IRP IS - removing some SuM IOCs from Itf-N                                                                                 | C   | 10.0.0 | 10.1.0 |
+| 12-2010        | SA-50 | SP-100833 | 004 | --  | Correcting the IOC PSSubscribedService name in XML definition - Align with 32.172 IS                                                                 | F   | 10.1.0 | 10.2.0 |
+| 12-2010        | SA-50 | SP-100755 | 006 | --  | Correcting faults in schema definition                                                                                                               | F   | 10.1.0 | 10.2.0 |
+| 12-2010        | SA-50 | SP-100755 | 007 | --  | Add the missing MobileUserData attribute in SuMSubscriberProfile - Align with 32.172 SuM NRM IS                                                      | F   | 10.1.0 | 10.2.0 |
+| 03-2011        | SA-51 | SP-110104 | 008 | 1   | Improve Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP) access service modelling - Align with 32.172 IS | C   | 10.2.0 | 10.3.0 |
+
+Error! No
+
+28
+
+Error! No text of specified style in
+
+Error! No
+
+28
+
+Error! No text of specified style in

marked/Rel-10/32_series/32181/raw.md

@@ -0,0 +1,637 @@
+
+
+
+
+
+
+
+
+# Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Introduction .....                                                         | 5  |
+| 1 Scope.....                                                               | 6  |
+| 2 References.....                                                          | 6  |
+| 3 Definitions and abbreviations .....                                      | 7  |
+| 3.1 Definitions.....                                                       | 7  |
+| 3.2 Abbreviations .....                                                    | 7  |
+| 4 UDC Framework overview.....                                              | 8  |
+| 4.1 General overview .....                                                 | 8  |
+| 4.2 Requirements coming from other Specifications .....                    | 8  |
+| 4.3 Overview of UDC Data and Information Models.....                       | 8  |
+| 5 UDC information model infrastructure.....                                | 10 |
+| 5.1 Common Baseline Information Model (CBIM).....                          | 10 |
+| 5.2 Application Information Models (AIM) .....                             | 10 |
+| 5.3 Specialised Information Model (SpIM) .....                             | 11 |
+| 6 UDC information model handling .....                                     | 11 |
+| 6.1 General .....                                                          | 11 |
+| 6.2 Initial SpIM Creation from CBIM .....                                  | 13 |
+| 6.3 AIM Integration into SpIM .....                                        | 13 |
+| 6.4 Consolidation of User Data in the SpIM.....                            | 13 |
+| 6.5.1 Example of consolidation of data in the SpIM using aggregation ..... | 13 |
+| 6.5.2 Example of specialization for authentication methods.....            | 14 |
+| 6.5.3.1 AkaUsim.....                                                       | 15 |
+| 6.5.3.1.1 Definition .....                                                 | 15 |
+| 6.5.3.2 CsAka.....                                                         | 15 |
+| 6.5.3.2.1 Definition .....                                                 | 15 |
+| 6.5.3.3 GPRSAka.....                                                       | 15 |
+| 6.5.3.3.1 Definition .....                                                 | 15 |
+| 6.5.3.4 EpsAka.....                                                        | 16 |
+| 6.5.3.4.1 Definition .....                                                 | 16 |
+| 6.5.3.5 ImsAkaIsim.....                                                    | 16 |
+| 6.5.3.5.1 Definition .....                                                 | 16 |
+| 6.5.3.6 ImsAka.....                                                        | 16 |
+| 6.5.3.6.1 Definition .....                                                 | 16 |
+| 6.5.3.7 ImsAkaUsimIsim.....                                                | 16 |
+| 6.5.3.7.1 Definition .....                                                 | 16 |
+| 6.5.3.8 GPRSImdBundled.....                                                | 16 |
+| 6.5.3.8.1 Definition .....                                                 | 16 |
+| 6.5.3.9 NassImdBundled.....                                                | 16 |
+| 6.5.3.9.1 Definition .....                                                 | 16 |
+| 6.5.3.10 SipDigest.....                                                    | 17 |
+| 6.5.3.10.1 Definition .....                                                | 17 |
+| 6.5 Construction of AIM.....                                               | 17 |
+| 7 Application management .....                                             | 17 |
+| 7.1 Application Access Control Data.....                                   | 17 |
+| 7.2 Application Data Model and Mapping to Consolidated Data Model.....     | 17 |
+| 7.2.1 Application Data Views .....                                         | 17 |
+| 7.3 Subscription and Notification Related Data.....                        | 19 |
+| 8 Consolidated data model management .....                                 | 20 |
+| 8.1 Lifecycle Management of the Consolidated Data Model in the UDR .....   | 20 |
+| 8.2 Activation and Deactivation of Application Adaptation.....             | 21 |
+| 9 Relation to other Information Models.....                                | 22 |
+| 9.1 Relation to SuM Network Resource Model.....                            | 22 |
+
+Annex A (informative): Change history.................................................................................................. 23
+
+# Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 User Data Convergence concept supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends. Network elements and functionalities should be designed to access profile data remotely and without storing them permanently locally, i.e. the front-ends shall work in a user dataless configuration."
+
+TR 22.985 and TS 22.101 provide the requirements for User data convergence so that user data can be moved from where it originated, to a facility called User Data Repository (UDR) where it can be accessed, stored and managed in a common way.
+
+Convergence of user data unifies the user data access interface and its protocol. In addition, the logical centralization of user data implies the support of user data provisioning, that is, user data manipulation like creation, deletion, reading, modification and other operations.
+
+In order to accommodate multiple applications and services, existing and new ones, a framework for model handling and management of the UDC has been developed including:
+
+- UDC information model infrastructure
+- UDC information model handling
+- Application management
+- Consolidated data model management.
+
+# --- 1 Scope
+
+The present document specifies the framework for overall management of the User Data Convergence.
+
+In order to accommodate multiple applications and services, existing and new ones, the framework for model handling and management of the UDC as identified by TS 22.101 includes the following items:
+
+- UDC information models:
+  - UDC information model infrastructure containing the common baseline information model (CBIM), application information models (AIM), and the specialised information model (SIM). The CBIM is standardised in TS 32.cde [4].
+- UDC information model handling:
+  - provide a template and guidelines explaining the design of application information models to be used together with the common baseline information model to create the specialized information model
+  - describe the process to combine the common baseline information model with application information models in order to produce an operator-specific specialised information model
+- Application management data:
+  - access control data for an application to UDC: identification and authentication
+  - assignment to an application data model, including linkage to the consolidated data model
+  - subscription rights for specific events on specific data of specific users
+- Consolidated data model management
+  - lifecycle management of the consolidated data model in the UDR and in the provisioning entity.
+  - activation/deactivation of application adaptation
+
+# --- 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 TR 22.985: "Service requirement for the User Data Convergence (UDC)".
+- [3] 3GPP TS 22.101: "Service aspects; Service principles".
+- [4] 3GPP TS 32.182: "User Data Convergence; Common Baseline Information Model ".
+- [5] 3GPP TR 32.808: "Study of Common Profile Storage (CPS) Framework of User Data for network services and management"
+- [6] 3GPP TS 33.102: "3G Security; Security architecture"
+- [7] 3GPP TS 33.203: "3G security; Access security for IP-based services"
+
+- [8] 3GPP TS 23.335: “User Data Convergence; Technical Realization and Information Flows;Stage 2“
+- [9] 3GPP TS 29.335: “User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface; Stage 3”
+- [10] 3GPP TS 32.172: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)”
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Application Data Model :** specific data model used by an application accessing the UDR. It is defined according to the UDC access protocol. It is related to an application information model.
+
+**Application Data View:** a function of the UDR that enables and limits applications access to data within the UDR.
+
+**Application Information Model :** specific information model used by an application accessing the UDR. It is defined with the same method as the common baseline information model. It is related to an application data model.
+
+**Common Baseline Information Model:** basic structure of UDC IOCs, see also definition in 3GPP TS 32.182 [4]
+
+**Consolidated Data Model:** Data model containing all data of the User Data Repository. It is the result of the implementation of the entire Specialized Information Model in the UDR for all applications.
+
+**Information Model:** Information Model denotes an abstract, formal representation of entity types, including their properties and relationships, the operations (e.g. read, write...) that can be performed on them, and related rules and constraints. In the information model, entities might have network topology relationship with each other.
+
+**Specialized Information Model:** Information model containing all information to be stored in the UDR. It is the result of operator specific specialisation of CBIM with addition of imported AIM.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] 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].
+
+|      |                                      |
+|------|--------------------------------------|
+| ADM  | Application Data Model               |
+| AIM  | Application Information Model        |
+| AKA  | Authentication and Key Agreement     |
+| AMF  | Authentication Management Field      |
+| CBIM | Common baseline Information Model    |
+| CDM  | Consolidated Data Model              |
+| ISIM | IMS Subscriber Identity Module       |
+| SpIM | Specialised Information Model        |
+| UDC  | User Data Convergence                |
+| UDR  | User Data Repository                 |
+| UICC | Universal Integrated Circuit Card    |
+| USIM | Universal Subscriber Identity Module |
+
+# --- 4 UDC Framework overview
+
+## 4.1 General overview
+
+TR 22.985 [2] and TS 22.101[3] request the baseline information model to be future proof and extensible, i.e. new applications and/or new service profiles can be added by the operator, if necessary. The flexibility shall also permit new
+
+data for existing applications to be introduced, or modified. For the actual information model of an operator Specialized Information Model is described in TR 22.985 [2].
+
+For the above purpose this specification defines and describes the infrastructure of UDC Information Models in Clause 5.
+
+The correlation and handling of the UDC Information Models is described in Clause 6.
+
+## 4.2 Requirements coming from other Specifications
+
+TR 22.985 [2] and TS 22.101[3] provide requirements for CBIM and SpIM . These documents also mention the Application Data Models for the Access Interface to the UDC.
+
+Specification 23.335 [8] in Clause 5.2 defines the requirements for application access to the UDR including authentication and authorisation.
+
+Specification 29.335 [9]: defines as Access Protocol over the Ud interface LDAP (Clause 4) and as Data Model on the interface LDAP Directory Schema (Clause 7).
+
+## 4.3 Overview of UDC Data and Information Models
+
+Figures Fig.4.3-1 and Fig.4.3-2 below show the data and information models contained in the UDC framework including the UDR and the Application Front Ends. Boxes outlined in black. connecting Information and Data Models represent the process steps needed to produce the output model (pointed to by an outgoing arrow) from an input model (shown by the source of an incoming arrow).As shown in these figures, the Specialized Information Model can be both an input and output model, i.e. its current version is used as an input model to a process that generates an enhanced version when an Application Information Model new to the UDR is integrated and consolidated.
+
+Fig.4.3-1 below shows the case of internal integration model handling, where implementation of the Application is under responsibility of the operator . In this situation operator specification of the AIM leads to the Application Data Model (ADM), that gets implemented in the application FE and in the Application Data Model View in the UDR.
+
+![Figure 4.3-1: UDC Data and Information Models Overview with Operator integration model handling. The diagram illustrates the flow of information models from Common Baseline IM (CBIM) and App IM (AIM) through various processing steps to produce a Consolidated Data Model (CDM) and Information Elements. It is divided into three horizontal zones: Application/FE, Ud interface, and UDR. CBIM is customized to operator services to become a Specialized IM (SpIM). SpIM and AIM are integrated into SpIM and consolidated to generate ADM, mapping, and a new SpIM. This new SpIM is used to generate a new CDM, which becomes the Consolidated Data Model (CDM). The CDM is then used to generate Information Elements and Information procedures. The App IM (AIM) also leads to an App Data Model in the Application/FE. The Ud interface contains an App Data View, App Data Model, and App Data Model Mapping. The Adaptation zone contains the App Data Model and App Data Model Mapping. The UDR contains the Information Element and Information procedure.](65550960f5c5afd9d27706aaeddb0638_img.jpg)
+
+```
+
+graph TD
+    subgraph Application/FE
+        AppIM[App IM (AIM)] --> AppDM[App Data Model]
+    end
+    subgraph Ud_interface [Ud interface]
+        AppDV[App Data View]
+        AppDM2[App Data Model]
+        AppDM3[App Data Model Mapping]
+    end
+    subgraph Adaptation
+        AppDM4[App Data Model]
+        AppDM5[App Data Model Mapping]
+    end
+    subgraph UDR
+        IE[Information Element]
+        IP[Information procedure]
+    end
+
+    CBIM[Common Baseline IM (CBIM)] --> Custom[Customise to Operator's Services]
+    Custom --> SpIM[Specialized IM (SpIM)]
+    SpIM --> Integrate[Integrate AIM into SpIM and consolidate]
+    Integrate --> NewSpIM[Generate new SpIM]
+    NewSpIM --> CDM[Consolidated Data Model (CDM)]
+    CDM --> IE
+    CDM --> IP
+
+    Integrate --> AppDM
+    Integrate --> AppDV
+    Integrate --> AppDM2
+    Integrate --> AppDM3
+    Integrate --> AppDM4
+    Integrate --> AppDM5
+  
+```
+
+Figure 4.3-1: UDC Data and Information Models Overview with Operator integration model handling. The diagram illustrates the flow of information models from Common Baseline IM (CBIM) and App IM (AIM) through various processing steps to produce a Consolidated Data Model (CDM) and Information Elements. It is divided into three horizontal zones: Application/FE, Ud interface, and UDR. CBIM is customized to operator services to become a Specialized IM (SpIM). SpIM and AIM are integrated into SpIM and consolidated to generate ADM, mapping, and a new SpIM. This new SpIM is used to generate a new CDM, which becomes the Consolidated Data Model (CDM). The CDM is then used to generate Information Elements and Information procedures. The App IM (AIM) also leads to an App Data Model in the Application/FE. The Ud interface contains an App Data View, App Data Model, and App Data Model Mapping. The Adaptation zone contains the App Data Model and App Data Model Mapping. The UDR contains the Information Element and Information procedure.
+
+Figure 4.3-1 UDC Data and Information Models Overview with Operator integration model handling
+
+Figure 4.3-2 below shows the case of generation of the Application Data Model (ADM) for an Application/Front-End when the development of the application is not the responsibility of the operator. In this situation, both the CBIM and the AIM of the application are used to generate the ADM being implemented in the Application/Front-End.
+
+![Figure 4.3-2: UDC Data and Information Models Overview with separate ADM generation for the Application/Front-End. The diagram illustrates the flow from Common Baseline IM (CBIM) and App IM (AIM) through various processing steps to generate the App Data Model for the Application/Front-End, while also contributing to the Consolidated Data Model (CDM) in the UDR.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+```
+
+graph TD
+    CBIM[Common Baseline IM (CBIM)] --> GADM[Generate ADM for Appl/FE]
+    CBIM --> COS[Customise to Operator's Services]
+    COS --> SpIM[Specialized IM (SpIM)]
+    SpIM --> GCDM[Generate new CDM]
+    GCDM --> CDM[Consolidated Data Model (CDM)]
+    CDM --> IE[Information Element]
+    CDM --> IP[Information procedure]
+    AIM[App IM (AIM)] --> GADM
+    AIM --> IA[Integrate AIM into SpIM and consolidate]
+    IA --> GADM
+    IA --> GCDM
+    IA --> ADVM[Generate ADM and mapping and new SpIM]
+    ADVM --> ADVM_SUB[App Data View | App Data Model | App Data Model Mapping]
+    ADVM_SUB --> IE
+    ADVM_SUB --> IP
+    subgraph Application/FE
+        GADM --> ADM[App Data Model]
+    end
+    subgraph Ud interface
+    end
+    subgraph Adaptation
+    end
+    subgraph UDR
+        CDM
+        ADVM_SUB
+    end
+  
+```
+
+Figure 4.3-2: UDC Data and Information Models Overview with separate ADM generation for the Application/Front-End. The diagram illustrates the flow from Common Baseline IM (CBIM) and App IM (AIM) through various processing steps to generate the App Data Model for the Application/Front-End, while also contributing to the Consolidated Data Model (CDM) in the UDR.
+
+Figure 4.3-2 UDC Data and Information Models Overview with separate ADM generation for the Application/Front-End
+
+# 5 UDC information model infrastructure
+
+## 5.1 Common Baseline Information Model (CBIM)
+
+CBIM provides the basic structure of UDC IOCs. It shall enable an operator to integrate the user data to be stored in the UDR.
+
+## 5.2 Application Information Models (AIM)
+
+NOTE: The present clause introduces AIM. AIM may be imported from existing applications or may be generated from information elements already existing in the UDR.
+
+An AIM should contain IOCs for
+
+- the Service Profile(s) of the particular application,
+- Identifier(s) used by the application
+
+and additionally, if needed, any other IOC defined in CBIM. E.g. related End Device, if such is to be connected to one or more identifiers within the application.
+
+## 5.3 Specialised Information Model (SpIM)
+
+NOTE: The present clause describes building the SpIM from CBIM and AIMs with consolidation of semantically identical data.
+
+SpIM is the Information model containing all information to be stored in the UDR. A Specialized Information Model is operator specific. An implementation of the entire Specialized Information Model in the User Data Repository for all the applications leads to the Consolidated Data Model.
+
+# 6 UDC information model handling
+
+## 6.1 General
+
+The relations of the UDC information models are depicted in Figure 6.1-1 below.
+
+![Diagram illustrating the UDC Information Models. The diagram shows two input models, 'Common Baseline IM (CBIM)' and 'Appl IM (AIM)', leading to two processing steps: 'Customise to Operator's Services' and 'Integrate AIM into SpIM and consolidate'. Both steps lead to the final output model, 'Specialized IM (SpIM)'.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg)
+
+```
+graph TD; CBIM[Common Baseline IM (CBIM)] --> Customise[Customise to Operator's Services]; AIM[Appl IM (AIM)] --> Integrate[Integrate AIM into SpIM and consolidate]; Customise --> SpIM[Specialized IM (SpIM)]; Integrate --> SpIM;
+```
+
+Diagram illustrating the UDC Information Models. The diagram shows two input models, 'Common Baseline IM (CBIM)' and 'Appl IM (AIM)', leading to two processing steps: 'Customise to Operator's Services' and 'Integrate AIM into SpIM and consolidate'. Both steps lead to the final output model, 'Specialized IM (SpIM)'.
+
+Fig. 6.1-1 UDC Information Models
+
+Figure 6.1-2 below shows the process that leads to integrating and consolidating data for a given operator from the UDR perspective.
+
+Initially the Common Baseline Information Model (CBIM) is specialised according to the service and user structure of the given operator resulting in the initial version of the operator's the Specialized Information Model (SpIM).
+
+The actual version of the operator's Specialized Information Model (SpIM) is combined together with one or more Application Information Models (AIMs) to form a new version of the Specialized Information Model (SpIM) of the operator. The SpIM represents and considers all the data of all converged services offered by the operator.
+
+It is the decision of the operator, when a new actual version of the SpIM is implemented into the UDR. An implementation of the actual version of the SpIM into the UDR leads to the Consolidated Data Model (CDM), which is representing the actual implementation of the UDR.
+
+![Flowchart showing the hierarchy of information models: Common Baseline IM (CBIM) leads to Specialized IM (SpIM), which leads to Consolidated Data Model (CDM). Multiple Appl IM (AIM) boxes also point to the Consolidated Data Model (CDM).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+graph TD; CBIM[Common Baseline IM (CBIM)] --> SpIM[Specialized IM (SpIM)]; SpIM --> CDM[Consolidated Data Model (CDM)]; AIM1[Appl IM (AIM)] --> CDM; AIM2[Appl IM (AIM)] --> CDM; AIM3[Appl IM (AIM)] --> CDM; AIM4[Appl IM (AIM)] --> CDM; AIM5[Appl IM (AIM)] --> CDM; AIM6[Appl IM (AIM)] --> CDM; AIM7[Appl IM (AIM)] --> CDM;
+```
+
+Flowchart showing the hierarchy of information models: Common Baseline IM (CBIM) leads to Specialized IM (SpIM), which leads to Consolidated Data Model (CDM). Multiple Appl IM (AIM) boxes also point to the Consolidated Data Model (CDM).
+
+Figure 6.1-2: UDC Information and Data Models in the UDR
+
+Consider now integration for a given application. An Application Data Model (ADM) has to be developed both for the UDR and for the Application/Front-End to be used on the Ud interface.
+
+In the integrated model handling environment under responsibility of the operator implementation of the SpIM and the AIM of the application leads to the Application Data Model (ADM), this is depicted in Figure 6.1-3. The ADM gets implemented in the application FE and in the Application Data Model View in the UDR.
+
+![Flowchart showing the integration of information models: Common Baseline IM (CBIM) leads to Specialized IM (SpIM), which leads to Application Data Model (ADM). Appl IM (AIM) also leads to Application Data Model (ADM).](853f59c89931a666c07903b31d098277_img.jpg)
+
+```
+graph TD; CBIM[Common Baseline IM (CBIM)] --> SpIM[Specialized IM (SpIM)]; SpIM --> ADM[Application Data Model (ADM)]; AIM[Appl IM (AIM)] --> ADM;
+```
+
+Flowchart showing the integration of information models: Common Baseline IM (CBIM) leads to Specialized IM (SpIM), which leads to Application Data Model (ADM). Appl IM (AIM) also leads to Application Data Model (ADM).
+
+Figure 6.1-3: UDC Information and Data Model handling for an Application Type in an integrated Operator environment
+
+In the case of separate development of the Application Data Model (ADM) for an application on the Application/Front-End side, implementation of the CBIM and the AIM of the application leads to the ADM being implemented there. This is depicted in Figure 6.1-4.
+
+![Diagram showing the relationship between Common Baseline IM (CBIM), Appl IM (AIM), and Application Data Model (ADM).](cab0834804fb031b43865554cc8d06ab_img.jpg)
+
+```
+graph TD; CBIM[Common Baseline IM (CBIM)] --> ADM[Application Data Model (ADM)]; AIM[Appl IM (AIM)] --> ADM;
+```
+
+The diagram illustrates two input boxes at the top, 'Common Baseline IM (CBIM)' on the left and 'Appl IM (AIM)' on the right. Both boxes have blue outlines and blue text. Arrows point from each of these boxes down to a single, larger box at the bottom labeled 'Application Data Model (ADM)'. This bottom box also has a blue outline and blue text.
+
+Diagram showing the relationship between Common Baseline IM (CBIM), Appl IM (AIM), and Application Data Model (ADM).
+
+**Figure 6.1-4: Separate Information and Data Model handling for an Application Type for Application Front-End**
+
+## 6.2 Initial SpIM Creation from CBIM
+
+The Specialized Information Model is initially generated through operator specific specialisation of CBIM e.g. through definition of the operator-specific End-User groupings.
+
+## 6.3 AIM Integration into SpIM
+
+After the initial SpIM has been created, AIMs are imported and consolidated into it. The SpIM takes into account the specific applications, the functionality included and the relevant business information.
+
+## 6.4 Consolidation of User Data in the SpIM
+
+### 6.5.1 Example of consolidation of data in the SpIM using aggregation
+
+The Figure 6.5.1-1 below provides an example of building the SpIM by aggregating semantically identical data. Attributes that are common to at least two different service profiles are defined in IOCs that are then aggregated to these service profiles. For example, the Roaming1 IOC contains roaming data that is common to GPRS, EPS and CS service profiles, ODB3 contains operator determined barring data that is common to both GPRS and EPS service profiles and Trace contains data that is about subscriber and equipment trace common to all GPRS, CS, EPS and IMS profiles. Using aggregation means that the attribute value will be always same in each of the service profile that has aggregated the IOC where the attribute is defined. Note also that this example only shows how a portion of the data can be consolidated using aggregation.
+
+![UML Class Diagram showing aggregation relationships between Roaming classes and Service Profiles, and further down to BasicService, Trace, and ODB classes.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+The diagram illustrates a hierarchy of Information Object Classes (IOCs) using aggregation relationships, represented by lines with open diamond symbols. At the top level, three classes are shown: <<InformationObjectClass>> Roaming1, <<InformationObjectClass>> Roaming2, and <<InformationObjectClass>> Roaming3. Roaming1 and Roaming2 both aggregate <<InformationObjectClass>> UdcCsServiceProfile and <<InformationObjectClass>> UdcGprsServiceProfile. Roaming3 aggregates <<InformationObjectClass>> UdcEpsServiceProfile and <<InformationObjectClass>> UdcImssServiceProfile. Below these, <<InformationObjectClass>> UdcCsServiceProfile and <<InformationObjectClass>> UdcGprsServiceProfile both aggregate <<InformationObjectClass>> BasicService, <<InformationObjectClass>> Trace, and <<InformationObjectClass>> ODB1. <<InformationObjectClass>> UdcEpsServiceProfile aggregates <<InformationObjectClass>> Trace and <<InformationObjectClass>> ODB3. <<InformationObjectClass>> UdcImssServiceProfile also aggregates <<InformationObjectClass>> ODB3. At the bottom, <<InformationObjectClass>> BasicService, <<InformationObjectClass>> Trace, and <<InformationObjectClass>> ODB1 all aggregate <<InformationObjectClass>> ODB2. Additionally, <<InformationObjectClass>> ODB1 and <<InformationObjectClass>> ODB2 both aggregate <<InformationObjectClass>> ODB3.
+
+UML Class Diagram showing aggregation relationships between Roaming classes and Service Profiles, and further down to BasicService, Trace, and ODB classes.
+
+Figure 6.5.1-1: Consolidation of data in the SpIM using aggregation.
+
+### 6.5.2 Example of specialization for authentication methods
+
+Figure 6.5.2-1 shows an example of how the CBIM can be further specialized for the purpose of considering different authentication methods.
+
+![UML Class Diagram showing authentication methods and their relationships. Classes include UdcCsServiceProfile, UdcGprsServiceProfile, UdcEpsServiceProfile, UdcImsServiceProfile, CsAka, GprsAka, EpsAka, ImsAka, IMPU, IMSI, IMPI, SipDigest, NassImsBundled, GprsImsBundled, AkaUsim, ImsAkaUsimImsim, and ImsAkaImsim. Relationships include associations like CsSPUsesCsAka, GprsSPUsesPsAka, EpsSPUsesEpsAka, IMPUDerivesFromIMSI, IMPUPairsOrDerivesFromIMPI, IMPIDerivesFromIMSI, IMSIPairsAkaUsim, IMPIPairsImsAkaImsim, ImsAkaUsesImsAkaImsim, and ImsAkaUsesAkaUsim.](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+```
+
+classDiagram
+    class UdcCsServiceProfile
+    class UdcGprsServiceProfile
+    class UdcEpsServiceProfile
+    class UdcImsServiceProfile
+    class CsAka
+    class GprsAka
+    class EpsAka
+    class ImsAka
+    class IMPU
+    class IMSI
+    class IMPI
+    class SipDigest
+    class NassImsBundled
+    class GprsImsBundled
+    class AkaUsim
+    class ImsAkaUsimImsim
+    class ImsAkaImsim
+
+    UdcCsServiceProfile "0..1" *-- "0..*" CsAka : CsSPUsesCsAka
+    UdcGprsServiceProfile "0..*" *-- "0..*" GprsAka : GprsSPUsesPsAka
+    UdcEpsServiceProfile "0..*" *-- "0..*" EpsAka : EpsSPUsesEpsAka
+    UdcImsServiceProfile "0..1" *-- "0..*" ImsAka : IMSSPcontainsIMPU
+
+    IMPU "0..1" -- "0..1" IMSI : IMPUDerivesFromIMSI
+    IMPU "0..*" -- "0..*" IMPI : IMPUPairsOrDerivesFromIMPI
+    IMSI "0..1" -- "0..1" IMPI : IMPIDerivesFromIMSI
+
+    IMSI "1" -- "0..1" AkaUsim : IMSIPairsAkaUsim
+    IMPI "1" -- "0..1" ImsAkaImsim : IMPIPairsImsAkaImsim
+    ImsAkaImsim "1" -- "0..1" ImsAkaUsimImsim : ImsAkaUsesImsAkaImsim
+    ImsAkaUsimImsim "0..1" -- "0..1" AkaUsim : ImsAkaUsesAkaUsim
+
+    ImsAka "0..1" -- "0..*" NassImsBundled
+    ImsAka "0..1" -- "0..*" GprsImsBundled
+    ImsAka "0..1" -- "0..1" SipDigest
+  
+```
+
+UML Class Diagram showing authentication methods and their relationships. Classes include UdcCsServiceProfile, UdcGprsServiceProfile, UdcEpsServiceProfile, UdcImsServiceProfile, CsAka, GprsAka, EpsAka, ImsAka, IMPU, IMSI, IMPI, SipDigest, NassImsBundled, GprsImsBundled, AkaUsim, ImsAkaUsimImsim, and ImsAkaImsim. Relationships include associations like CsSPUsesCsAka, GprsSPUsesPsAka, EpsSPUsesEpsAka, IMPUDerivesFromIMSI, IMPUPairsOrDerivesFromIMPI, IMPIDerivesFromIMSI, IMSIPairsAkaUsim, IMPIPairsImsAkaImsim, ImsAkaUsesImsAkaImsim, and ImsAkaUsesAkaUsim.
+
+Figure 6.5.2-1: Authentication methods
+
+#### 6.5.3.1 AkaUsim
+
+##### 6.5.3.1.1 Definition
+
+This object class represents data that is required to perform Authentication and Key Agreement (AKA) when the UE is equipped with a USIM. For details of AKA see subclause 6.3 in 3GPP TS 33.102 [6]. For example, an encrypted subscriber key and the AMF can be attributes of this object class.
+
+#### 6.5.3.2 CsAka
+
+##### 6.5.3.2.1 Definition
+
+This object class represents data that is required to perform AKA when accessing Circuit-Switched services, such as the sequence number used for AKA authentication to access CS services. For details of AKA see subclause 6.3 in 3GPP TS 33.102 [6].
+
+#### 6.5.3.3 GPRS Aka
+
+##### 6.5.3.3.1 Definition
+
+This object class represents data that is required to perform AKA when accessing GPRS services such as the sequence number used for AKA authentication to access GPRS services. For details of AKA see subclause 6.3 in 3GPP TS 33.102 [6].
+
+#### 6.5.3.4 EpsAka
+
+##### 6.5.3.4.1 Definition
+
+This object class represents data that is required to perform AKA when accessing Evolved Packet-Switched services, such as the sequence number used for AKA authentication to access EPS services. For details of AKA see subclause 6.3 in 3GPP TS 33.102 [6].
+
+#### 6.5.3.5 ImsAkalsim
+
+##### 6.5.3.5.1 Definition
+
+This object class represents data that is required to perform IMS AKA for accessing IMS services when the UE is equipped with a UICC that contains an ISIM, for example, the encrypted subscriber key and AMF that is used for accessing IMS services. For details of IMS AKA see subclause 6.1 in 3GPP TS 33.203 [7].
+
+#### 6.5.3.6 ImsAka
+
+##### 6.5.3.6.1 Definition
+
+This object class represents data that is required to perform IMS AKA when accessing IMS services, such as the sequence number used for AKA authentication to access IMS services. For details of IMS AKA see subclause 6.1 in 3GPP TS 33.203 [7].
+
+#### 6.5.3.7 ImsAkaUsimIsim
+
+##### 6.5.3.7.1 Definition
+
+This object class represents the data that is required to perform IMS AKA for accessing IMS services when the UE is equipped with either a USIM or an ISIM, for example, the realm. It aggregates one of the AkaUsim or ImsAkaIsim object classes, depending on whether the UE is equipped with a USIM or an ISIM, respectively. For details of IMS AKA see subclause 6.1 in 3GPP TS 33.203 [7].
+
+#### 6.5.3.8 GPRSImdBundled
+
+##### 6.5.3.8.1 Definition
+
+This abstract object class represents the data that is required to perform GPRS-IMS bundled authentication. For details of the GPRS-IMS bundled authentication see 3GPP TS 33.203 [6] Annex T.
+
+NOTE: This object class is set to be abstract because it does not need any new particular data. The GPRS-IMS bundled authentication requires the IPv4 address or IPv6 prefix allocated by GPRS to the UE, therefore, data that is stored elsewhere. This object class is merely here for completeness, but need not be implemented.
+
+#### 6.5.3.9 NassImdBundled
+
+##### 6.5.3.9.1 Definition
+
+This object class represents the data that is required to perform NASS-IMS bundled authentication, such as the line identifier. For details of the NASS-IMS bundled authentication see 3GPP TS 33.203 [6] Annex R.
+
+#### 6.5.3.10 SipDigest
+
+##### 6.5.3.10.1 Definition
+
+This object class represents the data that is required to perform SIP Digest authentication for accessing IMS services. For example, it includes the H(A1) parameter of HTTP Digest, the realm, QoP, and Algorithm directives in HTTP Digest authentication. For details of the SIP Digest authentication see 3GPP TS 33.203 [6] Annex N.
+
+## 6.5 Construction of AIM
+
+An AIM comprises all the information required by an application. In the construction of an AIM, the following possibilities exist with respect to the current version of the SpIM:
+
+- AIMs may be constructed from new information not yet present in the current version of the SpIM.
+- AIMs may be constructed by using information that already exists in the current version of the SpIM.
+- AIMs may be constructed requiring both new information and information that already exists in the current version of the SpIM.
+
+# --- 7 Application management
+
+## 7.1 Application Access Control Data
+
+Specification 23.335 [8] in Chapter 5.2 defines the requirements for application access to the UDR including authentication and authorisation.
+
+To be able to authenticate an application and to provide it access data in the UDR the following have to be stored:
+
+- identity of the application including additional access protocol dependent authentication information (e.g. password)
+- type of the application with associated Data Model
+
+To be able to authorise an application for access to data in the UDR the following have to be stored:
+
+- allowed PLMN-Id(s)
+- allowed operations with the associated Data Model
+- restrictions on operations possibly at information element level.
+
+## 7.2 Application Data Model and Mapping to Consolidated Data Model
+
+### 7.2.1 Application Data Views
+
+Different applications have different needs when accessing the data. Consider a piece of data: some applications may need to read and write that data; other applications will only need to read the same data; and a third group of applications should not be able to access that data at all. Since the UDR implements the CDM, there must exist a mechanism to control the access of data per application, so that only the authorised subset of the CDM is exposed to that application with the correct access permissions, details on primary access control are to be found in Chapter 7.1 of this specification.
+
+Access only to the authorised subset of the CDM is achieved by implementing Application Data Views in the UDR connected to the different application types. The concept is illustrated in Figure 7.2.1-1 in a simplified way. A detailed figure is given in Figure 7.2.1-2, and a more developed concept (considering different vendors) is provided in Figure 7.2.1-3.
+
+According to Figure 7.2.1-1 , the UDR implements the CDM. Application Data Views are implemented for each application type accessing its specific user data within CDM in the UDR. The Application Data View is responsible for enabling and limiting applications access to data within the UDR.
+
+![Figure 7.2.1-1: Application Data Views in the UDR (simplified). A central circle labeled 'CDM' is surrounded by three segments: 'App. 1 Data View' (blue), 'App. 2 Data View' (purple), and 'App. 3 Data View' (green). Three boxes labeled 'FE 1', 'FE 2', and 'FE 3' are positioned outside the circle, with double-headed arrows pointing from each box to its corresponding data view segment.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+Figure 7.2.1-1: Application Data Views in the UDR (simplified). A central circle labeled 'CDM' is surrounded by three segments: 'App. 1 Data View' (blue), 'App. 2 Data View' (purple), and 'App. 3 Data View' (green). Three boxes labeled 'FE 1', 'FE 2', and 'FE 3' are positioned outside the circle, with double-headed arrows pointing from each box to its corresponding data view segment.
+
+Figure 7.2.1-1: Application Data Views in the UDR (simplified)
+
+![Figure 7.2.1-2: Correlation of IM and Application Data View for a single Application type in the UDR. A box labeled 'App IM (AIM)' has arrows pointing to a table and a box labeled 'Specialized IM (SpIM)'. The 'Specialized IM (SpIM)' box also has an arrow pointing to the table. The table has three rows: 'App Data View' (spanning all three rows), 'App Data Model', 'App Data Model Mapping', and 'Capabilities for Apps'.](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+|               |                        |
+|---------------|------------------------|
+| App Data View | App Data Model         |
+|               | App Data Model Mapping |
+|               | Capabilities for Apps  |
+
+Figure 7.2.1-2: Correlation of IM and Application Data View for a single Application type in the UDR. A box labeled 'App IM (AIM)' has arrows pointing to a table and a box labeled 'Specialized IM (SpIM)'. The 'Specialized IM (SpIM)' box also has an arrow pointing to the table. The table has three rows: 'App Data View' (spanning all three rows), 'App Data Model', 'App Data Model Mapping', and 'Capabilities for Apps'.
+
+Figure 7.2.1-2: Correlation of IM and Application Data View for a single Application type in the UDR
+
+In a multi-vendor scenario, for a given application type, each Front End vendor and application version may implement their own data model. Therefore, data models for the same application need not be equal across different vendors or release of the software. This scenario conceptually requires a different application data model mapping for each application and vendor. The concept is illustrated in Figure 7.2.1-3. For each application type, there can be a number of Application Data Views, each one handling the mapping to the particular data model of the vendor of the Front End. For example, for Application type #1, there can be three Front End vendors, named FE<sub>1</sub>, FE<sub>2</sub>, FE<sub>3</sub>, respectively. Each of these front ends implements its own data model. A different Application Data View handles the correct mapping to each data model. In Figure 7.2.1-3, Application Data View 1<sub>1</sub> manages FE<sub>1</sub>, Application Data View 1<sub>2</sub> manages FE<sub>2</sub>, Application Data View 1<sub>3</sub> manages FE<sub>3</sub>, and so on.
+
+![Diagram illustrating Application Data Views in the UDR. A central circle labeled 'CD' is surrounded by segments labeled 'App 1_1', 'App 1_2', 'App 1_3', 'App 2_1', 'App 2_2', 'App 2_3', 'App 3_1', 'App 3_2', and 'App 3_3'. Each application segment is connected to a group of Functional Entity (FE) blocks. App 1_1 connects to FE 1_1, FE 1_2, and FE 1_3. App 1_2 connects to FE 1_1, FE 1_2, and FE 1_3. App 1_3 connects to FE 1_1, FE 1_2, and FE 1_3. App 2_1 connects to FE 2_1, FE 2_2, and FE 2_3. App 2_2 connects to FE 2_1, FE 2_2, and FE 2_3. App 2_3 connects to FE 2_1, FE 2_2, and FE 2_3. App 3_1 connects to FE 3_1, FE 3_2, and FE 3_3. App 3_2 connects to FE 3_1, FE 3_2, and FE 3_3. App 3_3 connects to FE 3_1, FE 3_2, and FE 3_3.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+Diagram illustrating Application Data Views in the UDR. A central circle labeled 'CD' is surrounded by segments labeled 'App 1\_1', 'App 1\_2', 'App 1\_3', 'App 2\_1', 'App 2\_2', 'App 2\_3', 'App 3\_1', 'App 3\_2', and 'App 3\_3'. Each application segment is connected to a group of Functional Entity (FE) blocks. App 1\_1 connects to FE 1\_1, FE 1\_2, and FE 1\_3. App 1\_2 connects to FE 1\_1, FE 1\_2, and FE 1\_3. App 1\_3 connects to FE 1\_1, FE 1\_2, and FE 1\_3. App 2\_1 connects to FE 2\_1, FE 2\_2, and FE 2\_3. App 2\_2 connects to FE 2\_1, FE 2\_2, and FE 2\_3. App 2\_3 connects to FE 2\_1, FE 2\_2, and FE 2\_3. App 3\_1 connects to FE 3\_1, FE 3\_2, and FE 3\_3. App 3\_2 connects to FE 3\_1, FE 3\_2, and FE 3\_3. App 3\_3 connects to FE 3\_1, FE 3\_2, and FE 3\_3.
+
+Figure 7.2.1-3: Application Data Views in the UDR
+
+## 7.3 Subscription and Notification Related Data
+
+Specification 23.335 [8] in Chapter 5.7 and 5.8 defines the procedure of subscription and notification. Specification 29.335[9] in Chapter 6.6, 6.7 and Annex A defines the content and format of the subscription and notification messages.
+
+Subscription can be done by subscription message (dynamic) or configuration of the UDR (permanent). To support both kinds of subscription and to allow authorised unsubscribe operations, the following information should be stored in the UDR:
+
+- type of subscription, dynamic or permanent
+- user identifier, e.g. IMSI, MSISDN, IMS public user identity or IMS private user identity, if not specified the subscription is applicable to all users' data of the application in the UDR.
+- information on the data requested to be observed
+- identity of the original (originating) subscribing entity identity, this item indicates the original entity which sent the subscription request message to the FE in order to subscribe to the notification of the specific events of the data requested to be observed
+- notification condition(s), this item indicates the specific events on which the notification shall be triggered. The triggering events shall consist of one or more of the following: the addition of the observed data, the deletion of the observed data or the changes of the observed data.
+- type of notification, this item indicates whether this subscription request should lead to a notification to any FE of the application type or cluster identifier, or to a notification to the FE requesting the notification.to originating entity or to an FE/application based on actual selection
+
+To support dynamic subscriptions the following information has to be stored in the UDR:
+
+- the subscription expiry time
+- the identifier of the FE or the FE Cluster which sent the subscription message (conditional, if the notification type indicates that the notification is to be sent to the FE requesting the subscription, this item is needed.)
+
+To support the notification of data modification, the following information should be stored in the UDR:
+
+- additional data to be sent to the application in the notification when the notification condition is met
+
+- the FE selection algorithm (conditional, if the notification type indicates that the notification is to be sent to any FE of the application type or cluster identifier, this item is needed. This is only the identifier of the selection algorithm, not the algorithm itself.)
+
+If the Notification Type indicates that the notification is to be sent to any FE, when the notification condition is met, the UDR should use the FE select algorithm to select a proper FE to notify. For example, the UDR may select to notify the application actually serving the user.
+
+# --- 8 Consolidated data model management
+
+## 8.1 Lifecycle Management of the Consolidated Data Model in the UDR
+
+Figure 8.1-1 below shows the operational environment of UDC according to Figure 4.3-1. The Provisioning Gateway is an additional aspect which is essential for the operation of the UDR. The Provisioning Gateway provides a single logical point for consistent provisioning of user data for all services in the UDR. The mechanism used by the Provisioning Gateway to access UDR data using the CDM is outside the scope of the present document. The Application boxes denote Application Front Ends including Provisioning Front Ends according to 23.335 [8]. The Provisioning Front Ends access UDR data via the Ud reference point and are restricted by their Application Data Model.
+
+Chapter 4.3 describes how AIM(s) may be added and consolidated into the SpIM and the generation of the Application Data Model and its mapping to the CDM. It is the decision of the operator when the newly added AIM(s) may become operational.
+
+It is the decision of the operator, when a new actual version of the SpIM with the newly added AIM(s) is implemented into the UDR as actual version of the CDM.
+
+The Provisioning Gateway provides a view of the actual version of the CDM to enable provisioning of all data stored by different applications in the UDR.
+
+The CDM implementation into the UDR is an atomic operation.
+
+![Figure 8.1-1: Evolution of the CDM in a UDR. The diagram illustrates the process of updating the Consolidated Data Model (CDM) in a User Data Repository (UDR). At the top, a green box labeled 'BSS' points down to a blue box labeled 'Provisioning Gateway'. The 'Provisioning Gateway' points down to a circular diagram representing the 'Consolidated Data Model (CDM)'. This circle is divided into segments: 'Full Data View' (yellow), 'Appl 1 View' (yellow), 'Appl 2 view' (green), 'APPL3 view' (red), and 'APPL 1 view' (pink). To the right, 'Appl 1' (yellow box) and 'Appl 2' (green box) are connected to the circle via arrows labeled 'Ud'. Below the circle, a red box labeled 'new Appl' points up to the circle via an arrow labeled 'Ud'. To the left, a green box labeled 'new AIM' points up to a grey box labeled 'Generate ADM and mapping and new SpIM'. This grey box points to the 'APPL3 view' and 'APPL 1 view' segments. Above it, another grey box labeled 'Generate new CDM' points to the 'Full Data View' segment and to a green box labeled 'SpIM'. The 'SpIM' box points to the 'new AIM' box.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+Figure 8.1-1: Evolution of the CDM in a UDR. The diagram illustrates the process of updating the Consolidated Data Model (CDM) in a User Data Repository (UDR). At the top, a green box labeled 'BSS' points down to a blue box labeled 'Provisioning Gateway'. The 'Provisioning Gateway' points down to a circular diagram representing the 'Consolidated Data Model (CDM)'. This circle is divided into segments: 'Full Data View' (yellow), 'Appl 1 View' (yellow), 'Appl 2 view' (green), 'APPL3 view' (red), and 'APPL 1 view' (pink). To the right, 'Appl 1' (yellow box) and 'Appl 2' (green box) are connected to the circle via arrows labeled 'Ud'. Below the circle, a red box labeled 'new Appl' points up to the circle via an arrow labeled 'Ud'. To the left, a green box labeled 'new AIM' points up to a grey box labeled 'Generate ADM and mapping and new SpIM'. This grey box points to the 'APPL3 view' and 'APPL 1 view' segments. Above it, another grey box labeled 'Generate new CDM' points to the 'Full Data View' segment and to a green box labeled 'SpIM'. The 'SpIM' box points to the 'new AIM' box.
+
+Figure 8.1-1: Evolution of the CDM in a UDR
+
+## 8.2 Activation and Deactivation of Application Adaptation
+
+As described above the operator shall be capable of
+
+- adding new AIM to SpIM, described in Chapter 4.3
+- adding ADM to UDR together with adaptation to CDM as described in Chapter 4.3 and 8.1.
+- generate and activate new actual CDM based on the current SpIM as described in Chapter 8.1 above
+- activate the access of the application to its data in the UDR which can only be done after the implementation of the CDM containing that data and is done by associating the proper Application Data View to the application.
+- deactivate the access of the application to its data in the UDR which is needed when, for example, the data of the application have changed. Deactivation is done by deleting the current association of Application Data View to the application.
+
+# 9 Relation to other Information Models
+
+## 9.1 Relation to SuM Network Resource Model
+
+The 3GPP SuM NRM as defined in the TS 32.172 [10] contains the information model related to the provisioning of the data of 3GPP services stored in the UDR.
+
+# Annex A (informative): Change history
+
+| Change history |       |           |     |     |                                             |       |        |
+|----------------|-------|-----------|-----|-----|---------------------------------------------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                             | Old   | New    |
+| 2010-03        | SA#47 | SP-100066 | --  | --  | Presentation to SA for information          | --    | 1.0.0  |
+| 2010-06        | SA#48 | SP-100372 | --  | --  | Presentation to SA for approval             | 1.0.0 | 2.0.0  |
+| 2010-06        | SA#48 | --        | --  | --  | Publication                                 | 2.0.0 | 9.0.0  |
+| 2010-09        | SA#49 | SP-100489 | 001 | --  | Correct inconsistency of PsAka with GprsAka | 9.0.0 | 10.0.0 |

marked/Rel-10/32_series/32182/raw.md

@@ -0,0 +1,620 @@
+
+
+Keywords  
+UDC, 3GPP
+
+# 3GPP TS 32.182 V10.0.0 (2011-03) ---
+
+*Technical Specification*
+
+**3GPP**  
+**3rd Generation Partnership Project;**  
+**Technical Specification Group Services and System Aspects;**  
+**Telecommunication management;**  
+**User Data Convolution (UDC);**  
+**Common Baseline Informatic**
+
+---
+
+3GPP support office address  
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 10
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font with a red signal icon below the 'G'.
+
+3GPP logo
+
+Internet  
+<http://www.3gpp.org>
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP..
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                          |    |
+|----------------------------------------------------------|----|
+| Foreword .....                                           | 5  |
+| Introduction .....                                       | 5  |
+| 1 Scope.....                                             | 6  |
+| 2 References.....                                        | 6  |
+| 3 Definitions and abbreviations .....                    | 6  |
+| 3.1 Definitions.....                                     | 6  |
+| 3.2 Abbreviations .....                                  | 7  |
+| 4 Modelling Approach .....                               | 8  |
+| 5 Information Object Classes.....                        | 8  |
+| 5.1 Imported Information Entities and Local Labels ..... | 8  |
+| 5.2 Class Diagram .....                                  | 8  |
+| 5.2.1 Attributes and relationships.....                  | 8  |
+| 5.2.2 Inheritance.....                                   | 9  |
+| 5.3 Information Object Class Definitions .....           | 10 |
+| 5.3.1 EndUser .....                                      | 10 |
+| 5.3.1.1 Definition .....                                 | 10 |
+| 5.3.2 Identifier .....                                   | 10 |
+| 5.3.2.1 Definition .....                                 | 10 |
+| 5.3.3 UdcServiceProfile .....                            | 10 |
+| 5.3.3.1 Definition .....                                 | 10 |
+| 5.3.4 EndDevice.....                                     | 10 |
+| 5.3.4.1 Definition .....                                 | 10 |
+| 5.3.5 UdcCsServiceProfile.....                           | 10 |
+| 5.3.5.1 Definition .....                                 | 10 |
+| 5.3.6 UdcGprsServiceProfile.....                         | 11 |
+| 5.3.6.1 Definition .....                                 | 11 |
+| 5.3.7 UdcEpsServiceProfile .....                         | 11 |
+| 5.3.7.1 Definition .....                                 | 11 |
+| 5.3.8 UdcImsServiceProfile .....                         | 11 |
+| 5.3.8.1 Definition .....                                 | 11 |
+| 5.3.9 MSISDN.....                                        | 11 |
+| 5.3.9.1 Definition .....                                 | 11 |
+| 5.3.10 IMSI.....                                         | 11 |
+| 5.3.10.1 Definition .....                                | 11 |
+| 5.3.11 IMPI.....                                         | 11 |
+| 5.3.11.1 Definition .....                                | 11 |
+| 5.3.12 IMPU.....                                         | 12 |
+| 5.3.12.1 Definition .....                                | 12 |
+| 5.3.13 E164.....                                         | 12 |
+| 5.3.13.1 Definition .....                                | 12 |
+| 5.3.14 NAI.....                                          | 12 |
+| 5.3.14.1 Definition .....                                | 12 |
+| 5.3.15 TelURI.....                                       | 12 |
+| 5.3.15.1 Definition .....                                | 12 |
+| 5.3.16 SIPURI.....                                       | 12 |
+| 5.3.16.1 Definition .....                                | 12 |
+| 5.3.17 UdcEndUserGroup .....                             | 12 |
+| 5.3.17.1 Definition .....                                | 12 |
+| 5.3.18 UdcSubscription .....                             | 13 |
+| 5.3.18.1 Definition .....                                | 13 |
+| 5.4 Information Relationship Definitions.....            | 13 |
+| 5.4.1. SubscriptionDeterminesSP.....                     | 13 |
+| 5.4.1.1 Definition .....                                 | 13 |
+| 5.4.2 SPMayIncludeID.....                                | 13 |
+
+|                        |                                 |    |
+|------------------------|---------------------------------|----|
+| 5.4.2.1                | Definition .....                | 13 |
+| 5.4.3                  | EUHasSP .....                   | 13 |
+| 5.4.3.1                | Definition .....                | 13 |
+| 5.4.4                  | IdentifierPairsIdentifier ..... | 13 |
+| 5.4.4.1                | Definition .....                | 13 |
+| 5.4.5                  | EUIDentifiedByID.....           | 13 |
+| 5.4.5.1                | Definition .....                | 13 |
+| 5.4.6                  | GroupMembership .....           | 14 |
+| 5.4.6.1                | Definition .....                | 14 |
+| 5.4.7                  | TemporarilyPaired .....         | 14 |
+| 5.4.7.1                | Definition .....                | 14 |
+| 5.4.8                  | CSSPcontainsMSISDN.....         | 14 |
+| 5.4.8.1                | Definition .....                | 14 |
+| 5.4.9                  | GPRSSPcontainsMSISDN.....       | 14 |
+| 5.4.9.1                | Definition .....                | 14 |
+| 5.4.10                 | EPSSPcontainsMSISDN.....        | 14 |
+| 5.4.10.1               | Definition .....                | 14 |
+| 5.4.11                 | IMSSPcontainsIMPU .....         | 14 |
+| 5.4.11.1               | Definition .....                | 14 |
+| 5.4.12                 | MSISDNPairsIMSI .....           | 15 |
+| 5.4.12.1               | Definition .....                | 15 |
+| 5.4.13                 | IMPIDerivesFromIMSI.....        | 15 |
+| 5.4.13.1               | Definition .....                | 15 |
+| 5.4.14                 | IMPUPairsOrDerivesFromIMPI..... | 15 |
+| 5.4.14.1               | Definition .....                | 15 |
+| 5.4.15                 | IMPUDerivesFromIMSI.....        | 15 |
+| 5.4.15.1               | Definition .....                | 15 |
+| 5.4.16                 | MSISDNTakesFormatOfE164 .....   | 15 |
+| 5.4.16.1               | Definition .....                | 15 |
+| 5.4.17                 | IMPITakesFormatOfNAI .....      | 15 |
+| 5.4.17.1               | Definition .....                | 15 |
+| 5.4.18                 | IMPUTakesFormatOfTelURI .....   | 16 |
+| 5.4.18.1               | Definition .....                | 16 |
+| 5.4.19                 | IMPUTakesFormatOfSIPURI .....   | 16 |
+| 5.4.19.1               | Definition .....                | 16 |
+| 5.4.20                 | TelURIDerivesFromE164.....      | 16 |
+| 5.4.20.1               | Definition .....                | 16 |
+| Annex A (informative): | Change history.....             | 17 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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
+
+User Data Convergence (UDC) presents a layered architecture where user data is accessible at a logically unique repository called User Data Repository (UDR). One or more dataless applications access the user data that is stored in the UDR. In this context, applications can be front ends, for example an HSS-FE or an HLR-FE, or application servers. In order to support UDC, a Common Baseline Information Model is defined in this specification.
+
+# --- 1 Scope
+
+The present document specifies a Common Baseline Information Model for UDC [2]. This information model denotes an abstract, formal representation of entity types that are common to many applications using the UDR. CBIM describes the basic IOCs of UDC, their properties and their relationships. Detailed requirements for the specification of this Common Baseline Information Model are given in 3GPP TR 22.985 [2] and 3GPP TS 22.101 [3].
+
+From the Common Baseline Information Model specialized information models and data models can be derived. All these derived models are out of the scope of this specification.
+
+# --- 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 TR 22.985: "Service requirement for the User Data Convergence (UDC)".
+- [3] 3GPP TS 22.101: "Service aspects; Service principles".
+- [4] 3GPP TS 32.151: "Integration Reference Point (IRP) Information Service (IS) template (Release 8)".
+- [5] 3GPP TS 32.152: "Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire (Release 8)".
+- [6] 3GPP TS 23.003: "Numbering, addressing and identification; (Release 8)".
+- [7] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2; (Release 8)".
+- [8] ITU-T Recommendation E.164: "The International Public Telecommunication Numbering Plan".
+- [9] IETF RFC 4282: "The Network Access Identifier".
+- [10] IETF RFC 3966: "The tel URI for Telephone Numbers".
+- [11] IETF RFC 3261: "SIP: Session Initiation Protocol".
+- [12] 3GPP TS 32.181: "User Data Convergence; Framework for Model Handling and Management".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Common Baseline Information Model:** an abstract, formal representation of entity types common to many applications using the UDR. CBIM describes the basic IOCs of UDC, their properties and their relationships, so that these IOCs constitute the baseline for any given application. Therefore, CBIM provides flexibility (in its data structure
+
+and content), extensibility and multi-application approach. In particular, CBIM provides support for the concepts of Subscription, Service Profile, End User, Identifiers, End User Group, and End Device, among others. CBIM does not define the models that are associated with each application and that are under their responsibility.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] 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].
+
+|        |                                          |
+|--------|------------------------------------------|
+| CBIM   | Common Baseline Information Model        |
+| UE     | User Equipment                           |
+| FE     | Front End                                |
+| IRP    | Integration Reference Point              |
+| IMPI   | IP Multimedia Private User Identity      |
+| IMPU   | IP Multimedia Public User Identity       |
+| IMS    | IP Multimedia Subsystem                  |
+| IMSI   | International Mobile Subscriber Identity |
+| ISDN   | Integrated Services Digital Network      |
+| IS     | Information Service                      |
+| ISIM   | IM Services Identity Module              |
+| MSISDN | Mobile Subscriber ISDN Number            |
+| NAI    | Network Access Identifier                |
+| UDC    | User Data Convergence                    |
+| UDR    | User Data Repository                     |
+| UML    | Unified Modelling Language               |
+| URI    | Uniform Resource Identifier              |
+
+# 4 Modelling Approach
+
+The CBIM is not an Integration Reference Point (IRP) as it is not used for a management interface; however this specification follows the IRP IS template specified in 3GPP TS 32.151 [4] and reuses the UML repertoire described in 3GPP TS 32.152 [5].
+
+NOTE: The intention of CBIM is to provide the basic common IOCs of UDC, including their definitions and relationships. Attributes of the IOCs are not intended to be part of this specification.
+
+# 5 Information Object Classes
+
+## 5.1 Imported Information Entities and Local Labels
+
+## 5.2 Class Diagram
+
+### 5.2.1 Attributes and relationships
+
+![UML Class Diagram showing UdcServiceProfile, UdcSubscription, EndUser, Identifier, UdcEndUserGroup, and EndDevice classes and their relationships.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+```
+classDiagram
+    class UdcServiceProfile
+    class UdcSubscription
+    class EndUser
+    class Identifier
+    class UdcEndUserGroup
+    class EndDevice
+
+    UdcServiceProfile "0..*" -- "0..1" UdcSubscription : SubscriptionDeterminesSP
+    EndUser "1" -- "0..*" UdcServiceProfile : EUHasSP
+    EndUser "1" -- "0..*" Identifier : EUIdentifiedByD
+    EndUser "0..*" -- "0..*" UdcEndUserGroup : GroupMembership
+    Identifier "0..*" -- "0..*" EndDevice : TemporarilyPaired
+    Identifier "0..*" -- "0..*" Identifier : IdentifierPairsIdentifier
+    UdcServiceProfile "0..*" -- "0..*" Identifier : SPMayIncludeID
+```
+
+The diagram illustrates the UDC CBIM Core View with the following classes and relationships:
+
+- UdcServiceProfile** (Information Object Class) has a relationship with **UdcSubscription** (Information Object Class) labeled *SubscriptionDeterminesSP*. Multiplicity: 0..\* to 0..1.
+- EndUser** (Information Object Class) has a relationship with **UdcServiceProfile** labeled *EUHasSP*. Multiplicity: 1 to 0..\*.
+- EndUser** has a relationship with **Identifier** (Information Object Class) labeled *EUIdentifiedByD*. Multiplicity: 1 to 0..\*.
+- EndUser** has a relationship with **UdcEndUserGroup** (Information Object Class) labeled *GroupMembership*. Multiplicity: 0..\* to 0..\*.
+- Identifier** has a relationship with **EndDevice** (Information Object Class) labeled *TemporarilyPaired*. Multiplicity: 0..\* to 0..\*.
+- Identifier** has a self-relationship labeled *IdentifierPairsIdentifier*. Multiplicity: 0..\* to 0..\*.
+- UdcServiceProfile** has a relationship with **Identifier** labeled *SPMayIncludeID*. Multiplicity: 0..\* to 0..\*.
+
+UML Class Diagram showing UdcServiceProfile, UdcSubscription, EndUser, Identifier, UdcEndUserGroup, and EndDevice classes and their relationships.
+
+Figure 5.2.1-1: UDC CBIM Core View
+
+![UML Class Diagram showing relationships between service profiles and identifiers.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+```
+
+classDiagram
+    class UdcCsServiceProfile
+    class UdcGprsServiceProfile
+    class UdcEpsServiceProfile
+    class UdcImssServiceProfile
+    class MSISDN
+    class IMSI
+    class IMPI
+    class IMPU
+    class E164
+    class NAI
+    class TelURI
+    class SIPURI
+
+    UdcCsServiceProfile "0..1" *-- "0..*" MSISDN : CSSPcontainsMSISDN
+    UdcGprsServiceProfile "0..1" *-- "0..*" MSISDN : GPRSSPcontainsMSISDN
+    UdcEpsServiceProfile "0..1" *-- "0..*" IMSI : EPSSPcontainsMSISDN
+    UdcImssServiceProfile "0..*" *-- "0..1" IMPU : IMSSPcontainsIMPU
+
+    MSISDN "0..*" -- "0..*" IMSI : MSISDNPairsIMSI
+    IMSI "0..1" -- "0..1" IMPI : IMPIDerivesFromIMSI
+    IMPI "0..*" -- "0..*" IMPU : IMPUPairsOrDerivesFromIMPI
+
+    MSISDN "1" -- "1" E164 : MSISDNTakesFormatOfE164
+    IMSI "1" -- "1" NAI : IMPITakesFormatOfNAI
+    IMPI "1" -- "1" TelURI : IMPUTakesFormatOfTelURI
+    IMPU "1" -- "1" SIPURI : IMPUTakesFormatOfSIPURI
+
+    TelURI "1" -- "0..1" E164 : TelURIDerivesFromE164
+  
+```
+
+UML Class Diagram showing relationships between service profiles and identifiers.
+
+**Figure 5.2.1-2: Identifiers**
+
+### 5.2.2 Inheritance
+
+![UML Class Diagram showing inheritance from UdcServiceProfile.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+```
+
+classDiagram
+    class UdcServiceProfile
+    class UdcCsServiceProfile
+    class UdcGprsServiceProfile
+    class UdcEpsServiceProfile
+    class UdcImssServiceProfile
+
+    UdcCsServiceProfile --|> UdcServiceProfile
+    UdcGprsServiceProfile --|> UdcServiceProfile
+    UdcEpsServiceProfile --|> UdcServiceProfile
+    UdcImssServiceProfile --|> UdcServiceProfile
+  
+```
+
+UML Class Diagram showing inheritance from UdcServiceProfile.
+
+**Figure 5.2.2-1: UdcServiceProfile inheritance**
+
+![UML Class Diagram showing inheritance from Identifier.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+```
+
+classDiagram
+    class Identifier
+    class MSISDN
+    class IMSI
+    class IMPI
+    class IMPU
+
+    MSISDN --|> Identifier
+    IMSI --|> Identifier
+    IMPI --|> Identifier
+    IMPU --|> Identifier
+  
+```
+
+UML Class Diagram showing inheritance from Identifier.
+
+**Figure 5.2.2-2: Identifier inheritance**
+
+## 5.3 Information Object Class Definitions
+
+### 5.3.1 EndUser
+
+#### 5.3.1.1 Definition
+
+In this context this object class represents an End User (as per 3GPP TS 21.905 [1]). This class represents the view that the telecommunication network has about the end user and contains the valid parameters that define the End User from UDC point of view. An EndUser object class has an End-User Identity attribute (EUI), which is described in 3GPP TS 21.905 [1].
+
+### 5.3.2 Identifier
+
+#### 5.3.2.1 Definition
+
+This abstract object class represents an end user identifier that is used within the network so that the different network functionalities can be used (mobility management, authentication, and service usage). This is an abstract IOC that can be inherited by the real identifier used in the network, like IMSI, MSISDN, IMPI, IMPU, etc.
+
+NOTE: This object does not include identities that are not associated to a user, such as an IMEI, hostID, etc.
+
+### 5.3.3 UdcServiceProfile
+
+#### 5.3.3.1 Definition
+
+This object class represents the data characterizing a service assigned to an EndUser. It includes service preferences and settings chosen for an EndUser. The service profile contains the permanent and temporary data pertaining to an end user that is subscribed to a service. This IOC can be inherited by different service profiles, such as CS, GPRS, EPS, IMS service profiles and so on.
+
+### 5.3.4 EndDevice
+
+#### 5.3.4.1 Definition
+
+This object class represents a composite of hardware and software that implements service terminal functions and that the EndUser operates in order to get access to telecommunication services.
+
+### 5.3.5 UdcCsServiceProfile
+
+#### 5.3.5.1 Definition
+
+This object class represents the part of the UdcServiceProfile that contains data related to Circuit-Switched services. An example of further specialization of this object class, including attributes, is provided in 3GPP TS 32.181 [12].
+
+### 5.3.6 UdcGprsServiceProfile
+
+#### 5.3.6.1 Definition
+
+This object class represents the part of the UdcServiceProfile that contains data related to Packet-Switched services. An example of further specialization of this object class, including attributes, is provided in 3GPP TS 32.181 [12].
+
+### 5.3.7 UdcEpsServiceProfile
+
+#### 5.3.7.1 Definition
+
+This object class represents the part of the `UdcServiceProfile` that contains data related to the Evolved Packet System services. An example of further specialization of this object class, including attributes, is provided in 3GPP TS 32.181 [12].
+
+### 5.3.8 UdcImServiceProfile
+
+#### 5.3.8.1 Definition
+
+This object class represents the part of the `UdcServiceProfile` that contains data related to IMS services. An example of further specialization of this object class, including attributes, is provided in 3GPP TS 32.181 [12].
+
+### 5.3.9 MSISDN
+
+#### 5.3.9.1 Definition
+
+In this context this object class represents a Mobile Subscriber Integrated Services Digital Network Number (as per 3GPP TS 23.003 [6]). An MSISDN is allocated from an E.164 numbering plan.
+
+### 5.3.10 IMSI
+
+#### 5.3.10.1 Definition
+
+In this context this object class represents an International Mobile Subscriber Identity (as per 3GPP TS 23.003 [6]).
+
+### 5.3.11 IMPI
+
+#### 5.3.11.1 Definition
+
+In this context this object class represents an IMS Private User Identity (as per 3GPP TS 23.228 [7]). The Private User Identity takes the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [9]. It is possible for a representation of the IMSI to be contained within the NAI for the private user identity.
+
+### 5.3.12 IMPU
+
+#### 5.3.12.1 Definition
+
+In this context this object class represents an IMS Public User Identity (as per 3GPP TS 23.228 [7]). An IMPU takes the form of either a SIP URI (see IETF RFC 3261 [11]) or a Tel URI (see IETF RFC 3966 [10]). For UEs that are not equipped with an ISIM application, it is possible to derive a temporary IMPU from the IMSI (see 3GPP TS 23.003 [6] for details).
+
+### 5.3.13 E164
+
+#### 5.3.13.1 Definition
+
+This object class represents a telephone number crafted according to ITU-T Recommendation E.164 [8].
+
+### 5.3.14 NAI
+
+#### 5.3.14.1 Definition
+
+This object class represents a Network Access Identifier (as per IETF RFC 4282 [9]).
+
+### 5.3.15 TelURI
+
+#### 5.3.15.1 Definition
+
+This object class represents a telephone URI (as per IETF RFC 3966 [10]).
+
+### 5.3.16 SIPURI
+
+#### 5.3.16.1 Definition
+
+This object class represents a SIP URI (as per IETF RFC 3261 [11]).
+
+### 5.3.17 UdcEndUserGroup
+
+#### 5.3.17.1 Definition
+
+This IOC represents a grouping of several End Users by the operator. The IOC includes information that describes the grouping and criteria for membership.
+
+Examples of UdcEndUserGroup may include the following: Closed User Group, VPN, and market segments.
+
+### 5.3.18 UdcSubscription
+
+#### 5.3.18.1 Definition
+
+This IOC represents common data shared by a group of UdcServiceProfile instances. This IOC exists due to the relationship of a subscriber to the service provider. The end user can be attached to different UDC subscriptions through UDC Service Profiles for different service usage (e.g. for a private and a professional service usage).
+
+**Editor's Note:** The relationship between Identifier and UdcSubscription is left for further study.
+
+## 5.4 Information Relationship Definitions
+
+### 5.4.1. SubscriptionDeterminesSP
+
+#### 5.4.1.1 Definition
+
+This represents the association established between UdcSubscription and UdcServiceProfile due to common data shared by a group of UdcServiceProfile instances.
+
+### 5.4.2 SPMayIncludeID
+
+#### 5.4.2.1 Definition
+
+This represents the association established between `Identifier` and `UdcServiceProfile`.
+
+### 5.4.3 EUHasSP
+
+#### 5.4.3.1 Definition
+
+This represents the association established between `UdcServiceProfile` and `EndUser` due to the fact that any end user who is receiving a service has a service profile associated to it.
+
+### 5.4.4 IdentifierPairsIdentifier
+
+#### 5.4.4.1 Definition
+
+This represents the relation established by instances of `Identifier` with other instances of `Identifier`. For example, one instance of `Identifier` can be an IMPU IOC, and the other an IMPI IOC. The relation of both is generically described by this relationship.
+
+### 5.4.5 EUIdentifiedByID
+
+#### 5.4.5.1 Definition
+
+This represents an instance of `EndUser` that aggregates instances of `Identifier`.
+
+### 5.4.6 GroupMembership
+
+#### 5.4.6.1 Definition
+
+This represents the association established between `EndUser` and `UdcEndUserGroup` determined due to the operator selecting instances of `EndUser` belonging to `UdcEndUserGroup`.
+
+### 5.4.7 TemporarilyPaired
+
+#### 5.4.7.1 Definition
+
+This represents the temporarily association established between `EndDevice` and `Identifiers`, and vice versa. The relation is determined by an identifier (such as an MSISDN or an IMPU) being used from end devices, and from an end device being used by identifiers.
+
+### 5.4.8 CSSPcontainsMSISDN
+
+#### 5.4.8.1 Definition
+
+This represents an aggregation from `UdcCsServiceProfile` to `MSISDN`.
+
+### 5.4.9 GPRSSPcontainsMSISDN
+
+#### 5.4.9.1 Definition
+
+This represents an aggregation from `UdcGprsServiceProfile` to one or more instances of `MSISDN`.
+
+### 5.4.10 EPSSPcontainsMSISDN
+
+#### 5.4.10.1 Definition
+
+This represents an aggregation from `UdcEpsServiceProfile` to `MSISDN`.
+
+### 5.4.11 IMSSPcontainsIMPU
+
+#### 5.4.11.1 Definition
+
+This represents an aggregation from `UdcImServiceProfile` to `IMPU`.
+
+### 5.4.12 MSISDNPairsIMSI
+
+#### 5.4.12.1 Definition
+
+This represents the association established between `MSISDN` and `IMSI`. This might be the case when an `MSISDN` uses `IMSIs` included in a SIM application for authentication purposes.
+
+### 5.4.13 IMPIDerivesFromIMSI
+
+#### 5.4.13.1 Definition
+
+This represents the association established when an `IMPI` is built from the contents of an `IMSI`. This might be the case when a UE that is accessing IMS services is not equipped with a `ISIM` application, but just a `USIM` application in the `UICC`. See details of the derivation process in 3GPP TS 23.003 [6].
+
+### 5.4.14 IMPUPairsOrDerivesFromIMPI
+
+#### 5.4.14.1 Definition
+
+This represents the association established when an `IMPU` is paired with an `IMPI`, where the `IMPI` is used for authentication purposes of that `IMPU`.
+
+### 5.4.15 IMPUDerivesFromIMSI
+
+#### 5.4.15.1 Definition
+
+This represents the association established when an `IMPU` is derived from an `IMSI`. This might be the case when a UE that is accessing IMS services is not equipped with an `ISIM` application, but a `USIM` application in the `UICC`. See details of the derivation process in 3GPP TS 23.003 [6].
+
+### 5.4.16 MSISDNTakesFormatOfE164
+
+#### 5.4.16.1 Definition
+
+This represents the association established when an MSISDN is created from an E.164 number.
+
+### 5.4.17 IMPI Takes Format Of NAI
+
+#### 5.4.17.1 Definition
+
+This represents the association established when the IMPI takes the format of a NAI. See details in 3GPP TS 23.003 [6].
+
+### 5.4.18 IMPU Takes Format Of Tel URI
+
+#### 5.4.18.1 Definition
+
+This represents the association established when an IMPU takes the format of a Tel URI. See details in 3GPP TS 23.003 [6].
+
+### 5.4.19 IMPU Takes Format Of SIP URI
+
+#### 5.4.19.1 Definition
+
+This represents the association established when an IMPU takes the format of a SIP URI. See details in 3GPP TS 23.003 [6].
+
+### 5.4.20 Tel URI Derives From E164
+
+#### 5.4.20.1 Definition
+
+This represents the association established when a Tel URI is derived from an E.164 number.
+
+# --- Annex A (informative): Change history
+
+| Change history |       |           |    |     |                                    |  |       |        |
+|----------------|-------|-----------|----|-----|------------------------------------|--|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                    |  | Old   | New    |
+| 2009-12        | SA#46 | SP-090727 | -- | --  | Presentation to SA for information |  | ---   | 1.0.0  |
+| 2010-03        | SA#47 | SP-100067 | -- | --  | Presentation to SA for Approval    |  | 1.0.0 | 2.0.0  |
+| 2010-03        | --    | --        | -- | --  | Publication of SA approved version |  | 2.0.0 | 9.0.0  |
+| 2011-03        | -     | -         | -  | -   | Update to Rel-10 version (MCC)     |  | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32271/raw.md

@@ -0,0 +1,933 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                |           |
+|--------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                 | 4         |
+| 1 Scope.....                                                                   | 5         |
+| 2 References.....                                                              | 5         |
+| 3 Definitions, symbols and abbreviations.....                                  | 7         |
+| 3.1 Definitions.....                                                           | 7         |
+| 3.2 Symbols.....                                                               | 9         |
+| 3.3 Abbreviations .....                                                        | 9         |
+| 4 Architecture considerations.....                                             | 10        |
+| 4.1 High level LCS architecture.....                                           | 10        |
+| 4.2 LCS offline charging architecture .....                                    | 11        |
+| 4.3 LCS online charging architecture.....                                      | 11        |
+| 5 LCS charging principles and scenarios.....                                   | 12        |
+| 5.1 LCS charging principles.....                                               | 12        |
+| 5.2 LCS offline charging scenarios .....                                       | 12        |
+| 5.2.1 Basic principles .....                                                   | 12        |
+| 5.2.2 Rf message flows.....                                                    | 12        |
+| 5.2.3 CDR Generation .....                                                     | 12        |
+| 5.2.3.1 Mobile originated location request (MO-LR).....                        | 13        |
+| 5.2.3.2 Mobile terminated location request (MT-LR) .....                       | 14        |
+| 5.2.3.3 Network induced location request (NI-LR).....                          | 16        |
+| 5.2.4 Ga record transfer flows .....                                           | 16        |
+| 5.2.5 B <sub>L</sub> CDR file transfer .....                                   | 16        |
+| 5.3 LCS online charging scenarios.....                                         | 17        |
+| 5.3.1 Basic principles .....                                                   | 17        |
+| 5.3.2 Ro message flows.....                                                    | 17        |
+| 5.3.2.1 Mobile originated Location Request (MO-LR).....                        | 17        |
+| 5.3.2.2 Mobile Terminated Location Request (MT-LR) .....                       | 18        |
+| 6 Definition of charging information.....                                      | 19        |
+| 6.1 Data description for LCS offline charging.....                             | 19        |
+| 6.1.1 Rf message contents .....                                                | 19        |
+| 6.1.2 Ga message contents.....                                                 | 19        |
+| 6.1.3 CDR description on the B <sub>L</sub> interface.....                     | 19        |
+| 6.1.3.1 LCS Records for Mobile Originated Location Request (LCS-GMO-CDR) ..... | 20        |
+| 6.1.3.2 LCS Records for mobile terminated location request .....               | 20        |
+| 6.1.3.2.1 LCS Records for Requesting GMLC (LCS-RGMT-CDR) .....                 | 20        |
+| 6.1.3.2.2 LCS Records for Home GMLC (LCS-HGMT-CDR) .....                       | 21        |
+| 6.1.3.2.3 LCS Records for Visited GMLC (LCS-VGMT-CDR).....                     | 21        |
+| 6.1.3.3 LCS Records for Network Initiated Location Request (LCS-GNI-CDR).....  | 22        |
+| 6.2 Data description for LCS online charging.....                              | 22        |
+| 6.2.1 R <sub>o</sub> message contents .....                                    | 22        |
+| 6.2.1.1 LCS Credit-Control-Request Message .....                               | 23        |
+| 6.2.1.2 LCS Credit-Control-Answer Message.....                                 | 24        |
+| 6.3 LCS Charging Specific Parameters.....                                      | 24        |
+| 6.3.1 Definition of LCS charging information .....                             | 24        |
+| 6.3.1.1 LCS charging information assignment for Service Information .....      | 24        |
+| 6.3.1.2 Definition of the LCS Information .....                                | 25        |
+| <b>Annex A (informative): Bibliography .....</b>                               | <b>26</b> |
+| Annex B (informative): Change history.....                                     | 27        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# --- 1 Scope
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging events per domain / subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
+
+The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
+
+The present document specifies the LCS Offline and Online Charging description for the LCS domain, based on the functional stage 2 description of the LCS in 3GPP TS 23.071 [201]. This charging description includes the offline and online charging architecture and scenarios specific to the LCS, as well as the mapping of the common 3GPP architecture specified in TS 32.240 [1] onto the LCS domain. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240 [1];
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298 [51].
+- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54].
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52].
+- The 3GPP Diameter application that is used for LCS domain offline and online charging is specified in TS 32.299 [50].
+
+All terms, definitions and abbreviations, used in the present document, that are common across 3GPP TSs, are defined in 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102].
+
+# --- 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.240: "Telecommunication management; Charging management; Charging architecture and principles".
+
+[2]-[9] Void.
+
+- [10] 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain charging".
+- [11]-[19] Void.
+- [20] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
+- [21]-[29] Void.
+- [30] 3GPP TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging".
+- [31]-[49] Void
+- [50] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging application".
+- [51] 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) encoding rules description".
+- [52] 3GPP TS 32.297: "Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer".
+- [53] 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS) applications and interfaces".
+- [54] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
+- [55]-[99] Void.
+- [100] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [101]-[199] Void.
+- [200] Void.
+- [201] 3GPP TS 23.271: "Location Services (LCS); Functional description; Stage 2".
+- [202] Void.
+- [203] 3GPP TS 25.305: "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN); Stage 2".
+- [204] 3GPP TS 43.059: "Functional stage 2 description of Location Services (LCS) in GERAN".
+- [206]-[299] Void.
+- [301]-[399] Void.
+- [400] Void.
+- [401] RFC 3588: "Diameter Base Protocol".
+- [402] IETF RFC 4006: "Diameter Credit Control Application".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions defined in 3GPP TR 21.905 [100] and 3GPP TS 32.240 [1], and the following apply:
+
+**accounting:** process of apportioning charges between the Home Environment, Serving Network and Subscriber.
+
+**billing:** function whereby CDRs generated by the charging function(s) are transformed into bills requiring payment.
+
+**Billing Domain:** part of the operator network, which is outside the telecommunications network, that receives and processes CDR files from the network charging functions. It includes functions that can provide billing mediation and billing or other (e.g. statistical) end applications. It is only applicable to offline charging (see “Online Charging System” for equivalent functionality in online charging).
+
+**CDR field categories:** the CDR fields are defined in the present document. They are divided into the following categories:
+
+- Mandatory (**M**): field that shall always be present in the CDR.
+- Conditional (**C**): field that shall be present in a CDR if certain conditions are met.
+- Operator Provisionable: Mandatory (**O<sub>m</sub>**): A field that operators have provisioned to always be included in the CDR.
+- Operator Provisionable: Conditional (**O<sub>c</sub>**): A field that operators have provisioned to be included in the CDR if certain conditions are met.
+
+**chargeable event:** activity utilizing telecommunications network resources and related services for:
+
+- user to user communication (e.g. a single call, a data communication session or a short message); or
+- user to network communication (e.g. service profile administration); or
+- inter-network communication (e.g. transferring calls, signalling, or short messages); or
+- mobility (e.g. roaming or inter-system handover); and
+- that the network operator may want to charge for.
+
+As a minimum, a chargeable event characterises the resource / service usage and indicates the identity of the involved end user(s).**charging:** a function within the telecommunications network and the associated OCS/BD components whereby information related to a chargeable event is collected, formatted, transferred and evaluated in order to make it possible to determine usage for which the charged party may be billed.
+
+**Charging Data Record (CDR):** a formatted collection of information about a chargeable event (e.g. time of call set-up, duration of the call, amount of data transferred, etc) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event a separate CDR shall be generated, i.e. more than one CDR may be generated for a single chargeable event, e.g. because of its long duration, or because more than one charged party is to be charged.
+
+**charging event:** a set of charging information forwarded by the CTF towards the CDF (offline charging) or towards the OCS (online charging). Each charging event matches exactly one chargeable event.
+
+**charging function:** entity inside the network domain, subsystem or service that is involved in charging for that domain, subsystem or service.
+
+**circuit switched domain:** domain within GSM / UMTS in which information is transferred in circuit switched mode.
+
+**credit control:** Editor's note: FFS.
+
+**domain:** part of a communication network that provides network resources using a certain bearer technology.
+
+**Fully Qualified Partial CDR (FQPC):** partial CDR that contains a complete set of the fields specified in the present document. This includes all the mandatory and conditional fields as well as those fields that the PLMN operator has provisioned to be included in the CDR. The first Partial CDR shall be a Fully qualified Partial CDR.
+
+**LCS Client:** software and/or hardware entity that interacts with a LCS Server for the purpose of obtaining location information for one or more Mobile Stations
+
+LCS Clients subscribe to LCS in order to obtain location information. LCS Clients may or may not interact with human users. The LCS Client is responsible for formatting and presenting data and managing the user interface (dialogue). The LCS Client may reside in the Mobile Station (UE).
+
+**LCS Server:** software and/or hardware entity offering LCS capabilities. The LCS Server accepts requests, services requests, and sends back responses to the received requests
+
+The LCS server consists of LCS components, which are distributed to one or more PLMN and/or service provider.
+
+**Location Based Service (LBS):** service provided either by teleoperator or a 3<sup>rd</sup> party service provider that utilizes the available location information of the terminal
+
+Location Application offers the User Interface for the service. LBS is either a pull or a push type of service (see Location Dependent Services and Location Independent Services). In ETSI/GSM documentation of SoLSA, LBS is called "Location Related Service". ETSI and/or 3GPP -wide terminology harmonization is expected here.
+
+**location estimate:** geographic location of an UE and/or a valid Mobile Equipment (ME), expressed in latitude and longitude data
+
+The Location Estimate shall be represented in a well-defined universal format. Translation from this universal format to another geographic location system may be supported, although the details are considered outside the scope of the primitive services.
+
+**middle tier (charging) TS:** used for the 3GPP charging TSs that specify the domain / subsystem / service specific, online and offline, charging functionality. These are all the TSs in the numbering range from 3GPP TS 32.250 to 3GPP TS 32.279, e.g. 3GPP TS 32.250 [10] for the CS domain, or 3GPP TS 32.270 [30] for the MMS service. Currently, there is only one "tier 1" TS in 3GPP, which is TS 32.240 [1] that specifies the charging architecture and principles. Finally, there are a number of top tier TSs in the 32.29x numbering range ([50] ff) that specify common charging aspects such as parameter definitions, encoding rules, the common billing domain interface or common charging applications.
+
+**offline charging:** charging mechanism where charging information **does not** affect, in real-time, the service rendered.
+
+**online charging:** charging mechanism where charging information can affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with bearer/session/service control is required.
+
+**Online Charging System:** **Editor's note: FFS.**
+
+**packet switched domain:** domain within GSM / UMTS in which data is transferred in packet switched mode. Corresponds to the term "GPRS".
+
+**partial CDR:** CDR that provides information on part of a subscriber session. A long session may be covered by several partial CDRs. Two formats are considered for Partial CDRs. One that contains all of the specified fields (FQPC); the second has a reduced format (RPC).
+
+**Positioning method (/locating method):** method or technical solution, which is used to get an estimate of the target mobile's geographical location
+
+**EXAMPLE:** Positioning methods based on radio cell coverage, GPS or Assisted GPS methods, which are based on the Time-Of-Arrival (TOA) algorithm, and OTDOA or E-OTD methods, which are based on the Time-Difference-Of-Arrival (TDOA) algorithm. The positioning methods are further described in UTRAN Stage 2, 3GPP TS 25.305 [203] and GERAN Stage 2, 3GPP TS 43.059 [204].
+
+**target UE:** UE being positioned
+
+**user:** an entity, not part of the 3GPP System, that uses network resources by means of a subscription. The user may or may not be identical to the subscriber holding that subscription.
+
+**User Equipment (UE):** a device allowing a user access to network services. For the purpose of 3GPP specifications the interface between the UE and the network is the radio interface. A User Equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently defined domains are the USIM and ME Domains. The ME Domain can further be subdivided into several components showing the connectivity between multiple
+
+functional groups. These groups can be implemented in one or more hardware devices. An example of such a connectivity is the TE – MT interface. Further, an occurrence of a User Equipment is an MS for GSM as defined in GSM TS 04.02.UE in the present document may also refer to a Mobile Equipment or User Equipment used for emergency calls, that do not have valid SIM or USIM.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|    |                                                                        |
+|----|------------------------------------------------------------------------|
+| B1 | Reference point for the CDR file transfer from the GMLC CGF to the BD, |
+| Lr | Interface between Gateway MLCs                                         |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [100], 3GPP TS 23.271 [20] and 3GPP TS 32.240 [1], and the following apply:
+
+|        |                                                                                   |
+|--------|-----------------------------------------------------------------------------------|
+| 3G     | 3 <sup>rd</sup> Generation                                                        |
+| 3GPP   | 3 <sup>rd</sup> Generation Partnership Project                                    |
+| AVP    | Attribute Value Pair                                                              |
+| BD     | Billing Domain                                                                    |
+| CCA    | Credit Control Answer                                                             |
+| CCR    | Credit Control Request                                                            |
+| CDF    | Charging Data Function                                                            |
+| CDR    | Charging Data Records                                                             |
+| CGF    | Charging Gateway Function                                                         |
+| CS     | Circuit-Switched                                                                  |
+| CTF    | Charging Trigger Function                                                         |
+| DCCA   | Diameter Credit Control Application                                               |
+| ECUR   | Event Charging with Unit Reservation                                              |
+| FTAM   | File Transfer, Access and Management                                              |
+| GERAN  | GSM EDGE Radio Access Network                                                     |
+| GGSN   | Gateway GPRS Support Node                                                         |
+| GMLC   | Gateway MLC                                                                       |
+| GPRS   | General Packet Radio Service                                                      |
+| GSM    | Global System for Mobile communication                                            |
+| gsmSCF | GSM Service Control Function                                                      |
+| H-GMLC | Home GMLC                                                                         |
+| HLR    | Home Location Register                                                            |
+| HPLMN  | Home PLMN                                                                         |
+| HSS    | Home Subscriber Server                                                            |
+| IEC    | Immediate Event Charging                                                          |
+| IETF   | Internet Engineering Task Force                                                   |
+| IMS    | IP Multimedia Subsystem                                                           |
+| IMSI   | International Mobile Subscriber Identity                                          |
+| IP     | Internet Protocol                                                                 |
+| ITU-T  | International Telecommunication Union - Telecommunications standardization sector |
+| LCS    | LoCation Service                                                                  |
+| MAP    | Mobile Application Part                                                           |
+| ME     | Mobile Equipment                                                                  |
+| MO     | Mobile Originated                                                                 |
+| MO-LR  | Mobile Originated - Location Request                                              |
+| MS     | Mobile Station                                                                    |
+| MSISDN | Mobile Station Integrated Services Data Network                                   |
+| MT     | Mobile Terminated                                                                 |
+| MT-LR  | Mobile Terminated - Location Request                                              |
+| NI-LR  | Network Induced - Location Request                                                |
+| OCS    | Online Charging System                                                            |
+| PLMN   | Public Land Mobile Network                                                        |
+| PMD    | Pseudonym Mediation Device functionality                                          |
+| PPR    | Privacy Profile Register                                                          |
+| PS     | Packet Switched                                                                   |
+
+|        |                                            |
+|--------|--------------------------------------------|
+| RAN    | Radio Access Network                       |
+| R-GMLC | Requesting - GMLC                          |
+| RPC    | Reduced Partial CDR                        |
+| SGSN   | Serving GPRS Support Node                  |
+| TR     | Technical Report                           |
+| TS     | Technical Specification                    |
+| UE     | User Equipment                             |
+| UMTS   | Universal Mobile Telecommunications System |
+| USIM   | User Service Identity Module               |
+| UTRAN  | Universal Terrestrial Radio Access Network |
+| V-GMLC | Visited GMLC                               |
+| VPLMN  | Visited PLMN                               |
+
+# 4 Architecture considerations
+
+## 4.1 High level LCS architecture
+
+Figure 4.1 depicts the logical LCS architecture, as described in 3GPP TS 23.271 [201].
+
+![Figure 4.1: LCS logical architecture with inter-GMLC [Lr] interface. The diagram shows the logical architecture of the Location Service (LCS) within a Visited Packet Core Network (VPMLN). On the left, User Equipment (UE) connects to GERAN (via Um) and UTRAN (via Uu). GERAN connects to a 2G-MSC (via A) and a 2G-SGSN (via Gb). UTRAN connects to a 3G-SGSN (via Iu) and an MSC server (via Iu). The 2G-MSC and 2G-SGSN connect to a Visited GMLC (V-GMLC) via Lg interfaces. The 3G-SGSN and MSC server also connect to the V-GMLC via Lg interfaces. The V-GMLC connects to a Home GMLC (H-GMLC) via an Lr interface. The H-GMLC connects to a Requesting GMLC (R-GMLC) via an Lr interface. The R-GMLC connects to an External LCS Client via an Le interface. The R-GMLC also connects to a PMD (via Lid) and an HSS/HLR (via Lh). The H-GMLC connects to a PMD (via Lid) and an HSS/HLR (via Lh). The V-GMLC connects to a PMD (via Lid) and a PPR (via Lpp). The H-GMLC connects to a gsmSCF (via Lc) and a PMD (via Lid). The gsmSCF connects to the External LCS Client via an OSA-LCS interface. The VPMLN is indicated by a double-headed arrow at the top.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg)
+
+Figure 4.1: LCS logical architecture with inter-GMLC [Lr] interface. The diagram shows the logical architecture of the Location Service (LCS) within a Visited Packet Core Network (VPMLN). On the left, User Equipment (UE) connects to GERAN (via Um) and UTRAN (via Uu). GERAN connects to a 2G-MSC (via A) and a 2G-SGSN (via Gb). UTRAN connects to a 3G-SGSN (via Iu) and an MSC server (via Iu). The 2G-MSC and 2G-SGSN connect to a Visited GMLC (V-GMLC) via Lg interfaces. The 3G-SGSN and MSC server also connect to the V-GMLC via Lg interfaces. The V-GMLC connects to a Home GMLC (H-GMLC) via an Lr interface. The H-GMLC connects to a Requesting GMLC (R-GMLC) via an Lr interface. The R-GMLC connects to an External LCS Client via an Le interface. The R-GMLC also connects to a PMD (via Lid) and an HSS/HLR (via Lh). The H-GMLC connects to a PMD (via Lid) and an HSS/HLR (via Lh). The V-GMLC connects to a PMD (via Lid) and a PPR (via Lpp). The H-GMLC connects to a gsmSCF (via Lc) and a PMD (via Lid). The gsmSCF connects to the External LCS Client via an OSA-LCS interface. The VPMLN is indicated by a double-headed arrow at the top.
+
+Figure 4.1: LCS logical architecture with inter-GMLC [Lr] interface
+
+As can be seen in figure 4.1, the following LCS elements are relevant for charging:
+
+- V-GMLC,
+- H-GMLC
+- R-GMLC.
+
+**Editor's note:** Add a statement stating that the SGSN and the MSC have also a role in the LCS Charging and that the associated LCS Charging functionality is described in TS 32.250 and TS 32.251
+
+## 4.2 LCS offline charging architecture
+
+As described in TS 32.240 [1], the CTF (an integrated component in each charging relevant NE) generates charging events and forwards them to the CDF. The CDF, in turn, generates CDRs which are then transferred to the CGF. Finally, the CGF creates CDR files and forwards them to the Billing Domain.
+
+In LCS, all charging functions (CTF, CDF and CGF) reside within the LCS R/S. I.e. the GMLC is connected directly to the Billing Domain via the B1 interface. B1 is the LCS specific variant of the common Bx interface. This architecture implies that there exists no separate CDF and CGF for LCS, i.e. no corresponding open interfaces between any such functions, within the 3GPP standards.
+
+Figure 4.2 depicts the mapping of the 3GPP common charging architecture, as laid down in 3GPP TS 32.240 [1], onto the LCS.
+
+**Editor's note: A clarification for the LCS offline charging reference point is in discussion**
+
+![Diagram of LCS offline charging architecture showing GMLC connected to BD via B1 interface.](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+The diagram illustrates the LCS offline charging architecture. On the left, a green rectangular box labeled 'GMLC' contains a smaller grey box labeled 'CDF/CGF'. A blue arrow points from the 'CDF/CGF' box to a yellow rectangular box on the right labeled 'BD'. Above the arrow, a white box labeled 'B1' indicates the interface between the GMLC and the BD.
+
+Diagram of LCS offline charging architecture showing GMLC connected to BD via B1 interface.
+
+**Figure 4.2: LCS offline charging architecture**
+
+In addition to the standard approach depicted in figure 4.2, vendors may choose to implement separate CDF and CGF for LCS. In that case, the interfaces between these functions should comply with the definition of the Rf and Ga interfaces (3GPP TS 32.299 [50] and 3GPP TS 32.295 [54], respectively) as much as possible.
+
+## 4.3 LCS online charging architecture
+
+LCS online charging is based on GMLC functionality that is further specified in the present document. For online charging, the GMLC utilises the Ro interface and application towards the OCS as specified in TS 32.299 [50]. The Ro reference point covers all online charging functionality required for LCS.
+
+The LCS online charging architecture is depicted in figure 4.3.
+
+![Diagram of LCS online charging architecture showing GMLC connected to Online Charging System via Ro interface.](536951b2bbd94325ae266d8d1363df8f_img.jpg)
+
+The diagram illustrates the LCS online charging architecture. On the left, a white rectangular box labeled 'GMLC' is connected by a horizontal line to a large blue rectangular box on the right labeled 'Online Charging System'. The connection line is labeled 'Ro'.
+
+Diagram of LCS online charging architecture showing GMLC connected to Online Charging System via Ro interface.
+
+**Figure 4.3: LCS online charging architecture**
+
+Details on the interfaces and functions can be found in TS 32.240 [1] for the general architecture components, TS 32.296 [53] for the OCS, and TS 32.299 [50] for the Ro application.
+
+# 5 LCS charging principles and scenarios
+
+**Editor's note:** Include a brief introduction statement saying that this clause contains the CDR and charging event types and their trigger conditions.
+
+## 5.1 LCS charging principles
+
+Charging information in the Service domain for LCS is collected for inter-operator charging purpose by the GMLC. The basic principle is that a network requesting location information may be charged by the network that provides the location information.
+
+The GMLC shall collect the following charging information:
+
+- Identity of the mobile subscriber to be located and of the entity requesting the location;
+- Identity of the GMLC or PLMN serving the LCS Client;
+- QoS Requested/Delivered: the charging information shall describe the quality of the location requested and delivered to the LCS client;
+- Request Timestamp: the charging information shall record the date and time the location procedure was requested by the LCS client;
+- Location services requested: the charging information shall describe the service types for which the LCS client is allowed to locate the particular UE;
+- Usage of continuous/periodic tracking;
+- Charging for Location Based Services (LBS): the charging information shall describe the service specific information in addition to the above location resource information.
+
+The information listed above is captured for use cases in relation to:
+
+- Mobile Originated Location Request;
+- Mobile Terminated Location Request;
+- Network Induced Location Request;
+
+Refer to TS 23.271 [201] for further details on the above LCS transactions.
+
+## 5.2 LCS offline charging scenarios
+
+### 5.2.1 Basic principles
+
+**Editor's note:** TBD.
+
+### 5.2.2 Rf message flows
+
+Not applicable, as the separation of the CTF and CDF is not in the scope of the LCS charging standards. Refer to clause 4.2 for further information.
+
+Note: Vendors may nevertheless implement a separate CTF and CDF for LCS charging. In this case, it is recommended that the approach chosen conforms to the principles and protocol applications specified in TS 32.299 [50].
+
+### 5.2.3 CDR Generation
+
+**Editor's note:** This section shall also include the triggers of the CDR generation, the CDR types
+
+The flows described in the present document specify the charging communications between the GMLC and the billing function for different charging scenarios. The LCS related messages associated with these charging scenarios are shown primarily for general information and to illustrate the charging triggers.
+
+For the purpose of these examples, the following assumptions have been made:
+
+- that the RAN location procedures are not depicted;
+- that the CS and PS location procedures are not distinguished;
+- that the LCS client has no privacy override capability;
+- that the LCS charging procedures in the CS and the PS domains are not depicted
+
+#### 5.2.3.1 Mobile originated location request (MO-LR)
+
+Mobile Originated location request allows the UE to obtain its own geographical location or have its location information transferred to another LCS client. In this procedure, the R-GMLC, H-GMLC and V-GMLC are the same as no privacy checking is performed.
+
+Figure 5.2.3.1 illustrates a Mobile Originated Location Request that allows a UE to request its own location.
+
+![Sequence diagram for Mobile Originated Location Request (MO-LR) within a Home Network. The diagram shows four lifelines: LCS Client, GMLC, MSC/SGSN, and UE. The sequence of messages is: 1. Location Services Invoke from UE to MSC/SGSN; 2. MAP Subscriber Location Report from MSC/SGSN to GMLC; 3. Location Information from GMLC to LCS Client; 4. Location Information ack from LCS Client to GMLC; 5. MAP Subscriber Location Report ack from GMLC to MSC/SGSN (marked with a circled '1'); 6. LCS MO-LR Return Result from MSC/SGSN to UE.](4636adff5682a064f0ae5f13a1d464a6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant MSC/SGSN
+    participant GMLC
+    participant LCS_Client as LCS Client
+    Note over all: Home Network
+    UE->>MSC/SGSN: 1. Location Services Invoke
+    MSC/SGSN->>GMLC: 2. MAP Subscriber Location Report
+    GMLC->>LCS_Client: 3. Location Information
+    LCS_Client->>GMLC: 4. Location Information ack
+    GMLC->>MSC/SGSN: 5. MAP Subscriber Location Report ack (1)
+    MSC/SGSN->>UE: 6. LCS MO-LR Return Result
+  
+```
+
+Sequence diagram for Mobile Originated Location Request (MO-LR) within a Home Network. The diagram shows four lifelines: LCS Client, GMLC, MSC/SGSN, and UE. The sequence of messages is: 1. Location Services Invoke from UE to MSC/SGSN; 2. MAP Subscriber Location Report from MSC/SGSN to GMLC; 3. Location Information from GMLC to LCS Client; 4. Location Information ack from LCS Client to GMLC; 5. MAP Subscriber Location Report ack from GMLC to MSC/SGSN (marked with a circled '1'); 6. LCS MO-LR Return Result from MSC/SGSN to UE.
+
+**Figure 5.2.3.1: Record trigger overview for MO-LR**
+
+1. The MSC (or SGSN) receives a Location Service Invoke from the UE
+2. The MSC (or SGSN) forwards the Location result to the GMLC by sending a MAP Subscriber Location Report
+3. The GMLC transfers the location information to the LCS client.
+4. The LCS Client sends to the GMLC the Location Information ack message signalling the result.
+5. The GMLC acknowledges the MAP Subscriber Location Report and the associated MO-LR CDR is processed as specified in TS 32.297 [52].
+6. The MSC (or SGSN) returns a Service Response message to the UE carrying any location estimate requested by the UE
+
+The record trigger associated to the MO-LR is called 'LCS GMLC Mobile Originated' (LCS-GMO)
+
+#### 5.2.3.2 Mobile terminated location request (MT-LR)
+
+Mobile terminated location request allows an external LCS client to ask for the location of a mobile subscriber (target UE).
+
+Figure 5.2.3.2 illustrates a Mobile Terminated Location Request scenario:
+
+![Sequence diagram for Mobile Terminated Location Request (MT-LR) showing interactions between Requesting Network (LCS Client, GMLC), Home Network (GMLC, HLR/HSS), and Visited Network (GMLC, MSC/SGSN, UE).](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+```
+
+sequenceDiagram
+    participant LCS_Client as LCS Client
+    participant GMLC_R as GMLC (Requesting)
+    participant GMLC_H as GMLC (Home)
+    participant HLR_HSS as HLR/HSS
+    participant GMLC_V as GMLC (Visited)
+    participant MSC_SGSN as MSC/SGSN
+    participant UE as UE
+
+    Note left of GMLC_R: Requesting Network
+    Note left of GMLC_H: Home Network
+    Note left of GMLC_V: Visited Network
+
+    LCS_Client->>GMLC_R: 1. Location Service Request
+    GMLC_R->>HLR_HSS: 2. Send Routing Info for LCS
+    HLR_HSS-->>GMLC_R: 3. Send Routing Info for LCS ack
+    GMLC_R->>GMLC_H: 4. LCS Service Request
+    Note right of GMLC_H: Privacy Check
+    GMLC_H->>HLR_HSS: 5. Send Routing Info for LCS
+    HLR_HSS-->>GMLC_H: 6. Send Routing Info for LCS ack
+    GMLC_H->>GMLC_V: 7. LCS Service Request
+    GMLC_V->>MSC_SGSN: 8. Provide Subscriber Location
+    Note right of MSC_SGSN: MT-LR procedures for CS and PS Domain
+    MSC_SGSN-->>GMLC_V: 9. Provide Subscriber Location ack
+    Note right of GMLC_V: LCS-VGMT-CDR Processing
+    GMLC_V->>GMLC_H: 10. LCS Service Response
+    Note right of GMLC_H: Privacy Check
+    Note right of GMLC_H: LCS-HGMT-CDR Processing
+    GMLC_H->>GMLC_R: 11. LCS Service Response
+    Note right of GMLC_R: LCS-RGMT-CDR Processing
+    GMLC_R->>LCS_Client: 12. LCS Service Response
+  
+```
+
+Sequence diagram for Mobile Terminated Location Request (MT-LR) showing interactions between Requesting Network (LCS Client, GMLC), Home Network (GMLC, HLR/HSS), and Visited Network (GMLC, MSC/SGSN, UE).
+
+Figure 5.2.3.2: Record trigger overview for MT-LR
+
+1. The external LCS client requests the location of a target UE from the R-GMLC
+2. The R-GMLC requests the H-GMLC address by sending a MAP Send Routing Info for LCS message to the home HLR/HSS of the target UE to be located
+
+3. The HLR/HSS returns a MAP Send Routing Info for LCS ack message that contains the H-GMLC address
+4. The R-GMLC forwards the Location Service Request to the H-GMLC
+5. After performing privacy check, the H-GMLC requests the V-GMLC address by sending a MAP Send Routing Info for LCS message to the home HLR/HSS
+6. The HLR/HSS returns a MAP Send Routing Info for LCS ack message that contains the V-GMLC address
+7. The H-GMLC forwards the Location Service Request to the V-GMLC
+8. The V-GMLC forwards the Location request to the MSC or SGSN by sending a MAP Provider Subscriber Location Report
+9. After either a CS-MT-LR or PS-MT-LR was processed, the MSC or SGSN sends the acknowledgement of the MAP Provider Subscriber Location Report  
+The associated LCS VGMT CDR is processed as specified in TS 32.297 [52]
+10. The V-GMLC sends the location service response to the H-GMLC. After the H-GMLC has performed privacy check, the associated LCS HGMT CDR is processed as specified in TS 32.297 [52]
+11. The H-GMLC sends the location service response to the R-GMLC and the associated LCS RGMT CDR is processed as specified in TS 32.297 [52].
+12. The R-GMLC returns a Service Response message to the LCS client carrying any location estimate requested by the LCS client
+
+#### 5.2.3.3 Network induced location request (NI-LR)
+
+Network induced location request allows positioning for an emergency service call.
+
+Figure 5.2.3.3 illustrates a Network Induced Location Request scenario:
+
+![Sequence diagram for Network Induced Location Request (NI-LR) scenario. The diagram shows four lifelines: LCS Client, GMLC, MSC/SGSN, and UE, all within a 'Home Network' frame. The sequence of messages is: 1. LCS Emergency Call Origination (UE to LCS Client); 2. Messages for individual positioning methods (UE to MSC/SGSN); 3. MAP Subscriber Location Report (MSC/SGSN to GMLC); 4. MAP Subscriber Location Report ack (GMLC to MSC/SGSN); 5. Location Information (GMLC to LCS Client), which also triggers 'LCS GNI CDR Processing' (GMLC to itself); 6. LCS Emergency Call Release (LCS Client to UE).](41a438d7e4adc17c3a4005e7c9500091_img.jpg)
+
+Sequence diagram for Network Induced Location Request (NI-LR) scenario. The diagram shows four lifelines: LCS Client, GMLC, MSC/SGSN, and UE, all within a 'Home Network' frame. The sequence of messages is: 1. LCS Emergency Call Origination (UE to LCS Client); 2. Messages for individual positioning methods (UE to MSC/SGSN); 3. MAP Subscriber Location Report (MSC/SGSN to GMLC); 4. MAP Subscriber Location Report ack (GMLC to MSC/SGSN); 5. Location Information (GMLC to LCS Client), which also triggers 'LCS GNI CDR Processing' (GMLC to itself); 6. LCS Emergency Call Release (LCS Client to UE).
+
+**Figure 5.2.3.3: Record trigger overview for NI-LR**
+
+1. An emergency call procedure is initiated between the UE and the LCS client
+2. Positioning procedures are instigated
+3. The MSC (or SGSN) forwards the Location request to the GMLC by sending a MAP Subscriber Location Report
+4. The GMLC acknowledges the MAP Subscriber Location Report
+5. The GMLC transfers the location information to the LCS client and the associated LCS-GNI-CDR is processed as specified in TS 32.297 [52].
+6. At some later time, the emergency services call is released.
+
+### 5.2.4 Ga record transfer flows
+
+Not applicable, as the separation of the CDF and CGF is not in the scope of the LCS charging standards. Refer to clause 4.3 for further information.
+
+**NOTE:** Vendors may nevertheless implement a separate CDF and CGF for LCS charging. In this case, it is recommended that the approach chosen conforms to the principles and protocol applications specified in TS 32.295 [54].
+
+### 5.2.5 B<sub>L</sub> CDR file transfer
+
+The integrated CGF of the GMLC transfers the CDR files to the BD as described in TS 32.297 [52]. In LCS, both fully qualified partial CDRs (FQPC) and reduced partial CDRs (RPC), as specified in TS 32.240 [1] may be supported on the B<sub>L</sub> interface. In line with TS 32.240 [13], the support of FQPCs is mandatory, the support of RPCs is optional. For further details on the B<sub>L</sub> protocol application refer to TS 32.297 [52].
+
+## 5.3 LCS online charging scenarios
+
+LCS online charging uses the credit control application as specified in TS 32.299 [50].
+
+### 5.3.1 Basic principles
+
+*Editors Note: This section should be updated and aligned with 32.299. Some of this text will go into 32.299 and removed from this TS.*
+
+Two cases for online charging are distinguished:
+
+- Immediate Event Charging (IEC); and
+- Event Charging with Unit Reservation (ECUR).
+
+In the case of Immediate Event Charging (IEC), granting units to the GMLC is performed in a single operation that also includes the deduction of the corresponding monetary units from the subscriber's account. The charging process is controlled by the corresponding credit control request which is sent for a given credit control event.
+
+In contrast, Event Charging with Unit Reservation (ECUR) also includes the process of requesting, reserving units and releasing and returning unused units. The deduction of the corresponding monetary units then occurs upon conclusion of the ECUR transaction. In this case, the credit control request is used to control the credit control session.
+
+The GMLC may apply either IEC, where CCR Event messages are generated, or ECUR, using CCR Initial, Termination and Update. The decision whether to apply IEC or ECUR is based on the service and/or operator's policy.
+
+NOTE: To the extent possible alignment with IETF RFC 4006 [402] is planned.
+
+*Editor's note: Modify the text above with LCS specific description on what the GMLC requests from the ECF*
+
+### 5.3.2 Ro message flows
+
+The message flows described in the present document specify the charging communications between the GMLC and the Online Charging System (OCS) for different charging scenarios. The LCS messages associated with these charging scenarios are shown primarily for general information and to illustrate the charging triggers that are also used for LCS offline charging.
+
+#### 5.3.2.1 Mobile originated Location Request (MO-LR)
+
+Figure 5.3.2.1 shows the credit control transactions that are required between GMLC and OCS during the mobile originated location request. In this scenario the UE is the party to charge for the location request.
+
+![Sequence diagram for LCS Online charging scenario for MO-LR. The diagram shows three main entities: MSC/SGSN, GMLC, and OCS. The MSC/SGSN sends a MAP Subscriber Location Report to the GMLC. The GMLC performs 'Location Request and UE validation'. It then enters a 'Credit Control Application' block, sending a CCR (Credit Control Request) to the OCS. The OCS performs 'LCS account and tariff validation' and returns a CCA (Credit Control Answer) to the GMLC. The GMLC then performs 'LCS validation and control' and finally sends a MAP Subscriber Location Report Ack back to the MSC/SGSN. The connections between MSC/SGSN and GMLC are labeled 'MAP', and between GMLC and OCS are labeled 'Ro'.](7ec4ba01d21d0840c67e18d51aeb1415_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MSC/SGSN
+    participant GMLC
+    participant OCS
+    Note over MSC/SGSN, GMLC: MAP
+    Note over GMLC, OCS: Ro
+    MSC/SGSN->>GMLC: MAP Subscriber Location Report
+    Note over GMLC: Location Request and UE validation
+    rect rgb(255, 255, 255)
+    Note over GMLC, OCS: Credit Control Application
+    GMLC->>OCS: CCR
+    Note over OCS: LCS account and tariff validation
+    OCS-->>GMLC: CCA
+    end
+    Note over GMLC: LCS validation and control
+    GMLC-->>MSC/SGSN: MAP Subscriber Location Report Ack
+
+```
+
+Sequence diagram for LCS Online charging scenario for MO-LR. The diagram shows three main entities: MSC/SGSN, GMLC, and OCS. The MSC/SGSN sends a MAP Subscriber Location Report to the GMLC. The GMLC performs 'Location Request and UE validation'. It then enters a 'Credit Control Application' block, sending a CCR (Credit Control Request) to the OCS. The OCS performs 'LCS account and tariff validation' and returns a CCA (Credit Control Answer) to the GMLC. The GMLC then performs 'LCS validation and control' and finally sends a MAP Subscriber Location Report Ack back to the MSC/SGSN. The connections between MSC/SGSN and GMLC are labeled 'MAP', and between GMLC and OCS are labeled 'Ro'.
+
+**Figure 5.3.2.1: LCS Online charging scenario for MO-LR**
+
+#### 5.3.2.2 Mobile Terminated Location Request (MT-LR)
+
+Figure 5.3.2.2 shows the credit control transactions that are required between GMLC and OCS during the mobile terminated location request.
+
+![Sequence diagram showing the interaction between LCS Client, GMLC, and OCS for MT-LR. The LCS Client sends a Location Service Request to the GMLC. The GMLC performs 'Location request and LCS Client validation'. Then, a 'Credit Control Application' block shows the GMLC sending a CCR to the OCS, which performs 'LCS account and tariff validation' and returns a CCA. Finally, the GMLC performs 'LCS validation and account reservation' and sends an LCS Service Response back to the LCS Client. Dashed lines labeled 'Le' and 'Ro' connect the LCS Client to GMLC and GMLC to OCS respectively.](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+```
+sequenceDiagram
+    participant LCS Client
+    participant GMLC
+    participant OCS
+    Note right of GMLC: Location request and LCS Client validation
+    Note right of OCS: LCS account and tariff validation
+    Note right of GMLC: LCS validation and account reservation
+
+    LCS Client->>GMLC: Location Service Request
+    GMLC->>OCS: CCR
+    OCS-->>GMLC: CCA
+    GMLC->>LCS Client: LCS Service Response
+```
+
+Sequence diagram showing the interaction between LCS Client, GMLC, and OCS for MT-LR. The LCS Client sends a Location Service Request to the GMLC. The GMLC performs 'Location request and LCS Client validation'. Then, a 'Credit Control Application' block shows the GMLC sending a CCR to the OCS, which performs 'LCS account and tariff validation' and returns a CCA. Finally, the GMLC performs 'LCS validation and account reservation' and sends an LCS Service Response back to the LCS Client. Dashed lines labeled 'Le' and 'Ro' connect the LCS Client to GMLC and GMLC to OCS respectively.
+
+Figure 5.3.2.2: LCS Online charging scenario for MT-LR
+
+# 6 Definition of charging information
+
+This clause provides Stage 3 specifications of the CDR type and content in line with the CDR type definitions provided in clause 5.2.3 and Diameter Credit Control messages for LCS
+
+## 6.1 Data description for LCS offline charging
+
+Dedicated types of CDRs can be generated for LCS by the GMLC. The content of each CDR type is defined in one of the tables that are part of this clause. For each CDR type the parameter definition includes the parameter name, description and category.
+
+Equipment vendors shall be able to provide all of the parameters listed in the CDR content table in order to claim compliance with the present document. However, since CDR processing and transport consume network resources, operators may opt to eliminate some of the parameters that are not essential for their operation. This operator provisionable reduction is specified by the parameter category.
+
+A parameter category can have one of two primary values:
+
+- M** This parameter is **M**andatory and shall always be present in the Diameter messages/CDR.
+- C** This parameter shall be present in the Diameter message/CDR only when certain Conditions are met. These Conditions are specified as part of the parameter definition.
+
+Some of these parameters are designated as Operator provisionable (**O**). Using TMN management functions or specific tools provided by an equipment vendor, operators may choose to include or omit the parameter from the charging event/CDR. Once omitted, this parameter is not generated in a CDR of the particular type.. To avoid any potential ambiguity, the CTF/CDF/CGF MUST be able to provide all these parameters. Only an operator can choose whether or not these parameters should be generated in its system, i.e. included in the charging Diameter message/CDR.
+
+Those parameters that the operator configures to be present or absent are further qualified with the "Operator provisionable" indicator as follows:
+
+- O<sub>m</sub>** This is a parameter that, if provisioned by the operator to be present, shall always be included in the Diameter messages/CDRs. In other words, an **O<sub>m</sub>** parameter that is provisioned to be present is a mandatory parameter.
+- O<sub>c</sub>** This is a parameter that, if provisioned by the operator to be present, shall be included in the Diameter messages/CDRs when the specified conditions are met. In other words, an **O<sub>c</sub>** parameter that is configured to be present is a conditional parameter.
+
+The GMLC's CGF shall be able to provide the CDRs at the Billing System interface in the format and encoding described in the present document. In LCS, both fully qualified partial CDRs (FQPC) and reduced partial CDRs (RPC), as specified in TS 32.240 [1] may be supported on the BI interface. In line with TS 32.240 [13], the support of FQPCs is mandatory, the support of RPCs is optional.
+
+### 6.1.1 Rf message contents
+
+Not applicable. Refer to subclause 5.2.2 for further information.
+
+### 6.1.2 Ga message contents
+
+Not applicable. Refer to subclause 5.2.3 for further information.
+
+### 6.1.3 CDR description on the B<sub>L</sub> interface
+
+This clause provides Stage 3 specifications of the CDR type and content for the 3GPP LCS domain. For each of the CDR types, a parameter table, which gives a short description of the parameters, is provided. The detailed specification of the CDR parameters and their encoding is contained in TS 32.298 [51], while TS 32.297 [52] specify the details of the CDR file transfer to the BD.
+
+#### 6.1.3.1 LCS Records for Mobile Originated Location Request (LCS-GMO-CDR)
+
+If enabled, a LCS GMLC Mobile originated Charging Data Record (LCS-GMO-CDR) shall be produced for each mobile originated location request performed via the GMLC. The fields in the record are specified in table 6.1.3.1, which provides a brief description of each field.
+
+**Table 6.1.3.1: LCS GMLC Mobile Originated CDR (LCS-GMO-CDR)**
+
+| Field                        | Category       | Description                                                                                                      |
+|------------------------------|----------------|------------------------------------------------------------------------------------------------------------------|
+| Record Type                  | M              | LCS GMLC Mobile Originated Record                                                                                |
+| Recording Entity             | M              | The E.164 address of this GMLC                                                                                   |
+| LCS Client Type              | C              | The type of the LCS client that invoked the LR, if available.                                                    |
+| LCS Client Identity          | C              | Further identification of the LCS client, if available.                                                          |
+| Served IMSI                  | M              | The IMSI of the subscriber that requests the location.                                                           |
+| Served MSISDN                | O <sub>m</sub> | The primary MSISDN of the subscriber that requests the location.                                                 |
+| Serving Entity               | C              | The E.164 address of the serving MSC (in case of CS-MO-LR) or SGSN (in case of PS-MO-LR)                         |
+| Location Estimate            | O <sub>c</sub> | The location estimate for the subscriber if contained in geographic position and the LR was successful.          |
+| Positioning Data             | C              | The positioning method used or attempted, if available.                                                          |
+| User Error                   | C              | The Location Service type of error if any failure happened                                                       |
+| Provider Error               | O <sub>c</sub> | The protocol related type of error if any failure happened                                                       |
+| Record Time Stamp            | O <sub>m</sub> | Time of generation of the CDR                                                                                    |
+| Local Record Sequence Number | O <sub>m</sub> | Consecutive record number created by this node. The number is allocated sequentially including all CDR types.    |
+| Record extensions            | O <sub>c</sub> | A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
+
+#### 6.1.3.2 LCS Records for mobile terminated location request
+
+##### 6.1.3.2.1 LCS Records for Requesting GMLC (LCS-RGMT-CDR)
+
+If enabled, a LCS Requesting GMLC Mobile terminated Charging Data Record (LCS-RGMT-CDR) shall be produced for each mobile a terminated location request is performed via the R-GMLC. The fields in the record are specified in table 6.1.3.2.1, which provides a brief description of each field.
+
+**Table 6.1.3.2.1: LCS Requesting GMLC Mobile Terminated CDR (LCS-RGMT-CDR)**
+
+| Field                        | Category       | Description                                                                                                      |
+|------------------------------|----------------|------------------------------------------------------------------------------------------------------------------|
+| Record Type                  | M              | LCS Requesting GMLC Mobile Terminated Record                                                                     |
+| Recording Entity             | M              | The E.164 address of this GMLC                                                                                   |
+| Home GMLC Identity           | C              | If available, the IP address of the HGMLC involved in the location request                                       |
+| LCS Client Type              | C              | The type of the LCS client that invoked the LR, if available.                                                    |
+| LCS Client Identity          | C              | Further identification of the LCS client, if available.                                                          |
+| Target IMSI                  | M              | The IMSI of the targeted LCS subscriber                                                                          |
+| Target MSISDN                | O <sub>m</sub> | The primary MSISDN of the targeted subscriber.                                                                   |
+| Location Type                | M              | The type of location information being requested.                                                                |
+| LCS Priority                 | C              | Priority of the LR, if available                                                                                 |
+| Result Code                  | O <sub>m</sub> | The result code that indicate the result of the request or individual positioning                                |
+| Record Time Stamp            | O <sub>m</sub> | Time of generation of the CDR                                                                                    |
+| Local Record Sequence Number | O <sub>m</sub> | Consecutive record number created by this node. The number is allocated sequentially including all CDR types.    |
+| Record extensions            | O <sub>c</sub> | A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
+
+##### 6.1.3.2.2 LCS Records for Home GMLC (LCS-HGMT-CDR)
+
+If enabled, a LCS Home GMLC Mobile terminated Charging Data Record (LCS-HGMT-CDR) shall be produced for each mobile a terminated location request is performed via the H-GMLC. The fields in the record are specified in table 6.1.3.2.2, which provides a brief description of each field.
+
+**Table 6.1.3.2.2: LCS Home GMLC Mobile Terminated CDR (LCS-HGMT-CDR)**
+
+| Field                        | Category       | Description                                                                                                      |
+|------------------------------|----------------|------------------------------------------------------------------------------------------------------------------|
+| Record Type                  | M              | LCS Home GMLC Mobile Terminated Record                                                                           |
+| Recording Entity             | M              | The E.164 address of this GMLC                                                                                   |
+| Requesting GMLC Identity     | C              | If available, the IP address of the RGMLC involved in the location request                                       |
+| Visited GMLC Identity        | C              | If available, the IP address of the VGMLC involved in the location request                                       |
+| Serving Network Identity     | O <sub>c</sub> | MCC and MNC of the serving network used during this record, if available.                                        |
+| LCS Client Type              | C              | The type of the LCS client that invoked the LR, if available.                                                    |
+| LCS Client Identity          | C              | Further identification of the LCS client, if available.                                                          |
+| Target IMSI                  | M              | The IMSI of the targeted LCS subscriber                                                                          |
+| Target MSISDN                | O <sub>m</sub> | The primary MSISDN of the targeted subscriber.                                                                   |
+| Location Type                | M              | The type of location information being requested.                                                                |
+| LCS Priority                 | C              | Priority of the LR, if available                                                                                 |
+| Result Code                  | O <sub>m</sub> | The result code that indicate the result of the request or individual positioning                                |
+| Record Time Stamp            | O <sub>m</sub> | Time of generation of the CDR                                                                                    |
+| Local Record Sequence Number | O <sub>m</sub> | Consecutive record number created by this node. The number is allocated sequentially including all CDR types.    |
+| Record extensions            | O <sub>c</sub> | A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
+
+##### 6.1.3.2.3 LCS Records for Visited GMLC (LCS-VGMT-CDR)
+
+If enabled, a LCS Visited GMLC Mobile terminated Charging Data Record (LCS-VGMT-CDR) shall be produced for each mobile a terminated location request is performed via the V-GMLC. The fields in the record are specified in table 6.1.3.2.3, which provides a brief description of each field.
+
+**Table 6.1.3.2.3: LCS Visited GMLC Mobile Terminated CDR (LCS-VGMT-CDR)**
+
+| Field                        | Category       | Description                                                                                                      |
+|------------------------------|----------------|------------------------------------------------------------------------------------------------------------------|
+| Record Type                  | M              | LCS Visited GMLC Mobile Terminated Record                                                                        |
+| Recording Entity             | M              | The E.164 address of this GMLC                                                                                   |
+| Home GMLC Identity           | C              | If available, the IP address of the HGMLC involved in the location request                                       |
+| LCS Client Type              | C              | The type of the LCS client that invoked the LR, if available.                                                    |
+| LCS Client Identity          | C              | Further identification of the LCS client, if available.                                                          |
+| Target IMSI                  | M              | The IMSI of the targeted LCS subscriber                                                                          |
+| Target MSISDN                | O <sub>m</sub> | The primary MSISDN of the targeted subscriber.                                                                   |
+| Location Type                | M              | The type of location information being requested.                                                                |
+| LCS Priority                 | C              | Priority of the LR, if available                                                                                 |
+| Result Code                  | O <sub>m</sub> | The result code that indicate the result of the request or individual positioning                                |
+| Record Time Stamp            | O <sub>m</sub> | Time of generation of the CDR                                                                                    |
+| Local Record Sequence Number | O <sub>m</sub> | Consecutive record number created by this node. The number is allocated sequentially including all CDR types.    |
+| Record extensions            | O <sub>c</sub> | A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
+
+#### 6.1.3.3 LCS Records for Network Initiated Location Request (LCS-GNI-CDR)
+
+If enabled, a LCS GMLC Network Induced Charging Data Record (LCS-GNI-CDR) shall be produced for each network induced location request performed via the GMLC. The fields in the record are specified in table 6.1.3.3, which provides a brief description of each field.
+
+**Table 6.1.3.3: LCS GMLC Network Induced CDR (LCS-GNI-CDR)**
+
+| Field                        | Category       | Description                                                                                                      |
+|------------------------------|----------------|------------------------------------------------------------------------------------------------------------------|
+| Record Type                  | M              | LCS GMLC Network Induced Record                                                                                  |
+| Recording Entity             | M              | The E.164 address of this GMLC                                                                                   |
+| LCS Client Type              | C              | The type of the LCS client that invoked the LR, if available.                                                    |
+| LCS Client Identity          | C              | Further identification of the LCS client, if available.                                                          |
+| Served IMSI                  | M              | The IMSI of the subscriber that requests the location.                                                           |
+| Served MSISDN                | O <sub>m</sub> | The primary MSISDN of the subscriber that requests the location.                                                 |
+| Serving Entity               | C              | The E.164 address of the serving MSC (in case of CS-NI-LR) or SGSN (in case of PS-NI-LR)                         |
+| Result Code                  | O <sub>m</sub> | The result code that indicate the result of the request or individual positioning                                |
+| Record Time Stamp            | O <sub>m</sub> | Time of generation of the CDR                                                                                    |
+| Local Record Sequence Number | O <sub>m</sub> | Consecutive record number created by this node. The number is allocated sequentially including all CDR types.    |
+| Record extensions            | O <sub>c</sub> | A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
+
+## 6.2 Data description for LCS online charging
+
+### 6.2.1 R<sub>o</sub> message contents
+
+The credit control request for the "interim interrogation" and "final interrogation" reports the actual number of "units" that were used, from what was previously reserved. This determines the actual amount debited from the subscriber's account.
+
+**Editor's note: The content above is FFS**
+
+Table 6.2.1 describes the use of these messages for online charging.
+
+**Table 6.2.1: Online Charging Messages Reference Table**
+
+| Command-Name           | Source | Destination | Abbreviation |
+|------------------------|--------|-------------|--------------|
+| Credit-Control-Request | GMLC   | OCS         | CCR          |
+| Credit-Control-Answer  | OCS    | GMLC        | CCA          |
+
+#### 6.2.1.1 LCS Credit-Control-Request Message
+
+Table 6.2.1.1 illustrates the basic structure of a Diameter credit control request message from GMLC as used for LCS online charging.
+
+**Table 6.2.1.1: Credit-Control-Request (CCR) Message Contents for LCS**
+
+| AVP                              | Category       | Description                                                                           |
+|----------------------------------|----------------|---------------------------------------------------------------------------------------|
+| Session-Id                       | M              | Described in RFC 3588, diameter base protocol [401]                                   |
+| Origin-Host                      | M              | Described in RFC 3588, diameter base protocol [401]                                   |
+| Origin-Realm                     | M              | Described in RFC 3588, diameter base protocol [401]                                   |
+| Destination-Realm                | M              | Described in RFC 3588, diameter base protocol [401]                                   |
+| Auth-Application-Id              | M              | Described in RFC 3588, diameter base protocol [401]                                   |
+| Destination-Host                 | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                                   |
+| User-Name                        | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                                   |
+| Origin-State-Id                  | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                                   |
+| Event-Timestamp                  | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                                   |
+| CC-Request-Type                  | M              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| CC-Request-Number                | M              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| CC-Sub-Session-Id                | M              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Acct-Multi-Session-Id            | ?              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Subscription-Id                  | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Service-Identifier               | ?              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Termination-Cause                | ?              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Requested-Service-Unit           | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Requested-Action                 | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Used-Service-Unit                | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Multiple-Services-Indicator      | O <sub>M</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Multiple-Services-Credit Control | O <sub>C</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| Service-Parameter-Info           | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| CC-Correlation-Id                | ?              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| User-Equipment-Info              | ?              | Described in Internet-Draft, Diameter Credit Control Application [402]                |
+| LCS-Information                  | O <sub>c</sub> | Holds the LCS service specific parameters. It is further described in the table below |
+
+NOTE: A full description and the detailed use of the AVPs for GMLC and for each CCR request type (initial/update/termination/event) is specified in TS 32.299 [50].
+
+#### 6.2.1.2 LCS Credit-Control-Answer Message
+
+Table 6.2.1.2 illustrates the basic structure of a Diameter credit control answer message as used for LCS charging. This message is always used by the OCS as specified below, independent of the receiving GMLC and the CCR request type that is being replied to.
+
+**Table 6.2.1.2: Credit-Control-Answer (CCA) Message Contents for LCS**
+
+| AVP                              | Category       | Description                                                            |
+|----------------------------------|----------------|------------------------------------------------------------------------|
+| Session-Id                       | M              | Described in RFC 3588, diameter base protocol [401]                    |
+| Result-Code                      | M              | Described in RFC 3588, diameter base protocol [401]                    |
+| Origin-Host                      | M              | Described in RFC 3588, diameter base protocol [401]                    |
+| Origin-Realm                     | M              | Described in RFC 3588, diameter base protocol [401]                    |
+| Auth-Application-Id              | M              | Described in RFC 3588, diameter base protocol [401]                    |
+| User-Name                        | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                    |
+| Origin-State-Id                  | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                    |
+| Event-Timestamp                  | O <sub>c</sub> | Described in RFC 3588, diameter base protocol [401]                    |
+| CC-Request-Type                  | M              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| CC-Request-Number                | M              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| CC-Session-Failover              | ?              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| CC-Sub-Session-Id                | M              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Acct-Multi-Session-Id            | ?              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Subscription-Id                  | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Granted-Service-Unit             | ?              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Multiple-Services-Credit Control | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Cost-Information                 | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Final-Unit-Indication            | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Check-Balance-Result             | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Credit-Control-Failure-Handling  | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Direct-Debiting-Failure-Handling | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Validity-Time                    | O <sub>c</sub> | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Redirect-Host AVP                | ?              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Redirect-Host-Usage              | ?              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+| Redirect-Max-Cache-Time          | ?              | Described in Internet-Draft, Diameter Credit Control Application [402] |
+
+## 6.3 LCS Charging Specific Parameters
+
+### 6.3.1 Definition of LCS charging information
+
+The LCS Information parameter used for LCS charging is provided in the Service Information parameter.
+
+#### 6.3.1.1 LCS charging information assignment for Service Information
+
+The components in the Service Information that are use for LCS charging can be found in Table 6.3.1.1.
+
+**Table 6.3.1.1: Service Information used for LCS Charging**
+
+| Field               | Category       | Description                                                                                                          |
+|---------------------|----------------|----------------------------------------------------------------------------------------------------------------------|
+| Service Information | O <sub>M</sub> | A set of fields hold the 3GPP specific parameter as defined in 3GPP TS 32.299 [50].                                  |
+| Subscription Id     | O <sub>M</sub> | Used as defined in 3GPP TS 32.260 [20].                                                                              |
+| LCS Information     | O <sub>M</sub> | This field holds a set of MMTel services with theirs specific parameters. The details are defined in clause 6.3.1.2. |
+
+#### 6.3.1.2 Definition of the LCS Information
+
+LCS specific charging information is provided within the LCS Information, and the detailed structure of the LCS Information can be found in table 6.3.1.2.
+
+**Table 6.3.1.2: Structure of the LCS Information**
+
+| Field             | Category       | Description                                                                                                                |
+|-------------------|----------------|----------------------------------------------------------------------------------------------------------------------------|
+| LCS Client ID     | O <sub>c</sub> | This field holds the ID of the LCS client that invoked the LR, if available.                                               |
+| Location Type     | O <sub>c</sub> | This field holds the type of location information being requested in case of MT-LR.                                        |
+| Location Estimate | O <sub>c</sub> | This field denotes the location of an MS in universal coordinates and the accuracy of the estimate upon successful MO-LR.  |
+| Positioning Data  | O <sub>c</sub> | This field indicates the positioning method that was attempted to determine the location estimate for MO-LR, if available. |
+
+# --- Annex A (informative): Bibliography
+
+## a) The 3GPP charging specifications
+
+- 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
+- 3GPP TS 32.252: "Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging".
+- 3GPP TS 23.125: "Overall High Level Functionality and Architecture Impacts of Flow Based Charging; Stage 2"
+
+## b) Common 3GPP specifications
+
+- 3GPP TS 22.101: "Service aspects; Service Principles".
+- 3GPP TS 22.115: "Service aspects; Charging and billing".
+- 3GPP TS 23.002: "Network Architecture".
+- 3GPP TS 23.003: "Numbering, addressing and identification".
+- 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+
+## c) other Domain and Service specific 3GPP / ETSI specifications
+
+- 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- GSM 04.02: "GSM Public Land Mobile Network (PLMN) access reference configuration".
+
+## d) Relevant ITU Recommendations
+
+- ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)".
+- ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- ITU-T Recommendation Q.767: "Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections".
+- ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".
+- ITU-T Recommendation X.121: "International numbering plan for public data networks".
+
+## e) Relevant IETF RFCs
+
+- IETF RFC 959 (1985): "File Transfer Protocol".
+- IETF RFC 1350: "The TFT Protocol (Revision 2)"
+
+# Annex B (informative): Change history
+
+| Change history |       |           |      |     |                                                           |     |        |        |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------|-----|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                           | Cat | Old    | New    |
+| Sep 2003       | SA 21 | SP-030411 | --   | --  | Submitted to TSG SA#21 for Information                    | --  | 1.0.0  | 1.1.0  |
+| Dec 2004       | SA 26 | SP-040781 | --   | --  | Submitted to TSG SA#26 for Approval                       | --  | 2.0.0  | 6.0.0  |
+| Jun 2005       | SA 28 | SP-050278 | 0001 | --  | Add peer GMLC Identification and network ID to LCS CDRs   | C   | 6.0.0  | 6.1.0  |
+| Jun 2005       | SA 28 | SP-050278 | 0002 | --  | Correction to scope                                       | F   | 6.0.0  | 6.1.0  |
+| Jun 2005       | SA 28 | SP-050278 | 0003 | --  | Correction to references                                  | F   | 6.0.0  | 6.1.0  |
+| Sep 2005       | SA 29 | SP-050622 | 0004 | --  | Correct GMLC address used in LCS CDRs                     | F   | 6.1.0  | 6.2.0  |
+| Jun 2007       | SA 36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7.    | --  | 6.2.0  | 7.0.0  |
+| Dec 2008       | SA 42 | SP-080841 | 0005 | --  | Correction on Multiple Service indication and parameter   | F   | 7.0.0  | 7.1.0  |
+| Dec 2008       | SA 42 | --        | --   | --  | Upgrade to Release 8                                      | --  | 7.1.0  | 8.0.0  |
+| Dec 2009       | -     | -         | -    | -   | Update to Rel-9 version (MCC)                             |     | 8.0.0  | 9.0.0  |
+| Dec 2010       | SA_50 | SP-100759 | 0006 | 2   | Change the Title of Clause 6.1.1 to "Rf message contents" | F   | 9.0.0  | 10.0.0 |
+| June-2012      | SA_56 | SP-120361 | 0012 | 3   | Correction of Location Information field in LCS Charging  | F   | 10.0.0 | 10.1.0 |

marked/Rel-10/32_series/32274/raw.md

@@ -0,0 +1,1011 @@
+
+
+# Keywords Charging, SMS, **3GPP TS 32.274 V10.0.0 (2011-03)**
+
+*Technical Specification*
+
+## **3GPP** **3rd Generation Partnership Project;** Postal address **Technical Specification Group Services and System Aspects;** **Telecommunication management;** 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 93 13 12 00 Fax: +33 4 93 13 47 36 **Charging management;** **Short Message Service**
+
+![LTE logo with '4ADVANCED' text above the 'e'](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e'
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon](390120de4fe440c42fea8154fcaad334_img.jpg)
+
+3GPP logo with a signal icon
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP) and may be further elaborated for the purposes of 3GPP.
+
+ETSI™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners and the GSM logo is a registered trademark of the GSM Association. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                                                          |    |
+|------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                           | 5  |
+| 1 Scope.....                                                                             | 6  |
+| 2 References.....                                                                        | 6  |
+| 3 Definitions and abbreviations .....                                                    | 7  |
+| 3.1 Definitions.....                                                                     | 7  |
+| 3.2 Abbreviations .....                                                                  | 7  |
+| 4 Architecture considerations.....                                                       | 8  |
+| 4.1 High level SMS architecture .....                                                    | 8  |
+| 4.2 SMS offline charging architecture .....                                              | 8  |
+| 4.3 SMS online charging architecture.....                                                | 8  |
+| 5 SMS charging principles and scenarios .....                                            | 9  |
+| 5.1 SMS charging principles.....                                                         | 9  |
+| 5.1.1 General principles.....                                                            | 9  |
+| 5.1.2 Segmentation and concatenation .....                                               | 9  |
+| 5.1.3 Triggers for generation of charging information .....                              | 9  |
+| 5.2 SMS offline charging scenarios .....                                                 | 11 |
+| 5.2.1 Basic principles .....                                                             | 11 |
+| 5.2.2 Rf message flows.....                                                              | 11 |
+| 5.2.3 CDR generation .....                                                               | 11 |
+| 5.2.3.1 Triggers for xxx-CDR charging information collection .....                       | 11 |
+| 5.2.3.2 Triggers for xxx-CDR Charging Information Addition .....                         | 11 |
+| 5.2.3.3 Triggers for xxx-CDR closure.....                                                | 11 |
+| 5.2.4 Ga record transfer flows .....                                                     | 11 |
+| 5.2.5 B <sub>xx</sub> CDR file transfer.....                                             | 11 |
+| 5.3 SMS online charging scenarios.....                                                   | 12 |
+| 5.3.1 Basic principles .....                                                             | 12 |
+| 5.3.2 Ro message flows.....                                                              | 12 |
+| 5.3.2.1 Simple Submission .....                                                          | 12 |
+| 5.3.2.2 Enhanced Submission.....                                                         | 13 |
+| 5.3.2.3 Delivery Report.....                                                             | 13 |
+| 5.3.2.4 Origination retry .....                                                          | 13 |
+| 5.3.2.5 Termination charge .....                                                         | 15 |
+| 5.3.2.6 Termination charge retry .....                                                   | 17 |
+| 5.3.2.7 Unsuccessful transaction.....                                                    | 19 |
+| 5.3.2.8 IMS/SMS Interworking Messages Charging.....                                      | 21 |
+| 5.3.2.9 Simple Submission with SM service request.....                                   | 23 |
+| 5.3.3 Credit Control related .....                                                       | 24 |
+| 5.3.3.1 Triggers for stopping for an SMS Credit Control session .....                    | 24 |
+| 5.3.3.2 Triggers for providing interim information for a SMS Credit Control session..... | 24 |
+| 6 Definition of charging information .....                                               | 25 |
+| 6.1 Data description for SMS offline charging .....                                      | 25 |
+| 6.1.1 Rf message contents .....                                                          | 25 |
+| 6.1.1.1 Summary of Offline Charging Message Formats .....                                | 25 |
+| 6.1.1.2 Structure for the Accounting Message Formats .....                               | 25 |
+| 6.1.1.2.1 Accounting-Request Message.....                                                | 25 |
+| 6.1.1.2.2 Accounting-Answer Message .....                                                | 25 |
+| 6.1.2 Ga message contents.....                                                           | 25 |
+| 6.1.3 CDR description on the B <sub>xx</sub> interface.....                              | 25 |
+| 6.2 Data description for SMS online charging.....                                        | 26 |
+| 6.2.1 Ro message contents.....                                                           | 26 |
+| 6.2.1.0 General.....                                                                     | 26 |
+| 6.2.1.1 Summary of Message Formats .....                                                 | 27 |
+| 6.2.1.2 Structure for the Credit Control Message Formats .....                           | 27 |
+| 6.2.1.2.1 Debit/Reserve Units Request Message .....                                      | 27 |
+| 6.2.1.2.2 Debit / Reserve Units Response Message .....                                   | 28 |
+
+|                        |                                                                   |    |
+|------------------------|-------------------------------------------------------------------|----|
+| 6.3                    | SMS charging specific parameters.....                             | 29 |
+| 6.3.1                  | Definition of the SMS charging information.....                   | 29 |
+| 6.3.1.1                | SMS charging information assignment for Service-Information ..... | 29 |
+| 6.3.1.2                | Definition of the SMS Information.....                            | 30 |
+| 6.3.2                  | Formal parameter description.....                                 | 31 |
+| 6.3.2.1                | SMS charging information for CDRs .....                           | 31 |
+| 6.3.2.2                | SMS charging information for charging events .....                | 31 |
+| Annex A (informative): | Change history.....                                               | 32 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# --- 1 Scope
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [2], which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain / subsystem / service (offline charging);
+- the content of real-time charging messages per domain / subsystem / service (online charging);
+- the functionality of online and offline charging for those domains / subsystems / services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
+
+The complete document structure for these TSs is defined in 3GPP TS 32.240 [2].
+
+The present document specifies the Offline and Online Charging description for the Short Message Service (SMS), based on the functional description in 3GPP TS 23.040 [7] and on the SMS over IP in 3GPP TS 23.204 [8]. The present document does not replace existing offline SMS charging functionality and therefore is in addition to that defined in 3GPP TS 32.250 [9] and 3GPP TS 32.251 [10]. This charging description includes the offline and online charging architecture and scenarios specific to SMS, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto SMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [2];
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in 3GPP TS 32.298 [3];
+- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [6];
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [5];
+- The 3GPP Diameter application that is used for SMS offline and online charging is specified in 3GPP TS 32.299 [4].
+
+Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102].
+
+# --- 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.240: "Telecommunication management; Charging management; Charging architecture and principles".
+- [3] 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) parameter description".
+- [4] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging application".
+
+- [5] 3GPP TS 32.297: "Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer".
+- [6] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
+- [7] 3GPP TS 23.040: "Technical realization of Short Message Service (SMS)"
+- [8] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2"
+- [9] 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain charging".
+- [10] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
+- [11] 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS) applications and interfaces".
+- [12] IETF RFC 4006: "Diameter Credit-Control Application"
+- [13] 3GPP TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging".
+- [14] 3GPP TS 23.038: "Alphabets and language-specific information".
+- [15] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Services (IMS) charging".
+- [16] 3GPP TS 22.142: " Value Added Services (VAS) for Short Message Service (SMS) requirements "
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 32.240 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or TS 32.240[2].
+
+**SMS node:** An SMS node, in this specification, refers to either an SMS router, IP-SM-GW, SMS-SC or a combination of these nodes.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 32.240 [2] 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] or TS 32.240 [2].
+
+# --- 4 Architecture considerations
+
+## 4.1 High level SMS architecture
+
+The high level SMS architecture is as defined in 3GPP TS 23.040 [7]. Only the SMS Router, SMS-SC and the IP-SM-GW are within the scope of this specification. The details for the other nodes in the SMS architecture are defined within 3GPP TS 32.250 [9] and 3GPP TS 32.251 [10].
+
+## 4.2 SMS offline charging architecture
+
+*Editor's Note: The offline architecture is For Further Study.*
+
+## 4.3 SMS online charging architecture
+
+For online charging, the relevant SMS nodes utilise the Ro interface and application towards the OCS as specified in TS 32.299 [4]. The Ro reference point covers all online charging functionality required for SMS.
+
+The SMS online charging architecture is depicted in figure 4.3.
+
+![Diagram of SMS online charging architecture showing SMS Router, SMS-SC, and IP-SM-GW connected to an Online Charging System via Ro interfaces.](e1a0d046fbe7f28f5e93a47091851747_img.jpg)
+
+```
+graph LR; SR[SMS Router] -- Ro --> OCS[Online Charging System]; SC[SMS-SC] -- Ro --> OCS; ISGW[IP-SM-GW] -- Ro --> OCS;
+```
+
+The diagram illustrates the SMS online charging architecture. On the left, three rectangular boxes are stacked vertically, labeled 'SMS Router', 'SMS-SC', and 'IP-SM-GW'. Each box has a horizontal line extending from its right side to a central vertical bus. Each of these horizontal lines is labeled 'Ro' at the point where it meets the bus. The central vertical bus is connected to a large blue rectangular box on the right labeled 'Online Charging System'.
+
+Diagram of SMS online charging architecture showing SMS Router, SMS-SC, and IP-SM-GW connected to an Online Charging System via Ro interfaces.
+
+**Figure 4.3: SMS online charging architecture**
+
+Details on the interfaces and functions can be found in TS 32.240 [2] for the general architecture components, TS 32.296 [11] for the OCS, and 32.299 [4] for the Ro application.
+
+# --- 5 SMS charging principles and scenarios
+
+## 5.1 SMS charging principles
+
+### 5.1.1 General principles
+
+The Short Message Service comprises 4 main operational scenarios:
+
+- Person to Person: The message is sent by a UE as originator and received by a UE as destination.
+- Person to Application: The message is sent by a UE as originator and received by a third party application as destination.
+- Application to Person: The message is sent by a third party application as originator and received by a UE as destination.
+- Application to Application: The message is sent by a third party application as originator and received by another third party application as destination.
+
+In addition SMS Nodes may apply services such as value added services specified in 3GPP TS 22.142 [16], services defined in industry standard protocols for SM submission from applications in a fixed network (protocols such as SMPP, UCP/EMI, OIS, CIMD, etc.) or vendor specific services as endorsed by 3GPP TS 23.040 [7].
+
+As such, the SMS node collects charging information such as:
+
+- the destination and source addresses applied for an SM;
+- an indication of origination or termination handling;
+- identification of the node(s) and connection(s) involved in the SM transaction;
+- SM validity period;
+- in scenarios involving an application / VASP, the charging information describes the identification of the application / VASP;
+- requested SM service type.
+
+### 5.1.2 Segmentation and concatenation
+
+Information about concatenated messages should be sent to the charging systems in order to apply the appropriate charging models. The charging system may be required to be stateful to process information about segmented messages.
+
+### 5.1.3 Triggers for generation of charging information
+
+The following service level events shall, based on operator configuration, trigger the generation of charging information:
+
+- Simple submission – based on reception at the SMS node.
+- Enhanced submission – based on completion of the transaction handling at the SMS node.
+- Origination retry – based on the enhanced submission where the initial handling fails and a redelivery attempt is initiated.
+- Delivery report
+- Termination – Application to Person scenario only.
+- Termination retry – Application to Person scenario only – reattempt delivery of an SM to a terminating entity;
+- SM service request.
+
+Depending on the charging model applied, a "refund" may be necessary for unsuccessful delivery.
+
+See clause 5.3 for detailed procedures associated with the triggers above.
+
+## 5.2 SMS offline charging scenarios
+
+### 5.2.1 Basic principles
+
+*Editor's Note: For Further Study.*
+
+### 5.2.2 Rf message flows
+
+*Editor's Note: For Further Study.*
+
+### 5.2.3 CDR generation
+
+#### 5.2.3.1 Triggers for xxx-CDR charging information collection
+
+*Editor's Note: For Further Study.*
+
+#### 5.2.3.2 Triggers for xxx-CDR Charging Information Addition
+
+*Editor's Note: For Further Study.*
+
+#### 5.2.3.3 Triggers for xxx-CDR closure
+
+*Editor's Note: For Further Study.*
+
+### 5.2.4 Ga record transfer flows
+
+*Editor's Note: For Further Study.*
+
+### 5.2.5 B<sub>xx</sub> CDR file transfer
+
+*Editor's Note: For Further Study.*
+
+## 5.3 SMS online charging scenarios
+
+### 5.3.1 Basic principles
+
+SMS online charging uses the Credit Control application as specified in 3GPP TS 32.299 [4].
+
+SMS charging may use the Immediate Event Charging (IEC) principle or the Event Charging with Unit Reservation (ECUR) principle as specified in 3GPP TS 32.299 [4]. The chargeable events for subscriber charging are associated with SM transactions.
+
+An implementation may use either IEC or ECUR for charging events based on operator configuration.
+
+The units used for quota shall be service specific and based on an SM.
+
+The selection of the OCS is implementation specific as there is no guaranteed means of providing the OCS address to the CTF.
+
+In addition, SMS charging may use the Refund Account principle when the operation has not been successfully completed after an Immediate Event Charging (IEC).
+
+NOTE: For SMSIP, the IP-SM-GW may receive information relevant for online charging through signalling in IMS.
+
+### 5.3.2 Ro message flows
+
+#### 5.3.2.1 Simple Submission
+
+This clause contains message flows for the different operation models IEC (figure 5.3.2.1-1) and ECUR (figure 5.3.2.1-2).
+
+![Sequence diagram showing the online charging process for IEC. The diagram involves two main entities: SMS Node and OCS. The sequence of messages is: 1. SM-Submit or Forward-SM (incoming to SMS Node), 2. Debit Units Request (SMS Node to OCS), 3. Credit processing (internal to OCS), 4. Debit Units Response (OCS to SMS Node), 5. Forward-SM (outgoing from SMS Node).](5a95b187de0044da69b7322e04761b86_img.jpg)
+
+```
+sequenceDiagram
+    participant External
+    participant SMS Node
+    participant OCS
+    Note right of OCS: 3. Credit processing
+    External->>SMS Node: 1. SM-Submit or Forward-SM
+    SMS Node->>OCS: 2. Debit Units Request
+    OCS->>SMS Node: 4. Debit Units Response
+    SMS Node->>External: 5. Forward-SM
+```
+
+Sequence diagram showing the online charging process for IEC. The diagram involves two main entities: SMS Node and OCS. The sequence of messages is: 1. SM-Submit or Forward-SM (incoming to SMS Node), 2. Debit Units Request (SMS Node to OCS), 3. Credit processing (internal to OCS), 4. Debit Units Response (OCS to SMS Node), 5. Forward-SM (outgoing from SMS Node).
+
+**Figure 5.3.2.1-1: Online charging in simple submission for IEC**
+
+- 1) Depending on which SMS mechanism (i.e. SMS or SMSIP) is in operation, the SMS node receives an incoming SM-Submit or a MAP-Forward-SM.
+- 2) The SMS node triggers a Debit Units Request message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Debit Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the origination procedures.
+
+![Sequence diagram for online charging in simple submission for ECUR. The diagram shows interactions between an external source, an SMS Node, and an OCS. The sequence is: 1. SM-Submit or Forward-SM to SMS Node; 2. Reserve Units Request (Initial) from SMS Node to OCS; 3. Credit processing in OCS; 4. Reserve Units Response (Initial) from OCS to SMS Node; 5. Forward short message from SMS Node; 6. Forward short message acknowledgement from SMS Node; 7. Reserve Units Request (Terminate) from SMS Node to OCS; 8. Credit processing in OCS; 9. Reserve Units Response (Terminate) from OCS to SMS Node.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+```
+
+sequenceDiagram
+    participant External
+    participant SMS Node
+    participant OCS
+    Note right of OCS: 3. Credit processing
+    Note right of OCS: 8. Credit processing
+    External->>SMS Node: 1. SM-Submit or Forward-SM
+    SMS Node->>OCS: 2. Reserve Units Request (Initial)
+    OCS->>SMS Node: 4. Reserve Units Response (Initial)
+    SMS Node->>External: 5. Forward short message
+    SMS Node->>SMS Node: 6. Forward short message acknowledgement
+    SMS Node->>OCS: 7. Reserve Units Request (Terminate)
+    OCS->>SMS Node: 9. Reserve Units Response (Terminate)
+  
+```
+
+Sequence diagram for online charging in simple submission for ECUR. The diagram shows interactions between an external source, an SMS Node, and an OCS. The sequence is: 1. SM-Submit or Forward-SM to SMS Node; 2. Reserve Units Request (Initial) from SMS Node to OCS; 3. Credit processing in OCS; 4. Reserve Units Response (Initial) from OCS to SMS Node; 5. Forward short message from SMS Node; 6. Forward short message acknowledgement from SMS Node; 7. Reserve Units Request (Terminate) from SMS Node to OCS; 8. Credit processing in OCS; 9. Reserve Units Response (Terminate) from OCS to SMS Node.
+
+**Figure 5.3.2.1-2: Online charging in simple submission for ECUR**
+
+- 1) Depending on which SMS mechanism (i.e. SMS or SMSIP) is in operation, the SMS node receives an incoming SM-Submit or a MAP-Forward-SM.
+- 2) The SMS node triggers a Reserve Units Request (Initial) message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Reserve Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the origination procedures.
+- 6) The SM transaction is successfully acknowledged.
+- 7) The SMS node triggers a Reserve Units Request (Terminate) message to the OCS reporting the successful event transaction.
+- 8) The OCS performs the appropriate credit processing based on the received request.
+- 9) The OCS responds with a Reserve Units Response message to the SMS node..
+
+#### 5.3.2.2 Enhanced Submission
+
+The enhanced submission procedures are similar to the simple submission procedures using ECUR. However, the trigger for Reserve Units Request (Terminate) may be based on unsuccessful handling e.g. negative acknowledgement and with or without successful storage of the message for future redelivery attempts. See failure scenarios defined in clause 5.3.2.7.
+
+#### 5.3.2.3 Delivery Report
+
+The origination of delivery reports use the same procedures as the simple submission procedures as described within clause 5.3.2.1. The delivery report itself is contained within a new SM.
+
+#### 5.3.2.4 Origination retry
+
+This clause contains message flows for the different operation models IEC (figure 5.3.2.4-1) and ECUR (figure 5.3.2.4-2) for redelivery attempts in the origination direction.
+
+![Sequence diagram for IEC online charging in origination redelivery attempt. Lifelines: SMS Node and OCS. Steps: 1. Internal trigger to attempt redelivery attempt (SMS Node); 2. Debit Units Request (SMS Node to OCS); 3. Credit processing (OCS); 4. Debit Units Response (OCS to SMS Node); 5. Forward short message (SMS Node).](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note left of SMS Node: 1. Internal trigger to attempt redelivery attempt
+    SMS Node->>OCS: 2. Debit Units Request
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Debit Units Response
+    SMS Node->>OCS: 5. Forward short message
+  
+```
+
+Sequence diagram for IEC online charging in origination redelivery attempt. Lifelines: SMS Node and OCS. Steps: 1. Internal trigger to attempt redelivery attempt (SMS Node); 2. Debit Units Request (SMS Node to OCS); 3. Credit processing (OCS); 4. Debit Units Response (OCS to SMS Node); 5. Forward short message (SMS Node).
+
+**Figure 5.3.2.4-1: Online charging in origination redelivery attempt for IEC**
+
+- 1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.
+- 2) The SMS node triggers a Debit Units Request message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Debit Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the origination procedures.
+
+![Sequence diagram for ECUR online charging in origination redelivery attempt. Lifelines: SMS Node and OCS. Steps: 1. Internal trigger to attempt redelivery attempt (SMS Node); 2. Reserve Units Request (Initial) (SMS Node to OCS); 3. Credit processing (OCS); 4. Reserve Units Response (Initial) (OCS to SMS Node); 5. Forward short message (SMS Node); 6. Forward short message acknowledgement (OCS to SMS Node); 7. Reserve Units Request (Terminate) (SMS Node to OCS); 8. Credit processing (OCS); 9. Reserve Units Response (Terminate) (OCS to SMS Node).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note left of SMS Node: 1. Internal trigger to attempt redelivery attempt
+    SMS Node->>OCS: 2. Reserve Units Request (Initial)
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Reserve Units Response (Initial)
+    SMS Node->>OCS: 5. Forward short message
+    OCS-->>SMS Node: 6. Forward short message acknowledgement
+    SMS Node->>OCS: 7. Reserve Units Request (Terminate)
+    Note right of OCS: 8. Credit processing
+    OCS-->>SMS Node: 9. Reserve Units Response (Terminate)
+  
+```
+
+Sequence diagram for ECUR online charging in origination redelivery attempt. Lifelines: SMS Node and OCS. Steps: 1. Internal trigger to attempt redelivery attempt (SMS Node); 2. Reserve Units Request (Initial) (SMS Node to OCS); 3. Credit processing (OCS); 4. Reserve Units Response (Initial) (OCS to SMS Node); 5. Forward short message (SMS Node); 6. Forward short message acknowledgement (OCS to SMS Node); 7. Reserve Units Request (Terminate) (SMS Node to OCS); 8. Credit processing (OCS); 9. Reserve Units Response (Terminate) (OCS to SMS Node).
+
+**Figure 5.3.2.4-2: Online charging in origination redelivery attempt for ECUR**
+
+- 1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.
+- 2) The SMS node triggers a Reserve Units Request (Initial) message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Reserve Units Response message to the SMS node.
+
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the origination or termination procedures.
+- 6) The SM transaction is successfully acknowledged.
+- 7) The SMS node triggers a Reserve Units Request (Terminate) message to the OCS reporting the successful event transaction.
+- 8) The OCS performs the appropriate credit processing based on the received request.
+- 9) The OCS responds with a Reserve Units Response message to the SMS node.
+
+#### 5.3.2.5 Termination charge
+
+![Sequence diagram showing online charging in termination for IEC. The diagram involves two main entities: SMS Node and OCS. The sequence of messages is: 1. SM-SUBMIT (incoming to SMS Node), 2. Debit Units Request (SMS Node to OCS), 3. Credit processing (OCS internal), 4. Debit Units Response (OCS to SMS Node), 5. Standard SMS handling (SMS Node internal).](724c7777b608e53be38b12b6fb3c43bc_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note over SMS Node, OCS: 
+    [Incoming Arrow]-->>SMS Node: 1. SM-SUBMIT
+    SMS Node->>OCS: 2. Debit Units Request
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Debit Units Response
+    Note left of SMS Node: 5. Standard SMS handling
+  
+```
+
+Sequence diagram showing online charging in termination for IEC. The diagram involves two main entities: SMS Node and OCS. The sequence of messages is: 1. SM-SUBMIT (incoming to SMS Node), 2. Debit Units Request (SMS Node to OCS), 3. Credit processing (OCS internal), 4. Debit Units Response (OCS to SMS Node), 5. Standard SMS handling (SMS Node internal).
+
+**Figure 5.3.2.5-1: Online charging in termination for IEC**
+
+- 1) The SMS node receives an incoming SM-SUBMIT from an application destined for a mobile recipient.
+
+NOTE: This scenario differs from simple submission charging as described in subclause 5.3.2.1 in that typically the mobile recipient (instead of originator or both parties) will be charged for such a short message.
+
+- 2) The SMS node triggers a Debit Units Request message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Debit Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the termination procedures.
+
+![Sequence diagram showing online charging in termination for ECUR between an SMS Node and an OCS. The sequence starts with an external SM-SUBMIT to the SMS Node. The SMS Node sends a Reserve Units Request (Initial) to the OCS. The OCS performs credit processing and returns a Reserve Units Response (Initial). The SMS Node then forwards the short message. The OCS sends a Forward short message acknowledgement. The SMS Node sends a Reserve Units Request (Terminate) to the OCS. The OCS performs credit processing and returns a Reserve Units Response (Terminate).](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant External
+    participant SMS Node
+    participant OCS
+    Note right of OCS: 3. Credit processing
+    Note right of OCS: 8. Credit processing
+
+    External->>SMS Node: 1. SM-SUBMIT
+    SMS Node->>OCS: 2. Reserve Units Request (Initial)
+    OCS->>OCS: 3. Credit processing
+    OCS->>SMS Node: 4. Reserve Units Response (Initial)
+    SMS Node->>External: 5. Forward short message
+    External->>OCS: 6. Forward short message acknowledgement
+    SMS Node->>OCS: 7. Reserve Units Request (Terminate)
+    OCS->>OCS: 8. Credit processing
+    OCS->>SMS Node: 9. Reserve Units Response (Terminate)
+  
+```
+
+Sequence diagram showing online charging in termination for ECUR between an SMS Node and an OCS. The sequence starts with an external SM-SUBMIT to the SMS Node. The SMS Node sends a Reserve Units Request (Initial) to the OCS. The OCS performs credit processing and returns a Reserve Units Response (Initial). The SMS Node then forwards the short message. The OCS sends a Forward short message acknowledgement. The SMS Node sends a Reserve Units Request (Terminate) to the OCS. The OCS performs credit processing and returns a Reserve Units Response (Terminate).
+
+**Figure 5.3.2.5-2: Online charging in termination for ECUR**
+
+- 1) The SMS node receives an incoming SM-SUBMIT from an application destined for a mobile recipient.
+
+NOTE: This scenario differs from simple submission charging as described in subclause 5.3.2.1 in that typically the mobile recipient (instead of originator or both parties) will be charged for such a short message.
+
+- 2) The SMS node triggers a Reserve Units Request (Initial) message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Reserve Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the termination procedures.
+- 6) The SM transaction is successfully acknowledged.
+- 7) The SMS node triggers a Reserve Units Request (Terminate) message to the OCS reporting the successful event transaction.
+- 8) The OCS performs the appropriate credit processing based on the received request.
+- 9) The OCS responds with a Reserve Units Response message to the SMS node.
+
+#### 5.3.2.6 Termination charge retry
+
+![Sequence diagram for IEC termination charge retry showing interactions between SMS Node and OCS.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note left of SMS Node: 1. Internal trigger to attempt redelivery attempt
+    SMS Node->>OCS: 2. Debit Units Request
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Debit Units Response
+    Note left of SMS Node: 5. Standard SMS handling
+  
+```
+
+Sequence diagram for IEC termination charge retry showing interactions between SMS Node and OCS.
+
+**Figure 5.3.2.6-1: Online charging in termination redelivery attempt for IEC**
+
+- 1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.
+- 2) The SMS node triggers a Debit Units Request message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Debit Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the termination procedures.
+
+![Sequence diagram for ECUR termination charge retry showing interactions between SMS Node and OCS.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note left of SMS Node: 1. Internal trigger to attempt redelivery attempt
+    SMS Node->>OCS: 2. Reserve Units Request (Initial)
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Reserve Units Response (Initial)
+    SMS Node->>OCS: 5. Forward short message
+    OCS-->>SMS Node: 6. Forward short message acknowledgement
+    SMS Node->>OCS: 7. Reserve Units Request (Terminate)
+    Note right of OCS: 8. Credit processing
+    OCS-->>SMS Node: 9. Reserve Units Response
+  
+```
+
+Sequence diagram for ECUR termination charge retry showing interactions between SMS Node and OCS.
+
+**Figure 5.3.2.6-2: Online charging in termination redelivery attempt for ECUR**
+
+- 1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.
+- 2) The SMS node triggers a Reserve Units Request (Initial) message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Reserve Units Response message to the SMS node.
+
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the termination procedures.
+- 6) The SM transaction is successfully acknowledged.
+- 7) The SMS node triggers a Reserve Units Request (Terminate) message to the OCS reporting the successful event transaction.
+- 8) The OCS performs the appropriate credit processing based on the received request.
+- 9) The OCS responds with a Reserve Units Response message to the SMS node.
+
+#### 5.3.2.7 Unsuccessful transaction
+
+Unsuccessful transaction after IEC
+
+The following flow in figure 5.3.2.7-1 only applies where a refund action is required for unsuccessful delivery.
+
+![Sequence diagram for Unsuccessful transaction after IEC. The diagram shows the interaction between an SMS Node and an OCS. The process starts with a 'Trigger to attempt delivery' at the SMS Node. The SMS Node sends a 'Debit Units Request' to the OCS. The OCS performs 'Credit processing' and responds with a 'Debit Units Response'. The SMS Node then attempts to 'Forward short message', but receives a 'Forward short message NOK' from the OCS. The SMS Node then sends a 'Debit Units Request (Refund Account)' to the OCS. The OCS performs 'Credit Refund' and responds with a 'Debit Units Response (Refund Account)'.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note left of SMS Node: 1. Trigger to attempt delivery
+    SMS Node->>OCS: 2. Debit Units Request
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Debit Units Response
+    SMS Node->>OCS: 5. Forward short message
+    OCS-->>SMS Node: 6. Forward short message NOK
+    SMS Node->>OCS: 7. Debit Units Request (Refund Account)
+    Note right of OCS: 8. Credit Refund
+    OCS-->>SMS Node: 9. Debit Units Response (Refund Account)
+  
+```
+
+Sequence diagram for Unsuccessful transaction after IEC. The diagram shows the interaction between an SMS Node and an OCS. The process starts with a 'Trigger to attempt delivery' at the SMS Node. The SMS Node sends a 'Debit Units Request' to the OCS. The OCS performs 'Credit processing' and responds with a 'Debit Units Response'. The SMS Node then attempts to 'Forward short message', but receives a 'Forward short message NOK' from the OCS. The SMS Node then sends a 'Debit Units Request (Refund Account)' to the OCS. The OCS performs 'Credit Refund' and responds with a 'Debit Units Response (Refund Account)'.
+
+**Figure 5.3.2.7-1: Unsuccessful transaction after IEC**
+
+- 1) The SMS node receives a trigger to attempt delivery of an SM. This may be for origination, termination or redelivery attempt.
+- 2) The SMS node triggers a Debit Units Request message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Debit Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for origination or termination procedures.
+- 6) The SM transaction is acknowledged as an unsuccessful transaction (either via explicit signalling or an internal trigger).
+- 7) The SMS node triggers a Debit Units Request (Refund Account) message to the OCS.
+- 8) The OCS performs the appropriate refund processing based on the received request.
+- 9) The OCS responds with a Debit Units Response (Refund Account) message to the SMS node.
+
+##### Unsuccessful transaction in ECUR
+
+![Sequence diagram illustrating an unsuccessful transaction in ECUR between an SMS Node and an OCS.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg)
+
+```
+sequenceDiagram
+    participant SMS Node
+    participant OCS
+    Note left of SMS Node: 1. Trigger to attempt delivery
+    SMS Node->>OCS: 2. Reserve Units Request (Initial)
+    Note right of OCS: 3. Credit processing
+    OCS-->>SMS Node: 4. Reserve Units Response (Initial)
+    SMS Node->>OCS: 5. Forward short message
+    OCS-->>SMS Node: 6. Forward short message NOK
+    SMS Node->>OCS: 7. Reserve Units Request (Terminate)
+    Note right of OCS: 8. Credit processing
+    OCS-->>SMS Node: 9. Reserve Units Response (Terminate)
+```
+
+The diagram is a sequence diagram with two lifelines: SMS Node and OCS. The interaction begins with a self-message on the SMS Node labeled '1. Trigger to attempt delivery'. The SMS Node sends a '2. Reserve Units Request (Initial)' message to the OCS. The OCS performs '3. Credit processing' and responds with '4. Reserve Units Response (Initial)'. The SMS Node then sends '5. Forward short message' to the OCS. The OCS responds with '6. Forward short message NOK'. The SMS Node sends '7. Reserve Units Request (Terminate)' to the OCS. The OCS performs '8. Credit processing' and responds with '9. Reserve Units Response (Terminate)'.
+
+Sequence diagram illustrating an unsuccessful transaction in ECUR between an SMS Node and an OCS.
+
+**Figure 5.3.2.7-2: Unsuccessful transaction for ECUR**
+
+- 1) The SMS node receives a trigger occurs to attempt delivery of an SM. This may be for origination, termination or redelivery attempt.
+- 2) The SMS node triggers a Reserve Units Request (Initial) message to the OCS.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Reserve Units Response message to the SMS node.
+- 5) If authorised, the SMS node continues the SM processing as appropriate for the origination or termination procedures.
+- 6) The SM transaction is acknowledged as an unsuccessful transaction (either via explicit signalling or an internal trigger).
+- 7) The SMS node triggers a Reserve Units Request (Terminate) message to the OCS reporting the used unit for the service to zero. This characterizes the unsuccessful event transaction.
+- 8) The OCS performs the appropriate credit processing based on the received request.
+- 9) The OCS responds with a Reserve Units Response message to the SMS node.
+
+#### 5.3.2.8 IMS/SMS Interworking Messages Charging
+
+This clause contains message flows for the different operation models IEC (figure 5.3.2.8-1) and ECUR (figure 5.3.2.8-2) for IMS/SMS Interworking messages in the origination direction.
+
+![Sequence diagram for online charging in origination IMS/SMS Interworking Messages for IEC. The diagram shows the interaction between an IP-SM-GW and an OCS. The process starts with an incoming SIP MESSAGE to the IP-SM-GW. The IP-SM-GW then parses the message and sends a Debit Units Request to the OCS. The OCS performs credit processing and returns a Debit Units Response. The IP-SM-GW then converts the SIP MESSAGE to 1 or n short messages and forwards them. The diagram includes a dashed line indicating a delay or continuation.](5445597cceefaca1ac89e710fe339325_img.jpg)
+
+```
+sequenceDiagram
+    participant External
+    participant IP_SM_GW as IP-SM-GW
+    participant OCS
+    Note right of IP_SM_GW: 2. Parse the SIP MESSAGE
+    Note right of OCS: 4. Credit processing
+    Note right of IP_SM_GW: 6. Convert the SIP MESSAGE to 1 or n short messages
+
+    External->>IP_SM_GW: 1. SIP MESSAGE
+    IP_SM_GW->>OCS: 3. Debit Units Request
+    OCS->>IP_SM_GW: 5. Debit Units Response
+    IP_SM_GW->>External: 7. Forward segmented short messages
+```
+
+Sequence diagram for online charging in origination IMS/SMS Interworking Messages for IEC. The diagram shows the interaction between an IP-SM-GW and an OCS. The process starts with an incoming SIP MESSAGE to the IP-SM-GW. The IP-SM-GW then parses the message and sends a Debit Units Request to the OCS. The OCS performs credit processing and returns a Debit Units Response. The IP-SM-GW then converts the SIP MESSAGE to 1 or n short messages and forwards them. The diagram includes a dashed line indicating a delay or continuation.
+
+**Figure 5.3.2.8-1: Online charging in origination IMS/SMS Interworking Messages for IEC**
+
+- 1) The IP-SM-GW receives an incoming SIP MESSAGE.
+- 2) The IP-SM-GW parses the SIP MESSAGE.
+- 3) The IP-SM-GW triggers a Debit Units Request message to the OCS.
+- 4) The OCS performs the appropriate credit processing based on the received Debit Units Request.
+- 5) The OCS responds with a Debit Units Response message to the IP-SM-GW.
+- 6) IP-SM-GW converts the SIP MESSAGE to 1 or n ( $n \geq 1$ ) short messages.
+- 7) If authorised, the IP-SM-GW forwards the segmented short messages.
+
+![Sequence diagram showing online charging in origination IMS/SMS Interworking Messages for ECUR. The diagram involves two main entities: IP-SM-GW and OCS. The sequence of messages is: 1. SIP MESSAGE (incoming to IP-SM-GW), 2. Parse the SIP MESSAGE (internal to IP-SM-GW), 3. Reserve Units Request (Initial) (IP-SM-GW to OCS), 4. Credit processing (internal to OCS), 5. Reserve Units Response (Initial) (OCS to IP-SM-GW), 6. Convert the SIP MESSAGE 1 or n short messages (internal to IP-SM-GW), 7. Forward segmented short messages (IP-SM-GW to OCS), 8. Forward segmented short messages acknowledgement (OCS to IP-SM-GW), 9. Reserve Units Request (Terminate) (IP-SM-GW to OCS), 10. Credit processing (internal to OCS), 11. Reserve Units Response (Terminate) (OCS to IP-SM-GW).](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg)
+
+```
+
+sequenceDiagram
+    participant External
+    participant IP-SM-GW
+    participant OCS
+    External->>IP-SM-GW: 1. SIP MESSAGE
+    Note over IP-SM-GW: 2. Parse the SIP MESSAGE
+    IP-SM-GW->>OCS: 3. Reserve Units Request (Initial)
+    Note over OCS: 4. Credit processing
+    OCS->>IP-SM-GW: 5. Reserve Units Response (Initial)
+    Note over IP-SM-GW: 6. Convert the SIP MESSAGE  
+1 or n short messages
+    IP-SM-GW->>OCS: 7. Forward segmented short messages
+    Note over IP-SM-GW,OCS: ...
+    IP-SM-GW->>OCS: 
+    OCS->>IP-SM-GW: 8. Forward segmented short messages acknowledgement
+    Note over IP-SM-GW,OCS: ...
+    OCS->>IP-SM-GW: 
+    IP-SM-GW->>OCS: 9. Reserve Units Request (Terminate)
+    Note over OCS: 10. Credit processing
+    OCS->>IP-SM-GW: 11. Reserve Units Response (Terminate)
+  
+```
+
+Sequence diagram showing online charging in origination IMS/SMS Interworking Messages for ECUR. The diagram involves two main entities: IP-SM-GW and OCS. The sequence of messages is: 1. SIP MESSAGE (incoming to IP-SM-GW), 2. Parse the SIP MESSAGE (internal to IP-SM-GW), 3. Reserve Units Request (Initial) (IP-SM-GW to OCS), 4. Credit processing (internal to OCS), 5. Reserve Units Response (Initial) (OCS to IP-SM-GW), 6. Convert the SIP MESSAGE 1 or n short messages (internal to IP-SM-GW), 7. Forward segmented short messages (IP-SM-GW to OCS), 8. Forward segmented short messages acknowledgement (OCS to IP-SM-GW), 9. Reserve Units Request (Terminate) (IP-SM-GW to OCS), 10. Credit processing (internal to OCS), 11. Reserve Units Response (Terminate) (OCS to IP-SM-GW).
+
+**Figure 5.3.2.8-2: Online charging in origination IMS/SMS Interworking Messages for ECUR**
+
+- 1) The IP-SM-GW receives an incoming SIP MESSAGE.
+- 2) The IP-SM-GW parses the SIP MESSAGE.
+- 3) The IP-SM-GW triggers a Reserve Units Request (Initial) message to the OCS.
+- 4) The OCS performs the appropriate credit processing based on the received Reserve Units Request.
+- 5) The OCS responds with a Reserve Units Response message to the IP-SM-GW.
+- 6) IP-SM-GW converts the SIP MESSAGE to 1 or n ( $n \geq 1$ ) short messages.
+- 7) If authorised, the IP-SM-GW forwards segmented short messages.
+- 8) All the short messages transactions are successfully acknowledged.
+- 9) The IP-SM-GW triggers a Reserve Units Request (Terminate) message to the OCS reporting the successful event transaction.
+- 10) The OCS performs the appropriate credit processing based on the received request.
+
+11) The OCS responds with a Reserve Units Response message to the IP-SM-GW.
+
+#### 5.3.2.9 Simple Submission with SM service request
+
+This clause contains message flows for operation models IEC (figure 5.3.2.9-1) where application of a SM service is subject to charging independent from the SM submission.
+
+**Editors Note: Simple SM submission with SM service request for operation model ECUR is FFS.**
+
+![Sequence diagram for online charging in simple submission with SM service request for IEC. The diagram shows interactions between an external source, an SMS Node, and an OCS. The sequence is: 1. SM-SUBMIT to SMS Node; 2. Debit Units Request 1 from SMS Node to OCS; 3. Credit processing in OCS; 4. Debit Units Response 1 from OCS to SMS Node; 5. SM Service Requested in SMS Node; 6. Debit Units Request 2 from SMS Node to OCS; 7. Credit processing 2 in OCS; 8. Debit Units Response 2 from OCS to SMS Node; 9. Service Application in SMS Node; 10. Forward -SM from SMS Node to external destination.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg)
+
+```
+sequenceDiagram
+    participant External
+    participant SMS Node
+    participant OCS
+    Note right of OCS: 3. Credit processing
+    Note right of OCS: 7. Credit processing 2
+    Note right of SMS Node: 5. SM Service Requested
+    Note right of SMS Node: 9. Service Application
+
+    External->>SMS Node: 1. SM-SUBMIT
+    SMS Node->>OCS: 2. Debit Units Request 1
+    OCS->>SMS Node: 4. Debit Units Response 1
+    SMS Node->>OCS: 6. Debit Units Request 2
+    OCS->>SMS Node: 8. Debit Units Response 2
+    SMS Node->>External: 10. Forward -SM
+```
+
+Sequence diagram for online charging in simple submission with SM service request for IEC. The diagram shows interactions between an external source, an SMS Node, and an OCS. The sequence is: 1. SM-SUBMIT to SMS Node; 2. Debit Units Request 1 from SMS Node to OCS; 3. Credit processing in OCS; 4. Debit Units Response 1 from OCS to SMS Node; 5. SM Service Requested in SMS Node; 6. Debit Units Request 2 from SMS Node to OCS; 7. Credit processing 2 in OCS; 8. Debit Units Response 2 from OCS to SMS Node; 9. Service Application in SMS Node; 10. Forward -SM from SMS Node to external destination.
+
+**Figure 5.3.2.9-1: Online charging in simple submission with SM service request for IEC**
+
+- 1) Depending on which SMS mechanism (i.e. SMS or SMSIP) is in operation, the SMS node receives an incoming SM-Submit or a MAP-Forward-SM which includes a SM service request (such as forwarding or SM copy).
+- 2) The SMS node triggers a Debit Units Request message to the OCS for the SM submission.
+- 3) The OCS performs the appropriate credit processing based on the received request.
+- 4) The OCS responds with a Debit Units Response message for the SM submission to the SMS node.
+- 5) If normal SM processing is authorized in step 4, the SMS Node analyzes the SM and detects that a SM service must be applied that is subject to charging.
+- 6) If a SM service subject to charging is detected in step 5, the SMS node triggers an additional Debit Units Request message to the OCS for the requested SM service.
+- 7) The OCS performs the appropriate credit processing based on the received request.
+- 8) The OCS responds with a Debit Units Response message for the requested SM service to the SMS node.
+- 9) If authorised in step 7, the SMS node applies the requested SM service.
+
+NOTE 1: Depending on the nature of the requested SM service, "service application" may involve creating additional messages (for example in case of a SM copy service). This is deemed part of step 9 and not otherwise shown in this diagram.
+
+10) If authorised in step 4, the SMS node continues the SM processing as appropriate for the origination procedures.
+
+NOTE 2: Authorization of SM processing is independent of the authorization for application of a SM service.  
+I.e. If authorization is for SM processing is granted in step 4 but authorization for SM service is refused in step 8 SM processing appropriate for the originating service continues without applying the requested SM service.
+
+### 5.3.3 Credit Control related
+
+#### 5.3.3.1 Triggers for stopping for an SMS Credit Control session
+
+Used in ECUR only, a Debit / Reserve Units Request message to terminate the credit control session is sent to OCS when:
+
+- Validity time for granted quota expires
+- Granted quota runs out (i.e. a successful event has occurred)
+- Abort-Session-Request is received from the OCS
+
+The expiration of the validity time for quota does not require the SMS procedures to be terminated. The CTF shall be configurable as to whether on expiration of validity time, the service should be aborted or not; i.e. whether the stored message should be deleted and no further (re-)delivery attempt should be made.
+
+#### 5.3.3.2 Triggers for providing interim information for a SMS Credit Control session
+
+The provision of interim information for credit control is not used in this release of the specification, due to the use of IEC and ECUR.
+
+# --- 6 Definition of charging information
+
+## 6.1 Data description for SMS offline charging
+
+### 6.1.1 Rf message contents
+
+#### 6.1.1.1 Summary of Offline Charging Message Formats
+
+*Editor's Note: For Further Study.*
+
+#### 6.1.1.2 Structure for the Accounting Message Formats
+
+##### 6.1.1.2.1 Accounting-Request Message
+
+*Editor's Note: For Further Study.*
+
+##### 6.1.1.2.2 Accounting-Answer Message
+
+*Editor's Note: For Further Study.*
+
+### 6.1.2 Ga message contents
+
+*Editor's Note: For Further Study.*
+
+### 6.1.3 CDR description on the B<sub>xx</sub> interface
+
+*Editor's Note: For Further Study.*
+
+## 6.2 Data description for SMS online charging
+
+### 6.2.1 Ro message contents
+
+#### 6.2.1.0 General
+
+The SMS node generates Debit / Reserve Units information that can be transferred from the CTF to the OCF. For this purpose, SMS online charging utilises the *Debit Units and Reserve Units* procedure that is specified in the 3GPP Debit / Reserve Units operation in 3GPP TS 32.299 [4].
+
+The SMS node generates refund information that can be transferred from the CTF to the OCF. For this purpose, it uses REFUND procedure defined in IETF RFC 4006 [12] with extended AVPs.
+
+The *Debit / Reserve Units* procedure employs the *Debit / Reserve Units Request* and *Debit / Reserve Units Response* messages.
+
+The Refund Account procedure employs the Debit Units Request (Refund Account) request and response messages.
+
+Table 6.2.1 describes the use of these messages for SMS online charging.
+
+**Table 6.2.1: SMS Online Charging Messages contents**
+
+| Command-Name                   | Source | Destination |
+|--------------------------------|--------|-------------|
+| Debit / Reserve Units Request  | CTF    | OCS         |
+| Debit / Reserve Units Response | OCS    | CTF         |
+
+This clause 6.2.1 describes the different fields used in the credit control messages.
+
+Detailed descriptions of the fields are provided in 3GPP TS 32.299 [4].
+
+#### 6.2.1.1 Summary of Message Formats
+
+#### 6.2.1.2 Structure for the Credit Control Message Formats
+
+##### 6.2.1.2.1 Debit/Reserve Units Request Message
+
+Table 6.2.1.2.1 illustrates the basic structure of a *Debit / Reserve Units Request* message from SMS node as used for SMS online charging.
+
+**Table 6.2.1.2.1: *Debit / Reserve Units Request* Message Contents for SMS**
+
+| Field                       | Category       | Description                                                                                                                                             |
+|-----------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Session Identifier          | M              | This field identifies the operation session.                                                                                                            |
+| Originator Host             | M              | This field contains the identification of the source point of the operation.                                                                            |
+| Originator Domain           | M              | This field contains the realm of the operation originator.                                                                                              |
+| Destination Domain          | M              | This field contains the realm of the operation destination.                                                                                             |
+| Operation Identifier        | M              | This field is a unique operation identifier.                                                                                                            |
+| Operation Token             | M              | This field contains the service context, i.e. SMS charging.                                                                                             |
+| Operation Type              | M              | This field defines the transfer type: event for immediate event based charging and initial, terminate for ECUR based charging.                          |
+| Operation Number            | M              | This field contains the sequence number of the transferred messages.                                                                                    |
+| Destination Host            | O <sub>C</sub> | This field contains the identification of the destination point of the operation.                                                                       |
+| User Name                   | O <sub>C</sub> | This field contains the identification of the source node.                                                                                              |
+| Origination State           | O <sub>C</sub> | Used for ECUR only.                                                                                                                                     |
+| Origination Timestamp       | O <sub>C</sub> | This field contains the time when the operation is requested.                                                                                           |
+| Subscriber Identifier       | O <sub>M</sub> | This field contains the identification of the subscriber (i.e. MSISDN) that uses the requested service.                                                 |
+| Termination Cause           | O <sub>C</sub> | This field contains information about the cause for termination of a credit control session. Used for terminating credit control sessions in ECUR only. |
+| Requested-Action            | O <sub>C</sub> | This field contains the requested action, used for IEC only.                                                                                            |
+| Multiple Operation          | O <sub>M</sub> | This field indicate the occurrence of multiple operations. Used for ECUR only                                                                           |
+| Multiple Unit Operation     | O <sub>C</sub> | This field contains the parameter for the quota management. Used for ECUR only                                                                          |
+| Subscriber Equipment Number | O <sub>C</sub> | This field contains the identification of the user equipment used to access service. Included if information is made available to the node.             |
+| Proxy Information           | O <sub>C</sub> | This field contains the parameter of the proxy.                                                                                                         |
+| Route Information           | O <sub>C</sub> | This field contains the parameter of the route.                                                                                                         |
+| Service Information         | O <sub>M</sub> | This field holds the SMS specific parameter and is described in clause 6.3.                                                                             |
+
+##### 6.2.1.2.2 Debit / Reserve Units Response Message
+
+Table 6.2.1.2.2 illustrates the basic structure of a Debit / Reserve Units Response message as used for SMS charging. This message is always used by the OCS as specified below, independent of the receiving SMS node and the operation type that is being replied to.
+
+**Table 6.2.1.2.2: Debit / Reserve Units Response Message Contents for SMS**
+
+| Field                          | Category       | Description                                                                                                               |
+|--------------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------|
+| Session Identifier             | M              | This field identifies the operation session.                                                                              |
+| Operation Result               | M              | This field identifies the result of the operation.                                                                        |
+| Originator Host                | M              | This field contains the identification of the source point of the operation.                                              |
+| Originator Domain              | M              | This field contains the realm of the operation originator.                                                                |
+| Operation Identifier           | M              | This field is a unique operation identifier.                                                                              |
+| Operation Type                 | M              | This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
+| Operation Number               | M              | This field contains the sequence number of the transferred messages.                                                      |
+| Operation Failover             | -              | Not used for SMS in 3GPP.                                                                                                 |
+| Multiple Unit Operation        | O <sub>C</sub> | This field contains the parameter for the quota management. Used in IEC for refund purpose and in ECUR.                   |
+| Operation Failure Action       | O <sub>C</sub> | This field defines the resulting operation at the SMS node if a failure has occurred at the OCS for ECUR.                 |
+| Operation Event Failure Action | O <sub>C</sub> | This field defines the resulting operation at the SMS node if a failure has occurred at the OCS for IEC.                  |
+| Redirection Host               | O <sub>C</sub> |                                                                                                                           |
+| Redirection Host Usage         | O <sub>C</sub> |                                                                                                                           |
+| Redirection Cache Time         | O <sub>C</sub> |                                                                                                                           |
+| Proxy Information              | O <sub>C</sub> | This field contains the parameter of the proxy.                                                                           |
+| Route Information              | O <sub>C</sub> | This field contains the parameter of the route.                                                                           |
+| Failed parameter               | O <sub>C</sub> | This field contains missing and/or unsupported parameter that caused the failure.                                         |
+| Service Information            | O <sub>C</sub> | This field contains SMS specific information.                                                                             |
+
+Editor's Note: The mechanism to carry refund information is For Future Study.
+
+## 6.3 SMS charging specific parameters
+
+### 6.3.1 Definition of the SMS charging information
+
+#### 6.3.1.1 SMS charging information assignment for Service-Information
+
+The components in the Service Information that are used for SMS charging can be found in table 6.3.1.1.
+
+**Table 6.3.1.1: Service Information used for SMS Charging**
+
+| Field                                  | Category       | Description                                                                                                                                                                                                                                                                                                                                                 |
+|----------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service Information                    | O <sub>M</sub> | This is a structured field and holds the 3GPP specific parameter as defined in TS 32.299 [50]. For SMS Charging the SMS-Information and selected parameters of MMS Information, PS-Information and IMS information are used.                                                                                                                                |
+| SMS Information                        | O <sub>M</sub> | This is a structured field and holds the SMS specific parameters. The details are defined in table 6.3.1.2.                                                                                                                                                                                                                                                 |
+| MMS Information                        | O <sub>M</sub> | This is a structure field and the following parameters are specific to SMS. The complete structure is defined in 3GPP TS 32.270 [13]                                                                                                                                                                                                                        |
+| Originator Address                     | O <sub>M</sub> | This field holds the address of the originator of the SM. This will typically be an E.164 number or a shortcode. Multiple addresses may be carried if additional information is available, e.g. IMSI and E.164 number.                                                                                                                                      |
+| Submission Time                        | O <sub>C</sub> | This field holds the timestamp of when the submitted SM arrived at the originating SMS Node. The information to populate this field is obtained from the TP-Service-Center-Time-Stamp (TP-SCTS) as defined in 3GPP TS 23.040 [7]. If a refund or retransmission is required, the timestamp carries the timestamp associated with the original submitted SM. |
+| Priority                               | O <sub>C</sub> | This field holds any priority information associated with an SM. Applicable to terminating procedures only. Priority handling is defined in 3GPP TS 23.040 [13]. The value "low" is not applicable.                                                                                                                                                         |
+| Message Id                             | O <sub>M</sub> | This field carries the identity used to identify an SM in the SMS node associated with entity that submitted it. The information to populate this field is obtained from the TP-Message-Reference (TP-MR) as defined in 3GPP TS 23.040 [7].                                                                                                                 |
+| Message Size                           | O <sub>M</sub> | This field carries the length of the user data part of the SM. The information to populate this field is obtained from the TP-User-Data-Length (TP-UDL) as defined in 3GPP TS 23.040 [7]                                                                                                                                                                    |
+| Message Class                          | O <sub>M</sub> | Used as defined in 3GPP TS 32.270 [13]. It is implementation dependent the value selected for a specific transaction.                                                                                                                                                                                                                                       |
+| Delivery Report Requested              | O <sub>C</sub> | This field indicates whether a delivery report is requested by the SM originator. The information to populate this field is obtained from the TP-Status-Report-Request (TP-SRR) as defined in 3GPP TS 23.040 [7]                                                                                                                                            |
+| PS Information                         | O <sub>C</sub> | This is a structured field and the following parameters are specific to SMS. The complete structure is defined in TS 32.251 [11].                                                                                                                                                                                                                           |
+| PDP Address                            | O <sub>C</sub> | This field holds the IP address used by the subscriber for the SMS transaction. Included if the SMS node is the IP-SM-GW.                                                                                                                                                                                                                                   |
+| 3GPP User Location Info                | O <sub>C</sub> | This field holds the information about the location of the subscriber during the SMS transaction.                                                                                                                                                                                                                                                           |
+| 3GPP RAT Type                          | O <sub>C</sub> | This field holds information about the radio access technology used for the SMS transaction.                                                                                                                                                                                                                                                                |
+| IMS Information                        | O <sub>C</sub> | This is a structured field and the following parameters are specific to SMS. The complete structure is defined in TS 32.260 [15].                                                                                                                                                                                                                           |
+| User Session Id                        | O <sub>C</sub> | This field holds the session identifier. For a SIP session the Session-ID contains the SIP Call ID.                                                                                                                                                                                                                                                         |
+| Number Portability routing information | O <sub>C</sub> | This field includes information on number portability after DNS/ENUM request from S-CSCF in the calling user's home network.                                                                                                                                                                                                                                |
+| Carrier Select routing information     | O <sub>C</sub> | This field includes information on carrier select after DNS/ENUM request from S-CSCF in the calling user's home network.                                                                                                                                                                                                                                    |
+
+#### 6.3.1.2 Definition of the SMS Information
+
+The components in the SMS Information that are used for SMS charging can be found in table 6.3.1.2.
+
+**Table 6.3.1.2: SMS Information used for SMS Charging**
+
+| Field                       | Category       | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|-----------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SMS Node                    | O <sub>M</sub> | Identifies the SMS Node as IP-SM-GW or SMS Router or a combined IP-SM-GW / SMS Router or as SMS-SC.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| SM Client Address           | O <sub>M</sub> | This field holds the address of the SMS node to which the charging system is connected to. This may be the same as the SMSC Address field.                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Originator SCCP Address     | O <sub>C</sub> | This field holds the SCCP calling address used to receive the SM at the SMS node. Only present if SMSIP is not used for the inward connection.                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Originator Received Address | O <sub>C</sub> | This field holds the original, unmodified address of the originator of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. This will typically be an E.164 number or a shortcode. Multiple addresses may be carried if additional information is available, e.g. IMSI and E.164 number.                                                                                                                                                                                                                            |
+| Recipient Info              | O <sub>C</sub> | This field holds recipient information for the SM. Each occurrence of this field denotes a different recipient.<br>Multiple occurrences of this field are allowed in case<br>- multiple recipients are associated with the charged event and<br>- all other charging information is identical for all recipients.<br>In case the SM contains a Delivery Report, as described in subclause 5.3.2.3, this field identifies the recipient of this Delivery Report. This recipient information must correspond to the originator information of the message that triggered this Delivery Report. (Note 2) |
+| Recipient Address           | O <sub>C</sub> | This field holds the address of the recipient of the SM. This will typically be an E.164 number or a shortcode. Multiple addresses may be carried if additional information is available, e.g. shortcode or IMSI and E.164 number.                                                                                                                                                                                                                                                                                                                                                                    |
+| Recipient Received Address  | O <sub>C</sub> | This field holds the original, unmodified address of the recipient of the SM, as received by the SMS node, in case address manipulation (such as number plan corrections) have been applied in the SMS node. This will typically be an E.164 number or a shortcode. Multiple addresses may be carried if additional information is available, e.g. shortcode or IMSI and E.164 number.                                                                                                                                                                                                                |
+| Recipient SCCP Address      | O <sub>C</sub> | This field holds the SCCP called address used by the SMS node to onward deliver the SM. Only present if SMSIP is not used for the outward connection.                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| SM Destination Interface    | O <sub>M</sub> | This is a structured field containing information describing the interface on which the SM is to be delivered (i.e. the next hop)<br>In case the charging event is for person to application messaging or for application to application messaging (see subclause 5.1.1) this field holds the identification of the application. (See also Note 3)                                                                                                                                                                                                                                                    |
+| SM Protocol Id              | O <sub>C</sub> | This field holds the TP-PROTOCOL-ID (TP-PID) as defined in 3GPP TS 23.040 [7]. This field relates to the recipient when charging MT SMS messages as specified in 32.240 [1].                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| SMSC Address                | O <sub>M</sub> | This field holds the address of the SMSC to which the originating or terminating SM is directed to.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| SM Data Coding Scheme       | O <sub>M</sub> | This field holds the data coding scheme used within the SM. The information to populate this field is obtained from TP-DCS header.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|                             |                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| SM Message Type             | O <sub>M</sub> | This field identifies the message that triggered the generation of charging information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| SM Originator Interface     | O <sub>M</sub> | This is a structured field containing information describing the interface on which the SM was received by the SMS node (i.e. the previous hop)<br>In case the charging event is for application to person messaging or for application to application messaging (see subclause 5.1.1) this field holds the identification of the application. (See also Note 3)                                                                                                                                                                                                                                      |
+| SM Protocol Id              | O <sub>C</sub> | This field holds the TP-PROTOCOL-ID (TP-PID) as defined in 3GPP TS 23.040 [7] This field relates to the originator when charging MO SMS messages as specified in 32.240 [1].                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| SM Reply Path Requested     | O <sub>C</sub> | This field carries an indication of whether a reply SM to an original SM shall follow the same path as identified by the TP-Reply-Path (TP-RP) flag.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| SM User Data Header         | O <sub>C</sub> | This field carries the user data header extracted from the user data of the SM. The user data header (TP-UDH) is specified in 3GPP TS 23.040 [7]                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| SM Status                   | O <sub>C</sub> | This field holds the information from the TP-Status field in a Status-Report TPDU. This information is only applicable to delivery report charging procedures or where ECUR is employed.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| SM Discharge Time           | O <sub>C</sub> | This field holds the time associated with the event being reported in the SM Status field. This information is only applicable to delivery report charging procedures.                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Number of Messages Sent     | O <sub>C</sub> | Indicates the number of SMSs sent by the IMS application if applicable.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+|                 |    |                                                                                                                                                  |
+|-----------------|----|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| SM Service Type | Oc | This field indicates the type of SM service that caused the charging interaction. It is only applicable for SM supplementary service procedures. |
+|-----------------|----|--------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE 1: The case of multi-destinations of SMS refers to SMS and Internet Electronic Mail interworking as specified in subclause 3.8 of TS 23.040 [7]
+
+NOTE 2: Implementations vary as to the originator address that is presented to an end user for a Delivery Report. Typically the originator address either identifies the SMS node that generated the Delivery Report or the originator address of a Delivery Report identifies the recipient of the original message that triggered this Report. It is expected that the charging event contains the information presented to the end user.
+
+NOTE 3: There is a distinction between short numbers (as conveyed in originator and/or recipient address fields) and the identification of SM applications (as carried in SM Originator Interface and/or SM Destination Interface). Short numbers are used by end users to address a service of an applications. Multiple short numbers may map to one application capable of multiple services. The identification of an application is how an application is known to the operator.
+
+### 6.3.2 Formal parameter description
+
+#### 6.3.2.1 SMS charging information for CDRs
+
+*Editor's Note: For Future Study.*
+
+#### 6.3.2.2 SMS charging information for charging events
+
+*Editor's Note: For Future Study.*
+
+# Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                                            |      |       |        |  |
+|----------------|-------|-----------|------|-----|----------------------------------------------------------------------------|------|-------|--------|--|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                            | Ca t | Old   | New    |  |
+| Sep 2007       | SP-37 | SP-070620 | --   | --  | Submitted to TSG SA#37 for Information                                     | --   | 1.0.0 |        |  |
+| Dec 2007       | SP-38 | SP-070748 | --   | --  | Submitted to TSG SA#38 for Approval                                        | --   | 2.0.0 | 8.0.0  |  |
+| Dec 2007       | --    | --        | --   | --  | editHelp: the figures are now visible in normal view                       | --   | 8.0.0 | 8.0.1  |  |
+| Mar 2008       | SP-39 | SP-080074 | 0001 | --  | Correction on Service Information for SMS Charging                         | F    | 8.0.1 | 8.1.0  |  |
+| Jun 2008       | SP-40 | SP-080330 | 0002 | --  | Support of Number Portability and Carrier Selection in SMS Online Charging | B    | 8.1.0 | 8.2.0  |  |
+| Sep 2008       | SP-41 | SP-081216 | 0003 | --  | Multiple SMS destination – Alignment with TS 23.040                        | C    | 8.2.0 | 8.3.0  |  |
+| Sep 2008       | SP-41 | SP-081224 | 0004 | --  | Introduce Online Charging from SMS-SC into 3GPP TS 32.274                  | B    | 8.2.0 | 8.3.0  |  |
+| Dec 2008       | SP-42 | SP-080706 | 0005 | --  | Correction on Multiple Unit Operation category                             | F    | 8.3.0 | 8.4.0  |  |
+| Dec 2008       | SP-42 | SP-080706 | 0006 | --  | Add SMS-SC as SMS node type                                                | B    | 8.3.0 | 8.4.0  |  |
+| Dec 2008       | SP-42 | SP-080706 | 0007 | --  | Additional Address Info for SMS charging                                   | B    | 8.3.0 | 8.4.0  |  |
+| Dec 2008       | SP-42 | SP-080706 | 0008 | --  | Add charging of SMS services to 32.274                                     | B    | 8.3.0 | 8.4.0  |  |
+| Mar 2009       | SP-43 | SP-090045 | 0009 | --  | SMS IE structure alignment                                                 | F    | 8.4.0 | 8.5.0  |  |
+| Jun 2009       | SP-44 | SP-090293 | 0010 | --  | Clarification of "Termination charge" and application addressing           | F    | 8.5.0 | 8.6.0  |  |
+| Sep 2009       | SP-45 | SP-090536 | 0011 | --  | IE usage for Delivery Reports and Application Identifiers                  | F    | 8.6.0 | 8.7.0  |  |
+| Dec 2009       | -     | -         | -    | -   | Update to Rel-9 version (MCC)                                              | -    | 8.7.0 | 9.0.0  |  |
+| Mar 2011       | -     | -         | -    | -   | Update to Rel-10 version (MCC)                                             | -    | 9.0.0 | 10.0.0 |  |
+

marked/Rel-10/32_series/32295/raw.md

@@ -0,0 +1,1201 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                              |           |
+|------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                               | 4         |
+| 1 Scope.....                                                                 | 5         |
+| 2 References.....                                                            | 5         |
+| 3 Definitions, symbols and abbreviations .....                               | 6         |
+| 3.1 Definitions.....                                                         | 6         |
+| 3.2 Abbreviations .....                                                      | 8         |
+| 3.3 Symbols.....                                                             | 9         |
+| 4 Architecture Considerations.....                                           | 9         |
+| 4.1 High level architecture .....                                            | 9         |
+| 5 Transfer principles and scenarios.....                                     | 10        |
+| 5.1 Transfer principles.....                                                 | 10        |
+| 5.1.1 Charging related transfer requirements .....                           | 10        |
+| 5.1.2 CDR Transport by GTP' .....                                            | 10        |
+| 5.1.2.1 CDF - CGF communication.....                                         | 11        |
+| 5.1.2.2 CGF - CGF communication.....                                         | 11        |
+| 5.1.3 Port usage .....                                                       | 12        |
+| 5.2 GTP' transfer scenarios .....                                            | 12        |
+| 5.2.1 Basic principles .....                                                 | 12        |
+| 5.2.2 GTP' messaging cases.....                                              | 12        |
+| 5.2.2.1 The normal CDR packet transfer.....                                  | 13        |
+| 5.2.2.2 The CDF-CGF connection breaks before a successful CDR reception..... | 14        |
+| 5.2.2.3 The CDF-CGF connection breaks after a successful CDR reception.....  | 16        |
+| 5.2.2.4 CGF redundancy mechanism.....                                        | 17        |
+| 6 Data description for the transfer.....                                     | 20        |
+| 6.1 The GTP' charging protocol .....                                         | 20        |
+| 6.1.1 Usage of GTP Header in charging.....                                   | 20        |
+| 6.1.2 Information Elements (IEs) .....                                       | 20        |
+| 6.2 GTP' Message Types.....                                                  | 21        |
+| 6.2.1 List of all GTP' message types .....                                   | 21        |
+| 6.2.2 Reused GTP message types.....                                          | 22        |
+| 6.2.3 GTP message type modifications, implied by GTP'.....                   | 23        |
+| 6.2.4 GTP' message types.....                                                | 23        |
+| 6.2.4.1 Node Alive Request.....                                              | 23        |
+| 6.2.4.2 Node Alive Response.....                                             | 23        |
+| 6.2.4.3 Redirection Request.....                                             | 23        |
+| 6.2.4.4 Redirection Response .....                                           | 25        |
+| 6.2.4.5 Data Record Transfer Request.....                                    | 25        |
+| 6.2.4.5.1 Information Elements in Data Record Transfer Request .....         | 25        |
+| 6.2.4.5.2 Packet Transfer Command IE .....                                   | 25        |
+| 6.2.4.5.3 Data Record Packet IE .....                                        | 27        |
+| 6.2.4.5.4 Sequence Numbers of Released Packets IE .....                      | 27        |
+| 6.2.4.5.5 Sequence Numbers of Cancelled Packets IE.....                      | 28        |
+| 6.2.4.5.6 Private Extension IE.....                                          | 28        |
+| 6.2.4.6 Data Record Transfer Response .....                                  | 28        |
+| 6.3 Data Record Format in GTP' .....                                         | 29        |
+| 6.3.1 Standard Data Record Format .....                                      | 29        |
+| 6.3.2 Private Data Record Formats.....                                       | 29        |
+| 6.4 Data Record Format Version for CDRs.....                                 | 30        |
+| <b>Annex A (informative): Bibliography .....</b>                             | <b>31</b> |
+| Annex B (informative): Change history.....                                   | 32        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# --- 1 Scope
+
+The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks (GSM/UMTS/EPS). The 3GPP core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain / subsystem / service (offline charging),
+- the content of real-time charging messages per domain / subsystem / service (online charging);
+- the functionality of online and offline charging for those domains / subsystems / services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events)
+
+The complete document structure for these TSs is defined in TS 32.240 [1].
+
+The present document specifies the transaction based mechanism for the near real time transfer of CDRs within the network.
+
+The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240 [1];
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51];
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the post-processing system or a mediation device) is specified in TS 32.297 [52];
+
+The 3GPP Diameter application that is used for offline and online charging is specified in TS 32.299 [50].
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP domains services, or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [101].
+
+# --- 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.240: "Telecommunication management; Charging management; Charging Architecture and Principles".
+- [2]-[9] Void.
+- [10] 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain charging".
+- [11] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
+
+|             |                                                                                                                           |
+|-------------|---------------------------------------------------------------------------------------------------------------------------|
+| [12]-[29]   | Void.                                                                                                                     |
+| [30]        | 3GPP TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging".         |
+| [31]-[49]   | Void.                                                                                                                     |
+| [50]        | 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging application".                       |
+| [51]        | 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) parameter description".    |
+| [52]        | 3GPP TS 32.297: "Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer". |
+| [53]-[99]   | Void.                                                                                                                     |
+| [100]       | TR 21.905: "Vocabulary for 3GPP Specifications".                                                                          |
+| [101]       | 3GPP TS 22.115 "Service aspects; Charging and billing"                                                                    |
+| [102]-[199] | Void.                                                                                                                     |
+| [200]       | 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".     |
+| [201]       | 3GPP TS 29.274: "Evolved GPRS Tunnelling Protocol for Control Plane (GTPv2-C); Stage 3".                                  |
+| [202]-[299] | Void.                                                                                                                     |
+| [300]-[399] | Void.                                                                                                                     |
+| [400-403]   | Void.                                                                                                                     |
+| [404]       | IETF RFC 768 (1980): "User Datagram Protocol" (STD 6).                                                                    |
+| [405]       | IETF RFC 793 (1981): "Transmission Control Protocol" (STD 7).                                                             |
+| [406]       | IETF RFC 791 (1981): "Internet Protocol" (STD 5).                                                                         |
+| [407]       | IETF RFC 792 (1981): "Internet Control Message Protocol" (STD 5).                                                         |
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TR 21.905 [50], 3GPP TS 32.240 [1], and the following apply:
+
+**2G- / 3G-:** prefixes 2G- and 3G- refers to functionality that supports only GSM or UMTS, respectively, e.g. 2G-CDF refers only to the GSM functionality of an CDF.
+
+**accounting:** process of apportioning charges between the Home Environment, Serving Network and User.
+
+**billing:** function whereby CDRs generated by the charging function are transformed into bills requiring payment.
+
+**Billing Domain:** Part of the operator network, which is outside the core network, that receives and processes CDR files from the core network charging functions. It includes functions that can provide billing mediation and billing other (e.g. statistical) end applications. It is only applicable to offline charging (see "Online Charging System" for equivalent functionality in online charging).
+
+**CDR field Categories:** the CDR fields are defined in the present document. They are divided into the following categories:
+
+- **Mandatory (M):** field that shall be present in the CDR.
+- **Conditional (C):** field that shall be present in a CDR if certain conditions are met.
+- **Operator Provisionable: Mandatory (O<sub>M</sub>):** A field that operators have provisioned to be included in the CDR for all conditions.
+- **Operator Provisionable: Conditional (O<sub>C</sub>):** A field that operators have provisioned to be included in the CDR if certain conditions are met.
+
+**chargeable event:** activity utilizing telecommunications network infrastructure and related services for:
+
+- user to user communication (e.g. a single call, a data communication session or a short message); or
+- user to network communication (e.g. service profile administration); or
+- inter-network communication (e.g. transferring calls, signalling, or short messages); or
+- mobility (e.g. roaming or inter-system handover); and
+- that the network operator wants to charge for.
+
+**charged party:** user involved in a chargeable event who has to pay parts or the whole charges of the chargeable event, or a third party paying the charges caused by one or all users involved in the chargeable event, or a network operator.
+
+**charging:** function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed.
+
+**Charging Data Record (CDR):** A formatted collection of information about a chargeable event (e.g. time of call set-up, duration of the call, amount of data transferred, etc) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event a separate CDR shall be generated, i.e. more than one CDR may be generated for a single chargeable event, e.g. because of its long duration, or because more than one charged party is to be charged.
+
+**charging function:** entity inside the core network domain, subsystem or service that is involved in charging for that domain, subsystem or service.
+
+**circuit switched domain:** domain within GSM / UMTS in which information is transferred in circuit mode.
+
+**domain:** part of a communication network that provides services using a certain technology.
+
+**GPRS:** Packet Services for GSM and UMTS systems.
+
+**GTP':** GPRS protocol, used for CDR transport. It is derived from GTP with enhancements to improve transport reliability necessary for CDRs. NOTE: This protocol is not used for tunnelling.
+
+**GSM only:** qualifier indicating that this clause or paragraph applies only to a GSM system. For multi-system cases this is determined by the current serving radio access network.
+
+**inter-system change:** change of radio access between different radio access technologies such as GSM and UMTS.
+
+**in GSM,....:** qualifier indicating that this paragraph applies only to GSM System.
+
+**in UMTS,....:** qualifier indicating that this paragraph applies only to UMTS System.
+
+**middle tier (charging) TS:** used for the 3GPP charging TSs that specify the domain / subsystem / service specific, online and offline, charging functionality. These are all the TSs in the numbering range from 3GPP TS 32.250 [10] to 3GPP TS 32.27x [3x], e.g. 3GPP TS 32.250 [10] for the CS domain, or 3GPP TS 32.270 [30] for the MMS service. Currently, there is only one "tier 1" TS in 3GPP, which is the TS 32.240 [1] that specifies the charging architecture and principles. Finally, there are a number of top tier TSs in the 32.29x numbering range ([50] ff) that specify common charging aspects such as parameter definitions, encoding rules, the common BD interface or common charging applications.
+
+**near real time:** near real time charging and billing information is to be generated, processed, and transported to a desired conclusion in less than 1 minute.
+
+**observed IMEI ticket:** record used to describe an EIR relevant event e.g. a blacklisted IMEI.
+
+**offline charging:** charging mechanism where charging information **does not** affect, in real-time, the service rendered.
+
+**online charging:** charging mechanism where charging information can affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with session/service control is required.
+
+**Online Charging System:** the entity that performs real-time credit control. Its functionality includes transaction handling, rating, online correlation and management of subscriber accounts/balances.
+
+**packet switched domain:** domain in which data is transferred between core network elements.
+
+**Real-time:** real time charging and billing information is to be generated, processed, and transported to a desired conclusion in less than 1 second.
+
+**subscriber:** A subscriber is an entity (associated with one or more users) that is engaged in a Subscription with a service provider. The subscriber is allowed to subscribe and unsubscribe services, to register a user or a list of users authorised to enjoy these services, and also to set the limits relative to the use that associated users make of these services.
+
+**UMTS only:** qualifier indicating that this clause or paragraph applies only to a UMTS system. For multi-system cases this is determined by the current serving radio access network.
+
+**user:** An entity, not part of the 3GPP System, that uses network resources by means of a subscription. The user may or may not be identical to the subscriber holding that subscription.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [50], 3GPP TS 32.240 [1] and the following apply:
+
+|           |                                                    |
+|-----------|----------------------------------------------------|
+| 3G        | 3 <sup>rd</sup> Generation                         |
+| 3GPP      | 3 <sup>rd</sup> Generation Partnership Project     |
+| AS        | Application Server                                 |
+| ASN.1     | Abstract Syntax Notation One                       |
+| BD        | Billing Domain                                     |
+| CDF       | Charging Data Function                             |
+| CDR       | Charging Data Record                               |
+| CG        | Charging Gateway                                   |
+| CGF       | Charging Gateway Function                          |
+| CS        | Circuit SwitchedDRP Data Record Packet             |
+| EPS       | Evolved Packet System                              |
+| E-UTRAN   | Evolved Universal Terrestrial Radio Access Network |
+| GPRS      | General Packet Radio Service                       |
+| GTP       | GPRS Tunnelling Protocol                           |
+| GTPv2-C   | GTP version 2 – Control Plane                      |
+| GTP'      | GPRS protocol, used for CDR transport              |
+| IE        | Information Element                                |
+| IP        | Internet Protocol                                  |
+| IPv4      | Internet Protocol version 4                        |
+| IPv6      | Internet Protocol version 6                        |
+| NE        | Network Element                                    |
+| OCS       | Online Charging System                             |
+| PDN       | Packet Data Network                                |
+| PS        | Packet-Switched                                    |
+| PT        | Protocol Type (Field in GTP' header)               |
+| S-SMO-CDR | SGSN Short Message Mobile Originated - CDR         |
+| TAP       | Transferred Account Procedure                      |
+| TLV       | Type, Length, Value (GTP header format)            |
+| TV        | Type, Value                                        |
+
+## 3.3 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|    |                                                                                               |
+|----|-----------------------------------------------------------------------------------------------|
+| Bx | The reference point between any (generic) 3G domain, subsystem or service CGF and the BD.     |
+| Ga | Reference point between a CDF and the CGF for CDR transfer.                                   |
+| Rf | Reference Point between the CTF within a 3G network element and the CDF for offline charging. |
+
+# 4 Architecture Considerations
+
+## 4.1 High level architecture
+
+The Ga is the reference point from the Charging Data Function (CDF) to the Charging Gateway Function (CGF), which is intended for the transport of Charging Data Records (CDRs).
+
+By definition, dealing with CDRs only implies that Ga is solely related to offline charging.
+
+The following figure 4.1 depicts the position of the Ga reference point within the overall 3GPP offline charging architecture.
+
+![Figure 4.1: Logical ubiquitous offline charging architecture. The diagram shows a 3GPP network (grey box) containing three domains: CN Domain (yellow), Service nodes (orange), and Sub-system (purple). Each domain contains a Charging Trigger Function (CTF, pink vertical bar) and a Charging Data Function (CDF, green vertical bar). Arrows labeled Rf point from the CTF to the CDF within each domain. Arrows labeled Ga point from the CDF in the Service nodes and Sub-system to a Charging Gateway Function (CGF, orange vertical bar). An arrow labeled Bx points from the CGF to the Billing Domain (blue box).](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg)
+
+Figure 4.1: Logical ubiquitous offline charging architecture. The diagram shows a 3GPP network (grey box) containing three domains: CN Domain (yellow), Service nodes (orange), and Sub-system (purple). Each domain contains a Charging Trigger Function (CTF, pink vertical bar) and a Charging Data Function (CDF, green vertical bar). Arrows labeled Rf point from the CTF to the CDF within each domain. Arrows labeled Ga point from the CDF in the Service nodes and Sub-system to a Charging Gateway Function (CGF, orange vertical bar). An arrow labeled Bx points from the CGF to the Billing Domain (blue box).
+
+|             |                                                                                              |
+|-------------|----------------------------------------------------------------------------------------------|
+| <b>CTF:</b> | <b>Charging Trigger Function</b>                                                             |
+| <b>CDF:</b> | <b>Charging Data Function</b>                                                                |
+| <b>CGF:</b> | <b>Charging Gateway Function</b>                                                             |
+| <b>BD:</b>  | <b>Billing Domain.</b> This may also be a billing mediation device / post-processing system. |
+
+**Figure 4.1: Logical ubiquitous offline charging architecture**
+
+As illustrated in the above figure 4.1, the CDF in each network domain, service or subsystem is relevant for the network side of the Ga reference point. Different mappings of the ubiquitous offline charging functions, CDF and CGF, onto physical implementations are possible. Further details of the configuration refer to 3GPP TS 32.240 [1]. Details of the implementation options per domain / subsystem / service (usually a subset of the overall possible variants described above) are specified in the respective middle tier TS, e.g. for EPC Charging in TS 32.251[11].
+
+The transport protocol associated to the Ga reference point, providing functions for transfer of CDRs from CDF to CGF, is **GTP'** (because of its derivation from the GTP protocol as specified in TS 29.060[200]).
+
+# --- 5 Transfer principles and scenarios
+
+## 5.1 Transfer principles
+
+The GTP' protocol is optional, and is used for CDR transport between the CDFs and the CGF.
+
+### 5.1.1 Charging related transfer requirements
+
+Each CDF will have an O&M configurable address list of CGFs (Charging Gateways) to which it can send its CDRs. The list will be organized in CGF address priority order. If the primary CGF is not available (e.g. out of service), then the CDF shall send the CDRs to the secondary CGF and so on.
+
+Each CDR generating function will only send the records to the CGF(s) of the same PLMN, not to CGF(s) located in other PLMNs.
+
+Each CGF in the PLMN may know of other CGFs' network addresses (e.g., for redundancy reasons, to be able to recommend another CGF address). This is achieved by O&M configuration facilities that will enable each CGF to have a configurable list of peer CGF addresses.
+
+### 5.1.2 CDR Transport by GTP'
+
+GTP' has been designed to deliver the CDR(s) from the CDF, which generates charging data records (CDRs) to the CGF(s). This protocol is required if the CGF resides outside the CDFs. It utilizes some aspects of GTP (defined in TS 29.060 [200]), which is used for packet data tunnelling in the backbone network.
+
+GTP' operates on the Ga interface and does not imply the use of any specific backbone network.
+
+GTP' performs the following functions:
+
+- CDR transfer between the CDF and the CGF.
+- Redirection of CDRs to another CGF.
+- Detect communication failures between the communicating peers, using echo messaging.
+- Advertise to peers about its CDR transfer capability (e.g., after a period of service downtime).
+- Prevents duplicate CDRs that might arise during redundancy operations.  
+If so configured, the CDR duplication prevention function may also be carried out by marking potentially duplicated CDR packets, and, delegating the final duplicate deletion task to a CGF or the Billing Domain (instead of handling the possible duplicates solely by GTP' messaging).
+
+#### 5.1.2.1 CDF - CGF communication
+
+As illustrated in Figure 5.1, the CDF - CGF communications are carried out using GTP' over UDP/TCP and IP.
+
+![Diagram showing protocol layers between CDF and CGF for CDRs. The diagram consists of two vertical stacks of five boxes representing protocol layers. The left stack is labeled 'CDF' at the bottom and the right stack is labeled 'CGF' at the bottom. Above each stack is the label 'CDRs' with a horizontal arrow pointing from the left 'CDRs' to the right 'CDRs'. The layers in each stack, from top to bottom, are: GTP', UDP/TCP, IP, L2, and L1. Horizontal lines connect corresponding layers between the CDF and CGF stacks.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+Diagram illustrating the protocol layers between the CDF and the CGF for CDRs. The diagram shows two stacks of protocol layers. The left stack is labeled CDF and the right stack is labeled CGF. Above each stack is the label CDRs with a horizontal arrow pointing from the left CDRs to the right CDRs. The layers in each stack, from top to bottom, are: GTP', UDP/TCP, IP, L2, and L1. Horizontal lines connect corresponding layers between the CDF and CGF stacks.
+
+Diagram showing protocol layers between CDF and CGF for CDRs. The diagram consists of two vertical stacks of five boxes representing protocol layers. The left stack is labeled 'CDF' at the bottom and the right stack is labeled 'CGF' at the bottom. Above each stack is the label 'CDRs' with a horizontal arrow pointing from the left 'CDRs' to the right 'CDRs'. The layers in each stack, from top to bottom, are: GTP', UDP/TCP, IP, L2, and L1. Horizontal lines connect corresponding layers between the CDF and CGF stacks.
+
+**Figure 5.1: Protocol layers between the CDF and the CGF**
+
+#### 5.1.2.2 CGF - CGF communication
+
+If necessary, CGF to CGF communications are carried out using GTP' over UDP/TCP and IP. This is illustrated in Figure 5.2.
+
+![Diagram showing protocol layers between two CGFs for CDRs. The diagram consists of two vertical stacks of five boxes representing protocol layers. The left stack is labeled 'CGF' at the bottom and the right stack is labeled 'CGF' at the bottom. Above each stack is the label 'CDRs' with a horizontal arrow pointing from the left 'CDRs' to the right 'CDRs'. The layers in each stack, from top to bottom, are: GTP', UDP/TCP, IP, L2, and L1. Horizontal lines connect corresponding layers between the two CGF stacks.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg)
+
+Diagram illustrating the protocol layers between two CGFs for CDRs. The diagram shows two stacks of protocol layers. The left stack is labeled CGF and the right stack is labeled CGF. Above each stack is the label CDRs with a horizontal arrow pointing from the left CDRs to the right CDRs. The layers in each stack, from top to bottom, are: GTP', UDP/TCP, IP, L2, and L1. Horizontal lines connect corresponding layers between the two CGF stacks.
+
+Diagram showing protocol layers between two CGFs for CDRs. The diagram consists of two vertical stacks of five boxes representing protocol layers. The left stack is labeled 'CGF' at the bottom and the right stack is labeled 'CGF' at the bottom. Above each stack is the label 'CDRs' with a horizontal arrow pointing from the left 'CDRs' to the right 'CDRs'. The layers in each stack, from top to bottom, are: GTP', UDP/TCP, IP, L2, and L1. Horizontal lines connect corresponding layers between the two CGF stacks.
+
+**Figure 5.2: Protocol layers between CGFs**
+
+### 5.1.3 Port usage
+
+Transporting the CDRs from the CDFs to the CGF over the Ga reference point may facilitate charging. The Path Protocol may be UDP (compliant with STD 0006[404]) or TCP (compliant with STD 0007[405]) over IP.
+
+- UDP as the Path Protocol
+
+Ports for signalling the request messages:
+
+- The UDP Destination Port may be the server port number 3386 which has been reserved for GTP'. Alternatively another port can be used, which has been configured by O&M, except Port Number 2123 which is used by GTPv2-C.
+- The UDP Source Port is a locally allocated port number at the sending network element.
+
+NOTE: UDP Source Port number should be different than UDP Source Port number allocated to GTPv2 (see TS 29.274 [201]).
+
+Ports for signalling the response messages:
+
+- The UDP Destination Port value shall be the value of the Source Port of the corresponding request message.
+- The UDP Source Port shall be the value from the Destination Port of the corresponding request message.
+
+- TCP as Path Protocol
+
+The TCP Destination Port may be the server port number 3386, which has been reserved for G-PDUs. Alternatively, another port may be used as configured by O&M. Extra implementation-specific destination ports are possible but all CGFs shall support the server port number.
+
+The TCP Source Port is a random port, locally assigned at the sending network element.
+
+- Network layer and lower layers
+
+Beneath the Path Protocol there is the network IP layer, which shall be the Internet Protocol (IP) compliant with STD 0005(see [406] and [407]). Beneath the network IP layer are the L2 and L1 layers, which are not specified, in the present document.
+
+## 5.2 GTP' transfer scenarios
+
+### 5.2.1 Basic principles
+
+Each function (i.e. CDF and CGF) that supports the GTP' shall be capable of handling or responding with a "Service/Version not supported" message if that function is configured to be addressed by another peer function.
+
+### 5.2.2 GTP' messaging cases
+
+The following example cases represent the three different key *Data Record Transfer Request/Response* messaging related CDR handling schemes. Cases (2) and (3) represent situations involving the redundancy mechanism.
+
+- (1) The normal CDR packet transfer:
+
+The CDF sends successfully a CDR packet to the CGF, and since the CDF gets a response (Request Accepted) for the Data Record Transfer Request, there is no need to use the CGF redundancy mechanism and redirect the CDR packet traffic flow to an other CGF.
+
+- (2) The CDF-CGF connection breaks before a successful CDR reception:
+
+In this case the CDR packet sent by the CDF is lost before it is received by the CGF. (The loss might be caused by a link failure or e.g. a major CGF failure.)
+
+- (3) The CDF-CGF connection breaks after a successful CDR reception:
+
+In this case the CDR sent by the CDF is received correctly by the CGF and moved to its non-volatile memory (or even to the next NE in the communication chain). Anyhow, the CDF-CGF communication stops working, in this example case, before the CDF gets the positive response (Data Record Transfer Response: Request Accepted) which would acknowledge that the CDR packet was successfully received by CGF.
+
+#### (4) CGF redundancy mechanism
+
+An overview on the mechanism, involved in cases (2) and (3), preventing duplicated CDR packets to enter a BD.
+
+The next four clauses describe in more detail each of these key *Data Record Transfer Request / Response* messaging schemes.
+
+#### 5.2.2.1 The normal CDR packet transfer
+
+Figure 5.3 represents the default mode of CDR transfer from the CDR generating functions (CDFs) to the CDR collecting functions (CGFs).
+
+![Sequence diagram of normal CDR transfer process between a CDF and CGF. Lifelines: CDF, CGF's volatile memory, Non-volatile CGF memory. Steps: 1. CDF sends 'Data Record Transfer Request: Send Data Record Packet' to CGF's volatile memory. 2. CGF's volatile memory stores CDRs in non-volatile CGF memory. 3. CGF's volatile memory sends 'Data Record Transfer Response: Request Accepted' back to CDF. 4. CDF deletes successfully sent CDRs from its buffers. Ellipses indicate further steps.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CDF
+    participant CGF as CGF's volatile memory
+    participant NVM as Non-volatile CGF memory
+    Note left of CDF: 4. < Successfully sent CDRs are deleted from the CDF buffers >
+    CDF->>CGF: 1. Data Record Transfer Request: Send Data Record Packet
+    CGF->>NVM: 2. CDRs are stored in a secure way
+    CGF->>CDF: 3. Data Record Transfer Response: Request Accepted
+    Note right of CGF: ...
+    Note right of NVM: ...
+  
+```
+
+Sequence diagram of normal CDR transfer process between a CDF and CGF. Lifelines: CDF, CGF's volatile memory, Non-volatile CGF memory. Steps: 1. CDF sends 'Data Record Transfer Request: Send Data Record Packet' to CGF's volatile memory. 2. CGF's volatile memory stores CDRs in non-volatile CGF memory. 3. CGF's volatile memory sends 'Data Record Transfer Response: Request Accepted' back to CDF. 4. CDF deletes successfully sent CDRs from its buffers. Ellipses indicate further steps.
+
+**Figure 5.3: A normal CDR transfer process between a CDF and CGF**
+
+- 1) The CDR generating entity sends CDR(s) in a packet to CGF (that is the current primary Charging Gateway Functionality for the specific CDF, "CGF1"). The sending is performed by using the *Data Record Transfer Request* message, with the *Packet Transfer Command* IE having the value "Send Data Record Packet".
+- 2) The CGF opens the received message and stores the packet contents in a safe way (to e.g. a redundant RAM memory unit or a mirrored non-volatile memory or even to another node).
+- 3) The CDR receiving entity (CGF) sends confirmation of the successful packet reception to the CDF (CDF). The confirmation is performed by using the *Data Record Transfer Response* message, with the **Cause** value being "Request Accepted".
+- 4) After the positive response "Request Accepted" is received by the CDF, it may delete the successfully sent CDRs from its send buffer.
+
+The general principle of GTP' to retransmit the request if the response has not been received within a configurable time-out limit, is also followed here in point 1). The maximum amount of retries is a configurable value.
+
+#### 5.2.2.2 The CDF-CGF connection breaks before a successful CDR reception
+
+Figure 5.4 describes the exceptional case when the CDR transfer from a CDR generating entity (CDF) to the primary CDR packet collecting entity (CGF1) fails in a way that the CGF1 is not able to store the CDR packet sent by the CDF. (The reason for the failure in packet transfer may be e.g. a link failure between the CDF and CGF1, or a capacity exhausting error in the storage device of CGF1, or a general CGF1 system failure or CGF1 maintenance break.)
+
+![Sequence diagram illustrating the CDR transfer process when the primary CGF1 fails. The diagram shows interactions between CDF, CGF1, CGF2, and a CDR post-processing system. The CDF sends a request to CGF1, which fails. The CDF then resends the request to CGF2, which succeeds. The CDF receives a response from CGF2, deletes its own buffers, and then sends a Node Alive request to CGF1. CGF1 responds. Finally, the CDF sends an empty request to CGF1, which is accepted, and then a release request to CGF2, which is also accepted.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CDF
+    participant CGF1
+    participant CGF2
+    participant CDR_post_processing_system as CDR post-processing system
+
+    Note left of CDF: 1. Data Record Transfer Request: Send Data Record Packet
+    CDF->>CGF1: 
+    Note right of CGF1: 2. < CDRs not stored to non-volatile memory nor sent to postprocessing >
+    Note left of CDF: 3. < No positive response to CDF even to resent requests >
+    Note left of CDF: 4. Data Record Transfer Request: Send possibly duplicated Data Record Packet
+    CDF->>CGF2: 
+    Note right of CGF2: 5. < CGF2 stores the CDR packet contents to its buffer for pot. dupl. packets >
+    Note left of CDF: 6. Data Record Transfer Response: Request Accepted
+    CDF->>CGF2: 
+    Note left of CDF: 7. < CDRs are deleted from CDF buffers >
+    Note left of CDF: 8. Node Alive Request
+    CDF->>CGF1: 
+    Note right of CGF1: 9. Node Alive Response: Request Accepted
+    Note left of CDF: 10. Data Record Transfer Request: Send possibly duplicated Data Record Packet (empty)
+    CDF->>CGF1: 
+    Note right of CGF1: 11. Data Record Transfer Response: Request Accepted
+    Note left of CDF: 12. Data Record Transfer Request: Release Data Record Packet
+    CDF->>CGF2: 
+    Note right of CDR_post_processing_system: 13. CDRs
+    CDR_post_processing_system->>CGF2: 
+    Note left of CDF: 14. Data Record Transfer Response: Request Accepted
+    CDF->>CGF2: 
+  
+```
+
+Sequence diagram illustrating the CDR transfer process when the primary CGF1 fails. The diagram shows interactions between CDF, CGF1, CGF2, and a CDR post-processing system. The CDF sends a request to CGF1, which fails. The CDF then resends the request to CGF2, which succeeds. The CDF receives a response from CGF2, deletes its own buffers, and then sends a Node Alive request to CGF1. CGF1 responds. Finally, the CDF sends an empty request to CGF1, which is accepted, and then a release request to CGF2, which is also accepted.
+
+**Figure 5.4: Duplicate prevention case: CDR sending via CGF1 had not succeeded**
+
+- 1) The CDR generating entity (CDF) sends CDR(s) in a packet to CGF (that is, the current primary CGF for the specific CDF, "CGF1"). The sending is performed by using the *Data Record Transfer Request* message, with the *Packet Transfer Command* IE having the value "Send Data Record Packet".
+- 2) Due to a failure in the CDF-CGF1 communication link of CGF1, the CGF1 is not able to store the packet sent by the CDF in a safe way (to e.g. a redundant RAM memory unit or a mirrored non-volatile memory or to another node).
+- 3) Therefore the CDF is not able to get a response (or it could alternatively get a negative response like "No resources available" as the *Cause* value in the *Data Record Transfer Response* message).
+
+- 4) The CDF may now first test the CDF-CGF2 link by an Echo Request message that the CGF2 would respond by the Echo Response.) Then, the CDF sends the same CDR packet that could not be sent to CGF1 to the next CGF in its CGF preference list (here CGF2) using the *Data Record Transfer Request* message, with the *Packet Transfer Command* IE having the value "Send possible duplicated Data Record Packet".
+- 5) As the connection to the CGF2 is working, the CGF2 is able to process the CDR packet. Since the packet was marked by the sending CDF to be potentially duplicated, it is stored into the CGF2, but not yet sent forward towards the BD.
+- 6) The CGF2 sends confirmation of the successful packet reception to the CDF. The confirmation is performed by using the *Data Record Transfer Response* message, with the **Cause** value being "Request Accepted"
+- 7) The CDF can now delete the now successfully sent (potentially duplicated) CDRs from its CDR buffer (but it keeps the sequence number(s) of the sent potentially duplicated packet(s) in a buffer dedicated for that.
+- 8) When CGF1 is recovering after a system reboot, it sends a *Node Alive Request* message to the configured peer CDF(s), and so the CDF notices that it can again successfully communicate with the CGF1. (The CDF may also detect this by using the *Echo Request* messages, which would be answered by CGF1 by the *Echo Response* message.)
+- 9) CDF acknowledges the CGF1 by *Node Alive Response* message.
+- 10) For the earlier unacknowledged *Data Record Transfer Request* message(s), the CDF sends CGF1 empty test packet(s) (with no CDR payload in the Data Record Packet IE but just the other parts of the message frame).
+- 11) CGF1 responds with *Data Record Transfer Response* message, with the **Cause** value being "Request Accepted", because in this example case CGF1 had lost the communication capability towards CDF before storing the previously received (and by CGF1 unacknowledged) CDR packet.
+- 12) Now CDF knows that the CGF1 had not originally been able to process and forward the original version of the CDR packet from the CDF, and it indicates CGF2 that CGF2 can send the CDR packet(s) related to the previously unacknowledged GTP' *Sequence Number(s)* to post-processing. Those packets' *Sequence Numbers* are indicated in the *Sequence Numbers of the Released Packets* IE.
+- 13) CGF2 shall now be able to send the released records towards the post-processing system.
+- 14) CGF2 responds with *Data Record Transfer Response* message, with the **Cause** value being 'Request Accepted'.
+
+After all the potentially duplicated packets are cleared from CGF(s), the CDF can continue in normal way the transfer of CDRs.
+
+#### 5.2.2.3 The CDF-CGF connection breaks after a successful CDR reception
+
+![Sequence diagram illustrating duplicate prevention when a connection breaks after successful CDR reception. Entities involved: CDF, CGF1, CGF2, and CDR post-processing system.](16152cf1d84aea10848758f51a91ff6a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CDF
+    participant CGF1
+    participant CGF2
+    participant PPS as CDR post-processing system
+
+    CDF->>CGF1: 1. Data Record Transfer Request: Send Data Record Packet
+    Note right of CGF1: < 2. CDR packet contents is stored to non-volatile  
+CGF1 memory or sent for postprocessing >
+    CGF1-->>PPS: 
+    Note over CDF, CGF1: 3. < No positive response to CDF, even to resent requests >
+    CDF->>CGF2: 4. Data Record Transfer Request: Send possibly duplicated Data Record Packet
+    Note right of CGF2: 5. < CGF2 stores the CDR packet contents to its buffer for pot. dupl. packets >
+    CGF2->>CDF: 6. Data Record Transfer Response: Request Accepted
+    Note left of CDF: 7. < CDRs are deleted from  
+CDF buffers >
+    Note over CDF, PPS: . . .
+    CDF->>CGF1: 8. Node Alive Request
+    CGF1->>CDF: 9. Node Alive Response
+    CDF->>CGF1: 10. Data Record Transfer Request: Send possibly  
+duplicated Data Record Packet (empty)
+    CGF1->>CDF: 11. Data Record Transfer Response: Request related  
+to possibly duplicated packets already fulfilled
+    CDF->>CGF2: 12. Data Record Transfer Request: Cancel Data Record Packet
+    Note right of CGF2: 13. < The cancelled packet(s) are deleted in CGF2 >
+    CGF2->>CDF: 14. Data Record Transfer Response: Request Accepted
+
+```
+
+Sequence diagram illustrating duplicate prevention when a connection breaks after successful CDR reception. Entities involved: CDF, CGF1, CGF2, and CDR post-processing system.
+
+**Figure 5.5: Duplicate prevention case: CDR sending via CGF1 had succeeded**
+
+- 1) The CDR generating entity (CDF) sends CDR(s) in a packet to CGF (that is the current primary Charging Gateway Functionality for the specific CDF, "CGF1"). The sending is performed by using the *Data Record Transfer Request* message, with the *Packet Transfer Command* IE having the value "Send Data Record Packet".
+- 2) The CGF1 is able to store the packet sent by the CDF in a safe way (to e.g. a redundant RAM memory unit or a mirrored non-volatile memory or to another network element, e.g. post-processing system).
+- 3) Since the CDF-CGF1 communication connection is now broken, the CDF is not able to get the response "Request Accepted" as the **Cause** value in the *Data Record Transfer Response* message.
+- 4) Then the CDF sends the same CDR packet that could not be sent to CGF1 to the next CGF in its CGF preference list (here CGF2) a *Data Record Transfer Request* message, with the *Packet Transfer Command* IE having the
+
+value "Send possible duplicated Data Record Packet". (That sending may be preceded by the testing of the CDF-CGF2 link by an *Echo Request* message, that the CGF2 would respond by the *Echo Response*.)
+
+- 5) As the connection to CGF2 is working, CGF2 is able to process the CDR packet. Since the packet was marked by the sending CDF to be potentially duplicated, it is stored in CGF2, but not yet sent forward towards the post processing or BD.
+- 6) The CGF2 sends confirmation of the successful packet reception to the CDF. The confirmation is performed by using the *Data Record Transfer Response* message, with the **Cause** value being "Request Accepted".
+- 7) The CDF can now delete the now successfully sent (potentially duplicated) CDRs from its CDR buffer (but it keeps the sequence number(s) of the sent potentially duplicated packet(s) in a buffer dedicated for that.
+- 8) When CGF1 is recovering after a system reboot, it sends a *Node Alive Request* message to the configured peer CDF(s), and so the CDF notices that it can again successfully communicate with the CGF1. (The CDF may also detect this by using the *Echo Request* messages, which would be answered by CGF1 by the *Echo Response* message.)
+- 9) CDF acknowledges the CGF1 by *Node Alive Response* message.
+- 10) For the earlier unacknowledged *Data Record Transfer Request* message(s), the CDF sends CGF1 empty test packet(s) (with no CDR payload in the *Data Record Packet* IE but just the other parts of the message frame).
+- 11) CGF1 responds with *Data Record Transfer Response* message, with the **Cause** value being "Request related to possibly duplicated packets already fulfilled", because in this example case CGF1 had lost the communication capability towards CDF after storing the previously received (and by CGF1 unacknowledged) CDR packet.
+- 12) Now CDF knows that the CGF1 had originally been able to process and forward the original version of the CDR packet from the CDF, and it indicates CGF2 that CGF2 can cancel the CDR packet(s) related to the previously unacknowledged GTP' CDF-CGF1 Sequence Number(s). Those packets' *Sequence Numbers* are indicated in the *Sequence Numbers of the Cancelled Packets* IE.
+- 13) CGF2 shall now delete the cancelled packet(s) from its buffer for potentially duplicated packets.
+- 14) CGF2 responds with *Data Record Transfer Response* message, with the **Cause** value being "Request Accepted".
+
+After all the potentially duplicated packets are cleared from CGF(s), the CDF can continue in normal way the transfer of CDRs.
+
+#### 5.2.2.4 CGF redundancy mechanism
+
+A summary of the CGF redundancy mechanism, which prevents duplicated CDR packets to enter the BS, is described below.
+
+This, or other mechanisms, are deployed to enhance the reliability of CDR transport.
+
+The general logic of the duplicate CDR packet prevention in CGF redundancy cases is shown in Figure 5.6, where the messages are numbered sequentially, alternative messages are indicated by an index character ("a" or "b") that follows the arrow sequence number. The main mechanism of the messaging in CGF redundancy cases (when a CDF-CGF link is down or a CGF is not working) is based on CDF (1) first trying to send a CDR packet to CGF1. In case no acknowledgement or a successful response is received (2) from CGF1 due to any reason, e.g. such as the request not reaching CGF1 despite repeated attempts (or the responses from CGF1 to the CDF are lost after the CGF1 has either stored it securely, or, forwarded it towards post-processing (2b)), the unacknowledged CDR packets are redirected to CGF2. The invocation for a re-transmission may be triggered by a time-out mechanism.
+
+The CDF may first test the CDF-CGF2 link by sending an 'Echo Request' message to CGF2, in response to which CGF2 would respond with the 'Echo Response' message. The CDR packets not successfully received by the primary CGF (=CGF1) are sent to CGF2 (3), and are marked as potential duplicates, and CGF2 responds to the request(s) (4). Such CDRs, i.e. CDRs that are marked as potential duplicates would wait there for further commands from CDF.
+
+When the CDF detects (5) & (6) that the primary CGF, in this case CGF1 is again able to communicate with it on receiving *Node Alive Request* (or getting a *Echo Response* from CGF2 to a *Echo Request* sent by the CDF) it answers by *Node Alive Response*. Then the CDF tests CGF1 with an empty packet (7), retrying continuously if no response is received, using e.g. increasing timeouts (using the old unacknowledged packet's Sequence Number, if the CGF1 would consider the packet to be a new one (8a) or an already received one (8b)). According to the response received from
+
+CGF1, the CDF gives the CGF2 a command to either release (9a) or cancel (9b) the corresponding CDR packet from CGF2. CGF2 then confirms the decision (10), and is able to send the CDRs towards the BS (11a).
+
+**Error handling:** By default, retransmissions after configurable timeouts are used. If after the CGF1 communication failure, the CDR packet sending from CDF to CGF2 does not succeed, the CDF tries to use CGF3 as the intermediate CDR packet storage entity, etc. If no acknowledgement (10) is received by the CDF for its message(s) (9a) or (9b), the CDF will retransmit the message (9a) or (9b) continuously and persistently, using e.g. increasing time intervals. An alarm should be sent to the O&M system if a communication link goes down. It shall be possible to release/cancel CDR packets from CGFs and unacknowledged sequence numbers from CDFs by O&M operations if permanent CDF-CGF link failures would occur. The buffers containing the Sequence Numbers of potentially duplicated packets, and the buffers containing the numbers of unacknowledged CDR packets shall be kept up to date (with CDR packet transfers) using transaction mechanisms. In the case of the CDF-CGF1 communication link being down, any new CDRs generated by the CDF are sent to a properly working CGF2, instead of the CGF1.
+
+![Sequence diagram of the General CGF redundancy messaging scheme showing interactions between CDF, CGF1, CGF2, and a post-processing System.](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CDF
+    participant CGF1
+    participant CGF2
+    participant PS as post-processing System
+
+    Note left of CGF1: 8.b) Req. rel. to poss. dupl. packet already fulfilled
+    CDF->>CGF1: 1. Send Data Record Packet
+    CGF1-->>CDF: 2. ( No response to CDF)
+    CDF->>CGF2: 3. Send Data Record Packet: pot.dupl.
+    CGF2-->>CDF: 4. Request Accepted
+    CDF->>CGF2: 9.a) Release Data Record Packet
+    CDF->>CGF2: 9.b) Cancel Data Record Packet
+    CGF2-->>CDF: 10. Request Accepted
+    CDF->>CGF1: 5. Node Alive Request
+    CGF1-->>CDF: 6. Node Alive Response
+    CDF->>CGF1: 7. Send Data Record Packet: pot.dupl., empty
+    CGF1-->>CDF: 8.a) Request Accepted
+    CGF1->>PS: 2.b) CDRs
+    PS->>CGF2: 11.a) CDRs
+  
+```
+
+The diagram illustrates the General CGF redundancy messaging scheme. It features four main entities: CDF (Customer Data Function), CGF1 (CGF 1), CGF2 (CGF 2), and a post-processing System. Each CGF and the post-processing System have a local buffer for CDRs (Customer Data Records). The sequence of messages is as follows:
+ 
+
+- The CDF sends a "1. Send Data Record Packet" to CGF1.
+- CGF1 responds with "2. ( No response to CDF)" to the CDF.
+- The CDF then sends a "3. Send Data Record Packet: pot.dupl." to CGF2.
+- CGF2 responds with "4. Request Accepted" to the CDF.
+- The CDF sends "9.a) Release Data Record Packet" and "9.b) Cancel Data Record Packet" to CGF2.
+- CGF2 responds with "10. Request Accepted" to the CDF.
+- The CDF sends "5. Node Alive Request" to CGF1.
+- CGF1 responds with "6. Node Alive Response" to the CDF.
+- The CDF sends "7. Send Data Record Packet: pot.dupl., empty" to CGF1.
+- CGF1 responds with "8.a) Request Accepted" to the CDF.
+- CGF1 sends "2.b) CDRs" to the post-processing System.
+- The post-processing System sends "11.a) CDRs" to CGF2.
+
+ A note at the top left indicates "8.b) Req. rel. to poss. dupl. packet already fulfilled", referring to the interaction between the CDF and CGF1.
+
+Sequence diagram of the General CGF redundancy messaging scheme showing interactions between CDF, CGF1, CGF2, and a post-processing System.
+
+**Figure 5.6: General CGF redundancy messaging scheme**
+
+##### **A more detailed description of the CGF redundancy mechanism:**
+
+Due to a network failure/network congestion or a temporary node failure, a CGF might not be able to send a response within the configured timeout period to a request it got from a CDF. As a first attempt, retries of requests are to be used as defined in TS 29.060 [200], if the response is not received in the configured time.
+
+If a CDF loses its connection to the CGF unexpectedly, it may send the CDRs to the next CGF in the priority list. If the CGF changes, the CDF can continue sending CDRs to different CGF nodes, depending on which CGF has been configured as the receiver of CDRs for a particular service.
+
+**Sequence number buffers:** The CDF might lose its connection to its primary CGF due to a link failure or CGF going down. In this kind of redundancy condition the CDF attempts to redirect the CDR traffic to a secondary CGF (after possible retries have failed). The CDF maintains an internal buffer for Sequence Numbers of requests not yet successfully responded to by the primary CGF, for the case that it may become capable of communicating to the primary CGF at a later date. The CDF will send the not responded Data Record Packets (DRPs) to the secondary CGF, and the CDF maintains also a buffer for the Sequence Numbers related to those DRPs that have been temporarily stored to this secondary CGF. (If the communication towards the secondary CGF would not work, the transfer of possibly duplicated DRPs and Sequence Number bookkeeping would be done for a tertiary CGF etc.) Also the CGFs maintain Sequence Number buffers for each of their CDF links. The Sequence Numbers may in future be needed in relation to the possibly duplicated CDRs that the CGFs have got from the CDF(s). The Sequence Numbers are stored to wait for a final decision to release them towards the BS (if the primary CGF had not received successfully the packets originally sent by a CDF) or to cancel them (if the primary CGF had received and processed successfully the originally by CDF sent packets).
+
+The CDF is able to instruct CGF2 to cancel (or instruct CGF2 to transfer towards the BS), the CDR packets sent to a secondary CGF if the primary CGF becomes available for service. To make the right decision the CDF first sends an empty test packet with the 'Send possibly duplicated Data Record Packet' Packet Transfer Command to the primary CGF, using a previously not responded Sequence Number.
+
+In case that the empty test packet to the primary CGF (which was temporarily down (or to which the link was down)) is responded with the **Cause** value "Request Accepted", the CDF will release the corresponding CDRs waiting for final decision in the secondary CGF, towards the BD with the Packet Transfer Command "Release Data Record Packet".
+
+If the primary CGF responses this test message with the **Cause** value "Request related to possibly duplicated packets already fulfilled", the CDF will cancel the corresponding CDRs waiting for final decision in the secondary CGF, using the Packet Transfer Command "Cancel Data Record Packet".
+
+To enable that a CDF failure (destroying its Sequence Number buffers per each CGF link for non-responded requests or possibly duplicated packets) would not cause CDR packets to stay forever in the temporary decision waiting buffers of CGFs, there should also be O&M means of emptying those CGF buffers.
+
+There shall also be a configurable parameter in the CGF for making the final decision, as to whether or not it is able to send the CDRs to the BS for the case where the backup buffering mechanism in the CDF could not be used until the end of the messaging sequence related to a certain CDR packet has been completed. This way the operator can:
+
+- A) Select that the CDFs and CGFs take care of duplicate prevention and the BS is not required to do duplicate checking due to possible duplicates caused by Network Element or CGF redundancy mechanisms.
+- B) Select that the BS performs the duplicate prevention. To do this in the most effective way, the CGF may include an additional flag linked to possibly duplicated CDRs sent to the BS, indicating that they have not been released by a CDF for BS use (or use special kind of file name if a file protocol is used between CGF and BS). This means that the BS has somewhat more processing work to do, but the BS would anyway get a duplicate free end result. CGF is in this case always authorised to forward CDRs towards the BS, also when they contain possibly duplicated data. For this case the CGFs may also have a configurable flag that *Data Record Packet Cancel/Release* operations are not needed.
+
+# --- 6 Data description for the transfer
+
+## 6.1 The GTP' charging protocol
+
+This clause describes the features of GTP'. The message types described in subclause 6.2.2 ("Reused GTP message types") are also described in the related clauses of TS 29.060 [200].
+
+### 6.1.1 Usage of GTP Header in charging
+
+In GTP' messaging only the signalling plane of GTP is partly reused. The GTP' header is shown in Figure 6.1.
+
+Bit 5 of octet 1 of the GTP header is the Protocol Type (PT) flag: it is '0' if the message is GTP'.
+
+The *Version* bits indicate the GTP' protocol version when the Protocol Type flag is '0'.
+
+Bit 1 of octet 1 is not used in GTP' (except in v0), and it is marked '0' in the GTP' header. It is in use in GTP' v0 and distinguishes the used header-length. In the case of GTP' v0, this bit being marked one (1) indicates the usage of the 6 octets header. If the bit is set to '0' (usually the case) the 20-octet header is used. For all other versions of GTP', this bit is not used and is set to '0'. However, this does not suggest the use of the 20-octet header, rather a shorter 6-octet header.
+
+The *Length* indicates the length of payload (number of octets after the GTP' header). The *Sequence Number* of the packet is part of the GTP' header.
+
+![](e636d7ccca0ad14c6b95201404324823_img.jpg)
+
+| Octets | Bits            |   |    |                 |   |   |         |   |
+|--------|-----------------|---|----|-----------------|---|---|---------|---|
+|        | 8               | 7 | 6  | 5               | 4 | 3 | 2       | 1 |
+| 1      | Version         |   | PT | Spare ' 1 1 1 ' |   |   | ' 0/1 ' |   |
+| 2      | Message Type    |   |    |                 |   |   |         |   |
+| 3 - 4  | Length          |   |    |                 |   |   |         |   |
+| 5 - 6  | Sequence Number |   |    |                 |   |   |         |   |
+
+Figure 6.1: GTP' header
+
+### 6.1.2 Information Elements (IEs)
+
+The messages may contain several Information Elements (IEs). The TLV (Type, Length, Value) or TV (Type, Value) encoding formats shall be used for the GTP' IEs. The GTP' messages shall have the IEs sorted with the *Type* fields in ascending order. The *Length* field shall contain the IE length excluding the Type and Length fields.
+
+Within the *Type* field the most significant bit will be set to 0 when the TV format is used and set to 1 when the TLV format is used. This is illustrated in Figures 6.2 and b, respectively.
+
+![](cd141897aa368dbbaa398ace230cdd85_img.jpg)
+
+|                   |   | Bits |                 |   |   |   |   |   |   |
+|-------------------|---|------|-----------------|---|---|---|---|---|---|
+| <del>Octets</del> |   | 8    | 7               | 6 | 5 | 4 | 3 | 2 | 1 |
+| (a)               | 1 | 0    | Type->TV format |   |   |   |   |   |   |
+
+  
+
+|                   |   | Bits |                  |   |   |   |   |   |   |
+|-------------------|---|------|------------------|---|---|---|---|---|---|
+| <del>Octets</del> |   | 8    | 7                | 6 | 5 | 4 | 3 | 2 | 1 |
+| (b)               | 1 | 1    | Type->TLV format |   |   |   |   |   |   |
+
+Figure 6.2: Type field for (a) TV and (b) TLV format
+
+## 6.2 GTP' Message Types
+
+### 6.2.1 List of all GTP' message types
+
+GTP' defines a set of messages between two associated nodes. The GTP' messages defined are shown in Table 6.1. The messages introduced by GTP' are in **boldface** letters. The other messages are inherited from the GTP protocol.
+
+The GTP' introduced signalling message types
+
+- Node Alive Request,
+- Node Alive Response,
+- Redirection Request and
+- Redirection Response
+
+belong to the "Path Management messages", while
+
+- Data Record Transfer Request and
+- Data Record Transfer Response
+
+are from the message type group "Record Transmission messages".
+
+The reserved fields in the signalling messages shall be filled with ones, and are intended for future use.
+
+GTP' reuses the GTP **Cause** values. The message type numbers required for the newly introduced GTP' messages have been derived from the unallocated message type number space specified in the GTP message table defined in TS 29.060 [200].
+
+The number ranges allocated for GTP' are as follows:
+
+For Information Elements: 117-127 (TV type fields) and 239-254 (for TLV type fields).
+
+TLV Information Element types introduced in the present document:
+
+|     |                                                                           |
+|-----|---------------------------------------------------------------------------|
+| 254 | <i>Address of Recommended Node</i>                                        |
+| 253 | <i>Requests Responded</i>                                                 |
+| 252 | <i>Data Record Packet</i>                                                 |
+| 251 | <i>Charging Gateway Address</i> (this IE is also used in TS 29.060 [200]) |
+| 250 | <i>Sequence Numbers of Cancelled Packets</i>                              |
+| 249 | <i>Sequence Numbers of Released Packets</i>                               |
+
+TV Information Element types introduced in the present document:
+
+|     |                                |
+|-----|--------------------------------|
+| 127 | <i>Charging ID</i>             |
+| 126 | <i>Packet Transfer Command</i> |
+
+For **Cause** Codes: **Cause** values used in requests: 49 to 63, **Cause** values used in responses indicating acceptance: 177 to 191, **Cause** values used in responses indicating rejection: 241 to 255.
+
+Charging related **Cause** values introduced for the present document:
+
+In requests:
+
+|    |                                               |
+|----|-----------------------------------------------|
+| 63 | <i>This node is about to go down</i>          |
+| 62 | <i>Another node is about to go down</i>       |
+| 61 | <i>The receive buffers are becoming full</i>  |
+| 60 | <i>The transmit buffers are becoming full</i> |
+| 59 | <i>System failure</i>                         |
+
+In responses indicating acceptance:
+
+|     |                           |
+|-----|---------------------------|
+| 177 | <i>CDR decoding error</i> |
+|-----|---------------------------|
+
+In responses indicating rejection:
+
+|     |                                                                         |
+|-----|-------------------------------------------------------------------------|
+| 255 | <i>Request not fulfilled</i>                                            |
+| 254 | <i>Sequence numbers of released/cancelled packets IE incorrect</i>      |
+| 253 | <i>Request already fulfilled</i>                                        |
+| 252 | <i>Request related to possibly duplicated packets already fulfilled</i> |
+
+The charging related message types are listed in Table 6.1. Brief descriptions of the GTP messages reused in GTP' are provided in subclause 6.2.2 ("Reused GTP message types") below. Further details are provided in TS 29.060 [200], the GTP specification.
+
+| Message Type value (Decimal) | GTP' message                  |
+|------------------------------|-------------------------------|
+| 1                            | Echo Request                  |
+| 2                            | Echo Response                 |
+| 3                            | Version Not Supported         |
+| 4                            | Node Alive Request            |
+| 5                            | Node Alive Response           |
+| 6                            | Redirection Request           |
+| 7                            | Redirection Response          |
+|                              |                               |
+| 240                          | Data Record Transfer Request  |
+| 241                          | Data Record Transfer Response |
+| others                       | reserved for future use       |
+
+Table 6.1: GTP' messages
+
+### 6.2.2 Reused GTP message types
+
+The existing *Echo Request* and *Echo Response* messages defined in TS 29.060 [200] are also used in PS domain charging. They may be used by the CDF or by the CGF for checking if another CDF or CGF is alive. If the present document and TS 29.060 [200] differ in their description, then the TS 29.060 [200] is to be taken as the latest specification status of the related Information Elements. If the path protocol is TCP, *Echo Request* and *Echo Response* messages are not required.
+
+The *Version Not Supported* message in the GTP' is similar to the corresponding GTP message. It indicates the latest GTP' version that the GTP' entity can support. If a receiving node receives a GTP' message of an unsupported version, then this node shall return a GTP' *Version Not Supported* message, indicating in the Version field of the GTP' header the latest GTP' version, this node supports. The received payload data of the GTP' packet shall then be discarded.
+
+The *Version* bits in the GTP' header have currently the following possible values:
+
+- GTP' version 0 (binary '000') identifies the following Message Type values:
+  - 3 = Version Not Supported,
+  - 4 = Node Alive Request,
+  - 5 = Node Alive Response,
+  - 6 = Redirection Request,
+  - 7 = Redirection Response.
+
+In clause 7.3.4.6 the Requests Responded information element has Length field in place of the Number of Requests Responded field, to make that TLV IE to be handled like normal TLV IEs.
+
+If GTP' v0 is used in parallel with GTP' v2 or a later version, then, a 6-octet header length (with no trailing dummy octets) is used also with v0 (like in GTP' v2).
+
+The mark of the usage of GTP' v0 with 6 octet header (instead of the original 20 octet long header) is then the version bits being 0 and the bit 1 of octet 1 being '1' (instead of '0').
+
+- GTP' version 1 (binary '001') is the same as version 0 but has, in addendum, the duplicate CDR prevention mechanism, introduced in GSM 12.15 version 7.2.1 (1999-07) of the GPRS charging specification.
+- GTP' version 2 (binary '010') is the same as version 1, but the header is just 6 octets long (no unused trailing octets). IPv6 address type is also supported (for Address of Recommended Node information element of the Redirection Request).
+
+### 6.2.3 GTP message type modifications, implied by GTP'
+
+The general principle is that the CDRs are always sent to a CGF residing in the same network as the CDF. In the case of roaming it is conceivable that some CDRs relating to the same service (e.g. in PS domain for the same IP-CAN bearer) will be sent to different networks' CGFs. The cost balancing of the roaming traffic is to be agreed between the UMTS Operators.
+
+### 6.2.4 GTP' message types
+
+#### 6.2.4.1 Node Alive Request
+
+The *Node Alive Request* message may be used to inform that a node in the network has started its service (e.g. after a service break due to software or hardware maintenance or data service interruption after an error condition). A node may send a different Node Address than its own in the Information Element, e.g. informing the "next node in the chain" that the "previous node in the chain" (which is located on the other side of the sender of this message) is now ready for service. This message type is optional if the Path Protocol is TCP.
+
+The *Node Alive Request* message allows a quicker reconnect capability than the *Echo Request* message based polling can provide, and its usage will have a reduced load effect on the network, particularly when the number of network nodes using GTP' is high. It may also be used to inform when a new network node has become available for service. If the *Echo Request* message is also used, then the usage of the *Node Alive Request* message allows the interval of *Echo Requests* to be longer, thus reducing network load by reducing number of *Echo Requests*.
+
+The Information elements in a Node Alive Request message are shown in Table 6.2.
+
+| Information Element      | Presence requirement |
+|--------------------------|----------------------|
+| Node Address             | Mandatory            |
+| Alternative Node Address | Optional             |
+| Private Extension        | Optional             |
+
+**Table 6.2: Information Elements in a Node Alive Request**
+
+The Node Address format is the same as for the Charging Gateway Address format described in TS 29.060 [200]).
+
+The format definition for the Node Address information element is the same as the format of the source and destination address of the IP packet that transports the GTP' messages. The optional Alternative Node Address IE can be used in the *Node Alive Request* if the message sender wants to advertise an IP address that is different from the node address format. This way both the IPv4 and IPv6 node address formats can be supported simultaneously in the messaging, regardless of whether IPv4 or IPv6 is used in the underlying transport.
+
+The optional Private Extension IE contains vendor- or operator-specific information.
+
+#### 6.2.4.2 Node Alive Response
+
+The *Node Alive Response* message, shown in Table 6.3, shall be sent as a response to a received *Node Alive Request*.
+
+| Information Element | Presence requirement |
+|---------------------|----------------------|
+| Private Extension   | Optional             |
+
+**Table 6.3: Information Elements in a Node Alive Response**
+
+The optional Private Extension IE contains vendor- or operator-specific information.
+
+#### 6.2.4.3 Redirection Request
+
+There are two use cases for the *Redirection Request* message:
+
+- One is to advise that received CDR traffic is to be redirected to another CGF due to the sending CGF node is about to stop service (due to an outage for maintenance or an error condition).
+- The second purpose is to inform a CDF which is currently sending data to this node (e.g. CGF), that the next node in the chain (e.g. a mediator device or Billing Computer) has lost connection to this node (e.g. CGF).
+
+The Information Elements in a *Redirection Request* Message are listed in Table 6.4.
+
+An *Address of Recommended Node* may be given if, for example, a CGF maintenance outage is handled by first introducing another CGF ready to take incoming CDRs. This way, the network performance can be maintained. The *Address of Recommended Node* shall only describe an intra-PLMN node containing a CGF, and not a node in any other PLMN.
+
+| Information Element                     | Presence requirement |
+|-----------------------------------------|----------------------|
+| Cause                                   | Mandatory            |
+| Address of Recommended Node             | Optional             |
+| Alternative Address of Recommended Node | Optional             |
+| Private Extension                       | Optional             |
+
+**Table 6.4: Information Elements in a Redirection Request**
+
+Possible **Cause** values are:
+
+- "This node is about to go down";
+- "Another node is about to go down";
+- "System failure";
+- "Receive buffers becoming full";
+- "Send buffers becoming full".
+
+The *Address of Recommended Node* information element, shown in Figure 6.3, defines the IPv4 or IPv6 format address that the node is identified by in the UMTS network.
+
+![Figure 6.3: Address of Recommended Node information elements. The diagram shows two tables representing the structure of the information element for IPv4 and IPv6. The IPv4 table has 3 rows: Octet 1 contains Type = 254 (Decimal); Octets 2-3 contain Length = 4 (Decimal); Octets 4-7 contain IPv4 Address. The IPv6 table has 3 rows: Octet 1 contains Type = 254 (Decimal); Octets 2-3 contain Length = 16 (Decimal); Octets 4-19 contain IPv6 Address. Both tables include a header row for Bits 8 through 1.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg)
+
+**IPv4 Address of Recommended Node**
+
+| Octets | Bits                 |   |   |   |   |   |   |   |
+|--------|----------------------|---|---|---|---|---|---|---|
+|        | 8                    | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1      | Type = 254 (Decimal) |   |   |   |   |   |   |   |
+| 2-3    | Length = 4 (Decimal) |   |   |   |   |   |   |   |
+| 4-7    | IPv4 Address         |   |   |   |   |   |   |   |
+
+**IPv6 Address of Recommended Node**
+
+| Octets | Bits                  |   |   |   |   |   |   |   |
+|--------|-----------------------|---|---|---|---|---|---|---|
+|        | 8                     | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1      | Type = 254 (Decimal)  |   |   |   |   |   |   |   |
+| 2-3    | Length = 16 (Decimal) |   |   |   |   |   |   |   |
+| 4-19   | IPv6 Address          |   |   |   |   |   |   |   |
+
+Figure 6.3: Address of Recommended Node information elements. The diagram shows two tables representing the structure of the information element for IPv4 and IPv6. The IPv4 table has 3 rows: Octet 1 contains Type = 254 (Decimal); Octets 2-3 contain Length = 4 (Decimal); Octets 4-7 contain IPv4 Address. The IPv6 table has 3 rows: Octet 1 contains Type = 254 (Decimal); Octets 2-3 contain Length = 16 (Decimal); Octets 4-19 contain IPv6 Address. Both tables include a header row for Bits 8 through 1.
+
+**Figure 6.3: Address of Recommended Node information elements**
+
+The format definition for the *Address of Recommended Node* information element is the same as the format of the source and destination address of the IP packet that transports the GTP' messages. The optional *Alternative Address of Recommended Node* IE can be used in the *Node Alive Request* if the message sender wants to advertise an IP address that is different from the node address format. This way both the IPv4 and IPv6 node address formats can be supported simultaneously in the messaging, regardless of whether IPv4 or IPv6 is used in the underlying transport.
+
+The optional Private Extension contains vendor- or operator- specific information.
+
+#### 6.2.4.4 Redirection Response
+
+A *Redirection Response* message shall be sent as a response of a received *Redirection Request*. The information elements of this message are listed in Table 6.5.
+
+| Information Element | Presence requirement |
+|---------------------|----------------------|
+| Cause               | Mandatory            |
+| Private Extension   | Optional             |
+
+**Table 6.5: Information Elements in a Redirection Response**
+
+Possible **Cause** values are:
+
+- "Request Accepted";
+
+- "No resources available";
+- "Service not supported";
+- "System failure";
+- "Mandatory IE incorrect";
+- "Mandatory IE missing";
+- "Optional IE incorrect";
+- "Invalid message format";
+- "Version not supported".
+
+The optional Private Extension contains vendor- or operator-specific information.
+
+#### 6.2.4.5 Data Record Transfer Request
+
+This message is used to transmit the CDR(s) to the CGF.
+
+The CDRs are placed in the *Data Record Packet* information element.
+
+##### 6.2.4.5.1 Information Elements in Data Record Transfer Request
+
+The Information Elements in *Data Record Transfer Request* message is specified in Table 6.6.
+
+| Information Element                   | Presence requirement |
+|---------------------------------------|----------------------|
+| Packet Transfer Command               | Mandatory            |
+| Data Record Packet                    | Conditional          |
+| Sequence Numbers of Released Packets  | Conditional          |
+| Sequence Numbers of Cancelled Packets | Conditional          |
+| Private Extension                     | Optional             |
+
+**Table 6.6: Information Elements in a Data Record Transfer Request**
+
+##### 6.2.4.5.2 Packet Transfer Command IE
+
+The value of the Packet Transfer Command in its Information Element tells the nature of the message:
+
+- 1 = 'Send Data Record Packet';
+- 2 = 'Send possibly duplicated Data Record Packet';
+- 3 = 'Cancel Data Record Packet';
+- 4 = 'Release Data Record Packet'.
+
+The following describes the usage of each Packet Transfer Command. The first command is for normal CDR transfer while the other values are only used as part of the redundancy mechanism.
+
+- 1) **Send Data Record Packet.** This is the usual command used for sending CDRs under normal conditions when no error recovery is needed or the redirection mechanism is not involved. It is shown in Figure 6.5. The other three commands are being used only in error recovery cases. Out of the three conditional IEs shown in Table 6.6, only the "Data Record Packet" is present in this message.
+- 2) **Send possibly duplicated Data Record Packet.** When the CDR packet is redirected to a secondary CGF (by a CDF) because the currently used CGF is not working or the CDR transfer is not working properly, or if there is an error in the link between the CDF and the CGF, then this Packet Transfer Command is used instead of the normal 'Send Data Record Packet'. Of the conditional IEs, the "Data Record Packet" is present in the message, when sending the message to a CGF acting as temporary storage, when the original primary CGF could not be contacted. This Packet Transfer Command is used also when sending "empty" test packets with older (but not yet acknowledged) sequence numbers after a peer node or link recovery, to check if the CGF had received some Data Record Packets (whose acknowledgement did not come to the *Data Record Packet* sending node) before the link to the recipient node became inoperable.
+- 3) **Cancel Data Record Packet.** Of the conditional IEs, the "Sequence Numbers of Cancelled Packets" is present in the message.
+- 4) **Release Data Record Packet.** Of the conditional IEs, the "Sequence Numbers of Released Packets" is present in the message.
+
+| Octets | Bits                    |   |   |   |   |   |   |   |
+|--------|-------------------------|---|---|---|---|---|---|---|
+|        | 8                       | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1      | Type = 126 (Decimal)    |   |   |   |   |   |   |   |
+| 2      | Packet Transfer Command |   |   |   |   |   |   |   |
+
+**Figure 6.5: Packet Transfer Command information element**
+
+After the CGF has received the *Packet Transfer Command* 'Release Data Record Packet' with the Sequence Number(s) for earlier sent 'Send possibly duplicated Data Record Packet' command(s), it can consider itself authorised to send the *Data Record Packets* previously marked as possibly duplicated towards the BD as normal (not duplicated) CDRs.
+
+##### 6.2.4.5.3 Data Record Packet IE
+
+The *Data Record Packet* element, which is present conditionally if the Packet Transfer Command is 'Send Data Record Packet' or 'Send possibly duplicated Data Record Packet', may contain one or more CDRs. This IE is illustrated in Figure 6.6. If an "empty packet" is to be sent, then the *Data Record Packet* IE contains only the *Type* (with value 252 in decimal) and the *Length* (with value 0) fields.
+
+As shown in Figure 6.6, there are two fields identifying the CDR format:
+
+*Data Record Format* and *Data Record Format Version*.
+
+The format of the CDRs is ASN.1 or some other format, as identified by the value of *Data Record Format*.
+
+The *Data Record Format Version* identifies the TS release and version numbers that were used for the CDR encoding.
+
+The formats of these two fields are described in detail in sections 6.3 and 6.4.
+
+| Octets  | Bits                       |   |   |   |   |   |   |   |
+|---------|----------------------------|---|---|---|---|---|---|---|
+|         | 8                          | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1       | Type = 252 (Decimal)       |   |   |   |   |   |   |   |
+| 2...3   | Length                     |   |   |   |   |   |   |   |
+| 4       | Number of Data Records     |   |   |   |   |   |   |   |
+| 5       | Data Record Format         |   |   |   |   |   |   |   |
+| 6...7   | Data Record Format Version |   |   |   |   |   |   |   |
+| 8...9   | Length of Data Record 1    |   |   |   |   |   |   |   |
+| 10...n  | Data Record 1              |   |   |   |   |   |   |   |
+|         | ⋮                          |   |   |   |   |   |   |   |
+| x...x+1 | Length of Data Record N    |   |   |   |   |   |   |   |
+| x+2...y | Data Record N              |   |   |   |   |   |   |   |
+
+**Figure 6.6: Data Record Packet information element**
+
+##### 6.2.4.5.4 Sequence Numbers of Released Packets IE
+
+The *Sequence Numbers of Released Packets* is present if the *Packet Transfer Command* is 'Release Data Record Packet'. The format of the Information Element is described in Figure 6.7 below:
+
+![](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+| Octets  | Bits              |   |   |   |   |   |   |   |
+|---------|-------------------|---|---|---|---|---|---|---|
+|         | 8                 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1       | Type = 249        |   |   |   |   |   |   |   |
+| 2...3   | Length            |   |   |   |   |   |   |   |
+| 4...5   | Sequence Number 1 |   |   |   |   |   |   |   |
+| ...     | ...               |   |   |   |   |   |   |   |
+| n...n+1 | Sequence Number N |   |   |   |   |   |   |   |
+
+**Figure 6.7: Sequence Numbers of Released Packets information element**
+
+##### 6.2.4.5.5 Sequence Numbers of Cancelled Packets IE
+
+The *Sequence Numbers of Cancelled Packets* information element is shown in Figure 6.8 and contains the IE *Type*, *Length* and the *Sequence Number(s)* (each 2 octets) of the cancelled *Data Record Transfer Request(s)*. It is present if the *Packet Transfer Command* is "Cancel Data Record Packet".
+
+![](e29665b8abcea967ef289c6aff07ae4c_img.jpg)
+
+| Octets  | Bits              |   |   |   |   |   |   |   |
+|---------|-------------------|---|---|---|---|---|---|---|
+|         | 8                 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1       | Type = 250        |   |   |   |   |   |   |   |
+| 2...3   | Length            |   |   |   |   |   |   |   |
+| 4...5   | Sequence Number 1 |   |   |   |   |   |   |   |
+| ...     | ...               |   |   |   |   |   |   |   |
+| n...n+1 | Sequence Number N |   |   |   |   |   |   |   |
+
+**Figure 6.8: Sequence Numbers of Cancelled Packets information element**
+
+##### 6.2.4.5.6 Private Extension IE
+
+The optional *Private Extension* contains vendor or operator specific information.
+
+#### 6.2.4.6 Data Record Transfer Response
+
+The message shall be sent as a response of a received *Data Record Transfer Request*. Also, several *Data Record Transfer Requests* can be responded by a single *Data Record Transfer Response*.
+
+| Information Element | Presence requirement |
+|---------------------|----------------------|
+| Cause               | Mandatory            |
+| Requests Responded  | Mandatory            |
+| Private Extension   | Optional             |
+
+**Table 6.7: Information Elements in a Data Record Transfer Response**
+
+The **Cause** (whatever the value may be) applies for all those *Data Record Transfer Requests*, responded by that particular *Data Record Transfer Response*.
+
+Possible **Cause** values are:
+
+- "Request Accepted";
+- "No resources available";
+- "Service not supported";
+
+- "System failure";
+- "Mandatory IE incorrect";
+- "Mandatory IE missing";
+- "Optional IE incorrect";
+- "Invalid message format";
+- "Version not supported";
+- "Request not fulfilled";
+- "CDR decoding error";
+- "Request already fulfilled";
+- "Request related to possibly duplicated packet already fulfilled";
+- "Sequence numbers of released/cancelled packets IE incorrect".
+
+The **cause** value "CDR decoding error" is optional, primarily intended to inform the CDF that the receiving node cannot decode the CDR. Thus, special features in the receiving node that are based on information within the CDR, would not be operable. This message could alert the operator of a remote generating node of incompatible CDR encoding. It is optional and no action or response is required.
+
+The **Requests Responded** information element contains the IE *Type*, *Length* and the *Sequence Numbers* (each 2 octets) of the *Data Record Transfer Requests*. It is shown in Figure 6.9.
+
+![](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg)
+
+| Octets  | Bits              |   |   |   |   |   |   |   |
+|---------|-------------------|---|---|---|---|---|---|---|
+|         | 8                 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1       | Type = 253        |   |   |   |   |   |   |   |
+| 2..3    | Length            |   |   |   |   |   |   |   |
+| 4..5    | Sequence Number 1 |   |   |   |   |   |   |   |
+| ...     |                   |   |   |   |   |   |   |   |
+| n...n+1 | Sequence Number 2 |   |   |   |   |   |   |   |
+
+**Figure 6.9: Requests Responded information element**
+
+The optional *Private Extension* contains vendor or operator specific information.
+
+Depending on the **Cause** value severity and general occurrence frequency, the node that sent the corresponding *Data Record Transfer Request*, may start to direct its CDRs to another CGF.
+
+## 6.3 Data Record Format in GTP'
+
+The format of the PS domain CDRs, sent from CDF to CGF, is defined by the *Data Record Format*, which is the 5<sup>th</sup> octet of *Data Record Packet* information element, shown in Figure 6.6.
+
+The following rules govern the *Data Record Format*:
+
+- This field consists of one octet (#5).
+- The value range is 1-255 in decimal. The value '0' should not be used.
+- Only the values 1-10 and 51-255 can be used for standards purposes.
+- Values in the range of 11-50 are to be configured only by operators, and are not subject to standardization.
+- The value '1' identifies ASN.1 Basic Encoding Rules (BER) encoding, which must be supported in PS domain charging.  
+Other values for optional encodings are specified in subclause 6.3.1.
+
+### 6.3.1 Standard Data Record Format
+
+For the PS domain CDR transfer, defined by the present document, only an ASN.1 BER encoding is mandatory. For this encoding, the *Data Record Format* value is '1'.
+
+Other ASN.1 encodings may be supported optionally, with *Data Record Format* values as indicated below:
+
+- "1" signifies the use of Basic Encoding Rules (BER)
+- "2" signifies the use of unaligned basic Packed Encoding Rules (PER)
+- "3" signifies the use of aligned basic Packed Encoding Rules (PER)
+
+### 6.3.2 Private Data Record Formats
+
+The *Data Record Format* values 11...50 (decimal) are reserved for private (implementation specific) format use.
+
+## 6.4 Data Record Format Version for CDRs
+
+The CDR release and versions numbers are defined by the '*Data Record Format Version*', in octet 6 and 7 of the *Data Record Packet IE*, shown in Figure 6.6. The format of this field is depicted in Figure 6.10.
+
+The first octet (#6 in *Data Record Packet IE*) is divided into two fields each with 4 bits :
+
+The first field (bits 8-5 of octet 6, see figure 6.10) identifies the application. For charging purposes, the *Application Identifier* has a value of '1' (decimal).
+
+Other possible applications of GTP may use different numbers.
+
+The second field (bits 4-1 of octet 6, see figure 6.10) identifies the release.
+
+The *Release Identifier* indicates the TS release, used to encode the CDR, i.e. its value corresponds to the first digit of the version number of the document [51], as shown on the cover sheet.
+
+The second octet (#7 in *Data Record Packet IE*) identifies the version of the TS used to encode the CDR, i.e. its value corresponds to the second digit of the version number of the document [51] (as shown on the cover sheet), plus '1'.
+
+E.g. for version 3.4.0, the *Version Identifier* would be "5".
+
+In circumstances where the second digit is an alphabetical character, (e.g. 3.b.0), the corresponding ASCII value shall be taken, e.g. the *Version Identifier* would be "66" (ASCII(b)).
+
+![](6a5c8326029e6290e69a5f43d6ed4548_img.jpg)
+
+| Data Record Packet IE |  | Bits                   |   |   |   |                    |   |   |   |
+|-----------------------|--|------------------------|---|---|---|--------------------|---|---|---|
+|                       |  | 8                      | 7 | 6 | 5 | 4                  | 3 | 2 | 1 |
+| 6                     |  | Application Identifier |   |   |   | Release Identifier |   |   |   |
+| 7                     |  | Version Identifier     |   |   |   |                    |   |   |   |
+
+Figure 6.10: The Format of the *Data Record Format Version* Field
+
+# --- Annex A (informative): Bibliography
+
+## a) The 3GPP charging specifications
+
+- 3GPP TS 32.252: "Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging".
+- 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
+- 3GPP TS 32.271: "Telecommunication management; Charging management; Location Services (LCS) charging".
+- 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS) applications and interfaces".
+
+## b) Common 3GPP specifications
+
+- TS 22.101: "Service aspects; Service Principles".
+- TS 22.115: "Service aspects; Charging and billing".
+- TS 23.002: "Network Architecture".
+- TS 23.003: "Numbering, addressing and identification".
+- TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+
+## c) other Domain and Service specific 3GPP / ETSI specifications
+
+- 
+
+## d) Relevant ITU Recommendations
+
+- ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)".
+- ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- ITU-T Recommendation Q.767: "Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections".
+- ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".
+- ITU-T Recommendation X.121: "International numbering plan for public data networks".
+
+## e) Relevant IETF RFCs
+
+- IETF RFC 959 (1985): "File Transfer Protocol".
+- IETF RFC 3588 (2003): "Diameter base protocol"
+- IETF Internet-Draft "Diameter Credit Control Application"
+- IETF RFC 1350: "The TFT Protocol (Revision 2)"
+
+# Annex B (informative): Change history
+
+| Change history |       |           |      |     |                                                                                   |       |        |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                   | Old   | New    |
+| Sep 2004       | SA 25 | SP-040553 | --   | --  | Submitted to TSG SA#25 for Approval                                               | 1.0.0 | 6.0.0  |
+| Jun 2005       | SA 28 | SP-050275 | 0001 | --  | Correction to scope                                                               | 6.0.0 | 6.1.0  |
+| Jun 2005       | SA 28 | SP-050275 | 0002 | --  | Correction to references                                                          | 6.0.0 | 6.1.0  |
+| Jun 2005       | SA_28 | SP-050275 | 0003 | --  | Correction on the use of 'reference point' and 'interface' – Align with TR 21.905 | 6.0.0 | 6.1.0  |
+| Jun 2007       | SA 36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7.                            | 6.1.0 | 7.0.0  |
+| Jun 2008       | SA 40 | SP-080274 | 0004 | --  | Implication on CDR transfer for EPC Charging                                      | 7.0.0 | 8.0.0  |
+| Sep 2009       | SA 45 | SP-090536 | 0005 | --  | UDP Port number differentiation between GTPv2 and GTPv2                           | 8.0.0 | 8.1.0  |
+| Dec 2009       | -     | -         | -    | -   | Update to Rel-9 version (MCC)                                                     | 8.1.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -    | -   | Update to Rel-10 version (MCC)                                                    | 9.0.0 | 10.0.0 |

marked/Rel-10/32_series/32297/raw.md

@@ -0,0 +1,893 @@
+
+
+# Keywords UMTS, E-UTRAN, GPRS, EPS, charging management 3GPP TS 32.297 V10.2.0 (2011-12)
+
+*Technical Specification*
+
+## **3GPP** **3rd Generation Partnership Project;** Postal address **Technical Specification Group Services and System Aspects;** **Telecommunication management;** 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 93 16 00 Fax: +33 4 93 17 15 27 Charging Data Record (CDR) file forr
+
+![LTE logo with '4 ADVANCED' text above the 't'](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo with '4 ADVANCED' text above the 't'
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon](390120de4fe440c42fea8154fcaad334_img.jpg)
+
+3GPP logo with a signal icon
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                                  |    |
+|------------------------------------------------------------------|----|
+| Foreword .....                                                   | 5  |
+| 1 Scope.....                                                     | 6  |
+| 2 References.....                                                | 6  |
+| 3 Definitions, symbols and abbreviations .....                   | 9  |
+| 3.1 Definitions.....                                             | 9  |
+| 3.2 Symbols.....                                                 | 10 |
+| 3.3 Abbreviations .....                                          | 10 |
+| 4 Architecture considerations.....                               | 11 |
+| 5 CDR File Transfer Principles and Scenarios .....               | 12 |
+| 5.1 Local CDR and CDR file handling .....                        | 12 |
+| 5.1.1 CDR processing.....                                        | 12 |
+| 5.1.2 CDR routeing.....                                          | 13 |
+| 5.1.3 Local CDR file management.....                             | 13 |
+| 5.2 File format principles .....                                 | 15 |
+| 5.3 File Transport and protocol .....                            | 16 |
+| 5.3.1 Basic file transport mechanism .....                       | 16 |
+| 5.3.2 Use of File Transfer IRP.....                              | 16 |
+| 5.3.3 Use of IPDR .....                                          | 16 |
+| 5.4 File transfer modes and session management .....             | 17 |
+| 5.4.1 Basic file transfer mechanism.....                         | 17 |
+| 5.4.1.1 Push mode.....                                           | 17 |
+| 5.4.1.2 Pull mode .....                                          | 17 |
+| 5.4.2 Use of File Transfer IRP.....                              | 17 |
+| 5.4.3 Use of IPDR .....                                          | 17 |
+| 6 CDR file format specification.....                             | 18 |
+| 6.1 File format conventions.....                                 | 18 |
+| 6.1.1 CDR file header format .....                               | 19 |
+| 6.1.1.1 File length .....                                        | 19 |
+| 6.1.1.2 Header length.....                                       | 19 |
+| 6.1.1.3 High release / version identifier.....                   | 19 |
+| 6.1.1.4 Low release / version identifier .....                   | 19 |
+| 6.1.1.5 File opening timestamp.....                              | 20 |
+| 6.1.1.6 Last CDR append timestamp .....                          | 20 |
+| 6.1.1.7 Number of CDRs in file.....                              | 20 |
+| 6.1.1.8 File sequence number .....                               | 20 |
+| 6.1.1.9 File Closure Trigger Reason.....                         | 20 |
+| 6.1.1.10 Node IP address .....                                   | 21 |
+| 6.1.1.11 Lost CDR indicator.....                                 | 21 |
+| 6.1.1.12 Length of CDR routeing filter .....                     | 21 |
+| 6.1.1.13 CDR routeing filter .....                               | 21 |
+| 6.1.1.14 Length of private extension .....                       | 22 |
+| 6.1.1.15 Private extension.....                                  | 22 |
+| 6.1.1.16 High release identifier extension .....                 | 22 |
+| 6.1.1.17 Low release identifier extension .....                  | 22 |
+| 6.1.2 CDR header format.....                                     | 22 |
+| 6.1.2.1 CDR length .....                                         | 22 |
+| 6.1.2.2 Release Identifier .....                                 | 23 |
+| 6.1.2.3 Version Identifier.....                                  | 23 |
+| 6.1.2.4 Data Record Format.....                                  | 23 |
+| 6.1.2.5 TS number.....                                           | 23 |
+| 6.1.2.6 Release Identifier extension.....                        | 24 |
+| 6.2 CDR file naming convention.....                              | 24 |
+| 6.3 Detailed FTP transfer and session management procedures..... | 25 |
+| 6.4 Error handling .....                                         | 25 |
+
+|                               |                                                                                                                                         |           |
+|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <b>Annex A (informative):</b> | <b>Bibliography ...................................................................................................................</b> | <b>27</b> |
+| Annex B (informative):        | Change history...................................................................................................................       | 28        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# --- 1 Scope
+
+The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks(GSM/UMTS/EPS). The 3GPP core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain / subsystem / service (offline charging),
+- the content of real-time charging messages per domain / subsystem / service (online charging);
+- the functionality of online and offline charging for those domains / subsystems / services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events)
+
+The complete document structure for these TSs is defined in TS 32.240 [1].
+
+The present document specifies the transaction based mechanism for the near real time transfer of CDRs within the network.
+
+The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240 [1];
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51];
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the post-processing system or a mediation device) is specified in TS 32.297 [52];
+
+The 3GPP Diameter application that is used for offline and online charging is specified in TS 32.299 [50].
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP domains services, or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [101].
+
+# --- 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.240: "Telecommunication management; Charging management; Charging architecture and principles".
+- [2]-[9] Void.
+- [10] 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain charging".
+- [11] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
+
+- [12] 3GPP TS 32.252: "Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging".
+- [13]-[19] Void
+- [20] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
+- [21]-[29] Void.
+- [30] 3GPP TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging".
+- [31] 3GPP TS 32.271: "Telecommunication management; Charging management; Location Services (LCS) charging".
+- [32] 3GPP TS 32.272: "Telecommunication management; Charging management; Push-to-talk over Cellular (PoC) charging".
+- [33] 3GPP TS 32.273: "Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging".
+- [34] 3GPP TS 32.275: "Telecommunication management; Charging management; Multimedia Telephony (MMTel) charging".
+- [35]-[49] Void.
+- [50] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging application".
+- [51] 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) encoding rules description".
+- [52] Void.
+- [53] 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS) applications and interfaces".
+- [54] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
+- [55]-[99] Void.
+- [100] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [101] 3GPP TS 22.115 "Service aspects; Charging and billing".
+- [102]-[199] Void.
+- [200] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2".
+- [201]-[399] Void
+- [400] IETF RFC 959 (1985): "File Transfer Protocol".
+- [401] ATIS-PP-0300075.1.200X "Usage Data Management for Packet-Based Services - Service Neutral Protocol Specification for Billing Applications"
+- [402] IPDR "IPDR/File Transfer Protocol"
+- [403] IPDR "IPDR/SP Protocol Specification"
+- [404]-[499] Void.
+- [500] 3GPP TS 32.341: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Requirements".
+
+- [501] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
+- [502] 3GPP TS 32.343: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
+- [503] 3GPP TS 32.344: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [100], 3GPP TS 32.240 [1] and the following apply:
+
+**Billing Domain:** part of the operator network, which is outside the telecommunication network that receives and processes charging information from the core network charging functions. It includes functions that can provide billing mediation and billing or other (e.g. statistical) end applications. It is only applicable to offline charging (see "Online Charging System" for equivalent functionality in online charging).
+
+**CDR field Categories:** defined in the middle tier charging TSs. CDR fields may be operator provisionable and are divided into the following categories:
+
+- **Mandatory (M):** field that shall always be present in the CDR.
+- **Conditional (C):** field that shall be present in a CDR if certain conditions are met.
+- **Operator Provisionable: Mandatory (O<sub>M</sub>):** field that, if provisioned by the operator, shall always be present in the CDR.
+- **Operator Provisionable: Conditional (O<sub>C</sub>):** field that, if provisioned by the operator, shall be present in a CDR if certain conditions are met.
+
+**charging:** function within the telecommunications network and the associated OCS/BD components whereby information related to a chargeable event is collected, formatted, transferred and evaluated in order to make it possible to determine usage for which the charged party may be billed (offline charging) or the subscriber's account balance may be debited / credited (online charging).
+
+**Charging Data Record (CDR):** formatted collection of information about one or more chargeable event(s) (e.g. time of call set-up, duration of the call, amount of data transferred, etc) for use in billing and accounting. For each party to be charged for parts of or all charges of the chargeable event(s) a separate CDR shall be generated, i.e. more than one CDR may be generated for a single chargeable event, e.g. because of its long duration, or because more than one charged party is to be charged.
+
+**charging function:** entity inside the core network domain, subsystem or service that is involved in charging for that domain, subsystem or service.
+
+**circuit switched domain:** domain within GSM / UMTS in which information is transferred in circuit switched mode.
+
+**domain:** part of the 3GPP telecommunication network that provides network resources using a certain bearer technology.
+
+**GPRS:** packet switched bearer and radio services for GSM and UMTS systems.
+
+**middle tier (charging) TS:** term used for the 3GPP charging TSs that specify the domain / subsystem / service specific, online and offline, charging functionality. These are all the TSs in the numbering range from 3GPP TS 32.250 to 3GPP TS 32.279, e.g. 3GPP TS 32.250 [10] for the CS domain, or 3GPP TS 32.270 [30] for the MMS service. Currently, there is only one "tier 1" charging TS in 3GPP, which is TS 32.240 [1] that specifies the charging architecture and principles. Finally, there are a number of top tier charging TSs in the 32.29x numbering range ([50] ff) that specify common charging aspects such as parameter definitions, encoding rules, the common billing domain interface or common charging applications.
+
+**near real-time:** near real-time charging and billing information is to be generated, processed, and transported to a desired conclusion in less than 1 minute.
+
+**offline charging:** charging mechanism where charging information **does not** affect, in real-time, the service rendered
+
+**online charging:** charging mechanism where charging information **can** affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with session/service control is required.
+
+**packet switched domain:** domain in which data is transferred between core network elements.
+
+**real-time:** real-time charging and billing information is to be generated, processed, and transported to a desired conclusion in less than 1 second.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|     |                                                                                                             |
+|-----|-------------------------------------------------------------------------------------------------------------|
+| Bc  | Reference point for the CDR file transfer from the Circuit Switched CGF to the BD.                          |
+| Bi  | Reference point for the CDR file transfer from the IMS CGF to the BD.                                       |
+| Bl  | Reference point for the CDR file transfer from the GMLC CGF to the BD.                                      |
+| Bm  | Reference point for the CDR file transfer from the MMS CGF to the BD.                                       |
+| Bmb | Reference point for the CDR file transfer from the MBMS CGF to the BD.                                      |
+| Bo  | Reference point for the CDR file transfer from the OCF CGF to the BD.                                       |
+| Bp  | Reference point for the CDR file transfer from the Packet Switched CGF to the BD.                           |
+| Bs  | Reference point for the CDR file transfer for CAMEL services to the BD, i.e. from the SCF CGF to the BD.    |
+| Bt  | Reference point for the CDR file transfer from the PoC CGF to the BD.                                       |
+| Bw  | Reference point for the CDR file transfer from the I-WLAN CGF to the BD.                                    |
+| Bx  | Reference point for CDR file transfer between any (generic) 3G domain, subsystem or service CGF and the BD. |
+| Ga  | Reference point for CDR transfer between a CDF and the CGF.                                                 |
+| Rf  | Offline Charging Reference Point between the CTF within a 3G network entity and the CDF.                    |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                           |
+|---------|-----------------------------------------------------------|
+| bcd     | binary coded decimal                                      |
+| BD      | Billing Domain                                            |
+| CAMEL   | Customised Applications for Mobile network Enhanced Logic |
+| CDF     | Charging Data Function                                    |
+| CDR     | Charging Data Record                                      |
+| CGF     | Charging Gateway Function                                 |
+| CS      | Circuit Switched                                          |
+| CTF     | Charging Trigger Function                                 |
+| EPS     | Evolved Packet System                                     |
+| E-UTRAN | Evolved Universal Terrestrial Radio Access Network        |
+| FTP     | File Transfer Protocol                                    |
+| GMLC    | Gateway MLC                                               |
+| GPRS    | General Packet Radio Service                              |
+| IMS     | IP Multimedia Subsystem                                   |
+| IP      | Internet Protocol                                         |
+| IPDR    | Internet Protocol Detail Record                           |
+| I-WLAN  | Interworking WLAN                                         |
+| LAN     | Local Area Network                                        |
+| MBMS    | Multimedia Broadcast/Multicast Service                    |
+| MLC     | Mobile Location Center                                    |
+| MMS     | Multimedia Messaging Service                              |
+| OAM&P   | Operation, Administration, Maintenance and Provisioning   |
+| OCF     | Online Charging Function                                  |
+| OCS     | Online Charging System                                    |
+| PoC     | Push-to-talk over Cellular                                |
+| PS      | Packet Switched                                           |
+| SCF     | Service Control Function                                  |
+| UTC     | Universal Time Coordinated                                |
+| WLAN    | Wireless LAN                                              |
+
+# 4 Architecture considerations
+
+"Bx" is a common designator for the reference points from the network to the billing domain (BD) that are intended for the transport of CDR files. The letter "x" indicates the different 3GPP network domain, subsystem or service, where
+
+- c represents Circuit Switched (CS) in TS 32.250 [10],
+- p represents Packet Switched (PS) in TS 32.251 [11],
+- i represents IP Multimedia Subsystem (IMS) in TS 32.260 [20],
+- l represents Location Service (LCS) in TS 32.271 [31],
+- m represents Multimedia Messaging Service (MMS) in TS 32.270 [30],
+- mb represents Multimedia Broadcast/Multicast Service (MBMS) in TS 32.273 [33],
+- o represents the Online Charging System (OCS) in TS 32.296 [53],
+- t represents the PoC service (PoC) in TS 32.272 [32],
+- s represents the CAMEL SCF in TS 23.078 [200], and
+- w represents interworking Wireless LAN (I-WLAN) in TS 32.252[12].
+
+By definition, dealing with CDR files only implies that Bx is solely related to offline charging. The following figure depicts the position of the Bx reference point within the overall 3GPP offline charging architecture.
+
+![Figure 4.1: Logical ubiquitous offline charging architecture diagram. The diagram shows the 3GPP network (grey box) containing three domains: CN Domain (yellow), Service nodes (orange), and Sub-system (magenta). Each domain contains a Charging Trigger Function (CTF, pink), a Charging Data Function (CDF, green), and a Charging Gateway Function (CGF, orange). The CGF in each domain is connected to the Billing Domain (blue box) via the Bx reference point. The Bx reference point is shown as a line with a break and a label 'Bx'.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+The diagram illustrates the logical ubiquitous offline charging architecture. A large grey box labeled "3GPP network" contains three stacked colored areas: a yellow "CN Domain", an orange "Service nodes" area, and a magenta "Sub-system" area. Within each area, there are vertical bars representing functions: a pink bar for CTF (Charging Trigger Function), a green bar for CDF (Charging Data Function), and an orange bar for CGF (Charging Gateway Function). Lines labeled "Rf" connect the CTF to the CDF. Lines labeled "Ga" connect the CDF to the CGF. All three CGFs (one in each domain) are connected to a single blue box on the right labeled "Billing Domain" via a common line labeled "Bx".
+
+Figure 4.1: Logical ubiquitous offline charging architecture diagram. The diagram shows the 3GPP network (grey box) containing three domains: CN Domain (yellow), Service nodes (orange), and Sub-system (magenta). Each domain contains a Charging Trigger Function (CTF, pink), a Charging Data Function (CDF, green), and a Charging Gateway Function (CGF, orange). The CGF in each domain is connected to the Billing Domain (blue box) via the Bx reference point. The Bx reference point is shown as a line with a break and a label 'Bx'.
+
+**CTF:** Charging Trigger Function  
+**CDF:** Charging Data Function  
+**CGF:** Charging Gateway Function  
+**BD:** Billing Domain. This may also be a billing system/ billing mediation device.
+
+**Figure 4.1: Logical ubiquitous offline charging architecture**
+
+As illustrated in figure 4.1, the CGF in each network domain, service or subsystem is relevant for the network side of the Bx reference point and is connected with the BD that forms the receiving end of the Bx reference point. Further details of the Billing Domain, i.e. beyond terminating Bx, are outside the scope of 3GPP standardization. Refer to 3GPP TS 32.240 [1] for the complete description of the 3GPP charging architecture.
+
+Note that the OCS can also generate CDRs and transfer them to the BD across the Bo reference point (not depicted in figure 4.1). Refer to 3GPP TS 32.296 [53] for further information on the OCS.
+
+Furthermore the GSM SCF, defined in CAMEL, can also generate CDRs and transfer them to the BD across the Bs reference point (not depicted in figure 4.1). Refer to 3GPP TS 23.078 [200] for further information on CAMEL.
+
+# 5 CDR File Transfer Principles and Scenarios
+
+This clause contains specifications for the principles and scenarios covering the CDR file transfer interface from the network to the Billing Domain. These specifications apply to all domains, subsystems and services that are listed in clause 4, including the OCS Bo and the GSM SCF's Bs interface. Alternatively, in the CS domain (i.e. for Bc), the file transfer mechanism specified in 3GPP TS 32.250 [10] may be used. Consequently, for Bc it is up to implementation choice to provide either the legacy interface, the interface specified in the present document, or both.
+
+The scenarios in this clause are divided into the following categories:
+
+- Local CDR and CDR file handling;
+- File format principles;
+- File Transport and protocol;
+- File transfer modes and session management.
+
+Other interface principles such as security and performance are dependent on vendor implementation and operator's network design and are not covered by the present document.
+
+## 5.1 Local CDR and CDR file handling
+
+### 5.1.1 CDR processing
+
+As depicted in figure 4.1. above, the CGF collects CDRs from the CDF. If the CDF and the CGF are separate entities, then the standard Ga interface as specified in 3GPP TS 32.295 [54] is used to transfer the CDRs from the CDF to the CGF. If CDF and CGF are integrated, then a proprietary, internal mechanism is used. The possibilities of separate or integrated CDF and CGF are specified per domain, subsystem and service in the respective "middle tier" charging TS, i.e. those in the [10] through [49] reference number range, and in TS 32.296 [53] for the OCS.
+
+In any case, CDRs are transferred, in near real time, from the CDF to the CGF as soon as they have been closed by the CDF. Refer to 3GPP TS 32.295 [54] for further details. Once received by the CGF, the CDRs may undergo semantical and/or syntactical sanity checks, however, these checks are not specified further within the present document.
+
+If the CGF determines that a CDR is not well formatted, or otherwise incorrect, then the defective CDR parameter(s) shall be filled with an appropriate "replacement" indicator within the limits of the syntax allowed for the parameter. If the error renders the complete CDR unusable (i.e. the above replacement of erroneous parameters is not possible), then no further action of the CGF can be performed regarding this CDR. An example of a case where the erroneous parameter cannot be replaced is when the "CDR type" attribute of a CDR received by the CGF is corrupted. Details of this function are implementation specific.
+
+CDRs that have been processed by the CGF without error, or where errors have been corrected by the CGF as described above, are considered "acceptable" by the CGF. CDRs that have non-recoverable errors are not considered "acceptable" by the CGF. The "acceptable" CDRs are immediately placed into a CDR file by the CGF. The CDRs that are not "acceptable" should be properly reflected in an error log and appropriate alarms should be generated, after which they may be destroyed. Furthermore, to the extent possible, the number of lost CDRs and the fact that CDRs were lost, shall be indicated in the CDR file.
+
+It is acknowledged that the processing of a CDR between being received until it is placed on the CDR file, will take a small amount of time. Hence, where the present document mandates the "immediate" treatment of CDRs received by the CGF, it is to be interpreted such that it is not allowed to postpone the processing of any received CDRs for any reason. In technical terms, "immediate" shall be interpreted as
+
+- The system shall be capable of complying with near real time requirements as specified in subclause 3.1.
+- The system should be capable of complying, as closely as possible, with real time requirements as specified in subclause 3.1.
+
+Once a CDR has been stored on the appropriate file, the CGF may destroy any other reference to that CDR.
+
+### 5.1.2 CDR routeing
+
+In the default mode of operation, the CGF manages a single ("default") file for the storage of all "acceptable" CDRs. However, the CGF may also route CDRs to different files that are kept open concurrently, i.e. additional files may be configured by OAM&P commands together with associated CDR routeing filters. While the CGF will store only those CDRs matching the associated routeing filter on each of the additional files, the default file is used to store all CDRs that do not match any of the routeing filters configured for the additional files.
+
+The CDR routeing function shall apply CDR parameters and CDR origin to decide into which file to place the CDR. The file name shall, within the limits of the file naming conventions, contain an indication of the CDR routeing filter applied.
+
+As a minimum, each CGF implementation shall support the CDR type and the sending CDF as selection criteria for CDR routeing. It shall then be possible to include in a file only the following CDRs:
+
+- CDRs of a single type;
+- CDRs of a set of specified types (e.g. only IMS CDR types);
+- CDRs originated by a single CDF;
+- CDRs originated by a set of CDFs;
+- Any combination of the above.
+
+Further details of the CDR routeing function, such as
+
+- the maximum number of simultaneously open CDR files;
+- the order in which the routeing filters are evaluated;
+- the way CDR filters can be configured by OAM&P;
+
+are implementation specific. In order to avoid arbitrary routeing of CDRs, operators should assure that the routeing filters assigned per file, do not overlap with each other.
+
+The term "matching CDR" is used in the present document to denote a CDR that matches the routeing filter of a given CDR file.
+
+### 5.1.3 Local CDR file management
+
+For the default case, plus each of the additional CDR routeing filters that may be set up on the CGF (cf. subclause 5.1.2 above), the CGF provides a non-interrupted chain of CDR files. As described above, each CDR is immediately stored in the appropriate file after being received and determined "acceptable" by the CGF.
+
+Several conditions may govern the closure of a CDR file by the CGF:
+
+- A configurable file size limit;
+- A configurable file closure time;
+- A configurable file lifetime ("interval");
+- A configurable number of CDRs within the file;
+- CDR release, version or encoding change;
+- Manual OAM&P actions;
+- System defined reasons (e.g. file system full).
+
+When a CDR file is closed, the next matching CDR shall be placed in the next file in the chain. The exact time when this next CDR file is physically generated, i.e.:
+
+- immediately after the previous file has been closed (i.e. the earliest possible time),
+
+- when the next matching CDR arrives (i.e. the latest possible time),
+- anytime in between,
+
+is implementation specific. However, each CDR file must contain all "acceptable" matching CDRs received and processed by the CGF between the closure of the previous file and the configured file closure trigger of the current file, as specified above. In any case, a file must be generated and closed upon the occurrence of the file closure trigger, i.e. an empty file (containing no CDRs) if no matching CDRs arrived since the closure of the last file in the chain. Upon file closure, the CDR file is immediately available for transfer to the BD.
+
+CDR files may be removed from the CGF in one of the following ways:
+
+- By the BD issuing corresponding commands provided by the file transfer protocol;
+- By the CGF application once the file has been transferred;
+- Due to CGF file system storage limitation or configurable file age limits;
+- OAM&P action.
+
+In order to avoid loss of CDRs, Operators should manage the system in a way that the "system defined" file closure triggers mentioned above do not occur.
+
+## 5.2 File format principles
+
+The CDR file format is depicted below.
+
+![Diagram of CDR File Format showing a header followed by concatenated CDRs.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+The diagram illustrates the structure of a CDR file. At the top is a yellow rectangular block labeled **Header with Specified Length**. Below this header is a vertical stack of light blue rectangular blocks representing concatenated CDRs. The first five blocks are labeled **CDR 1**, **CDR 2**, **CDR 3**, **CDR 4**, and **CDR 5** respectively. A vertical ellipsis (three dots) is shown between the fifth and the final block, indicating that there can be any number of CDRs. The final block is labeled **CDR n**. To the left of the stack of CDR blocks, a large curly brace groups them together and is labeled **Concatenated CDRs**.
+
+Diagram of CDR File Format showing a header followed by concatenated CDRs.
+
+**Figure 5.2.1: CDR File Format**
+
+The CDR files contain a variable length header section followed by a variable sized CDR data section. The CDR data section contains zero or more concatenated CDRs. Each CDR in a file includes a header indicating the CDR length, data record format, release, version and encoding scheme.
+
+The BD should use a decoder with a version number which is equal or greater of this version to be able to decode all the CDRs in the file.
+
+Clause 6 of the present document specifies the file format applying the above principles at bit level detail.
+
+## 5.3 File Transport and protocol
+
+Two mechanisms are defined for the transport of CDR files from the CGF to the BD:
+
+- A basic transport mechanism is defined in subclause 5.3.1 and must be supported by all CGF implementations;
+- The use of the File Transfer IRP as described in subclause 5.3.2 may additionally be supported by the CGF as an implementation option.
+
+The use of IPDR as described in subclause 5.3.3 may optionally be supported on the Bx reference point.
+
+### 5.3.1 Basic file transport mechanism
+
+The following stipulations govern the choice and usage of file transport protocol for this transport mechanism.
+
+- a) The default protocol for CDR file transport is FTP (RFC 959 [400]).
+- b) The use of other protocols is optional, however FTP must always be supported.
+- c) The CDR files may be transferred in either push or pull mode on the Bx interface. Further specifications of these transfer modes are provided in subclause 5.4.1 and subclause 5.4.2, respectively.
+- d) All standard FTP commands specified in RFC 959 [400] shall be supported by the CGF.
+
+All further requirements specified within the present document with reference to the operation of the file transfer protocol in this mechanism (cf. clause 6), are solely related to FTP as the transfer protocol, as no assumptions can be made as to the ways of working of optional other protocols. However, additional protocols shall be implemented such that, to the extent possible, the same logic is applied as described in the present document for FTP.
+
+### 5.3.2 Use of File Transfer IRP
+
+The File Transfer IRP is specified in 3GPP TSs 32.341 [500], 32.342 [501], 32.343 [502] and 32.344 [503]. The support of the solution sets (CORBA, CMIP or both) is left to implementation choice. Otherwise, the CGF implementation of the IRP shall comply with the above TSs, i.e. there are no further additions or limitations with regard to the use of the IRP in charging.
+
+### 5.3.3 Use of IPDR
+
+As depicted in ATIS-PP-0300075.1.200X [401] IPDR file transfer or streaming protocol can be used for the Bx reference point.
+
+The IPDR file transfer is specified in IPDR/File Transfer Protocol [402]. The IPDR streaming protocol is specified in IPDR/SP [403].
+
+## 5.4 File transfer modes and session management
+
+### 5.4.1 Basic file transfer mechanism
+
+Files can be transferred to the BD in one, or both, of the following modes. Detailed FTP file transfer and session management procedures are specified in clause 6.
+
+#### 5.4.1.1 Push mode
+
+In this transfer mode the CDR files are written from the CGF to the BD filestore at a time and/or frequency controlled by the CGF. I.e. the CGF *pushes* the files to the BD. This implies that the CGF operates in client mode and the BD in server mode. If the CGF generates concurrent CDR files based on the CDR routeing function specified in subclause 5.1.2, then it shall be able to send the different files to different BD systems, i.e. the BD address is part of the CDR file routeing filter.
+
+As a minimum, the following events shall be capable of triggering a file push in the CGF:
+
+- A (configured number of) new CDR file(s) has become available for transmission;
+- The CDR file / files has / have exceeded a configurable (total) size limit;
+- A configurable, regular time interval has elapsed;
+- The CGF filestore utilization has exceeded a configurable level.
+
+If the file transfer fails, the CGF should properly reflect this in an error log and generate appropriate alarms. Possible measures to handle file transfer failures are discussed in clause 6.
+
+Security measures, e.g. the mutual identification / verification of the peer systems, are outside the scope of the present document.
+
+#### 5.4.1.2 Pull mode
+
+In this transfer mode the BD reads the CDR files that are available in the appropriate CGF directories. The time and/or frequency of the file transfer is controlled by the BD. I.e. the BD *pulls* the files from the CGF. This implies that the CGF operates in server mode and the BD in client mode.
+
+In this mode, the BD may request the files from the CGF at any point in time at the discretion of the BD, i.e. the CGF cannot make any assumptions of the time or frequency of the file pull to occur. If the file transfer fails, any further action is up to the BD, however, the CGF should properly reflect this in an error log and generate appropriate alarms. Possible measures to handle file transfer failures are discussed in clause 6.
+
+Security measures, e.g. the mutual identification / verification of the peer systems, are outside the scope of the present document.
+
+### 5.4.2 Use of File Transfer IRP
+
+File transfer modes and session management using the optional File Transfer IRP are governed by 3GPP TSs 32.341 [500], 32.342 [501], 32.343 [502] and 32.344 [503].
+
+### 5.4.3 Use of IPDR
+
+File transfer mode and session management using the optional IPDR protocols are governed by IPDR File Transfer [402] or streaming protocol [403].
+
+# --- 6 CDR file format specification
+
+This clause provides detail specifications for the CDR file format. These specifications apply to all domains, subsystems and services listed in clause 4. Alternatively, in the CS domain (i.e. for Bc), the file transfer mechanism specified in 3GPP TS 32.250 [10] may be used. Consequently, for Bc it is up to implementation choice to provide either the legacy interface, the interface specified in the present document, or both.
+
+The file format specification in this clause is divided into the following categories:
+
+- File format conventions;
+- File naming and directory conventions;
+- Detailed file transfer and session management procedures.
+- Error handling
+
+Only the basic file transfer mechanism is covered in the present document. Refer to 3GPP TSs 32.341 [500], 32.342 [501], 32.343 [502] and 32.344 [503] for the corresponding details when using the optional File Transfer IRP and [402], [403] when using the optional IPDR protocols.
+
+## 6.1 File format conventions
+
+The file format shall apply the following conventions.
+
+- a) The CDR files contain a variable length file header immediately followed by a variable number (zero or more) of concatenated CDRs which are structured according to the CDR format specified in the middle tier charging TSs.
+- b) The syntax and encoding rules for the CDRs are specified in 3GPP TS 32.298 [51].
+- c) Each CDR is immediately preceded by a fixed length plain text header.
+- d) The file header fields and CDR header fields are in Network byte order (Big Endian).
+- e) The file header contains fields specified in subclause 6.1.1.
+- f) The CDR header contains fields specified in subclause 6.1.2.
+- g) File header fields that are not known at the time the file is opened are populated after all the CDRs are included and the file is ready to be closed.
+
+The CDR file is named based on the naming convention specified in clause 6.2.
+
+### 6.1.1 CDR file header format
+
+The exact format of the CDR file header is given in table 6.1.1.
+
+**Table 6.1.1: Format of CDR File Header**
+
+| Octets     | Bits                                         |   |   |   |                         |   |   |   |  |  |  |  |
+|------------|----------------------------------------------|---|---|---|-------------------------|---|---|---|--|--|--|--|
+|            | 8                                            | 7 | 6 | 5 | 4                       | 3 | 2 | 1 |  |  |  |  |
+| 1..4       | File length                                  |   |   |   |                         |   |   |   |  |  |  |  |
+| 5..8       | Header length                                |   |   |   |                         |   |   |   |  |  |  |  |
+| 9          | High Release Identifier                      |   |   |   | High Version Identifier |   |   |   |  |  |  |  |
+| 10         | Low Release Identifier                       |   |   |   | Low Version Identifier  |   |   |   |  |  |  |  |
+| 11..14     | File opening timestamp                       |   |   |   |                         |   |   |   |  |  |  |  |
+| 15..18     | Timestamp when last CDR was appended to file |   |   |   |                         |   |   |   |  |  |  |  |
+| 19..22     | Number of CDRs in file                       |   |   |   |                         |   |   |   |  |  |  |  |
+| 23..26     | File sequence number                         |   |   |   |                         |   |   |   |  |  |  |  |
+| 27         | File Closure Trigger Reason                  |   |   |   |                         |   |   |   |  |  |  |  |
+| 28..47     | IP Address of Node that generated file       |   |   |   |                         |   |   |   |  |  |  |  |
+| 48         | Lost CDR indicator                           |   |   |   |                         |   |   |   |  |  |  |  |
+| 49..50     | Length of CDR routing filter                 |   |   |   |                         |   |   |   |  |  |  |  |
+| 51..xy     | CDR routing filter                           |   |   |   |                         |   |   |   |  |  |  |  |
+| xy+1..xy+2 | Length of Private Extension                  |   |   |   |                         |   |   |   |  |  |  |  |
+| xy+3..n    | Private Extension                            |   |   |   |                         |   |   |   |  |  |  |  |
+| n+1        | High Release Identifier extension            |   |   |   |                         |   |   |   |  |  |  |  |
+| n+2        | Low Release Identifier extension             |   |   |   |                         |   |   |   |  |  |  |  |
+
+The following subclauses specify the contents and encoding of the CDR file header fields. Unless otherwise specified in the subclauses below, all parameters are mandatory and shall always be included in a CDR file header.
+
+#### 6.1.1.1 File length
+
+The "file length" parameter contains a binary value that identifies the total length of the CDR file in octets, including the file header and the total CDR payload length.
+
+The value with all bits set to "1" is reserved for future extensions (e.g. for CDR files longer than that value) and shall therefore not be used.
+
+#### 6.1.1.2 Header length
+
+The "header length" parameter contains a binary value that identifies the total length of the CDR file header in octets.
+
+The value with all bits set to "1" is reserved for future extensions (e.g. for CDR file headers longer than that value) and shall therefore not be used.
+
+#### 6.1.1.3 High release / version identifier
+
+This field is a copy of octet 3 of the CDR header. It is copied from the CDR where the equation:
+
+$$\text{Release Identifier} * 100 + \text{Version Identifier}$$
+
+For Rel-10 and higher this equation shall be used:
+
+$$(\text{Release Identifier} + \text{Release Identifier Extension} + 1) * 100 + \text{Version Identifier}$$
+
+yields the highest result of all CDRs in the file. The representation of Release Identifier and Version Identifier in this field is the same as in octet 3 of the CDR header. For Rel-10 and higher, i.e with High Release Identifier field set to value "7", the release identifier is included in "High Release Identifier extension" field.
+
+#### 6.1.1.4 Low release / version identifier
+
+This field is a copy of octet 3 of the CDR header. It is copied from the CDR where the equation:
+
+$$\text{Release Identifier} * 100 + \text{Version Identifier}$$
+
+For Rel-10 and higher this equation shall be used:
+
+$$(\text{Release Identifier} + \text{Release Identifier Extension} + 1) * 100 + \text{Version Identifier}$$
+
+yields the lowest result of all CDRs in the file. The representation of Release Identifier and Version Identifier in this field is the same as in octet 3 of the CDR header. For Rel-10 and higher, i.e with Low Release Identifier field set to value "7", the release identifier is included in "Low Release Identifier extension" field.
+
+#### 6.1.1.5 File opening timestamp
+
+These parameters indicate the time when the file was opened, according to the following binary format:
+
+- The first four binary bits indicate the month (1 .. 12), according to the CGF's local time zone;
+- The next five binary bits contain the date (1 :: 31), according to the CGF's local time zone;
+- The next five binary bits contain the hour (0 .. 23), according to the CGF's local time zone;
+- The next six binary bits contain the minute (0 .. 59), according to the CGF's local time zone;
+- The next bit indicates the sign of the local time differential from UTC (bit set to "1" expresses "+" or bit set to "0" expresses "-" time deviation), in case the time differential to UTC is 0 then the sign may be arbitrarily set to "+" or "-";
+- The next five binary bits contain the hour (0 .. 23) deviation of the local time towards UTC, according to the CGF's local time zone;
+- The next six binary bits contain the minute (0 .. 59) deviation of the local time towards UTC, according to the CGF's local time zone;
+
+Note that the CDR file name contains detailed date and time information related to file closure (cf. clause 6.2)
+
+#### 6.1.1.6 Last CDR append timestamp
+
+This parameter is formatted the same as in 6.1.1.5, and indicates the time when the last CDR was appended to the file in UTC format. In case of an empty file (i.e. no CDRs included), the value of the parameter is "0".
+
+#### 6.1.1.7 Number of CDRs in file
+
+This parameter contains a binary value that specifies the total number of CDRs that are included in the file.
+
+The value with all bits set to "1" is reserved for future extensions (e.g. for CDR files containing more CDRs than represented by that value) and shall therefore not be used.
+
+#### 6.1.1.8 File sequence number
+
+This parameter is a value in binary that contains a running number of the CDR file generated by the same CGF. The first file of a CGF is indicated by the value "0". When the maximum number of file is reached (all bits set to "1"), the sequence shall be restarted with "0".
+
+#### 6.1.1.9 File Closure Trigger Reason
+
+The file closure reason provides a means to determine the reason that the file was closed by the CGF. It is encoded as a single octet as follows.
+
+Normal closure reasons (Binary values 0 to 127):
+
+- 0 = Normal closure (Undefined normal closure reason).
+- 1 = File size limit reached (OA&M configured).
+- 2 = File open-time limit reached (OA&M configured).
+- 3 = Maximum number of CDRs in file reached (OA&M configured).
+- 4 = File closed by manual intervention.
+- 5 = CDR release, version or encoding change.
+- 6 to 127 are reserved for future use.
+
+Abnormal closure reasons (Binary values 128 to 255):
+
+- 128 = Abnormal file closure (Undefined error closure reason).
+- 129 = File system error.
+- 130 = File system storage exhausted.
+- 131 = File integrity error.
+- 132 to 255 are reserved for future use.
+
+#### 6.1.1.10 Node IP address
+
+This parameter indicates the IP address of the CGF generating the file. For both IPv4 and IPv6 CGF addresses, the parameter is encoded in IPv6 representation. The first four bytes of the parameter, which are preceding this IPv6 address, are insignificant, e.g. filled with 'FF'.
+
+#### 6.1.1.11 Lost CDR indicator
+
+This parameter indicates if and how many CDRs were lost during their processing in the CGF (cf. clause 5.1.1). The term "lost" implies that the CDR(s) could not be placed into the destination file due to irrecoverable errors.
+
+Due to the possibility that the irrecoverable CDR errors may have impacted CDR parameters that are relevant for CDR routing, it is possible that the CGF cannot determine for a particular file whether CDRs have been lost. Appropriate indication shall be given according to the following encoding of the "lost CDR indicator".
+
+- MSB bit "0", all other bits "0": no CDRs have been lost;
+
+- MSB bit "0", all other bits set to a value corresponding to decimal 1 to decimal 126: CGF has identified that a number of CDRs corresponding to the value of the lower 7 bits were lost, while it is unknown whether more CDRs were lost;
+- MSB bit "0", all other bits set to "1": CGF has identified that 127 or more CDRs were lost, while it is unknown whether more CDRs were lost;
+- MSB bit "1", all other bits "0": CDRs have been lost but CGF cannot determine the number of lost CDRs;
+- MSB bit "1", all other bits set to a value corresponding to decimal 1 to decimal 126: CGF has calculated the number of lost CDRs as indicated in the value of the lower 7 bits;
+- MSB bit "1", all other bits set to "1": CGF has calculated the number of lost CDRs to be 127 or more.
+
+#### 6.1.1.12 Length of CDR routeing filter
+
+This parameter contains a binary value that specifies the length of the subsequent CDR routeing filter in octets. The value excludes the two octets of the "length" parameter itself.
+
+The value of "65535" (all bits set to "1") is reserved for future extensions (e.g. for CDR routeing filters longer than 65534 octets) and shall therefore not be used.
+
+#### 6.1.1.13 CDR routeing filter
+
+This parameter indicates the filter that determined the routeing of CDRs into this file. Its encoding is vendor specific.
+
+#### 6.1.1.14 Length of private extension
+
+This parameter contains a binary value that specifies the length of the subsequent "private extension" field in octets. It is present only if a private extension field is included in the CDR file header. Its value excludes the two octets of the "length" parameter itself.
+
+The value of "65535" (all bits set to "1") is reserved for future extensions (e.g. for private extensions longer than 65534 octets) and shall therefore not be used.
+
+#### 6.1.1.15 Private extension
+
+This optional field contains a vendor specific private extension to the CDR file header, if any. Its encoding, if present, is vendor specific.
+
+#### 6.1.1.16 High release identifier extension
+
+This eight bit field contains a binary value that identifies the 3GPP Release of the TS 32.298 [51] for High Release Identifier beyond Rel-9: the representation of High Release Identifier in this field is the same as in Octet 5 of CDR header.
+
+This field shall be present only when "High Release Identifier" field is set with value "7" (all bits set to "1").
+
+#### 6.1.1.17 Low release identifier extension
+
+This eight bit field contains a binary value that identifies the 3GPP Release of the TS 32.298 [51] for Low Release Identifier beyond Rel-9: the representation of Low Release Identifier in this field is the same as in Octet 5 of CDR header.
+
+This field shall be present only when "Low Release Identifier" field is set with value "7" (all bits set to "1").
+
+### 6.1.2 CDR header format
+
+The exact format of the CDR header is given in table 6.1.2.
+
+**Table 6.1.2: Format of CDR Header**
+
+| Octets | Bits                         |   |   |   |                    |   |   |   |
+|--------|------------------------------|---|---|---|--------------------|---|---|---|
+|        | 8                            | 7 | 6 | 5 | 4                  | 3 | 2 | 1 |
+| 1..2   | CDR length                   |   |   |   |                    |   |   |   |
+| 3      | Release Identifier           |   |   |   | Version Identifier |   |   |   |
+| 4      | Data Record Format           |   |   |   | TS number          |   |   |   |
+| 5      | Release Identifier extension |   |   |   |                    |   |   |   |
+
+The following subclauses specify the contents and encoding of the CDR header fields.
+
+The CDR header is 4 octets or 5 octets length: presence the Release Identifier extension octet depends on Release Identifier value.
+
+#### 6.1.2.1 CDR length
+
+This two octet field contains a binary value that specifies the length of the subsequent CDR, excluding the header octets. The value of "65535" (all bits set to "1") in the CDR length field implies that it is reserved for future extensions and shall therefore not be used.
+
+#### 6.1.2.2 Release Identifier
+
+This three bit field contains a binary value that identifies the 3GPP Release of the Technical Specification indicated in "TS number" (see clause 6.1.2.5). Its value is set / used according to the following rules:
+
+**Table 6.1.2.2: Release Identifier**
+
+| Release Identifier (3 bits) | 3GPP Release | Indicates 3GPP "TS number" for the release                                           | Comment                                |
+|-----------------------------|--------------|--------------------------------------------------------------------------------------|----------------------------------------|
+| "0"                         | Rel-99       | 32.005 or 32.015                                                                     | this parameter shall be ignored        |
+| "1"                         | Rel-4        | 32.205, 32.215 or 32.235                                                             |                                        |
+| "2"                         | Rel-5        | 32.205, 32.215, 32.225 or 32.235                                                     |                                        |
+| "3"                         | Rel-6        | 32.250, 32.251, 32.252, 32.260, 32.270, 32.271, 32.272 or 32.273                     |                                        |
+| "4"                         | Rel-7        | 32.250, 32.251, 32.252, 32.260, 32.270, 32.271, 32.272 or 32.273                     |                                        |
+| "5"                         | Rel-8        | 32.250, 32.251, 32.252, 32.260, 32.270, 32.271, 32.272 , 32.273 or 32.275            |                                        |
+| "6"                         | Rel-9        | 32.250, 32.251, 32.252, 32.260, 32.270, 32.271, 32.272 , 32.273, 32.274 or 32.275    |                                        |
+| "7"                         | Beyond Rel-9 | The 3GPP Release for "TS number" is included in "Release Identifier extension" field | this parameter is used as an indicator |
+
+#### 6.1.2.3 Version Identifier
+
+This five bit field contains a binary value that identifies the version of the TS 32.298 [51]. Its value corresponds to the middle digit of the version number of that TS, as indicated on the TS cover sheet.
+
+#### 6.1.2.4 Data Record Format
+
+This three bit field contains a binary value that identifies the CDR encoding according to the following table:
+
+- "1" signifies the use of Basic Encoding Rules (BER);
+- "2" signifies the use of unaligned basic Packed Encoding Rules (PER);
+- "3" signifies the use of aligned basic Packed Encoding Rules (PER);
+- "4" signifies the use of XML Encoding Rules (XER).
+
+#### 6.1.2.5 TS number
+
+This five bit field contains a binary value that identifies the number of the TS associated to the domain CDRs encoding according to table 6.1.2.5:
+
+**Table 6.1.2.5: "TS number" Identifier**
+
+| "TS number" Identifier (5 bits) | TS number |
+|---------------------------------|-----------|
+| 0                               | 32.005    |
+| 1                               | 32.015    |
+| 2                               | 32.205    |
+| 3                               | 32.215    |
+| 4                               | 32.225    |
+| 5                               | 32.235    |
+| 6                               | 32.250    |
+| 7                               | 32.251    |
+| 8                               | 32.252    |
+| 9                               | 32.260    |
+| 10                              | 32.270    |
+| 11                              | 32.271    |
+| 12                              | 32.272    |
+| 13                              | 32.273    |
+| 14                              | 32.275    |
+| 15                              | 32.274    |
+| NOTE: 16-31 are for future use. |           |
+
+#### 6.1.2.6 Release Identifier extension
+
+This eight bit field contains a binary value that identifies the 3GPP Release of the TS 32.298 [51], for Releases beyond Rel-9. Its value is set / used according to the following rules:
+
+**Table 6.1.2.6: Release Identifier extension**
+
+| Release Identifier (8 bits)                                                                            | 3GPP Release | Comment |
+|--------------------------------------------------------------------------------------------------------|--------------|---------|
+| "0"                                                                                                    | Rel-10       |         |
+| "1"                                                                                                    | Rel-11       |         |
+| NOTE: Additional "Release Identifier extension" value incremented by "1" indicates subsequent releases |              |         |
+
+This field shall be present only when "release identifier" field is set with value "7" (all bits set to "1").
+
+## 6.2 CDR file naming convention
+
+The file naming convention ensures that CDR file names are unique among a large number of CGF nodes over an extended period of time (at least several months). In order to accomplish this requirement, the file name includes the following information:
+
+<NodeID> \_ - <RC>.<date> \_ - <time>[.<PI>][.<FE>]
+
+- 1) NodeID. This is the name of the CGF that generated the file. When the CGF is integrated in another node (see 3GPP TS 32.240 [1]), then this parameter contains the NodeID of the node that the CGF is integrated in.
+- 2) The RC parameter is a running count, starting with the value of "1". Note that the delimiter preceding this field is made up of an underscore character (\_), followed by a minus character (-), followed by another underscore character (-).
+- 3) The "date" field indicates in ASCII, the date when the CDR file was closed. It is of the form YYYYMMDD, where:
+  - YYYY is the year in four-digit notation;
+  - MM is the month in two digit notation (01 - 12);
+  - DD is the day in two-digit notation (01 - 31).
+
+Note that this field is preceded by a point (.) character as delimiter.
+
+- 4) The "time" field indicates in ASCII, the time when the CDR file was closed. It is of the form HHMMshhmm, where:
+  - HH is the two-digit hour of the day (local time), based on 24-hour clock (00 - 23);
+  - MM is the two digit minute of the hour (local time);
+  - s is in ASCII, the sign of the local time differential from UTC (+ or -), in case the time differential to UTC is 0 then the sign may be arbitrarily set to "+" or "-";
+  - hh is the two-digit number of hours of the local time differential from UTC (00-23);
+  - mm is the two digit number of minutes of the local time differential from UTC (00-59).
+
+Note that the delimiter preceding this field is made up of an underscore character (\_), followed by a minus character (-), followed by another underscore character (-).
+- 5) Optional private information. The content of this field is implementation specific. This field, if present, is preceded by a point (.) character delimiter.
+- 6) Optional file extension. The content of this field is implementation specific. This field, if present, is preceded by a point (.) character delimiter.
+
+Some examples describing file-naming convention (note that the quotation marks do not form part of the file name):
+
+- 1) file name: "CGFNodeId\_-\_1234.20050401\_-\_2315+0200",  
+meaning: file #1234 produced by CGF <CGFNodeId> on April 1, 2005 at 23:15 local time, with a time differential of +2 hours against UTC.
+- 2) file name: "CGFNodeId\_-\_44.20051224\_-\_1700-1130.thankgoditschristmas.abc",  
+meaning: file #44 produced by CGF <CGFNodeId> on December 24, 2005 at 17:00 local time, with a time differential of -11:30 hours against UTC, private information "thankgoditschristmas" and extension "abc".
+- 3) file name: "CGFNodeId\_-\_44.20051224\_-\_1700-1130..abc",  
+meaning: same file as 2) above but this time without private extension. Note that there are two point characters (.) preceding the file extension due to the missing (=empty) private extension.
+
+There shall be a configurable base directory on the CGF which contains one or more subdirectories that contain all CDR files that are ready for transfer to the BD. Further details of the directory structure on the CGF for the storage of CDR files are implementation specific.
+
+## 6.3 Detailed FTP transfer and session management procedures
+
+The detailed FTP transfer and session management procedures are out of scope of the current 3GPP release. However the following items should be considered in actual implementations.
+
+- FTP client behaviour;
+- FTP server role;
+- File transfer triggers;
+- Each of the above in relation to push and pull modes.
+
+## 6.4 Error handling
+
+The detailed error handling on the CGF is out of scope of the current 3GPP release. However the following items should be considered in actual implementations.
+
+- Replacement of invalid CDR parameters;
+- Handling of irrecoverable CDRs;
+- System dependent failures (file system full, etc.);
+
+- File transfer failure in relation to
+  - Pull mode;
+  - Push mode.
+
+# --- Annex A (informative): Bibliography
+
+## **a) The 3GPP charging specifications**
+
+- 3GPP TS 32.274: "Telecommunication management; Charging management; Short Message Service (SMS) charging".
+- 3GPP TS 32.275: "Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging".
+- 3GPP TS 32.280: "Telecommunication management; Charging management; Advice of Charge (AoC) service".
+
+## **b) Common 3GPP specifications**
+
+- TS 22.101: "Service aspects; Service Principles".
+- TS 22.115: "Service aspects; Charging and billing".
+- TS 23.002: "Network Architecture".
+- TS 23.003: "Numbering, addressing and identification".
+- TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
+
+## **c) other Domain and Service specific 3GPP / ETSI specifications**
+
+- 
+
+## **d) Relevant ITU Recommendations**
+
+- ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)".
+- ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- ITU-T Recommendation Q.767: "Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections".
+- ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".
+- ITU-T Recommendation X.121: "International numbering plan for public data networks".
+
+## **e) Relevant IETF RFCs**
+
+- IETF RFC 3588 (2003): "Diameter base protocol"
+- IETF Internet-Draft "Diameter Credit Control Application"
+- IETF RFC 1350: "The TFT Protocol (Revision 2)"
+
+# Annex B (informative): Change history
+
+| Change history |       |           |      |      |                                                                                                                                                                 |      |        |        |
+|----------------|-------|-----------|------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | R ev | Subject/Comment                                                                                                                                                 | Ca t | Old    | New    |
+| Jun 2003       | SP-20 | SP-030273 | --   | --   | Submitted to TSG SA#20 for Information                                                                                                                          | --   | 1.0.0  | --     |
+| Mar 2004       | SP-23 | SP-040142 | --   | --   | Submitted to TSG SA#23 for Approval                                                                                                                             | --   | 2.0.0  | 6.0.0  |
+| Jun 2005       | SP-28 | SP-050272 | 0001 | 1    | Corrections, alignments and additions to complete remaining technical gaps                                                                                      | C    | 6.0.0  | 6.1.0  |
+| Sep 2006       | SP-33 | SP-060526 | 0003 | --   | Correct field descriptions to the appropriate formats that represent binary                                                                                     | F    | 6.1.0  | 6.2.0  |
+| Sep 2006       | SP-33 | SP-060544 | 0004 | --   | Add optional solution set for the Bx reference point to fulfil the ITU-T requirement on CDR file transfer with IPDR in context of NGN Accounting (FBI-TISP2-CH) | B    | 6.2.0  | 7.0.0  |
+| Mar 2008       | SP-39 | SP-080190 | 0005 | 2    | Correction of errors and inconsistencies - Align with 32.240                                                                                                    | F    | 7.0.0  | 7.1.0  |
+| Sep 2008       | SP-41 | SP-080466 | 0006 | -    | Clarification on EPC Charging                                                                                                                                   | B    | 7.1.0  | 8.0.0  |
+| Sep 2008       | SP-41 | SP-080462 | 0007 | -    | Alignment on Bx interface                                                                                                                                       | D    | 7.1.0  | 8.0.0  |
+| Dec 2008       | SP-42 | SP-080706 | 0008 | -    | TS 32.297 evolution for Rel-8                                                                                                                                   | B    | 8.0.0  | 8.1.0  |
+| Jun 2009       | SP-44 | SP-090293 | 0009 | -    | Correction on length of Node IP Address                                                                                                                         | F    | 8.1.0  | 8.2.0  |
+| Dec 2009       | -     | -         | -    | -    | Update to Rel-9 version (MCC)                                                                                                                                   | -    | 8.2.0  | 9.0.0  |
+| Mar 2011       | SP-51 | SP-110109 | 0010 | 1    | Release considerations beyond Release 9 for CDR headers                                                                                                         | C    | 9.0.0  | 10.0.0 |
+| Sep 2011       | SP-53 | SP-110530 | 0011 | 1    | Correction of the release/version identifier in CDR file header format                                                                                          | F    | 10.0.0 | 10.1.0 |
+| Dec 2011       | SP-54 | SP-110710 | 0012 | -    | Correction of the high/low release identifier in CDR file header format                                                                                         | F    | 10.1.0 | 10.2.0 |
+| Dec 2011       | SP-54 | SP-110710 | 0013 | -    | Correction on CDR header format                                                                                                                                 | F    | 10.1.0 | 10.2.0 |
+

marked/Rel-10/32_series/32300/raw.md

@@ -0,0 +1,929 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Name convention for Managed Objects (Release 10)** ---
+
+![3GPP logo with TM symbol](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font. The '3' is bold and black, the 'G' is black, the 'P' is black, and the 'P' is black. A small red signal icon is positioned below the 'G'. A 'TM' symbol is located to the upper right of the 'P'.
+
+3GPP logo with TM symbol
+
+Keywords  
+UMTS, Management
+
+**3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+![LTE logo with 'ADVANCED' text above the 'e' and a signal icon above the 'l'.](1211e36d120f0d2912a745437f4c8f19_img.jpg)
+
+The logo for LTE (Long Term Evolution) is displayed. It features the letters 'lte' in a bold, lowercase font. Above the 'e' is the word 'ADVANCED' in a smaller, uppercase font. Above the 'l' is a red signal icon consisting of four curved lines of increasing height. A small 'TM' trademark symbol is located to the right of the 'e'.
+
+LTE logo with 'ADVANCED' text above the 'e' and a signal icon above the 'l'.
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+**3GPP**
+
+# Contents
+
+|                                                                                                |           |
+|------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                 | 4         |
+| Introduction .....                                                                             | 4         |
+| 1 Scope.....                                                                                   | 6         |
+| 2 References.....                                                                              | 6         |
+| 3 Definitions and abbreviations .....                                                          | 7         |
+| 3.1 Definitions.....                                                                           | 7         |
+| 3.1.1 Void .....                                                                               | 7         |
+| 3.1.2 Void .....                                                                               | 7         |
+| 3.1.3 Managed Object and Network Resource .....                                                | 7         |
+| 3.1.4 Name.....                                                                                | 7         |
+| 3.1.5 Name space.....                                                                          | 7         |
+| 3.1.6 Global Root and Local Root.....                                                          | 8         |
+| 3.1.7 Distinguished Name and Relative Distinguished Name .....                                 | 8         |
+| 3.2 Abbreviations .....                                                                        | 8         |
+| 4 System overview .....                                                                        | 9         |
+| 4.1 System context .....                                                                       | 9         |
+| 5 Name Convention for Managed Objects.....                                                     | 9         |
+| 6 Representations of Distinguished Name (DN).....                                              | 10        |
+| 7 String Representation of DN.....                                                             | 11        |
+| 7.A Overview .....                                                                             | 11        |
+| 7.B Allowed character sets .....                                                               | 11        |
+| 7.1 Converting DN from ASN.1 to String .....                                                   | 11        |
+| 7.1.1 Rule for one-string DN.....                                                              | 11        |
+| 7.1.1.1 Converting RDNSequence .....                                                           | 11        |
+| 7.1.1.2 Converting RelativeDistinguishedName .....                                             | 12        |
+| 7.1.1.3 Converting AttributeTypeAndValue .....                                                 | 12        |
+| 7.1.2 Rule for multi-string DN .....                                                           | 12        |
+| 7.1.2.1 Converting RDNSequence .....                                                           | 12        |
+| 7.1.2.2 Converting RelativeDistinguishedName .....                                             | 12        |
+| 7.1.2.3 Converting AttributeTypeAndValue .....                                                 | 12        |
+| 7.2 Character syntax.....                                                                      | 13        |
+| 7.3 EBNF of DN String Representation.....                                                      | 13        |
+| 7.4 Maximum size of DN string.....                                                             | 16        |
+| 8 Examples of DN in string representation.....                                                 | 17        |
+| 9 Usage Scenario.....                                                                          | 18        |
+| 9.1 DN prefix usage .....                                                                      | 18        |
+| <b>Annex A (normative): Mapping of RDN AttributeType to Strings.....</b>                       | <b>19</b> |
+| <b>Annex B (normative): Rule for MO Designers regarding AttributeType interpretation .....</b> | <b>20</b> |
+| <b>Annex C (informative): DN Prefix and Local Distinguished Name (LDN) .....</b>               | <b>22</b> |
+| <b>Annex D (informative): Interpreting EBNF [13] .....</b>                                     | <b>24</b> |
+| <b>Annex E (informative): IOC/MOC name recommendation .....</b>                                | <b>26</b> |
+| <b>Annex F (informative): Change history.....</b>                                              | <b>27</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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
+
+Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.
+
+CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs.
+
+## Background
+
+Traditionally, multiple name conventions have been used by different vendors' NEs, or even within the same vendor, to name network resources. The following problems have thus arisen:
+
+- Different classes of NE have used different name conventions. Network Management applications, when interfacing with these NEs, have been required to understand multiple name conventions to manage the NEs.
+- Network management applications (e.g. Fault Management application), when interfacing with other applications (e.g. Configuration Management application, trouble ticket system) have been required to understand multiple name conventions.
+- When a customer purchased multiple classes of NEs from the same or different vendors, the customer was confronted with multiple name conventions.
+- Without a name convention, it is difficult to integrate IRP conformant vendors' resource name space (see subclause 3.1.5 for definition of name space) into the customer's Enterprise name space.
+
+## Benefits
+
+The benefits of using the subject name convention to name 3G network resources for network management purposes are as follows:
+
+- A resource name is guaranteed to be unambiguous in that it refers to, at most, one network resource. Unambiguous naming of managed network resources is necessary for interoperability among managing applications and systems.
+
+- The resource name syntax is specified such that management applications can be designed with assurance that its name-parsing algorithm needs not be modified in the future. We can derive this benefit only if the subject name convention is widely accepted.
+
+The root and upper portions of the name hierarchy are based on name infrastructure of Domain Name System (DNS) (see IETF RFC 2247 [5]). The subject name convention can naturally fit in DNS and can integrate well with other hierarchical naming systems, such as ITU-T Recommendation X.500 [2].
+
+# --- 1 Scope
+
+A more detailed background and introduction of the IRP concept is given in 3GPP TS 32.150 [16].
+
+To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the IRP context.
+
+To facilitate integration of network management information obtained via multiple IRPs based on different IRP Solution Set technologies, identical network resource name semantics shall be conveyed in all IRPs. The present document specifies one such name convention.
+
+The present document also specifies an IOC/MOC name recommendation (see annex E) in order to avoid potential problems with valid characters in some programming languages.
+
+# --- 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] Void.
+- [2] ITU-T Recommendation X.500 (1993): "Information technology - Open Systems Interconnection - The Directory: Overview of concepts, models and services".
+- [3] T. Howes, ISBN 1-57870-070-1: "Understanding and Deploying LDAP Directory Services".
+- [4] IETF RFC 1737 (1994): "Functional Requirements for Uniform Resource Names".
+- [5] IETF RFC 2247 (1998): "Using Domains in LDAP/X.500 Distinguished Names".
+- [6] IETF RFC 1035 (1987): "Domain names - implementation and specification".
+- [7] IETF RFC 2253 (1997): "Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names".
+- [8] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [9] 3GPP TS 32.622: " Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [10] Void.
+- [11] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [12] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [13] ISO/IEC 14977: "Information technology – Syntactic metalanguage – Extended BNF".
+- [14] ISO/IEC 646: "Information technology – ISO 7-bit coded character set for information interchange".
+- [15] ISO/IEC 10646: "Information technology – Universal multiple-octet Coded Character Set (UCS)".
+
+- [16] 3GPP TS 32.150: "Integration Reference Point (IRP) Concept and definitions".
+- [17] 3GPP2 S.S0028-E "OAM&P for cdma2000 (Overview, 3GPP R7 Delta Specification, 3GPP2 Network Resource Model IRP)"
+- [18] MEF Technical Specification MEF 7.1, Phase 2 EMS-NMS Information Model, October 2009
+- [19] ATM Forum, Technical Committee, Network Management, M4 Network View CMIP MIB Specification
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [11], 3GPP TS 32.102 [12] and 3GPP TS 32.150 [16] apply. This subclause defines terms essential for understanding of name convention in the IRP context.
+
+### 3.1.1 Void
+
+### 3.1.2 Void
+
+### 3.1.3 Managed Object and Network Resource
+
+In the context of the present document, a Managed Object (MO) is a software object that encapsulates the manageable characteristics and behaviour of a particular network resource. Examples of network resource are switch, scanner for monitoring performance data, cell, site, transmission links, satellite, operator profile, etc. In the present document, MO sometimes is referred to as MO instance.
+
+### 3.1.4 Name
+
+In the context of the present document, a name is restricted to the identification of a MO, that is, a software object representing a real network resource.
+
+### 3.1.5 Name space
+
+A name space is a collection of names. This name convention uses a hierarchical containment structure, including its simplest form - the one-level, flat name space. This name convention does not support an arbitrarily connected name space, or graph structure, in which a named object can be both child and parent of another named object. Figure 1 shows some examples of supported and unsupported name spaces (this figure is from T. Howes, ISBN 1-57870-070-1 [3] and it provides useful information on name space design).
+
+![Figure 1: Examples of supported and unsupported name spaces. The diagram shows four examples: 'Supported' (a tree structure and a vertical chain), and 'Unsupported' (a triangle and a circle with a self-loop).](06da11ab76cacc38bbcd714e437797ea_img.jpg)
+
+The diagram illustrates four examples of name space structures:
+
+- Supported:**
+  - A tree structure with a root node and three child nodes.
+  - A vertical chain of four nodes connected in a single path.
+- Unsupported:**
+  - A triangle structure where three nodes are all interconnected, forming a cycle.
+  - A circle with two nodes, where each node has a self-loop, representing a more complex cycle.
+
+Figure 1: Examples of supported and unsupported name spaces. The diagram shows four examples: 'Supported' (a tree structure and a vertical chain), and 'Unsupported' (a triangle and a circle with a self-loop).
+
+Figure 1: Examples of supported and unsupported name spaces
+
+### 3.1.6 Global Root and Local Root
+
+Names in name space are organised in hierarchy. An MO instance that contains another one is referred to as the superior (parent), whereas the contained MO instance is referred to as the subordinate (child).
+
+In modern network management, it is expected that the Enterprise name space be partitioned for implementations in multiple managed system (see annex C for reasons of name space partitioning). The parent of all MO instances in a single managed system is called the Local Root. The ultimate parent of all MO instances of all managed systems is called the Global Root.
+
+### 3.1.7 Distinguished Name and Relative Distinguished Name
+
+A Distinguished Name (DN) is used to uniquely identify a MO within a name space. A DN is built from a series of "name components", referred to as Relative Distinguished Names (RDNs). ITU-T Recommendation X.500 [2] defines the concepts of DN and RDN in detail, using ASN.1, in the following way:
+
+```
+DistinguishedName ::= RDNSequence
+RDNSequence ::= SEQUENCE OF RelativeDistinguishedName
+RelativeDistinguishedName ::= SET SIZE (1..MAX) OF AttributeTypeAndValue
+AttributeTypeAndValue ::= SEQUENCE {type AttributeType, value AttributeValue}
+```
+
+The present document references this ASN.1 structure but it only uses single-valued (not multi-valued) RDN.
+
+From a DN of a MO, one can derive the DN of its containing MO, if any. This containment relation is the only relation carried by the DN. No other relation can be carried or implied by the DN.
+
+See annex B for a rule for MO designers to avoid ambiguity concerning the `AttributeType` of a DN string.
+
+See annex C for discussion of DN prefix.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                       |
+|-------|---------------------------------------|
+| ASN.1 | Abstract Syntax Notation One          |
+| BER   | Basic Encoding Rules                  |
+| CM    | Configuration Management              |
+| DC    | Domain Component                      |
+| DN    | Distinguished Name                    |
+| DNS   | Domain Name Service                   |
+| EBNF  | Extended Backus-Naur Form             |
+| FM    | Fault Management                      |
+| IETF  | Internet Engineering Task Force       |
+| IOC   | Information Object Class              |
+| IRP   | Integration Reference Point           |
+| IS    | Information Service                   |
+| LDN   | Local Distinguished Name              |
+| MO    | Managed Object                        |
+| MOC   | Managed Object Class                  |
+| MOI   | Managed Object Instance               |
+| NE    | Network Element                       |
+| NR    | Network Resource                      |
+| NRM   | Network Resource Model                |
+| PM    | Performance Management                |
+| QoS   | Quality of Service                    |
+| RDN   | Relative Distinguished Name           |
+| SS    | Solution Set                          |
+| TMN   | Telecommunications Management Network |
+
+# --- 4 System overview
+
+## 4.1 System context
+
+Situations under which MO (representing network resource) names are used are as follows:
+
+- a) MO names cross various Integration Reference Points (IRPs).
+
+EXAMPLE 1: In the context of Alarm IRP 3GPP TS 32.111-2 [8], IRP Agent notifies IRP Manager of the alarm condition of a network resource. The DN of the MO, representing alarmed network resource, encoded as specified in the present document, is carried in the `Managed Object Instance` parameter of the notification.
+
+EXAMPLE 2: In the context of Generic Network Resources IRP: NRM, 3GPP TS 32.622 [9], IRP Agent notifies IRP Manager of the creation of new object. The DN of the newly created object, encoded as specified in the present document, is carried in the notification.
+
+EXAMPLE 3: In the context of Generic Network Resources IRP: NRM, 3GPP TS 32.622 [9], IRP Manager requests IRP Agent to search for a particular object by specifying the start point of the search. The DN of the base object, upon which the search begins downward hierarchically, is carried in the request.
+
+- b) Co-operating management applications need to exchange information that includes MO (representing network resource) names.
+
+EXAMPLE 4: A Fault Management (FM) application may request a trouble ticket system to open a new trouble ticket reporting the alarmed condition of a network resource by specifying, among other things, the MO name representing the alarmed network resource. The DN of the MO, encoded as specified in the present document, is included in the request.
+
+EXAMPLE 5: A Performance Management (PM) system that produces reports on performance of network resources. The DNs of the MOs, representing the reported network resources, encoded as specified in the present document, are printed on the report.
+
+# --- 5 Name Convention for Managed Objects
+
+Network resources shall be named using the naming conventions in ITU-T Recommendation X.500 [2] with one restriction listed below. Central to the X.500 naming convention is the concept of the Distinguished Name (DN) (see subclause 3.1.7).
+
+The restriction is that this IRP name convention does not support multi-value RDN. Only single-value RDN is supported.
+
+# --- 6 Representations of Distinguished Name (DN)
+
+A DN can be encoded and represented in many ways. The present document specifies one representation. Future work on IRP specifications may require the definition(s) of other representation(s)..
+
+The DN is encoded using the string representation.
+
+The DN string representation encoding scheme:
+
+- shall be used for DNs exchanged through all IRP SS technologies,
+- is in itself IRP SS technology neutral, and
+- is subject to IRP SS technology specific handling, such as escaping, if required by such a technology.
+
+# 7 String Representation of DN
+
+## 7.A Overview
+
+This clause specifies the string representation of DN. This work is based on IETF RFC 2253 [7]. A DN string representation, using the string-encoding scheme specified in the present document, is also a valid DN string according to IETF RFC 2253 [7].
+
+The string-encoding scheme specified in the present document imposes further restrictions as compared to IETF RFC 2253 [7]. The most important restrictions are:
+
+- Multi-valued RDN is not supported in the subject name convention.
+- Character asterisk is used to denote wildcard in the subject name convention.
+
+## 7.B Allowed character sets
+
+Subject to further restrictions described in the following subclauses, the allowed characters for the string representation of DN are:
+
+- Characters of ISO/IEC 646 [14] International Reference Version (IRV) coded character set, and
+- Characters of standard coded character sets supporting and extending ISO/IEC 646 [14] IRV coded character set, e.g. ISO/IEC 10646 [15] coded character set.
+
+NOTE 1: ISO/IEC 646 [14] IRV coded character set is the international equivalent to the ANSI X3.4 ASCII coded character set.
+
+NOTE 2: The character set of ISO/IEC 646 [14] IRV corresponds to the subset of characters that range from U+0000 to U+007F in the character set of ISO/IEC 10646 [15].
+
+NOTE 3: The ISO/IEC 646 [14] IRV characters specifically referenced in this specification are further identified using ISO/IEC 10646 [15] character short identifier notation form "U+XXXX".
+
+## 7.1 Converting DN from ASN.1 to String
+
+Subclause 7.1.1 defines the algorithm to convert an ASN.1 structured representation to one-string DN representation. Subclause 7.1.2 defines the algorithm to convert an ASN.1 structured representation to multi-string DN representation.
+
+CORBA SS uses one-string DN representation. XML SS uses both one-string and multi-string DN representations.
+
+### 7.1.1 Rule for one-string DN
+
+#### 7.1.1.1 Converting RDNSequence
+
+If the RDNSequence is an empty sequence, the result is the empty or zero length string.
+
+Otherwise, the output consists of the string encoding of each RDN in the RDNSequence (according to subclause 7.1.1.2), starting with the first element of the sequence and moving forward toward the last element.
+
+The encoding of adjacent RDNs are separated by a comma character (',', U+002C), to be consistent with IETF RFC 2253 [7].
+
+White spaces adjacent to the comma character shall be ignored.
+
+#### 7.1.1.2 Converting RelativeDistinguishedName
+
+When converting from an RDN to a string, the output consists of the string encoding of the singleton `AttributeTypeAndValue` (according to subclause 7.1, i.e. “Multi-valued RDN is not supported in the subject name convention.”).
+
+Although ITU-T Recommendation X.500 DN supports multi-valued RDN, this specification supports single-valued RDN only.
+
+#### 7.1.1.3 Converting AttributeTypeAndValue
+
+The `AttributeTypeAndValue` is encoded as the string representation of the `AttributeType`, followed by an equals sign character ('=', U+003D), followed by the string representation of the `AttributeValue`.
+
+Although ITU-T Recommendation X.500 ASN.1 `AttributeValue` and `AttributeType` support wide range of character representation, this specification supports a restrictive set of characters according to subclause 7.2.
+
+String representation of `AttributeValue` allows character escape mechanism such as the use of a reverse solidus character ('\, U+005C) followed by two hexadecimal digits to replace a character in a string. String representation of `AttributeType` does not allow character escape mechanism.
+
+EXAMPLE: "CN=Before\0DAfter,O=Test,C=GB". In this example, the reverse solidus character and the two hexadecimal digits form a single byte in the code of the escaped character. The reverse solidus character followed by "0D" indicates a carriage return character. See annex B for a rule for MO designers to avoid ambiguity concerning the `AttributeType` of a DN string.
+
+### 7.1.2 Rule for multi-string DN
+
+#### 7.1.2.1 Converting RDNSequence
+
+If the `RDNSequence` is an empty sequence, there is no equivalent multi-string DN output, i.e. there is no multi-string DN representation for empty `RDNSequence` sequence.
+
+Otherwise, the output consists of the string encoding of all RDNs in the `RDNSequence` (according to subclause 7.1.2.2).
+
+One RDN encoding is within an NRM class associated XML element. A multiple `RDNSequence` would be converted into multiple RDN encodings, using multiple NRM class associated XML elements. They are arranged in a hierarchy in the XML document. The outer NRM class associated XML element represents the first RDN in the `RDNSequence`.
+
+#### 7.1.2.2 Converting RelativeDistinguishedName
+
+When converting from an RDN to a string, the output consists of the encoding of the singleton `AttributeTypeAndValue` (according to subclause 7.1, i.e. “Multi-valued RDN is not supported in the subject name convention.”).
+
+Although ITU-T Recommendation X.500 DN supports multi-valued RDN, this specification supports single-valued RDN only.
+
+#### 7.1.2.3 Converting AttributeTypeAndValue
+
+Within an NRM class XML element, there is an element such as `<element name="ManagedElement">` and there is another element `<attribute name="id" type="string" use="required"/>` which is inherited by using `<extension base="xn:NrmClass">`.
+
+The `AttributeType` and `AttributeValue` are mapped to the former and latter XML elements. The `AttributeType` carries the IOC name while the `AttributeValue` carries the value of the IOC naming-attribute.
+
+Although ITU-T Recommendation X.500 ASN.1 `AttributeValue` and `AttributeType` support wide range of character representation, this specification supports a restrictive set of characters according to subclause 7.2.
+
+String representation of `AttributeValue` allows character escape mechanism (see 7.1.1.3).
+
+## 7.2 Character syntax
+
+This subclause specifies the character syntax for `AttributeType` and `AttributeValue`.
+
+They are:
+
+1. Any character except:
+  - comma character (',', U+002C),
+  - equals sign character ('=', U+003D),
+  - carriage return character (U+000D),
+  - line feed character (U+000A),
+  - plus sign character ('+', U+002B),
+  - less-than sign character ('<', U+003C),
+  - greater-than sign character ('>', U+003E),
+  - number sign character ('#', U+0023),
+  - semicolon character (';', U+003B),
+  - reverse solidus character ('\', U+005C),
+  - quotation mark character ('"', U+0022).
+2. The full stop character ('.', U+002E). This character may be used in the `AttributeValue` whose `AttributeType` is "DC". An example is "DC=marketing.CompanyXYZ.com". This full stop character shall not be used in `AttributeType`.
+3. The asterisk character ('\*', U+002A) is reserved to denote wildcard. Wildcard character(s) can appear in `AttributeType` and `AttributeValue`. The wildcard character can be used to represent one or more characters which are legal in that field (i.e., `attributeType`, `attributeValue`).
+
+## 7.3 EBNF of DN String Representation
+
+The formal definitions provided within this subclause consolidate several rules and concepts (null distinguished name, DN prefix, local DN, domain component type, class names starting with upper case characters, attribute names starting with lower case characters, classes with or without an "Id" naming attribute, attribute type and attribute value allowed characters, wildcard character). The definition is more detailed to clarify these naming rules, and will not introduce compliancy issues for implementations compliant with Rel-5 version of this specification.
+
+The following is the EBNF for DN in string representation (Extended Backus-Naur Form; see ISO/IEC 14977 [13] for more information):
+
+```
+
+DistinguishedName            =  NullDN                      (* Distinguished Names shall not exceed  *)
+                             |  RegularDN ;                 (* 400 octets as specified in section 7.4 *)
+
+NullDN                       =  ; (* empty string; null DN is specified in subclause 7.1.1 *)
+
+RegularDN                    =  DNPrefixPlusRDNSeparator    (* DN prefix and local DN *)
+                             ,  LocalDN ;                   (* are defined in annex C *)
+
+DNPrefixPlusRDNSeparator     =  ( NullDNPrefix , NullRDNSeparator )
+                             |  ( DNPrefixWithDomainComponent , RDNSeparator )
+                             |  ( DNPrefixWithoutDomainComponent , RDNSeparator ) ;
+
+NullDNPrefix                 =  ; (* empty string *)
+
+NullRDNSeparator             =  ; (* empty string *)
+
+DNPrefixWithDomainComponent  =  DomainComponentRDN
+                             ,  { RDNSeparator , DomainComponentRDN }
+                             ,  { RDNSeparator , RegularRDN } ;
+  
+```
+
+```
+
+DNPrefixWithoutDomainComponent = RegularRDN
+    , { RDNSeparator , RegularRDN } ;
+
+LocalDN = LocalRDN
+    , { RDNSeparator , LocalRDN } ;
+
+RDNSeparator = [ RDNSeparatorWhiteSpace ] (* use of optional white space *)
+    , CommaChar (* is recommended to be avoided *)
+    , [ RDNSeparatorWhiteSpace ] ;
+
+RDNSeparatorWhiteSpace = [ CarriageReturnChar ]
+    , [ SpaceChar ] ;
+
+DomainComponentRDN = DCAttributeTypeAndValue ;
+
+RegularRDN = RegularAttributeTypeAndValue ;
+
+LocalRDN = LocalDNAttributeTypeAndValue ;
+
+DCAttributeTypeAndValue = DCAttributeType
+    , AttributeTypeAndValueSeparator
+    , ( DCAttributeValue | WildcardDCAttributeValue ) ;
+
+RegularAttributeTypeAndValue = ( RegularAttributeType | WildcardRegularAttributeType )
+    , AttributeTypeAndValueSeparator
+    , ( RegularAttributeValue | WildcardRegularAttributeValue ) ;
+
+LocalDNAttributeTypeAndValue = ( LocalDNAttributeType | WildcardLocalDNAttributeType )
+    , AttributeTypeAndValueSeparator
+    , ( RegularAttributeValue | WildcardRegularAttributeValue ) ;
+
+AttributeTypeAndValueSeparator = EqualsSignChar ;
+
+DCAttributeType = "DC" ; (* ISO/IEC 646 IRV U+0044/0043 Latin capital letters D&C *)
+
+DCAttributeValue = DCLabel (* this is specified *)
+    , { DCLabelSeparator , DCLabel } ; (* in IETF RFC 1035 *)
+
+WildcardDCAttributeValue = ( ( DCLabel | WildcardDCLabel )
+    , { DCLabelSeparator , ( DCLabel | WildcardDCLabel ) } )
+    - DCAttributeValue ;
+
+DCLabelSeparator = FullStopChar ; (* this is specified in IETF RFC 1035 *)
+
+DCLabel = LetterChar (* this is specified *)
+    , [ { LetterDigitHypenMinusChar } (* in IETF RFC 1035 *)
+    , LetterDigitChar ] ;
+
+WildcardDCLabel = ( ( LetterChar | WildcardChar )
+    , [ { LetterDigitHypenMinusChar | WildcardChar }
+    , ( LetterDigitChar | WildcardChar ) ] )
+    - DCLabel ;
+
+RegularAttributeType = LetterChar (* this is specified *)
+    , { LetterDigitHypenMinusChar } ; (* in IETF RFC 2253 *)
+
+WildcardRegularAttributeType = ( ( LetterChar | WildcardChar )
+    , { LetterDigitHypenMinusChar | WildcardChar } )
+    - RegularAttributeType ;
+
+LocalDNAttributeType = NameOfClassWithIdAttribute (* definition selected shall *)
+    | NamesOfClassAndNamingAttribute ; (* be in accordance with the *)
+    (* rules defined in annex B *)
+
+WildcardLocalDNAttributeType = WildcardNameOfClassWithIdAttr
+    | WildcardNamesOfClassAndNamAttr ;
+
+NameOfClassWithIdAttribute = ClassName ; (* see rules defined in annex B *)
+
+WildcardNameOfClassWithIdAttr = WildcardClassName ;
+
+NamesOfClassAndNamingAttribute = ClassName (* see rules defined in annex B *)
+    , ClassNamingAttributeSeparator
+    , NamingAttributeName ;
+
+WildcardNamesOfClassAndNamAttr = ( ( ClassName | WildcardClassName )
+    , ClassNamingAttributeSeparator
+
+```
+
+```
+
+        , ( NamingAttributeName | WildcardNamingAttributeName ) )
+        - NamesOfClassAndNamingAttribute ;
+
+ClassNamingAttributeSeparator = FullStopChar ; (* see rules defined in annex B *)
+
+ClassName = CapitalLetterChar (* see recommendation on *)
+        , { LocalDNAttributeTypeChar } ; (* characters for class names *)
+        (* in annex E *)
+WildcardClassName = ( ( CapitalLetterChar | WildcardChar )
+        , { LocalDNAttributeTypeChar | WildcardChar } )
+        - ClassName ;
+
+NamingAttributeName = SmallLetterChar
+        , { LocalDNAttributeTypeChar } ;
+
+WildcardNamingAttributeName = ( ( SmallLetterChar | WildcardChar )
+        , { LocalDNAttributeTypeChar | WildcardChar } )
+        - NamingAttributeName ;
+
+RegularAttributeValue = ( ( AttributeValueChar - SpaceChar ) (* this is *)
+        , [ { AttributeValueChar } (* specified in *)
+        , ( AttributeValueChar - SpaceChar ) ] ; (* IETF RFC 2253 *)
+
+WildcardRegularAttributeValue = ( ( ( AttributeValueChar - SpaceChar ) | WildcardChar )
+        , [ { AttributeValueChar | WildcardChar }
+        , ( ( AttributeValueChar - SpaceChar ) | WildcardChar ) ] )
+        - RegularAttributeValue ;
+
+LocalDNAttributeTypeChar = DNChar - FullStopChar ;
+
+AttributeValueChar = DNChar | EscapedCharSequence ;
+
+WildcardChar = AsteriskChar ; (* this is specified in subclause 7.2 *)
+
+DNChar = DNCharUnrestricted - ReservedChar ;
+
+DNCharUnrestricted = ? Character of ISO/IEC 646 IRV ?
+        | ? Character of standard coded character set
+        supporting and extending ISO/IEC 646 IRV ? ;
+
+EscapedCharSequence = ReverseSolidusChar (* this is specified *)
+        , 2 * HexadecimalDigitChar ; (* in subclause 7.1.3 *)
+
+ReservedChar = Rfc2253ReservedChar | CarriageReturnChar | LineFeedChar
+        | AsteriskChar ;
+
+Rfc2253ReservedChar = CommaChar | EqualsSignChar | PlusSignChar | LessThanSignChar
+        | GreaterThanSignChar | NumberSignChar | SemiColonChar
+        | ReverseSolidusChar | QuotationMarkChar ;
+
+LetterChar = CapitalLetterChar | SmallLetterChar ;
+
+LetterDigitChar = LetterChar | DigitChar ;
+
+LetterDigitHyphenMinusChar = LetterDigitChar | HyphenMinusChar ;
+
+HexadecimalDigitChar = DigitChar | CapitalLetterAtoFChar | SmallLetterAtoFChar ;
+
+LineFeedChar = ? ISO/IEC 646 IRV U+000A character line feed ? ;
+
+CarriageReturnChar = ? ISO/IEC 646 IRV U+000D character carriage return ? ;
+
+SpaceChar = ' ' ; (* ISO/IEC 646 IRV U+0020 character space *)
+
+QuotationMarkChar = '"' ; (* ISO/IEC 646 IRV U+0022 character quotation mark *)
+
+NumberSignChar = '#' ; (* ISO/IEC 646 IRV U+0023 character number sign *)
+
+AsteriskChar = '*' ; (* ISO/IEC 646 IRV U+002A character asterisk *)
+
+PlusSignChar = '+' ; (* ISO/IEC 646 IRV U+002B character plus sign *)
+
+CommaChar = ',' ; (* ISO/IEC 646 IRV U+002C character comma *)
+
+HyphenMinusChar = '-' ; (* ISO/IEC 646 IRV U+002D character hyphen-minus *)
+
+FullStopChar = '.' ; (* ISO/IEC 646 IRV U+002E character full stop *)
+
+```
+
+```
+
+DigitChar           = '0' | '1' | '2' | '3' | '4'      (* ISO/IEC 646 IRV U+0030-0039 *)
+                    | '5' | '6' | '7' | '8' | '9' ;      (* digits 0 to 9 *)
+
+SemiColonChar       = ';' ;      (* ISO/IEC 646 IRV U+003B character semicolon *)
+
+LessThanSignChar    = '<' ;      (* ISO/IEC 646 IRV U+003C character less-than sign *)
+
+EqualsSignChar      = '=' ;      (* ISO/IEC 646 IRV U+003D character equals sign *)
+
+GreaterThanSignChar = '>' ;      (* ISO/IEC 646 IRV U+003E character greater-than sign *)
+
+CapitalLetterAtoFChar = 'A' | 'B' | 'C'      (* ISO/IEC 646 IRV U+0041-0046 *)
+                    | 'D' | 'E' | 'F' ;      (* Latin capital letters A to F *)
+
+CapitalLetterChar   = CapitalLetterAtoFChar | 'G' | 'H'      (* ISO/IEC 646 IRV *)
+                    | 'I' | 'J' | 'K' | 'L' | 'M' | 'N'      (* U+0041-005A *)
+                    | 'O' | 'P' | 'Q' | 'R' | 'S' | 'T'      (* Latin capital *)
+                    | 'U' | 'V' | 'W' | 'X' | 'Y' | 'Z' ;      (* letters A to Z *)
+
+ReverseSolidusChar  = '\'; ;      (* ISO/IEC 646 IRV U+005C character reverse solidus *)
+
+SmallLetterAtoFChar = 'a' | 'b' | 'c'      (* ISO/IEC 646 IRV U+0061-0066 *)
+                    | 'd' | 'e' | 'f' ;      (* Latin small letters a to f *)
+
+SmallLetterChar     = SmallLetterAtoFChar | 'g' | 'h'      (* ISO/IEC 646 IRV *)
+                    | 'i' | 'j' | 'k' | 'l' | 'm' | 'n'      (* U+0061-007A *)
+                    | 'o' | 'p' | 'q' | 'r' | 's' | 't'      (* Latin small *)
+                    | 'u' | 'v' | 'w' | 'x' | 'y' | 'z' ;      (* letters a to z *)
+
+```
+
+## 7.4 Maximum size of DN string
+
+The maximum length of a DN string, including RDN separators and including white spaces, shall not exceed 400 bytes (8-bit).
+
+# --- 8 Examples of DN in string representation
+
+This subclause gives a few examples of DN written in the string representation specified in the present document.
+
+- EXAMPLE 1: "DC=com, DC=CompanyXYZ, DC=marketing, IRPAgent=ATMPVCBilling, Log=19990101131000, AccountingRecord=100098". In this example, the name space aligns with DNS. The AttributeType of the top three RDN are "DC". Concatenation of the corresponding AttributeValues produces the DNS registered name, i.e. "marketing.CompanyXYZ.com". The top RDN is the Global Root because DNS defines "DC=com" as the root of its name space. That top RDN is the Local Root as well.
+- EXAMPLE 2: "DC=marketing.CompanyXYZ.com, IRPAgent=ATMPVCBilling, Log=19990101131000, AccountingRecord=100098". In this example, the name space aligns with DNS as well. Instead of using three RDNs to represent the DNS registered name, this example chooses to use one RDN. The top RDN is the Global Root (and Local Root as well).
+- EXAMPLE 3: "SubNetwork=ABCNetwork, SubNetwork=TN2, MSCFunction=B5C0100". In this example, the name space designer chooses not to name its objects under the DNS nor X.500 scheme. The name space designer chooses to use "SubNetwork=ABCNetwork" as the Local Root of its name space (by looking at the DN string, it is not possible to say if the Local Root is the Global Root). DNs in this name space will start with that string as their Local Root.
+- EXAMPLE 4: The following example illustrates the use of the comma character as separator for RDNs. It also illustrates the use of space and full stop characters as part of the legal character syntax for RDNs: "CN=John T. Mills, O=Cyber System Consulting"
+
+# 9 Usage Scenario
+
+## 9.1 DN prefix usage
+
+This subclause presents recommended steps designer uses to partition the Enterprise name space while building an Alarm IRP compliant NE (the Alarm IRP Agent).
+
+1. The NE designer specifies the NRM (e.g. 3GPP TS 32.622 [9]) for the NE. Suppose the NRM is a two level hierarchy with 3 classes like:
+
+```
+Node
+|----- Port
+|----- CrossConnect
+```
+
+2. The NE designer, based on the NRM and other design choices, decides that there are 7 instances within the NE that can report alarms, such as
+
+```
+Port=1, Port=2, Port=3, Port=4, Port=5, CrossConnect=1, Node=1.
+```
+
+3. The NE designer decides on the DN prefix (see annex C) and configures its system accordingly. Since NE designer will not know the customer's name space in advance, he would normally configure the DN prefix to reflect his test environment. The DN prefix can be configured to "Network=test". The Global Root is "Network=test". The Local Root is "Node=1". It should be noted that the NE should not hard code the DN prefix but should treat DN prefix as a system configuration parameter, settable.
+
+EXAMPLE 1: At system start-up time.
+
+4. When constructing the alarm record (in coding phase), NE designer shall concatenate the name of the alarmed instance with the DN prefix to form the DN of his test environment. The resultant DN (e.g. "Network=test, Node=1, Port=3") will be placed in the Managed Object Instance (MOI) field of the alarm record.
+5. The NE is sold to a customer. The customer administrator knows his Enterprise name space, the topology of his network and where the NE will be deployed. Based on the information, he configures the DN prefix of the NE.
+
+EXAMPLE 2: The customer administrator can configure it to:
+
+```
+"DC=marketing.CompanyXYZ.com, Net=DS3BackBone, Station=TMR"
+```
+
+The Global Root in this case is "DC=marketing.CompanyXYZ.com".
+
+6. At run time, whenever NE is reporting an alarm on Port=3 via the IRP, the following string will be in the MOI field of the alarm record:
+
+```
+"DC=marketing.CompanyXYZ.com, Net=DS3BackBone, Station=TMR, Node=1, Port=3"
+```
+
+# Annex A (normative): Mapping of RDN AttributeType to Strings
+
+NOTE: This annex is normative for users of string representation.
+
+AttributeType of RDN is mapped into string for use in the DN string representation. This annex specifies the mapping.
+
+The AttributeType shall include all MO classes defined in the 3GPP Network Resource Model (NRM) IRP specifications such as the 3GPP TS 32.622 [9].
+
+It can also include classes defined by other domain specific NRMs such as [17], [18] and [19]. Such inclusion is necessary where 3GPP-defined mobile access network is part of a Fixed Mobile Convergence network management environment.
+
+There is one AttributeType that is not defined in NRM of 3GPP TS 32.622 [9] or other domain specific NRMs as listed in the Introduction clause. This special AttributeType is used to denote the domain component of the DNS. The following partial DN string representations are examples to illustrate the valid use of "DC" strings for the three DNS domain components of "marketing.CompanyXYZ.com":
+
+- "DC=com.CompanyXYZ.marketing,..."
+- "DC=com, DC=CompanyXYZ, DC=marketing,..."
+- "DC=com, DC=CompanyXYZ.marketing,..."
+- "DC=com.CompanyXYZ, DC=marketing,..."
+
+**Table A.1: Example of RDN AttributeType Strings**
+
+| String     | AttributeType                                                                                                                                                                   |
+|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DC         | Domain component of DNS                                                                                                                                                         |
+| SubNetwork | MO class name SubNetwork defined in NRM of 3GPP TS 32.622 [9].                                                                                                                  |
+| etc.       | See note.                                                                                                                                                                       |
+| NOTE:      | For each MO class name found in 3GPP set of specifications, its corresponding AttributeType String shall be identical to the class name with the leading character capitalised. |
+
+# Annex B (normative): Rule for MO Designers regarding `AttributeType` interpretation
+
+NOTE: This annex is normative for users of one string representation.
+
+This annex discusses the two possible interpretations for the `AttributeType` of the DN string and establishes a rule for MO designers to avoid ambiguity concerning their usage. It also gives a rule for designing MO classes such that one DN string, regardless of the IRP SS technology used, will result in a unique reference to the corresponding network resource.
+
+## First interpretation
+
+ITU-T Recommendation X.500 [2] uses the `AttributeType` (defined for use as the first component of the `AttributeTypeAndValue` of a RDN, see subclause 3.1.6) to identify one attribute of the subject MO for naming purpose. This `AttributeType` is called the *naming attribute* to distinguish itself from other attributes that may be present in the MO.
+
+Suppose the following is the MO class definition in pseudo notation and this MO class is inherited from root.
+
+```
+Class Bsc {
+  Attribute id;
+  Attribute ..}
+```
+
+Suppose further that the naming attribute is `id`.
+
+If this (first) interpretation is used for constructing the DN string, then the DN will be "..., id=123". MO class name cannot be derived from the DN string. The value of the `AttributeValue` contains the value of the naming attribute.
+
+## Second interpretation
+
+Generally, this interpretation shall be preferred to the first interpretation.
+
+The `AttributeType` (defined for use as the first component of the `AttributeTypeAndValue` of a RDN) is used to identify the MO class. Using this interpretation for constructing the DN string the DN will be "..., Bsc=123". The name of the naming attribute cannot be derived from the DN string. The value of the `AttributeValue` contains the value of the naming attribute.
+
+## Rule
+
+Given the two interpretations, a DN reader cannot know how to interpret the `AttributeType`, i.e. if the `AttributeType` identifies class or naming attribute. To avoid ambiguity, the following rules shall apply:
+
+- If the IS name of the IOC naming attribute is "id", ignoring case of "id", then the DN shall use "..., Yyy=123, ..." where "Yyy" is the IS name of the IOC, preserving case of "Yyy".
+
+EXAMPLE 1: If "Bsc" is the IS name of the IOC and if the IS name of its naming attribute is "id" then the DN shall be "..., Bsc=123, ...".
+
+- If the IS name of the IOC naming attribute is not the concatenation of the IS name of the IOC and "Id", ignoring case for both, and if the IS name of the IOC naming attribute is not "id", ignoring case of "id", then the DN shall use "..., Yyy.zzz=123, ..." where "Yyy" is the IS name of the IOC and "zzz" is the IS name of the IOC naming attribute, preserving case for both.
+
+EXAMPLE 2: If "Bsc" is the IS name of the IOC and if the IS name of its naming attribute is "serialNumber", then the DN shall be "..., Bsc.serialNumber=123, ...".
+
+- If the IS name of the IOC naming attribute is the concatenation of the IS name of the IOC and "Id", ignoring case for both, then the DN shall use "..., Xxx=123, ..." where "Xxx" is the IS name of the IOC, preserving case.
+
+EXAMPLE 3: If "Bsc" is the IS name of the IOC and if the IS name of its naming attribute is "bscId", then the DN shall be "..., Bsc=123, ...".
+
+# Annex C (informative): DN Prefix and Local Distinguished Name (LDN)
+
+A Distinguished Name (DN) is used to uniquely identify a MO within a name space. A DN is built from a series of "name components", referred to as Relative Distinguished Names (RDNs).
+
+DNs within a name space are arranged in hierarchy similar to concepts of naming files in UNIX file system. A file name, in the context of a local subdirectory, contains the path (series of subdirectory names) of the file starting from the local subdirectory. The same file, in the global context, contains the path of the file starting from the root directory. Similar concept applies to naming MOs. From a particular (local) context, the name of a MO is the Local Distinguished Name (LDN). From a global context, the name of the same MO is the DN. LDN is a proper subset of DN. In the context of a particular local context, a DN prefix is defined such that all LDNs in that particular context, if attached behind the DN prefix of that context, will yield the DNs of the MOs.
+
+The concepts of DN Prefix and LDN support the partitioning of large name space into smaller ones for efficient name space implementation. DN design, the subject of the present document, does not depend on these concepts. There exist other concepts that support partitioning of large name space as well. Although these concepts are independent from DN design, their use is wide spread and this annex illustrates their use in partitioning large name space.
+
+In modern network management, it is expected that the Enterprise name space be partitioned for implementations in multiple hosts. The following are reasons for the partitioning.
+
+- The Enterprise name space can be large (e.g. containing millions of objects). Partition of a large name space facilitates name space management.
+
+EXAMPLE 1: It may be easier to manage two name spaces of 1 million objects each than to manage one name space with two million objects.
+
+- Separate IRPAgents manage sub-set of the Enterprise name space relevant to their own local environment.
+
+EXAMPLE 2: One NE manages a name space (subset of the Enterprise name space) containing names of its MOs representing its own network resources. Another NE manages another sub-set, etc.
+
+- For reasons such as security, replication, back-up policy and performance, sub-sets of the Enterprise name space are managed by separate systems.
+
+EXAMPLE 3: Operation and Marketing departments may want to manage their name spaces using their respective management policies. Partitioning of Enterprise name space according to departmental jurisdiction may facilitate deployment of independent management policies.
+
+Suppose the Enterprise name space is organized hierarchically and is partitioned into 4 sub-sets as shown in figure C.1.
+
+![Figure C.1: Name space partitions. A hierarchical diagram showing four name space partitions (NS-A, NS-B, NS-C, NS-D) branching from a central root node. Each partition contains its own hierarchy of nodes. Labels indicate the DN prefix and RDNs for each partition.](a7835229df7a34816e1d35b5bbbc8c9e_img.jpg)
+
+The diagram illustrates the hierarchical structure of name space partitions. At the top is a root node. Below it, four boxes represent the partitions: NS-A, NS-B, NS-C, and NS-D. Each partition contains a sub-hierarchy of nodes.
+
+- NS-A:** The root node of this partition has an RDN of "DC=com.CompanyXYZ.marketing". It has two children with RDNs "A=7" and "A=9". The DN prefix for this partition is "".
+- NS-B:** The root node of this partition has an RDN of "A=9". It has two children with RDNs "X=1" and "Y=1". The DN prefix for this partition is "DC=com.CompanyXYZ.marketing".
+- NS-C:** The root node of this partition has an RDN of "H=2". It has one child with an RDN of "F=1". The DN prefix for this partition is "DC=com.CompanyXYZ.marketing, A=7, X=1".
+- NS-D:** The root node of this partition has an RDN of "H=2". It has one child with an RDN of "G=1". The DN prefix for this partition is "DC=com.CompanyXYZ.marketing, A=9, F=1, G=1".
+
+Figure C.1: Name space partitions. A hierarchical diagram showing four name space partitions (NS-A, NS-B, NS-C, NS-D) branching from a central root node. Each partition contains its own hierarchy of nodes. Labels indicate the DN prefix and RDNs for each partition.
+
+Figure C.1: Name space partitions
+
+NS (name space)-A contains 5 objects. DN prefix is NULL. The Global Root and Local Root of NS-A is "DC=com.CompanyXYZ.marketing" (see the Note below). DN of top object is "DC=com.CompanyXYZ.marketing". RDNs of the other four objects are, from bottom left to bottom right, "A=1", "A=7", "A=3" and "A=9". DNs of the same four objects are "DC=com.CompanyXYZ.marketing,A=1", "DC=com.CompanyXYZ.marketing,A=7", "DC=com.CompanyXYZ.marketing,A=3" and "DC=com.CompanyXYZ.marketing,A=9". The second and fourth objects are reference objects to MOs in NS-B.
+
+NS-B contains two branches. They have the same DN prefix that is "DC=com.CompanyXYZ.marketing". The Global Root is "DC=com.CompanyXYZ.marketing".
+
+The Local Root and RDN of top object of the right branch is "A=9". Its DN is "DC=com.CompanyXYZ.marketing,A=9". RDNs of other objects are shown in figure C.1. DN of the bottom object is "DC=com.CompanyXYZ.marketing,A=9,F=1,G=1,H=2". This object refers to object of another name space called NS-D.
+
+The Local Root and RDN of the top object of the left branch is "A=7". Its DN is "DC=com.CompanyXYZ.marketing,A=7". RDNs of other objects are shown in figure C.1. DN of the bottom object is "DC=com.CompanyXYZ.marketing,A=7,X=1,Y=1". This object refers to object of another name space called NS-C.
+
+NS-C contains a branch of 4 objects. Its DN prefix is "DC=com.CompanyXYZ.marketing,A=7,X=1". The Local Root and RDN of the top object is "Y=1".
+
+NS-D contains a branch of 5 objects. Its DN prefix is "DC=com.CompanyXYZ.marketing,A=9,F=1,G=1". The Local Root and RDN of the top object is "H=2".
+
+In figure C.1, the bottom object of NS-B right branch has the following names:
+
+- DN is "DC=com.CompanyXYZ.marketing,A=9,F=1,G=1,H=2".
+- LDN is "A=9,F=1,G=1,H=2".
+- RDN is "H=2".
+
+With this example, we can see that DN of an object is a series of RDNs spanning the global name space. LDN of an object is a series of RDNs spanning the local name space where the subject MO resides.
+
+The concatenation of the LDN with DN prefix of that (partitioned) name space shall produce the DN of the global name space.
+
+**NOTE:** Use of "DC" in "DC=com.CompanyXYZ.marketing" is an attempt to align the RDN with DNS name associated with the named organisation. The "DC" stands for Domain Component and is an attribute name defined by IETF for use in directory work. Annex A specifies other valid ways to align RDN with DNS as well. Equally valid, the example can choose to align the RDN with the X.500 convention. In such case, the subject string can be "O=com,O=CompanyXYZ,OU=marketing" where O and OU are X.500 standard attributes denoting organisation and organization unit respectively. The alignment choice belongs to the name space designer of each operator. The choice will be reflected in the value of the DN prefix, probably a product configuration parameter. See clause 7 for more information.
+
+# Annex D (informative): Interpreting EBNF [13]
+
+This annex provides a very simplified summary of EBNF, and does not modify in any way the reference text in ISO/IEC 14977: "Information technology – Syntactic metalanguage – Extended BNF" [13].
+
+ISO/IEC 14977 [13] specification also provides far greater coverage supported by numerous examples which are not included within this annex.
+
+The EBNF metalanguage is useful for defining rigorous syntax notations and is a notation for defining syntax rules.
+
+The language uses sequences of formal definitions.
+
+Definitions may have several layers of definition. The definitions which are refined are termed as "non terminal symbols".
+
+A term which cannot be defined at a lower level of detail is known as a "terminal symbol". I.e. the "terminal symbols" cannot be further decomposed.
+
+The language permits sentences to be constructed.
+
+The sentences consist of a non terminal, or a terminal symbol, followed by an equality symbol, followed by a formal definition of the symbol.
+
+Each sentence terminates with the semicolon ';' terminal symbol.
+
+Ideally the definitions are read from the top across to the right hand side of the page and downwards.
+
+A definition commences with an identifier (of the thing being defined) followed by an equality sign.
+
+The thing is defined by the symbols and identifiers to the right hand side of the equality symbol, up to the next semicolon ';'.
+
+There is a natural breaking down of definitions, by other definitions until a point is reached that a terminal symbol is reached – which cannot be further defined (e.g. the leaves of definition hierarchy).
+
+There are terminal symbols which permit optional choice, sequence, exclusion, comments to be included in the sentence.
+
+The set of terminal symbols as defined in table 1 of ISO/IEC 14977 [13] are below.
+
+The normal character representing each operator of Extended BNF and its implied precedence is (highest precedence at the top):
+
+'\*' repetition-symbol
+
+'-' except-symbol
+
+';' concatenate-symbol
+
+'|' definition-separator-symbol
+
+'=' defining-symbol
+
+';' terminator-symbol
+
+The normal precedence is over-ridden by the following pairs of terminal symbols:
+
+|      |                      |                     |      |
+|------|----------------------|---------------------|------|
+| "'"  | first-quote-symbol   | first-quote-symbol  | "'"  |
+| '''  | second-quote-symbol  | second-quote-symbol | '''  |
+| "(*" | start-comment-symbol | end-comment-symbol  | "*)" |
+| '('  | start-group-symbol   | end-group-symbol    | ')'  |
+
+|     |                         |                         |     |
+|-----|-------------------------|-------------------------|-----|
+| '[' | start-option-symbol     | end-option-symbol       | ']' |
+| '{' | start-repeat-symbol     | end-repeat-symbol       | '}' |
+| '?' | special-sequence-symbol | special-sequence-symbol | '?' |
+
+Examples:
+
+```
+letter    = "A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" | "I" | "J" | "K" | "L"  
+          | "M" | "N" | "O" | "P" | "Q" | "R" | "S" | "U" | "V" | "W" | "X" | "Y" | "Z" ;  
+vowel     = "A" | "E" | "I" | "O" | "U" ; (* a subset of letters *)  
+consonant = letter - vowel ; (* the set of letters except vowels *)
+```
+
+# --- Annex E (informative): IOC/MOC name recommendation
+
+## **Recommendation:**
+
+3GPP considers the use of many non-alphanumeric characters as valid characters for constructing the IOC names. The Java programming language considers the use of alphanumeric characters plus only two non-alphanumeric characters, i.e. "\$" and " \_ ", as valid characters for Java Packages and Java Class names. Because the names of the Java Packages and Java Classes generated by Java programming tools for SS implementation may include MO Class names, a Java environment would have to include a translation mechanism that replaces the invalid characters (if they are used in the IS specification to name an IOC, that is mapped to the same MOC name in a Solution Set) by valid characters. For example, replace "-" by " \_ ". This translation mechanism causes unwanted complexity and reduction in performance of the implementation. Given Java may become popular for coding IRPManager and/or IRPAgent capabilities, this note recommends the specification authors to use valid Java name characters (i.e. all alphanumeric characters plus "\$" and " \_ ") to name their IS IOCs and SS MOCs.
+
+# Annex F (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                                               |         |       |        |  |
+|----------------|-------|-----------|------|-----|-------------------------------------------------------------------------------------------------------------------------------|---------|-------|--------|--|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                               | Ca<br>t | Old   | New    |  |
+| Jun 2001       | SP-12 | SP-010283 | --   | --  | Approved at TSG SA #12 and placed under Change Control                                                                        | --      | 2.0.0 | 4.0.0  |  |
+| Dec 2001       | SP-14 | SP-010641 | 0001 | --  | Alignment of Figure C.1 with text in annex C                                                                                  | --      | 4.0.0 | 4.1.0  |  |
+| Sep 2001       | SP-17 | SP-020481 | 0002 | --  | Upgrade to Rel-5 (Remove information in the Introduction that is only relevant to Rel-4)                                      | F       | 4.1.0 | 5.0.0  |  |
+| Dec 2002       | --    | --        | --   | --  | Cosmetics                                                                                                                     | F       | 5.0.0 | 5.0.1  |  |
+| Dec 2004       | SP-26 | SP-040793 | 0003 | --  | Correct and convert formal specification from BNF syntax to EBNF with corrections                                             | F       | 5.0.1 | 6.0.0  |  |
+| Mar 2005       | SP-27 | SP-050049 | 0004 | --  | Re-introduce text erroneously deleted during implementation of CR 003                                                         | F       | 6.0.0 | 6.1.0  |  |
+| Jun 2005       | SP-28 | SP-050285 | 0005 | --  | Correct DN string representation formal definition to support wildcard character                                              | F       | 6.1.0 | 6.2.0  |  |
+| Dec 2005       | SP-30 | SP-050726 | 0006 | --  | Clarify DN string encoding applicability to all IRP technologies other than CMIP                                              | F       | 6.2.0 | 6.3.0  |  |
+| Dec 2005       | SP-30 | SP-050716 | 0007 | --  | Add Annex A from 32.622t                                                                                                      | F       | 6.2.0 | 6.3.0  |  |
+| Jul 2006       | --    | --        | --   | --  | Delete duplicated paragraph in the "Introduction" clause                                                                      | --      | 6.3.0 | 6.3.1  |  |
+| Jun 2007       | SP-36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. CMIP is still mentioned in spite of discontinuation of CMIP SSs in R7. | --      | 6.3.1 | 7.0.0  |  |
+| Sep 2007       | SP-37 | SP-070612 | 0008 | --  | Discontinuing of CMIP Solution Sets in Release 7                                                                              | F       | 7.0.0 | 7.1.0  |  |
+| Dec 2007       | SP-38 | SP-070731 | 0009 | --  | Discontinuation of CMIP Solution Sets in Release 7                                                                            | F       | 7.1.0 | 7.2.0  |  |
+| Dec 2008       | SA_42 | --        | --   | --  | Upgrade to Release 8                                                                                                          | --      | 7.2.0 | 8.0.0  |  |
+| Sep 2009       | SA_45 | SP-090627 | 0010 | --  | Cleanup of old references                                                                                                     | F       | 8.0.0 | 9.0.0  |  |
+| Dec 2009       | SA_46 | SP-090719 | 0009 | --  | Clarify IOC instance naming rule                                                                                              | F       | 9.0.0 | 9.1.0  |  |
+| Jun 2010       | SA_48 | SP-100429 | 0011 | 1   | Add missing encoding rules for Distinguished Name                                                                             | F       | 9.1.0 | 9.2.0  |  |
+| Mar 2011       | SA_51 | SP-110095 | 0012 | 1   | Clarify name space and Distinguished Name usage examples and general updates                                                  | F       | 9.2.0 | 10.0.0 |  |

marked/Rel-10/32_series/32301/raw.md

@@ -0,0 +1,207 @@
+
+
+
+
+Keywords  
+management
+
+# 3GPP TS 32.301 V10.0.0 (2011-03)
+
+*Technical Specification*
+
+**3rd Generation Partnership Project;**  
+**Technical Specification Group Services and System**  
+ Postal address  
+**Aspects;**  
+**Telecommunication management;**  
+ 3GPP support office address  
+**Configuration Management (CM);**  
+ 050 Route des Lucioles - B.P. 106  
+ Valbonne - FRANCE  
+ Tel.: +33 (0) 93 639 94 4200 Fax: +33 (0) 93 639 47 47  
+**Notification Integration Reference**
+
+![LTE logo with '4ADVANCED' text above the 't'.](8c378a184b5ae4d1605cb74d7b7a7e3f_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 't'.
+
+Internet
+
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon below the 'G'.](1211e36d120f0d2912a745437f4c8f19_img.jpg)
+
+3GPP logo with a signal icon below the 'G'.
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                          |   |
+|----------------------------------------------------------|---|
+| Foreword .....                                           | 4 |
+| Introduction .....                                       | 4 |
+| 1 Scope.....                                             | 6 |
+| 2 References.....                                        | 6 |
+| 3 Definitions and abbreviations .....                    | 6 |
+| 3.1 Definitions.....                                     | 6 |
+| 3.2 Abbreviations .....                                  | 7 |
+| 4 Notification management functions over Itf-N.....      | 7 |
+| 4.1 Notification mechanism subscription functions .....  | 7 |
+| 4.2 Subscription control functions .....                 | 7 |
+| 4.3 Notification control functions .....                 | 7 |
+| 4.4 Function to discover notification capabilities ..... | 7 |
+| 4.5 Generic notification header .....                    | 8 |
+| Annex A (informative): Change history.....               | 9 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements**
+- 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)
+- 32.306: Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions
+
+The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in Alarm IRP: Information Service [3], is one possible kind of event, an object creation as specified in Basic CM IRP: Information Service [4] is another possible kind of event.
+
+Information of an event is carried in notification. An IRP Agent (typically an EM or a NE) emits notifications. IRP Manager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRP Manager can subscribe to IRP Agent for receiving notifications.
+
+This IRP bases its design on work captured in ITU-T Recommendation X.734 [5], OMG Notification Service [6]. The central design ideas are:
+
+- Separation of notification Consumers (IRP Managers) from Producers (IRP Agents);
+- Notifications are sent to IRP Managers without the need for IRP Managers to periodically check for new notifications.
+
+Common characteristics related to notifications in all other IRPs are gathered in one IRP.
+
+# --- 1 Scope
+
+The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Requirements" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
+
+# --- 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.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
+- [5] ITU-T Recommendation X.734: "Information technology - Open Systems Interconnection - Systems Management: Event report management function".
+- [6] OMG: "OMG Notification Service".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Element Manager (EM):** See 3GPP TS 32.101 [1].
+
+**IRPAgent:** See 3GPP TS 32.102 [2].
+
+**IRPManager:** See 3GPP TS 32.102 [2].
+
+**Network Manager (NM):** See 3GPP TS 32.101 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                           |
+|-------|-------------------------------------------|
+| CM    | Configuration Management                  |
+| CORBA | Common Object Request Broker Architecture |
+| EM    | Element Manager                           |
+| FM    | Fault Management                          |
+
+|       |                                                           |
+|-------|-----------------------------------------------------------|
+| IRP   | Integration Reference Point                               |
+| ITU-T | International Telecommunication Union - Telecommunication |
+| MIB   | Management Information Base                               |
+| NE    | Network Element                                           |
+| NR    | Network Resource                                          |
+| OMG   | Object Management Group                                   |
+| OS    | Operations System                                         |
+| TM    | Telecom Management                                        |
+| UMTS  | Universal Mobile Telecommunications System                |
+
+# --- 4 Notification management functions over Itf-N
+
+## 4.1 Notification mechanism subscription functions
+
+The IRP Agent shall provide IRP Managers with the capabilities to subscribe and unsubscribe to the notification mechanism. An IRP Manager shall be able to specify the types of notifications IRP Agent should emit to IRP Manager during subscription, to specify filtering criteria that shall be applied by the notification mechanism. An IRP Manager shall be able to subscribe several times in order to include in a subscription different types of notifications. An IRP Manager shall also be able to request multiple subscriptions, which is equivalent, from the IRP Agent perspective, to multiple IRP Managers each providing one subscription.
+
+## 4.2 Subscription control functions
+
+The IRP Agent may provide to IRP Managers capabilities to control its subscriptions. An IRP Manager may then be able to check whether its subscription is still active or not, to know the details of a particular subscription and to know the list of all subscriptions it has opened.
+
+## 4.3 Notification control functions
+
+In principle, notifications are forwarded to the IRP Managers as soon as they are available. The real-time forwarding of these notifications occurs via appropriate filtering mechanisms ("discriminators" on CMIP interfaces, "subscription" on CORBA interfaces) in accordance with ITU-T Recommendation X.734 [5] or OMG event/notification service. Any IRP Manager may be able to set and change filter criteria applicable during the life-cycle of one of its subscriptions in order to ensure that only the notifications which fulfil pre-defined criteria are sent. An IRP Manager may also be able to enable and disable the emission of notifications corresponding to its subscriptions.
+
+## 4.4 Function to discover notification capabilities
+
+The IRP Agent may provide IRP Managers with a capability to discover the IRPs supported by the IRP Agent that are capable of sending notifications through the notification IRP. Those IRPs shall be identified with their version.
+
+## 4.5 Generic notification header
+
+Notifications are emitted by the notification IRP. Those notifications can be defined in any other IRP (e.g. a notification for a new alarm as specified in 3GPP TS 32.111-2 [3] Alarm IRP: Information Service). It is required that all notifications emitted by the notification IRP support the same header that contains enough information to identify the type of notification, the resource at the origin of the notification and the time of the notification.
+
+# Annex A (informative): Change history
+
+| Change history |       |           |    |     |                                                                                                                    |       |        |
+|----------------|-------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                                                                                                    | Old   | New    |
+| Jun 2001       | S 12  | SP-010283 | -- | --  | Approved at TSG SA #12 and placed under Change Control                                                             | 2.0.0 | 4.0.0  |
+| Mar 2002       | --    | --        | -- | --  | Cosmetics (changed styles/field codes on cover/page headings)                                                      | 4.0.0 | 4.0.1  |
+| Mar 2002       | S 15  | --        | -- | --  | Automatic upgrade to Rel-5 (no CR)                                                                                 | 4.0.1 | 5.0.0  |
+| Dec 2002       | --    | --        | -- | --  | Cosmetics                                                                                                          | 5.0.0 | 5.0.1  |
+| Mar 2004       | S 23  | SP-040105 | -- | --  | Automatic upgrade to Rel-6 (no CR)                                                                                 | 5.0.1 | 6.0.0  |
+| Jun 2005       | --    | --        | -- | --  | Introduction update : added 32.305 new TS-family member                                                            | 6.0.0 | 6.0.1  |
+| Jun 2007       | SA_36 | --        | -- | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | 6.0.1 | 7.0.0  |
+| Dec 2008       | SA_42 | --        | -- | --  | Upgrade to Release 8                                                                                               | 7.0.0 | 8.0.0  |
+| Dec 2009       | -     | -         | -  | -   | Update to Rel-9 version (MCC)                                                                                      | 8.0.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -  | -   | Update to Rel-10 version (MCC)                                                                                     | 9.0.0 | 10.0.0 |

marked/Rel-10/32_series/32302/raw.md

@@ -0,0 +1,933 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 32.302 V10.0.0 (2010-09) Telecommunication Management; Configuration Management (CM); Technical Specification Notification Integration Reference Point (IRP); Information Service (IS) (Release 10)** ---
+
+![3GPP logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'G' and 'P'. A 'TM' symbol is located to the top right of the logo.
+
+3GPP logo
+
+Keywords  
+UMTS, management
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                         |    |
+|---------------------------------------------------------|----|
+| Foreword .....                                          | 5  |
+| Introduction .....                                      | 5  |
+| 1 Scope.....                                            | 7  |
+| 2 References.....                                       | 7  |
+| 3 Definitions and abbreviations .....                   | 8  |
+| 3.1 Definitions.....                                    | 8  |
+| 3.2 Abbreviations .....                                 | 8  |
+| 4 System overview .....                                 | 9  |
+| 4.1 System Context .....                                | 9  |
+| 5 Information Object Classes.....                       | 9  |
+| 5.1 Imported information entities and local labels..... | 9  |
+| 5.2 Class Diagram .....                                 | 10 |
+| 5.2.1 Attributes and relationships.....                 | 10 |
+| 5.2.2 Inheritance .....                                 | 10 |
+| 5.3 Information object classes definition .....         | 11 |
+| 5.3.1 NtfSubscriber.....                                | 11 |
+| 5.3.1.1 Definition .....                                | 11 |
+| 5.3.1.2 Attributes .....                                | 11 |
+| 5.3.2 NtfSubscription.....                              | 11 |
+| 5.3.2.1 Definition .....                                | 11 |
+| 5.3.2.2 Attributes .....                                | 11 |
+| 5.3.2.3 State diagram .....                             | 12 |
+| 5.3.3 NotificationIRP .....                             | 12 |
+| 5.3.3.1 Definition .....                                | 12 |
+| 5.4 Information relationship definitions.....           | 13 |
+| 5.4.1 relation-ntfSubscriber-ntfSubscription (M).....   | 13 |
+| 5.4.1.1 Definition .....                                | 13 |
+| 5.4.1.2 Roles .....                                     | 13 |
+| 5.4.1.3 Constraints .....                               | 13 |
+| 5.4.2 relation-ntfIRP-ntfSubscriber (M).....            | 13 |
+| 5.4.2.1 Definition .....                                | 13 |
+| 5.4.2.2 Roles .....                                     | 13 |
+| 5.4.2.3 Constraints .....                               | 13 |
+| 5.5 Information attribute definitions .....             | 14 |
+| 5.5.1 Definitions and legal values .....                | 14 |
+| 5.5.2 Constraints.....                                  | 14 |
+| 6 Interface Definition .....                            | 15 |
+| 6.1 Class diagram representing interfaces.....          | 15 |
+| 6.2 Generic rules .....                                 | 15 |
+| 6.3 notificationIRPManagement Interface (M).....        | 16 |
+| 6.3.1 Operation subscribe (M).....                      | 16 |
+| 6.3.1.1 Definition .....                                | 16 |
+| 6.3.1.2 Input parameters .....                          | 16 |
+| 6.3.1.3 Output parameters.....                          | 16 |
+| 6.3.1.4 Pre-condition.....                              | 16 |
+| 6.3.1.5 Post-condition .....                            | 17 |
+| 6.3.1.6 Exceptions.....                                 | 17 |
+| 6.3.2 Operation unsubscribe (M).....                    | 17 |
+| 6.3.2.1 Definition .....                                | 17 |
+| 6.3.2.2 Input parameters .....                          | 17 |
+| 6.3.2.3 Output parameters.....                          | 18 |
+| 6.3.2.4 Pre-condition.....                              | 18 |
+| 6.3.2.5 Post-condition .....                            | 18 |
+| 6.3.2.6 Exceptions.....                                 | 18 |
+
+|                        |                                                   |    |
+|------------------------|---------------------------------------------------|----|
+| 6.4                    | subscriberManagement Interface (O).....           | 18 |
+| 6.4.1                  | Operation getSubscriptionIds (M) .....            | 18 |
+| 6.4.1.1                | Definition .....                                  | 18 |
+| 6.4.1.2                | Input parameters .....                            | 18 |
+| 6.4.1.3                | Output parameters.....                            | 19 |
+| 6.4.1.4                | Pre-condition.....                                | 19 |
+| 6.4.1.5                | Post-condition .....                              | 19 |
+| 6.4.1.6                | Exceptions.....                                   | 19 |
+| 6.5                    | subscriptionStatusOperations Interface (O) .....  | 19 |
+| 6.5.1                  | Operation getSubscriptionStatus (M) .....         | 19 |
+| 6.5.1.1                | Definition .....                                  | 19 |
+| 6.5.1.2                | Input parameters .....                            | 19 |
+| 6.5.1.3                | Output parameters.....                            | 20 |
+| 6.5.1.4                | Pre-condition.....                                | 20 |
+| 6.5.1.5                | Post-condition .....                              | 20 |
+| 6.5.1.6                | Exceptions.....                                   | 20 |
+| 6.6                    | subscriptionFilterOperations Interface (O) .....  | 20 |
+| 6.6.1                  | Operation changeSubscriptionFilter (M).....       | 20 |
+| 6.6.1.1                | Definition .....                                  | 20 |
+| 6.6.1.2                | Input parameters .....                            | 20 |
+| 6.6.1.3                | Output parameters.....                            | 21 |
+| 6.6.1.4                | Pre-condition.....                                | 21 |
+| 6.6.1.5                | Post-condition .....                              | 21 |
+| 6.6.1.6                | Exceptions.....                                   | 21 |
+| 6.7                    | subscriptionSuspendOperations Interface (O) ..... | 21 |
+| 6.7.1                  | Operation suspendSubscription (M) .....           | 21 |
+| 6.7.1.1                | Definition .....                                  | 21 |
+| 6.7.1.2                | Input parameters .....                            | 21 |
+| 6.7.1.3                | Output parameters.....                            | 21 |
+| 6.7.1.4                | Pre-condition.....                                | 22 |
+| 6.7.1.5                | Post-condition .....                              | 22 |
+| 6.7.1.6                | Exceptions.....                                   | 22 |
+| 6.7.2                  | Operation resumeSubscription (M).....             | 22 |
+| 6.7.2.1                | Definition .....                                  | 22 |
+| 6.7.2.2                | Input parameters .....                            | 22 |
+| 6.7.2.3                | Output parameters.....                            | 22 |
+| 6.7.2.4                | Pre-condition.....                                | 22 |
+| 6.7.2.5                | Post-condition .....                              | 23 |
+| 6.7.2.6                | Exceptions.....                                   | 23 |
+| 6.8                    | IRPManagementOperations Interface (O) .....       | 24 |
+| 6.8.1                  | Operation getNotificationCategories (M).....      | 24 |
+| 6.8.1.1                | Definition .....                                  | 24 |
+| 6.8.1.2                | Input parameters .....                            | 24 |
+| 6.8.1.3                | Output parameters.....                            | 24 |
+| 6.8.1.4                | Pre-condition.....                                | 24 |
+| 6.8.1.5                | Post-condition .....                              | 24 |
+| 6.8.1.6                | Exceptions.....                                   | 24 |
+| 6.9                    | NotificationIRPNotification Interface.....        | 25 |
+| Annex A (informative): | Change history.....                               | 27 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements
+- 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)**
+- 32.303: Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
+- 32.305: Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition
+- 32.307: Configuration Management (CM); Notification Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS)
+
+The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [5] and 3GPP TS 32.102 [6].
+
+Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in Alarm IRP: Information Service [1], is one possible kind of event, an object creation as specified in Basic CM IRP: Information Service [8] is another possible kind of event.
+
+Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to IRPAgent for receiving notifications.
+
+This IRP bases its design on work captured in ITU-T Recommendation X.734 [2], OMG Notification Service [4]. The central design ideas are:
+
+- Separation of notification Consumers (IRPManagers) from Producers (IRPAgents);
+- Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications.
+
+Common characteristics related to notifications in all other IRPs are gathered in one IRP.
+
+# --- 1 Scope
+
+The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Information Service" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
+
+An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information Service [1]) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent's emission of notifications (suspendSubscription and resumeSubscription operations).
+
+Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
+
+Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
+
+This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, *perceivedSeverity* is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP: Information Service [1].
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
+
+# --- 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.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [2] ITU-T Recommendation X.734 (1992): "Information technology - Open Systems Interconnection - Systems management: Event report management function".
+- [3] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+- [4] OMG: "OMG Notification Service". <http://www.omg.org/technology/documents/>
+- [5] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [6] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [7] 3GPP TS 32.301: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements".
+
+- [8] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
+- [9] Void.
+- [10] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management: Information Service (IS)".
+- [11] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements".
+- [12] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [5], 3GPP TS 32.102 [6] and 3GPP TS 32.301 [7] and the following apply:
+
+**IRP Agent:** See 3GPP TS 32.102 [6].
+
+**IRP Manager:** See 3GPP TS 32.102 [6].
+
+**event:** it is an occurrence that is of significance to network operators, the NEs under surveillance and network management applications
+
+Events can indicate many types of network management information, such as network alarms, network configuration change information and network performance data.
+
+**notification:** it refers to the transport of information regarding events from event producer to consumer (receiver)  
+In this IRP, notification is used to carry information about network events from IRP Agent to IRP Manager. Producer sends notifications to consumers as soon as new events occur. Consumer does not need to check ("pull") for events.
+
+**IRP:** See 3GPP TS 32.102 [6].
+
+**notification category:** The semantics and syntax of the notification category string are identical to that defined for "IRP document version number string", see 3GPP TS 32.311 [11] subclause 3.1.
+
+**qualifiers:** the meaning of qualifiers for operations, parameters and information attributes (whether they are Mandatory(M)/ Conditional(C)/ Optional(O)) defined in the present (Information Service) document is provided in 3GPP TS 32.102 [6].
+
+Moreover, qualifiers of information attributes, when those information attributes are re-used in other IRP ISs, obey to the following rule: Mandatory and Conditional qualifiers of information attributes shall always be the same in other IRPs ISs, Optional qualifiers of information attributes may be set to either Optional or Mandatory in the other IRP ISs.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                           |
+|-------|-------------------------------------------|
+| CM    | Configuration Management                  |
+| CORBA | Common Object Request Broker Architecture |
+| DN    | Distinguished Name                        |
+| EM    | Element Manager                           |
+| IOC   | Information Object Class                  |
+| IRP   | Integration Reference Point               |
+| IS    | Information Service                       |
+| NE    | Network Element                           |
+| NM    | Network Manager                           |
+| NR    | Network Resource                          |
+| NRM   | Network Resource Model                    |
+| OMG   | Object Management Group                   |
+| SS    | Solution Set                              |
+
+# 4 System overview
+
+## 4.1 System Context
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [12] subclause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in figure 1 and figure 2.
+
+![Figure 1: System Context A. A UML diagram showing an IRPManager (NM) connected to an IRPAgent (EM), which is connected to multiple NEs. A dashed vertical line separates the NM and EM. A curved arrow labeled 'Itf-N' points from the EM side to the NM side, with the text 'Notification IRP' next to it.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg)
+
+The diagram illustrates System Context A. On the left, a box labeled 'IRPManager' is associated with 'NM'. On the right, a box labeled 'IRPAgent' is associated with 'EM'. A solid horizontal line connects the IRPManager and the IRPAgent. To the right of the IRPAgent, a dotted line connects it to a box labeled 'NEs'. A dashed vertical line runs between the IRPManager and the IRPAgent. A curved arrow labeled 'Itf-N' originates from the IRPAgent side and points towards the IRPManager side, with the text 'Notification IRP' positioned next to the arrow.
+
+Figure 1: System Context A. A UML diagram showing an IRPManager (NM) connected to an IRPAgent (EM), which is connected to multiple NEs. A dashed vertical line separates the NM and EM. A curved arrow labeled 'Itf-N' points from the EM side to the NM side, with the text 'Notification IRP' next to it.
+
+Figure 1: System Context A
+
+![Figure 2: System Context B. A UML diagram showing an IRPManager (NM) connected to an IRPAgent (NE). A dashed vertical line separates the NM and NE. A curved arrow labeled 'Itf-N' points from the NE side to the NM side, with the text 'Notification IRP' next to it.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg)
+
+The diagram illustrates System Context B. On the left, a box labeled 'IRPManager' is associated with 'NM'. On the right, a box labeled 'IRPAgent' is associated with 'NE'. A solid horizontal line connects the IRPManager and the IRPAgent. A dashed vertical line runs between the IRPManager and the IRPAgent. A curved arrow labeled 'Itf-N' originates from the IRPAgent side and points towards the IRPManager side, with the text 'Notification IRP' positioned next to the arrow.
+
+Figure 2: System Context B. A UML diagram showing an IRPManager (NM) connected to an IRPAgent (NE). A dashed vertical line separates the NM and NE. A curved arrow labeled 'Itf-N' points from the NE side to the NM side, with the text 'Notification IRP' next to it.
+
+Figure 2: System Context B
+
+# 5 Information Object Classes
+
+## 5.1 Imported information entities and local labels
+
+| Label reference                                     | Local label       |
+|-----------------------------------------------------|-------------------|
+| 3GPP TS 32.312 [10], Support IOC, ManagedGenericIRP | ManagedGenericIRP |
+
+## 5.2 Class Diagram
+
+### 5.2.1 Attributes and relationships
+
+This subclause depicts the set of Support IOCs that encapsulate information within the notification IRP. The intent is to identify the information required for the notification IRP implementation of its operations and notification emission.
+
+This subclause provides the overview of all Support IOCs in UML. Subsequent subclauses provide more detailed specification of various aspects of these Support IOCs.
+
+![UML Class Diagram showing relationships between NotificationIRP, NtfSubscriber, and NtfSubscription.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+```
+classDiagram
+    class NotificationIRP {
+        <<SupportIOC>>
+    }
+    class NtfSubscriber {
+        <<SupportIOC>>
+    }
+    class NtfSubscription {
+        <<SupportIOC>>
+    }
+    NotificationIRP "1" *-- "0..n" NtfSubscriber : +theNotificationIRP
+    NtfSubscriber "1" -- "1..n" NtfSubscription : +theNtfSubscriber, +theNtfSubscription
+```
+
+The diagram illustrates three classes: **<<SupportIOC>> NotificationIRP**, **<<SupportIOC>> NtfSubscriber**, and **<<SupportIOC>> NtfSubscription**. **NotificationIRP** has a composition relationship with **NtfSubscriber** (multiplicity 1 to 0..n), labeled **+theNotificationIRP** and **relation-ntfIRP-ntfSubscriber**. **NtfSubscriber** has an association relationship with **NtfSubscription** (multiplicity 1 to 1..n), labeled **+theNtfSubscriber** and **+theNtfSubscription**, and **relation-ntfSubscriber-ntfSubscription**.
+
+UML Class Diagram showing relationships between NotificationIRP, NtfSubscriber, and NtfSubscription.
+
+### 5.2.2 Inheritance
+
+This subclause depicts the inheritance relationships that exist between Support IOCs.
+
+![UML Class Diagram showing inheritance from NotificationIRP to ManagedGenericIRP.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg)
+
+```
+classDiagram
+    class ManagedGenericIRP {
+        <<SupportIOC>>
+        (from TS 32.312)
+    }
+    class NotificationIRP {
+        <<SupportIOC>>
+    }
+    NotificationIRP --|> ManagedGenericIRP
+```
+
+The diagram shows an inheritance relationship where **<<SupportIOC>> NotificationIRP** inherits from **<<SupportIOC>> ManagedGenericIRP (from TS 32.312)**.
+
+UML Class Diagram showing inheritance from NotificationIRP to ManagedGenericIRP.
+
+## 5.3 Information object classes definition
+
+### 5.3.1 NtfSubscriber
+
+#### 5.3.1.1 Definition
+
+This Support IOC represents a Subscriber from a notification IRP perspective : a subscriber is fully identified by a manager reference. An IRPManager using multiple managerReference attributes to subscribe will result in multiple NtfSubscriber instances.
+
+#### 5.3.1.2 Attributes
+
+| Attribute name      | Support Qualifier | Read Qualifier | Write Qualifier |
+|---------------------|-------------------|----------------|-----------------|
+| ntfManagerReference | M                 | M              | M               |
+
+### 5.3.2 NtfSubscription
+
+#### 5.3.2.1 Definition
+
+This Support IOC represents a subscription that has been requested by an IRPManager and created.
+
+#### 5.3.2.2 Attributes
+
+| Attribute name             | Support Qualifier | Read Qualifier | Write Qualifier |
+|----------------------------|-------------------|----------------|-----------------|
+| ntfSubscriptionId          | M                 | M              | -               |
+| ntfSubscriptionState       | M                 | M              | M               |
+| ntfTimeTick                | M                 | M              | M               |
+| ntfTimeTickTimer           | M                 | -              | -               |
+| ntfNotificationCategorySet | M                 | M              | M               |
+| ntfFilter                  | M                 | M              | M               |
+
+#### 5.3.2.3 State diagram
+
+The diagram below depicts states that can be supported by a NtfSubscription.
+
+![State diagram for NtfSubscription showing states notSuspended and suspended, with transitions for subscribe, suspendSubscription, resumeSubscription, and unsubscribe.](7f17c430b9598e4d748a8041457810b3_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> notSuspended : subscribe / ntfTimeTickTimer initialised
+    notSuspended --> notSuspended : resumeSubscription
+    notSuspended --> notSuspended : ntfTimeTickTimer=0 / ntfSubscription is not deleted
+    notSuspended --> notSuspended : getSubscriptionStatus / ntfTimeTickTimer re-initialised
+    notSuspended --> suspended : suspendSubscription
+    suspended --> notSuspended : resumeSubscription
+    suspended --> suspended : suspendSubscription
+    notSuspended --> [*] : ntfTimeTickTimer=0 / ntfSubscription (and possibly ntfSubscriber) is deleted.
+    suspended --> [*] : unSubscribe / ntfSubscription (and possibly ntfSubscriber) is deleted
+
+```
+
+The state diagram illustrates the lifecycle of a `NtfSubscription`. It begins at an initial state, transitioning to `notSuspended` via a `subscribe` event that initializes the `ntfTimeTickTimer`. From `notSuspended`, a `resumeSubscription` event loops back to the same state, while a `suspendSubscription` event transitions to the `suspended` state. From `suspended`, a `resumeSubscription` event returns to `notSuspended`. Both states can transition to the final state: `notSuspended` via a `ntfTimeTickTimer=0` event (deleting the subscription and possibly the subscriber) or `suspended` via an `unSubscribe` event (also deleting the subscription and possibly the subscriber). Additionally, `notSuspended` has self-transitions for `ntfTimeTickTimer=0` (if the subscription is not deleted) and `getSubscriptionStatus` (re-initializing the timer).
+
+State diagram for NtfSubscription showing states notSuspended and suspended, with transitions for subscribe, suspendSubscription, resumeSubscription, and unsubscribe.
+
+NotificationIRP can lose the list of `managerReference` that identifies current IRPManagers under subscription. Under this condition, IRPAgent is incapable of sending events to the affected subscriber(s).
+
+This Notification IRP recommends that IRPManager should invoke the `getSubscriptionStatus` operation periodically to confirm that IRPAgent still has the IRPManager's reference in its list. In case `getSubscriptionStatus` returns the exception `operation_failed`, IRPManager should assume that IRPAgent has lost the IRPManager's reference.
+
+This IRP does not recommend the frequency IRPManager should use to invoke `getSubscriptionStatus` operation.
+
+### 5.3.3 NotificationIRP
+
+#### 5.3.3.1 Definition
+
+This Support IOC represents a notification IRP. It inherits from Support IOC `ManagedGenericIRP`.
+
+## 5.4 Information relationship definitions
+
+### 5.4.1 relation-ntfSubscriber-ntfSubscription (M)
+
+#### 5.4.1.1 Definition
+
+This relationship defines the relationship between a NtfSubscriber and its current subscriptions.
+
+#### 5.4.1.2 Roles
+
+| Name               | Definition                                                                                                                                |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| theNtfSubscriber   | This role represents the one who has subscribed. It can be played by instances of Support IOC NtfSubscriber                               |
+| theNtfSubscription | This role represents the subscriptions which were made and not unsubscribed. It can be played by instances of Support IOC NtfSubscription |
+
+#### 5.4.1.3 Constraints
+
+| Name                                  | Definition                                                                                                                                                                 |
+|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| inv_notificationCategoriesAllDistinct | The notification categories contained in the ntfNotificationCategorySet attribute of NtfSubscription playing the role theNtfSubscription are all distinct from each other. |
+
+### 5.4.2 relation-ntfIRP-ntfSubscriber (M)
+
+#### 5.4.2.1 Definition
+
+This relationship defines the relationship between the NotificationIRP and the current subscribers of notifications.
+
+#### 5.4.2.2 Roles
+
+| Name               | Definition                                                                                                                               |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| theNtfSubscriber   | This role represents the entities to which IRPAgent will notify events. It is played by instances of Support IOC NtfSubscriber           |
+| theNotificationIRP | This role represents the NotificationIRP to which an IRPManager has subscribed. It is played by instances of Support IOC NotificationIRP |
+
+#### 5.4.2.3 Constraints
+
+| Name                       | Definition                                                                                                                                                             |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| inv_uniqueManagerReference | All NtfSubscriber involved in the subscriptionRegistration relationship with NotificationIRP are distinguished from each other by their ntfManagerReference Attribute. |
+
+## 5.5 Information attribute definitions
+
+This subclause defines the semantics of the Attributes used in Support IOCs.
+
+### 5.5.1 Definitions and legal values
+
+| Attribute Name             | Definition                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Legal Values                                                                             |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| ntfSubscriptionId          | It identifies uniquely a subscription                                                                                                                                                                                                                                                                                                                                                                                                                         | N/A                                                                                      |
+| ntfSubscriptionState       | It indicates the activation state of a subscription                                                                                                                                                                                                                                                                                                                                                                                                           | "suspended": the subscription is suspended<br>"notSuspended": the subscription is active |
+| ntfTimeTick                | this Attribute represents the initial value of ntfTimeTickTimer. It is in unit of whole minute. This value defines a time window within which IRPManager intends to invoke <code>getSubscriptionStatus</code> (or <code>subscribe</code> ) operation to confirm its subscription. A special value indicates infinity which is such that timer will never expire and IRPAgent needs other means to decide when to delete resources allocated to the IRPManager | Integer greater or equal to 15, OR special infinite value                                |
+| ntfTimeTickTimer           | this Attribute represents the current value of a timer                                                                                                                                                                                                                                                                                                                                                                                                        | integer greater or equal to zero                                                         |
+| ntfNotificationCategorySet | this Attribute represents a set of notification categories (see also Definition of notification category in subclause 3.1)                                                                                                                                                                                                                                                                                                                                    |                                                                                          |
+| ntfFilter                  | this Attribute represents the filter of a subscription. The filter can be applied to parameters of notification header (see <code>NotificationIRPNotification</code> interface) and to parameters of notifications defined as filterable in other IRP ISs. IRPAgent shall notify IRPManagers if the event satisfies the filter constraint.                                                                                                                    |                                                                                          |
+| ntfManagerReference        | this Attribute contains the reference of a manager. It uniquely identifies a subscriber                                                                                                                                                                                                                                                                                                                                                                       |                                                                                          |
+
+### 5.5.2 Constraints
+
+- "ntfTimeTickTimer is lower or equal to ntfTimeTick".
+
+# 6 Interface Definition
+
+## 6.1 Class diagram representing interfaces
+
+![UML Class diagram showing the NotificationIRP interface and its associated interfaces.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg)
+
+```
+
+classDiagram
+    class SubscriptionStatusOperations {
+        <<Interface>>
+        getSubscriptionStatus()
+    }
+    class SubscriptionFilterOperations {
+        <<Interface>>
+        changeSubscriptionFilter()
+    }
+    class SubscriptionSuspendOperations {
+        <<Interface>>
+        suspendSubscription()
+        resumeSubscription()
+    }
+    class IRPManagementOperations {
+        <<Interface>>
+        getNotificationCategories()
+    }
+    class NotificationIRPManagement {
+        <<Interface>>
+        subscribe()
+        unsubscribe()
+    }
+    class SubscriberManagement {
+        <<Interface>>
+        getSubscriptionIds()
+    }
+    class NotificationIRP {
+        <<SupportIOC>>
+    }
+    class NotificationIRPNotification {
+        <<Interface>>
+        notify()
+    }
+
+    NotificationIRP --> SubscriptionStatusOperations : <<may realize>>
+    NotificationIRP --> SubscriptionFilterOperations : <<may realize>>
+    NotificationIRP --> SubscriptionSuspendOperations : <<may realize>>
+    NotificationIRP --> IRPManagementOperations : <<may realize>>
+    NotificationIRP --> NotificationIRPManagement : <<may realize>>
+    NotificationIRP --> SubscriberManagement : <<may realize>>
+    NotificationIRP --> NotificationIRPNotification : <<use>> 0..1
+  
+```
+
+This <<interface>> defines the notificationHeader. Other <<interface>>, such as AlarmIRPNotification, inherits from this <<interface>> and the notifications emitted by these other <<interface>> shall support the inherited notificationHeader.
+
+UML Class diagram showing the NotificationIRP interface and its associated interfaces.
+
+## 6.2 Generic rules
+
+- Rule 1:** Each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+- Rule 2:** Each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+- Rule 3:** Each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 notificationIRPManagement Interface (M)
+
+### 6.3.1 Operation `subscribe` (M)
+
+#### 6.3.1.1 Definition
+
+IRPManager invokes this operation to establish subscription to receive network events via notifications, under the filter constraint specified in this operation.
+
+#### 6.3.1.2 Input parameters
+
+| Parameter Name         | Qualifier | Information Type                                                           | Comment                                                                                                                                                                                                                      |
+|------------------------|-----------|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| managerReference       | M         | NtfSubscriber.ntfManagerReference                                          | It specifies the reference of IRPManager to which notifications shall be sent.                                                                                                                                               |
+| timeTick               | O         | NtfSubscription.ntfTimeTick                                                | It specifies the value of a timer hold by NotificationIRP for the subject IRPManager.<br>The value is in unit of whole minute.<br>A special infinite value is assumed when parameter is absent or present but equal to zero. |
+| notificationCategories | O         | SET OF (name of IRP, version of IRP)                                       | It identifies one or more Notification Category (see also Definition in subclause 3.1)                                                                                                                                       |
+| filter                 | O         | NtfSubscription.ntfFilter<br><br>Filter constraint grammar is SS dependent | It specifies a filter constraint that IRPAgent shall use to filter notification of the category specified in notificationCategories parameter.<br>If this parameter is absent, then no filter constraint shall be applied.   |
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                                                            | Comment                                                                                                                                                                                                                   |
+|----------------|-----------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionId | M         | NtfSubscription.ntfSubscriptionId                                               | It holds an unambiguous identity of this subscription.                                                                                                                                                                    |
+| status         | M         | ENUM (OperationSucceeded, OperationFailedExistingSubscription, OperationFailed) | If subscriptionCreated is true, status = OperationSucceeded.<br>If operation_failed_existing_subscription is true, status = OperationFailedExistingSubscription<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.3.1.4 Pre-condition
+
+notificationCategoriesNotAllSubscribed OR notificationCategoriesParameterAbsentAndNotAllSubscribed.
+
+| Assertion Name                                           | Definition                                                                                                                                                                                                                                                                                                                            |
+|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| notificationCategoriesNotAllSubscribed                   | At least one notificationCategory identified in the notificationCategories input parameter is supported by IRPAgent and is not a member of the ntfNotificationCategorySet attribute of an NtfSubscription which is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter. |
+| notificationCategoriesParameterAbsentAndNotAllSubscribed | The notificationCategories input parameter is absent and at least one notificationCategory supported by IRPAgent is not a member of the ntfNotificationCategorySet attribute of an ntfSubscription which is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter.        |
+
+#### 6.3.1.5 Post-condition
+
+subscriberPossiblyCreated AND subscriptionCreated.
+
+| Assertion Name            | Definition                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriberPossiblyCreated | An NtfSubscriber with a ntfManagerReference attribute equal to the value of the managerReference input parameter is involved in a subscriptionRegistration relationship with NotificationIRP.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| subscriptionCreated       | An NtfSubscription has been created according to the following rules: <ul style="list-style-type: none"> <li>ntfSubscriptionState attribute value has been set to "notSuspended";</li> <li>ntfTimeTick attribute value has been set to the value of the timeTick input parameter if this value was higher or equal to 15, or set to 15 if this parameter value was between 1 and 15, or set to a special infinite value if the parameter value was lower or equal to 0 or if parameter was absent;</li> <li>ntfTimeTickTimer has been reset with the value of timeTick attribute;</li> <li>ntfFilter attribute value has been set to the value of the filter input parameter if present;</li> <li>NtfSubscription is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter;</li> <li>attribute ntfNotificationCategorySet of NtfSubscription contains EITHER the notification categories identified by the notificationCategories input parameter that were not already contained in the ntfNotificationCategorySet attribute of other NtfSubscription of the same NtfSubscriber identified by the managerReference input parameter OR if notificationCategories input parameter is absent, all notification categories supported by IRPAgent that were not already contained in the ntfNotificationCategorySet attribute of other subscriptions of the same NtfSubscriber identified by the managerReference input parameter.</li> </ul> |
+
+#### 6.3.1.6 Exceptions
+
+| Name                                   | Definition                                                                                                                                                                                                                    |
+|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed_existing_subscription | <b>Condition:</b> (notificationCategoriesNotAllSubscribed OR notificationCategoriesParameterAbsentAndNotAllSubscribed) not true<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+| Operation_failed                       | <b>Condition:</b> Post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State                                                                                       |
+
+### 6.3.2 Operation unsubscribe (M)
+
+#### 6.3.2.1 Definition
+
+The IRPManager invokes this operation to cancel subscriptions. The IRPManager can cancel one subscription made with a managerReference by providing the corresponding subscriptionId or all subscriptions made with the same managerReference by leaving the subscriptionId parameter absent.
+
+#### 6.3.2.2 Input parameters
+
+| Parameter Name   | Qualifier | Information Type                  | Comment                                                                               |
+|------------------|-----------|-----------------------------------|---------------------------------------------------------------------------------------|
+| managerReference | M         | NtfSubscriber.ntfManagerReference | It specifies the reference of an IRPManager.                                          |
+| subscriptionId   | O         | NtfSubscription.ntfSubscriptionId | It holds a subscriptionId carried as the output parameter in the subscribe operation. |
+
+#### 6.3.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                          | Comment                                                                                                                                            |
+|----------------|-----------|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| status         | M         | ENUM<br>(OperationSucceeded, OperationFailed) | If (subscriptionDeleted OR allSubscriptionDeleted) is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.3.2.4 Pre-condition
+
+validSubscriptionId&ManagerReference OR SubscriptionIdAbsent&ValidManagerReference
+
+| Assertion Name                             | Definition                                                                                                                                                                             |
+|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId&ManagerReference       | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter. |
+| SubscriptionIdAbsent&ValidManagerReference | The subscriptionId input parameter is absent and the NtfSubscriber identified by the managerReference input parameter exists.                                                          |
+
+#### 6.3.2.5 Post-condition
+
+subscriptionDeleted OR allSubscriptionDeleted.
+
+| Assertion Name         | Definition                                                                                                                                                                                                                                                                                    |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionDeleted    | The NtfSubscription identified by subscriptionId input parameter is no more involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter and has been deleted. If this NtfSubscriber has no more NtfSubscription, it is deleted as well. |
+| allSubscriptionDeleted | In the case subscriptionId input parameter was absent, the NtfSubscriber identified by the managerReference input parameter is no more involved in any subscription relationship and is deleted, the corresponding NtfSubscription have been deleted as well.                                 |
+
+#### 6.3.2.6 Exceptions
+
+| Name             | Definition                                                                                                                                                        |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.4 subscriberManagement Interface (O)
+
+### 6.4.1 Operation getSubscriptionIds (M)
+
+#### 6.4.1.1 Definition
+
+IRPManager invokes this operation to get the values of all still valid (not unsubscribed or removed by IRPAgent) subscriptionIds assigned by NotificationIRP as result of previously subscribe operations performed by this IRPManager.
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name   | Qualifier | Information Type                  | Comment                                                                                                                           |
+|------------------|-----------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| managerReference | M         | NtfSubscriber.ntfManagerReference | It specifies the reference of IRPManager that requests the set of identifiers of active subscriptions related to this IRPManager. |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name    | Qualifier | Matching Information                                                                                                                                                                | Comment                                                                                                                                                                                                                                                                                           |
+|-------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionIdSet | M         | SET OF NtfSubscription.ntfSubscriptionId where NtfSubscription is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter | It holds a set of the subscriptionId, each assigned as output parameter in previous subscribe operations invoked by the current IRPManager. This value should contain no information if the IRPManager did not yet subscribed to that System or System lost all subscription related information. |
+| status            | M         | ENUM (Operation succeeded, Operation failed)                                                                                                                                        | If validSubscriptionIdSet is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed.                                                                                                                                                                         |
+
+#### 6.4.1.4 Pre-condition
+
+validManagerReference.
+
+| Assertion Name        | Definition                                                                   |
+|-----------------------|------------------------------------------------------------------------------|
+| validManagerReference | The NtfSubscriber identified by the managerReference input parameter exists. |
+
+#### 6.4.1.5 Post-condition
+
+None specific
+
+#### 6.4.1.6 Exceptions
+
+| Name             | Definition                                                                                                                             |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.5 subscriptionStatusOperations Interface (O)
+
+### 6.5.1 Operation getSubscriptionStatus (M)
+
+#### 6.5.1.1 Definition
+
+IRPManager invokes this operation to query the subscription status of a particular subscription. IRPManager can use getSubscriptionStatus operation to know about the filter constraint in effect, the state of subscription (i.e. if subscription is suspended/inactive or resumed/active), the timeTick value that may be set at subscribe invocation time and the notificationCategory currently in used in the subscription.
+
+#### 6.5.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type                  | Comment                                                                                |
+|----------------|-----------|-----------------------------------|----------------------------------------------------------------------------------------|
+| subscriptionId | M         | NtfSubscription.ntfSubscriptionId | It holds the subscriptionId carried as the output parameter in the subscribe operation |
+
+#### 6.5.1.3 Output parameters
+
+| Parameter Name          | Qualifier | Matching Information                         | Comment                                                                                                            |
+|-------------------------|-----------|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| notificationCategorySet | C         | NtfSubscription.ntfNotificationCategorySet   | It identifies the notification Category(ies) supported in this subscription.                                       |
+| filterInEffect          | O         | NtfSubscription.ntfFilter                    | It contains the filter constraint currently set.                                                                   |
+| SubscriptionState       | O         | NtfSubscription.ntfSubscriptionState         |                                                                                                                    |
+| timeTick                | O         | NtfSubscription.ntfTimeTick                  | It carries the same value as the one in subscribe operation                                                        |
+| status                  | M         | ENUM (Operation succeeded, Operation failed) | If (timeTickReset) is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.5.1.4 Pre-condition
+
+validSubscriptionId.
+
+| Assertion Name      | Definition                                                                                                    |
+|---------------------|---------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId | "the NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship" |
+
+#### 6.5.1.5 Post-condition
+
+timeTickReset
+
+| Assertion Name | Definition                                                                                                                                                          |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| timeTickReset  | The ntfTimeTickTimer attribute of NtfSubscription identified as input parameter has been reset with the value of ntfTimeTick attribute of the same NtfSubscription. |
+
+#### 6.5.1.6 Exceptions
+
+| Name             | Definition                                                                                                                                                        |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.6 subscriptionFilterOperations Interface (O)
+
+### 6.6.1 Operation changeSubscriptionFilter (M)
+
+#### 6.6.1.1 Definition
+
+IRPManager invokes this operation to replace the present filter constraint with a new one.
+
+#### 6.6.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type                  | Comment                                                                                   |
+|----------------|-----------|-----------------------------------|-------------------------------------------------------------------------------------------|
+| subscriptionId | M         | NtfSubscription.ntfSubscriptionId | It carries the subscriptionId carried as the output parameter in the subscribe operation. |
+| filter         | M         | NtfSubscription.ntfFilter         | It specifies a filter constraint                                                          |
+
+#### 6.6.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                         | Comment                                                                                                          |
+|----------------|-----------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| status         | M         | ENUM (Operation succeeded, Operation failed) | If filterUpdated is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.6.1.4 Pre-condition
+
+validNtfSubscriptionId.
+
+| Assertion Name         | Definition                                                                                                   |
+|------------------------|--------------------------------------------------------------------------------------------------------------|
+| validNtfSubscriptionId | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship. |
+
+#### 6.6.1.5 Post-condition
+
+filterUpdated.
+
+| Assertion Name | Definition                                                                                                                                                 |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| filterUpdated  | The ntfFilter attribute value of the NtfSubscription identified by subscriptionId input parameter has been set to the value of the filter input parameter. |
+
+#### 6.6.1.6 Exceptions
+
+| Name             | Definition                                                                                                                                                        |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.7 subscriptionSuspendOperations Interface (O)
+
+### 6.7.1 Operation suspendSubscription (M)
+
+#### 6.7.1.1 Definition
+
+IRPManager invokes this operation to request IRPAgent to stop emission of notifications. IRPAgent may lose notification(s) if subscription is suspended.
+
+#### 6.7.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type                  | Comment                                                                                   |
+|----------------|-----------|-----------------------------------|-------------------------------------------------------------------------------------------|
+| subscriptionId | M         | NtfSubscription.ntfSubscriptionId | It carries the subscriptionId carried as the output parameter in the subscribe operation. |
+
+#### 6.7.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                         | Comment                                                                                                                       |
+|----------------|-----------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| status         | M         | ENUM (Operation succeeded, Operation failed) | If subscriptionStateSuspended is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.7.1.4 Pre-condition
+
+validSubscriptionId.
+
+| Assertion Name      | Definition                                                                                                   |
+|---------------------|--------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship. |
+
+#### 6.7.1.5 Post-condition
+
+subscriptionStateSuspended.
+
+| Assertion Name             | Definition                                                                                                                                           |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionStateSuspended | The ntfSubscriptionState attribute value of the NtfSubscription identified by subscriptionId input parameter has been set to or kept as "suspended". |
+
+#### 6.7.1.6 Exceptions
+
+| Name             | Definition                                                                                                                                                        |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+### 6.7.2 Operation resumeSubscription (M)
+
+#### 6.7.2.1 Definition
+
+IRPManager invokes this operation to request IRPAgent to resume emission of notifications.
+
+#### 6.7.2.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type                  | Comment                                                                                   |
+|----------------|-----------|-----------------------------------|-------------------------------------------------------------------------------------------|
+| subscriptionId | M         | NtfSubscription.ntfSubscriptionId | It carries the subscriptionId carried as the output parameter in the subscribe operation. |
+
+#### 6.7.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information                         | Comment                                                                                                                          |
+|----------------|-----------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| status         | M         | ENUM (Operation succeeded, Operation failed) | If subscriptionStateNotSuspended is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.7.2.4 Pre-condition
+
+validSubscriptionId.
+
+| Assertion Name      | Definition                                                                                                   |
+|---------------------|--------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship. |
+
+#### 6.7.2.5 Post-condition
+
+subscriptionStateNotSuspended.
+
+| Assertion Name                | Definition                                                                                                                                              |
+|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionStateNotSuspended | The ntfSubscriptionState attribute value of the NtfSubscription identified by subscriptionId input parameter has been set to or kept as "notSuspended". |
+
+#### 6.7.2.6 Exceptions
+
+| Name             | Definition                                                                                                                                                        |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.8 IRPManagementOperations Interface (O)
+
+### 6.8.1 Operation getNotificationCategories (M)
+
+#### 6.8.1.1 Definition
+
+IRPManager invokes this operation to query the categories of notification supported by IRPAgent. IRPAgent returns the list of categories of notification supported. Each category of notification defines the name and the version of the IRP specification. The list of category of notification returned shall only contain the name and version of the IRP specifications that actually have notifications defined.
+
+IRPManager does not need to be in subscription to invoke this operation.
+
+#### 6.8.1.2 Input parameters
+
+None.
+
+#### 6.8.1.3 Output parameters
+
+| Parameter Name           | Qualifier | Matching Information                                                                                                                                                    | Comment                                                   |
+|--------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|
+| NotificationCategoryList | M         | SET OF (name and version of IRP specification) where each IRP is contained by IRPAgent and the attribute notificationNameProfile of the ManagedGenericIRP is not empty. |                                                           |
+| status                   | M         | ENUM (Operation succeeded, Operation failed)                                                                                                                            | OperationFailed only if operation_failed_internal_problem |
+
+#### 6.8.1.4 Pre-condition
+
+None specific.
+
+#### 6.8.1.5 Post-condition
+
+None specific.
+
+#### 6.8.1.6 Exceptions
+
+None specific.
+
+## 6.9 NotificationIRPNotification Interface
+
+IRP Agent notifies the subscribed IRP Manager that an event has occurred and that the event has satisfied the filter constraints used for this subscription. One event example is the notification defined in Alarm IRP: IS (3GPP TS 32.111-2 [1]).
+
+It should be possible to pack multiple notifications together for sending to NM. This provides more efficient use of data communication resources. In order to pack multiple notifications, an EM/NE configurable parameter defines the maximum number of notifications to be packed together. Additionally an EM/NE configurable parameter defines the maximum time delay before the notifications have to be sent.
+
+Under normal operations, an IRP Agent shall send, to each IRP Manager, notifications in the same order they were generated, i.e. in the First-In, First-Out order. There shall not be any priority given to types of notifications.
+
+This interface doesn't define any specific notification but instead defines information that is commonly found in notifications defined by other IRPs. This information is called notificationHeader. Notification interfaces defined in other IRPs, such as Alarm IRP: IS (3GPP TS 32.111-2 [1]), shall inherit from this interface and define their notifications by:
+
+- Identifying and qualifying the Notification Header attributes for their use;
+- Specify additional attributes specific to their use.
+
+Despite the fact that the semantic of notifications is defined by other IRP ISs, it is notification IRP and not those IRP that is responsible for the emission of those notifications.
+
+The Notification Header is defined here below.
+
+| Attribute Name   | Qualifier | Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|------------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| objectClass      | M, Y      | It specifies the class name of the IOC. A network event has occurred in an instance of this class.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| objectInstance   | M, Y      | It specifies the instance of the above IOC in which the network event occurred by carrying the Distinguished Name (DN) of this object instance. This object may or may not be identical to the object instance actually emitting the notification.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| notificationId   | O,N       | <p>This is an identifier for the notification, which may be used to correlate notifications. The identifier of the notification shall be chosen to be unique across all notifications of a particular managed object throughout the time that correlation is significant, it uniquely identifies the notification from other notifications generated by the subject Information Object.</p> <p>If IRPManager receives notifications from one IRPAgent, IRPManager shall use the identifier of the notification and the <code>objectInstance</code> to uniquely identify all received notifications.</p> <p>If IRPManager receives notifications from multiple IRPAgents and notifications of each Information Object are reported at most through one IRPAgent, IRPManager shall use the identifier of the notification and <code>objectInstance</code> to uniquely identify all received notifications.</p> <p>If IRPManager receives notifications from multiple IRPAgents and notifications of one or more Information Objects are reported through two or more IRPAgents, IRPManager shall use the identifier of the notification together with <code>objectInstance</code> and the identity of IRPAgent (<code>systemDN</code>), to uniquely identify all received notifications. If the information <code>systemDN</code> is absent, IRPManager needs other means, which are outside the scope of this IRP, to determine the identity of IRPAgent.</p> <p>How identifiers of notifications are re-used to correlate notifications is outside of the scope of this recommendation.</p> |
+| eventTime        | M, Y      | It indicates the event occurrence time. The semantics of Generalised Time specified by ITU-T shall be used here.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| systemDN         | C, Y      | <p>The <code>systemDN</code> of that notification shall carry either (1) the <code>IRPAgent</code> instance containing that Interface IRP instance, or (2) the DN of that particular Interface IRP instance responsible for the emission of the notification.</p> <p>(1) If the <code>IRPAgent</code> contains single (not multiple) Interface IRP instance of a particular class, then the <code>systemDN</code> of a notification may carry the DN of the <code>IRPAgent</code> or DN of the subject Interface IRP instance.</p> <p>(2) If the <code>IRPAgent</code> contains multiple Interface IRP instances of the same class, then the <code>systemDN</code> of a notification shall carry the DN of a particular Interface IRP instance responsible for the emission of that notification.</p> <p>Example of item (2) above:</p> <ul style="list-style-type: none"> <li>Alarm IRP:IS specifies <code>notifyNewAlarm</code>. If there are multiple <code>AlarmIRP</code> instances under one <code>IRPAgent</code>, then the <code>systemDN</code> of <code>notifyNewAlarm</code> shall be present and carry the DN of the <code>AlarmIRP</code>.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| notificationType | M, Y      | The type of notification which is reported by the notification                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+# Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                                                               |         |       |        |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------|---------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                                               | Ca<br>t | Old   | New    |
+| Jun 2001       | S_12  | SP-010283 | --   | --  | Approved at TSG SA #12 and placed under Change Control                                                                                        | --      | 2.0.0 | 4.0.0  |
+| Dec 2001       | S_14  | SP-010642 | 0001 | --  | Remove ambiguity of the return information for getNotificationCategories() operation                                                          | F       | 4.0.0 | 4.1.0  |
+| Dec 2001       | S_14  | SP-010653 | 0002 | --  | Change from Mandatory to Conditional the qualifier of the output parameter 'NotificationCategorySet' of the operation 'getSubscriptionStatus' | C       | 4.1.0 | 5.0.0  |
+| Mar 2002       | --    | --        | --   | --  | Cosmetics (changed styles on cover)                                                                                                           | --      | 5.0.0 | 5.0.1  |
+| Dec 2002       | --    | --        | --   | --  | Cosmetics                                                                                                                                     | --      | 5.0.1 | 5.0.2  |
+| Jun 2003       | S_20  | SP-030278 | 0004 | --  | Correction of the description of the objectClass and objectInstance parameter of the notification header                                      | A       | 5.0.2 | 5.1.0  |
+| Mar 2004       | S_23  | SP-040118 | 0005 | --  | Update Ntf IRP IS using new Template and UML Repertoire                                                                                       | F       | 5.1.0 | 6.0.0  |
+| Dec 2004       | S_26  | SP-040793 | 0007 | --  | Add missing rules on how to construct the string NotificationCategory                                                                         | A       | 6.0.0 | 6.1.0  |
+| Mar 2005       | S_27  | SP-050035 | 0008 | --  | Apply Generic System Context                                                                                                                  | F       | 6.1.0 | 6.2.0  |
+| Jun 2005       | --    | --        | --   | --  | Introduction update : added 32.305 new TS-family member                                                                                       | --      | 6.2.0 | 6.2.1  |
+| Mar 2006       | SA_31 | SP-060089 | 0009 | --  | Correct the use/meaning of systemDN in notification header                                                                                    | F       | 6.2.1 | 6.3.0  |
+| Jun 2007       | SA_36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards.                            | --      | 6.3.0 | 7.0.0  |
+| Dec 2008       | SA_42 | --        | --   | --  | Upgrade to Release 8                                                                                                                          | -       | 7.0.0 | 8.0.0  |
+| Dec 2009       | SA_46 | SP-090719 | 0010 | --  | Align usage of SupportIOC according to repertoire and template                                                                                | C       | 8.0.0 | 9.0.0  |
+| Sep 2010       | SA_49 | SP-100489 | 0011 | --  | Correction of incorrect attribute name for NtfSubscription                                                                                    | F       | 9.0.0 | 10.0.0 |

marked/Rel-10/32_series/32311/raw.md

@@ -0,0 +1,196 @@
+
+
+
+
+Keywords  
+UMTS, management
+
+# 3GPP TS 32.311 V10.1.0 (2011-12)
+
+*Technical Specification*
+
+## 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; c Integration Reference Point (IRP) management:
+
+3GPP support office address  
+050 Route des Lucioles - Sophia Antipolis  
+06410 VALBONNE - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+![LTE logo with '4ADVANCED' text above the 'e'.](b6cb8677b4ffb35c6468fa5c24091bff_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e'.
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a registered trademark symbol.](1211e36d120f0d2912a745437f4c8f19_img.jpg)
+
+3GPP logo with a registered trademark symbol.
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.  
+3GPP LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners.  
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.  
+GSM® and the GSM logo are registered and owned by the GSM Association.  
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.  
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices
+
+# --- 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 Generic IRP functions over Itf-N..... 6
+- 4.1 Version retrieval function..... 6
+- 4.2 Profiles retrieval functions ..... 6
+- Annex A (informative): Change history..... 8
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.311: "Generic Integration Reference Point (IRP) management; Requirements".**
+- 32.312: "Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- 32.316: " Generic Integration Reference Point (IRP) management; Solution Set (SS) Definitions".
+
+The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+The IRPs support a set of common services. Those features allow to retrieve IRP profile and IRP supported versions. The present document contains the requirements of those common services.
+
+# --- 1 Scope
+
+The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Requirements" part. It defines the requirements that shall be fulfilled by all IRPs, such as AlarmIRP, supporting this common service.
+
+With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP which is name-contained by an IRPAgent. An IRPManager shall also be able to retrieve the IRPVersions supported by the given IRP.
+
+# --- 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 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and the following apply:
+
+**IRP:** see 3GPP TS 32.102 [2].
+
+**IRPAgent:** see 3GPP TS 32.102 [2].
+
+**IRPManager:** see 3GPP TS 32.102 [2].
+
+**IRP document version number string:** the IRP document version number (sometimes called "IRPVersion") string is used to identify a technology of a particular IRP Solution Set (SS) specification and its version number.
+
+For Release 9 and earlier releases, it is derived using the following rule:
+
+Take the 3GPP TS/version number on the front page of the SS specification, such as "3GPP TS 32.111-3 V4.1.0 (2001-09)". Discard the leading "3GPP TS". Discard all characters after and including the last period. Eliminate leading and trailing spaces. Reduce multiple consecutive spaces to one space. Express the resultant in a string. Capitalise all letters of the string.
+
+EXAMPLE 1: If the 3GPP document version number is "3GPP TS 32.111-3 V4.1.0 (2001-09)", then the IRP document version number shall be "32.111-3 V4.1".
+
+EXAMPLE 2: If the 3GPP document version number is "3GPP TS 32.303 V4.1.0 (2001-09)", then the IRP document version number shall be "32.303 V4.1".
+
+For Release 10 and later releases, it is derived using the following rule:
+
+Take the 3GPP TS/version number on the front page of the SS specification, such as "3GPP TS 32.111-6 V10.1.0 (2011-06)", Discard the leading "3GPP TS". Discard all characters after and including the last period. Remove all spaces. Construct a string that is a concatenation of ‘-’, the identifier of the Annex where the solution set technology is captured (e.g., ‘A’ for Annex A) and a trailing space. Insert the concatenated string before ‘V’, Express the resultant in a string. Capitalise all letters of the string.
+
+EXAMPLE 3: If the 3GPP document version number is "3GPP TS 32.111-6 V10.1.0 (2011-06)", then the IRP document version number shall be:
+
+- "32.111-6-A V10.1" for CORBA Solution Set;
+- "32.111-6-B V10.1" for XML Definitions;
+- "32.111-6-C V10.1" for SOAP Solution Set.
+
+EXAMPLE 4: If the 3GPP document version number is "3GPP TS 32.306 V10.1.0 (2011-09)", then the IRP document version number shall be:
+
+- "32.306-A V10.1" for CORBA Solution Set;
+- "32.306-B V10.1" for XML Definitions;
+- "32.306-C V10.1" for SOAP Solution Set.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                             |
+|-----|-----------------------------|
+| CM  | Configuration Management    |
+| EM  | Element Manager             |
+| IRP | Integration Reference Point |
+| IS  | Information Service         |
+| NE  | Network Element             |
+| NM  | Network Manager             |
+| SS  | Solution Set                |
+
+# 4 Generic IRP functions over Itf-N
+
+The requirements for the generic IRP service over Itf-N are provided in the following clauses.
+
+## 4.1 Version retrieval function
+
+An IRPAgent may support one or multiple IRP instances simultaneously (e.g. AlarmIRP instances, BulkCMIRP instances, etc.).
+
+The set of capabilities of each IRP instance is fully identified by the version number of the corresponding IRP specification (i.e. the “IRP document version number string” or in short, the IRPVersion; see clause 3.1.).
+
+An IRP instance shall provide a function to allow IRPManager to retrieve all its (i.e. IRP instance’s) supported IRPVersion(s) over Itf-N.
+
+An IRPManager may then decide if it wants to communicate with the IRP instance.
+
+## 4.2 Profiles retrieval functions
+
+Each IRP supported by an IRPAgent provides a set of operations and notifications. It is possible to define in each IRP Information Service (IS) some operations and notification that are optional, which means that the final implementation of those operations and notifications is vendor dependant. Similarly, some parameters of operations and notifications may be defined as optional in the IRP IS.
+
+It shall be possible for an IRPManager to retrieve over Itf-N the profile of an IRP of a given version: the profile shall provide information such as name of supported operations and notifications, and the list of supported parameters for each supported operation and notification.
+
+# Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                                    |        |        |
+|----------------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                    | Old    | New    |
+| Jun 2001       | SA 12 | SP-010285 | --   | --  | Approved at TSG SA #12 and placed under Change Control                                                             | 2.0.0  | 4.0.0  |
+| Jul 2001       | --    | --        | --   | --  | TS number wrongly shown as 32.312 instead of 32.311                                                                | 4.0.0  | 4.0.1  |
+| Mar 2002       | SA 15 | --        | --   | --  | Automatic upgrade to Rel-5 (no Rel-5 CR)                                                                           | 4.0.1  | 5.0.0  |
+| Dec 2002       | --    | --        | --   | --  | Cosmetics                                                                                                          | 5.0.0  | 5.0.1  |
+| Dec 2003       | SA 22 | SP-030639 | 0002 | --  | Align with 32.102                                                                                                  | 5.0.1  | 5.1.0  |
+| Mar 2004       | SA 23 | SP-040105 | --   | --  | Automatic upgrade to Rel-6 (no CR)                                                                                 | 5.1.0  | 6.0.0  |
+| Dec 2004       | SA 26 | SP-040794 | 0003 | --  | Update UML diagrams, Add reference to its CORBA/CMIP SSs                                                           | 6.0.0  | 6.1.0  |
+| Jun 2007       | SA_36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | 6.1.0  | 7.0.0  |
+| Dec 2008       | SA 42 | --        | --   | --  | Upgrade to Release 8                                                                                               | 7.0.0  | 8.0.0  |
+| Dec 2009       | -     | -         | -    | -   | Update to Rel-9 version (MCC)                                                                                      | 8.0.0  | 9.0.0  |
+| Mar 2011       | -     | -         | -    | -   | Update to Rel-10 version (MCC)                                                                                     | 9.0.0  | 10.0.0 |
+| Dec 2012       | SA 54 | SP-110706 | 0004 | 4   | Enhance definition of IRPVersion                                                                                   | 10.0.0 | 10.1.0 |

marked/Rel-10/32_series/32312/raw.md

@@ -0,0 +1,477 @@
+
+
+
+
+Keywords  
+UMTS, management
+
+# 3GPP TS 32.312 V10.1.0 (2013-03)
+
+*Technical Specification*
+
+## 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; c Integration Reference Point (IRP) management: Information
+
+3GPP support office address  
+050 Route des Lucioles - Sophia Antipolis  
+06410 VALBONNE - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet  
+<http://www.3gpp.org>
+
+![LTE logo with '4ADVANCED' text above the 'e'.](f5f48eb1753d75fb380cf01027a6395d_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e'.
+
+![3GPP logo with a signal icon below the 'P'.](1211e36d120f0d2912a745437f4c8f19_img.jpg)
+
+3GPP logo with a signal icon below the 'P'.
+
+## Copyright Notification
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2013, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.  
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners.  
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.  
+GSM™ and the GSM logo are registered and owned by the GSM Association.  
+Specifications and reports for implementation of the 3GPP system should be obtained via the 3GPP Organisational Partners' Publications Offices
+
+# Contents
+
+|                                                         |    |
+|---------------------------------------------------------|----|
+| Foreword .....                                          | 5  |
+| Introduction .....                                      | 5  |
+| 1 Scope.....                                            | 6  |
+| 2 References.....                                       | 6  |
+| 3 Definitions and abbreviations .....                   | 6  |
+| 3.1 Definitions.....                                    | 6  |
+| 3.2 Abbreviations .....                                 | 7  |
+| 4 System Overview .....                                 | 8  |
+| 4.1 System Context .....                                | 8  |
+| 5 Information Object Classes (IOCs).....                | 9  |
+| 5.1 Imported information entities and local labels..... | 9  |
+| 5.2 Class Diagram .....                                 | 9  |
+| 5.2.1 Attributes and relationships.....                 | 9  |
+| 5.2.2 Inheritance .....                                 | 9  |
+| 5.3 Information object class definitions .....          | 9  |
+| 5.3.1 ManagedGenericIRP .....                           | 9  |
+| 5.3.1.1 Definition .....                                | 9  |
+| 5.3.1.2 Attributes .....                                | 10 |
+| 5.3.1.3 Notification .....                              | 10 |
+| 5.4 Information relationship definitions.....           | 10 |
+| 5.5 Information attribute definitions .....             | 10 |
+| 5.5.1 Definitions and legal values .....                | 10 |
+| 6 Interface Definition .....                            | 11 |
+| 6.1 Class diagram representing interfaces.....          | 11 |
+| 6.2 Generic rules .....                                 | 12 |
+| 6.3 genericIRPVersionOperations Interface (M).....      | 12 |
+| 6.3.1 Operation getIRPVersion (M).....                  | 12 |
+| 6.3.1.1 Definition .....                                | 12 |
+| 6.3.1.2 Input parameters .....                          | 12 |
+| 6.3.1.3 Output parameters.....                          | 12 |
+| 6.3.1.4 Pre-condition.....                              | 12 |
+| 6.3.1.5 Post-condition .....                            | 12 |
+| 6.3.1.6 Exceptions.....                                 | 12 |
+| 6.4 genericIRPProfileOperations Interface (O) .....     | 13 |
+| 6.4.1 Operation getOperationProfile (O).....            | 13 |
+| 6.4.1.1 Definition .....                                | 13 |
+| 6.4.1.2 Input parameters .....                          | 13 |
+| 6.4.1.3 Output parameters.....                          | 13 |
+| 6.4.1.4 Pre-condition.....                              | 13 |
+| 6.4.1.5 Post-condition .....                            | 13 |
+| 6.4.1.6 Exceptions.....                                 | 13 |
+| 6.4.2 Operation getNotificationProfile (O).....         | 14 |
+| 6.4.2.1 Definition .....                                | 14 |
+| 6.4.2.2 Input parameters .....                          | 14 |
+| 6.4.2.3 Output parameters.....                          | 14 |
+| 6.4.2.4 Pre-condition.....                              | 14 |
+| 6.4.2.5 Post-condition .....                            | 14 |
+| 6.4.2.6 Exceptions.....                                 | 14 |
+| Annex A (informative): Change history.....              | 15 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.311: Generic Integration Reference Point (IRP) management; Requirements
+- 32.312: Generic Integration Reference Point (IRP) management; Information Service (IS)**
+- 32.316: Generic Integration Reference Point (IRP) management; Solution Set (SS) Definitions
+
+The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 [1] and TS 32.102 [2].
+
+All IRPs support a set of generic features. Those features allow to retrieve IRP profile and IRP supported versions. The present document contains the specification of those generic features.
+
+# --- 1 Scope
+
+The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controllable by management system's client (i.e. IRPManager) via the Itf-N. It also specifies the semantics of and the interactions used to carry this information.
+
+With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP name-contained by an IRPAgent. An IRPManager can also retrieve the IRPVersions supported by a given IRP.
+
+# --- 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.301: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements".
+- [4] Void.
+- [5] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
+- [6] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [7] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [8] 3GPP TS 32.622: "Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TS 32.101 [1], TS 32.102 [2], TS 32.301 [3] and the following apply:
+
+**IRP:** see TS 32.102 [2].
+
+**IRPAgent:** see TS 32.102 [2].
+
+**IRPManager:** see TS 32.102 [2].
+
+**IRP document version number string (or "IRPVersion"):** see TS 32.311 [5].
+
+**Itf-N:** see TS 32.102 [2].
+
+**SupportIOC:** see TS 32.150 [6].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                                                |
+|-------|--------------------------------------------------------------------------------|
+| CM    | Configuration Management                                                       |
+| DN    | Distinguished Name                                                             |
+| EM    | Element Manager                                                                |
+| IOC   | Information Object Class                                                       |
+| IRP   | Integration Reference Point                                                    |
+| IS    | Information Service                                                            |
+| ITU-T | International Telecommunication Union Telecommunication standardisation sector |
+| NE    | Network Element                                                                |
+| NM    | Network Manager                                                                |
+| NR    | Network Resource                                                               |
+| NRM   | Network Resource Model                                                         |
+| OMG   | Object Management Group                                                        |
+| RDN   | Relative Distinguished Name                                                    |
+| SS    | Solution Set                                                                   |
+| UML   | Unified Modelling Language (OMG)                                               |
+
+# 4 System Overview
+
+## 4.1 System Context
+
+The general definition of the System Context for the present IRP is found in TS 32.150 [6] clause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below.
+
+![Figure 4.1: System Context A. A diagram showing an IRPManager (NM) connected to an IRPAgent (EM) via an interface labeled Itf-N. The IRPAgent is connected to multiple NEs. A curved arrow labeled 'Any IRP' points to the Itf-N interface.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg)
+
+The diagram illustrates the system context for IRP. On the left, a box labeled 'NM' contains a sub-box 'IRPManager'. A solid line connects 'IRPManager' to another box on the right labeled 'EM', which contains a sub-box 'IRPAgent'. A vertical dashed line, labeled 'Itf-N' at its base, separates the 'NM' and 'EM' boxes. To the right of the 'EM' box, a dotted line connects 'IRPAgent' to a box labeled 'NEs'. A curved arrow labeled 'Any IRP' points from the right towards the 'Itf-N' interface.
+
+Figure 4.1: System Context A. A diagram showing an IRPManager (NM) connected to an IRPAgent (EM) via an interface labeled Itf-N. The IRPAgent is connected to multiple NEs. A curved arrow labeled 'Any IRP' points to the Itf-N interface.
+
+Figure 4.1: System Context A
+
+![Figure 4.2: System Context B. A diagram showing an IRPManager (NM) connected to an IRPAgent (NE) via an interface labeled Itf-N. A curved arrow labeled 'Any IRP' points to the Itf-N interface.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg)
+
+The diagram illustrates the system context for IRP. On the left, a box labeled 'NM' contains a sub-box 'IRPManager'. A solid line connects 'IRPManager' to another box on the right labeled 'NE', which contains a sub-box 'IRPAgent'. A vertical dashed line, labeled 'Itf-N' at its base, separates the 'NM' and 'NE' boxes. A curved arrow labeled 'Any IRP' points from the right towards the 'Itf-N' interface. Unlike Figure 4.1, there is no connection to 'NEs'.
+
+Figure 4.2: System Context B. A diagram showing an IRPManager (NM) connected to an IRPAgent (NE) via an interface labeled Itf-N. A curved arrow labeled 'Any IRP' points to the Itf-N interface.
+
+Figure 4.2: System Context B
+
+# 5 Information Object Classes (IOCs)
+
+## 5.1 Imported information entities and local labels
+
+| Label reference                                           | Local label           |
+|-----------------------------------------------------------|-----------------------|
+| 3GPP TS 32.111-2 [7], notification, notifyNewAlarm        | notifyNewAlarm        |
+| 3GPP TS 32.111-2 [7], notification, notifyChangedAlarm    | notifyChangedAlarm    |
+| 3GPP TS 32.111-2 [7], notification, notifyClearedAlarm    | notifyClearedAlarm    |
+| 3GPP TS 32.111-2 [7], notification, notifyAckStateChanged | notifyAckStateChanged |
+| 3GPP TS 32.622 [8], information object class, Top         | Top                   |
+
+## 5.2 Class Diagram
+
+### 5.2.1 Attributes and relationships
+
+This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this IRP. This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.
+
+![UML Class Diagram showing a class box for ManagedGenericIRP with the stereotype <<SupportIOC>>.](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+```
+
+classDiagram
+    class ManagedGenericIRP {
+        <<SupportIOC>>
+    }
+  
+```
+
+UML Class Diagram showing a class box for ManagedGenericIRP with the stereotype <>.
+
+### 5.2.2 Inheritance
+
+This clause depicts the inheritance relationships that exist between SupportIOCs.
+
+![UML Class Diagram showing inheritance from ManagedGenericIRP to Top class.](3b621c21b0af3a504a28d2547e87138f_img.jpg)
+
+```
+
+classDiagram
+    class Top {
+        <<InformationObjectClass>>
+        (from TS 32.622)
+    }
+    class ManagedGenericIRP {
+        <<SupportIOC>>
+    }
+    ManagedGenericIRP --|> Top
+  
+```
+
+UML Class Diagram showing inheritance from ManagedGenericIRP to Top class.
+
+## 5.3 Information object class definitions
+
+### 5.3.1 ManagedGenericIRP
+
+#### 5.3.1.1 Definition
+
+This SupportIOC represents a generic IRP which supports generic management capabilities associated with each IRP Agent. This SupportIOC cannot be instantiated. It is defined for sub-classing purposes.
+
+#### 5.3.1.2 Attributes
+
+| Attribute name               | Support Qualifier | Read Qualifier | Write Qualifier |
+|------------------------------|-------------------|----------------|-----------------|
+| iRPId                        | M                 | M              | -               |
+| iRPVersions                  | M                 | M              | -               |
+| operationNameProfile         | O                 | M              | -               |
+| operationParameterProfile    | O                 | M              | -               |
+| notificationNameProfile      | O                 | M              | -               |
+| notificationParameterProfile | O                 | M              | -               |
+
+#### 5.3.1.3 Notification
+
+| Name                  | Qualifier | Notes                                |
+|-----------------------|-----------|--------------------------------------|
+| notifyNewAlarm        | O         | See Alarm IRP (3GPP TS 32.111-2 [7]) |
+| notifyChangedAlarm    | O         | See Alarm IRP (3GPP TS 32.111-2 [7]) |
+| notifyClearedAlarm    | O         | See Alarm IRP (3GPP TS 32.111-2 [7]) |
+| notifyComments        | O         | See Alarm IRP (3GPP TS 32.111-2 [7]) |
+| notifyAckStateChanged | O         | See Alarm IRP (3GPP TS 32.111-2 [7]) |
+
+## 5.4 Information relationship definitions
+
+None
+
+## 5.5 Information attribute definitions
+
+This clause defines the semantics of the attributes used in SupportIOCs.
+
+### 5.5.1 Definitions and legal values
+
+| Attribute Name               | Definition                                                                                                                                                                                                                                                                                                                                                              | Legal Values                                                       |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| iRPId                        | An attribute whose 'name+value' can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.                                                                                                                                                       |                                                                    |
+| iRPVersions                  | This attribute contains a set of IRPVersions. The set contains at least one element.                                                                                                                                                                                                                                                                                    | See definition "IRP document version number string" in clause 3.1. |
+| operationNameProfile         | This attribute contains a set of elements. The n-th element of this set contains the set of operation names supported for the IRPVersion identified in the n-th element of iRPVersions attribute.                                                                                                                                                                       |                                                                    |
+| notificationNameProfile      | This attribute contains a set of elements. The n-th element of this set contains the set of notification names supported for the IRPVersion identified in the n-th element of iRPVersions attribute.                                                                                                                                                                    |                                                                    |
+| operationParameterProfile    | This attribute contains a set of elements. The n-th element of this set contains the set of set of notification parameters supported by the operations identified in the n-th element of operationNameProfile attribute. The set of operation parameters are placed in the set in the same order as the order followed by the operation names in their set.             |                                                                    |
+| notificationParameterProfile | This attribute contains a set of elements. The n-th element of this set contains the set of set of notification parameters supported by the notifications identified in the n-th element of notificationNameProfile attribute. The set of notification parameters are placed in the set in the same order as the order followed by the notification names in their set. |                                                                    |
+
+# 6 Interface Definition
+
+## 6.1 Class diagram representing interfaces
+
+![UML Class diagram showing ManagedGenericIRP implementing GenericIRPVersionOperations and possibly realizing GenericIRPProfileOperations.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+```
+classDiagram
+    class ManagedGenericIRP {
+        <<SupportIOC>>
+        ManagedGenericIRP
+    }
+    class GenericIRPVersionOperations {
+        <<Interface>>
+        getIRPVersion()
+    }
+    class GenericIRPProfileOperations {
+        <<Interface>>
+        <<opt>> getOperationProfile()
+        <<opt>> getNotificationProfile()
+    }
+    ManagedGenericIRP --|> GenericIRPVersionOperations
+    ManagedGenericIRP --> GenericIRPProfileOperations : <<may realize>>
+```
+
+The diagram illustrates a class hierarchy. At the top is a class box labeled **<<SupportIOC>> ManagedGenericIRP**. Below it are two interface boxes. The left interface is labeled **<<Interface>> GenericIRPVersionOperations** and contains the method **getIRPVersion()**. The right interface is labeled **<<Interface>> GenericIRPProfileOperations** and contains two optional methods: **<<opt>> getOperationProfile()** and **<<opt>> getNotificationProfile()**. A solid line with an open triangle arrowhead points from **ManagedGenericIRP** to **GenericIRPVersionOperations**, indicating inheritance or implementation. A dashed line with an open arrowhead points from **ManagedGenericIRP** to **GenericIRPProfileOperations**, labeled with **<<may realize>>**, indicating a possible realization of the interface.
+
+UML Class diagram showing ManagedGenericIRP implementing GenericIRPVersionOperations and possibly realizing GenericIRPProfileOperations.
+
+## 6.2 Generic rules
+
+- **Rule 1:** each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+- **Rule 2:** Each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+- **Rule 3:** each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 genericIRPVersionOperations Interface (M)
+
+### 6.3.1 Operation getIRPVersion (M)
+
+#### 6.3.1.1 Definition
+
+IRPManager wishes to find out the IRP SS versions supported by an IRP. The IRP shall respond with a set of supported IRP SS version(s). The list of returned `IRPVersions` is such that the IRPManager can use any of these versions without having to specify an `IRPVersion` to the IRPAgent.
+
+#### 6.3.1.2 Input parameters
+
+None
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name                | Qualifier | Matching Information                         | Comment                                                                                                                                                         |
+|-------------------------------|-----------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>versionNumberSet</code> | M         | <code>ManagedGenericIRP.iRPPVersions</code>  | It indicates one or more SS version numbers ( <code>IRPVersion</code> , as defined by "IRP document version number string" in clause 3.1) supported by the IRP. |
+| <code>status</code>           | M         | ENUM (Operation succeeded, Operation failed) | If <code>operation_failed_internal_problem status = OperationFailed</code> .                                                                                    |
+
+#### 6.3.1.4 Pre-condition
+
+None specific
+
+#### 6.3.1.5 Post-condition
+
+None specific
+
+#### 6.3.1.6 Exceptions
+
+None specific
+
+## 6.4 genericIRPProfileOperations Interface (O)
+
+### 6.4.1 Operation getOperationProfile (O)
+
+#### 6.4.1.1 Definition
+
+IRPManager invokes this operation to query the detailed profile of an IRP (supported operations and supported parameters) for a specific supported version. The notification profile will provide details about notifications that are specifically defined by this IRP.
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type                                        | Comment                       |
+|----------------|-----------|---------------------------------------------------------|-------------------------------|
+| iRPVersion     | M         | Element of <code>ManagedGenericIRP.iRPVersions</code> . | It contains a version number. |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name            | Qualifier | Matching Information                                                                                                         | Comment                                                                                            |
+|---------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| operationNameProfile      | M         | Elements of <code>ManagedGenericIRP.operationNameProfile</code> corresponding to the <code>iRPVersion</code> parameter.      | If this parameter contains no information, it implies that the IRP does not support any operation. |
+| operationParameterProfile | M         | Elements of <code>ManagedGenericIRP.operationParameterProfile</code> corresponding to the <code>iRPVersion</code> parameter. |                                                                                                    |
+| status                    | M         | ENUM (Operation succeeded, Operation failed)                                                                                 | If <code>operation_failed_invalid_version</code> status = <code>OperationFailed</code> .           |
+
+#### 6.4.1.4 Pre-condition
+
+`validIRPVersion`.
+
+| Assertion Name               | Definition                                                                                                                                                                   |
+|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>validIRPVersion</code> | The <code>iRPVersion</code> input parameter identifies a supported version contained in attribute <code>iRPVersions</code> of the <code>ManagedGenericIRP</code> SupportLOC. |
+
+#### 6.4.1.5 Post-condition
+
+None specific
+
+#### 6.4.1.6 Exceptions
+
+| Name                                          | Definition                                                                                                                                            |
+|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>Operation_failed_invalid_version</code> | <b>Condition:</b> <code>validIRPVersion</code> is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+### 6.4.2 Operation `getNotificationProfile` (O)
+
+#### 6.4.2.1 Definition
+
+`IRPManager` invokes this operation to query the detailed notification profile of an IRP (supported notifications and supported parameters) for a specific supported version. The notification profile will provide details about notifications that are specifically defined by this IRP. For example, if this IRP is notification IRP R4, then `getNotificationProfile` will not return any information since no notification is defined in notification IRP R4.
+
+#### 6.4.2.2 Input parameters
+
+| Parameter Name          | Qualifier | Information Type                                     | Comment                       |
+|-------------------------|-----------|------------------------------------------------------|-------------------------------|
+| <code>iRPVersion</code> | M         | Element of <code>ManagedGenericIRP.iRPVersion</code> | It contains a version number. |
+
+#### 6.4.2.3 Output parameters
+
+| Parameter Name                            | Qualifier | Matching Information                                                                                                           | Comment                                                                                               |
+|-------------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
+| <code>notificationNameProfile</code>      | M         | Element of <code>ManagedGenericIRP.notificationNameProfile</code> corresponding to the <code>iRPVersion</code> parameter.      | If this parameter contains no information, it implies that the IRP does not support any notification. |
+| <code>notificationParameterProfile</code> | M         | Element of <code>ManagedGenericIRP.notificationParameterProfile</code> corresponding to the <code>iRPVersion</code> parameter. |                                                                                                       |
+| <code>status</code>                       | M         | ENUM (Operation succeeded, Operation failed)                                                                                   | If <code>operation_failed_invalid_version</code><br><code>status = OperationFailed</code> .           |
+
+#### 6.4.2.4 Pre-condition
+
+`validIRPVersion`.
+
+| Assertion Name               | Definition                                                                                                                                                                    |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>validIRPVersion</code> | The <code>iRPVersion</code> input parameter identifies a supported version contained in attribute <code>iRPVersions</code> of the <code>ManagedGenericIRP SupportIOC</code> . |
+
+#### 6.4.2.5 Post-condition
+
+None specific
+
+#### 6.4.2.6 Exceptions
+
+| Name                                          | Definition                                                                                                                                                         |
+|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>Operation_failed_invalid_version</code> | <b>Condition:</b> <code>validIRPVersion</code> is false<br><b>Returned Information:</b> The output parameter <code>status</code><br><b>Exit state:</b> Entry State |
+
+# Annex A (informative): Change history
+
+| Change history |       |           |          |     |                                                                                                                    |     |        |        |
+|----------------|-------|-----------|----------|-----|--------------------------------------------------------------------------------------------------------------------|-----|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR       | Rev | Subject/Comment                                                                                                    | Cat | Old    | New    |
+| Jun 2001       | SA_12 | SP-010285 | --       | --  | Approved at TSG SA #12 and placed under Change Control                                                             | --  | 2.0.0  | 4.0.0  |
+| Mar 2002       | SA_15 | --        | --       | --  | Automatic upgrade to Rel-5 (no Rel-5 CR)                                                                           | --  | 4.0.0  | 5.0.0  |
+| Dec 2002       | --    | --        | --       | --  | Cosmetics                                                                                                          | --  | 5.0.0  | 5.0.1  |
+| Dec 2003       | SA_22 | SP-030640 | 000<br>2 | --  | Align with 32.102 and 32.311                                                                                       | A   | 5.0.1  | 5.1.0  |
+| Mar 2004       | SA_23 | SP-040105 | --       | --  | Automatic upgrade to Rel-6 (no CR)                                                                                 | --  | 5.1.0  | 6.0.0  |
+| Dec 2004       | SA_26 | SP-040794 | 000<br>3 | --  | Update UML diagrams, Add reference to its CORBA/CMIP SSs                                                           | F   | 6.0.0  | 6.1.0  |
+| Jun 2005       | SA_28 | SP-050329 | 000<br>4 | --  | Apply Generic System Context – Align with TS 32.150                                                                | F   | 6.1.0  | 6.2.0  |
+| Dec 2006       | SA_34 | SP-060708 | 000<br>5 | --  | Add missing Notification Table for ManagedGenericIRP                                                               | F   | 6.2.0  | 6.3.0  |
+| Jun 2007       | SA_36 | --        | --       | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | --  | 6.3.0  | 7.0.0  |
+| Dec 2008       | SA_42 | --        | --       | --  | Upgrade to Release 8                                                                                               | --  | 7.0.0  | 8.0.0  |
+| Dec 2009       | SA_46 | SP-090719 | 000<br>6 | --  | Align usage of SupportIOC according to repertoire and template                                                     | C   | 8.0.0  | 9.0.0  |
+| Mar 2011       | -     | -         | -        | -   | Update to Rel-10 version (MCC)                                                                                     | -   | 9.0.0  | 10.0.0 |
+| Mar 2013       | SA_59 | SP-130049 | 001<br>1 | --  | add missing iRPId etc.                                                                                             | A   | 10.0.0 | 10.1.0 |

marked/Rel-10/32_series/32316/raw.md

@@ -0,0 +1,987 @@
+
+
+# Keywords UMTS, management, **3GPP TS 32.316 V10.0.0 (2010-06)**
+
+*Technical Specification*
+
+**3GPP**
+
+## Postal address **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **Telecommunication management;** 3GPP support office address **Generic Integration Reference Point (IRP) management;** **Solution Set**
+
+![LTE logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+LTE logo
+
+Internet Protocol Suite: IPv6  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 92 94 42 01
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo](4f4b52340aaccb1bcf733468dca9ee03_img.jpg)
+
+3GPP logo
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- 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 Solution Set definitions.....                                   | 6         |
+| <b>Annex A (normative): CORBA Solution Set.....</b>               | <b>7</b>  |
+| A.1 Architectural Features.....                                   | 7         |
+| A.1.1 Syntax for Distinguished Names.....                         | 7         |
+| A.1.2 Abstract IOC .....                                          | 7         |
+| A.2 Mapping .....                                                 | 7         |
+| A.2.1 Operation mapping.....                                      | 7         |
+| A.2.2 Operation parameter mapping.....                            | 7         |
+| A.3 Solution Set definitions.....                                 | 9         |
+| A.3.1 IDL definition structure.....                               | 9         |
+| A.3.2 IDL specification “GenericIRPManagementConstDefs.idl” ..... | 9         |
+| A.3.3 IDL specification “GenericIRPManagementSystem.idl” .....    | 11        |
+| <b>Annex B (normative): SOAP Solution Set.....</b>                | <b>13</b> |
+| B.1 Architectural Features.....                                   | 13        |
+| B.1.1 Syntax for Distinguished Names.....                         | 13        |
+| B.2 Mapping .....                                                 | 14        |
+| B.2.1 Operation mapping.....                                      | 14        |
+| B.2.2 Operation parameter mapping.....                            | 14        |
+| B.2.2.1 Operation getIRPVersion .....                             | 14        |
+| B.2.2.1.1 Input parameters .....                                  | 14        |
+| B.2.2.1.2 Output parameters.....                                  | 14        |
+| B.2.2.1.3 Fault definition.....                                   | 14        |
+| B.2.2.2 Operation getOperationProfile .....                       | 15        |
+| B.2.2.2.1 Input parameters .....                                  | 15        |
+| B.2.2.2.2 Output parameters.....                                  | 15        |
+| B.2.2.2.3 Fault definition.....                                   | 15        |
+| B.2.2.3 Operation getNotificationProfile .....                    | 15        |
+| B.2.2.3.1 Input parameters .....                                  | 15        |
+| B.2.2.3.2 Output parameters.....                                  | 16        |
+| B.2.2.3.3 Fault definition.....                                   | 16        |
+| B.3 Solution Set definitions.....                                 | 16        |
+| B.3.1 WSDL definition structure .....                             | 16        |
+| B.3.2 Graphical Representation.....                               | 16        |
+| B.3.3 WSDL specification “GenericIRPSystem.wsdl” .....            | 16        |
+| Annex C (informative): Change history.....                        | 20        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.311: Generic Integration Reference Point (IRP) management; Requirements
+- 32.312: Generic Integration Reference Point (IRP) management; Information Service (IS)
+- 32.316: Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions**
+
+# --- 1 Scope
+
+The present document provides the Solution Set definitions for Generic Integration Reference Point (IRP) management, whose capabilities are specified in 3GPP TS 32.312 [1], the Generic IRP management: Information Service.
+
+This Solution Set Definition specification is related to 3GPP TS 32.312 V10.0.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 TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management: Information Service (IS)".
+- [2] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
+- [3] 3GPP TS 32.111-2: "Telecommunication management; Alarm Integration Reference Point (IRP); Information Service (IS)".
+- [4] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [5] W3C WSDL 1.1 specification (<http://www.w3.org/TR/2001/NOTE-wSDL-20010315>)
+- [6] Thompson, H.S., Beech, D., Maloney, M., Mendleshon, N., eds. (May 2002). "XML Schema Part 1: Structures," Recommendation, World Wide Web Consortium <http://www.w3.org/TR/xmlschema-1/>
+- [7] Biron, P.V., Malhotra, A., eds. (May 2002). "XML Schema Part 2: Datatypes," Recommendation, World Wide Web Consortium <http://www.w3.org/TR/xmlschema-2/>
+- [8] W3C SOAP 1.1 specification (<http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>)
+- [9] RFC 2616 (June 1999): "Hypertext Transfer Protocol – HTTP/1.1"
+- [10] W3C WSDL 1.1 specification (<http://www.w3.org/TR/2001/NOTE-wSDL-20010315>)
+- [11] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>)
+- [12] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TS 32.312 [1] apply.
+
+**IRP document version number string (or "IRPVersion")**: See 3GPP TS 32.311 [2] subclause 3.1.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                            |
+|-------|--------------------------------------------|
+| CORBA | Common Object Request Broker Architecture  |
+| HTTP  | HyperText Transfer Protocol                |
+| IDL   | Interface Definition Language              |
+| IRP   | Integration Reference Point                |
+| IOC   | Information Object Class                   |
+| OMG   | Object Management Group                    |
+| SS    | Solution Set                               |
+| WSDL  | Web Services Description Language          |
+| WS-I  | Web Services Interoperability Organization |
+| XML   | eXtensible Markup Language                 |
+
+# --- 4 Solution Set definitions
+
+This specification defines the following 3GPP Generic IRP management Solution Set definitions:
+
+- 3GPP Generic IRP management CORBA SS (Annex A)
+- 3GPP Generic IRP management SOAP Solution Set (Annex B)
+
+Solution Set to XML definitions is not present in the current version of this specification.
+
+# --- Annex A (normative): CORBA Solution Set
+
+This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Generic IRP: Information Service (TS 32.312 [1]).
+
+---
+
+## A.1 Architectural Features
+
+The overall architectural feature of this IRP is specified in 3G TS 32.312 [1]. This clause specifies features that are specific to the CORBA SS.
+
+### A.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [12].
+
+### A.1.2 Abstract IOC
+
+The capabilities of the Generic IRP management: IS [1] are captured by the definition of an IOC called ManagedGenericIRP. This IOC is an abstract class and is mapped to a MOC of the same name. The MOC is intended for inheritance by other MOCs specified in Interface IRPs such as AlarmIRP [3], NotificationIRP [4], etc.
+
+---
+
+## A.2 Mapping
+
+### A.2.1 Operation mapping
+
+Generic IRP management: IS [1] defines semantics of operation visible across the Itf-N. Table A.1 indicates mapping of these operations to their equivalents defined in this SS.
+
+**Table A.1: Mapping from IS Notification/Operation to SS equivalents**
+
+| IS Operation TS 32.312 [1] | SS Method                              | Qualifier |
+|----------------------------|----------------------------------------|-----------|
+| getIRPVersion              | get_irp_versions                       | M         |
+| getOperationProfile        | get_interface_irp_operation_profile    | O         |
+| getNotificationProfile     | get_interface_irp_notification_profile | O         |
+
+### A.2.2 Operation parameter mapping
+
+Generic IRP management: IS [1] defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicates the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table A.2 Mapping from IS getIRPVersion parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter                                                  | Qualifier |
+|------------------------|----------------------------------------------------------------------|-----------|
+| versionNumberSet       | Return value of type GenericIRPManagementConstDefs::VersionNumberSet | M         |
+| status                 | Exceptions:<br>GenericIRPManagementSystem::GetIRPVersions            | M         |
+
+**Table A.3 Mapping from IS getOperationProfile parameters to SS equivalents**
+
+| IS Operation parameter                             | SS Method parameter                                                                                                                                                                                                                  | Qualifier |
+|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iRPVersion                                         | GenericIRPManagementConstDefs::VersionNumber<br>this_irp_version                                                                                                                                                                     | M         |
+| operationNameProfile,<br>operationParameterProfile | Return value of type<br>GenericIRPManagementConstDefs::MethodList                                                                                                                                                                    | M         |
+| status                                             | Exceptions:<br>GenericIRPManagementSystem::GetInterfaceIRPOperationsProfile,<br>GenericIRPManagementSystem::OperationNotSupported,<br>GenericIRPManagementSystem::InvalidParameter,<br>GenericIRPManagementSystem::ValueNotSupported | M         |
+
+**Table A.4 Mapping from IS getNotificationProfile parameters to SS equivalents**
+
+| IS Operation parameter                                   | SS Method parameter                                                                                                                                                                                                                    | Qualifier |
+|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iRPVersion                                               | GenericIRPManagementConstDefs::VersionNumber<br>this_irp_version                                                                                                                                                                       | M         |
+| notificationNameProfile,<br>notificationParameterProfile | Return value of type<br>GenericIRPManagementConstDefs::NotificationList                                                                                                                                                                | M         |
+| status                                                   | Exceptions:<br>GenericIRPManagementSystem::GetInterfaceIRPNotificationProfile,<br>GenericIRPManagementSystem::OperationNotSupported,<br>GenericIRPManagementSystem::InvalidParameter,<br>GenericIRPManagementSystem::ValueNotSupported | M         |
+
+## --- A.3 Solution Set definitions
+
+### A.3.1 IDL definition structure
+
+Clause A.3.2 defines the constants and types used by the Generic IRP.
+
+Clause A.3.3 defines the operations and notifications which are performed by the Generic IRP agent.
+
+### A.3.2 IDL specification “GenericIRPManagementConstDefs.idl”
+
+```
+//File: GenericIRPManagementConstDefs.idl
+#ifndef _GENERIC_IRP_MANAGEMENT_CONST_DEFS_IDL_
+#define _GENERIC_IRP_MANAGEMENT_CONST_DEFS_IDL_
+#include <TimeBase.idl>
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+/* ## Module: GenericIRPManagementConstDefs
+This module contains definitions commonly used among all IRPs.
+=====
+*/
+module GenericIRPManagementConstDefs
+{
+    /*
+     * Definition imported from CosTime.
+     * The time refers to time in Greenwich Time Zone.
+     * It also consists of a time displacement factor in the form of minutes of
+     * displacement from the Greenwich Meridian.
+     */
+    typedef TimeBase::UtcT IRPTime;
+    typedef string DN;
+    typedef sequence <DN> DNList;
+
+    enum Signal {OK, FULL_FAILURE, PARTIAL_FAILURE};
+    enum Result {SUCCESS, FAILURE};
+    /*
+     * This holds a list of notification Ids
+     */
+    typedef sequence <long> NotifIdSet;
+
+    /*
+     * This holds identifiers of notifications that are correlated.
+     */
+    struct CorrelatedNotification
+    {
+        DN source;// Contains DN of MO that emitted the set of notifications
+                  // DN string format in compliance with Name Convention for
+                  // Managed Object.
+                  // This may be a zero-length string. In this case, the MO
+                  // is identified by the value of the MOI attribute
+                  // of the Structured Event, i.e., the notification.
+        NotifIdSet notif_id_set; // Set of related notification ids
+    };
+    /*
+     * The VersionNumber is a string that identifies the IRP specification name
+     * and its version number. See definition "IRP document version number
+     * string" or "IRPVersion".
+     * The VersionNumberSet is a sequence of such VersionNumber. It is returned
+     * by get_XXX_IRP_versions(). The sequence order has no significance.
+     */
+    typedef string VersionNumber;
+    typedef sequence <VersionNumber> VersionNumberSet;
+    typedef string MethodName;
+    typedef string ParameterName;
+    typedef sequence <ParameterName> ParameterList;
+    /*
+     * The Method defines the structure to be returned as part of
+     * get_supported_operations_profile(). The name shall be the actual method
+     * name (ex. "attach_push", "change_subscription_filter", etc.)
+     * The parameter_list contains a list of strings. Each string shall be
+     * the actual parameter name (ex. "manager_reference", "filter", etc.)
+     */
+    struct Method
+    {
+        MethodName name;
+    };
+}
+```
+
+```
+
+        ParameterList parameter_list;
+    };
+    /*
+     * List of all methods and their associated parameters.
+     */
+    typedef sequence <Method> MethodList;
+    typedef string NotificationName;
+    struct Notification
+    {
+        NotificationName name;
+        ParameterList parameter_list;
+    };
+    typedef sequence <Notification> NotificationList;
+    /*
+     * Defines the name of an attribute of a Managed Object
+     */
+    typedef string MOAttributeName;
+    /*
+     * Defines the value of an attribute of a Managed Object in form of a CORBA
+     * Any. Apart from basic datatypes already defined in CORBA, the allowed
+     * attribute value types are defined in the AttributeTypes module.
+     */
+    typedef any MOAttributeValue;
+    /*
+     * Represents an attribute: "name" is the attribute name
+     * and "value" is the attribute value.
+     */
+    struct MOAttribute
+    {
+        MOAttributeName name;
+        MOAttributeValue value;
+    };
+    typedef sequence <MOAttribute> MOAttributeSet;
+
+    typedef string ManagerIdentifier;
+    /*
+     * The following are types carrying an optional parameter.
+     * If the boolean is TRUE, then the value is present.
+     * Otherwise the value is absent.
+     */
+    union StringOpt switch (boolean)
+    {
+        case TRUE: string value;
+    };
+    union ShortOpt switch (boolean)
+    {
+        case TRUE: short value;
+    };
+    union UnsignedShortOpt switch (boolean)
+    {
+        case TRUE: unsigned short value;
+    };
+    union LongOpt switch (boolean)
+    {
+        case TRUE: long value;
+    };
+    union UnsignedLongOpt switch (boolean)
+    {
+        case TRUE: unsigned long value;
+    };
+    union IRPTimeOpt switch (boolean)
+    {
+        case TRUE: GenericIRPManagementConstDefs::IRPTime value;
+    };
+};
+
+#endif // _GENERIC_IRP_MANAGEMENT_CONST_DEFS_IDL_
+
+```
+
+### A.3.3 IDL specification “GenericIRPManagementSystem.idl”
+
+```
+//File: GenericIRPManagementSystem.idl
+#ifndef _GENERIC_IRP_MANAGEMENT_SYSTEM_IDL_
+#define _GENERIC_IRP_MANAGEMENT_SYSTEM_IDL_
+
+#include <GenericIRPManagementConstDefs.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+module GenericIRPManagementSystem
+{
+    exception GetInterfaceIRPNotificationProfile { string reason; };
+    exception GetInterfaceIRPOperationProfile { string reason; };
+    exception GetIRPVersions { string reason; };
+
+    /*
+    Exception thrown when an unsupported optional parameter
+    is passed with information.
+    The parameter shall be the actual unsupported parameter name.
+    */
+    exception ParameterNotSupported {
+        GenericIRPManagementConstDefs::ParameterName parameter; };
+
+    /*
+    Exception thrown when an invalid parameter value is passed.
+    The parameter shall be the actual parameter name.
+    */
+    exception InvalidParameter {
+        GenericIRPManagementConstDefs::ParameterName parameter; };
+
+    /*
+    Exception thrown when a valid but unsupported parameter value is passed.
+    The parameter shall be the actual parameter name.
+    */
+    exception ValueNotSupported {
+        GenericIRPManagementConstDefs::ParameterName parameter; };
+
+    /*
+    Exception thrown when an unsupported optional method is called.
+    */
+    exception OperationNotSupported {};
+
+    interface GenericIRPManagement
+    {
+        /*
+        Return the list of all supported Interface IRP versions
+        Each IRPVersion is defined by the rule in the definition
+        "IRP document version number string" or "IRPVersion"
+        (see subclause 3.1).
+        */
+        GenericIRPManagementConstDefs::VersionNumberSet get_irp_versions
+        (
+        )
+        raises (GetIRPVersions);
+
+        /*
+        Return the list of all supported methods and their supported
+        parameters for this Interface IRPVersion.
+        */
+        GenericIRPManagementConstDefs::MethodList
+            get_interface_irp_operation_profile
+            (
+                in GenericIRPManagementConstDefs::VersionNumber this_irp_version
+            )
+            raises (GetInterfaceIRPOperationProfile,
+                    OperationNotSupported,
+                    InvalidParameter,
+                    ValueNotSupported);
+
+        /*
+        Return the list of all supported notifications and their supported
+        parameters for this Interface IRPVersion.
+        */
+        typedef GenericIRPManagementConstDefs::NotificationList NotificationList;
+```
+
+```
+NotificationList get_interface_irp_notification_profile
+(
+    in GenericIRPManagementConstDefs::VersionNumber this_irp_version
+)
+raises (GetInterfaceIRPNotificationProfile,
+        OperationNotSupported,
+        InvalidParameter,
+        ValueNotSupported);
+};
+
+};
+
+#endif // _GENERIC_IRP_MANAGEMENT_SYSTEM_IDL_
+```
+
+# --- Annex B (normative): SOAP Solution Set
+
+This annex specifies the SOAP Solution Set for the IRP whose semantics are specified in Generic IRP: Information Service (3GPP TS 32.312[1]).
+
+## --- B.1 Architectural Features
+
+The overall architectural feature of this IRP is specified in 3G TS 32.312 [1]. This clause specifies features that are specific to the SOAP SS.
+
+The SOAP 1.1 specification [8] and WSDL 1.1 specification [5] are supported.
+
+The SOAP 1.2 specification [11] is optionally supported.
+
+This specification uses "document" style in the WSDL description.
+
+This specification uses "literal" encoding style in the WSDL description.
+
+This specification uses a number of namespace prefixes throughout that are listed in Table B.1.
+
+**Table B.1: Prefixes and Namespaces used in this specification**
+
+| Prefix                 | Namespace                                                                                                                                                 |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| http                   | <a href="http://schemas.xmlsoap.org/wsdl/http/">http://schemas.xmlsoap.org/wsdl/http/</a>                                                                 |
+| soap                   | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a>                                                                 |
+| SOAP-ENV               | <a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>                                                         |
+| SOAP-ENC or<br>soapenc | <a href="http://schemas.xmlsoap.org/soap/encoding/">http://schemas.xmlsoap.org/soap/encoding/</a>                                                         |
+| xs or xsd              | <a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>                                                                           |
+| xsi                    | <a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>                                                         |
+| genericIRPData         | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData">http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData</a> |
+
+### B.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [12].
+
+## B.2 Mapping
+
+### B.2.1 Operation mapping
+
+Generic IRP management: IS [1] defines semantics of operation visible across the Itf-N. Table B.2.1 indicates mapping of these operations to their equivalents defined in this SS.
+
+**Table B.2.1: Mapping from IS Notification/Operation to SS equivalents**
+
+| IS Operation TS 32.312 [1] | SS Operation           | Qualifier |
+|----------------------------|------------------------|-----------|
+| getIRPVersion              | getIRPVersion          | M         |
+| getOperationProfile        | getOperationProfile    | O         |
+| getNotificationProfile     | getNotificationProfile | O         |
+
+### B.2.2 Operation parameter mapping
+
+#### B.2.2.1 Operation getIRPVersion
+
+##### B.2.2.1.1 Input parameters
+
+None.
+
+Here is the XML schema fragment of the getIRPVersion request:
+
+```
+<!-- getIRPVersion Request -->
+<element name="getIRPVersion">
+</element>
+```
+
+##### B.2.2.1.2 Output parameters
+
+None.
+
+**Table B.2.2.1.2: Mapping from IS getIRPVersion output parameters to SS equivalents**
+
+| IS Operation parameter | SS Operation parameter                               | Qualifier |
+|------------------------|------------------------------------------------------|-----------|
+| versionNumberSet       | genericIRPData:VersionNumberSetType versionNumberSet | M         |
+| status                 | genericIRPData:getIRPVersionFault                    | M         |
+
+Here is the XML schema fragment of the getIRPVersion response:
+
+```
+<!-- getIRPVersion Response -->
+<element name="getIRPVersionResponse">
+  <complexType>
+    <sequence>
+      <element name="versionNumberSet" type="genericIRPData:VersionNumberSetType"/>
+    </sequence>
+  </complexType>
+</element>
+```
+
+##### B.2.2.1.3 Fault definition
+
+```
+<!-- getIRPVersion Fault -->
+<element name="getIRPVersionFault">
+  <complexType>
+    <choice>
+      <element name="getIRPVersionFault" type="string" default="getIRPVersionFault"/>
+    </choice>
+  </complexType>
+</element>
+```
+
+#### B.2.2.2 Operation getOperationProfile
+
+##### B.2.2.2.1 Input parameters
+
+**Table B.2.2.2.1: Mapping from IS getOperationProfile input parameters to SS equivalents**
+
+| IS Operation parameter | SS Operation parameter                      | Qualifier |
+|------------------------|---------------------------------------------|-----------|
+| iRPVersion             | genericIRPData:VersionNumberType iRPVersion | M         |
+
+Here is the XML schema fragment of the getOperationProfile request:
+
+```
+<!-- getOperationProfile Request -->
+<element name="getOperationProfile">
+  <complexType>
+    <sequence>
+      <element name="iRPVersion" type="genericIRPData:VersionNumberType"/>
+    </sequence>
+  </complexType>
+</element>
+```
+
+##### B.2.2.2.2 Output parameters
+
+**Table B.2.2.2.2: Mapping from IS getOperationProfile output parameters to SS equivalents**
+
+| IS Operation parameter                         | SS Operation parameter                       | Qualifier |
+|------------------------------------------------|----------------------------------------------|-----------|
+| operationNameProfile,operationParameterProfile | genericIRPData:OperationSetType operationSet | M         |
+| status                                         | genericIRPData:getOperationProfileFault      | M         |
+
+Here is the XML schema fragment of the getOperationProfile response:
+
+```
+<!-- getOperationProfile Response -->
+<element name="getOperationProfileResponse">
+  <complexType>
+    <sequence>
+      <element name="operationSet" type="genericIRPData:OperationSetType"/>
+    </sequence>
+  </complexType>
+</element>
+```
+
+##### B.2.2.2.3 Fault definition
+
+```
+<!-- getOperationProfile Fault -->
+
+<element name="getOperationProfileFault">
+  <complexType>
+    <choice>
+      <element name="getOperationProfileFault" type="string"/>
+      <element ref="genericIRPData:OperationNotSupportedFault"/>
+      <element ref="genericIRPData:InvalidParameterFault"/>
+    </choice>
+  </complexType>
+</element>
+```
+
+#### B.2.2.3 Operation getNotificationProfile
+
+##### B.2.2.3.1 Input parameters
+
+**Table B.2.2.3.1: Mapping from IS getNotificationProfile input parameters to SS equivalents**
+
+| IS Operation parameter | SS Operation parameter                      | Qualifier |
+|------------------------|---------------------------------------------|-----------|
+| iRPVersion             | genericIRPData:VersionNumberType iRPVersion | M         |
+
+Here is the XML schema fragment of the getNotificationProfile request:
+
+```
+<!-- getNotificationProfile Request -->
+```
+
+```
+
+<element name="getNotificationProfile">
+  <complexType>
+    <sequence>
+      <element name="iRPVersion" type="genericIRPData:VersionNumberType"/>
+    </sequence>
+  </complexType>
+</element>
+
+```
+
+##### B.2.2.3.2 Output parameters
+
+**Table B.2.2.3.2: Mapping from IS getNotificationProfile output parameters to SS equivalents**
+
+| IS Operation parameter                               | SS Operation parameter                             | Qualifier |
+|------------------------------------------------------|----------------------------------------------------|-----------|
+| notificationNameProfile,notificationParameterProfile | genericIRPData:NotificationSetType notificationSet | M         |
+| Status                                               | genericIRPData:getNotificationProfileFault         | M         |
+
+Here is the XML schema fragment of the getNotificationProfile response:
+
+```
+
+<!-- getNotificationProfile Response -->
+<element name="getNotificationProfileResponse">
+  <complexType>
+    <sequence>
+      <element name="notificationSet" type="genericIRPData:NotificationSetType"/>
+    </sequence>
+  </complexType>
+</element>
+
+```
+
+##### B.2.2.3.3 Fault definition
+
+```
+
+<!-- getNotificationProfile Fault -->
+<element name="getNotificationProfileFault">
+  <complexType>
+    <choice>
+      <element name="getNotificationProfileFault" type="string"
+        default="getNotificationProfileFault"/>
+      <element ref="genericIRPData:OperationNotSupportedFault"/>
+      <element ref="genericIRPData:InvalidParameterFault"/>
+    </choice>
+  </complexType>
+</element>
+
+```
+
+## B.3 Solution Set definitions
+
+### B.3.1 WSDL definition structure
+
+Clause B.3.2 provides a graphical representation of the Generic IRP service.
+
+Clause B.3.3 defines the services which are supported the Generic IRP agent.
+
+### B.3.2 Graphical Representation
+
+Not present in the current version of this specification.
+
+### B.3.3 WSDL specification “GenericIRPSystem.wsdl”
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
+  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
+  xmlns:genericIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem"
+  xmlns:xs="http://www.w3.org/2001/XMLSchema"
+  xmlns:genericIRPData="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData"
+  targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem">
+
+```
+
+```
+
+<types>
+  <schema
+targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData"
+xmlns="http://www.w3.org/2001/XMLSchema">
+    <element name="OperationNotSupportedFault" type="string"/>
+    <element name="InvalidParameterFault" type="string"/>
+    <simpleType name="VersionNumberType">
+      <restriction base="string"/>
+    </simpleType>
+    <complexType name="VersionNumberSetType">
+      <sequence>
+        <element name="versionNumber" type="genericIRPData:VersionNumberType"
+maxOccurs="unbounded"/>
+      </sequence>
+    </complexType>
+    <complexType name="ParameterSetType">
+      <sequence>
+        <element name="parameterName" type="string" maxOccurs="unbounded"/>
+      </sequence>
+    </complexType>
+    <complexType name="OperationType">
+      <sequence>
+        <element name="operationName" type="string"/>
+        <element name="parameterSet" type="genericIRPData:ParameterSetType"/>
+      </sequence>
+    </complexType>
+    <complexType name="OperationSetType">
+      <sequence>
+        <element name="operation" type="genericIRPData:OperationType"
+maxOccurs="unbounded"/>
+      </sequence>
+    </complexType>
+    <complexType name="NotificationType">
+      <sequence>
+        <element name="notificationName" type="string"/>
+        <element name="parameterSet" type="genericIRPData:ParameterSetType"/>
+      </sequence>
+    </complexType>
+    <complexType name="NotificationSetType">
+      <sequence>
+        <element name="notification" type="genericIRPData:NotificationType"
+maxOccurs="unbounded"/>
+      </sequence>
+    </complexType>
+    <!-- getIRPVersion Request -->
+    <element name="getIRPVersion"/>
+    <!-- getIRPVersion Response -->
+    <element name="getIRPVersionResponse">
+      <complexType>
+        <sequence>
+          <element name="versionNumberSet" type="genericIRPData:VersionNumberSetType"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- getIRPVersion Fault -->
+    <element name="getIRPVersionFault">
+      <complexType>
+        <choice>
+          <element name="getIRPVersionFault" type="string"/>
+        </choice>
+      </complexType>
+    </element>
+    <!-- getOperationProfile Request -->
+    <element name="getOperationProfile">
+      <complexType>
+        <sequence>
+          <element name="iRPVersion" type="genericIRPData:VersionNumberType"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- getOperationProfile Response -->
+    <element name="getOperationProfileResponse">
+      <complexType>
+        <sequence>
+          <element name="operationSet" type="genericIRPData:OperationSetType"/>
+        </sequence>
+      </complexType>
+    </element>
+  </schema>
+</types>
+
+```
+
+```
+
+    <!-- getOperationProfile Fault -->
+    <element name="getOperationProfileFault">
+      <complexType>
+        <choice>
+          <element name="getOperationProfileFault" type="string"/>
+          <element ref="genericIRPData:OperationNotSupportedFault"/>
+          <element ref="genericIRPData:InvalidParameterFault"/>
+        </choice>
+      </complexType>
+    </element>
+    <!-- getNotificationProfile Request -->
+    <element name="getNotificationProfile">
+      <complexType>
+        <sequence>
+          <element name="iRPVersion" type="genericIRPData:VersionNumberType"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- getNotificationProfile Response -->
+    <element name="getNotificationProfileResponse">
+      <complexType>
+        <sequence>
+          <element name="notificationSet" type="genericIRPData:NotificationSetType"/>
+        </sequence>
+      </complexType>
+    </element>
+    <!-- getNotificationProfile Fault -->
+    <element name="getNotificationProfileFault">
+      <complexType>
+        <choice>
+          <element name="getNotificationProfileFault" type="string"/>
+          <element ref="genericIRPData:OperationNotSupportedFault"/>
+          <element ref="genericIRPData:InvalidParameterFault"/>
+        </choice>
+      </complexType>
+    </element>
+  </schema>
+</types>
+<message name="getIRPVersionRequest">
+  <part name="parameter" element="genericIRPData:getIRPVersion"/>
+</message>
+<message name="getIRPVersionResponse">
+  <part name="parameter" element="genericIRPData:getIRPVersionResponse"/>
+</message>
+<message name="getIRPVersionFault">
+  <part name="parameter" element="genericIRPData:getIRPVersionFault"/>
+</message>
+<message name="getOperationProfileRequest">
+  <part name="parameter" element="genericIRPData:getOperationProfile"/>
+</message>
+<message name="getOperationProfileResponse">
+  <part name="parameter" element="genericIRPData:getOperationProfileResponse"/>
+</message>
+<message name="getOperationProfileFault">
+  <part name="parameter" element="genericIRPData:getOperationProfileFault"/>
+</message>
+<message name="getNotificationProfileRequest">
+  <part name="parameter" element="genericIRPData:getNotificationProfile"/>
+</message>
+<message name="getNotificationProfileResponse">
+  <part name="parameter" element="genericIRPData:getNotificationProfileResponse"/>
+</message>
+<message name="getNotificationProfileFault">
+  <part name="parameter" element="genericIRPData:getNotificationProfileFault"/>
+</message>
+<portType name="GenericIRPPortType">
+  <operation name="getIRPVersion">
+    <input message="genericIRPSystem:getIRPVersionRequest"/>
+    <output message="genericIRPSystem:getIRPVersionResponse"/>
+    <fault name="getIRPVersionFault" message="genericIRPSystem:getIRPVersionFault"/>
+  </operation>
+  <operation name="getOperationProfile">
+    <input message="genericIRPSystem:getOperationProfileRequest"/>
+    <output message="genericIRPSystem:getOperationProfileResponse"/>
+    <fault name="getOperationProfileFault"
+message="genericIRPSystem:getOperationProfileFault"/>
+  </operation>
+  <operation name="getNotificationProfile">
+
+```
+
+```
+
+        <input message="genericIRPSystem:getNotificationProfileRequest"/>
+        <output message="genericIRPSystem:getNotificationProfileResponse"/>
+        <fault name="getNotificationProfileFault"
+message="genericIRPSystem:getNotificationProfileFault"/>
+      </operation>
+    </portType>
+    <binding name="GenericIRPBinding" type="genericIRPSystem:GenericIRPPortType">
+      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+      <operation name="getIRPVersion">
+        <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#getIRPVersion" style="document"/>
+        <input>
+          <soap:body use="literal"/>
+        </input>
+        <output>
+          <soap:body use="literal"/>
+        </output>
+        <fault name="getIRPVersionFault">
+          <soap:fault name="getIRPVersionFault" use="literal"/>
+        </fault>
+      </operation>
+      <operation name="getOperationProfile">
+        <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#getOperationProfile"
+style="document"/>
+        <input>
+          <soap:body use="literal"/>
+        </input>
+        <output>
+          <soap:body use="literal"/>
+        </output>
+        <fault name="getOperationProfileFault">
+          <soap:fault name="getOperationProfileFault" use="literal"/>
+        </fault>
+      </operation>
+      <operation name="getNotificationProfile">
+        <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#getNotificationProfile"
+style="document"/>
+        <input>
+          <soap:body use="literal"/>
+        </input>
+        <output>
+          <soap:body use="literal"/>
+        </output>
+        <fault name="getNotificationProfileFault">
+          <soap:fault name="getNotificationProfileFault" use="literal"/>
+        </fault>
+      </operation>
+    </binding>
+  </definitions>
+
+```
+
+# --- Annex C (informative): Change history
+
+| Change history |       |           |    |     |                                                 |    |           |            |     |
+|----------------|-------|-----------|----|-----|-------------------------------------------------|----|-----------|------------|-----|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                                 |    | Ca<br>t   | Old        | New |
+| 2010-05        | SA-48 | SP-100272 | -- | --  | Presentation to SA for information and approval | -- | --        | 1.0.0      |     |
+| 06-2010        | SA-48 | --        | -- | --  | Publication                                     | -- | 1.0.<br>0 | 10.0.<br>0 |     |
+
+Error! No
+
+20
+
+Error! No text of specified style in
+
+Error! No
+
+20
+
+Error! No text of specified style in

marked/Rel-10/32_series/32321/raw.md

@@ -0,0 +1,342 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Test management Integration Reference Point (IRP); Requirements (Release 10)**
+
+![LTE Advanced logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The logo for LTE Advanced, featuring the word "lte" in bold lowercase letters with a red signal icon above the "e". The word "ADVANCED" is written in smaller capital letters above the "e". A trademark symbol (TM) is at the bottom right of the "e".
+
+LTE Advanced logo
+
+![3GPP logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+The logo for 3GPP, featuring the letters "3GPP" in a stylized, bold font. The "3" is black, "G" is black, "P" is black, and "P" is black. A red signal icon is positioned below the "G". A trademark symbol (TM) is at the top right of the "P".
+
+3GPP logo
+
+Keywords  
+UMTS, GSM, management
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTETM is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# 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 Purpose.....                             | 6  |
+| 5 Requirements .....                       | 7  |
+| 5.1 Overview .....                         | 7  |
+| 5.2 Test.....                              | 7  |
+| 5.2.1 Test Initiation.....                 | 7  |
+| 5.2.2 Test Termination .....               | 8  |
+| 5.2.2.1 Explicit Test Termination .....    | 8  |
+| 5.2.2.2 Implicit Test Termination .....    | 8  |
+| 5.2.3 Test Monitoring .....                | 8  |
+| 5.2.4 Test Result Reporting.....           | 9  |
+| 5.3 Test States .....                      | 9  |
+| 5.4 Test Categories.....                   | 10 |
+| 5.4.1 Resource Self Test.....              | 10 |
+| 5.4.2 Connection Test.....                 | 10 |
+| 5.4.3 Loopback Test .....                  | 10 |
+| Annex A (informative): Change history..... | 11 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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.321:** "Test management Integration Reference Point (IRP): Requirements";
+- 32.322:** "Test management Integration Reference Point (IRP): Information Service (IS)";
+- 32.326:** "Test management Integration Reference Point (IRP): Solution Set (SS) definitions".
+
+A 3G telecommunication network is composed of a multitude of different network elements (NE). For a successful operation of the network the operator must be provided with mechanisms allowing him to manage the network. These management activities can be grouped into several areas: configuration management, fault management, performance management, accounting management and security management.
+
+A management function assisting in different high level management areas such as fault management and performance management is test management. The purpose of testing is to get information about the functionality and performance of the 3G managed network subject to the test.
+
+The present document is part of a set of technical specifications defining the telecommunication management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 [5]. The TM architecture is described in 3GPP TS 32.102 [6]. The other specifications define the interface (ITf-N) between the managing system (manager), which is in general the network manager (NM) and the managed system (agent), which is either an element manager (EM) or the managed NE itself. The Itf-N is composed of a number of integration reference points (IRPs) defining the information in the agent that is visible for the manager, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. One of these IRPs is the Test Management IRP.
+
+Each IRP is specified by a set of TSs: Requirements, Information Service, CORBA SS, etc.
+
+# --- 1 Scope
+
+The present document describes, in addition to the requirements defined in [1] and [2], the requirements for the Test Management IRP.
+
+# --- 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] ITU-T Recommendation X.745: "Information technology - Open Systems Interconnection - Systems Management: Test management function".
+- [4] 3GPP TS 32.301: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements".
+- [5] Void
+- [6] ITU-T Recommendation X.737: "Information technology - Open Systems Interconnection; Systems Management: Confidence and diagnostic test categories".
+- [7] IETF RFC2679: "A One-way Delay Metric for IPPM".
+- [8] IETF RFC3393: "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)".
+- [9] IETF RFC2680: "A One-way Packet Loss Metric for IPPM".
+- [10] IETF RFC2681: "A Round-trip Delay Metric for IPPM".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**test category:** one or more tests sharing a common purpose and similar characteristics
+
+**Tester Object (TO):** managed object that is instantiated for the purpose of monitoring and controlling a test invocation  
+Each test invocation has one associated TO. TOs are created and deleted by managed objects with TARR functionality.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                              |
+|------|------------------------------|
+| NE   | Network Element              |
+| NM   | Network Management Center    |
+| TARR | Test Action Request Receiver |
+| TO   | Tester Object                |
+
+# --- 4 Purpose
+
+The purpose of testing is to get information about the functionality and performance of the 3G managed network subject to the test. This information can be used in other network management areas, for instance in fault management.
+
+Testing is an activity that involves the operator, the managing system (the OS) and the managed system (the NE). Generally the operator requests the execution of tests from the OS and the managed NE autonomously executes the tests without any further support from the operator.
+
+In case of intrusive tests it is required that the network resources to be tested are locked prior to test execution. During the test execution the telecommunication service provided by the network resources is interrupted. After completion of the test, depending on the test result, the network resources shall be set to the most appropriate state.
+
+Test management capabilities should be provided over the Itf-N in order to allow the NM operator to perform tests on network resources. This capability is especially important at times when only the NM but not the OMC is attended, which might be the case at night or during weekends.
+
+In the context of fault management the NM operator may use the testing capabilities over the Itf-N for numerous purposes:
+
+- When a fault has been detected and if the information provided in the alarm report is not sufficient to localise the faulty resource, tests can be executed in order to localise the fault.
+- When a fault has been detected and if the information provided in the alarm report specifies the faulty resource, tests can be executed on that resource in order to determine the required repair action.
+- During normal operation of the NE, tests can be executed for the purpose of discovering undetected faults.
+- After a faulty resource has been repaired or replaced and before it is restored to service, tests can be executed on that resource in order to make sure that it is fault free.
+
+However, regardless of the context where the testing is used, its target is always the same: verify if a system's physical or functional resource performs properly and, in case it happens to be faulty, provide all the information to help the operator to localise and correct the fault.
+
+The requirements for the test management service shall be based on ITU-T Recommendation X.745 [3].
+
+# --- 5 Requirements
+
+## 5.1 Overview
+
+The IRPManager (test conductor) must be able to initiate and terminate tests. For this purpose special test initiation and termination requests may be used. The IRPAgent (test performer) must be able to receive and react upon these requests. Special objects may be created for the purpose of monitoring and control of the test execution. During test execution the IRPManager shall be able to monitor the test.
+
+Test results shall be made available to the IRPManager by test result reports (notifications). It shall be possible to log these test result reports.
+
+This gives rise to the following requirements for the test management function to be satisfied:
+
+- the ability for the manager to initiate tests;
+- the ability for the manager to terminate tests;
+- the ability for the manager to monitor the test execution;
+- the specification of a mechanism to report the test results to the manager;
+- the specification of a mechanism to log test results in the agent.
+
+These capabilities are outlined in the following sections in more detail.
+
+## 5.2 Test
+
+### 5.2.1 Test Initiation
+
+The IRPManager shall be able to initiate a test in the IRPAgent by sending a test request to the IRPAgent. The IRPAgent must have at least one object instance capable of receiving these test requests. In response to a test request one or more tests shall be initiated. Each test shall be controlled and monitored individually by special objects instantiated exclusively for this purpose. These objects are called Tester Objects (TOs). Each of the tests initiated in response to a test request shall have a single associated TO.
+
+The test request shall include the following information:
+
+- The network resources to be tested.
+- Information about the managed objects (e.g. TOs) assisting in the test execution.
+- Any other information useful for the test execution.
+
+In response to the test request the IRPAgent shall send a test request response to the IRPManager. For a successful test request this response shall contain the following information:
+
+- A unique identifier for each test initiated by the test request.
+- Information about the managed objects assisting to execute the test.
+
+For a failed test request the response shall contain the following information:
+
+- Information about the reason for the failure.
+
+### 5.2.2 Test Termination
+
+A test may terminate in two different ways, either by request (explicit test termination) or spontaneously (implicit test termination).
+
+#### 5.2.2.1 Explicit Test Termination
+
+During the lifetime of a test explicit test termination may be requested by the IRPManager by:
+
+- Emission of a test termination request.
+
+The test termination request must be directed to the object in the IRPAgent which received the test request. The test termination request shall provide the following information:
+
+- The identifiers of the tests to be terminated.
+
+All TO(s) related to the tests to be terminated shall be deleted.
+
+After reception of a test termination request a test termination response shall be generated by the IRPAgent and forwarded to the IRPManager. In case the test termination request is successful the test termination response shall contain the following information:
+
+- The identifiers of all tests that have been successfully terminated.
+
+If one or more of the tests specified in the test termination request cannot be terminated a test termination request failure response shall be generated. This response shall contain the following information:
+
+- The identifiers of the tests that could not be deleted.
+- Information about the reason for the failure.
+
+#### 5.2.2.2 Implicit Test Termination
+
+Implicit test termination may be triggered by three events:
+
+- Fulfilment of conditions for a successful completion of the test.
+- Fulfilment of conditions for a premature termination of the test, e.g. expiry of a time-out period.
+- Occurrence of abnormal conditions, e.g. fault situations.
+
+### 5.2.3 Test Monitoring
+
+The IRPManager shall be able to monitor the tests, i. e. get information about the tests while they are still executing. For this purpose the IRPManager shall be able to inquire the values of attributes containing specific information about the test execution.
+
+### 5.2.4 Test Result Reporting
+
+Test results shall be made available to the IRPManager by one or more notifications emitted by the TO that is related to the test. These notifications shall be generated in an automatic manner upon occurrence of predefined triggering events without that any action of the IRPManager is required (unsolicited reporting). The triggering events depend on the test category and shall be defined by the TO class behaviour.
+
+Depending on the nature of the test and the amount of test result data to be transferred to the IRPManager it may be beneficial to capture some test result data in a file and to transfer this file to the IRPManager. It is up to the TO to decide whether the file based transfer of test result data shall be used in addition to the emission of test result notifications.
+
+Test result notifications may be emitted during the test execution (intermediate test result reporting) and at the end of the test execution (final test result reporting).
+
+The event triggering the emission of final test result reports is the termination of the test execution, irrespective of if the test terminates by request or spontaneously except for the case where the test is terminated by deleting its related TO. This applies to all test categories.
+
+The events triggering intermediate test result reporting depend on the test category. They may include:
+
+- Arrival of the test execution at specified points, for example at the end of test phases.
+- Expiry of specified reporting time intervals.
+- Fulfilment of certain predefined criteria.
+
+A test result notification shall include the following information:
+
+- The identifier of the test for which the results are reported.
+- Information about the outcome of the test, e.g. if the test terminated successfully upon test completion or prematurely.
+- Information about the test and the test execution, e.g. tested network resources, proposed repair actions in case of fault detection.
+- Any other useful information pertaining to the test.
+
+For test result reporting the Notification IRP as defined in 3GPP TS 32.301 [4] to 3GPP TS 32.304 [5] shall be used. According to the operations provided by the Notification IRP the IRPManager is able to specify filter conditions selecting the notifications that are forwarded over the Itf-N to the IRPManager. Notifications not satisfying the filter conditions are discarded.
+
+## 5.3 Test States
+
+For the purpose of monitoring tests TOs shall provide information about the current state of a test. Therefore each TO shall support a special test state attribute. The test state may assume one of the following values: not initialised, idle, initialising, testing, terminating, disabled. The actual test state value shall be derived from the actual operational state and procedural status according to the mapping table specified in ITU-T Recommendation X.745 [3].
+
+Any state change shall be reported to the NM using the Notification IRP.
+
+## 5.4 Test Categories
+
+Most tests can be classified into test categories. In ITU-T Recommendation X.737 [6] eight different test categories are defined.
+
+In case a certain test does not fit in any of the test categories defined in ITU-T Recommendation X.737 [6] vendors shall define new vendor-specific-extended (VSE) test categories.
+
+### 5.4.1 Resource Self Test
+
+Resource self tests are used to investigate the ability of a simple resource in the managed network (e.g. a hardware board) to perform its allotted function. For the specification of the resource to be tested a single MORT is required. No associated objects are necessary.
+
+The resource self test may be intrusive or non-intrusive. In case of intrusive tests the MORT has to be placed in the appropriate state before the test may start. If this is not possible the test request is rejected.
+
+### 5.4.2 Connection Test
+
+The connection test allows investigation of the ability of a communications path in the IP network to support a desired service or level of functionality. Both the MORT(s) and AOs are required in the connection test. The MORT(s) represent the communications path to be tested. Two AOs are defined that reference the resources at the ends of the communications path.
+
+The following parameters should be returned:
+
+- the time delay in the communications path [7];
+- the time delay variation in the communications path [8];
+- The packet loss ratio in the communications path [9].
+
+In the ITU-T Recommendation X.737 [6], the definition of the above parameters is not given.
+
+In the IP network, the definition of these parameters is given in the IETF RFC [7], [8], [9].
+
+### 5.4.3 Loopback Test
+
+The Loopback test is used to verify that data may be sent and received over a communications path within a specified loopback time-out period with an acceptable error ratio. Both the MORT(s) and AOs are required in the loopback test. The MORTs represent the resources that are being tested by the loopback test. The AOs references the resources providing the loopback points.
+
+The following parameters should be returned.
+
+- the time delay in the communications path [10].
+- the time delay variation in the communications path.
+- the packet loss ratio detected in the tested communications path.
+
+In ITU-T Recommendation X.737 [6] the definition of the above parameters is not given.
+
+In the IP network the definition of time delay in the loopback test is given in the IETF RFC [10].
+
+The definitions of time delay variation and loss ratio in the loopback test are similar to the definitions in the connection test in the IETF RFC [8], [9].
+
+# Annex A (informative): Change history
+
+| Change history |           |           |          |     |                                                                                                                                                                    |         |           |            |  |
+|----------------|-----------|-----------|----------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|------------|--|
+| Date           | TSG #     | TSG Doc.  | CR       | Rev | Subject/Comment                                                                                                                                                    | Ca<br>t | Old       | New        |  |
+| Jun 2002       | SA_1<br>6 | SP-020328 | --       | --  | Submitted to TSG SA #16 for Information                                                                                                                            | --      | 1.0.<br>0 |            |  |
+| Sep 2002       | SA_1<br>7 | SP-020456 | --       | --  | Submitted to TSG SA #17 for Approval                                                                                                                               | --      | 2.0.<br>0 | 5.0.0      |  |
+| Dec 2002       | --        | --        | --       | --  | Cosmetics                                                                                                                                                          | --      | 5.0.<br>0 | 5.0.1      |  |
+| Mar 2004       | SA_2<br>3 | SP-040105 | --       | --  | Automatic upgrade to Rel-6 (no CR)                                                                                                                                 | --      | 5.0.<br>1 | 6.0.0      |  |
+| Sep 2006       | SA_3<br>3 | SP-060549 | 000<br>1 | --  | Add new test categories of network performance measurement                                                                                                         | B       | 6.0.<br>0 | 7.0.0      |  |
+| Mar 2007       | --        | --        | --       | --  | Delete reference to the 32.324 CMIP SS. Reason: SA#35 endorsed the SA5 decision to not propagate the CMIP Solution Sets to Rel-7 (TS 32.3x4, TS 32.4x4, TS 32.6x4) | --      | 7.0.<br>0 | 7.0.1      |  |
+| Dec 2007       | SA_3<br>8 | SP-070743 | 000<br>2 | --  | R8 CR 32.321-701 Add new output parameters (time delay, time delay variation and packet loss ratio in connection and loopback test categories)                     | B       | 7.0.<br>1 | 8.0.0      |  |
+| Dec 2009       | -         | -         | -        | -   | Update to Rel-9 version (MCC)                                                                                                                                      | -       | 8.0.<br>0 | 9.0.0      |  |
+| Mar 2011       | -         | -         | -        | -   | Update to Rel-10 version (MCC)                                                                                                                                     | -       | 9.0.<br>0 | 10.0.<br>0 |  |

marked/Rel-10/32_series/32326/raw.md

@@ -0,0 +1,1463 @@
+
+
+# Keywords CORBA, XML, SOAP, management, architecture 3GPP TS 32.326 V10.1.0 (2010-12)
+
+*Technical Specification*
+
+**3GPP**  
+**3rd Generation Partnership Project;**  
+**Technical Specification Group Services and System Aspects;**  
+**Telecommunication management;**  
+**Test management Integration Reference Point (IRP):**  
+**Solution Set**
+
+Postal address:  
+3GPP support office address  
+0556 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+![LTE logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo](390120de4fe440c42fea8154fcaad334_img.jpg)
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP..
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# ***Copyright Notification***
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTETM is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                    |           |
+|--------------------------------------------------------------------|-----------|
+| Foreword .....                                                     | 5         |
+| Introduction .....                                                 | 5         |
+| 1 Scope.....                                                       | 6         |
+| 2 References.....                                                  | 6         |
+| 3 Definitions, symbols and abbreviations.....                      | 7         |
+| 3.1 Definitions.....                                               | 7         |
+| 3.2 Abbreviations .....                                            | 7         |
+| 4 Solution Set Definitions .....                                   | 8         |
+| <b>Annex A (normative): CORBA Solution Set.....</b>                | <b>9</b>  |
+| 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 TestManagementIRPNotification Interface .....                | 9         |
+| A.1.5.1 Method push (M).....                                       | 10        |
+| A.2 Mapping .....                                                  | 11        |
+| A.2.1 Operation and Notification mapping.....                      | 11        |
+| A.2.2 Operation parameter mapping.....                             | 11        |
+| A.2.3 Notification parameter mapping.....                          | 13        |
+| A.3 Solution Set definitions.....                                  | 14        |
+| A.3.1 IDL definition structure.....                                | 14        |
+| A.3.2 IDL specification "TestManagementIRPConstDefs.idl" .....     | 15        |
+| A.3.3 IDL specification "TestManagementIRPSystem.idl" .....        | 17        |
+| A.3.4 IDL specification "TestManagementIRPNotifications.idl" ..... | 19        |
+| <b>Annex B (normative): XML Definitions.....</b>                   | <b>21</b> |
+| B.1 Architectural Features .....                                   | 21        |
+| B.1.1 Syntax for Distinguished Names.....                          | 21        |
+| B.1.2 Notification Services.....                                   | 21        |
+| B.1.3 IOC Definitions.....                                         | 21        |
+| B.2 Mapping .....                                                  | 21        |
+| B.3 Solution Set definitions.....                                  | 21        |
+| B.3.1 XML definition structure .....                               | 21        |
+| B.3.2 Graphical Representation.....                                | 22        |
+| B.3.3 XML Schema "tMIRPNotif.xsd".....                             | 23        |
+| <b>Annex C (normative): SOAP Solution Set.....</b>                 | <b>24</b> |
+| C.1 Architectural features.....                                    | 24        |
+| C.1.1 Syntax for Distinguished Names.....                          | 24        |
+| C.1.2 Notification Services.....                                   | 24        |
+| C.1.3 Supported W3C specifications.....                            | 24        |
+| C.1.4 Prefixes and namespaces.....                                 | 24        |
+| C.2 Mapping .....                                                  | 25        |
+| C.2.1 Operation and notification mapping.....                      | 25        |
+| C.2.2 Operation parameter mapping.....                             | 25        |
+| C.2.3 Notification parameter mapping.....                          | 25        |
+| C.3 Solution Set definitions.....                                  | 26        |
+| C.3.1 WSDL definition structure .....                              | 26        |
+
+|                        |                                             |    |
+|------------------------|---------------------------------------------|----|
+| C.3.2                  | Graphical Representation .....              | 26 |
+| C.3.3                  | WSDL specification “TMIRPSystem.wsdl” ..... | 27 |
+| Annex D (informative): | Change history.....                         | 32 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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; Test management Integration Reference Point (IRP), as identified below:
+
+- 32.321: "Test management Integration Reference Point (IRP); Requirements"
+- 32.322: "Test management Integration Reference Point (IRP): Information Service (IS)"
+- 32.326: "Test management Integration Reference Point (IRP): Solution Set definitions (SS)"**
+
+A 3G telecommunication network is composed of a multitude of different Network Elements (NE). For a successful operation of the network the operator must be provided with mechanisms allowing him to manage the network. These management activities can be grouped into several areas: configuration management, fault management, performance management, accounting management and security management.
+
+A management function assisting in different high level management areas such as fault management and performance management is test management. The purpose of testing is to get information about the functionality and performance of the 3G managed network subject to the test.
+
+The present document is part of a TS-family defining the Telecommunication Management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 [2]. The TM architecture is described in 3GPP TS 32.102 [3]. The other specifications define the interface (Itf-N) between the managing system (manager), which is in general the Network Manager (NM) and the managed system (agent), which is either an Element Manager (EM) or the managed NE itself. The Itf-N is composed of a number of integration reference points (IRPs) defining the information in the agent that is visible for the manager, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. One of these IRPs is the Test Management IRP.
+
+Each IRP is specified by the requirements part, the IS part and SS part.
+
+# --- 1 Scope
+
+The present document contains the Solution Sets for the IRP whose semantics is specified in Test management IRP IS (3GPP TS 32.322 [5]).
+
+This Solution Set specification is related to 3GPP TS 32.322 V10.0.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.322: "Telecommunication management; Test management Integration Reference Point (IRP): Information Service (IS)".
+- [6] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+- [7] W3C SOAP 1.1 specification (<http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>)
+- [8] W3C XPath 1.0 specification (<http://www.w3.org/TR/1999/REC-xpath-19991116>)
+- [9] W3C WSDL 1.1 specification (<http://www.w3.org/TR/2001/NOTE-wsdl-20010315>)
+- [10] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>)
+- [11] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [12] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [13] 3GPP TS 32.336: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [14] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements".
+- [15] Object Management Group 98 (November 1998): "*Notification Service: Joint Revised Submission OMG TC Document telecom/98-11-01*". <http://www.omg.org/technology/documents/>
+- [16] G CORBA Services (November 1996): "Common Object Services Specification" (clause 4 contains the Event Service specification). <http://www.omg.org/technology/documents/>
+- [17] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
+
+# --- 3 Definitions, symbols 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], 3GPP TS 32.331 [14] and 3GPP TS 32.322 [5] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Test Category:** one or more tests sharing a common purpose and similar characteristics
+
+**Tester Object (TO):** managed object that is instantiated for the purpose of monitoring and controlling a test invocation  
+Each test invocation has one associated TO. TOs are created and deleted by managed objects with TARR functionality.
+
+### **IRP document version number string:**
+
+The IRP document version number (sometimes called "IRP version" or "version number") string is used to identify the present document. The definition of "IRP document version number string" in 3GPP TS 32.311 [17] provides the rule to derive such a string.
+
+This string is returned in `get_test_management_IRP_versions` method and is carried in the first field of the notification header of all notifications related to Test Management IRP. This string is also returned in `get_notification_categories` method of the Notification IRP Agent, in case that IRP Agent is responsible for emitting notifications related to Test Management IRP.
+
+## 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].
+
+|       |                                           |
+|-------|-------------------------------------------|
+| CORBA | Common Object Request Broker Architecture |
+| EM    | Element Manager                           |
+| GSM   | Global System for Mobile communications   |
+| IDL   | Interface Definition Language             |
+| IRP   | Integration Reference Point               |
+| IOC   | Information Object Class                  |
+| IS    | Information Service                       |
+| NE    | Network Element                           |
+| NL    | Notification Log                          |
+| NM    | Network Manager                           |
+| OMG   | Object Management Group                   |
+| QoS   | Quality of Service                        |
+| SS    | Solution Set                              |
+| TARR  | Test Action Request Receiver              |
+| TM    | Test Management                           |
+| TMIRP | Test Management IRP                       |
+| TO    | Tester Object                             |
+| XML   | eXtensible Markup Language                |
+
+# --- 4 Solution Set Definitions
+
+This specification defines the following 3GPP Test 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 Test management IRP: Information Service (TS 32.322 [5]).
+
+---
+
+## A.1 Architectural features
+
+The overall architectural feature of Test Management IRP is specified in 3GPP TS 32.322 [5]. This clause specifies features that are specific to the CORBA SS.
+
+### A.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [6].
+
+### A.1.2 Notification Services
+
+In implementations of CORBA SS, IRPAgent conveys Test Management information to IRPManager via OMG Notification Service (OMG Notification Service [15]).
+
+OMG Event Service [16] provides event routing and distribution capabilities. OMG Notification Service provides, in addition to Event Service, event filtering and Quality of Service (QoS) as well.
+
+A necessary and sufficient sub set of OMG Notification Services shall be used to support `TestManagementIRPNotifications` notifications as specified in 3GPP TS 32.322 [5].
+
+### A.1.3 Push and Pull Style
+
+OMG Notification Service defines two styles of interaction. One is called push style. In this style, IRPAgent pushes notifications to IRPManager as soon as they are available. The other is called pull style. In this style, IRPAgent keeps the notifications till IRPManager requests for them.
+
+The Notification CORBA SS in 3GPP TS 32.306 [11] 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, IRPAgent may send multiple notifications using one single push operation. To pack multiple notifications into one push operation, IRPAgent may wait and not invoke the push operation as soon as notifications are available. To avoid IRPAgent to wait for an extended period of time that is objectionable to IRPManager, IRPAgent shall implement an IRPAgent wide timer configurable by administrator. On expiration of this timer, IRPAgent shall invoke push if there is at least one notification to be conveyed to IRPManager. This timer is re-started after each push invocation.
+
+### A.1.5 TestManagementIRPNotification Interface
+
+OMG CORBA Notification push operation is used to realise the notification of `TestManagementIRPNotifications`. 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 [15]). 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: IRP Agent may push EventBatch with only one Structured Event.
+
+## A.2 Mapping
+
+### A.2.1 Operation and Notification mapping
+
+The Test Management IRP IS in 3GPP TS 32.322 [5] defines semantics of operation and notification visible across the Test Management IRP. Table A.2.1 indicates mapping of these operations and notifications to their equivalents defined in the present SS.
+
+**Table A.2.1: Mapping from IS Operations and Notification to SS equivalents**
+
+| IS Operations/ notification TS 32.322 [5]                                                                                                | SS Method                                    | Qualifier |
+|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------|
+| initiateTests                                                                                                                            | initiate tests                               | M         |
+| terminateTests                                                                                                                           | terminate tests                              | M         |
+| monitorTest                                                                                                                              | monitor test                                 | M         |
+| getIRPVersion                                                                                                                            | get test management IRP versions             | M         |
+| getOperationProfile (see note)                                                                                                           | get test management IRP operation profile    | O         |
+| getNotificationProfile (see note)                                                                                                        | get test management IRP notification profile | O         |
+| notifyTestResult                                                                                                                         | push_structured_event (See subclause A.1.5)  | M         |
+| NOTE: This operation is of ManagedGenericIRP IOC specified in 3GPP TS 32.312 [12].<br>The TestManagementIRP IOC of [5] inherits from it. |                                              |           |
+
+### A.2.2 Operation parameter mapping
+
+The Test Management IRP IS in 3GPP TS 32.322 [5] defines semantics of parameters carried in operations across the Test Management IRP. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table A.2.2.1: Mapping from IS `initiateTests` parameters to SS equivalents**
+
+| IS Operation parameter  | SS Method parameter                                                                                                                                                                | Qualifier |
+|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| testInvocationInitiator | TestManagementIRPConstDefs::TestInvocationInitiator<br>test_invocation_initiator                                                                                                   | M         |
+| toBeInitiatedTests      | TestManagementIRPConstDefs::ToBeInitiatedTestSeq<br>to_be_initiated_test_seq                                                                                                       | M         |
+| response                | TestManagementIRPConstDefs::InitiateTestsResponse<br>Exceptions:<br>InitiateTests,<br>ManagedGenericIRPSystem::ParameterNotSupported,<br>ManagedGenericIRPSystem::InvalidParameter | M         |
+
+**Table A.2.2.2: Mapping from IS `terminateTests` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter                                                                                                                                                                                                                     | Qualifier |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| toBeTerminatedTests    | TestManagementIRPConstDefs::ToBeTerminatedTestSeq<br>to be terminated test seq                                                                                                                                                          | M         |
+| response               | TestManagementIRPConstDefs::TerminateTestsResponse<br>Exceptions:<br>TerminateTests,<br>ManagedGenericIRPSystem::OperationNotSupported,<br>ManagedGenericIRPSystem::ParameterNotSupported,<br>ManagedGenericIRPSystem::InvalidParameter | M         |
+
+**Table A.2.2.3: Mapping from IS monitorTest parameters to SS equivalents**
+
+| IS Operation parameter   | SS Method parameter                                                                                                                                                                                                  | Qualifier |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| toBeMonitoredTO          | TestManagementIRPConstDefs::ToBeMonitoredTO<br>to be monitored TO                                                                                                                                                    | M         |
+| monitoredAttributeValues | TestManagementIRPConstDefs::TOAttributes tO_attributes                                                                                                                                                               | M         |
+| error                    | ManagedGenericIRPConstDefs::Signal<br>Exceptions:<br>MonitorTest,<br>ManagedGenericIRPSystem::OperationNotSupported,<br>ManagedGenericIRPSystem::ParameterNotSupported,<br>ManagedGenericIRPSystem::InvalidParameter | M         |
+
+### A.2.3 Notification parameter mapping
+
+The Test Management IRP IS in 3GPP TS 32.322 [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 [15]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [15], is:
+
+```
+Header
+  Fixed Header
+    domain_name
+    type_name
+    event_name
+  Variable Header
+Body
+  filterable_body_fields
+  remaining_body
+```
+
+Table A.2.3 lists in the second column all OMG Structured Event attributes. The first column identifies notification
+
+parameters defined in 3GPP TS 32.322 [5], Test Management: Information Service (IS).
+
+**Table A.2.3: Mapping for notifyTestResult**
+
+| IS Parameters                           | OMG CORBA Structured Event attribute  | Qualifier  | Comment                                                                                                                                                                                                                                                                                                                                                                                          |
+|-----------------------------------------|---------------------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| There is no corresponding IS parameter. | domain_name                           | M          | It carries the IRP document version number string. See subclause 3.1.<br>It indicates the syntax and semantics of the Structured Event as defined by the present document.                                                                                                                                                                                                                       |
+| notificationType                        | type_name                             | M          | This is the NOTIFY_TM_TEST_RESULT of module of TestManagementIRPConstDefs.                                                                                                                                                                                                                                                                                                                       |
+| There is no corresponding IS parameter. | event_name                            | M          | It carries no information.                                                                                                                                                                                                                                                                                                                                                                       |
+| There is no corresponding IS parameter. | 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.<br><br>Name of this NV pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is a string. See corresponding table in TS 32.306 [11] Notification IRP: Solution Set (SS) definitions. |
+| notificationId                          | One NV pair of remaining_body         | M          | Name of NV pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is a long. See corresponding table in TS 32.306 [11] Notification IRP: Solution Set (SS) definitions.                                                                                                                                                         |
+| eventTime                               | One NV pair of filterable_body_fields | M          | Name of NV pair is the EVENT_TIME of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is IRPTime. See corresponding table in TS 32.306 [11] Notification IRP: Solution Set (SS) definitions.                                                                                                                                                             |
+| systemDN                                | One NV pair of filterable_body_fields | M          | Name of NV pair is the SYSTEM_DN of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is a string. See corresponding table in TS 32.306 [11] Notification IRP: Solution Set (SS) definitions.                                                                                                                                                             |
+| testInvocationInitiator                 | One NV pair of filterable_body_fields | M          | Name of NV pair is the TEST_INVOCATION_INITIATOR of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a string.                                                                                                                                                                                                                                                                      |
+| testOutcome                             | One NV pair of remaining_body         | O          | Name of NV pair is the TEST_OUTCOME of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a enum {Inconclusive, Pass, Fail, TimeOut, PrematureTermination}                                                                                                                                                                                                                            |
+| mORT                                    | One NV pair of remaining_body         | O          | Name of NV pair is the MORT of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a string.                                                                                                                                                                                                                                                                                           |
+| proposedRepairActions                   | One NV pair of remaining_body         | O          | Name of NV pair is the PROPOSED_REPAIR_ACTIONS of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a string.                                                                                                                                                                                                                                                                        |
+| additionalInformation                   | One NV pair of remaining_body         | O          | Name of NV pair is the ADDITIONAL_INFORMATION of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a string.                                                                                                                                                                                                                                                                         |
+| fileReference                           | One NV pair of remaining_body         | M (Note 1) | Name of NV pair is the FILE_REFERENCE of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a string.                                                                                                                                                                                                                                                                                 |
+| fileExpiryDate                          | One NV pair of remaining_body         | M (Note 2) | Name of NV pair is the FILE_EXPIRY_DATE of module TestManagementIRPConstDefs.<br><br>Value of NV pair is a string.                                                                                                                                                                                                                                                                               |
+
+| IS Parameters | OMG CORBA Structured Event attribute                                                                                                                                                                                                     | Qualifier | Comment |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|
+| Note 1:       | It shall contain no information or be absent if there is no test result captured in a file.                                                                                                                                              |           |         |
+| Note 2:       | It shall contain information if the test results are captured in a file.<br>It shall contain no information or be absent if fileReference carries no information or absent.<br>Otherwise, it shall contain a valid future date and time. |           |         |
+
+## --- A.3 Solution Set definitions
+
+### A.3.1 IDL definition structure
+
+Clause A.3.2 defines the constants and types used by the Test management IRP.
+
+Clause A.3.3 defines the operations which are performed by the Test management IRP agent.
+
+Clause A.3.4 defines the notifications which are emitted by the Test management IRP agent.
+
+### A.3.2 IDL specification "TestManagementIRPConstDefs.idl"
+
+```
+// File: TestManagementIRPConstDefs.idl
+
+#ifndef _TESTMANAGEMENTIRPCONSTDEFS_IDL_
+#define _TESTMANAGEMENTIRPCONSTDEFS_IDL_
+
+#include "CosNotification.idl"
+#include "ManagedGenericIRPConstDefs.idl"
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: TestManagementIRPConstDefs
+This module contains commonly used definitions for Test Management IRP
+=====
+*/
+module TestManagementIRPConstDefs
+{
+    /*
+    This defines the notification type of this Test Management
+    IRP.
+    */
+    const string NOTIFY_TM_TEST_RESULT = "x1";
+
+    /*
+    This enum defines the test state
+    */
+    enum TestStateType {
+        NotInitialized,
+        Idle,
+        Initializing,
+        Testing,
+        Terminating,
+        Disabled
+    };
+
+    /*
+    This enum defines the test outcome
+    */
+    enum TestOutcomeType {
+        Inconclusive,
+        Pass,
+        Fail,
+        TimeOut,
+        PrematureTermination
+    };
+
+    /*
+    This block defines notification attributes of this IRP.
+    These attribute values should not clash with those used
+    in Notification header (see IDL of Notification IRP).
+    */
+    interface AttributeNameValue
+    {
+        const string TEST_INVOCATION_INITIATOR = "f";
+        const string TEST_INVOCATION_ID = "g";
+        const string TEST_ACTUAL_START_TIME = "h";
+        const string TEST_ACTUAL_STOP_TIME = "i";
+        const string TEST_OUTCOME = "j";
+        const string MORT = "k";
+        const string PROPOSED_REPAIR_ACTIONS = "l";
+        const string ADDITIONAL_INFORMATION = "m";
+        const string FILE_REFERENCE = "n";
+        const string FILE_EXPIRY_DATE = "o";
+        const string TEST_SOURCE_ADDRESS = "p";
+        const string TEST_DESTINATION_ADDRESS = "q";
+        const string TEST_LOOPBACK_ADDRESS = "r";
+        const string TEST_PACKET_INFORMATION = "s";
+    };
+
+    typedef string TestInvocationInitiator;
+    typedef string ToBeMonitoredTO;
+```
+
+```
+
+typedef CosNotification::PropertySeq NVPairs;
+
+/*
+Define a seq of to-be-initiated-test
+*/
+struct ToBeInitiatedTest
+{
+    unsigned long max_testing_state_duration;//seconds;0->no limit
+    string toBeTestedMORT; //MORT DN
+    string tOClass;          //Tester object class
+    string tODN;             //Tester object DN
+    NVPairs tONVPair;        //Tester object attributes in NV pairs
+};
+
+typedef sequence <ToBeInitiatedTest> ToBeInitiatedTestSeq;
+
+/*
+Define the structure returned by initiate_tests
+*/
+struct InitiateTestsResponseElement
+{
+    // If failureReason is NULL, the test is initiated successfully and
+    // testInvocationId contains the invocation id. In case the tester object name is not
+    // provided in the request, it shall be carried by testerObjectDN. In case the tester
+    // object name is provided in the request tODN shall be NULL.
+    // Else, the test initiation fails and failureReason contains
+    // the failure reason and testInvocationId contains garbage.
+    string failureReason;
+    string testInvocationId;
+    string tODN;
+};
+
+typedef sequence <InitiateTestsResponseElement> InitiateTestsResponse;
+
+/*
+Define a seq of to-be-terminated-test
+*/
+typedef string TestInvocationId;
+typedef sequence <TestInvocationId> ToBeTerminatedTestSeq;
+
+/*
+Define the structure returned by terminate_tests
+*/
+struct TerminateTestsResponseElement
+{
+    // If failureReason is NULL, the test has terminated successfully and
+    // testInvocationId identifies the terminated invocation.
+    // Else, the test termination fails and failureReason contains
+    // the failure reason and testInvocationId contains garbage.
+    string failureReason;
+    string testInvocationId;
+};
+
+typedef sequence <TerminateTestsResponseElement> TerminateTestsResponse;
+
+/*
+Define the structure of a TOAttributes.
+*/
+struct TOAttributes
+{
+    TestStateType testState;
+    TestOutcomeType testOutcome;
+    NVPairs attributesInNVPairs;
+};
+
+};
+
+#endif // _TESTMANAGEMENTIRPCONSTDEFS_IDL_
+
+```
+
+### A.3.3 IDL specification "TestManagementIRPSystem.idl"
+
+```
+// File: TestManagementIRPSystem.idl
+
+#ifndef _TESTMANAGEMENTIRPSYSTEM_IDL_
+#define _TESTMANAGEMENTIRPSYSTEM_IDL_
+
+#include "TestManagementIRPConstDefs.idl"
+#include "ManagedGenericIRPSystem.idl"
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: TestManagementIRPSystem
+This module contains the specification of all methods of TestManagement IRP Agent.
+=====
+*/
+module TestManagementIRPSystem
+{
+    /*
+    System may fail to complete an operation. System can provide reason
+    to qualify the failed reason. The semantics carried in reason
+    is outside the scope of this IRP.
+    */
+    exception GetTestManagementIRPVersions { string reason; };
+    exception GetTestManagementIRPOperationsProfile { string reason; };
+    exception GetTestManagementIRPNotificationProfile { string reason; };
+    exception InitiateTests { string reason; };
+    exception TerminateTests { string reason; };
+    exception MonitorTest { string reason; };
+
+    interface TestManagementIRP
+    {
+        /*
+        Return the list of all supported TestManagement IRP versions.
+        */
+        ManagedGenericIRPConstDefs::VersionNumberSet
+        get_Test_Management_IRP_versions (
+        )
+        raises (GetTestManagementIRPVersions);
+
+        /*
+        Return the list of all supported operations and their supported
+        parameters for a specific TestManagement IRP version.
+        */
+        ManagedGenericIRPConstDefs::MethodList
+        get_Test_Management_IRP_operations_profile (
+            in ManagedGenericIRPConstDefs::VersionNumber
+            test_management_irp_version
+        )
+        raises (GetTestManagementIRPOperationsProfile,
+                ManagedGenericIRPSystem::OperationNotSupported,
+                ManagedGenericIRPSystem::InvalidParameter);
+
+        /*
+        Return the list of all supported notifications and their supported
+        parameters for a specific TestManagement IRP version.
+        */
+        ManagedGenericIRPConstDefs::MethodList
+        get_Test_Management_IRP_notification_profile (
+            in ManagedGenericIRPConstDefs::VersionNumber
+            test_management_irp_version
+        )
+        raises (GetTestManagementIRPNotificationProfile,
+                ManagedGenericIRPSystem::OperationNotSupported,
+                ManagedGenericIRPSystem::InvalidParameter);
+    }
+}
+```
+
+```
+
+    /*
+Request to initiate tests.
+*/
+TestManagementIRPConstDefs::InitiateTestsResponse
+initiate_tests (
+    in TestManagementIRPConstDefs::TestInvocationInitiator
+        test_invocation_initiator,
+    in TestManagementIRPConstDefs::ToBeInitiatedTestSeq
+        to_be_initiated_test_seq
+)
+raises (InitiateTests,
+        ManagedGenericIRPSystem::InvalidParameter);
+
+    /*
+Request to terminate tests.
+*/
+TestManagementIRPConstDefs::TerminateTestsResponse
+terminate_tests (
+    in TestManagementIRPConstDefs::ToBeTerminatedTestSeq
+        to_be_terminated_test_seq
+)
+raises (TerminateTests,
+        ManagedGenericIRPSystem::InvalidParameter);
+
+    /*
+Request test info (to monitor a test).
+*/
+ManagedGenericIRPConstDefs::Signal monitor_test (
+    in TestManagementIRPConstDefs::ToBeMonitoredTO
+        to_be_monitored_TO,
+    out TestManagementIRPConstDefs::TOAttributes toO_attributes
+)
+raises (MonitorTest,
+        ManagedGenericIRPSystem::InvalidParameter);
+
+};
+
+};
+
+#endif // _TESTMANAGEMENTIRPSYSTEM_IDL_
+
+```
+
+### A.3.4 IDL specification "TestManagementIRPNotifications.idl"
+
+```
+// File: TestManagementIRPNotifications.idl
+
+#ifndef _TESTMANAGEMENTIRPNOTIFICATIONS_IDL
+#define _TESTMANAGEMENTIRPNOTIFICATIONS_IDL
+
+#include "TestManagementIRPConstDefs.idl"
+#include "NotificationIRPConstDefs.idl"
+#include "NotificationIRPNotifications.idl"
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/** Module: TestManagementIRPNotifications
+This module contains the specification of all notifications of Test Management IRP Agent.
+=====
+*/
+
+module TestManagementIRPNotificationsfDefs
+{
+    /**
+     * Constant definitions for the notifyTestResult notification
+     */
+    interface notifyTestResult: NotificationIRPNotifications::Notify
+    {
+        const string EVENT_TYPE = "notifyTestResult";
+
+        /**
+         * This constant defines the name of the period property,
+         * which is transported in the filterable_body fields.
+         * The data type for the value of this property
+         * is TestManagementIRPConstDefs:: TestInvocationInitiator.
+         */
+        const string TEST_INVOCATION_INITIATOR =
+            TestManagementIRPConstDefs::AttributeNameValue::TEST_INVOCATION_INITIATOR;
+
+        /**
+         * This constant defines the name of the
+         * TestInvocationId property,
+         * which is transported in the remaining body
+         * fields.
+         * The data type for the value of this property
+         * is TestManagementIRPConstDefs:: TestInvocationId.
+         */
+        const string TEST_INVOCATION_ID =
+            TestManagementIRPConstDefs::AttributeNameValue::TEST_INVOCATION_ID;
+
+        /**
+         * This constant defines the name of the
+         * TestActualStartTime property,
+         * which is transported in the remaining_body
+         * fields.
+         * The data type for the value of this property
+         * is TestManagementIRPConstDefs:: TestActualStartTime.
+         */
+        const string TEST_ACTUAL_START_TIME =
+            TestManagementIRPConstDefs::AttributeNameValue::TEST_ACTUAL_START_TIME;
+
+        /**
+         * This constant defines the name of the
+         * TestActualStopTime property,
+         * which is transported in the remaining_body
+         * fields.
+         * The data type for the value of this property
+         * is TestManagementIRPConstDefs:: TestActualStopTime.
+         */
+        const string TEST_ACTUAL_STOP_TIME =
+            TestManagementIRPConstDefs::AttributeNameValue::TEST_ACTUAL_STOP_TIME;
+
+        /**
+         * This constant defines the name of the
+         * testOutcome property,
+         * which is transported in the remaining_body
+         * fields.
+         * The data type for the value of this property
+         */
+    }
+}
+```
+
+```
+
+    * is TestManagementIRPConstDefs:: testOutcome.
+    */
+    const string TEST_OUTCOME = TestManagementIRPConstDefs::AttributeNameValue::TEST_OUTCOME;
+
+    /*
+    * This constant defines the name of the
+    * MORT property,
+    * which is transported in the remaining_body
+    * fields.
+    * The data type for the value of this property
+    * is TestManagementIRPConstDefs::MORT.
+    */
+    const string MORT = TestManagementIRPConstDefs::AttributeNameValue::MORT;
+
+    /*
+    * This constant defines the name of the
+    * ProposedRepairActions property,
+    * which is transported in the remaining_body
+    * fields.
+    * The data type for the value of this property
+    * is TestManagementIRPConstDefs::ProposedRepairActions.
+    */
+    const string PROPOSED_REPAIR_ACTIONS =
+        TestManagementIRPConstDefs::AttributeNameValue::PROPOSED_REPAIR_ACTIONS;
+
+    /*
+    * This constant defines the name of the
+    * AdditionalInformation property,
+    * which is transported in the remaining_body
+    * fields.
+    * The data type for the value of this property
+    * is TestManagementIRPConstDefs:: AdditionalInformation.
+    */
+    const string ADDITIONAL_INFORMATION =
+        TestManagementIRPConstDefs::AttributeNameValue::ADDITIONAL_INFORMATION;
+
+    /*
+    * This constant defines the name of the
+    * FileReference property,
+    * which is transported in the remaining_body
+    * fields.
+    * The data type for the value of this property
+    * is TestManagementIRPConstDefs:: FdditionalInformation.
+    */
+    const string FILE_REFERENCE = TestManagementIRPConstDefs::AttributeNameValue::FILE_REFERENCE;
+
+    /*
+    * This constant defines the name of the
+    * FileExpiryDate property,
+    * which is transported in the remaining_body
+    * fields.
+    * The data type for the value of this property
+    * is TestManagementIRPConstDefs:: FileExpiryDate.
+    */
+    const string FILE_EXPIRY_DATE =
+        TestManagementIRPConstDefs::AttributeNameValue::FILE_EXPIRY_DATE;
+
+};
+
+};
+
+#endif // _TESTMANAGEMENTIRPNOTIFICATIONS_IDL_
+
+```
+
+# --- Annex B (normative): XML Definitions
+
+This annex contains the XML Definitions for the Test management Integration Reference Point (Test management IRP) as it applies to Itf-N, in accordance with Test management IRP IS definitions [5] as well as Notification Log IRP XML Definitions [13].
+
+Apart from being used for the Notification Log, the XML definitions for Test management IRP notifications are also used by the Test management IRP SOAP SS.
+
+## --- B.1 Architectural Features
+
+The overall architectural feature of Test management IRP is specified in 3G TS 32.322 [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 [6].
+
+### B.1.2 Notification Services
+
+This annex defines the XML syntax of Test management IRP notifications that is to be used for the Test 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 [13].
+
+### B.1.3 IOC Definitions
+
+This annex defines the XML syntax for the IOC definitions of the Test management IRP IS [5], which are used by the XML definitions for the Test management IRP notifications and the Test 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 Test management IRP notifications as defined in [5]. These definitions are to be used for the Test 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 [13], as well as considerations for NL IRP XML File Name Conventions defined therein.
+
+### B.3.2 Graphical Representation
+
+![Diagram of the NotifyTestResults XML schema structure showing header and body components.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg)
+
+The diagram shows the structure of the **NotifyTestResults** message. The root element **NotifyTestResults** branches into a sequence containing:
+
+- xe:header** [+]
+- xt:body**
+  - A sequence containing:
+    - xt:TestInvocationId** (optional/dashed)
+    - xt:TestInvocationInitiator** (optional/dashed)
+    - xt:TestOutcome** (optional/dashed)
+    - xt:MORT**
+    - xt:ProposedRepairActions** [+] (optional/dashed)
+    - xt:AdditionalInformation** [+] (optional/dashed)
+    - xt:FileReference**
+    - xt:fileExpiryDate**
+
+Diagram of the NotifyTestResults XML schema structure showing header and body components.
+
+**Figure B.3.2**
+
+NOTE: The use of XML schema key word "sequence" to support IS-defined set (not sequence) is for the purpose of XML processor efficiency. This shall not imply the use of "sequence" in other technology.
+
+### B.3.3 XML Schema “tMIRPNotif.xsd”
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    3GPP TS 32.326 TMIRP Notification XML Schema
+    tMIRPNotif.xsd
+-->
+<schema xmlns:xt="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#tMIRPNotif"
+    xmlns:xe="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#notification"
+    xmlns="http://www.w3.org/2001/XMLSchema"
+    targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#tMIRPNotif"
+    elementFormDefault="qualified" attributeFormDefault="unqualified">
+    <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#notification" />
+    <simpleType name="TestInvocationId">
+        <restriction base="string"/>
+    </simpleType>
+    <simpleType name="TestOutcome">
+        <restriction base="string">
+            <enumeration value="pass"/>
+            <enumeration value="fail"/>
+            <enumeration value="inconclusive"/>
+            <enumeration value="timed-out"/>
+            <enumeration value="premature-termination"/>
+        </restriction>
+    </simpleType>
+    <complexType name="NotifyTestResults">
+        <complexContent>
+            <extension base="xe:Notification">
+                <sequence>
+                    <element name="body">
+                        <complexType>
+                            <sequence>
+                                <element name="fileReference" type="string"/>
+                                <element name="fileExpiryDate" type="dateTime"/>
+                                <element name="testInvocationId" type="xt:TestInvocationId"
+minOccurs="0"/>
+                                <element name="testInvocationInitiator" type="string"
+minOccurs="0"/>
+                                <element name="testOutcome" type="xt:TestOutcome" minOccurs="0"/>
+                                <element name="mORT" type="string" minOccurs="0"/>
+                                <element name="proposedRepairActions" type="anyType" minOccurs="0"/>
+                                <element name="additionalInformation" type="anyType" minOccurs="0"/>
+                            </sequence>
+                        </complexType>
+                    </element>
+                </sequence>
+            </extension>
+        </complexContent>
+    </complexType>
+    <element name="NotifyTestResults" type="xt:NotifyTestResults"/>
+</schema>
+```
+
+# --- Annex C (normative): SOAP Solution Set
+
+This annex specifies the SOAP Solution Set for the IRP whose semantics are specified in Test management IRP: Information Service (3GPP TS 32.322 [5]).
+
+---
+
+## C.1 Architectural features
+
+The overall architectural feature of the Test management IRP is specified in 3GPP TS 32.322 [5]. This clause specifies features that are specific to the SOAP Solution Set.
+
+### C.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [6].
+
+### C.1.2 Notification Services
+
+The Test management IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.306 [11]. The IRP Agent shall support the push interface model, which means that the IRP Agent sends notifications to the IRP Manager as soon as new events occur. The IRP Manager does not need to check ("pull") for events.
+
+Relevant definitions are imported from the Test management IRP XML definitions in Annex B.
+
+### C.1.3 Supported W3C specifications
+
+The SOAP 1.1 specification [7] and WSDL 1.1 specification [9] are supported.
+
+The SOAP 1.2 specification [10] is supported optionally.
+
+This specification uses "document" style in WSDL file.
+
+This specification uses "literal" encoding style in WSDL file.
+
+The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification [8]). IRP Agents may throw a FilterComplexityLimit fault when a given filter is too complex.
+
+### C.1.4 Prefixes and namespaces
+
+This specification uses a number of namespace prefixes throughout that are listed in Table C.1.4.
+
+**Table C.1.4: Prefixes and Namespaces used in this specification**
+
+| PREFIX           | NAMESPACE                                                                                                                                                                     |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| (no prefix)      | <a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a>                                                                                               |
+| soap             | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a>                                                                                     |
+| tmIRPSystem      | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPSystem</a>                           |
+| tmIRPData        | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPData">http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPData</a>                               |
+| genericNrm       | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm">http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm</a>                             |
+| genericIRPSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem</a>                 |
+| ntfIRPNtfSystem  | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem</a> |
+
+## C.2 Mapping
+
+### C.2.1 Operation and notification mapping
+
+The Test management IRP IS (3GPP TS 32.322 [5]) defines semantics of operation and notification visible across the Itf-N. Table C.2.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
+
+**Table C.2.1: Mapping from IS Operation to SS Equivalents**
+
+| IS Operations in 3GPP TS 32.322 [5] | SS Operations   | SS Port                    | Qualifier |
+|-------------------------------------|-----------------|----------------------------|-----------|
+| initiateTests                       | initiateTests   | TMIRPControlOperationsPort | M         |
+| terminateTests                      | terminateTests  | TMIRPControlOperationsPort | M         |
+| monitorTest                         | monitorTest     | TMIRPMonitorOperationsPort | M         |
+| notifyFilePreparationError          | notify (note 1) | NotificationIRPNtfPort     | M         |
+
+NOTE 1: The IS equivalent maps to an XML definition specified in Annex B, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3GPP TS 32.306 [11].
+
+### C.2.2 Operation parameter mapping
+
+The Test management IRP IS (3GPP TS 32.322 [5]) defines semantics of parameters carried in the operations. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table C.2.2.1: Mapping from IS `initiateTests` parameters to SS equivalents**
+
+| IS Operation parameter  | SS Method parameter     | Qualifier |
+|-------------------------|-------------------------|-----------|
+| testInvocationInitiator | testInvocationInitiator | M         |
+| toBeInitiatedTests      | toBeInitiatedTests      | M         |
+| response                | response                | M         |
+
+**Table C.2.2.2: Mapping from IS `terminateTests` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|---------------------|-----------|
+| toBeTerminatedTests    | toBeTerminatedTests | M         |
+| response               | response            | M         |
+
+**Table C.2.2.3: Mapping from IS `monitorTest` parameters to SS equivalents**
+
+| IS Operation parameter   | SS Method parameter      | Qualifier |
+|--------------------------|--------------------------|-----------|
+| toBeMonitoredTO          | toBeMonitoredTO          | M         |
+| monitoredAttributeValues | monitoredAttributeValues | M         |
+| error                    | error                    | M         |
+
+### C.2.3 Notification parameter mapping
+
+The Test management IRP Notifications are defined in Annex B.
+
+## C.3 Solution Set definitions
+
+### C.3.1 WSDL definition structure
+
+Clause C.3.2 provides a graphical representation of the Test management IRP service.
+
+Clause C.3.3 defines the services which are supported the Test management IRP agent.
+
+### C.3.2 Graphical Representation
+
+The WSDL structure is depicted in Figure C.3.2 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service.
+
+![WSDL structure diagram showing Port Types, Bindings, and Services for the Test management IRP SOAP Solution Set.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg)
+
+The diagram illustrates the WSDL structure for the Test management IRP SOAP Solution Set, organized into three columns: Port Types, Bindings, and Services.
+
+- Port Types:**
+  - GenericIRPPortType:** Operations include getIRPVersion, getOperationProfile, and getNotificationProfile.
+  - NotificationIRPNTf:** Operation include notify.
+  - TMIRPControlOperations:** Operations include initiateTests and terminateTests.
+  - TMIRPMonitorOperations:** Operation include monitorTest.
+- Bindings:**
+  - GenericIRPBinding:** Transport: http://schemas.xmlsoap.org/soap/http. Operations: getIRPVersion, getOperationProfile, getNotificationProfile.
+  - NotificationIRPNTf:** Transport: http://schemas.xmlsoap.org/soap/http. Operation: notify.
+  - TMIRPControlOperations:** Transport: http://schemas.xmlsoap.org/soap/http. Operations: initiateTests, terminateTests.
+  - TMIRPMonitorOperations:** Transport: http://schemas.xmlsoap.org/soap/http. Operation: monitorTest.
+- Services:**
+  - NotificationIRPNTf:** Location: To be defined.
+  - TMIRPService:** Contains four ports:
+    - GenericIRPPort:** Location: http://www.3gpp.org/ftp/specs/archive/32\_series/32.316#GenericIRP
+    - NotificationIRPNTfPort:** Location: http://www.3gpp.org/ftp/specs/archive/32\_series/32.306#NotificationIRPNTf
+    - TMIRPControlOperationsPort:** Location: http://www.3gpp.org/ftp/specs/archive/32\_series/32.326#TMIRPControl
+    - TMIRPMonitorOperationsPort:** Location: http://www.3gpp.org/ftp/specs/archive/32\_series/32.326#TMIRPMonitor
+
+WSDL structure diagram showing Port Types, Bindings, and Services for the Test management IRP SOAP Solution Set.
+
+Figure C.3.2: Test management IRP SOAP Solution Set WSDL structure
+
+
+
+### C.3.3 WSDL specification “TMIRPSystem.wsdl”
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    3GPP TS 32.326 Test Management IRP SOAP Solution Set
+-->
+<definitions
+  xmlns="http://schemas.xmlsoap.org/wsdl/"
+  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
+  xmlns:tMIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPSystem"
+  xmlns:tMIRPData="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPData"
+  xmlns:genericNrm="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"
+  xmlns:genericIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem"
+  xmlns:ntfIRPNtfSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem"
+  targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPSystem">
+  <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem"/>
+  <import
+  namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem"/>
+  <types>
+    <schema targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPData"
+    xmlns="http://www.w3.org/2001/XMLSchema">
+      <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"/>
+      <!-- attributeNameValue Type -->
+      <complexType name="attributeNameValueType">
+        <sequence>
+          <element name="attributeName" type="string"/>
+          <element name="attributeValue" type="string"/>
+        </sequence>
+      </complexType>
+      <!-- operationResult Type -->
+      <simpleType name="operationResultType">
+        <restriction base="string">
+          <enumeration value="operationFailedEntirely"/>
+          <enumeration value="operationFailedPartly"/>
+          <enumeration value="operationSucceeded"/>
+        </restriction>
+      </simpleType>
+      <!-- initiateTests Request -->
+      <element name="initiateTestsRequest">
+        <complexType>
+          <sequence>
+            <element name="testInvocationInitiator" type="genericNrm:dn"/>
+            <element name="toBeInitiatedTests">
+              <complexType>
+                <sequence maxOccurs="unbounded">
+                  <choice minOccurs="0">
+                    <element name="maxTestingStateDuration" type="duration"/>
+                    <element name="noLimitTestingStateDuration"/>
+                  </choice>
+                  <element name="toBeTestedMORT" type="genericNrm:dn" minOccurs="0"/>
+                  <element name="testerObjectClass" type="genericNrm:dn"/>
+                  <element name="testerObjectName" type="string" minOccurs="0"/>
+                  <element name="testerObjectInitialAttributeList" minOccurs="0">
+                    <complexType>
+                      <sequence maxOccurs="unbounded">
+                        <element name="initialAttribute"
+type="tMIRPData:attributeNameValueType"/>
+                      </sequence>
+                    </complexType>
+                  </element>
+                </sequence>
+              </complexType>
+            </element>
+          </sequence>
+        </complexType>
+      </element>
+      <!-- initiateTests Response -->
+      <element name="initiateTestsResponse">
+        <complexType>
+          <sequence>
+            <element name="initiateTestsResult" type="tMIRPData:operationResultType"/>
+            <element name="response">
+              <complexType>
+                <sequence maxOccurs="unbounded">
+                  <choice>
+                    <element name="testInitiated">
+
+```
+
+```
+
+        <complexType>
+          <sequence>
+            <element name="testInvocationId" type="string"/>
+            <element name="testerObjectName" type="string"
+minOccurs="0"/>
+          </sequence>
+        </complexType>
+      </element>
+      <element name="testNotInitiated">
+        <complexType>
+          <sequence>
+            <element name="failureReason">
+              <simpleType>
+                <restriction base="string">
+                  <enumeration value="TOClassNotExisting"/>
+                  <enumeration value="MORTNotExisting"/>
+                  <enumeration value="MORTNotAvailable"/>
+                  <enumeration
+value="operation_failed_invalid_input_parameter"/>
+                  <enumeration
+value="operation_failed_unsupported_optional_input_parameter_maxTestingStateDuration"/>
+                  <enumeration
+value="operation_failed_unsupported_optional_input_parameter_noLimitTestingStateDuration"/>
+                  <enumeration
+value="operation_failed_unsupported_optional_input_parameter_toBeTestedMORT"/>
+                  <enumeration
+value="operation failed unsupported optional input parameter_testerObjectName"/>
+                  <enumeration
+value="operation_failed_unsupported_optional_input_parameter_testerObjectInitialAttributeList"/>
+                  <enumeration
+value="operation failed internal problem"/>
+                </restriction>
+              </simpleType>
+            </element>
+          </sequence>
+        </complexType>
+      </element>
+    </choice>
+  </sequence>
+</complexType>
+</element>
+</sequence>
+</complexType>
+</element>
+<!-- initiateTests Fault -->
+<element name="initiateTestsFault">
+  <simpleType>
+    <restriction base="string">
+      <enumeration value="OperationFailed"/>
+    </restriction>
+  </simpleType>
+</element>
+<!-- terminateTests Request -->
+<element name="terminateTestsRequest">
+  <complexType>
+    <sequence maxOccurs="unbounded">
+      <element name="testInvocationId" type="string"/>
+    </sequence>
+  </complexType>
+</element>
+<!-- terminateTests Response -->
+<element name="terminateTestsResponse">
+  <complexType>
+    <sequence>
+      <element name="terminateTestsResult" type="tmIRPData:operationResultType"/>
+      <element name="response">
+        <complexType>
+          <sequence maxOccurs="unbounded">
+            <choice>
+              <element name="testTerminated">
+                <complexType>
+                  <sequence>
+                    <element name="testInvocationId" type="string"/>
+                  </sequence>
+                </complexType>
+              </element>
+              <element name="testNotTerminated">
+                <complexType>
+
+```
+
+```
+
+        <sequence>
+          <element name="testInvocationId" type="string"/>
+          <element name="failureReason">
+            <simpleType>
+              <restriction base="string">
+                <enumeration value="testInvocationIdNotExisting"/>
+                <enumeration
+value="operation_failed_invalid_input_parameter"/>
+                <enumeration
+value="operation_failed_internal_problem"/>
+              </restriction>
+            </simpleType>
+          </element>
+        </sequence>
+      </complexType>
+    </element>
+  </choice>
+</sequence>
+</complexType>
+</element>
+</sequence>
+</complexType>
+</element>
+</sequence>
+</complexType>
+</element>
+<!-- terminateTests Fault -->
+<element name="terminateTestsFault">
+  <simpleType>
+    <restriction base="string">
+      <enumeration value="OperationFailed"/>
+    </restriction>
+  </simpleType>
+</element>
+<!-- monitorTest Request -->
+<element name="monitorTestRequest">
+  <complexType>
+    <sequence>
+      <element name="toBeMonitoredTO" type="genericNrm:dn"/>
+    </sequence>
+  </complexType>
+</element>
+<!-- monitorTest Response -->
+<element name="monitorTestResponse">
+  <complexType>
+    <sequence>
+      <element name="monitorTestResult" type="tmIRPData:operationResultType"/>
+      <element name="monitoredAttributeValues" minOccurs="0">
+        <complexType>
+          <sequence>
+            <element name="testState">
+              <simpleType>
+                <restriction base="string">
+                  <enumeration value="notInitialized"/>
+                  <enumeration value="idle"/>
+                  <enumeration value="initializing"/>
+                  <enumeration value="testing"/>
+                  <enumeration value="terminating"/>
+                  <enumeration value="disabled"/>
+                </restriction>
+              </simpleType>
+            </element>
+            <element name="testOutcome">
+              <simpleType>
+                <restriction base="string">
+                  <enumeration value="pass"/>
+                  <enumeration value="fail"/>
+                  <enumeration value="inconclusive"/>
+                  <enumeration value="timed-out"/>
+                  <enumeration value="premature-termination"/>
+                </restriction>
+              </simpleType>
+            </element>
+            <sequence minOccurs="0" maxOccurs="unbounded">
+              <element name="otherAttribute"
+type="tmIRPData:attributeNameValueType"/>
+            </sequence>
+          </sequence>
+        </complexType>
+      </element>
+      <element name="error">
+
+```
+
+```
+
+    <complexType>
+      <sequence>
+        <element name="failureReason">
+          <simpleType>
+            <restriction base="string">
+              <enumeration value="TOInstanceNotExisting"/>
+              <enumeration value="errorReadingAttribute"/>
+              <enumeration value="operation_failed_invalid_input_parameter"/>
+              <enumeration value="operation_failed_internal_problem"/>
+            </restriction>
+          </simpleType>
+        </element>
+        <element name="errorInfo" type="string"/>
+      </sequence>
+    </complexType>
+  </element>
+</sequence>
+</complexType>
+</element>
+<!-- monitorTest Fault -->
+<element name="monitorTestFault">
+  <simpleType>
+    <restriction base="string">
+      <enumeration value="OperationFailed"/>
+    </restriction>
+  </simpleType>
+</element>
+</schema>
+</types>
+<message name="initiateTestsRequest">
+  <part name="parameter" element="tmIRPData:initiateTestsRequest"/>
+</message>
+<message name="initiateTestsResponse">
+  <part name="parameter" element="tmIRPData:initiateTestsResponse"/>
+</message>
+<message name="initiateTestsFault">
+  <part name="parameter" element="tmIRPData:initiateTestsFault"/>
+</message>
+<message name="terminateTestsRequest">
+  <part name="parameter" element="tmIRPData:terminateTestsRequest"/>
+</message>
+<message name="terminateTestsResponse">
+  <part name="parameter" element="tmIRPData:terminateTestsResponse"/>
+</message>
+<message name="terminateTestsFault">
+  <part name="parameter" element="tmIRPData:terminateTestsFault"/>
+</message>
+<message name="monitorTestRequest">
+  <part name="parameter" element="tmIRPData:monitorTestRequest"/>
+</message>
+<message name="monitorTestResponse">
+  <part name="parameter" element="tmIRPData:monitorTestResponse"/>
+</message>
+<message name="monitorTestFault">
+  <part name="parameter" element="tmIRPData:monitorTestFault"/>
+</message>
+<portType name="TMIRPControlOperations">
+  <operation name="initiateTests">
+    <input message="tmIRPSystem:initiateTestsRequest"/>
+    <output message="tmIRPSystem:initiateTestsResponse"/>
+    <fault name="initiateTestsFault" message="tmIRPSystem:initiateTestsFault"/>
+  </operation>
+  <operation name="terminateTests">
+    <input message="tmIRPSystem:terminateTestsRequest"/>
+    <output message="tmIRPSystem:terminateTestsResponse"/>
+    <fault name="terminateTestsFault" message="tmIRPSystem:terminateTestsFault"/>
+  </operation>
+</portType>
+<portType name="TMIRPMonitorOperations">
+  <operation name="monitorTest">
+    <input message="tmIRPSystem:monitorTestRequest"/>
+    <output message="tmIRPSystem:monitorTestResponse"/>
+    <fault name="monitorTestFault" message="tmIRPSystem:monitorTestFault"/>
+  </operation>
+</portType>
+<binding name="TMIRPControlOperations" type="tmIRPSystem:TMIRPControlOperations">
+  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+  <operation name="initiateTests">
+
+```
+
+```
+
+    <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#initiateTests" style="document"/>
+    <input>
+      <soap:body use="literal"/>
+    </input>
+    <output>
+      <soap:body use="literal"/>
+    </output>
+    <fault name="initiateTestsFault">
+      <soap:fault name="initiateTestsFault" use="literal"/>
+    </fault>
+  </operation>
+  <operation name="terminateTests">
+    <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#terminateTests"
+style="document"/>
+    <input>
+      <soap:body use="literal"/>
+    </input>
+    <output>
+      <soap:body use="literal"/>
+    </output>
+    <fault name="terminateTestsFault">
+      <soap:fault name="terminateTestsFault" use="literal"/>
+    </fault>
+  </operation>
+</binding>
+<binding name="TMIRPMonitorOperations" type="tmIRPSystem:TMIRPMonitorOperations">
+  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+  <operation name="monitorTest">
+    <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#monitorTest" style="document"/>
+    <input>
+      <soap:body use="literal"/>
+    </input>
+    <output>
+      <soap:body use="literal"/>
+    </output>
+    <fault name="monitorTestFault">
+      <soap:fault name="monitorTestFault" use="literal"/>
+    </fault>
+  </operation>
+</binding>
+<service name="TMIRPService">
+  <port name="TMIRPControlOperationsPort" binding="tmIRPSystem:TMIRPControlOperations">
+    <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPControl"/>
+  </port>
+  <port name="TMIRPMonitorOperationsPort" binding="tmIRPSystem:TMIRPMonitorOperations">
+    <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.326#TMIRPMonitor"/>
+  </port>
+  <port name="GenericIRP" binding="genericIRPSystem:GenericIRPBinding">
+    <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRP"/>
+  </port>
+  <port name="NotificationIRPNtfPort" binding="ntfIRPNtfSystem:NotificationIRPNtf">
+    <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtf"/>
+  </port>
+</service>
+</definitions>
+
+```
+
+# --- Annex D (informative): Change history
+
+| Change history |       |           |     |     |                                                                                  |        |        |
+|----------------|-------|-----------|-----|-----|----------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                                                                  | Old    | New    |
+| 2010-09        | SA#49 | SP-100514 | --  | --  | Presentation to SA for Information and Approval                                  | ---    | 1.0.0  |
+| 2010-10        | --    | --        | --  | --  | Publication                                                                      | 1.0.0  | 10.0.0 |
+| 2010-12        | SA#50 | SP-100833 | 001 | 1   | Correcting the definition of parameter MORT in XML schema - Align with 32.322 IS | 10.0.0 | 10.1.0 |
+

marked/Rel-10/32_series/32331/raw.md

@@ -0,0 +1,288 @@
+
+
+# Keywords UMTS, management, alarm 3GPP TS 32.331 V10.0.0 (2011-03)
+
+*Technical Specification*
+
+## <sup>3GPP</sup> **3rd Generation Partnership Project;** **Technical Specification Group Services and System Aspects;** **Telecommunication management;** ~~Notification Leg (NL) Integration Reference Point (IRP);~~
+
+![LTE logo with '4ADVANCED' text above the 'e'](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo with '4ADVANCED' text above the 'e'
+
+~~3GPP support office address:~~  
+~~655 Route des Lucioles - Sophia Antipolis~~  
+~~Valbonne - FRANCE~~  
+~~Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16~~
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon below the 'P'](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+3GPP logo with a signal icon below the 'P'
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- 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 Notification log Management concept.....                                     | 6         |
+| 4.1 Notification Log Management .....                                          | 6         |
+| 4.2 Detection of the Notification Log state .....                              | 7         |
+| 4.3 Notification Log / Notification Log Record Retrieval .....                 | 7         |
+| 4.4 Notification Log Full Action.....                                          | 7         |
+| 5 Notification log IRP requirements .....                                      | 8         |
+| 5.1 Management of Logging/Log Records .....                                    | 8         |
+| 5.2 Information contained in Notification Log / Notification Log Records ..... | 8         |
+| 5.3 Notifications emitted by Notification Log IRP .....                        | 8         |
+| 5.4 Retrieval of Notification Log Records .....                                | 8         |
+| 5.5 Exporting Notification Log Records .....                                   | 9         |
+| 5.6 Overview of IRPs related to Notification Log IRP .....                     | 9         |
+| <b>Annex A (informative): Bibliography .....</b>                               | <b>10</b> |
+| Annex B (informative): Change history.....                                     | 11        |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced for the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.331 "Notification Log (NL) Integration Reference Point (IRP); Requirements"**
+- TS 32.332 "Notification Log (NL) (NL) Integration Reference Point (IRP); Information Service (IS)"
+- TS 32.336 "Notification Log (NL) Integration Reference Point (IRP): Solution Sets (SS)".
+
+The present document describes the requirements and information model necessary for Telecommunications Management (TM). The TM principles and TM architecture are specified in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2] respectively.
+
+A communications system is composed of a multitude of Network Elements (NE) of various types and, typically, different vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users' communication requirements.
+
+The occurrence of faults in an NE may cause deterioration or loss of this NE's function. Fault Management is the functional area, which allows the operator to detect the occurrence of faults in the network in real-time. Configuration Management and Performance Management are two more functional areas, which require the operator to be alerted to certain conditions in the network.
+
+A standard general-purpose mechanism for the management of Notification Logs containing selected or all notifications from the network is required to provide an ability to perform historical analysis on faults and conditions, which occurred in the network. The TS 32.33x-series constituting the Notification Log IRP, sets forth such a mechanism - and the present document contains the concept and IRP requirements definition.
+
+# --- 1 Scope
+
+The present document specifies overall requirements for Notification Log Management over Itf-N.
+
+Clause 4 provides the Notification Log Management concept for the manipulation of Notification Logs and the retrieval of notifications selected for logging.
+
+Clause 5 of the present document defines the functional requirements for the Notification Log IRP, for the purpose of Notification Log Management, as seen from a Network Manager (NM) through Itf-N. The Itf-N is fully standardized so as to connect systems of any vendor to an NM via this interface.
+
+# --- 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.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.662: "Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS)".
+- [5] 3GPP TS 32.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault management requirements".
+- [6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [7] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
+- [8] ITU-T Recommendation X.735: "Information technology - Open Systems Interconnection - Systems Management: Log control function".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Alarm:** defined in 3GPP TS 32.111-1 [5].
+
+**Alarm Notification:** defined in 3GPP TS 32.111-1 [5].
+
+**Event:** defined in 3GPP TS 32.111-1 [5].
+
+**Fault:** defined in 3GPP TS 32.111-1 [5].
+
+**Notification:** defined in 3GPP TS 32.111-1 [5].
+
+**Notification Log:** managed resource in which the notifications are stored
+
+Notifications logs contain Notification Log Records. Notification Log may represent a physical or a logical/virtual storage, and which is not apparent to an IRPManager.
+
+**Notification Log Record:** records track information about when a particular notification was entered into the Notification Log and the details of the notification
+
+Each Notification Log Record is associated with one notification, where a notification may be an alarm or an event.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                             |
+|------|-----------------------------|
+| COTS | Commercial Off The Shelf    |
+| EM   | Element Manager             |
+| IRP  | Integration Reference Point |
+| LM   | Log Management              |
+| NE   | Network Element             |
+| NM   | Network Manager             |
+| OS   | Operations System           |
+
+# --- 4 Notification log Management concept
+
+A general-purpose Notification Logging mechanism is required to hold notifications related to different functional areas in the network.
+
+Any Notification Log must, at any one point in time, be capable of holding fault management alarms, configuration management events, performance management events, and event log management events. A log is capable of capturing all semantics carried in a notification.
+
+Only those requirements covered by clause 5 and as applicable to the Notification Log IRP IS shall be considered as valid requirements for compliance to the standard defined by the present document.
+
+## 4.1 Notification Log Management
+
+Notification logs are resources in a communications network. An operator needs to be able to create Notification Logs, delete Notification Logs, query Notification Logs and to delete records. To allow an operator to do this a Notification Log management framework needs to be in place.
+
+The following aspects for Notification Log Management are derived from ITU-T Recommendation X.735 [8]:
+
+- The definition of a flexible Notification Log control service, which will allow selection of Notification Log records that are to be logged by a management system (NMs or EMs) in a Notification Log or a particular Notification Log.
+- The ability for a client system to modify the criteria used in logging notification records.
+- The ability for a client system to determine whether the logging characteristics were modified or whether notifications log records has been lost.
+- Specification of a mechanism to enable Notification Logging to be suspended and subsequently to be resumed.
+- The ability for a client system to retrieve and delete Notification Log records.
+- The ability for a client system to create and delete those Notification Logs.
+- The ability to log partial notifications.
+
+Another aspect is listed below:
+
+- Ability to export a log to an industry standard format such as XML.
+
+Such an export facility would allow the analysis and reporting of logs to be carried out by COTS tools.
+
+## 4.2 Detection of the Notification Log state
+
+The Notification Log management system must notify all interested OS about its current state. An event-based approach is used to update OSs on the current state of the Notification Log.
+
+To facilitate the notification of attribute or state changes, a Notification Log has the capability to generate such events, which all OSs may subscribe to via the Notification IRP 3GPP TS 32.302 [3].
+
+The Notification Log management system may also emit Notification Log creation and log deletion notifications to signal the creation or deletion of a particular log. Again all interested OSs may subscribe via 3GPP TS 32.302 [3] to receive such notifications.
+
+To notify OSs about the loss or imminent loss of Notification Log records, the system is able to emit capacity threshold alarms that alert the subscribed OSs that a capacity threshold has been crossed in a particular Notification Log. This threshold value may indicate that the Notification Log is full and incoming notifications shall be dealt with in a predetermined manner set by an operator.
+
+The system may emit other events to notify an OS of the completion of an I/O intensive operation, such as deletion of Notification Log records, or the exporting of a Notification Log.
+
+## 4.3 Notification Log / Notification Log Record Retrieval
+
+An OS may retrieve Notification Log records either by querying a particular Notification Log with a filter, or by exporting a Notification Log, or a particular section of a Notification Log. Exporting a Notification Log utilizing the File Transfer IRP (3GPP TS 32.342 [7]) allows the OS to retrieve the Notification Log in a standard format such as XML. An XML data format may be used by generic XML utilities and next generation web browsers for analysis and reporting. XML is a widely accepted data interchange format, and its application to Notification Log management provides an ease of use unparalleled in traditional Notification Log systems.
+
+## 4.4 Notification Log Full Action
+
+The OS must be able to set the behaviour of a Notification Log that becomes full. ITU-T Recommendation X.735 [8] recommends two actions, halt and wrap.
+
+- A Notification Log that halts when full implies the agent should notify the OS by way of generating a capacity threshold alarm. New notifications, which should be logged according to the Notification Log's filter criteria, are discarded. This behaviour implies that the old Notification Log records are more important than new ones.
+- An OS can set the behaviour of the Notification Log to wrap when full. In this case the Notification Log behaves like a circular buffer, replacing the oldest Notification Log records with new ones. This behaviour implies that new Notification Log records are more important than old Notification Log records.
+
+# --- 5 Notification log IRP requirements
+
+## 5.1 Management of Logging/Log Records
+
+The IRPManager may request the IRPAgent to start or stop logging of notifications, or the IRPAgent may initiate logging by itself (an IRPAgent may log notifications independent from IRPManager initiated logging). Upon start of Notification Logging, the IRPAgent shall generate an identifier for it. All Notification Logging activity identifiers must be unique within the IRPAgent. The IRPAgent may alert all interested IRPManagers about the creation of the new Notification Logging activity. An initiating IRPManager may request the IRPAgent to stop logging of notifications, and the IRPAgent may then alert all interested IRPManagers about the stop of this Notification Logging activity.
+
+Deletion of Notification Log Records is in the realm of the IRPAgent, where two methods should apply:
+
+- Notification Log Full Action: the IRPAgent should apply the "circular buffer" or "wrap" method (see also clause 4.4); a one-time Notification Log threshold capacity alarm (e.g. at 98 % full) will indicate to IRPManagers that the IRPAgent is applying this method currently, while clearance will be indicated as well (e.g. at 90 % full)
+- Maintenance: the IRPAgent may delete Notification Log Records from a Notification Log.
+
+The IRPManager may request a list of all IRPManager initiated or IRPAgent initiated log activities currently managed by the IRPAgent. The IRPAgent returns a list of Notification Log identifiers to the IRPManager. The IRPManager may then use these identifiers to query or export a log or parts of it.
+
+## 5.2 Information contained in Notification Log / Notification Log Records
+
+A Notification Log may be created by the IRPAgent upon request of the IRPManager, or by the IRPAgent itself. A Notification Log may represent a physical or a logical/virtual storage, and which is not apparent to an IRPManager.
+
+All Notifications available at the IRPAgent for potential transmission over Itf-N shall be logged if requested by a start log request, irrespective of the subscriptions and filter settings of IRPManagers.
+
+The Notification Log Record will contain a notification as specified by 3GPP TS 32.302 [3]. The Notification Log Record is time-stamped, allowing the operator to determine the time at which the Notification Log Record was added to the Notification Log.
+
+The IRPAgent should avoid logging the following duplicated or recursive notifications
+
+- Logging of notifications resulting from asynchronous alarm synchronization (3GPP TS 32.111-2 [6]).
+
+## 5.3 Notifications emitted by Notification Log IRP
+
+LM reports are forwarded in real-time to the IRPManager via appropriate filtering located in the IRPAgents. The Notification Log IRP reports consist of:
+
+- Notification log starting and stopping reports, upon the activation/deactivation of a Notification Logging activity.
+- Notification log capacity threshold reached report, and notification when logging has resumed.
+
+## 5.4 Retrieval of Notification Log Records
+
+The IRPManager will request the IRPAgent to query the notifications log based on filter criteria. The IRPAgent will then return the Notification Log Records that match the IRPManager's filter criteria. Each Notification Log Record returned will contain a notification that the IRPManager is interested in.
+
+## 5.5 Exporting Notification Log Records
+
+The IRPManager may request the IRPAgent to export either a Notification Log or part thereof. In this case the IRPManager will supply a filter criteria and Notification Log Records matching that criteria will be exported to a standard format such as XML defined by the Notification Log IRP. The IRPAgent will provide this export file to an IRPManager utilizing the File Transfer IRP (3GPP TS 32.342 [7]).
+
+## 5.6 Overview of IRPs related to Notification Log IRP
+
+The Itf-N interface relies on the Notification IRP 3GPP TS 32.302 [3] as well as File Transfer IRP (3GPP TS 32.342 [7]), and serves a number of IRPs. The basic structure of the IRPs is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+For the purpose of LM, the following IRPs are served:
+
+- Alarm IRP: Information Service 3GPP TS 32.111-2 [6].
+- Kernel CM IRP: Information Service 3GPP TS 32.662 [4].
+- All other IRP's emitting notifications.
+
+# --- Annex A (informative): Bibliography
+
+- World Wide Web Consortium: [www.w3c.org](http://www.w3c.org).
+
+# --- Annex B (informative): Change history
+
+| Change history |       |           |    |     |                                                                                                                    |       |        |
+|----------------|-------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                                                                                                    | Old   | New    |
+| Sep 2003       | S 22  | SP-030638 | -- | --  | Submitted to TSG SA#22 for Information                                                                             | 1.0.0 |        |
+| Mar 2004       | S 23  | SP-040122 | -- | --  | Submitted to TSG SA#23 for Approval                                                                                | 2.0.0 | 6.0.0  |
+| Jun 2005       | --    | --        | -- | --  | Introduction update : added 32.335 new TS-family member                                                            | 6.0.0 | 6.0.1  |
+| Jun 2007       | SA_36 | --        | -- | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | 6.0.1 | 7.0.0  |
+| Dec 2008       | SA 42 | --        | -- | --  | Upgrade to Release 8                                                                                               | 7.0.0 | 8.0.0  |
+| Dec 2009       | -     | -         | -  | -   | Update to Rel-9 version (MCC)                                                                                      | 8.0.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -  | -   | Update to Rel-10 version (MCC)                                                                                     | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32332/raw.md

@@ -0,0 +1,1049 @@
+
+
+# Keywords UMTS, Management 3GPP TS 32.332 V10.0.0 (2011-03)
+
+*Technical Specification*
+
+**3GPP**  
+**3rd Generation Partnership Project;**  
+Postal address  
+**Technical Specification Group Services and System Aspects;**  
+**Telecommunication management;**  
+3GPP support office address  
+150 Route des Lucioles - 69121 Saint-Fons  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16  
+**Identification Log (NL) Integration Reference Point (IRP);**  
+Informa
+
+![LTE logo with '4 ADVANCED' text above the 'e'](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+LTE logo with '4 ADVANCED' text above the 'e'
+
+Internet  
+<http://www.3gpp.org>
+
+![3GPP logo with a signal icon below the 'P'](390120de4fe440c42fea8154fcaad334_img.jpg)
+
+3GPP logo with a signal icon below the 'P'
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# --- Contents
+
+|                                                               |    |
+|---------------------------------------------------------------|----|
+| Foreword .....                                                | 6  |
+| Introduction .....                                            | 6  |
+| 1 Scope.....                                                  | 7  |
+| 2 References.....                                             | 7  |
+| 3 Definitions and abbreviations .....                         | 7  |
+| 3.1 Definitions.....                                          | 7  |
+| 3.2 Abbreviations .....                                       | 8  |
+| 4 System overview .....                                       | 8  |
+| 4.2 Compliance rules.....                                     | 8  |
+| 5 Information Object Classes (IOCs).....                      | 9  |
+| 5.1 Information entities imported and local labels.....       | 9  |
+| 5.2 Class diagram .....                                       | 10 |
+| 5.2.1 Attributes and relationships.....                       | 10 |
+| 5.2.2 Inheritance .....                                       | 11 |
+| 5.3 Information Object Class (IOC) definitions.....           | 12 |
+| 5.3.1 NLIRP.....                                              | 12 |
+| 5.3.1.1 Definition .....                                      | 12 |
+| 5.3.1.2 Attributes .....                                      | 12 |
+| 5.3.2 Log.....                                                | 12 |
+| 5.3.2.1 Definition .....                                      | 12 |
+| 5.3.2.2 Attributes .....                                      | 12 |
+| 5.3.2.3 State diagram .....                                   | 13 |
+| 5.3.3 LogRecord .....                                         | 13 |
+| 5.3.3.1 Definition .....                                      | 13 |
+| 5.4 Information relationship definitions.....                 | 14 |
+| 5.4.1 Relation-nLIRP-log (M).....                             | 14 |
+| 5.4.1.1 Definition .....                                      | 14 |
+| 5.4.1.2 Role.....                                             | 14 |
+| 5.4.1.3 Constraint.....                                       | 14 |
+| 5.4.2 Relation-log-logRecord (M).....                         | 14 |
+| 5.4.2.1 Definition .....                                      | 14 |
+| 5.4.2.2 Role.....                                             | 14 |
+| 5.4.2.3 Constraint.....                                       | 14 |
+| 5.4.3 Relation-logRecord-notificationIRPNotification (M)..... | 15 |
+| 5.4.3.1 Definition .....                                      | 15 |
+| 5.4.3.2 Role.....                                             | 15 |
+| 5.4.3.3 Constraint.....                                       | 15 |
+| 5.5 Information attribute definition.....                     | 16 |
+| 5.5.1 Definition and legal values.....                        | 16 |
+| 5.5.2 Constraints .....                                       | 17 |
+| 6 Interface definition .....                                  | 17 |
+| 6.1 Class diagram.....                                        | 17 |
+| 6.2 Generic rules .....                                       | 18 |
+| 6.3 NLIRPOperations_1 Interface (M) .....                     | 18 |
+| 6.3.1 Operation subscribeLog (M) .....                        | 18 |
+| 6.3.1.1 Definition .....                                      | 18 |
+| 6.3.1.2 Input parameters .....                                | 18 |
+| 6.3.1.3 Output parameters.....                                | 19 |
+| 6.3.1.4 Pre-condition.....                                    | 19 |
+| 6.3.1.5 Post-condition .....                                  | 19 |
+| 6.3.1.6 Exceptions.....                                       | 19 |
+| 6.3.2 Operation unsubscribeLog (M) .....                      | 20 |
+| 6.3.2.1 Definition .....                                      | 20 |
+
+|           |                                                                 |    |
+|-----------|-----------------------------------------------------------------|----|
+| 6.3.2.2   | Input parameters .....                                          | 20 |
+| 6.3.2.3   | Output parameters.....                                          | 20 |
+| 6.3.2.4   | Pre-condition.....                                              | 20 |
+| 6.3.2.5   | Post-condition .....                                            | 20 |
+| 6.3.2.6   | Exceptions.....                                                 | 20 |
+| 6.3       | Operation <code>exportLogRecords</code> (O) .....               | 21 |
+| 6.3.3.1   | Definition .....                                                | 21 |
+| 6.3.3.2   | Input parameters .....                                          | 21 |
+| 6.3.3.3   | Output parameters.....                                          | 21 |
+| 6.3.3.4   | Pre-condition.....                                              | 21 |
+| 6.3.3.5   | Post-condition .....                                            | 21 |
+| 6.3.3.6   | Exceptions.....                                                 | 21 |
+| 6.3.4     | Operation <code>getLogRecords</code> (O) .....                  | 22 |
+| 6.3.4.1   | Definition .....                                                | 22 |
+| 6.3.4.2   | Input parameters .....                                          | 22 |
+| 6.3.4.3   | Output parameters.....                                          | 22 |
+| 6.3.4.4   | Pre-condition.....                                              | 22 |
+| 6.3.4.5   | Post-condition .....                                            | 22 |
+| 6.3.4.6   | Exceptions.....                                                 | 22 |
+| 6.4       | NLIRPOperations_2 Interface (O) .....                           | 23 |
+| 6.4.1     | Operation <code>getLogSubscriptionIds</code> (M) .....          | 23 |
+| 6.4.1.1   | Definition .....                                                | 23 |
+| 6.4.1.2   | Input parameters .....                                          | 23 |
+| 6.4.1.3   | Output parameters.....                                          | 23 |
+| 6.4.1.4   | Pre-condition.....                                              | 23 |
+| 6.4.1.5   | Post-condition .....                                            | 23 |
+| 6.4.1.6   | Exceptions.....                                                 | 23 |
+| 6.4.2     | Operation <code>getLogSubscriptionStatus</code> (M).....        | 24 |
+| 6.4.2.1   | Definition .....                                                | 24 |
+| 6.4.2.2   | Input parameters .....                                          | 24 |
+| 6.4.2.3   | Output parameters.....                                          | 24 |
+| 6.4.2.4   | Pre-condition.....                                              | 24 |
+| 6.4.2.5   | Post-condition .....                                            | 24 |
+| 6.4.2.6   | Exceptions.....                                                 | 24 |
+| 6.5       | NLIRPNotifications_1 Interface (M).....                         | 25 |
+| 6.5.1     | Notification <code>notifyLogSubscribed</code> (M) .....         | 25 |
+| 6.5.1.1   | Definition .....                                                | 25 |
+| 6.5.1.2   | Input Parameters .....                                          | 25 |
+| 6.5.1.3   | Triggering Event.....                                           | 25 |
+| 6.5.1.3.1 | From-state.....                                                 | 25 |
+| 6.5.1.3.2 | To-state.....                                                   | 25 |
+| 6.5.2     | Notification <code>notifyLogUnsubscribed</code> (M) .....       | 26 |
+| 6.5.2.1   | Definition .....                                                | 26 |
+| 6.5.2.2   | Input Parameters .....                                          | 26 |
+| 6.5.2.3   | Triggering Event.....                                           | 26 |
+| 6.5.2.3.1 | From-state.....                                                 | 26 |
+| 6.5.2.3.2 | To-state.....                                                   | 26 |
+| 6.6       | NLIRPNotifications_2 Interface (O).....                         | 27 |
+| 6.6.1     | Notification <code>notifyOccupancyLevelCrossed</code> (M) ..... | 27 |
+| 6.6.1.1   | Definition .....                                                | 27 |
+| 6.6.1.2   | Input Parameters .....                                          | 27 |
+| 6.6.1.3   | Triggering Event.....                                           | 27 |
+| 6.6.1.3.1 | From-state.....                                                 | 27 |
+| 6.6.1.3.2 | To-state.....                                                   | 27 |
+| 6.6.2     | Notification <code>notifyLoggingResumed</code> (O) .....        | 28 |
+| 6.6.2.1   | Definition .....                                                | 28 |
+| 6.6.2.2   | Input Parameters .....                                          | 28 |
+| 6.6.2.3   | Triggering Event.....                                           | 28 |
+| 6.6.2.3.1 | From-state.....                                                 | 28 |
+| 6.6.2.3.2 | To-state.....                                                   | 28 |
+
+Annex A (informative): Change history..... 29
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.331 "Notification Log (NL) Integration Reference Point (IRP): Requirements"
+- TS 32.332 "Notification Log (NL) Integration Reference Point (IRP): Information Service (IS)"**
+- TS 32.336 "Notification Log (NL) Integration Reference Point (IRP); Solution Set (SS) definitions"
+
+The present document describes the requirements and information model necessary for Telecommunication Management (TM). The TM principles and TM architecture are specified in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+A communications system is composed of a multitude of Network Elements (NE) of various types and, typically, different vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users' communication requirements.
+
+The occurrence of faults in an NE may cause deterioration or loss of this NE's function. Fault Management is the functional area, which allows the operator to detect the occurrence of faults in the network in real-time. Configuration Management and Performance Management are two more functional areas, which require the operator to be alerted to certain conditions in the network.
+
+A standard general-purpose mechanism for the management of logs containing selected notifications from the network is required to provide an ability to perform historical analysis on faults and conditions, which occurred in the network. The TS 32.33x-series, constituting the Notification log IRP, sets forth such a mechanism - and the present document contains the IS definition.
+
+# --- 1 Scope
+
+The present document specifies the Information Service for the Notification Log Integration Reference Point (NLIRP) as it applies to Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+# --- 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.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [5] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [6] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [7] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements".
+- [8] 3GPP TS 32.342 "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
+- [9] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.111-2 [5] and 3GPP TS 32.331 [7] apply.
+
+**notification category:** it refers to the set of notifications of one 3GPP IRP Information Service specification  
+A Notification Category is identified by the name of the IRP specification and the IRP specification version number.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                              |
+|-------|----------------------------------------------|
+| DN    | Distinguished Name                           |
+| EM    | Element Manager                              |
+| FT    | File Transfer                                |
+| IOC   | Information Object Class                     |
+| IRP   | Integration Reference Point                  |
+| M     | Mandatory                                    |
+| NE    | Network Element                              |
+| NL    | Notification Log                             |
+| NLIRP | Notification Log Integration Reference Point |
+| NM    | Network Manager                              |
+| O     | Optional                                     |
+| UML   | Unified Modelling Language                   |
+
+# 4 System overview
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [9] clause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below
+
+![Figure 4.1: System Context A diagram](0236eff05bcb8f3a343ea7933aaa306b_img.jpg)
+
+The diagram shows a Network Manager (NM) containing an IRPManager, connected via a solid line to an Element Manager (EM) containing an IRPAgent. The IRPAgent is connected via a dotted line to multiple Network Elements (NEs). A vertical dashed line separates the NM and EM. Below the dashed line, an arrow labeled 'Itf-N' points to a list of three Integration Reference Points: Notification IRP, Notification Log IRP, and File Transfer IRP.
+
+Figure 4.1: System Context A diagram
+
+Figure 4.1: System Context A
+
+![Figure 4.2: System Context B diagram](9791722d75115ddcc599b07d7bc35d73_img.jpg)
+
+The diagram shows a Network Manager (NM) containing an IRPManager, connected via a solid line to a Network Element (NE) containing an IRPAgent. A vertical dashed line separates the NM and NE. Below the dashed line, an arrow labeled 'Itf-N' points to a list of three Integration Reference Points: Notification IRP, Notification Log IRP, and File Transfer IRP.
+
+Figure 4.2: System Context B diagram
+
+Figure 4.2: System Context B
+
+## 4.2 Compliance rules
+
+For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for *operations, notifications and parameters* (of operations and notifications) please refer to 3GPP TS 32.102 [2].
+
+# 5 Information Object Classes (IOCs)
+
+## 5.1 Information entities imported and local labels
+
+| Label reference                                                           | Local label                 |
+|---------------------------------------------------------------------------|-----------------------------|
+| 3GPP TS 32.622 [4], information object class, Top                         | Top                         |
+| 3GPP TS 32.312 [6], information object class, ManagedGenericIRP           | ManagedGenericIRP           |
+| 3GPP TS 32.342 [8], information object class, FileTransferIRP             | FileTransferIRP             |
+| 3GPP TS 32.302 [3], information object class, NotificationIRP             | NotificationIRP             |
+| 3GPP TS 32.302 [3], information object class, NotificationIRPNotification | NotificationIRPNotification |
+
+## 5.2 Class diagram
+
+### 5.2.1 Attributes and relationships
+
+This clause introduces the set of IOCs that encapsulate information within the IRP Agent. The intent is to identify the information required for NLIRP operations and notification. This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes.
+
+![UML Class diagram showing NLIRP, Log, LogRecord, and NotificationIRPNotification classes and their relationships.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+```
+classDiagram
+    class NLIRP {
+        maxLogs
+    }
+    class Log {
+        logSubscriptionId
+        loggingEndTime
+        maxSize
+        currentSize
+        creationTime
+        logState
+        logRecordCount
+        notificationCategories
+        filter
+        logFullAction
+        occupancyLevels
+        logManagerToken
+    }
+    class LogRecord {
+        logRecordId
+        logRecordContent
+    }
+    class NotificationIRPNotification {
+        notificationId
+        eventTime
+        systemDN
+        notificationType
+    }
+
+    NLIRP "1" *-- "0..*" Log : <<names>>
+    Log "1" *-- "0..*" LogRecord : +logRecord
+    LogRecord "1" -- "1" NotificationIRPNotification : relation-logRecord-notification
+```
+
+The diagram illustrates the Information Object Class (IOC) structure. It consists of four classes: **NLIRP**, **Log**, **LogRecord**, and **NotificationIRPNotification**. **NLIRP** has an attribute **maxLogs**. **Log** has attributes: **logSubscriptionId**, **loggingEndTime**, **maxSize**, **currentSize**, **creationTime**, **logState**, **logRecordCount**, **notificationCategories**, **filter**, **logFullAction**, **occupancyLevels**, and **logManagerToken**. **LogRecord** has attributes: **logRecordId** and **logRecordContent**. **NotificationIRPNotification** (from TS32.302) has attributes: **notificationId**, **eventTime**, **systemDN**, and **notificationType**. Relationships: **NLIRP** has a composition relationship with **Log** (multiplicity 1 to 0..\*, role name **<<names>>**). **Log** has a composition relationship with **LogRecord** (multiplicity 1 to 0..\*, role name **+logRecord**). **LogRecord** has a bidirectional association with **NotificationIRPNotification** (multiplicity 1 to 1, role name **relation-logRecord-notification**).
+
+UML Class diagram showing NLIRP, Log, LogRecord, and NotificationIRPNotification classes and their relationships.
+
+Figure 5.1: Information Object Class (IOC) UML diagram
+
+To change: change logid, add logrecordcontent, remove logrecordsource.
+
+### 5.2.2 Inheritance
+
+![UML diagram showing Information Object Class (IOC) inheritance. ManagedGenericIRP is the root class. NLIRP inherits from ManagedGenericIRP. Top (from TS32.622) is a base class for Log and LogRecord. Log and LogRecord inherit from Top.](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+```
+classDiagram
+    class ManagedGenericIRP {
+        <<InformationObjectClass>>
+        (from TS32.312)
+    }
+    class NLIRP {
+        <<InformationObjectClass>>
+        maxLogs
+    }
+    class Top {
+        <<InformationObjectClass>>
+        Top
+        (from TS32.622)
+        objectClass
+        objectInstance
+    }
+    class Log {
+        <<InformationObjectClass>>
+        Log
+        logSubscriptionId
+        loggingEndTime
+        maxSize
+        currentSize
+        creationTime
+        logState
+        logRecordCount
+        notificationCategories
+        filter
+        logFullAction
+        occupancyLevels
+        logManagerToken
+    }
+    class LogRecord {
+        <<InformationObjectClass>>
+        LogRecord
+        logRecordId
+        logRecordContent
+    }
+    ManagedGenericIRP <|-- NLIRP
+    Top <|-- Log
+    Top <|-- LogRecord
+```
+
+The diagram illustrates the inheritance hierarchy for Information Object Classes (IOCs). At the top is the **ManagedGenericIRP** class (from TS32.312). Below it, the **NLIRP** class (an **<<InformationObjectClass>>**) inherits from **ManagedGenericIRP** and has a **maxLogs** attribute. To the right, the **Top** class (an **<<InformationObjectClass>>** from TS32.622) has **objectClass** and **objectInstance** attributes. Below **Top**, the **Log** class (an **<<InformationObjectClass>>**) and the **LogRecord** class (an **<<InformationObjectClass>>**) both inherit from it. The **Log** class has attributes: **logSubscriptionId**, **loggingEndTime**, **maxSize**, **currentSize**, **creationTime**, **logState**, **logRecordCount**, **notificationCategories**, **filter**, **logFullAction**, **occupancyLevels**, and **logManagerToken**. The **LogRecord** class has attributes: **logRecordId** and **logRecordContent**.
+
+UML diagram showing Information Object Class (IOC) inheritance. ManagedGenericIRP is the root class. NLIRP inherits from ManagedGenericIRP. Top (from TS32.622) is a base class for Log and LogRecord. Log and LogRecord inherit from Top.
+
+Figure 5.2: Information Object Class (IOC) inheritance UML diagram
+
+## 5.3 Information Object Class (IOC) definitions
+
+### 5.3.1 NLIRP
+
+#### 5.3.1.1 Definition
+
+LogIRP is the representation of the notification log management capabilities specified by the present document. This IOC inherits from ManagedGenericIRP IOC specified in TS 32.312 [6].
+
+#### 5.3.1.2 Attributes
+
+| Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
+|----------------|-------------------|----------------|-----------------|
+| maxLogs        | O                 | M              | -               |
+
+### 5.3.2 Log
+
+#### 5.3.2.1 Definition
+
+The Log IOC is the representation of a Notification Log.
+
+#### 5.3.2.2 Attributes
+
+| Attribute name         | Support Qualifier | Read Qualifier | Write Qualifier |
+|------------------------|-------------------|----------------|-----------------|
+| logSubscriptionId      | M                 | M              | -               |
+| loggingEndTime         | O                 | M              | -               |
+| logManagerToken        | O                 | -              | -               |
+| maxSize                | O                 | M              | -               |
+| currentSize            | O                 | M              | -               |
+| creationTime           | O                 | M              | -               |
+| logState               | M                 | M              | -               |
+| logRecordCount         | O                 | M              | -               |
+| notificationCategories | O                 | M              | -               |
+| filter                 | O                 | M              | -               |
+| logFullAction          | M                 | M              | -               |
+| occupancyLevels        | M                 | M              | -               |
+
+#### 5.3.2.3 State diagram
+
+![State diagram for Notification Log showing four states: logging, logWrapping, logHalted, and stopped. Transitions include startLog, occupancyLevelChanged, logFull (wrap/halt), stopLog (lifeTimeExpired), and logNotFull (notifyLoggingResumed).](007b053fe94a8348f75128a584503fd0_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> logging : startLog
+    logging --> logging : occupancyLevelChanged
+    logging --> logWrapping : logFull[ logFullAction==wrap ]
+    logging --> stopped : stopLog || logLifeTimeExpired
+    logging --> logHalted : logFull[ logFullAction==halt ]
+    logWrapping --> logging : stopLog || logLifeTimeExpired
+    logWrapping --> stopped : stopLog || logLifeTimeExpired
+    logHalted --> logging : logNotFull / notifyLoggingResumed()
+    logHalted --> stopped : stopLog || logLifeTimeExpired
+    stopped --> [*]
+  
+```
+
+State diagram for Notification Log showing four states: logging, logWrapping, logHalted, and stopped. Transitions include startLog, occupancyLevelChanged, logFull (wrap/halt), stopLog (lifeTimeExpired), and logNotFull (notifyLoggingResumed).
+
+**Figure 5.3: State diagram for Notification Log**
+
+The disposition of a log that has been stopped, that is, whether the log remains visible across the Itf-N, is left as vendor specific functionality. The time of the deletion of logs is vendor specific.
+
+### 5.3.3 LogRecord
+
+#### 5.3.3.1 Definition
+
+The LogRecord IOC is the representation of an individual Notification Log Record.
+
+| Attribute name   | Support Qualifier | Read Qualifier | Write Qualifier |
+|------------------|-------------------|----------------|-----------------|
+| logRecordId      | M                 | M              | –               |
+| logRecordContent | O                 | M              | –               |
+
+## 5.4 Information relationship definitions
+
+### 5.4.1 Relation-nLIRP-log (M)
+
+#### 5.4.1.1 Definition
+
+This represents the relationship between `NLIRP` and the `Log`.
+
+#### 5.4.1.2 Role
+
+| Name               | Definition                             |
+|--------------------|----------------------------------------|
+| <code>nLIRP</code> | It represents the <code>NLIRP</code> . |
+| <code>log</code>   | It represents the <code>Log</code> .   |
+
+#### 5.4.1.3 Constraint
+
+| Name                                 | Definition                                                                                                                              |
+|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| <code>uniqueLogSubscriptionId</code> | The log subscription id must be unique amongst all logs managed by a given <code>NLIRP</code> instance.                                 |
+| <code>uniqueLogManagerToken</code>   | The log manager token must be unique amongst all managers and logs utilizing logging services from a given <code>NLIRP</code> instance. |
+
+### 5.4.2 Relation-log-logRecord (M)
+
+#### 5.4.2.1 Definition
+
+This represents the relationship between `Log` and the `LogRecord`.
+
+#### 5.4.2.2 Role
+
+| Name                   | Definition                                 |
+|------------------------|--------------------------------------------|
+| <code>log</code>       | It represents the <code>Log</code> .       |
+| <code>logRecord</code> | It represents the <code>LogRecord</code> . |
+
+#### 5.4.2.3 Constraint
+
+| Name                           | Definition                                                                    |
+|--------------------------------|-------------------------------------------------------------------------------|
+| <code>uniqueLogRecordId</code> | The log record id must be unique amongst all logs records within a given log. |
+
+### 5.4.3 Relation-logRecord-notificationIRPNotification (M)
+
+#### 5.4.3.1 Definition
+
+This represents the relationship between `LogRecord` and the notification header represented by `NotificationIRPNotification`.
+
+#### 5.4.3.2 Role
+
+| Name                      | Definition                                                   |
+|---------------------------|--------------------------------------------------------------|
+| <code>logRecord</code>    | It represents the <code>LogRecord</code> .                   |
+| <code>notification</code> | It represents the <code>NotificationIRPNotification</code> . |
+
+#### 5.4.3.3 Constraint
+
+| Name                                          | Definition                                                                                                                                                            |
+|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logRecordIdRelatesNotificationId</code> | Within a given log, there is a one-to-one relationship between <code>Notification Id</code> and <code>Log Id</code> (as each notification can only be recorded once). |
+
+## 5.5 Information attribute definition
+
+### 5.5.1 Definition and legal values
+
+| Attribute Name         | Definition                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Legal Values                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| creationTime           | The time when the log is created.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | YYYYMMDDhhmmss                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| currentSize            | This attribute provides the number of bytes currently utilized by a given log. When taken in conjunction with maxSize, the amount of space remaining in the log can be determined.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Either:<br><ul style="list-style-type: none"> <li>zero</li> <li>a positive whole number</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                              |
+| filter                 | It specifies a filter constraint that IRPAgent shall use to filter notification of the category specified in notificationCategories parameter.<br>Support of time based filter is mandatory. Support of other filter constraints is optional.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Filter constraint grammar is SS dependent                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| logFullAction          | Indicate the action that will be taken by this instance of NLIRP when the Log.maxSize has been reached.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An ENUM that can have one of the following values:<br><ul style="list-style-type: none"> <li>wrap: The oldest LogRecord(s) in the Log, based on the log time, will be deleted to free resources for the logging of new LogRecord(s).</li> <li>halt: No more LogRecord(s) will be logged and all incoming events are discarded. LogRecord/s already in the Log will be retained.</li> </ul>                                                                                                      |
+| loggingEndTime         | Defines the date and time when the log stops logging.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | If log is created by IRPManager:<br><ul style="list-style-type: none"> <li>value provided by the IRP Manager - the IRP Agent may reject the value provided by the IRP Manager in case this value is excessive</li> <li>in case no value is provided by the IRP Manager then this value is set by the IRP Agent.</li> </ul><br>If log is created by IRPAgent:<br><ul style="list-style-type: none"> <li>value indicates date and time or</li> <li>value is expressed as "indefinite".</li> </ul> |
+| logManagerToken        | This attribute contains the token of a manager utilizing logging services from a given NLIRP instance, assigned by the IRPAgent.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | The value of this attribute must be unique amongst all managers and logs utilizing logging services from the given NLIRP instance.                                                                                                                                                                                                                                                                                                                                                              |
+| logRecordContent       | The notification information of a log record, excluding the notification header information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | The content format varies depending on the type of the notification.                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| logRecordCount         | The number of log records currently logged within a given log.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | positive whole number, including zero                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| logRecordId            | This attribute contains the id of a log record within a given log, assigned by the IRPAgent.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | The value of this attribute must be unique amongst all log record contained by a given log.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| logState               | Provides an indication of the current state of a specific log                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | An ENUM that can have one of the following values:<br><ul style="list-style-type: none"> <li>logging</li> <li>logFull</li> <li>stopped</li> </ul>                                                                                                                                                                                                                                                                                                                                               |
+| logSubscriptionId      | This attribute contains the id of a log subscription within a given NLIRP instance, assigned by the IRPAgent.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | The value of this attribute must be unique amongst all log subscriptions managed by a given NLIRP instance.                                                                                                                                                                                                                                                                                                                                                                                     |
+| maxLogs                | Defines the maximum number of logs that can be supported by a given Notification Log IRP, assigned by the IRPAgent.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Non-zero, positive whole number                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| maxSize                | This attribute defines the maximum number of bytes that may be utilized by a given log, assigned by the IRPAgent.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Either:<br><ul style="list-style-type: none"> <li>Non-zero, positive whole number</li> <li>Zero indicates no limit on the number of records is set by the IRPAgent (log full handling will provide limitation information)</li> </ul>                                                                                                                                                                                                                                                           |
+| notificationCategories | Specifies the notification categories that can be recorded within a given log - SET OF (name of IRP, version of IRP)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | It identifies one or more Notification Category (see also Definition in clause 3.1)                                                                                                                                                                                                                                                                                                                                                                                                             |
+| occupancyLevels        | Case Log.logFullAction == 'halt' and Log.maxSize is non-zero:<br><ul style="list-style-type: none"> <li>this attribute contains a list of 3 values fixed (determined by the IRPAgent and never changed) of percentage, of Log.maxLog</li> <li>the NLIRP will generate notifyOccupancyLevelCrossed to alert IRPManagers about the Log capacity currently used.</li> </ul><br>Case Log.logFullAction == 'wrap':<br><ul style="list-style-type: none"> <li>this attribute contains 1 value fixed (determined by the IRPAgent and never changed) of percentage of Log.maxLog</li> <li>the NLIRP will generate notifyOccupancyLevelCrossed to alert IRPManagers that the specified percentage of the capacity has been written to the wrapping Log.</li> </ul> | Case of 'halt': a set of 3 values.<br><br>Case of 'wrap': 1 value.                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+### 5.5.2 Constraints
+
+| Name                 | Definition                                                    |
+|----------------------|---------------------------------------------------------------|
+| inv_lastModifiedTime | Time indicated shall be greater than or equal to creationTime |
+| inv_logRecordCount   | Number indicated shall be less than or equal to maxSize       |
+
+# 6 Interface definition
+
+## 6.1 Class diagram
+
+![UML Class diagram showing NLIRP class and its interfaces and notifications.](16152cf1d84aea10848758f51a91ff6a_img.jpg)
+
+The diagram illustrates the class structure for NLIRP. At the top left is the **NLIRPOperations\_1** interface with methods `subscribeLog()`, `unsubscribeLog()`, `<<optional>> exportLogRecords()`, and `<<optional>> getLogRecords()`. A note above it states: "NLIRPOperations\_1 shall support either operation exportLogRecords or operation getLogRecords as mandatory." Below it is the **NLIRPOperations\_2** interface with methods `getLogSubscriptionIds()` and `getLogSubscriptionStatus()`. The **NLIRP** class (InformationObjectClass) has an attribute `maxLogs` and implements both interfaces. It has a `<<use>>` relationship with the **NLIRPNotifications\_1** notification (methods `notifyLogSubscribed()` and `notifyLogUnsubscribed()`) and a `<<may use>>` relationship with the **NLIRPNotifications\_2** notification (methods `notifyOccupancyLevelCrossed()` and `<<optional>> notifyLoggingResumed()`). The **FileTransferRP** (from TS32.342) and the **NotificationRP** (from TS32.302) are shown as agent-internal usages of the **NLIRP** class.
+
+```
+classDiagram
+    class NLIRPOperations_1 {
+        <<Interface>>
+        subscribeLog()
+        unsubscribeLog()
+        <<optional>> exportLogRecords()
+        <<optional>> getLogRecords()
+    }
+    class NLIRPOperations_2 {
+        <<Interface>>
+        getLogSubscriptionIds()
+        getLogSubscriptionStatus()
+    }
+    class NLIRP {
+        <<InformationObjectClass>>
+        maxLogs
+    }
+    class NLIRPNotifications_1 {
+        <<Notification>>
+        notifyLogSubscribed()
+        notifyLogUnsubscribed()
+    }
+    class NLIRPNotifications_2 {
+        <<Notification>>
+        notifyOccupancyLevelCrossed()
+        <<optional>> notifyLoggingResumed()
+    }
+    class FileTransferRP {
+        FileTransferRP (from TS32.342)
+    }
+    class NotificationRP {
+        <<InformationObjectClass>>
+        NotificationRP (from TS32.302)
+    }
+
+    NLIRP --|> NLIRPOperations_1
+    NLIRP --|> NLIRPOperations_2
+    NLIRP --> NLIRPNotifications_1 : <<use>>
+    NLIRP --> NLIRPNotifications_2 : <<may use>>
+    FileTransferRP --> NLIRP : <<agent-internal-usage>>
+    NotificationRP --> NLIRP : <<agent-internal-usage>>
+    NotificationRP --> NLIRPNotifications_1 : <<agent-internal-usage>>
+    NotificationRP --> NLIRPNotifications_2 : <<agent-internal-usage>>
+```
+
+UML Class diagram showing NLIRP class and its interfaces and notifications.
+
+**Figure 6.1: Class diagram**
+
+NLIRPOperations\_1 shall support either operation exportLogRecords or operation getLogRecords as mandatory.
+
+## 6.2 Generic rules
+
+- Rule 1:** Each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+- Rule 2:** Each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+- Rule 3:** Each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 NLIRPOperations\_1 Interface (M)
+
+### 6.3.1 Operation subscribeLog (M)
+
+#### 6.3.1.1 Definition
+
+Using this operation, an IRPManager is initiating the logging of notifications. Resulting from this operation an IRPAgent shall start logging of notifications and, if necessary, also create an associated log.
+
+#### 6.3.1.2 Input parameters
+
+| Parameter Name                      | Qualifier | Information type                                                              | Comment                                                                                                                                                                                                                                                                 |
+|-------------------------------------|-----------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logSubscriptionId</code>      | M         | <code>Log.logSubscriptionId</code>                                            | See clause 5.5.1<br>If empty, then IRPAgent shall create a new log and return the <code>logSubscriptionId</code> as output parameter. However not all IRPAgents will provide this capability, i.e. IRPManager must provide an existing <code>logSubscriptionId</code> . |
+| <code>loggingEndTime</code>         | O         | <code>Log.loggingEndTime</code>                                               | See clause 5.5.1                                                                                                                                                                                                                                                        |
+| <code>notificationCategories</code> | O         | <code>Log.notificationCategories</code>                                       | See clause 5.5.1; if <code>notificationCategories</code> is absent than all notifications are logged                                                                                                                                                                    |
+| <code>filter</code>                 | O         | <code>Log.ntfFilterfilter</code><br>Filter constraint grammar is SS dependent | See clause 5.5.1; if this parameter is absent, then no filter constraint shall be applied.                                                                                                                                                                              |
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name    | Qualifier | Matching Information                          | Comment                                                                                                                                                                                                                                        |
+|-------------------|-----------|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionId | M         | Log.logSubscriptionId                         | See clause 5.5.1<br>This parameter contains either<br><ul style="list-style-type: none"> <li>the logSubscriptionId of the log created resulting from this operation or</li> <li>the value of the input parameter logSubscriptionId.</li> </ul> |
+| logManagerToken   | O         | Log.logManagerToken                           | See clause 5.5.1<br>See also comment 6.3.2.2.<br>Note: Security Management IRP may provide capabilities that make this parameter redundant.                                                                                                    |
+| loggingEndTime    | O         | Log.loggingEndTime                            | See clause 5.5.1<br>If supported by the Log IOC (5.3.2) and not already provided by the IRP Manager then the output of this operation must support this parameter.                                                                             |
+| status            | M         | ENUM<br>(OperationSucceeded, OperationFailed) | If loggingEndTime is valid and notificationCategories is valid or absent, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed.<br>If loggingEndTime excessive, status = OperationFailed.                     |
+
+#### 6.3.1.4 Pre-condition
+
+logsNotMaxed
+
+| Assertion Name | Definition                                                          |
+|----------------|---------------------------------------------------------------------|
+| logsNotMaxed   | The number of logs is less than the maximum number of logs allowed. |
+
+#### 6.3.1.5 Post-condition
+
+logStarted
+
+| Assertion Name | Definition                                                                                 |
+|----------------|--------------------------------------------------------------------------------------------|
+| logStarted     | A log is started with the specified characteristics (lifetime and notificationCategories). |
+
+#### 6.3.1.6 Exceptions
+
+| Exception Name             | Definition                                                                                                                                                           |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionId_required | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+| maxLogs_reached            | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+| operation_failed           | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.2 Operation `unsubscribeLog` (M)
+
+#### 6.3.2.1 Definition
+
+Using this operation, the IRPManager that started a specific log is able to stop this log via unsubscribing. Note stopping a log implies that the log becomes invisible across Itf-N, independent from the `loggingEndTime`; therefore the IRPManager should retrieve log information of interest before using this `unsubscribeLog` operation, e.g. through the `exportLogRecords` operation.
+
+The disposition of a log that has been stopped, that is, whether the log remains visible across the Itf-N, is left as vendor specific functionality. The time of the deletion of logs is vendor specific.
+
+In consideration of a multi-manager environment, the log can only be stopped by the creating IRPManager if this IRPManager provided a related token while initiating `subscribeLog`.
+
+#### 6.3.2.2 Input parameters
+
+| Parameter Name                 | Qualifier | Information type                   | Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------------------------|-----------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logSubscriptionId</code> | M         | <code>Log.logSubscriptionId</code> | See clause 5.5.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| <code>logManagerToken</code>   | O         | <code>Log.logManagerToken</code>   | See clause 5.5.1<br>If <code>subscribeLog</code> returned a <code>logManagerToken</code> for a log with <code>logSubscriptionId="X"</code> , then <code>logManagerToken</code> must be provided as input parameter of this operation to successfully stop log with <code>logSubscriptionId="X"</code> .<br>If <code>subscribeLog</code> did not return a <code>logManagerToken</code> for a log with <code>logSubscriptionId="X"</code> , then <code>logManagerToken</code> must contain NULL value to successfully stop log with <code>logSubscriptionId="X"</code> . |
+
+#### 6.3.2.3 Output parameters
+
+| Parameter Name      | Qualifier | Matching Information                                                    | Comment                                                                                                                                                                                                                                 |
+|---------------------|-----------|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>status</code> | M         | ENUM ( <code>OperationSucceeded</code> , <code>OperationFailed</code> ) | If <code>logSubscriptionId</code> is valid and <code>logManagerToken</code> (if supported) is matching, <code>status = OperationSucceeded</code> .<br>If <code>operation_failed</code> is true, <code>status = OperationFailed</code> . |
+
+#### 6.3.2.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.3.2.5 Post-condition
+
+`logStopped`
+
+| Assertion Name          | Definition                    |
+|-------------------------|-------------------------------|
+| <code>logStopped</code> | The specified log is stopped. |
+
+#### 6.3.2.6 Exceptions
+
+| Exception Name                | Definition                                                                                                                                                                         |
+|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>operation_failed</code> | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter <code>status</code> .<br><b>Exit state:</b> Entry state. |
+
+### 6.3.3 Operation `exportLogRecords` (O)
+
+Support for this operation is mandatory if `getLogRecords` is not supported.
+
+#### 6.3.3.1 Definition
+
+Using this operation, an IRPManager can initiate export of all or part of a log into a file. This file then is being transferred to the IRPManager using the File Transfer IRP (note also that the FTIRP is providing the file location to the IRPManager).
+
+#### 6.3.3.2 Input parameters
+
+| Parameter Name         | Qualifier | Information type           | Comment          |
+|------------------------|-----------|----------------------------|------------------|
+| logSubscriptionId      | M         | Log.logSubscriptionId      | See clause 5.5.1 |
+| notificationCategories | O         | Log.notificationCategories | See clause 5.5.1 |
+| filter                 | O         | Log.filterLog.filter       | See clause 5.5.1 |
+
+#### 6.3.3.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|----------------|-----------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| invocationId   | M         | --                   | <p>This parameter carries an identifier that NLIRP assigns to identify the request if the status is OperationSucceeded. This parameter carries no information if the status is not OperationSucceeded.</p> <p>One identifier can at most identify one request. NLIRP should not reuse identifier values.</p> <p>This identifier shall also appear in the file name of the exported log file as &lt;specificIRP_extension&gt; (as part specified in Appendix A: File Name Convention of [8]).</p> <p>When the exported log file is ready, FTIRP issues notifyFileReady notification which carries the exported log file name.</p> |
+
+#### 6.3.3.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.3.3.5 Post-condition
+
+logRecordsExported
+
+| Assertion Name     | Definition                                                                                                                                                                                                                              |
+|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logRecordsExported | The specified log records have been exported as requested. In case the log is empty or in case that all the log records do not satisfy the criteria of input parameters notificationCategories and filter, this post-condition is true. |
+
+#### 6.3.3.6 Exceptions
+
+| Exception Name   | Definition                                                                                                                                                           |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| export_failed    | The NLIRP was unable to export the specified records.                                                                                                                |
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.4 Operation getLogRecords (O)
+
+Support for these operations is mandatory if exportLogRecords is not supported.
+
+#### 6.3.4.1 Definition
+
+Using this operation, an IRPManager can retrieve one or more log records from a certain log.
+
+Note that this operation might be preferred for retrieval of small amounts of log records, while operation `exportLogRecords` might be preferred for retrieval of medium to large amounts of log records, as providing a more efficient bulk transfer mechanism.
+
+#### 6.3.4.2 Input parameters
+
+| Parameter Name                      | Qualifier | Information type                        | Comment          |
+|-------------------------------------|-----------|-----------------------------------------|------------------|
+| <code>logSubscriptionId</code>      | M         | <code>Log.logSubscriptionId</code>      | See clause 5.5.1 |
+| <code>notificationCategories</code> | O         | <code>Log.notificationCategories</code> | See clause 5.5.1 |
+| <code>filter</code>                 | O         | <code>Log.filter</code>                 | See clause 5.5.1 |
+
+#### 6.3.4.3 Output parameters
+
+| Parameter Name                   | Qualifier | Matching Information                                                    | Comment                                                                                                                                                                                                                                                                      |
+|----------------------------------|-----------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>getLogRecordsResult</code> | M         | List of <code>logRecord</code> 's                                       | List of <code>logRecords</code> ; each entry of the list holds all supported attributes of <code>IOC LogRecord</code> (see 5.3.3.2).                                                                                                                                         |
+| <code>status</code>              | M         | ENUM ( <code>OperationSucceeded</code> , <code>OperationFailed</code> ) | If <code>logSubscriptionId</code> is valid and ( <code>logRecordIdList</code> is empty or <code>logRecordIdList</code> contains valid Id's), <code>status = OperationSucceeded</code> .<br>If <code>operation_failed</code> is true, <code>status = OperationFailed</code> . |
+
+#### 6.3.4.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.3.4.5 Post-condition
+
+`logRecordsRetrieved`
+
+| Assertion Name                   | Definition                                                                                                                                                                                                                                        |
+|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logRecordsRetrieved</code> | The specified log records have been retrieved as requested. If the log is empty or all the log records do not satisfy the criteria of input parameters <code>notificationCategories</code> and <code>filter</code> , this post-condition is true. |
+
+#### 6.3.4.6 Exceptions
+
+| Exception Name                | Definition                                                                                                                                                                         |
+|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>operation_failed</code> | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter <code>status</code> .<br><b>Exit state:</b> Entry state. |
+
+## 6.4 NLIRPOperations\_2 Interface (O)
+
+### 6.4.1 Operation `getLogSubscriptionIds` (M)
+
+#### 6.4.1.1 Definition
+
+Using this operation, an `IRPManager` can query the `NLIRP` for all available log subscriptions.
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|----------------|-----------|------------------|---------|
+| --             | --        | --               | --      |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name     | Qualifier | Matching Information                       | Comment                                                                                                            |
+|--------------------|-----------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionIds | M         | List of logSubscriptionId's                | See clause 5.5.1 & 6.4.1.2.<br>Note that empty list is a valid value.                                              |
+| status             | M         | ENUM (OperationSucceeded, OperationFailed) | If operation is successful, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.4.1.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.4.1.5 Post-condition
+
+There are no post-conditions. Querying of log subscription Id's does not result in any changes within the IRP Agent.
+
+#### 6.4.1.6 Exceptions
+
+| Exception Name   | Definition                                                                                                                                                           |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.4.2 Operation getLogSubscriptionStatus (M)
+
+#### 6.4.2.1 Definition
+
+Using this operation, an IRPManager can query the NLIRP for available log status information of an individual log.
+
+#### 6.4.2.2 Input parameters
+
+| Parameter Name    | Qualifier | Information type      | Comment          |
+|-------------------|-----------|-----------------------|------------------|
+| logSubscriptionId | M         | Log.logSubscriptionId | See clause 5.5.1 |
+
+#### 6.4.2.3 Output parameters
+
+| Parameter Name   | Qualifier | Matching Information                                 | Comment                                                                                                              |
+|------------------|-----------|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| logAttributeList | M         | Attributes of related Log IOC except logManagerToken | List of all supported attributes of IOC Log except logManagerToken (see clause 5.3.2.2).                             |
+| status           | M         | ENUM (OperationSucceeded, OperationFailed)           | If logSubscriptionId is valid status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.4.2.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.4.2.5 Post-condition
+
+There are no post-conditions. Querying of log attributes does not result in any changes within the IRPAgent.
+
+#### 6.4.2.6 Exceptions
+
+| Exception Name   | Definition                                                                                                                                                           |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+## 6.5 NLIRPNotifications\_1 Interface (M)
+
+### 6.5.1 Notification notifyLogSubscribed (M)
+
+#### 6.5.1.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Managers that a log subscription has been successfully initiated.
+
+#### 6.5.1.2 Input Parameters
+
+| Parameter Name         | Qualifier | Matching Information       | Comment                                                             |
+|------------------------|-----------|----------------------------|---------------------------------------------------------------------|
+| objectClass            | M,Y       | Log.objectClass            | Notification header - see [3]. It shall carry the Log class name.   |
+| objectInstance         | M,Y       | Log.objectInstance         | Notification header - see [3]. It shall carry the DN of Log.        |
+| notificationId         | M,N       | --                         | Notification header - see [3].                                      |
+| eventTime              | M,Y       | --                         | Notification header - see [3].                                      |
+| notificationType       | M,Y       | "notifyLogSubscribed"      | Notification header - see [3].                                      |
+| systemDN               | C,Y       | --                         | Notification header - see [3].                                      |
+| logSubscriptionId      | M,N       | Log.logSubscriptionId      | See clause 5.5.1                                                    |
+| loggingEndTime         | O,N       | Log.loggingEndTime         | See clause 5.5.1                                                    |
+| notificationCategories | O,N       | Log.notificationCategories | See clause 5.5.1; if absent than all notifications are being logged |
+| filter                 | O,N       | Log.filter                 | See clause 5.5.1                                                    |
+
+#### 6.5.1.3 Triggering Event
+
+##### 6.5.1.3.1 From-state
+
+subscribeLog
+
+| Assertion Name | Definition                                         |
+|----------------|----------------------------------------------------|
+| subscribeLog   | An IRP Manager requests that a new log be started. |
+
+##### 6.5.1.3.2 To-state
+
+logStarted
+
+| Assertion Name | Definition                                            |
+|----------------|-------------------------------------------------------|
+| logStarted     | The NLIRP has started the requested logging activity. |
+
+### 6.5.2 Notification `notifyLogUnsubscribed` (M)
+
+#### 6.5.2.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Manager that a log subscription has stopped.
+
+#### 6.5.2.2 Input Parameters
+
+| Parameter Name                 | Qualifier | Matching Information                   | Comment            |
+|--------------------------------|-----------|----------------------------------------|--------------------|
+| <code>objectClass</code>       | M,Y       | <code>Log.objectClass</code>           | See table 6.5.1.2. |
+| <code>objectInstance</code>    | M,Y       | <code>Log.objectInstance</code>        | See table 6.5.1.2. |
+| <code>notificationId</code>    | M,N       | --                                     | See table 6.5.1.2. |
+| <code>eventTime</code>         | M,Y       | --                                     | See table 6.5.1.2. |
+| <code>notificationType</code>  | M,Y       | " <code>notifyLogUnsubscribed</code> " | See table 6.5.1.2. |
+| <code>systemDN</code>          | C,Y       | --.                                    | See table 6.5.1.2. |
+| <code>logSubscriptionId</code> | M,N       | <code>Log.logSubscriptionId</code>     | See table 6.5.1.2. |
+
+#### 6.5.2.3 Triggering Event
+
+##### 6.5.2.3.1 From-state
+
+`unsubscribeLog` OR `loggingEndTimeReached`
+
+| Assertion Name                     | Definition                                                                                |
+|------------------------------------|-------------------------------------------------------------------------------------------|
+| <code>unsubscribeLog</code>        | The IRP Manager that started the log requests that the log be unsubscribed.               |
+| <code>loggingEndTimeReached</code> | The logging end time specified for the log in <code>subscribeLog</code> has been reached. |
+
+##### 6.5.2.3.2 To-state
+
+`logStopped`
+
+| Assertion Name          | Definition                        |
+|-------------------------|-----------------------------------|
+| <code>logStopped</code> | The logging activity has stopped. |
+
+## 6.6 NLIRPNotifications\_2 Interface (O)
+
+### 6.6.1 Notification notifyOccupancyLevelCrossed (M)
+
+#### 6.6.1.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Managers about the occupancy level of a certain log according with levels defined in 5.5.1 (in addition also the log full action type of this NLIRP instance is being provided for context purposes).
+
+#### 6.6.1.2 Input Parameters
+
+| Parameter Name        | Qualifier | Matching Information                                                           | Comment            |
+|-----------------------|-----------|--------------------------------------------------------------------------------|--------------------|
+| objectClass           | M,Y       | Log.objectClass                                                                | See table 6.5.1.2. |
+| objectInstance        | M,Y       | Log.objectInstance                                                             | See table 6.5.1.2. |
+| notificationId        | M,N       | --                                                                             | See table 6.5.1.2. |
+| eventTime             | M,Y       | --                                                                             | See table 6.5.1.2. |
+| notificationType      | M,Y       | "notifyOccupancyLevelCrossed"                                                  | See table 6.5.1.2. |
+| systemDN              | C,Y       | --                                                                             | See table 6.5.1.2. |
+| logSubscriptionId     | M,Y       | Log.logSubscriptionId                                                          | See table 6.5.1.2. |
+| currentOccupancyLevel | M,N       | The integer portion of $((\text{Log.currentSize} / \text{Log.maxSize}) * 100)$ | See clause 5.5.1.  |
+| logFullAction         | O,N       | Log.logFullAction                                                              | See clause 5.5.1.  |
+
+#### 6.6.1.3 Triggering Event
+
+##### 6.6.1.3.1 From-state
+
+logFull OR occupancyLevelCrossed
+
+| Assertion Name        | Definition                                                                                                                                                                                        |
+|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logFull               | The log is full, that is, the number of log records contained within the log has exceeded the maximum number of log records that was established at log startup (log capacity has reached 100 %). |
+| occupancyLevelCrossed | The number of log records within the log has crossed one of the threshold boundaries (see 5.5.1 Log.occupancyLevels).                                                                             |
+
+##### 6.6.1.3.2 To-state
+
+logWrapping OR (logHalted OR logging)
+
+| Assertion Name | Definition                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logWrapping    | Applicable for case Log.logFullAction='wrap': The number of log records within the log has exceeded the maximum number of allowed log records (100 % capacity has been crossed). The logging of new records will cause the oldest records within the log to be deleted and replaced (first in, first out). The deletion of records may occur in a block, such that the log transitions back to the "started" state prior to any new records being written. |
+| logHalted      | Applicable for case Log.logFullAction='halt': The number of log records within the log has exceeded the maximum number of allowed log records (100 % capacity has been crossed). The logging of new records will be discontinued until the deletion of records has occurred (deletion of records is outside the scope of this IRP).                                                                                                                        |
+| logging        | Applicable for case Log.logFullAction='halt': The number of log records within the log is below the maximum number of allowed records. The generation of the notification is done to inform the subscribed IRP Managers that the log is filling up.                                                                                                                                                                                                        |
+
+### 6.6.2 Notification notifyLoggingResumed (O)
+
+#### 6.6.2.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Managers that the amount of data within a given log has been reduced, allowing logging to resume continue (according to the information provided when the log was created). Note that this notification only applies to Log.logFullAction == 'halt'.
+
+#### 6.6.2.2 Input Parameters
+
+| Parameter Name    | Qualifier | Matching Information   | Comment            |
+|-------------------|-----------|------------------------|--------------------|
+| objectClass       | M,Y       | Log.objectClass        | See table 6.5.1.2. |
+| objectInstance    | M,Y       | Log.objectInstance     | See table 6.5.1.2. |
+| notificationId    | M,N       | --                     | See table 6.5.1.2. |
+| eventTime         | M,Y       | --                     | See table 6.5.1.2. |
+| notificationType  | M,Y       | "notifyLoggingResumed" | See table 6.5.1.2. |
+| systemDN          | C,Y       | --                     | See table 6.5.1.2. |
+| logSubscriptionId | M,Y       | Log.logSubscriptionId  | See table 6.5.1.2. |
+
+#### 6.6.2.3 Triggering Event
+
+##### 6.6.2.3.1 From-state
+
+logFull
+
+| Assertion Name        | Definition                                                                                                                                                                                                                     |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logHalted             | The log is full, that is, the number of log records contained within the log has exceeded the maximum number of log records that was established at log startup (log capacity has reached 100 % and Log.logFullAction='halt'). |
+| occupancyLevelCrossed | The number of log records within the log has crossed one of the threshold boundaries (see 5.5.1 Log.occupancyLevels).                                                                                                          |
+
+##### 6.6.2.3.2 To-state
+
+| Assertion Name | Definition                                                                                                                                                                                            |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logging        | The number of log records within the log is below the maximum number of allowed records. The generation of the notification is done to inform the subscribed IRP Managers that the log is filling up. |
+
+# Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                                    |     |       |        |
+|----------------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------|-----|-------|--------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                    | Cat | Old   | New    |
+| Mar 2004       | S_23  | SP-040123 | --   | --  | Submitted to SA#23 for Information                                                                                 | --  | 1.0.0 |        |
+| Dec 2004       | S_26  | SP-040798 | --   | --  | Submitted to SA#26 for Approval                                                                                    | --  | 2.0.0 | 6.0.0  |
+| Jun 2005       | S_28  | SP-050290 | 0001 | --  | Correct mapping info of currentOccupancyLevel and some editorial errors                                            | F   | 6.0.0 | 6.1.0  |
+| Jun 2005       | S_28  | SP-050329 | 0002 | --  | Apply Generic System Context – Align with TS 32.150                                                                | F   | 6.0.0 | 6.1.0  |
+| Mar 2006       | SA_31 | SP-060091 | 0003 | --  | Add invocationId output parameter of exportLogRecords operation                                                    | F   | 6.1.0 | 6.2.0  |
+| Mar 2006       | SA_31 | SP-060089 | 0004 | --  | Correct ambiguity of object class and object instance usage in notification                                        | F   | 6.1.0 | 6.2.0  |
+| Dec 2006       | SA_34 | SP-060709 | 0005 | --  | Correct the errors in the definition of occupancyLevels and currentOccupancyLevel                                  | F   | 6.2.0 | 6.3.0  |
+| Jun 2007       | SA_36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | --  | 6.3.0 | 7.0.0  |
+| Sep 2007       | SA_37 | SP-070614 | 0006 | --  | Remove the use of visibility symbol                                                                                | C   | 7.0.0 | 8.0.0  |
+| Dec 2009       | -     | -         | -    | -   | Update to Rel-9 version (MCC)                                                                                      | -   | 8.0.0 | 9.0.0  |
+| Mar 2011       | -     | -         | -    | -   | Update to Rel-10 version (MCC)                                                                                     | -   | 9.0.0 | 10.0.0 |
+

marked/Rel-10/32_series/32341/raw.md

@@ -0,0 +1,249 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements (Release 10)**
+
+![3GPP logo](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+---
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, 'G' is black, 'P' is black, and 'P' is black. There is a small red signal icon below the 'G'.
+
+3GPP logo
+
+Keywords  
+UMTS, management, FT
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- 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 File Transfer IRP concept .....                           | 6 |
+| 5 File Transfer IRP requirements.....                       | 6 |
+| 5.1 General requirements for File Transfer IRP.....         | 6 |
+| 5.2 File type requirements .....                            | 7 |
+| 5.3 File exchange requirements.....                         | 7 |
+| 5.4 File management/maintenance/security requirements ..... | 7 |
+| 6 Overview of IRP's related to File Transfer (FT).....      | 8 |
+| Annex A (informative): Change history.....                  | 9 |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 the 32.34x-series covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.341: "File Transfer (FT) Integration Reference Point (IRP): Requirements"**
+- 32.342: "File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)"
+- 32.346: "File Transfer (FT) Integration Reference Point (IRP); Solution Set (SS) definitions"
+
+The Itf-N interface is built up by a number of Integration Reference Points (IRP's) and a related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRP's is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+Network Elements (NEs) under management, element managers as well as network managers generate various management information stored in file format. This IRP is addressing how these file are exchanged through Itf-N as well as certain aspects of file management and maintenance. It is anticipated that all management functions (e.g. PM, Call Trace, CM) as well as associated IRP's making reuse of capabilities provided by this File Transfer IRP.
+
+# --- 1 Scope
+
+The present document specifies the overall requirements for the File Transfer Integration Reference Point (FT IRP) as it applies to the Itf-N.
+
+# --- 2 References
+
+The following documents contain provisions that, 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.111-series: "Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP)".
+- [4] 3GPP TS 32.30x-series: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP)".
+- [5] 3GPP TS 32.33x-series: "Telecommunication management; Notification log Integration Reference Point (IRP)".
+- [6] 3GPP TS 32.32x-series: "Telecommunication management; Test management Integration Reference Point (IRP)".
+- [7] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".
+- [8] 3GPP TS 32.41x-series: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP)".
+- [9] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements".
+- [10] 3GPP TS 32.61x-series: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP)".
+- [11] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                               |
+|------|-------------------------------|
+| CM   | Configuration Management      |
+| EM   | Element Manager               |
+| FT   | File Transfer                 |
+| FTP  | File Transfer Protocol        |
+| IRP  | Integration Reference Point   |
+| NE   | Network Element               |
+| NM   | Network Manager               |
+| PM   | Performance Management        |
+| SFTP | Secure File Transfer Protocol |
+
+# --- 4 File Transfer IRP concept
+
+Network Elements (NEs) under management, element managers as well as network managers generate various management information that is stored in files. This IRP is addressing how these file are exchanged through Itf-N as well as certain aspects of file management and maintenance. It is anticipated that all management functions (e.g. PM, Call Trace, CM) as well as associated IRP's making reuse of capabilities provided by this File Transfer IRP.
+
+It should be noted that this File Transfer IRP is not defining a file transfer protocol (applicable file transfer protocols are defined by 3GPP TS 32.101 [1]) but will make reuse of generic concepts defined by these file transfer protocol.
+
+# --- 5 File Transfer IRP requirements
+
+## 5.1 General requirements for File Transfer IRP
+
+The FT IRP shall ensure preservation of file content:
+
+- The used file transfer protocol implementation shall preserve the formatting of the file during exchange.
+- The used file transfer protocol implementation shall preserve the encoding of the file during exchange.
+
+NOTE 1: Above requirement(s) are considered as being satisfied by FTP.
+
+The FT IRP shall support the following file transfer protocols:
+
+- FTP.
+- SFTP
+
+NOTE 2: SFTP providing initial security capabilities, which may be complemented by additional security features that might be added in future versions of the present document.
+
+The FT IRP shall specify all necessary descriptive file information and parameters, to enable exchange of files between IRPManager and IRPAgent and to ensure respective file management capabilities (such as listing).
+
+File Name conventions:
+
+- In the context of this File Transfer IRP an overall applicable file name convention should be specified, ensuring the use of meaningful and uniform names of files generated by various IRP's. This convention should reuse the current PM File Naming Conventions to the greatest extent possible [7].
+- This file name convention should address issues with potential Operating System based changes in file names during or after file exchange (e.g. upper case / lower case).
+- The file name shall contain the file expiration date
+
+## 5.2 File type requirements
+
+The FT IRP shall support the exchange and management/maintenance of the following file types:
+
+- Performance measurement results as defined in [7] and [8].
+- Test results as defined in [6].
+- Bulk CM files as defined in [10].
+- Call trace records as defined in [9].
+- Notification log as defined in [5].
+- Charging files as defined in [11].
+- Vendor-specific files containing management information.
+
+Subsequently this File Transfer IRP shall consider requirements from management applications listed above.
+
+Future 3GPP management information file types shall be supported as well (e.g. inventory information).
+
+## 5.3 File exchange requirements
+
+The IRP Manager shall be able to:
+
+- Upload (read) one or more files from the IRP Agent using FTP or SFTP;
+- Download (write) one or more files to the IRP Agent using FTP or SFTP, and indicate to the IRP Agent that files have been downloaded.
+
+Subsequently: the IRP Manager will always act as the initiator (client) of file transfer actions, while the IRP Agent shall provide the corresponding server capabilities.
+
+This IRP Agent should provide the following notifications to the IRP Manager:
+
+- "File Ready", indicating that a file is ready for upload;
+- "File Preparation Error", indicating that an error occurred during or before file preparation and that no file is being made available related to a specific request;
+- "File Deleted", indicating that a file has been made unavailable for access through Itf-N.
+
+## 5.4 File management/maintenance/security requirements
+
+The IRP Manager should be able to request the IRP Agent to:
+
+- Provide a list of available files, based on file name and file creation date/time filter criteria.
+
+In addition the following requirements should be considered:
+
+- Security mechanisms supported by applicable file transfer protocols defined in [1] should be supported (e.g. username, password, encryption).
+- File system overload mechanism on IRP Agent side (e.g. automatic deletion of transmitted files, automatic deletion of outdated files, emission of notifications in case of automatic deletion).
+- File deletion is determined by a file expiration date, which is part of the file name.
+
+# --- 6 Overview of IRP's related to File Transfer (FT)
+
+Itf-N is built up by a number of IRP's. The basic structure of the IRP's is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+For the purpose of the File Transfer IRP the following IRP's are needed:
+
+- Notification IRP [4].
+
+The following IRP/specifications shall consider using this FT IRP for file transfer purposes (future IRP or IRP capabilities not listed here shall also consider reuse of this FT IRP for file transfer purposes):
+
+- Performance measurement results as defined in [7] and [8].
+- Test results as defined in [6].
+- Bulk CM files as defined in [10].
+- Call trace records as defined in [9].
+- Notification log exports as defined in [5].
+
+Specification changes needed by those IRP's to make reuse of the FT IRP are outside the scope of the present document.
+
+# Annex A (informative): Change history
+
+| Change history |       |           |      |     |                                                                                                                    |         |       |        |  |
+|----------------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------|---------|-------|--------|--|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                    | Ca<br>t | Old   | New    |  |
+| Jun 2003       | SA_20 | SP-030295 | --   | --  | Submitted to TSG SA#20 for information                                                                             | --      | 1.0.0 |        |  |
+| Mar 2004       | SA_23 | SP-040124 | --   | --  | Submitted to TSG SA#23 for Approval                                                                                | --      | 2.0.0 | 6.0.0  |  |
+| Mar 2005       | SA_27 | SP-050037 | 0001 | --  | Add file type requirements - Align with FTIRP IS in TS 32.342                                                      | F       | 6.0.0 | 6.1.0  |  |
+| Sep 2006       | SA_33 | SP-060530 | 0002 | --  | Correct the file exchange requirements in File Transfer (FT) Integration Reference Point (IRP)                     | F       | 6.1.0 | 6.2.0  |  |
+| Jun 2007       | SA_36 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | --      | 6.2.0 | 7.0.0  |  |
+| Mar 2009       | SA_43 | SP-090207 | 0003 | --  | Include reference to SOAP Solution Set specification                                                               | D       | 7.0.0 | 8.0.0  |  |
+| 2009-12        | -     | -         | -    | -   | Update to Rel-9 version (MCC)                                                                                      | -       | 8.0.0 | 9.0.0  |  |
+| 2011-03        | -     | -         | -    | -   | Update to Rel-10 version (MCC)                                                                                     | -       | 9.0.0 | 10.0.0 |  |

marked/Rel-10/32_series/32342/raw.md

@@ -0,0 +1,715 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP TS 32.342 V10.0.0 (2011-03) Telecommunication management; File Transfer (FT) Technical Specification Integration Reference Point (IRP); Information Service (IS) (Release 10)** ---
+
+![3GPP logo with TM symbol](935eed7aa61f7777f62cfc032e11bee9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold, black font. The '3' is slightly larger and positioned to the left of the 'G', 'P', and 'P'. A small 'TM' symbol is located to the upper right of the 'P'.
+
+3GPP logo with TM symbol
+
+Keywords  
+GSM, UMTS, management
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                          |    |
+|----------------------------------------------------------|----|
+| Foreword .....                                           | 5  |
+| Introduction .....                                       | 5  |
+| 1 Scope.....                                             | 6  |
+| 2 References.....                                        | 6  |
+| 3 Definitions and abbreviations .....                    | 7  |
+| 3.1 Definitions.....                                     | 7  |
+| 3.2 Abbreviations .....                                  | 7  |
+| 4 System Overview .....                                  | 8  |
+| 4.1 System context .....                                 | 8  |
+| 4.2 Compliance rules.....                                | 8  |
+| 5 Information Object Classes (IOC) .....                 | 9  |
+| 5.1 Information entities imported and local labels.....  | 9  |
+| 5.2 Class Diagram .....                                  | 9  |
+| 5.2.1 Attributes and relationships.....                  | 9  |
+| 5.2.2 Inheritance .....                                  | 10 |
+| 5.3 Information Object Class (IOC) definitions.....      | 11 |
+| 5.3.1 FileTransferIRP .....                              | 11 |
+| 5.3.1.1 Definition .....                                 | 11 |
+| 5.3.2 AvailableFileDescriptor .....                      | 11 |
+| 5.3.2.1 Definition .....                                 | 11 |
+| 5.3.2.2 Attributes .....                                 | 11 |
+| 5.3.3 AvailableFileList .....                            | 11 |
+| 5.3.3.1 Definition .....                                 | 11 |
+| 5.3.4 File.....                                          | 11 |
+| 5.3.4.1 Definition .....                                 | 11 |
+| 5.4 Information relationship definitions.....            | 12 |
+| 5.4.1 relation-flIRP-availableFileList (M) .....         | 12 |
+| 5.4.1.1 Definition .....                                 | 12 |
+| 5.4.1.2 Role.....                                        | 12 |
+| 5.4.2 relation-availableFileList-availableFiles (M)..... | 12 |
+| 5.4.2.1 Definition .....                                 | 12 |
+| 5.4.2.2 Role.....                                        | 12 |
+| 5.4.2.3 Constraint.....                                  | 12 |
+| 5.4.3 relation-availableFileDescriptor-file (M) .....    | 12 |
+| 5.4.3.1 Definition .....                                 | 12 |
+| 5.4.3.2 Role.....                                        | 12 |
+| 5.5 Information attribute definition.....                | 13 |
+| 5.5.1 Definition and legal values.....                   | 13 |
+| 6 Interface Definition .....                             | 14 |
+| 6.1 Class diagram.....                                   | 14 |
+| 6.2 Generic rules .....                                  | 14 |
+| 6.3 FileTransferIRPOperations_1 Interface .....          | 15 |
+| 6.3.1 Operation listAvailableFiles (M).....              | 15 |
+| 6.3.1.1 Definition .....                                 | 15 |
+| 6.3.1.2 Input parameters .....                           | 15 |
+| 6.3.1.3 Output parameters.....                           | 15 |
+| 6.3.1.4 Pre-condition.....                               | 15 |
+| 6.3.1.5 Post-condition .....                             | 15 |
+| 6.3.1.6 Exceptions.....                                  | 16 |
+| 6.4 FileTransferIRPOperations_2 Interface .....          | 16 |
+| 6.4.1 Operation fileDownloadIndication (O) .....         | 16 |
+| 6.4.1.1 Definition .....                                 | 16 |
+| 6.4.1.2 Input parameters .....                           | 16 |
+| 6.4.1.3 Output parameters.....                           | 16 |
+
+|                             |                                                   |           |
+|-----------------------------|---------------------------------------------------|-----------|
+| 6.4.1.4                     | Pre-condition.....                                | 16        |
+| 6.4.1.5                     | Post-condition .....                              | 16        |
+| 6.4.1.6                     | Exceptions.....                                   | 16        |
+| 6.5                         | FileTransferIRPNotifications_1 Interface.....     | 17        |
+| 6.5.1                       | Notification notifyFileReady (M).....             | 17        |
+| 6.5.1.1                     | Definition .....                                  | 17        |
+| 6.5.1.2                     | Input Parameters .....                            | 17        |
+| 6.5.1.3                     | Triggering Event .....                            | 17        |
+| 6.5.1.3.1                   | From-state.....                                   | 17        |
+| 6.5.1.3.2                   | To-state.....                                     | 17        |
+| 6.5.2                       | Notification notifyFilePreparationError (M) ..... | 18        |
+| 6.5.2.1                     | Definition .....                                  | 18        |
+| 6.5.2.2                     | Input Parameters .....                            | 18        |
+| 6.5.2.3                     | Triggering Event .....                            | 18        |
+| 6.5.2.3.1                   | From-state.....                                   | 18        |
+| 6.5.2.3.2                   | To-state.....                                     | 18        |
+| <b>Annex A (normative):</b> | <b>File Naming Convention .....</b>               | <b>19</b> |
+| Annex B (informative):      | Change history.....                               | 20        |
+
+# --- Foreword
+
+This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
+
+- 32.341: "File Transfer (FT) Integration Reference Point (IRP): Requirements"
+- 32.342: "File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)"**
+- 32.346: "File Transfer (FT) Integration Reference Point (IRP); Solution Set (SS) definitions"
+
+The present document is part of a TS-family which describe 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 [1] and 3GPP TS 32.102 [2].
+
+Network Elements (NEs) under management, element managers as well as network managers generate various management information stored in file format. This IRP is addressing how these files are exchanged through Itf-N as well as certain aspects of file management and maintenance. It is anticipated that all management functions (e.g. PM, Call Trace, CM) as well as associated IRPs making reuse of capabilities provided by this File Transfer IRP.
+
+# --- 1 Scope
+
+The present document specifies the Information Service for the File Transfer Integration Reference Point (FileTransferIRP) as it applies to the Itf-N.
+
+The present document defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+# --- 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.111-2: "Telecommunication management; Fault management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [5] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP): Information Service (IS)".
+- [6] 3GPP TS 32.321: "Telecommunication management; Test management Integration Reference Point (IRP): Requirements".  
+3GPP TS 32.322: "Telecommunication management; Test management Integration Reference Point (IRP): Information Service (IS)".  
+3GPP TS 32.323: "Telecommunication management; Test management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".  
+3GPP TS 32.325: "Telecommunication management; Test management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions".
+- [7] 3GPP TS 32.341 "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Requirements".
+- [8] 3GPP TS 32.411: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Requirements".  
+3GPP TS 32.412: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Information Service (IS)".  
+3GPP TS 32.413: "Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".  
+3GPP TS 32.415 Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions".
+
+- [9] 3GPP TS 32.421: "Telecommunication Management; Subscriber and Equipment Trace: Trace Concepts and Requirements".
+  
+- [10] 3GPP TS 32.611: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements".
+- 3GPP TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) ".
+- 3GPP TS 32.613: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
+- 3GPP TS 32.615: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition".
+  
+- [11] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements".
+- 3GPP TS 32.332: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Information Service (IS)".
+- 3GPP TS 32.333: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)".
+- 3GPP TS 32.335: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): eXtensible Markup Language (XML) solution definitions".
+  
+- [12] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+  
+- [13] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
+  
+- [14] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.101 [1], TS 32.102 [2] and TS 32.341 [7] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                             |
+|-----|-----------------------------|
+| CM  | Configuration Management    |
+| EM  | Element Manager             |
+| IOC | Information Object Class    |
+| IRP | Integration Reference Point |
+| NE  | Network Element             |
+| PM  | Performance Management      |
+| UML | Unified Modelling Language  |
+
+# 4 System Overview
+
+## 4.1 System context
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [14] subclause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below.
+
+![Figure 4.1: System Context A](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+Diagram illustrating System Context A. It shows an IRPManager (NM) connected to an IRPAgent (EM), which is connected to NEs. A dashed vertical line labeled 'Itf-N' separates the NM and EM. Below the Itf-N line, a list of IRPs is shown: Notification IRP and File Transfer IRP.
+
+Figure 4.1: System Context A
+
+Figure 4.1: System Context A
+
+![Figure 4.2: System Context B](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+Diagram illustrating System Context B. It shows an IRPManager (NM) connected to an IRPAgent (NE), which is connected to NEs. A dashed vertical line labeled 'Itf-N' separates the NM and NE. Below the Itf-N line, a list of IRPs is shown: Notification IRP and File Transfer IRP.
+
+Figure 4.2: System Context B
+
+Figure 4.2: System Context B
+
+## 4.2 Compliance rules
+
+For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for *operations, notifications and parameters* (of operations and notifications) please refer to 3GPP TS 32.150 [14].
+
+# 5 Information Object Classes (IOC)
+
+## 5.1 Information entities imported and local labels
+
+| Label reference                                                              | Local label       |
+|------------------------------------------------------------------------------|-------------------|
+| 3GPP TS 32.622 [12], information object class, <code>Top</code>              | Top               |
+| 3GPP TS 32.622 [12], information object class, <code>IRPAgent</code>         | IRPAgent          |
+| 3GPP TS 32.622 [12], information object class, <code>GenericIRP</code>       | GenericIRP        |
+| 3GPP TS 32.312 [5], information object class, <code>ManagedGenericIRP</code> | ManagedGenericIRP |
+| 3GPP TS 32.302 [4], information object class, <code>NotificationIRP</code>   | NotificationIRP   |
+
+## 5.2 Class Diagram
+
+### 5.2.1 Attributes and relationships
+
+This clause introduces the set of information object classes (IOCs) that encapsulate information within the `IRPAgent`. The intent is to identify the information required for the FileTransferIRP Agent implementation of its operations and notification emission. This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes.
+
+![UML Class Diagram showing Information Object Classes (IOCs) and their relationships including ManagedGenericIRP, FileTransferIRP, AvailableFileList, AvailableFileDescriptor, and File.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg)
+
+```
+
+classDiagram
+    class ManagedGenericIRP["<<Information Object Class>>\nManagedGenericIRP\n(from TS 32.312)"]
+    class FileTransferIRP["<<Information Object Class>>\nFileTransferIRP"]
+    class AvailableFileList["<<Information Object Class>>\nAvailableFileList"]
+    class AvailableFileDescriptor["<<Information Object Class>>\nAvailableFileDescriptor\n+ fileSize\n+ fileCompression\n+ fileReadyTime\n+ fileExpirationTime\n+ fileFormat\n+ fileLocation\n+ managementDataType"]
+    class File["<<proxy Object>>\nFile"]
+
+    ManagedGenericIRP <|-- FileTransferIRP
+    FileTransferIRP "1" *-- "1" AvailableFileList : relation-ftIRP-availableFileList
+    AvailableFileList "1" *-- "0..n" AvailableFileDescriptor : relation-availableFileList-availableFiles
+    AvailableFileDescriptor "1" -- "1" File : relation-availableFileDescriptor-file
+
+    note for FileTransferIRP "+theFileTransferIRP"
+    note for AvailableFileList "+theAvailableFileList"
+    note for AvailableFileDescriptor "+theAvailableFileDescriptor"
+    note for File "+theFile"
+  
+```
+
+The diagram illustrates the following classes and relationships:
+
+- ManagedGenericIRP** (Information Object Class, from TS 32.312) is the base class for **FileTransferIRP**.
+- FileTransferIRP** (Information Object Class) has a composition relationship with **AvailableFileList** (Information Object Class) labeled *relation-ftIRP-availableFileList*. The multiplicity is 1 at both ends. Role names are `+theFileTransferIRP` and `+theAvailableFileList`.
+- AvailableFileList** (Information Object Class) has a composition relationship with **AvailableFileDescriptor** (Information Object Class) labeled *relation-availableFileList-availableFiles*. The multiplicity is 1 at the list end and 0..n at the descriptor end. Role names are `+theAvailableFileList` and `+theAvailableFileDescriptor`.
+- AvailableFileDescriptor** (Information Object Class) contains attributes: `+ fileSize`, `+ fileCompression`, `+ fileReadyTime`, `+ fileExpirationTime`, `+ fileFormat`, `+ fileLocation`, and `+ managementDataType`. It has an association with **File** (proxy Object) labeled *relation-availableFileDescriptor-file*. The multiplicity is 1 at both ends. Role names are `+theAvailableFileDescriptor` and `+theFile`.
+
+UML Class Diagram showing Information Object Classes (IOCs) and their relationships including ManagedGenericIRP, FileTransferIRP, AvailableFileList, AvailableFileDescriptor, and File.
+
+Figure 5.1: Information Object Class (IOC) UML Diagram
+
+### 5.2.2 Inheritance
+
+![UML Class Diagram showing Information Object Class (IOC) inheritance. At the top is the class '<<Information Object Class>> Top (from TS 32.622)'. Three classes inherit directly from Top: '<<Information Object Class>> AvailableFileDescriptor' (containing attributes: + fileSize, + fileCompression, + fileReadyTime, + fileExpirationTime, + fileFormat, + fileLocation, + managementDataType), '<<Information Object Class>> GenericRP (from TS 32.622)', and '<<Information Object Class>> AvailableFileList'. Below GenericRP, '<<Information Object Class>> ManagedGenericRP (from TS 32.312)' inherits from it. Finally, '<<Information Object Class>> FileTransferRP' inherits from ManagedGenericRP.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+```
+classDiagram
+    class Top["<<Information Object Class>>\nTop\n(from TS 32.622)"]
+    class AvailableFileDescriptor["<<Information Object Class>>\nAvailableFileDescriptor"]
+    AvailableFileDescriptor : + fileSize
+    AvailableFileDescriptor : + fileCompression
+    AvailableFileDescriptor : + fileReadyTime
+    AvailableFileDescriptor : + fileExpirationTime
+    AvailableFileDescriptor : + fileFormat
+    AvailableFileDescriptor : + fileLocation
+    AvailableFileDescriptor : + managementDataType
+    class GenericRP["<<Information Object Class>>\nGenericRP\n(from TS 32.622)"]
+    class AvailableFileList["<<Information Object Class>>\nAvailableFileList"]
+    class ManagedGenericRP["<<Information Object Class>>\nManagedGenericRP\n(from TS 32.312)"]
+    class FileTransferRP["<<Information Object Class>>\nFileTransferRP"]
+
+    Top <|-- AvailableFileDescriptor
+    Top <|-- GenericRP
+    Top <|-- AvailableFileList
+    GenericRP <|-- ManagedGenericRP
+    ManagedGenericRP <|-- FileTransferRP
+```
+
+UML Class Diagram showing Information Object Class (IOC) inheritance. At the top is the class '<> Top (from TS 32.622)'. Three classes inherit directly from Top: '<> AvailableFileDescriptor' (containing attributes: + fileSize, + fileCompression, + fileReadyTime, + fileExpirationTime, + fileFormat, + fileLocation, + managementDataType), '<> GenericRP (from TS 32.622)', and '<> AvailableFileList'. Below GenericRP, '<> ManagedGenericRP (from TS 32.312)' inherits from it. Finally, '<> FileTransferRP' inherits from ManagedGenericRP.
+
+Figure 5.2: Information Object Class (IOC) Inheritance UML Diagram
+
+## 5.3 Information Object Class (IOC) definitions
+
+### 5.3.1 FileTransferIRP
+
+#### 5.3.1.1 Definition
+
+FileTransferIRP is the representation of the file transfer management capabilities specified by the present document. This IOC inherits from `ManagedGenericIRP` IOC specified in 3GPP TS 32.312 [5].
+
+### 5.3.2 AvailableFileDescriptor
+
+#### 5.3.2.1 Definition
+
+`AvailableFileDescriptor` represents the information about an existing closed file containing management data (performance measurement data, etc.). The file is ready for retrieval by IRPManagers.
+
+#### 5.3.2.2 Attributes
+
+| <b>Attribute name</b>           | <b>Visibility</b> | <b>Support Qualifier</b> | <b>Read Qualifier</b> | <b>Write Qualifier</b> |
+|---------------------------------|-------------------|--------------------------|-----------------------|------------------------|
+| <code>managementDataType</code> | +                 | M                        | M                     | -                      |
+| <code>fileSize</code>           | +                 | M                        | M                     | -                      |
+| <code>fileCompression</code>    | +                 | M                        | M                     | -                      |
+| <code>fileReadyTime</code>      | +                 | M                        | M                     | -                      |
+| <code>fileExpirationTime</code> | +                 | M                        | M                     | -                      |
+| <code>fileFormat</code>         | +                 | M                        | M                     | -                      |
+| <code>fileLocation</code>       | +                 | M                        | M                     | -                      |
+
+### 5.3.3 AvailableFileList
+
+#### 5.3.3.1 Definition
+
+`AvailableFileList` is the representation of a list of files represented by individual `AvailableFileDescriptor(s)`.
+
+### 5.3.4 File
+
+#### 5.3.4.1 Definition
+
+The Proxy Object File represents the file stored in the managed system.
+
+## 5.4 Information relationship definitions
+
+### 5.4.1 relation-ftIRP-availableFileList (M)
+
+#### 5.4.1.1 Definition
+
+This represents the relationship between `FileTransferIRP` and `AvailableFileList`.
+
+#### 5.4.1.2 Role
+
+| Name                              | Definition                                         |
+|-----------------------------------|----------------------------------------------------|
+| <code>theAvailableFileList</code> | It represents the <code>AvailableFileList</code> . |
+| <code>theFileTransferIRP</code>   | It represents the <code>FileTransferIRP</code> .   |
+
+### 5.4.2 relation-availableFileList-availableFiles (M)
+
+#### 5.4.2.1 Definition
+
+This represents the relationship between `AvailableFileDescriptor` and `AvailableFileList`.
+
+#### 5.4.2.2 Role
+
+| Name                                    | Definition                                               |
+|-----------------------------------------|----------------------------------------------------------|
+| <code>theAvailableFileDescriptor</code> | It represents the <code>AvailableFileDescriptor</code> . |
+| <code>theAvailableFileList</code>       | It represents the <code>AvailableFileList</code> .       |
+
+#### 5.4.2.3 Constraint
+
+| Name                            | Definition                                                                                                                                                                   |
+|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>uniqueFileLocation</code> | The <code>fileLocation</code> , playing the role of the file within the same <code>FileTransferIRP</code> , must be unique among all <code>AvailableFileDescriptors</code> . |
+
+### 5.4.3 relation-availableFileDescriptor-file (M)
+
+#### 5.4.3.1 Definition
+
+This represents the relationship between `AvailableFileDescriptor` and `PhysicalFile`.
+
+#### 5.4.3.2 Role
+
+| Name                                    | Definition                                               |
+|-----------------------------------------|----------------------------------------------------------|
+| <code>theAvailableFileDescriptor</code> | It represents the <code>AvailableFileDescriptor</code> . |
+| <code>theAvailableFile</code>           | It represents the <code>PhysicalFile</code> .            |
+
+## 5.5 Information attribute definition
+
+### 5.5.1 Definition and legal values
+
+| Attribute Name     | Definition                                                                                                                                  | Legal Values                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| fileSize           | It identifies the size of the file.                                                                                                         | Its value is positive Integer (the unit is byte).                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| fileCompression    | It identifies the name of the compression algorithm used for the file.                                                                      | An empty fileCompression means that there is no compression on the file. Choice of compression algorithm is vendor-specific but is encouraged to use industrial standard algorithm such as GZIP.                                                                                                                                                                                                                                                                                   |
+| fileReadyTime      | It identifies the date and time when the file was last closed and made available for upload and the file content will not be changed        | All values that indicate valid time.                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| fileExpirationTime | It identifies the date and time beyond which the file may be deleted.                                                                       | All values that indicate valid time.<br>It should be later than fileReadyTime.<br>It shall not be empty.                                                                                                                                                                                                                                                                                                                                                                           |
+| fileFormat         | It identifies the encoding technique used by the file.                                                                                      | Its value should indicate the IRPVersion of the file format specification plus to indicate if "ASN1" or "XML-schema" is used.                                                                                                                                                                                                                                                                                                                                                      |
+| fileLocation       | It identifies the location of the file described by AvailableFileDescriptor in the IRPAgent. The location may be a directory path or a URL. | <ul style="list-style-type: none"> <li>Any valid file directory path.</li> <li>Any valid URL.</li> </ul> E.g.:<br>“\\202.112.101.1\D:\user\performanceFiles\<xxx>” or<br>“ <a href="http://nms.telecom.org.com/datastore/&lt;xxx&gt;">http://nms.telecom.org.com/datastore/&lt;xxx&gt;</a> ”<br>where <xxx> is the filename and the file naming convention is defined in Annex A File Naming Convention.                                                                           |
+| managementDataType | It identifies the type of the management data in the file.                                                                                  | "CG" for charging files (TS 32.240 [13]),<br>"CM" for configuration files (except inventory) (Bulk CM IRP TS 32.61x [10]),<br>"CT" for call trace files (Subscriber and Equipment Trace TS 32.421 [9]),<br>"IM" for inventory files,<br>"NL" for notification log files (Notification Log IRP TS 32.33x [11]),<br>"OT" for other files,<br>"PM" for performance data files (Performance Management IRP TS 32.41x [8]),<br>"TE" for test files (Test Management IRP TS 32.32x [6]). |
+
+# 6 Interface Definition
+
+## 6.1 Class diagram
+
+![UML Class Diagram showing FileTransferIRP as an InformationObjectClass. It has three associations: 1) A generalization/specialization relationship with FileTransferIRPOperations_1 (Interface) labeled '<<may realize>>'. 2) A generalization/specialization relationship with FileTransferIRPOperations_2 (Interface) labeled '<<may realize>>'. 3) A directed association with FileTransferIRPNotifications_1 (Notification) labeled '<<use>>'. FileTransferIRPOperations_1 has an operation + listAvailableFiles(). FileTransferIRPNotifications_1 has operations + notifyFileReady() and + notifyFilePreparationError(). FileTransferIRPNotifications_1 has a directed association with NotificationIRP (InformationObjectClass, from TS 32.302) labeled '<<agent-internal-usage>>'.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+
+classDiagram
+    class FileTransferIRP {
+        <<InformationObjectClass>>
+    }
+    class FileTransferIRPOperations_1 {
+        <<Interface>>
+        +listAvailableFiles()
+    }
+    class FileTransferIRPOperations_2 {
+        <<Interface>>
+        +fileDownloadIndication()
+    }
+    class FileTransferIRPNotifications_1 {
+        <<Notification>>
+        +notifyFileReady()
+        +notifyFilePreparationError()
+    }
+    class NotificationIRP {
+        <<InformationObjectClass>>
+        (from TS 32.302)
+    }
+
+    FileTransferIRP --> FileTransferIRPOperations_1 : <<may realize>>
+    FileTransferIRP --> FileTransferIRPOperations_2 : <<may realize>>
+    FileTransferIRP --> FileTransferIRPNotifications_1 : <<use>>
+    FileTransferIRPNotifications_1 --> NotificationIRP : <<agent-internal-usage>>
+  
+```
+
+UML Class Diagram showing FileTransferIRP as an InformationObjectClass. It has three associations: 1) A generalization/specialization relationship with FileTransferIRPOperations\_1 (Interface) labeled '<>'. 2) A generalization/specialization relationship with FileTransferIRPOperations\_2 (Interface) labeled '<>'. 3) A directed association with FileTransferIRPNotifications\_1 (Notification) labeled '<>'. FileTransferIRPOperations\_1 has an operation + listAvailableFiles(). FileTransferIRPNotifications\_1 has operations + notifyFileReady() and + notifyFilePreparationError(). FileTransferIRPNotifications\_1 has a directed association with NotificationIRP (InformationObjectClass, from TS 32.302) labeled '<>'.
+
+Figure 6.1: Class Diagram
+
+## 6.2 Generic rules
+
+- **Rule 1:** each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+- **Rule 2:** each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+- **Rule 3:** each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 FileTransferIRPOperations\_1 Interface
+
+### 6.3.1 Operation listAvailableFiles (M)
+
+#### 6.3.1.1 Definition
+
+This operation allows IRPManager to list all or specified available management data files stored in the IRPAgent.
+
+A Solution Set may choose to split this operation in several operations (e.g. operations to get "iterator" which fulfil the criteria and other operations to retrieve the detailed information of the files from the "iterator").
+
+#### 6.3.1.2 Input parameters
+
+| Parameter Name                  | Qualifier | Information type                                                                                                                                                 | Comment                                                                                                                           |
+|---------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| <code>managementDataType</code> | M         | AvailableFileDescriptor.<br>managementDataType                                                                                                                   | It specifies the type of the management data stored in the file.                                                                  |
+| <code>beginTime</code>          | M         | The IRPManager wants a list of the available file(s) whose ready time(s) are later or equal to this time.<br>This parameter is expressed in UTC time.            | This parameter indicates date and time. If this parameter is empty, no beginTime-restriction should be applied on the ready time. |
+| <code>endTime</code>            | M         | The IRPManager wants to list information about the available file(s) whose ready time(s) are earlier than this time.<br>This parameter is expressed in UTC time. | This parameter indicates date and time. If this parameter is empty, no endTime-restriction should be applied on the ready time.   |
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name            | Qualifie<br>r | Matching Information                                                                                                                                                                                                                                                         | Comment                                                       |
+|---------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| <code>fileInfoList</code> | M             | LIST of STRUCT <<br>AvailableFileDescriptor.fileLocation,<br>AvailableFileDescriptor.fileSize<br>AvailableFileDescriptor.fileReadyTime<br>AvailableFileDescriptor.fileExpirationTime<br>AvailableFileDescriptor.fileCompression,<br>AvailableFileDescriptor.fileFormat,<br>> | The output parameter specifies the required file information. |
+| <code>status</code>       | M             | ENUM (Success, Failure)                                                                                                                                                                                                                                                      |                                                               |
+
+#### 6.3.1.4 Pre-condition
+
+validTimes
+
+| Assertion Name          | Definition                                                                                       |
+|-------------------------|--------------------------------------------------------------------------------------------------|
+| <code>validTimes</code> | The beginTime is before the invocation time of the operation and the endTime is after beginTime. |
+
+#### 6.3.1.5 Post-condition
+
+requiredFileInfoIsReturned
+
+| Assertion Name                          | Definition                                 |
+|-----------------------------------------|--------------------------------------------|
+| <code>requiredFileInfoIsReturned</code> | The required file information is returned. |
+
+#### 6.3.1.6 Exceptions
+
+| Exception Name            | Definition                                                                                                                                                 |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>invalidTimes</code> | <b>Condition:</b> (validTimes) not verified.<br><b>Returned information:</b> output parameter status is set to Failure.<br><b>Exit state:</b> Entry State. |
+
+## 6.4 FileTransferIRPOperations\_2 Interface
+
+### 6.4.1 Operation fileDownloadIndication (O)
+
+#### 6.4.1.1 Definition
+
+This operation allows IRPManager to indicate IRPAgent about completion of the file exchange procedure and related file descriptive information when IRPManager finish downloading one or more files to IRPAgent.
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type                                                                                                                                                                                                                                                             | Comment                                                             |
+|----------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
+| fileInfoList   | M         | LIST of STRUCT <<br>AvailableFileDescriptor.fileLocation,<br>AvailableFileDescriptor.fileSize<br>AvailableFileDescriptor.fileReadyTime<br>AvailableFileDescriptor.fileExpirationTime<br>AvailableFileDescriptor.fileCompression,<br>AvailableFileDescriptor.fileFormat,<br>> | It carries the information of the files downloaded to the IRPAgent. |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information    | Comment |
+|----------------|-----------|-------------------------|---------|
+| status         | M         | ENUM (Success, Failure) |         |
+
+#### 6.4.1.4 Pre-condition
+
+validFileInfoList
+
+| Assertion Name    | Definition                 |
+|-------------------|----------------------------|
+| validFileInfoList | The fileInfoList is valid. |
+
+#### 6.4.1.5 Post-condition
+
+validFileSize
+
+| Assertion Name | Definition                                                         |
+|----------------|--------------------------------------------------------------------|
+| validFileSize  | The downloaded file exist and the size of it is greater than zero. |
+
+#### 6.4.1.6 Exceptions
+
+| Exception Name      | Definition                                                                                                                                                        |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| InvalidFileInfoList | <b>Condition:</b> (validFileInfoList) not verified.<br><b>Returned information:</b> output parameter status is set to Failure.<br><b>Exit state:</b> Entry State. |
+
+## 6.5 FileTransferIRPNotifications\_1 Interface
+
+### 6.5.1 Notification notifyFileReady (M)
+
+#### 6.5.1.1 Definition
+
+After the management data files have been prepared ready in the IRPAgent, IRPAgent will emit notification to subscribed IRPManager(s) to notify the availability of the file(s).
+
+#### 6.5.1.2 Input Parameters
+
+| Parameter Name   | Qualifier | Matching Information                                                    | Comment                                                                   |
+|------------------|-----------|-------------------------------------------------------------------------|---------------------------------------------------------------------------|
+| objectClass      | M, Y      | FTIRP.objectClass                                                       | Notification header - see [4]. It shall carry the FTIRP class name.       |
+| objectInstance   | M, Y      | FTIRP.objectInstance                                                    | Notification header - see [4]. It shall carry the DN of the FTIRP.        |
+| notificationId   | M, N      | --                                                                      | Notification header - see [4].                                            |
+| eventTime        | M, Y      | --                                                                      | Notification header - see [4].                                            |
+| systemDN         | C, Y      | --                                                                      | Notification header - see [4].                                            |
+| notificationType | M, Y      | "notifyFileReady "                                                      | Notification header - see [4].                                            |
+| fileInfoList     | M, N      | See clause 6.3.1.3 (output parameters of listAvailableFiles operation). | It specifies the information of the available file.                       |
+| additionalText   | O, N      | String                                                                  | It carries vendor-specific semantics not defined in the present document. |
+
+#### 6.5.1.3 Triggering Event
+
+##### 6.5.1.3.1 From-state
+
+*filesAreReadyAndClosed*
+
+| Assertion Name         | Definition                                                                                              |
+|------------------------|---------------------------------------------------------------------------------------------------------|
+| filesAreReadyAndClosed | IRP Agent has stored the result data into one or more files which corresponds to management operations. |
+
+##### 6.5.1.3.2 To-state
+
+*newNotificationReported*
+
+| Assertion Name          | Definition                                                                                                                                                                                                    |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| newNotificationReported | The 'notifyFileReady ' notification is emitted to the subscribed IRP Manager(s). Based on the information contained in the notification, the IRP Manager can get the file(s) through file transfer mechanism. |
+
+### 6.5.2 Notification notifyFilePreparationError (M)
+
+#### 6.5.2.1 Definition
+
+The subscribed IRPManagers are notified regarding the occurrence of an error during the preparation of the file. This notification is an event and will not be treated as alarms defined in Alarm IRP IS (3GPP TS 32.111-2 [3]).
+
+#### 6.5.2.2 Input Parameters
+
+| Parameter Name   | Qualifier | Matching Information                                                    | Comment                                                                                                                                                                                                                              |
+|------------------|-----------|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| objectClass      | M, Y      | FTIRP.objectClass                                                       | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+| objectInstance   | M, Y      | FTIRP.objectInstance                                                    | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+| notificationId   | M, N      | --                                                                      | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+| eventTime        | M, Y      | --                                                                      | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+| systemDN         | C, Y      | --                                                                      | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+| notificationType | M, Y      | "notifyFilePreparationError"                                            | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+| fileInfoList     | M, N      | See clause 6.3.1.3 (output parameters of listAvailableFiles operation). | If file is kept, this parameter Identifies the file whose preparation provoked an error. If file is not generated, this parameter is empty.                                                                                          |
+| reason           | M, N      | --                                                                      | The detailed reason is given, including<br>- errorInPreparation<br>- hardDiskFull<br>- hardDiskFailure<br>- tooManyFiles<br>- collectionTimeOut<br>- incompleteTruncatedFile<br>- corruptedFile<br>- lowMemory<br>- dataNotAvailable |
+| additionalText   | O, N      | --                                                                      | See Table 6.5.1.2.                                                                                                                                                                                                                   |
+
+#### 6.5.2.3 Triggering Event
+
+##### 6.5.2.3.1 From-state
+
+*errorInPreparation OR hardDiskFull OR hardDiskFailure OR tooManyFiles OR collectionTimeOut OR incompleteTruncatedFile OR corruptedFile OR lowMemory OR dataNotAvailable*
+
+| Assertion Name          | Definition                                                                                 |
+|-------------------------|--------------------------------------------------------------------------------------------|
+| errorInPreparation      | There is unspecified error when IRPAgent prepares the files.                               |
+| hardDiskFull            | The file system is full and no more files can be opened.                                   |
+| hardDiskFailure         | The hard disk has failed and normal input/output cannot be performed.                      |
+| tooManyFiles            | The file system lacks resource to open a new file to capture management data.              |
+| collectionTimeOut       | The collection time of management data into files takes too long.                          |
+| incompleteTruncatedFile | The file is truncated for unspecified reason. The suspect flag should be set in the files. |
+| corruptedFile           | The file is corrupted for unspecified reason. The suspect flag should be set in the files. |
+| lowMemory               | The system lacks sufficient memory to open a new file to capture management data.          |
+| dataNotAvailable        | Management data is not available when the collected management object(s) is being read.    |
+
+##### 6.5.2.3.2 To-state
+
+*fileIsKept OR fileNotGenerated*
+
+| Assertion Name   | Definition                                                                                                                                                                                                                        |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| fileIsKept       | The file, whose preparation provokes an error, is kept. And the file naming convention, expiration date, available to be listed, etc. should be treated the same as and be consistent with case when file is prepared successful. |
+| fileNotGenerated | No file was generated and fileInfoList indicates "no file".                                                                                                                                                                       |
+
+# Annex A (normative): File Naming Convention
+
+The following convention shall be applied for file naming:
+
+<managementData\_type><file\_ready\_date><file\_ready\_time><file\_expiration\_delta\_time>  
+[<specificIRP\_extension>][<separator><RC>]
+
+- 1) The managementData\_type field is the type of the management data contained in the file, the value of managementData\_type field including
+
+"PM" for performance data files,
+
+"CM" for configuration files (except inventory),
+
+"IM" for inventory files,
+
+"TE" for test files,
+
+"CT" for call trace files,
+
+"NL" for notification log files,
+
+"CG" for charging files,
+
+"OT" for other files.
+
+- 2) The file\_ready\_date field is of the form YYYYMMDD, where:
+
+- YYYY is the year in four-digit notation;
+- MM is the month in two digit notation (01 - 12);
+- DD is the day in two digit notation (01 - 31).
+
+The file\_ready\_date is the date when the file was last closed and made available for upload and the file content will not be changed.
+
+- 3) The file\_ready\_time field is of the form HHMMshhmm, where:
+
+- HH is the two digit hour of the day (local time), based on 24 hour clock (00 - 23);
+- MM is the two digit minute of the hour (local time, 00 - 59);
+- s is the sign of the local time differential from UTC (+ or -), in case the time differential to UTC is 0 then the sign may be arbitrarily set to "+" or "-";
+- hh is the two digit number of hours of the local time differential from UTC (00 - 23);
+- mm is the two digit number of minutes of the local time differential from UTC (00 - 59).
+
+The file\_ready\_time is the time when the file was last closed and made available for upload and the file content will not be changed.
+
+- 4) To reduce length of the file name, the file\_expiration\_delta\_time field could be a delta time interval from file ready time. The unit is hour.
+- 5) The specificIRP\_extension field is used for other IRPs to extend the extra file naming convention which is not covered by the basic file naming convention defined in FileTransferIRP.
+- 6) The RC parameter is a running count, starting with the value of "1", and shall be appended only if the filename is not unique, i.e. more than one file is generated and all other parameters of the file name are identical.
+- 7) The separator field is "\_-\_", which is an underscore character (\_), followed by a minus character (-), followed by an underscore character (\_).
+
+# Annex B (informative): Change history
+
+| Change history |        |           |      |     |                                                                                                                    |     |       |        |
+|----------------|--------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------|-----|-------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                    | Cat | Old   | New    |
+| Dec 2003       | SA_2 2 | SP-030637 | --   | --  | Submitted to TSG SA#22 for Information                                                                             | --  | 1.0.0 |        |
+| Jun 2004       | SA_2 4 | SP-040244 | --   | --  | Submitted to TSG SA#24 for Approval                                                                                | --  | 2.0.0 | 6.0.0  |
+| Jun 2005       | SA_2 8 | SP-050292 | --   | --  | Apply Generic System Context                                                                                       | --  | 6.0.0 | 6.1.0  |
+| Mar 2006       | SA_3 1 | SP-060089 | 0002 | --  | Correct ambiguity of object class and object instance usage in notification                                        | F   | 6.1.0 | 6.2.0  |
+| Jun 2007       | SA_3 6 | --        | --   | --  | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | --  | 6.2.0 | 7.0.0  |
+| Mar 2009       | SA_4 3 | SP-090207 | 0003 | --  | Include reference to SOAP Solution Set specification                                                               | D   | 7.0.0 | 8.0.0  |
+| Dec 2009       | -      | -         | -    | -   | Update to Rel-9 version (MCC)                                                                                      | -   | 8.0.0 | 9.0.0  |
+| Mar 2011       | -      | -         | -    | -   | Update to Rel-10 version (MCC)                                                                                     | -   | 9.0.0 | 10.0.0 |